Yet another OSD Failing to install the CCM Client

[biewz]

Hi Guys,

I Have been banging my head over this issue for about 4 days now, I have a whole SCCM setup going thanks to the fantastic guides provided by this site.

but now while tackling OSD I have run into an issue I can't seem to resolve.

In Short the Install Existing Operating System Task Sequence doesnt install the CCM client so nothing after the step runs.

The system reboots, joins domain and completes setup without installing updates or applications because there is no client.

 

(I am deploying Windows 7 x64 from an existing build, I sadly dont have the luxury of starting afresh with the reference image although I have made one to test with the ensure that the TS is working properly)

 

(SCCM 2012 SP1 CU2)

 

By the looks of smsts.log, it seems to try to install the client but there are no real error codes other than one repeated line which stands out as below:

:

Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook

 

I have done quite a bit of searching on it and followed a number of different problems people had where they saw that line but none seem to exactly apply to my case.

 

I have checked for unsigned drivers and tested the deployment with the BIOS set to emulate IDE mode to eliminate the Mass storage driver as some people had issues with these.

 

I previously also had Users and ProgramData on the D: drive and had to add command line tasks to create symbolic links from C: otherwise Dism spat the dummy and wouldnt install drivers. I originally used the sysprep option:

<FolderLocations>
<ProfilesDirectory>D:\Users</ProfilesDirectory>
<ProgramData>D:\ProgramData</ProgramData>
</FolderLocations>

So It seemed supported at the time, but Dism ignores the registry setting and variables pointing to is and assumes its all on C:

(Although I can report no major issues those folders in that location for 3 years on over 1000 PC's) (Microsoft DRM wont work with ProgramData moved, though it can easily be fixed by using mklink /j to link C:\ProgramData to it's new location.)

 

to eliminate this as a possible issue though, I kept everything on the C: drive, the D: drive is just an empty partition.

 

however its probably worth mentioning that the _SMSTaskSequence folder is created on the D: drive. (seems to pick it automatically)

 

This is the last part of the smsts.log where the issue occurs:

 

