New System Center 2012 VHDs available

Yesterday Microsoft has released System Center 2012 VHDs, based on Service Pack 1 (beta). Thay way it's very easy to have a look at all new functionality in a demo environment. The downloads consists of files that must be extract into a single pre-configured VHD file for this System Center component. The VHD enables you to create a virtual machine to evaluate the different System Center components.

The VHDs can be found on the following locations:

System Center 2012 Service Pack 1 Beta – Data Protection Manager – Evaluation (VHD)

System Center 2012 Service Pack 1 Beta – Operations Manager – Evaluation (VHD)

System Center 2012 Service Pack 1 Beta – Orchestrator – Evaluation (VHD)

System Center 2012 Service Pack 1 Beta – App Controller – Evaluation (VHD)

System Center 2012 Service Pack 1 Beta– Service Manager – Evaluation (VHD)

Unfortunately no VHD is available for System Center 2012 Configuration Manager (ConfigMgr) with Endpoint Protection. Maybe it will be released at a later moment. Just have fun with the already available ones!

How to create a reference image in ConfigMgr

In ConfigMgr 2007 and 2012 the most used functionality is Operating System (OS) deployment. With OS deployment it's possible to migrate or install an unknown or known system, which can be a server, fat client (desktop or notebook), thin client or virtual desktop. To migrate or install an unknown or known system, a reference image is needed. This is the image created on a (virtual) system, which is prepared for deployment. Unfortunately you can't use the Install.wim from the Windows XP, Vista or Win7 ISO file, because it will be installed on the D: drive by default. That's the Microsoft way for creating images :)

A reference image can be created with a Build and Capture task sequence, which is the preferred way. All Windows files from a ISO file must be imported in ConfigMgr to use this task sequence. A Windows OS will be installed on the host system, Sysprep is running which reboots the system, Windows PE will start automatically and a reference image will be uploaded to the ConfigMgr server. A default Build and Capture can be created within the task sequence wizard. The ConfigMgr client will be installed in this reference image (mandatory step).

Another possibility is using ConfigMgr Capture media on an already installed system. That way the system must be joined to a workgroup and Sysprep files must be present on the host OS. In Windows 7 or Windows 8 this isn't needed, because Sysprep is build-in. When ConfigMgr Capture media is started (within Windows, because it isn't bootable) Sysprep is running which reboots the system. Windows PE will start automatically after reboot and a reference image will be uploaded to the ConfigMgr server. No ConfigMgr client will be installed this time.

A reference image contains software updates and maybe a few applications like DotNet Framework for example. It's not a best practice to install user-specific applications in the reference image. Just keep it as clean as possible! That's also the reason to create it on a virtual machine, because less drivers are needed. When using ConfigMgr 2007 it's needed to install software updates during Build and Capture to have an updated image. In ConfigMgr 2012 it's not needed anymore to install software updates during installation. Just build the image and use Offline Servicing in ConfigMgr 2012 for offline update integration.

With Windows Server 2012 and Windows 8 (which will be supported in ConfigMgr 2012 SP1), no reference image is needed anymore. Within Windows Server 2012 and Windows 8 it's possible to mount an ISO file by richtclick and mount it, without the need for additional software. Just copy the Install.wim from the (mounted) ISO file and import it in ConfigMgr 2012 SP1. Use Offline Servicing for offline update integration and you're done! That way you can save a lot of time which can be used for all new awesome functionality in ConfigMgr!

That's it for now. If there are still questions about this topic, use comments below.

One management product to rule them all

As mentioned in my other blogposts, Service Pack 1 for System Center 2012 will become available in Q1 2013. With SP1 for ConfigMgr 2012 (which is part of System Center) a lot of new functionality is added to this already awesome product. In this blogpost I created an overview of all ConfigMgr Client support for this product. Expect a lot of new possibilities: One product to manage them all.

ConfigMgr 2012 SP1 will do management on the following OSEs:
 
Client devices:

