Client installation fails during TS on VM

[Phred]

Hello all -

 

Here is a weird problem. After an OS update, I can no longer use my 32bit WIM to reimage my test VM. The same image and TS works fine on a physical machine. The OS installs fine. The TS fails when trying to install the SCCM client. I can run the SCCM client manually after the TS fails.

 

the ccmsetup.log file says:

---

MSI: There is not enough available disk space on C: to complete this operation. Installation requires at least 90MB free disk space. ccmsetup 5/25/2016 8:25:20 AM 3468 (0x0D8C)
---

Which is weird as I have a 40GB disk image assigned to the VM and after reimage I have 10GB free, so plenty of space.

 

That got me thinking that maybe it didn't boot off the C drive with the OS.

 

Looking deeper, at the beginning of ccmsetup.log it says:

---

Detected 919 MB free disk space on system drive. ccmsetup 5/25/2016 8:23:22 AM 3468 (0x0D8C)
---

Ok that is not good. So that got me looking into the smsts.log to see what is happening during the disk partitioning.

 

The smsts.log says:

---

Reading partition size info for partition 0 OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
Remaining size before partition: 42944186880 OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
size units: SIZE_MB OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
Set partition size: 367001600 OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
Remaining size after partition 0: 42577185280 OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
Set an environment variable for partitions 0-1 without drive letter OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
Reading partition size info for partition 1 OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
Remaining size before partition: 42577185280 OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
size units: SIZE_PERCENT OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
100% size specified. OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
Remaining size after partition 1: 0 OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)
Set an environment variable for partitions 0-2 with drive letter OSDDiskPart 5/25/2016 7:43:15 AM 1116 (0x045C)

Volume C:\ has 42485960704 bytes of free space TSManager 5/25/2016 7:43:29 AM 1172 (0x0494)

 

The volume C:\ exists and is a local hard drive. ApplyOperatingSystem 5/25/2016 7:43:30 AM 1920 (0x0780)
The volume C:\ is using a valid file system. ApplyOperatingSystem 5/25/2016 7:43:30 AM 1920 (0x0780)
Windows target partition is 0-2, driver letter is C:\ ApplyOperatingSystem 5/25/2016 7:43:30 AM 1920 (0x0780)
---

So it looks like it did what I asked, create two partitions. The first is 350MB and the second takes up the remaining space. It doesn't assign a drive letter to the first partition and assigns C to the 2nd partition.

 

Then we know it works because the OS gets applied properly.

--

Applying image to C:\ ApplyOperatingSystem 5/25/2016 7:51:36 AM 1920 (0x0780)
Applying image 2 to volume C: ApplyOperatingSystem 5/25/2016 7:51:36 AM 1920 (0x0780)
Successfully applied image to C:\ ApplyOperatingSystem 5/25/2016 8:10:34 AM 1920 (0x0780)
--

What I can't figure out is why it doesn't install the client.

The Apply Windows Settings, Apply Network Settings, Apply Drivers all come back successful.

 

On to OSDSetupHook part of the log:

---

Executing C:\_SMSTaskSequence\OSD\SFU00003\ccmsetup.exe /useronly /source:C:\_SMSTaskSequence\OSD\SFU00003 /config:MobileClient.TCF /status:628 OSDSetupHook 5/25/2016 8:23:19 AM 3120 (0x0C30)
Command line for extension .exe is "%1" %* OSDSetupHook 5/25/2016 8:23:19 AM 3120 (0x0C30)
Set command line: "C:\_SMSTaskSequence\OSD\SFU00003\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\SFU00003 /config:MobileClient.TCF /status:628 OSDSetupHook 5/25/2016 8:23:19 AM 3120 (0x0C30)
Executing command line: "C:\_SMSTaskSequence\OSD\SFU00003\ccmsetup.exe" /useronly /source:C:\_SMSTaskSequence\OSD\SFU00003 /config:MobileClient.TCF /status:628 OSDSetupHook 5/25/2016 8:23:19 AM 3120 (0x0C30)
Process completed with exit code 6 OSDSetupHook 5/25/2016 8:27:21 AM 3120 (0x0C30)
FALSE, HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\installclient.cpp,1151) OSDSetupHook 5/25/2016 8:27:21 AM 3120 (0x0C30)
Client installation failed, code 6 OSDSetupHook 5/25/2016 8:27:21 AM 3120 (0x0C30)
---

This is where the error occurs. I'm guessing it is responding to the error from the ccmsetup.log failure.

 

Anybody have any ideas why it would work on physical but not virtual? I've created a new TS using the same wim. I don't have another WIM to test right now. But then why would a WIM cause this problem?

 

Thanks,

[YPCC]

the ccmsetup.log and clientmsi.log should give you detailed info on whats going on. Post them up and lets see

[Phred]

Here they are.

ccmsetup-1-part.log

smsts-1-part.log