OSD Deployment fails at Client Upgrade

[MikeHalliday]

Hi Guys,

 

I am having big problems deploying W7 onto any hardware since SP1 update!

 

I have rebuilt the Build and Capture sequence and sucessfully made a new .wim file to use i the deployment.

 

Deployment proceeds properly until the Set up Windows and Configmgr task.

 

client.msi.log attached.

 

In the deployment task I have set OSDPreserveDriveLetter to False and the image is installed on E: yet in the client.msi.log file it shows some lines that states;

 

MSI (s) (6C:D0) [11:06:22:073]: PROPERTY CHANGE: Modifying SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933 property. Its current value is 'E:\WINDOWS\system32\'. Its new value: 'D:\WINDOWS\system32'.

 

Then I get

 

[11:06:22] WARNING: Cache directory from WMI: D:\WINDOWS\ccmcache does not exists. Would re-calculate the cache settings.

Then

 

MSI (s) (6C:D0) [11:06:22:946]: Product: Configuration Manager Client -- Disk full: Out of disk space -- Volume: 'D:'; required space: 903 KB; available space: 0 KB. Free some disk space and retry.

 

D: drive is the DVD Writer so cant be written to!!! - I assume that if it was pointing to E: all would be good?

 

The package line for Client Upgrade using CCMSetup in the task sequence is as follows;

 

ccmsetup.exe /noservice CCMINSTALLDIR=%Windir%\System32\CCM SMSSITECODE=AUTO

 

I've been trying to find an answer for the failed deployment for the last 3 days, without success.

 

What's wrong, anyone got any ideas??? - The task sequence worked fine before SP1 update. Since the SP1 update I have hit lots of problems (Just like everyone else using it)

 

 

Cheers

 

MIke.

 

client.msi.zip

[MikeHalliday]

Ok, So it looks like I may have solved this.

 

My deployment task sequence partitions the main disc as a 100gb partition and a 500mb partition. It assigns the 100GB partition C: and the 500mb partition as D: It then installs the captured .WIM file to C: drive, which is fine. My client.msi now completes the install, but puts 4 files on D:\Windows\System32\ folder (CCMCore.DLL, CCMPERF.DLL, FRAMEWORKPERF.DLL and ISMIF32.DLL). The D: drive was supposed to be used for BitLocker stuff in the future (And was going to be hidden partition, but I thought I would keep it visible to see what happens - Next step is to build with a hidden partition and see if the client fails again). - This matches up with the client.msi.log I uploaded trying to install to D: drive, via the SystemFolder variable!

 

Is this a bug in Client.MSI? Where it is assuming that OSDPreserveDriveLetter is not set to false and the OS is being deployed to D: ??? - Can anybody try this in a VM and see if it does the same thing? (Reference image created with C: as main disc and D: as cd drive). I would try this in a VM, but our VM infrastructure is only v4.1 and I am waiting for it to be upgraded to 5.1 vSphere (but that could take weeks)

 

(SCCM build and capture using install.wim, C: 100% partition, D: cd drive. Deploy task is a standard SCCM task pointing to the captured .WIM file) - All my pre sp1 customisations have been left out of this new task just to be on the safe side.

 

 

Thanks

 

Mike.

[MikeHalliday]

So my last deployment had the 500mb partition hidden instead of primary. This forced the dvd drive to be e:. client.msi still fell over due to D: existing but being hidden and not writable! (Out of disk space on D:)

 

Not sure how to proceed now!

[smithse79]

Did you ever figure this out? I am running into this exact same brick wall...