Hi Guys,

On 6th Feb we upgraded SCCM 2012 to SP1. Since then I have not been able to complete a deployment of W7 and its frustrating the hell out of me.

The logs I have looked at point to a bug in client.msi but not sure if thats me reading too much in to it.

Windows 7 x86 enterprise is built and captured using a new task sequence from Install.wim (This works fine, although we have to use a very basic bare metal machine [HP DC7600], due to our vsphere infrastructure not working with PE 4.0)

The deployment task sequence is also new (Not migrated from pre SP1, or from MDT) and uses the .WIM file captured in the build and capture sequence. (This I know installs to D: instead of C:, but using OSDPreserveDriveLetter set to false stops this from happening).

I have created new boot media and made a bootable USB memory stick, and boot from it.

During the task sequence,

My custom HTA file loads properly, asking for the Image details and the machine name, the process then continues, partitions the HDD (500MB for bitlocker, 100GB for OS, rest of the drive empty and hidden), formats and installs to C:, with the DVD rom drive allocated to D: and the USB boot pen is E: with ram disk X:

All my config settings are collected, the drivers are installed, customisations copied over to the C: drive

The Setup Windows and ConfirMgr task entry fails every time. Checking in c:\windows\ccmsetup\ there is a folder named LastError and in that is client.msi.log

Loading this into CMtrace shows that at some point the MSI changes the SystemFolder variable from C:\Windows\System32 to D:\Windows\System32 then craps out with a Disk Full: Out Of Disk Space -- Volume D:

Parts of the client.log with the error;

PROPERTY CHANGE: Modifying SystemFolder.12C909B6_5F69_4C4D_8EC3_C225C1607933 property. Its current value is 'C:\WINDOWS\system32\'. Its new value: 'D:\WINDOWS\system32'.
PROPERTY CHANGE: Modifying SystemFolder.A6940213_CD40_4753_8BA2_E803376DECC3 property. Its current value is 'C:\WINDOWS\system32\'. Its new value: 'D:\WINDOWS\system32'.
PROPERTY CHANGE: Modifying SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61 property. Its current value is "C:\WINDOWS\system32\'. Its new value: 'D:\WINDOWS\system32'.
PROPERTY CHANGE: Adding PerfDir.F65FD590_5BEA_48BE_8408_26F7244E8B61 property. Its value is "C:\WINDOWS\CCM\Perf'.
PROPERTY CHANGE: Adding Logs.43F063D4_4A7B_4402_BA1E_93454819EF9E property. Its value is 'C:\WINDOWS\CCM\Logs'.
PROPERTY CHANGE: Modifying SystemFolder.8AE6A59B_5597_4D75_9BFD_7F566BF56500 property. Its current value is 'C:\WINDOWS\system32\'. Its new value: 'D:\WINDOWS\system32'.
PROPERTY CHANGE: Adding RemCtrl.98C5B086_7EB0_422A_B0A8_674010F525CD property. Its value is 'C:\WINDOWS\CCM\RemCtrl'.
PROPERTY CHANGE: Adding Res1033.754ED406_3093_4B9E_BD1B_3B4F9EEF31BA property. Its value is 'C:\WINDOWS\CCM\1033'.
PROPERTY CHANGE: Adding Res1033.0EACD2EE_412B_4985_9727_96BC217AABD8 property. Its value is 'C:\WINDOWS\CCM\1033'.
PROPERTY CHANGE: Adding Res1033.6D67DFA7_9FBD_4680_8316_A664B7446743 property. Its value is 'C:\WINDOWS\CCM\1033'.
PROPERTY CHANGE: Adding Res1033.3D94DDFA_E8E4_46D9_AB9C_B63F80D2077D property. Its value is 'C:\WINDOWS\CCM\1033'.
PROPERTY CHANGE: Adding Res1033.ED41C92B_FF46_43B2_8535_65F491146D68 property. Its value is 'C:\WINDOWS\CCM\1033'.

Then further down the log...

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.

Disk full: Out of disk space -- Volume: 'D:'; required space: 903 KB; available space: 0 KB.  Free some disk space and retry.
Action ended 11:06:22: InstallValidate. Return value 3.
Action ended 11:06:22: INSTALL. Return value 3.

If I run the same sequence on a machine without a DVD drive the whole task sequence completes, but there are 4 files written to the USB stick under Windows\System32 (The USB Stick was designated D: during deployment)

This looks like a bug to me? - The client.msi looks like it assumes we will be installing to D: and ignores the OSDPreserveDriveLetter variable!

Any ideas on why client.msi wants to install 4 files to D: and not C: (When all the files above and below these 4 in the log are copied to C:\Windows\System32)???

Been driving me mad for the last 4 working days - Any feedback welcome!

Cheers

Mike.

• Edited by MikeHalliday Wednesday, April 10, 2013 8:04 AM

Did you ever get a Fix on this?  I am having exactly the same issues.

Works on machines without a D:\ (CDRom)  but curious if you managed to get around this issue (apart from unplugging the CDRom)

My thoughts are currently to see if I can Disable the CDRom.  maybe using Subst so i can point D:\ to C:\

regards