• Windows XP SP3, Windows Vista SP2, 
• Windows 7 (SP1), Windows 8
• Windows To Go

Server devices:

• Windows Server 2003 SP2, Windows Server 2003 R2 SP2
• Windows Server 2008 SP2, Windows Server 2008 R2 (SP1)
• Windows Server 2012

Thin Clients based on Windows XP SP3:

• Windows Embedded Standard 2009
• Windows XP Embedded SP3
• Windows Fundamentals for Legacy PCs (WinFLP)
• Windows Embedded POSReady 2009
• WEPOS 1.1 with SP3

Thin Clients based on Windows 7:

• Windows Embedded Standard 7 with SP1
• Windows Embedded POSReady 7
• Windows Thin PC (SA benefit)

MAC Computers:

• Mac OS X 10.6 (Snow Leopard), Mac OS X 10.7 (Lion)

Linux and UNIX Servers:

• AIX version 5.3, 6.1, 7.1
• HP-UX version 11iv2, 11iv3
• Red Hat Enterprise Linux (RHEL) version 4, 5, 6
• Solaris version 9, 10, 11
• SUSE Linux Enterprise Server (SLES) version 9, 10 SP1, 11

Mobile devices (Depth management):

• Windows Mobile 6.1, Windows Mobile 6.5 (phones)
• Nokia Symbian Belle (phones)

EAS connected Mobile devices (Light management):

• Windows Phone 7
• Android, iOS (phones and tablets)

Windows Intune integration (Depth management): 

• Windows Phone 7, Windows Phone 8
• Windows Runtime (RT) tablets
• Android, iOS (phones and tablets)

Are you excited yet about all Operating Systems which can be managed? With ConfigMgr 2012 SP1 (and Windows Intune integration) all modern OSEs can be managed for Servers, Clients, Thin Clients and Mobiles. Installing ConfigMgr is not about managing Windows clients anymore, it's about managing a whole range of devices. The future is bright!

Resources: Supported Configurations for Configuration Manager

BSOD in Windows 8 on bridge.sys driver

Today I had several times a BSOD in Windows 8. BSOD stands for "Blue Screen Of Death", and is the result of an error. My system (with Windows 8 RTM) is installed a month ago and I've installed the Hyper-V role in it. With Hyper-V on Windows 8 it's possible to install Virtual Machines without the need to install VMware Workstation or Oracle VirtualBox.

Last days there were some Windows updates installed and a reboot was needed. After this reboot I had multiple BSOD screens and no quick solution to fix it. Looking for the error message in Event Viewer
"DRIVER_IRQL_NOT_LESS_OR_EQUAL (bridge.sys)"
it seems that Hyper-V was failing on the driver. A quick workaround for this is to plugin a network cable and deactivate Wi-Fi.

 

 

A better way to fix this is change the Virtual Switch settings in Hyper-V Manager. Just look at the settings configured at your external connection, and untag "Allow management operating system to share this network adapter" in Connection type. After that my system is stable again and no unexpected reboots are longer present. Hope there is a Microsoft fix for this issue soon.

Update: I don't know if it matters, but configure the Hyper-V connection type on your fixed NIC adapter, not on your Wi-Fi adapter. For it seems some people still have issues otherwise.

Update 23-7-2013: For it seems the issue is still valid. I'm using Internet Connection Sharing (ICS) for a while now, so no need to configure a bridge. With ICS you can share internet from a fixed or Wi-Fi connection to the vEthernet connection. Much better that way, and no BSOD issues on the bridge.sys driver.

Thin Client management in ConfigMgr 2012

Manage Devices Through a ‘Single Pane of Glass’

In the past years I've installed Symantec Altiris Deployment Solution and Wyse Device Manager a few times for HP and Wyse Thin Client (TC) management. With these products BIOS settings can be changed, the Write filter can be activated/de-activated, and Windows Embedded and additional software packages can be deployed. Even Patch management is available for Windows Embedded. Microsoft has a TC management solution itself, it's called: Windows Embedded Device Manager.

