Deployment, MDT, SCCM2012RTM, UEFI

Hello!
I stumbled upon this problem when i was at a customer this week creating a Windows 8.1 image and was going to make the Microsoft Surface 2 Pro certified for deploying via CM2012R2.
As everyone knows the Surface 2 Pro uses UEFI and has no bios, and I constantly ran into different problems when trying to apply the operating system to the UEFI formated disk.
The error I got was the following (one of them after trying different fixes). ( the interesting part is highlighted with bold)

The task sequence execution engine failed executing the action (Apply Windows 8.1 Enterprise X64) in the group (Install) with the error code 2147942487
Action output: Command line for extension .exe is ”%1” %*
Set command line: ”OSDApplyOS.exe” /image:S02001F0,1 ”/config:S02001F6,Unattend.xml” /target:%OSDisk% /runfromnet:False
((g_Target.Disk > 0) || (arg == L”0″)) && (g_Target.Partition >= c_MinPartition), HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,254)
ParseCommandLine(), HRESULT=80070057 (e:\nts_sccm_release\sms\client\osdeployment\applyos\applyos.cpp,429)
The /target parameter specifies an invalid target location.. The operating system reported error 2147942487: The parameter is incorrect.

So if we take a look at the default MDT Task Sequence in ConfigMGR ( note, that this problem only occurs on SCCM 2012 RTM , AND if you upgrade from RTM to a newer version)
The default looks like this, and this will break the first step in the UEFI deployment.
What we need to do there is to remove everything EXEPT the last step. ON BOTH STEPS that are enclosed with red.

When those are removed double click the OSdisk step and change the following. Change it to OSDISK, and as you probably figured out by now… THIS is what breaks it, the value here is not OSDisk but OSDTemporaryDrive…


The next step is to change the second part of the UEFI disk format step under the “Format disk” step. Make sure the “MAKE THIS THE BOOT DISK” is checked, this is NOT checked on RTM and will break the “apply OS” step later in the TS.

Also make sure the OSDisk Primary also uses the variable OSDisk!
Next step we need to change is the “Preserve driver letter” step in the sequence so that the image applies to the driver letter we actually created the reference image from. THIS CAN BREAK the TS if you are running Windows 7 deployment and uses the original .WIM from the source media ( NEVER DO THIS always create a reference image). Change the value from FALSE to TRUE.
The next step is to change the “apply operating system” and change the destination to logical driver letter stored in a variable to OSDisk.

Deployment, MDT, Okategoriserade, SCCM2012, UEFI

Advanced format disk , and unpatched Images

I ran into this problem a few days ago when i was going to certify new hardware for Windows 7 Ent SP1 x64 and x86. The process went fine when installing the drivers on the machines that used Windows 7 Ent SP1 x64, but when i depoyed the x86 version to the same hardware and the SAME drivers but for x86 i ran into a problem…
Bild

So my first thought was that this has to be driver related and tried to remove drivers from the driver-package and then re-deploy the machine, but i still ran in to the same problem…So after some googling on the problem i found this Technet article describing the problem.http://support.microsoft.com/kb/982018/en-us

I checked the patches installed on the x86 version of the image and suprice suprice there where NONE, so basically this was an RTM release of the media, so what is the fastest way of adding this KB to the image? create a new one ofcourse! ( In MDT always ). So i double checked that the KB982018 was installed before i did the capture and then i deployed the machined again and…BAM!! it works!

The old way of solving this issue was to change the SATA settings in the bios to IDE, but on new hardware that has UEFI firware has this option removed… ( not all but most ). So to solve this issue you need to update the image you are deploying or create a ”Advanced Format Disk” step in the Task Sequence in CM when formating the disk, but if you dont have the KB in the img it´s time anyway to create a new ref img ! 🙂

Happy Deployment!

Okategoriserade

Aero, resolution and Windows 7

Hello my first bloggpost!
I just thought i would send out this tip regarding Windows 7 deployment and getting the right resolution and enabling the Aero interface for each computer in the deployment solution.

The problem
Some drivers in MDT and in CM does not enable the Aero interface by themselves and thus users can experience that Windows looks different, and I have gotten this question when I am out at customers a lot of times “why does not aero enable by itself, when integrating MDT in the task sequence?” well here is an easy solution how to solve it! And I hope some of you out there will have use of it .

Adjusting the resolution in customsettings.ini
To get the customsettings.ini auto-adjust the resolution for all certified hardware in the deployment environment simply add these lines in the file under the [Default] section. This enables auto-detection.

BitsPerPel=32
VRefresh=60
XResolution=1
YResolution=1
Enable Aero interface in the Task Sequence.
This is just two easy steps that we can use to enable this action in the Task Sequence. Add them under the ,or after “State Restore” step, like this. This will enable the Aero Interface on all models we now deploy out, and we will get rid of the problem of resolution customization for each model in the customsetting.ini

Happy deployment!

Best Regards, Johan

C:\Windows\system32\winsat.exe d3d
C:\Windows\system32\winsat.exe dwm