SCCM 2012 R2 – MDT 2013 UEFI OS Deployment Error

I recently upgraded to SCCM 2012 R2 and also upgraded to MDT 2013 to take full advantage of its OS deployment goodies. Everything has been going well until I decided I’d like to deploy an OS to a 2nd Generation Hyper-V Virtual Machine. I started getting all sorts of different errors. It really started driving me insane. A lot of four letter words were used. For that I am sorry. Good news is, I got it working in the end.

Here are some of the errors that I was receiving. Sometimes it would error before it pre staged the WINPE image, sometimes after. Sometimes after a reboot.

I received a (0xC00000005) error.

 

A generic memory error.

 

An “Unable to find a raw disk that could be partitioned as the system disk” error that resulted in a (0x8007000F) error.

 

And the weirdest one I got, was after the partitions and disk had been setup and SCCM rebooted, it came up with a 0xc0000359 error saying the storvsc.sys was missing.

 

 

By this time I’d be round and round and round in circles. It’s then I found a blog post that showed me to change the Partition Variable for the OSDisk from OSDTemporaryDrive to OSDisk. This is apparently set by default to OSDTemporaryDrive in MDT 2013. Seems like a bit of a fail to me L Could I please have a day and half of my life back please Microsoft. That is all.

In the task sequence, look in the Initialization folder for the 4 different format and partition steps.

If you look at the OSDisk partition, you’ll find that its variable is set to OSDTemporary Drive.

 

Change this to OSDisk.

That’s all you need to do.

 

 

 

Hyper-V Error – An Authentication error.

Hyper-V Error – An Authentication error has occurred. The Local Security Authority cannot be contacted.

Today I was trying to connect to a Hyper-V Virtual Machine when I started to get this error on all of the VM's on that particular host. I was connecting to the Hyper-V host via a Windows 8 Workstation via the Hyper-V Manager.

Hyper-V Error

At first I thought it was an issue with my account, but it wasn't. After hunting around for ages and running out of ideas, I stumbled across the obvious. The Hyper-V host didn't have the correct DNS servers set.

ncpa.cpl

So I changed the DNS Servers to the correct ones that were being used in my Domain and bob was my uncle!

DNS Servers

 

Hope this helps!

 

 

 

Hyper-V Virtual Machine Error 0x80070569

If you find you are getting a similar error 0x80070569 on Hyper-V 2012, you might be experiencing something similar to this.

So I jumped on to one of my Hyper-V hosts the other day to bang out a fresh Virtual Machine. I clicked on Create New Virtual Machine and BAM!, I get this error.

 

30-04-2013 6-11-55 PM

 

Try restarting the Hyper-V Virtual Machine Management Service.

I wasn't sure if I could restart this service while I had Virtual Machines running, but since it was on my home lab environment, I thought I'd give it a shot. The service restarted with no issues on any of my virtual machines. What's more, when I tried to create a virtual machine, it worked, no error. I'm not sure why this happens or why restarting the service fixes it as it seems by the error to be a permissions issue but as a work around it seems to do the trick.

 

Installing the Hyper-V Feature via Powershell on Windows Server 2012

 

Open up a Powershell Console as an Administrator.

 

We can use the Get-WindowsFeature cmdlet to find what Hyper-V features are available for installation.

 

PS>Get-WindowsFeature –Name hyper-v*

 

This will show the Hyper-V features that we can install. 

Once we know what we would like to install. We can use the Install-WindowsFeature cmdlet to install the feature. We can use the IncludeSubFeature and IncludeManagementTools parameters to install all subfeatures and management tools at the same time. The –Restart parameter will make the machine reboot once it has finished installing.

 

PS>Install-WindowsFeature –Name Hyper-V –IncludeSubFeature –IncludeManagementTools –Restart

The Feature will then install. 

After a reboot, you should be able to see the Hyper-V Manager in your Start Page.