Windows Embedded Device Manager (WEDM) enables enterprises to deploy, assess and update Windows Embedded devices, providing a single management solution (Single Pane of Glass) that offers enhanced insight and control over IT infrastructure and systems by extending the capabilities of  System Center Configuration Manager (ConfigMgr) 2007. More information about WEDM 2011 can be found HERE.

But now ConfigMgr 2012 is available (!), and we want management in that, do we? Therefore WEDM 2012 support is needed. WEDM 2012 will be available in the first quarter (Q1) of 2013 to support System Center 2012 Configuration Manager customers. This release will be in the same quarter as the System Center 2012 SP1 release, Nice!
 
With ConfigMgr 2012 SP1, the capabilities of ConfigMgr will be extended to manage Windows Embedded thin clients, Point-of-Sale (POS) terminals, digital signage, kiosks, and Thin PC's. This functionality means additional devices can be managed by ConfigMgr 2012 SP1 without requiring any additional software. Isn't that great!?

Expect to manage al physical, virtual and mobile devices in one single Microsoft management solution: ConfigMgr 2012. This with Windows Intune integration (cloud-based device management) and WEDM 2012. ConfigMgr will be more advanced with every release.

Update 24-9-2012: Steve Beaumont mentioned to me that WEDM 2012 has been cancelled and the features will be rolled into ConfigMgr as part of SP1. Unfortunately there's nothing to be found on the web that confirms me of this integration. In this blogpost I will keep you up-to-date of this functionality.

Update 26-9-2012: Yesterday Steve Beaumont mentioned on his blog that WEDM 2012 is no more, and functionality will be in ConfigMgr 2012 SP1. That way above message is right: additional devices can be managed by ConfigMgr 2012 SP1 without requiring any additional software. With ConfigMgr 2012 SP1 no Symantec Altiris Deployment Solution and/or Wyse Device Manager is needed anymore. Just use ConfigMgr for ALL fat/thin/virtual systems!

Blog Steve Beaumont about "Windows Embedded Devices and Configuration Manager 2012 SP1" can be found HERE.

Installation Prerequisite Check for ConfigMgr 2012 SP1 Beta

Today I installed the new System Center 2012 Configuration Manager (ConfigMgr) SP1 Beta. During the upgrade some new prerequisites are needed on the ConfigMgr server. In this blogpost I will mention the new prerequisites and where to find them. There we go:

• WSUS on site server: ConfigMgr requires WSUS of at least version 3.0 SP2 with KB2720211 and KB2734608 installed
• User State Migration tool (USMT) installed: he User State Migration Tool component of the Assessment and Deployment Kit (ADK) is required and must be installed before Setup can continue
• SQL Server version: ConfigMgr sites require a supported SQL Server version with required hotfixes for site database operations to succeed (in my case I installed SQL Server 2008 R2 SP2 to go further)
• Windows Deployment Tools installed: The Windows Deployment Tools component of the Assessment and Deployment Kit (ADK) is required and must be installed before Setup can continue
• Windows Preinstallation Environment installed: The Windows Preinstallation Environment component of the Assessment and Deployment Kit (ADK) is required and must be installed before Setup can continue

After installing all prerequisites, setup can be continued.

In my next posts expect more to see about new functionality! Have a look HERE for all improvements.

Windows Server 2012 and Windows 8 support in ConfigMgr

Because Windows Server 2012 and Windows 8 are final now, it's good to know if ConfigMgr 2007/2012 has support for both Operating Systems. At the moment only MDT 2012 Update 1 has support for them. More about that HERE.

On the System Center Configuration Manager Team blog the following is mentioned:
"In ConfigMgr there will be (client) support for Windows Server 2012 and Windows 8 for both ConfigMgr 2012 and 2007 SP2 (includes R2 and R3)." 
Good news! This support and any required updates will be available in the same timeframe as System Center 2012 SP1 in early 2013.

Support in ConfigMgr 2012 SP1:

