qballgeek

I figured it out. Setup Windows and ConfigMgr task copied the CCM package down to C:\_SMSTaskSequence AND creates a file called c:\windows\setup\scripts\setupcomplete.cmd. This file is supposed to run c:\windows\system32\osdsetuphook.exe /execute setupcomplete.cmd is run automatically during windows setup just before the OS gets to the login window. The osdsetuphook.exe is whats needed to have the CCM client install in a windows session. The image i'm using is a thick image with the Altiris DAgent installed. Altiris DAgent deleted the setupcomplete.cmd file every time the Altiris services startup on the computer. This is also near the beginning of windows setup, making the file not available when its supposed to be executed. My work around has been to run osdsetuphook from the unattand.xml answer file in the OOBE pass. Its works fine now.

No other log file. The only SCCM folder I can see is this C:\_SMSTaskSequence folder. If I look at a "Setup Windows and ConfigMgr" that ran successfully it shows a section called "OSDSetupHook.exe". None of that section is in this failed TS. The CCM package has been copied to the C:\_SMSTaskSequence successfully and I can watch the files being copied in the WinPE GUI. Its rights after the files are copied that it fails. And the CCM setup never does start. I've look for it in task manager and left a computer over the weekend to see if it would magically continue the TS.

I'm running an OSD TS and it fails to "install the CM Client". The part of the "Setup Windows and ConfigMgr" that copies the CCM files to C:\_SMSTaskSequence works but the next part, OSDSetupHook.exe never starts. Attached is the smsts.log file. This is a captured Win7 32 bit image. The same TS will work using a simple windows 7 install.wim file. I have been banging on this now for 3 weeks. smsts.log