none
Standalone OSD hanging during "Setup Windows and Configuration" phase

    Question

  • We've used standalone OSD media for quite some time with config manager 2007.  Never had an issue with it finishing the task sequence and getting to the windows login screen.   With SCCM 2012 however, the standalone hangs around the time of the config manager client registration right after it installs.    It never finishes.  

    It finishes fine when installing it over the network.

    Looking at the logs, it stops around here.  Anyone have any advice?   Seems like some others have had this problem but not resolutions.

    SMSTS.LOG below

    Registering the task sequence with the execution manager in the newly installed operating system.
    Active request handle is empty, registering with new active request handle. This is expected if the TS was started from a media/PXE.
    [Saving the new active request handle for the task sequence:  {1A527333-79EB-48C0-8683-185967DBF33D}
    <![LOG[Failed to create instance for IMTCTokenHandler interface, hr=0x80070005]LOG
    G[Waiting for ccmexec process to start]LOG]
    Failed to create instance for IMTCTokenHandler interface, hr=0x8

    It does this every 5 minutes.  Fails to create instanance for IMTCTokenHandler.

    I also seen these in other logs:

    "failed to register task sequence" with the newly installed client

    And some others.. accidentally formatted the drive with other logs.  I'll add them soon.

    Thursday, February 28, 2013 9:48 PM

Answers

  • I can't see it helping at all if you have the old client installed.  I would start with a new image captured the new version of the client installed.  When the task sequence fails, get a command prompt open and look at the ccmsetup.log to see if the client is actually being installed without issue.

    Andy


    My Personal Blog: http://madluka.wordpress.com

    • Marked as answer by CSMatMan Monday, March 04, 2013 12:53 PM
    Friday, March 01, 2013 7:32 PM

All replies

  • Friday, March 01, 2013 5:02 PM
  • Definitely worth a shot.  I'll keep the thread posted.

    Thanks Luka

    Btw, from further testing, the standalone media will work if the network cable is plugged in and connected to the network.  If not, it stalls while/after config manager is installed during setup windows and configmgr phase.

    So this is definitely worth trying.

    • Edited by CSMatMan Friday, March 01, 2013 6:03 PM
    Friday, March 01, 2013 6:02 PM
  • While I am waiting for my media to be created and to test.. going to post some more log entries I see from other logs:

    It seems obvious to me it wants to find the mp and that might be why it stalls without a network cable.  But it shouldn't since it's standalone.

    [Failed in WinHttpSendRequest API,
    ] ERROR: URL=HTTP://mpserver.lan/SMS_FSP/.sms_fsp, Port=80, Options=224, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED]LO
    <![LOG[[CCMHTTP] ERROR: URL=HTTP://mpserver.lan/SMS_FSP/.sms_fsp, Port=80, Options=224, Code=12007, Text=ERROR_WINHTTP_NAME_NOT_RESOLVED]LOG]!><time="12:27:13.934+300" date="03-01-2013" component="FSPStateMessage" context="" type="1" thread="2224" file="ccmhttperror.cpp:297">
    <![LOG[Successfully sent location services HTTP failure message.]LOG]!><time="12:27:13.949+300" date="03-01-2013" component="FSPStateMessage" c

    <![LOG[Attempting to retrieve lookup MP(s) from DNS]LOG]!
    <![LOG[Attempting to retrieve default management points from DNS]LOG]!><time="12:
    <![LOG[Failed to retrieve DNS service record using _mssms_mp_cs1._tcp.mpserver.LAN lookup. DNS returned error 9852]LOG]!><time="12:27:13
    <![LOG[No lookup MP(s) from DNS]LOG]!><time="12:27:13.949+300" date="0
    <![LOG[Sending Fallback Status Point message, STATEID='608'.]LOG]!><time="12:27:
    <![LOG[Failed to send status 608 to the FSP (80072EE7)]LOG]!><time="12:27


    <![LOG[RegTask: Failed to refresh site code. Error: 0x8000ffff]LOG]!><time="12:47:13.888+300" date="0



    Friday, March 01, 2013 6:26 PM
  • Could it be this? > http://support.microsoft.com/kb/2716946

    Andy

    My Personal Blog: http://madluka.wordpress.com

    Luka,

    You're putting this right after the Setup Windows and Configuration Manager phase, correct?  and before the package/application installs.

    Thanks

    Friday, March 01, 2013 6:50 PM
  • Yeah it should be placed immediately following the Setup Windows and ConfigMgr step and definately before any package install steps.  Do remember of course that if you're machine is supposed to be joining the domain then there must be a network card attached for this to happen.

    My Personal Blog: http://madluka.wordpress.com

    Friday, March 01, 2013 7:17 PM
  • Thanks.  Unfortunately no go.   no domain join on this media.

    Only thing I can think is that I originally created the windows 7 wim file with the sccm 2007 capture.   Moved it over to 2012.  Maybe it has remnants of the old client install or something. 

    Friday, March 01, 2013 7:26 PM
  • I can't see it helping at all if you have the old client installed.  I would start with a new image captured the new version of the client installed.  When the task sequence fails, get a command prompt open and look at the ccmsetup.log to see if the client is actually being installed without issue.

    Andy


    My Personal Blog: http://madluka.wordpress.com

    • Marked as answer by CSMatMan Monday, March 04, 2013 12:53 PM
    Friday, March 01, 2013 7:32 PM
  • I updated my reference vm machine.   I uninstalled sccm 2007 client and then installed the sccm 2012 client.   I then captured and deployed the capture.   It then got past this phase without a hitch.


    • Edited by CSMatMan Monday, March 04, 2013 12:55 PM
    Monday, March 04, 2013 12:55 PM