Microsoft will add the following operating systems to their client support matrix with the release of System Center 2012 SP1:

• Windows 8 Pro
• Windows 8 Enterprise
• Windows Server 2012 Standard
• Windows Server 2012 Datacenter

Note: Systems with these operating systems will also be able to host a distribution point.

Support in ConfigMgr 2007 SP2:

Microsoft will add the following operating systems to their client support matrix in System Center 2007 SP2 (includes R2 and R3):

• Windows 8 Pro
• Windows 8 Enterprise
• Windows Server 2012 Standard
• Windows Server 2012 Datacenter

Note: Though these will be fully supported as clients, there is no plan to add support for deploying these as operating systems by using the Configuration Manager 2007 operating system deployment feature. Also, no site servers or site systems will be supported on any SKU of Windows Server 2012.

So yes, there is good news, but not for customers with ConfigMgr 2007 SP2 installed. To deploy Windows Server 2012 and Windows 8 a ConfigMgr 2012 SP1 infrastructure is needed. Otherwise MDT 2012 Update 1 must be used for this. Stay tuned!

ConfigMgr 2012 SP1 is coming out early 2013

On the Server & Cloud blog the following is mentioned:
"Look for availability of System Center 2012 Configuration Manager SP1 and the next release of Windows Intune in early 2013."

Support for Windows Server 2012, SQL Server 2012 and Windows 8 must wait till early 2013 I guess. I hope the release will be much sooner than this, because Microsoft Deployment Toolkit (MDT) 2012 Update 1 already supports these Operations Systems.

Microsoft Deployment Toolkit (MDT) 2012 Update 1 is the newest version of MDT, a Solution Accelerator for operating system and application deployment. MDT 2012 Update 1 supports deployment of Windows 8, Windows 7, Office 2010 and 365, Windows Server 2012, and Windows Server 2008 R2 in addition to deployment of Windows Vista, Windows Server 2008, Windows Server 2003, and Windows XP.

Look for more on Microsoft TechNet: System Center 2012 Configuration Manager SP1 Beta and Windows Intune Update

MDT 2012 Update 1 can be download right now: HERE.

Choose the right SQL Collation during installation

During SQL Server installation you must choose which SQL Collation will be installed. With ConfigMgr 2012 there is just one choice which will work: SQL_Latin1_General_CP1_CI_AS. See my other blogpost about "SQL Server requirements for ConfigMgr 2012 installation" for that HERE. With OpsMgr 2012 it seems you have the choice between Latin1_General_CI_AS and SQL_Latin1_General_CP1_CI_AS during installation. Unfortunately that isn't the case. For OpsMgr 2012 the SQL Collation must also be SQL_Latin1_General_CP1_CI_AS.

This because the information on "Supported Configurations: System Center 2012 - Operations Manager" contains wrong information. It mentions: "SQL Server collation settings for all databases must be one of the following: SQL_Latin1_General_CP1_CI_AS, French_CI_AS, Cyrillic_General_CI_AS, Chinese_PRC_CI_AS, Japanese_CI_AS, Traditional_Spanish_CI_AS, or Latin1_General_CI_AS. No other collation settings are supported." This can be found HERE.

Can you still follow me? Well, the reason for that is because some functionality won't work on Latin1_General_CI_AS. With SQL_Latin1_General_CP1_CI_AS you won't have an issue on that. The issue is especially seen on the reporting functionality in the OpsMgr Data Warehouse. There will be error messages then in the Reporting pane.

On "Clarification on SQL Server Collation Requirements for System Center 2012" the following message is displayed: The SCOM data warehouse installer will always install the data warehouse with SQL_Latin1_General_CP1_CI_AS regardless of the SQL Server collation. Until this issue is fixed, please always install the SCOM operational database using SQL_Latin1_General_CP1_CI_AS. There are some compatibility issues when the SCOM operational database is Latin1_General_CI_AS and the data warehouse DB is SQL_Latin1_General_CP1_CI_AS. This can be found HERE.

