Search This Blog

Loading...

Friday, November 14, 2014

Hotfixes that breaks OSD

Once again I have found my self in a situation where a customer had problems with a task Sequence stopping, so now it’s time to do a post about this well known situation

You might see your Task Sequence stopping with the following error in smsts.log:

Failed to set log directory. Some execution history may be lost. The system cannot find the file specified. (Error: 80070002; Source: Windows)

image

The problem is well documented in the support case here : KB2894518

If a Microsoft System Center Configuration Manager task sequence that uses the "Install Software Updates" step installs a software update that triggers multiple restarts after the task sequence successfully runs the Install Software Updates task, the task sequence can fail.

The first restart that is initiated by the software update is controlled by the task sequence. However, the second restart request is initiated by a Windows component (typically, Component-Based Servicing) and therefore is not controlled by the task sequence. Because the second restart is not controlled by the task sequence, the task sequence execution state is not saved before the restart. When the task sequence resumes after the second restart, no state is available to continue successfully.

Unfortunately the support case is not updated the moment an update requiring multiple restarts are released, so note this issue so that you know what's going on the next time you see this error.

image

Thursday, November 6, 2014

Identify VMM RU4 installation

Microsoft has release Update Rollup 4 for System Center 2012 R2 Virtual Machine Manager http://support2.microsoft.com/kb/2992024.

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:

image

After the RU4 update for the console has been installed you should see version 3.2.7768.0:

image

Before updating my console showed version 3.2.7672.0 for CU3:

image

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

Update Rollup4 for Microsoft System Center Virtual Machine Manager Administrator Console (x**) (KB2992023):

image

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

image

After updating the server with RU4 you should see version 3.2.7768.0:

image

Before I updated my server the version was 3.2.7672.0 for RU3:

image

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

Update Rollup 4 for Microsoft System Center Virtual Manager Server (x64) (KB2992024):

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 RU4 you should see version 3.2.7768.0:

image

Before I updated the VMM Agent it showed 3.2.7672.0 for RU3:

image

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

image

The VMM Agent version can also be found in Programs and Features on the Hyper-V host:

image

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)"'

Before updating my Hyper-V server had installed version 3.2.7672.0 which is the RU3 version.

image

After upgrading to the RU4 version the PowerShell command returns version 3.2.7768.0:

image

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

image

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):

image

Wednesday, October 22, 2014

Time to Upgrade Windows 10 from build 9860 to 9878

Update 14-11-2014

Build 9879 is available, the update procedure is the same as last time, you just need to change your update pace to fast:

image

This time there the enterprise version is also available as a ISO file, in order to download this go here:

http://www.microsoft.com/en-us/evalcenter/evaluate-windows-technical-preview-for-enterprise?i=1

image

Original post

Microsoft has released a new build of Windows 10 called 9860, so how do we upgrade?

No ISO will be released for this new build so the only way is to use the build in upgrade feature.

Start by entering Windows update settings in the search field in the new start menu, and then click on Windows update settings in the top.

image

In PC settings select Preview builds and then Download now:

image

When the download is completed click Install now:

image

You can find the downloaded esd file in your Windows\SoftwareDistribution\Download folder, so here the size of the downloaded file is 2.7 GB.

image

You need to restart the computer:

image

Now wait for Windows to get ready Smile

image

And finally:

image

After the upgrade is completed you will see two new updates in windows update (KB3008956 and KB3010668), install the updates and you are ready to go (this will of course change over time Smile but valid 22-10-2014):

image