Search This Blog

Loading...

Thursday, May 21, 2015

Task Sequence installs Windows to wrong drive

When deploying install.wim (from DVD) using System Center Configuration Manager 2012, you will see that the installation is done on drive D:\ instead of the expected drive C:\.

Even though the Task Sequence reported that the installation was done on C:\

image

image

You will be able to use different methods around this problem, but the fastest and easiest way will often be to use the Task Sequence variable OSDPreserveDriveLetter.

Set the variable to FALSE as shown here:

image

Insert the variable immediately before  Apply Operating System

And the result after using OSDPreserveDriveLetter = False:

image

This is actually a problem with more to it than you might think, so read this post if you want to know more and also other possible solutions.

How to Ensure that Windows Installs on C: During a System Center 2012 Configuration Manager OSD Task Sequence

Tuesday, May 12, 2015

Update SCCM client with latest RollUp in a Task Sequence

Microsoft release Rollup update for System Center Configuration manager and they will normally also include a client update.

But if you do nothing and just use a standard task sequence your client version will be the one released together with SCCM 2012 R2.

As shown her (all versions are 5.00.7958.1000):

clip_image001

There are a lot of ways around this problem but lets take a closer look on a fairly simple one using OSD:

I our Task Sequence, just before Setup Windows and Configuration Manager, we can copy the current MSP patch from the latest Rollup to a local folder.

xcopy configmgr2012ac-r2-kb3054451-x64.msp C:\Windows\SCCMHotfix\ /E /H /C /I /Q /Y

image

You will be able to find the name of the MSP file in the latest update in the hotfix folder of your SCCM 2012 R2 installation:

image

You can see the KB number needed on the source folder on the latest RollUP package -  if in doubt:

image

Now use the PATCH property with the local path to the MSP file:

PATCH="C:\Windows\SCCMHotfix\configmgr2012ac-r2-kb3054451-x64.msp"

image

And when trying the Task Sequence again the client is updated as shown her:

image

In the above I used the x64 version, you must of course use the correct file name, matching your version (x64 or x86).

Using hardcoded c:\ might not always be the best solution, so if you experience problems you could go for the OSDISK variable to control the destination:

clip_image001[4]

clip_image001[6]

clip_image001[8]

Thursday, May 7, 2015

Has SCCM 2012 R2 CU5 been installed?

Cumulative Update 5 for System Center Configuration Manager 2012 R2 has been released https://support.microsoft.com/en-gb/kb/3054451

Note that ConfigMgr 2012 R2 SP1 is expected next week, so you might just wait for that one instead of installing CU5.

image

So once again it’s time to take a closer look at how to determine the installation status of this cumulative update, this time for CU5.

After upgrading to System Center Configuration Manager 2012 R2 CU5, you will be able to identify the update as shown here.

First let us take a look at the console, after the update the console reports version 5.0.7958.1604

image

The console reported version 5.0.7958.1501 before updating which is 2012 R2 CU4.

clip_image001

The Console update is also listed in Control Panel as an Installed Update.

image

The site will still report version 5.00.7958.1000 after the update.

clip_image001[4]

In order to check if the update has been applied we must look in the registry.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup\CULevel

CULevel reports 5 after CU5 has been applied.

image

Before updating CULevel reported 4 because Cumulative Update 4 was installed.

clip_image001[6]

This update is also visible under Installed Updates in Control Panel.

image

The client will report 5.00.7958.1604 after it has been updated.

image

With these components updated:

image

Before updating the client reported 5.00.7958.1501 for 2012 R2 CU4 client

clip_image001[10]

CU5 includes an update for SCEP.

Which means that scepinstall.exe file in the ConfigMgr install folder “.\Program Files\Configuration Manager\Client” will be updated to version 4.7.0209.0

image

Before updating the version was 4.6.0305.0 which is the version from 2012 R2 CU4 (October 2014 update)

clip_image001[8]

And finally as reported by the client after update 4.7.209.0.

image

The SCEP update is a revised version of the February 2015 SCEP update

https://support.microsoft.com/en-gb/kb/3041687

Monday, May 4, 2015

Identify VMM RU6 installation (Update Rollup 6)