I learned my lesson the hard way unfortunately. Just use the SQL Collation SQL_Latin1_General_CP1_CI_AS for every new SQL Server installation used for Microsoft System Center 2012 components from now on! Pity that Microsoft displays wrong information on the Microsoft TechNet website on this specific topic.

Next Release of Windows Intune announced!

Today the Next Release of Windows Intune is announced. The Next Release of Windows Intune is adding new client management capabilities as it relates to System Center 2012 Configuration Manager (ConfigMgr) Service Pack 1 (SP1) Beta.

Microsoft offers two separate endpoint management solutions – System Center 2012 Configuration Manager (ConfigMgr) for on-premises management, and Windows Intune for management through the cloud.  With ConfigMgr 2012 SP1 and the next version of Windows Intune, Microsoft is taking the first step in delivering interoperability between these products through Configuration Manager’s administration console. 

This will enable customers to add mobile devices managed through the cloud with Windows Intune into their ConfigMgr 2012 SP1 console and manage all the devices through one tool. While you can continue to use Windows Intune as a "fully in the cloud" management solution for PC and mobile device management, the interoperability of Microsoft's on-premises and cloud services is a big step forward for organizations that want to manage all of their devices from one place.

To evaluate the current release of Windows Intune, you can sign up for a free 30-day trial of Windows Intune at the Microsoft website.   

Brad Anderson mentioned during MMS 2012 in Las Vegas already: Regarding Windows Intune and ConfigMgr: "as we go forward we are going to bring these two closer together".

Great to see that ConfigMgr 2012 and Windows Intune now works together to manage both on-premises and through the cloud! Look for availability of ConfigMgr 2012 SP1 and the next release of Windows Intune in early 2013.

More information about Windows Intune can be found HERE.

System Center 2012 SP1 (Beta) available now!

Today the System Center 2012 Service Pack 1 Beta has become available. Service Pack 1 (SP1) will bring many important improvements to all System Center components. Let's have a look at the new Configuration Manager (ConfigMgr) 2012 features.
 
One of the most significant changes is support for Windows 8. Configuration Manager SP1 supports Windows 8 in the following ways:

• You can install the Configuration Manager client on Windows 8 computers and deploy Windows 8 to new computers or to upgrade previous client operating versions. Configuration Manager also supports Windows To Go.
• Configuration Manager supports Windows 8 features, such as metered Internet connections and Always On Always Connected.
• You can configure user data and profiles configuration items for folder redirection, offline files, and roaming profiles.
• You can configure new deployment types for Windows 8 applications, which support standalone applications (.appx files) and links to the Windows Store.

 Other significant changes include the following:

• Support for Windows Server 2012 and SQL Server 2012.
• Clients are now supported on Mac computers, and on Linux and UNIX servers.
• Windows PowerShell cmdlets are available to automate Configuration Manager operations by using Windows PowerShell scripts.
• Support for cloud services, including a new distribution point for Windows Azure.
• More flexible hierarchy management with support to expand a stand-alone primary site into a hierarchy that includes a new central administration site, and the migration of a Configuration Manager SP1 hierarchy to another Configuration Manager SP1 hierarchy.
• Support for multiple software update points for a site to provide automatic redundancy for clients in the same way as you can configure multiple management points.
• Client notification to initiate some client operations from the Configuration Manager console, which include downloading computer policy and initiating a malware scan to be performed as soon as possible, instead of during the normal client policy polling interval.
• Support for virtual environments that allow multiple virtual applications to share file system and registry information instead of running in an isolated space.
• Email alert subscriptions are now supported for all features, not just Endpoint Protection.

Great to see that Windows Server 2012, SQL Server 2012 and Windows 8 are all supported now. Also good to see that significant changes has been added to this already great product. There's still more to come in ConfigMgr with new Service Packs and Releases!