Downloaded file from http://DP.fqdn.com,au:80/SMS_DP_SMSPKG$/P010003D/sccm?/x64/windowsupdateagent30-x64.exe to E:\_SMSTaskSequence\Packages\P010003D\x64/windowsupdateagent30-x64.exe OSDSetupHook 30/04/2014 15:59:22 1332 (0x0534)
Download done setting progress bar to 100 OSDSetupHook 30/04/2014 15:59:22 1332 (0x0534)
VerifyContentHash: Hash algorithm is 32780 OSDSetupHook 30/04/2014 15:59:22 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:22 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:22 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:22 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:22 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:23 1332 (0x0534)
e:\_smstasksequence\packages\p010003d\i386 is a directory. Setting directory security OSDSetupHook 30/04/2014 15:59:23 1332 (0x0534)
e:\_smstasksequence\packages\p010003d\x64 is a directory. Setting directory security OSDSetupHook 30/04/2014 15:59:23 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:23 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:24 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:25 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:26 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:26 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:26 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:26 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:26 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:26 1332 (0x0534)
Failed to open Software\Microsoft\Sms\Mobile Client\Software Distribution registry key. The client should not get checked for RWH OpLock Type OSDSetupHook 30/04/2014 15:59:26 1332 (0x0534)
Content successfully downloaded at E:\_SMSTaskSequence\Packages\P010003D OSDSetupHook 30/04/2014 15:59:26 1332 (0x0534)
Copying SMS client package source from "E:\_SMSTaskSequence\Packages\P010003D" to "E:\_SMSTaskSequence\OSD\P010003D". OSDSetupHook 30/04/2014 15:59:26 1332 (0x0534)
Locating architecture-specific OSDGina.dll OSDSetupHook 30/04/2014 15:59:27 1332 (0x0534)
Successfully copied file OSDSETUPHOOK.EXE to D:\Windows\SYSTEM32 OSDSetupHook 30/04/2014 15:59:27 1332 (0x0534)
Successfully copied file TSProgressUI.exe to D:\Windows\SYSTEM32\_SMSOSDSetup OSDSetupHook 30/04/2014 15:59:27 1332 (0x0534)
Successfully copied file tsres.dll to D:\Windows\SYSTEM32\_SMSOSDSetup\1033 OSDSetupHook 30/04/2014 15:59:27 1332 (0x0534)
Saving desktop wallpaper information. OSDSetupHook 30/04/2014 15:59:27 1332 (0x0534)
Entering ReleaseSource() for E:\_SMSTaskSequence\Packages\P010003D OSDSetupHook 30/04/2014 15:59:27 1332 (0x0534)
reference count 1 for the source E:\_SMSTaskSequence\Packages\P010003D before releasing OSDSetupHook 30/04/2014 15:59:27 1332 (0x0534)
Released the resolved source E:\_SMSTaskSequence\Packages\P010003D OSDSetupHook 30/04/2014 15:59:27 1332 (0x0534)
Exiting ConfigureEx: 0x00000000 OSDSetupHook 30/04/2014 15:59:27 1332 (0x0534)
Process completed with exit code 0 OSDSetupWindows 30/04/2014 15:59:27 708 (0x02C4)
Installing hook to 'D:\Windows' OSDSetupWindows 30/04/2014 15:59:27 708 (0x02C4)
Command line for extension .EXE is "%1" %* OSDSetupWindows 30/04/2014 15:59:27 708 (0x02C4)
Set command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:D:\Windows" /version:6.1 OSDSetupWindows 30/04/2014 15:59:27 708 (0x02C4)
Executing command line: "X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:D:\Windows" /version:6.1 OSDSetupWindows 30/04/2014 15:59:27 708 (0x02C4)
Installing OSD setup hook OSDSetupHook 30/04/2014 15:59:27 1460 (0x05B4)
Setup hook install completed successfully OSDSetupHook 30/04/2014 15:59:27 1460 (0x05B4)
Process completed with exit code 0 OSDSetupWindows 30/04/2014 15:59:27 708 (0x02C4)
OfflineRegistry::Init("D:\Windows") OSDSetupWindows 30/04/2014 15:59:27 708 (0x02C4)
Loading offline registry hive "D:\Windows\system32\config\software" into HKLM\OfflineRegistry1 OSDSetupWindows 30/04/2014 15:59:27 708 (0x02C4)
Loading offline registry hive "D:\Windows\system32\config\system" into HKLM\OfflineRegistry2 OSDSetupWindows 30/04/2014 15:59:28 708 (0x02C4)
CurrentControlSet is mapped to ControlSet001 OSDSetupWindows 30/04/2014 15:59:28 708 (0x02C4)
SMS Client is not installed OSDSetupWindows 30/04/2014 15:59:28 708 (0x02C4)
Unloading offline SOFTWARE registry hive OSDSetupWindows 30/04/2014 15:59:28 708 (0x02C4)
Unloading offline SYSTEM registry hive OSDSetupWindows 30/04/2014 15:59:28 708 (0x02C4)
Exiting with code 0x00000000 OSDSetupWindows 30/04/2014 15:59:28 708 (0x02C4)
Process completed with exit code 0 TSManager 30/04/2014 15:59:28 1076 (0x0434)
!--------------------------------------------------------------------------------------------! TSManager 30/04/2014 15:59:28 1076 (0x0434)
Successfully completed the action (Setup Windows and ConfigMgr) with the exit win32 code 0 TSManager 30/04/2014 15:59:28 1076 (0x0434)
MP server http://sccmserver.fqdn.com.au. Ports 80,443. CRL=false. TSManager 30/04/2014 15:59:28 1076 (0x0434)
Setting authenticator TSManager 30/04/2014 15:59:28 1076 (0x0434)
Set authenticator in transport TSManager 30/04/2014 15:59:28 1076 (0x0434)
Sending StatusMessage TSManager 30/04/2014 15:59:28 1076 (0x0434)
Setting message signatures. TSManager 30/04/2014 15:59:28 1076 (0x0434)
Setting the authenticator. TSManager 30/04/2014 15:59:28 1076 (0x0434)
CLibSMSMessageWinHttpTransport::Send: URL: sccmserver.fqdn.com.au:80 CCM_POST /ccm_system/request TSManager 30/04/2014 15:59:28 1076 (0x0434)
Request was succesful. TSManager 30/04/2014 15:59:28 1076 (0x0434)
Set a global environment variable _SMSTSLastActionRetCode=0 TSManager 30/04/2014 15:59:28 1076 (0x0434)
Set a global environment variable _SMSTSLastActionSucceeded=true TSManager 30/04/2014 15:59:28 1076 (0x0434)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 30/04/2014 15:59:28 1076 (0x0434)
Clear local default environment TSManager 30/04/2014 15:59:28 1076 (0x0434)
The action (Setup Windows and ConfigMgr) requested a retry TSManager 30/04/2014 15:59:28 1076 (0x0434)
Reboot to local harddisk TSManager 30/04/2014 15:59:28 1076 (0x0434)
_OSDGinaIsConfigured variable set to TRUE TSManager 30/04/2014 15:59:28 1076 (0x0434)
_SMSTSServiceStartType variable set to TSManager 30/04/2014 15:59:28 1076 (0x0434)
Command line for extension .exe is "%1" %* TSManager 30/04/2014 15:59:28 1076 (0x0434)
Set command line: "bcdedit.exe" TSManager 30/04/2014 15:59:28 1076 (0x0434)
Executing command line: "bcdedit.exe" TSManager 30/04/2014 15:59:28 1076 (0x0434)
Process completed with exit code 0 TSManager 30/04/2014 15:59:29 1076 (0x0434)
Calling RebootSystem() TSManager 30/04/2014 15:59:29 1076 (0x0434)
OSD type of task sequence. ignore the service window setting TSManager 30/04/2014 15:59:29 1076 (0x0434)
Updated security on object C:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 30/04/2014 15:59:29 1076 (0x0434)
Updated security on object D:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 30/04/2014 15:59:29 1076 (0x0434)
Updated security on object E:\_SMSTSVolumeID.7159644d-f741-45d5-ab29-0ad8aa4771ca. TSManager 30/04/2014 15:59:29 1076 (0x0434)
Updated security on object E:\_SMSTaskSequence. TSManager 30/04/2014 15:59:29 1076 (0x0434)
Set a global environment variable _SMSTSNextInstructionPointer=20 TSManager 30/04/2014 15:59:29 1076 (0x0434)
Set a TS execution environment variable _SMSTSNextInstructionPointer=20 TSManager 30/04/2014 15:59:29 1076 (0x0434)
Set a global environment variable _SMSTSInstructionStackString=19 TSManager 30/04/2014 15:59:29 1076 (0x0434)
Set a TS execution environment variable _SMSTSInstructionStackString=19 TSManager 30/04/2014 15:59:29 1076 (0x0434)
Save the current environment block TSManager 30/04/2014 15:59:29 1076 (0x0434)
Expand a string: %_SMSTSMDataPath%\Logs TSManager 30/04/2014 15:59:29 1076 (0x0434)

 

To verify that the client install works as it is supposed to (along with the whole TS for that matter) I have created a blank reference image and substituted it into the existing TS and the client does install.

 

 

 

I hope what I am doing wrong may be obvious to someone, Although making a new image would fix this issue I would like to know what it could be in the current image that broke this.

 

Thanks in advance

[biewz]

I forgot to mention that before anyone suggests checking the ccmsetup.log, It's not on the deployed system at all, in fact the CCM folder is missing in C:\Windows\System32 and SysWOW64.

 

It would be good if someone can point me to some info on how the client is actually installed in OSD,

I understand that the files are copied in PE, but does the install occur to the offline image from PE, or does it have something to do with

"X:\sms\bin\x64\OSDSETUPHOOK.EXE" "/install:D:\Windows" /version:6.1 ?

 

I was hoping to find a setup string in the unattend.xml file in C:\Windows\Panther but thats clearly not the way it installs.

 

Cheers,

 

David Bielen