Jump to content


hotdog453

Established Members
  • Posts

    1
  • Joined

  • Last visited

hotdog453's Achievements

Newbie

Newbie (1/14)

0

Reputation

  1. Howdy all. Surfed the forum a lot, but never posted So, here's what we got. SCCM 2007 SP2. Windows 7 x86 OSD/Task Sequence. Works fine in bootable media (no PXE boot). Trying to deploy the exact same task sequence via Standalone USB. The system crashes out directly after failing the ConfigMGR setup and processing. Please view log for the entire thing. The errors standing out are, obviously: The client GUID must be set in an environment variable OSDSetupHook 10/24/2012 5:23:23 PM 2616 (0x0A38) and then the resultant: Failed to install SMS Client (0x80004005) OSDSetupHook 10/24/2012 5:23:24 PM 2616 (0x0A38) I'm really at a loss as to what the issue is. I've stripped the task sequence, re-made it from scratch, used multiple versions of the CCMSetup package (for the bootable media sequence, we're using the script packages to blend together the hotfixes; the normal, bare bones install does the same thing, though). Another thing of note, and maybe someone could explain it to me: Executing command line: "C:\_SMSTaskSequence\OSD\OIS001BC\ccmsetup.exe" /useronly /config:MobileClient.TCF /status:660 OSDSetupHook 10/24/2012 5:21:18 PM 2616 (0x0A38) Where is it deriving the /config:MobileClient.TCF from? This file does not exist anywhere on the USB boot key, but noticed it obviously fails with an exit code "1". This same process happens on the bootable media side, but does not fail. Please let me know if any other logs would be of use. Thanks in advance for any information. smsts.log
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.