With SP1, the capabilities of ConfigMgr 2012 will be extended to manage Windows Embedded thin clients, Point-of-Sale (POS) terminals, digital signage, kiosks, and Thin PC's. This functionality means additional devices can be managed by ConfigMgr 2012 SP1 without requiring any additional software. Isn't that great!?

More information can be found HERE. The Beta is now available for download on the Microsoft Download Center website.

Overview of new Microsoft 2012 exams

Today I passed the System Center 2012 Configuration Manager (ConfigMgr) exam. ConfigMgr 2012 is the only System Center product with a dedicated exam. The other System Center products are bundled in a Microsoft Private Cloud exam. Because of new Microsoft System Center 2012 exams, Windows Server 2012 exams, and Windows 8 exams, I place a complete overview in this blogpost. Here we go!

MCTS: System Center 2012
 
70-243 Administering and Deploying System Center 2012 Configuration Manager
As mentioned earlier this is just for ConfigMgr 2012. The other System Center 2012 products are bundled in the Microsoft Private Cloud exams.

MCSE: Microsoft Private Cloud
 
70-246 Monitoring and Operating a Private Cloud with System Center 2012
70-247 Configuring and Deploying a Private Cloud with System Center 2012 
All System Center 2012 products (except ConfigMgr 2012) are bundled in these exams. More information about both exams HERE
More information: Microsoft Learning
 
MCSA: Windows Server 2012
 
70-410 Installing and Configuring Windows Server 2012
70-411 Administering Windows Server 2012
70-412 Configuring Advanced Windows Server 2012 Services 
The MCSA: Windows Server 2012 certification shows that you have the primary set of Windows Server skills that are relevant across multiple solution areas in a business environment.
More information: Microsoft Learning

MCSE: Server Infrastructure
 
70-413 Designing and Implementing a Server Infrastructure
70-414 Implementing an Advanced Server Infrastructure
The MCSE: Server Infrastructure certification validates your ability to build comprehensive server infrastructure solutions.
More information: Microsoft Learning
 
MCSE: Desktop Infrastructure
 
70-415 Implementing a Desktop Infrastucture
70-416 Implementing Desktop Application Environments
The MCSE: Desktop Infrastructure certification validates your skills in desktop virtualization, remote desktop services and application virtualization.
70-417 Upgrading Your Skills to MCSA Windows Server 2012
If you have an MCSA: Windows Server 2008 certification, you may take Exam 417 to upgrade to the MCSA: Windows Server 2012.
More information: Microsoft Learning
 
MCSA: Windows 8
 
70-687 Configuring Windows 8
At the moment this is the only Windows 8 exam available.
70-688 Managing and Maintaining Windows 8
Update 18-1-2013: A new Windows 8 exam is available now!
70-689 Upgrading Your Skills to MCSA Windows 8
The MCSA: Windows 7 certification allows you to upgrade to the MCSA: Windows 8 certification, by taking a single upgrade exam.
Update 18-1-2013: The Windows 8 upgrade exam is available now!
 
That's it for now! I think there will be more exams to come about deployment with MDT 2012. This in combination with Windows 8 and Office 2013. With these exams there's lot to do next months! :)

Error in ConfigMgr 2012 Self Service Application Catalog

Last days I installed a new ConfigMgr 2012 demo environment. Everything was working fine after installation on my server, but when accessing a client it went wrong. It wasn't possible to start the Self Service Application Catalog from within the Software Center.

The following error message was displayed here:
Could not load type 'System.ServiceModel.Activation.HttpModule' from assembly 'System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
 

 
Good news is there's an easy solution for this, which can be find on: Microsoft Support
 
To resolve this issue, run the following command line:
aspnet_regiis.exe /iru
 
The Aspnet_regiis.exe file can be found in one of the following locations:
%windir%\Microsoft.NET\Framework\v4.0.30319 (x86 computer)
%windir%\Microsoft.NET\Framework64\v4.0.30319 (x64 computer)

Cause of this has something to do with IIS and .NET installation order. After run this command the Self Service Application Catalog is working! Now it's possible to use this great new functionality.