Microsoft has released Update Rollup 6 for System Center 2012 R2 Virtual Machine Manager Update Rollup 6 for System Center 2012 R2 Virtual Machine Manager

If you manually download the update packages from the Microsoft Update Catalog and install them by double-clicking the packages, you have to install the Virtual Machine Manager Server package as an elevated user.

image

You can install the Virtual Machine Manager Administrator Console package by double-clicking the package also as an elevated user.

Please note that there has been some problems with the naming, so the x64 Admin console update might be in the x86 cab file.

image

If you also have the Administrator Console installed on the VMM server, install the updates in the following order:

  • Update Rollup 6 for Virtual Machine Manager Server
  • Update Rollup 6 for the Administrator Console

Between these two installations, Virtual Machine Manager Server might create a critical error log under the VMMLogs directory. This issue occurs because the Administrator Console shares some DLLs with Virtual Machine Manager Server, and a version conflict could lead to the logging of the critical failure. To resolve this issue, install both updates on the Virtual Machine Manager Server that you use to start the Virtual Machine Manager Service.

Let’s take a look on how we identify the versions installed.

First the administrative console, you can see the current version by selecting about in the console:

clip_image001

After the RU6 update for the console has been installed, you should see version 3.2.8002.0:

image

Before updating my console showed version 3.2.7895.0 for CU5:

clip_image001[4]

You can also see the installed update by looking in installed Updates with RU6 you should see

Update Rollup 6 for Microsoft System Center Virtual Machine Manager Administrator Console (x**) (KB3050947):

image

You can find the current version for the VMM server by right clicking the server in the console and selection Properties:

clip_image001[6]

After updating the server with RU6 you should see version 3.2.8002.0:

image

Before I updated my server, the version was 3.2.7895.0 for RU5:

clip_image001[8]

The Server update is also visible in installed Updates, when RU6 is installed you should see

Update Rollup 6 for Microsoft System Center Virtual Manager Server (x64) (KB3050317):

image

The VMM agent version on your Hyper-V servers can be found by right clicking the Hyper-V server and select Properties.

If you have chosen to display the column Agent version you can see it directly on the host (Blue box):

image

After the VMM agent has been updated to RU6 you should see version 3.2.8002.0:

image

Before I updated the VMM Agent it showed 3.2.7895.0 for RU5:

clip_image001

You can use the Update Agent command to update your Hyper-V hosts:

clip_image001[10]

The VMM Agent version can also be found in Programs and Features on the Hyper-V host, after update you should see version 3.2.8002.0:

image

One interesting change is the possibility to add a Azure subscription to the VMM console and do some very lightweight administration on Azure VM’s, but more on that later:

image

Before RU5, users had to manually update the DHCP extension after update rollup installation on all hosts. This is now automated. After the DHCP extension is replaced in the Virtual Machine Manager server's installation folder to the latest version, Virtual Machine Manager automatically checks the DHCP extension against all hosts. If the host has an older version of DHCP extensions, the agent version status will be displayed as "DHCP extension needs to be updated in host properties on the Status page." The user calls the update agent and updates the DHCP extension on the Hyper-V host in the same way that the user did this for the Virtual Machine Manager agent. Also, if the VSwitch is a logical switch, the status will be shown in "logical switch compliance." The user can remediate the logical switch. This will also update the DHCP extension on the host.

So this version check is not any longer necessary, but included for historical reasons:

And finally we should check the installation of Microsoft System Center Virtual Machine manager DHCP Server (x64) on the Hyper-V hosts, we can do this by a PowerShell command:

Get-WmiObject -Class win32_product -Filter 'Name = "Microsoft System Center Virtual Machine Manager DHCP Server (x64)"'

clip_image001[17]

You can also here find the same information in Programs and Features on the Hyper-V host:

clip_image001[19]

The MSI file for installing the updated version of the System Center Virtual Machine Manager DHCP Server (x64) component can be found on your VMM server after updating the server to RU4

C:\Program Files\Microsoft System Center 2012 R2\Virtual Machine Manager\SwExtn (depending on were you installed VMM but this is default):

clip_image001[21]