Vacation time!

Today my vacation is starting for the next coming weeks. During my vacation there will be no new blogposts as you can guess :) So enjoy yourself (I will do also) and expect a lot of new information and knowledge later this year. There will be lot to write and share about upcoming and already available Microsoft products.

Thanks for visiting my blog and see you later!

It's vacation time now!



Location of OpsMgr 2012 installation logfiles

During installation of OpsMgr 2012 bad things can happen (sometimes). Then it's very useful to know where the installation logfiles are placed, to know what's going on. Yesterday I wrote a blogpost already about a Microsoft update which brakes the OpsMgr installation. That blogpost can be found HERE. Today I explain where the installation logfiles resides.

Just open Windows Explorer for that and browse to the
%LocalAppData%\SCOM\Logs directory. Then the following logfiles can be seen:

• FullPrereq.xml: Contains adjusted prerequisite check information
• OMConsole.log: Verbose logging of installation of the Operations console
• OMServer.log: Verbose logging of installation of the mgmt server role
• OpsMgrSetupWizard.log: Reports activity and progress of setup wizard
• SCOMPrereqCheck.log: XML output of the prerequisite checker
• Setup(x).log: Detailed logging of installation progress
• WebConsole.log: Verbose logging of installation of the Web console

Because of multiple installations yesterday, I also have multiple Setup(x).log files in my Logs directory.

On the SQL Server where I've installed the Reporting component the following logfiles can be seen:

• FullPrereq.xml: Contains adjusted prerequisite check information
• OMReporting.log: Logs progress of installation of the reporting feature
• OpsMgrSetupWizard.log: Reports activity and progress of setup wizard
• SCOMPrereqCheck.log: XML output of the prerequisite checker
• Setup(x).log: Detailed logging of installation progress

Because of these logfiles you know where to look for troubleshooting. In my opinion these logfiles are viewed best with Trace32.exe which can be found HERE. Just install the "System Center Configuration Manager 2007 Toolkit V2" and open Trace32.exe for making it the default viewer for logfiles. Hope to help other people this way!

Cannot start service OMSDK during OpsMgr 2012 setup

Today i ran into an error during a new (clean) OpsMgr 2012 installation. During the Prerequisite Check all went fine, but when installation started it went wrong. The errors started during the installation of new System Center services. There were errors like:

• Cannot start service OMSDK on computer
• The System Center Data Access service could not start
• A timeout was reached (30000 milliseconds) while waiting for the System Center Data Access Service service to connect.
• No connection could be made because the target machine actively refused it <IP-address>:5724

I've seen a lot off solutions for this errors, but for me this were the right ones:

• A service does not start + reboot the server
• SDK and Configuration service timeouts + reboot the server

They mentions:

The service control manager waits for the time that is specified by the ServicesPipeTimeout entry before logging event 7000 or 7011. Services that depend on the Windows Trace Session Manager service may require more than 60 seconds to start. Therefore, increase the ServicesPipeTimeout value appropriately to give all the dependent services enough time to start.

We had the same problem both services failed to start after applying windows updates. It also caused a problem with de SQL reporting service(s) not automatically starting after a restart. The update that caused the problem for us was 'Update for Microsoft Windows (KB2677070)'. After removing that update both services started fine again and on servers with the SQL Reporting Service installed it would start automatically once again.

After this the Data Access service was started and OpsMgr 2012 installation was continuing! How it's possible that Microsoft releases a patch (which is still available) that brakes the OpsMgr 2012 setup? Hope they have a fix for this issue soon.

How to Create a Windows To Go USB Drive

With Windows 8 coming within a few months it's good to have a look a new functionality. One way to install Windows 8 is on a VHD (Virtual Hard Disk). New in Windows 8 is the option to mount VHD files and boot from it! A guide to install Windows 8 on a VHD can be found HERE. Great that so many people viewed this blogpost to install it that way. In this blogpost I explain the new Windows To Go functionality.

Windows To Go is an enterprise feature of Windows 8 that enables users to boot Windows from a USB-connected external drive. Windows To Go drives can use the same image enterprises use for their desktops and laptops and can be managed the same way. Windows To Go is not intended to replace desktops, laptops or supplant other mobility offerings. Rather, it provides support for efficient use of resources for alternative workplace scenarios.

 You need the following for installation:

• 16 GB or larger USB 2.0 / 3.0 Drive
• Windows 8 Release Preview ISO (download HERE) 
• ImageX.exe stand-alone straight from Microsoft (download HERE)

That way you don't have to download a full copy of Windows Automated Installation Kit (AIK) for Windows 7 (1.7 GB) found HERE.

How to Create a Windows To Go USB Drive:

• Quick Format the USB device with NTFS, and create a partition on it
• Extract or mount the Windows 8 ISO and copy the Install.wim file (Sources folder) to a folder where ImageX.exe is also placed
• Have a look at the drive letter which is used for the USB device and type the following command: ImageX.exe /apply Install.wim 1 F:\ (where F: is the drive letter of your USB device)
• The result (after some time) must be "Successfully applied image"
• Once this is done the boot record on the USB device must be changed with the following command: Bcdboot.exe F:\Windows /s F: /f ALL (where F: is the drive letter of your USB device)
• The result must be "Boot files successfully created" now

After the command has completed you are ready to use your new Windows To Go USB device. Now it's time to reboot your system and start from the USB device. There will be some final configuration during first start. During the session the USB device must be plugged in.

What a great year with many new Microsoft releases and functionality!

Installing Microsoft Office 2013 Customer Preview

Today I installed the new Microsoft Office 2013 Preview. Because the existing Office 2010 installation on my Windows 8 Release Preview device, I choose for a upgrade. The installation is done in a few minutes and a reboot is needed afterwards. Then the new functionality can be used. The following tiles are available after installation:

 

Just notice that Lync 2013 is installed by default now, no other installation is needed for that. Programs that are still exists after the upgrade are:

• SharePoint Workspace 2010
• Office Picture Manager
• Lync 2010

As far as I can see everything works fine after the upgrade. Nice to see that Microsoft Office 2013 will have support for Touch devices, SkyDrive, Yammer, Skype and Cloud services now!

Microsoft Office 2013 Customer Preview has arrived

Yesterday a new Office has arrived. It's called Microsoft Office 2013.

Microsoft Corp. CEO Steve Ballmer unveiled the customer preview of the new Microsoft Office, available at office.com/preview.

The next release features an intuitive design that works beautifully with touch, stylus, mouse or keyboard across new Windows devices, including tablets. The new Office is social and unlocks modern scenarios in reading, note-taking, meetings and communications and will be delivered to subscribers through a cloud service that is always up to date.  

The new, modern Office will deliver unparalleled productivity and flexibility for both consumers and business customers. It is a cloud service and will fully light-up when paired with Windows 8

While the full lineup of offerings and pricing plans will be announced in the fall, Ballmer discussed three new Office 365 subscription services. When available, each new subscription offer will include the new 2013 editions of the Office applications. In addition, subscribers will receive future rights to version upgrades as well as per-use rights across up to five PCs or Macs and mobile devices. More about new functionality HERE

MSDN members can download Office at CLICK

Office Language Packs and other downloads at CLICK

Nice to see that Microsoft Office 2013 will have support for Touch devices, SkyDrive, Yammer, Skype and Cloud services now!

Windows 8 and Windows Server 2012 available soon

Yesterday Microsoft revealed on the Worldwide Partner Conference in Toronto that Windows 8 will be Release to Manufacturing (RTM) in the first week on August, with a release in late October to retail stores.

Today Microsoft revealed that Windows Server 2012 will be RTM at the same time (August 2012), with a release in September already.

That way both Windows 8 and Windows Server 2012 will be RTM in August and available for download also. Just a few weeks later the products are final and ready on selling points.

Good news that Microsoft has so many new releases in one year!