none
OSD PXE boot - "windows is starting up" RRS feed

  • Question

  • This is really annoying. I was testing OSD over and over on a machine applying different software installation settings. Now it just stopped working. PE pops up after loading the boot image, sets the network settings and the says windows is starting up. And the previous image loads. Nothing has changed. The TS I was using was a copy of the original which had no Software Installation applied. I've reverted back to the original and same results.

    I saw a similar thread about the correct drivers missing from the boot image, but it's the same PC, same drivers, same everything. I've refreshed the collection, cleared previous PXE (which is always populated after an attempt so I know the TS is applied to the correct PC), rebooted servers, new Ad and new TS, even tried a different PXE server. It's just that the TS won't continue. Why????????? I'm currently updating all the DPs with boot images, drivers, etc. but I'm not counting on that really helping. And theAd status only updates when I make adjustments to the ad like re-running it.

    Friday, July 23, 2010 4:21 PM

Answers

  • I created a new TS identical to the previous that did work then stopped working... and have kicked if off a few times and it seems to be working now leaving me with just a big giant question mark. SCCM is whacked.
    • Marked as answer by jjstok Friday, July 23, 2010 6:18 PM
    Friday, July 23, 2010 6:18 PM

All replies

  • press f8 when windows PE starts and do ipconfig, do you have an ip ? if not winpe will reboot without an error. If you do have an ip then you are probably missing a vital package, please read your smsts.log file to find out the failure and post it here

     



    My step by step SCCM Guides
    I'm on Twitter > ncbrady
    Friday, July 23, 2010 4:25 PM
    Moderator
  • It is pulling an IP address. I've been asked for the SMSTS.log before in past threads. It stopped updating in March... The service was stopped... I changed it from manual to auto started it and it stopped and went back to manual. Here is what happend.

    Anyhow, these logs concern you? They don't look inspiring to me.

    7/23/2010 12:00:31 PM Successfully intialized Logging for TS Manager.
    7/23/2010 12:00:31 PM Commandline: "C:\Program Files\SMS_CCM\TSManager.exe" /service
    7/23/2010 12:00:31 PM Successfully registered Task Sequencing COM Interface.
    7/23/2010 12:00:31 PM Executing as a service
    7/23/2010 12:00:31 PM Started ServiceMain
    7/23/2010 12:00:31 PM Failed to restore logs from cache. Execution history may be lost.
    7/23/2010 12:00:31 PM Task Sequence Manager executing as service main thread
    7/23/2010 12:00:31 PM Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created
    7/23/2010 12:00:31 PM Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created
    7/23/2010 12:00:31 PM Failed to locate the local data path. The files needed to resume the task sequence are missing.  This could be because the task sequence finished while in Windows PE.  Please check the largest available partition for SMSTSLog\smsts.log file for more information.
    The system cannot find the file specified. (Error: 80070002; Source: Windows)
    7/23/2010 12:00:31 PM Task Sequence Manager could not initialize Task Sequence Environment. code 80070002
    7/23/2010 12:00:31 PM Task sequence execution failed with error code 80070002
    7/23/2010 12:00:31 PM Cleaning Up. Removing Authenticator
    7/23/2010 12:00:31 PM Successfully unregistered Task Sequencing Environment COM Interface.
    7/23/2010 12:00:31 PM Executing command line: C:\Program.exe Files\SMS_CCM\TsProgressUI.exe /Unregister
    7/23/2010 12:00:31 PM CreateProcess failed. Code(0x80070002)
    7/23/2010 12:00:31 PM Command line execution failed (80070002)
    7/23/2010 12:00:31 PM Getting active request access handle
    7/23/2010 12:00:31 PM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/23/2010 12:00:31 PM Error - could not get package and program IDs. code 80070002
    7/23/2010 12:00:31 PM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/23/2010 12:00:31 PM Start to cleanup TS policy
    7/23/2010 12:00:33 PM End TS policy cleanup
    7/23/2010 12:00:33 PM Error executing Task Sequence Manager service. Code 0x80070002
    7/23/2010 12:00:33 PM Sending error status message
    7/23/2010 12:00:33 PM MP name must be set in an environment variable
    7/23/2010 12:00:33 PM Non fatal error sending status message. Code 0x80004005
    7/23/2010 12:00:33 PM Successfully finalized logs to SMS client log directory from C:\Program Files\SMS_CCM\Logs
    7/23/2010 12:00:33 PM Resuming SMS Components
    7/23/2010 12:00:33 PM Waiting for CcmExec service to be fully operational
    7/23/2010 12:00:33 PM CcmExec service is up and fully operational
    7/23/2010 12:00:33 PM Getting SoftwareDistribution pause cookie
    7/23/2010 12:00:33 PM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/23/2010 12:00:33 PM Error - could not get pause cookie for SoftwareDistribution. code 80070002
    7/23/2010 12:00:33 PM Getting SoftwareUpdates pause cookie
    7/23/2010 12:00:33 PM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/23/2010 12:00:33 PM Error - could not get pause cookie for SoftwareUpdates. code 80070002
    7/23/2010 12:00:33 PM Getting System Health Agent pause cookie
    7/23/2010 12:00:33 PM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/23/2010 12:00:33 PM Error - could not get pause cookie for System Health Agent. code 80070002
    7/23/2010 12:00:33 PM Getting active request access handle
    7/23/2010 12:00:33 PM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/23/2010 12:00:33 PM Error - could not get asccess handle for the active request. code 80070002
    7/23/2010 12:00:33 PM IIDFromString() failed.
    7/23/2010 12:00:33 PM Task Sequence Manager could not release active TS request. code 80004005
    7/23/2010 12:00:33 PM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/23/2010 12:00:33 PM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/23/2010 12:00:33 PM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/23/2010 12:00:33 PM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/23/2010 12:00:33 PM Stopping Task Sequence Manager service

    Friday, July 23, 2010 5:11 PM
  • I noted in the previous post (then removed it) that this was working after I changed the boot driver. I think I did that and rebooted the PC the same time I started the TS service. Now it does not work again...
    Friday, July 23, 2010 5:45 PM
  • I forgot to check the log on the PXE server I had been using primarily.

     

    7/22/2010 11:16:57 AM Successfully intialized Logging for TS Manager.
    7/22/2010 11:16:57 AM Commandline: C:\WINDOWS\system32\CCM\TSManager.exe /service
    7/22/2010 11:16:57 AM Successfully registered Task Sequencing COM Interface.
    7/22/2010 11:16:57 AM Executing as a service
    7/22/2010 11:16:57 AM Started ServiceMain
    7/22/2010 11:16:57 AM Failed to restore logs from cache. Execution history may be lost.
    7/22/2010 11:16:57 AM Task Sequence Manager executing as service main thread
    7/22/2010 11:16:57 AM Environment scope "Global\{51A016B6-F0DE-4752-B97C-54E6F386A912}" successfully created
    7/22/2010 11:16:57 AM Environment scope "Global\{BA3A3900-CA6D-4ac1-8C28-5073AFC22B03}" successfully created
    7/22/2010 11:16:57 AM Failed to locate the local data path. The files needed to resume the task sequence are missing.  This could be because the task sequence finished while in Windows PE.  Please check the largest available partition for SMSTSLog\smsts.log file for more information.
    The system cannot find the file specified. (Error: 80070002; Source: Windows)
    7/22/2010 11:16:57 AM Task Sequence Manager could not initialize Task Sequence Environment. code 80070002
    7/22/2010 11:16:57 AM Task sequence execution failed with error code 80070002
    7/22/2010 11:16:57 AM Cleaning Up. Removing Authenticator
    7/22/2010 11:16:57 AM Successfully unregistered Task Sequencing Environment COM Interface.
    7/22/2010 11:16:57 AM Executing command line: "C:\WINDOWS\system32\CCM\TsProgressUI.exe" /Unregister
    7/22/2010 11:16:57 AM ==========[ TsProgressUI started in process 5636 ]==========
    7/22/2010 11:16:57 AM Unregistering COM classes
    7/22/2010 11:16:57 AM Shutdown complete.
    7/22/2010 11:16:57 AM Process completed with exit code 0
    7/22/2010 11:16:57 AM Successfully unregistered TS Progress UI.
    7/22/2010 11:16:57 AM Getting active request access handle
    7/22/2010 11:16:57 AM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/22/2010 11:16:57 AM Error - could not get package and program IDs. code 80070002
    7/22/2010 11:16:57 AM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/22/2010 11:16:57 AM Start to cleanup TS policy
    7/22/2010 11:16:57 AM End TS policy cleanup
    7/22/2010 11:16:57 AM Error executing Task Sequence Manager service. Code 0x80070002
    7/22/2010 11:16:57 AM Sending error status message
    7/22/2010 11:16:57 AM MP name must be set in an environment variable
    7/22/2010 11:16:57 AM Non fatal error sending status message. Code 0x80004005
    7/22/2010 11:16:57 AM Successfully finalized logs to SMS client log directory from C:\WINDOWS\system32\CCM\Logs
    7/22/2010 11:16:57 AM Resuming SMS Components
    7/22/2010 11:16:57 AM Waiting for CcmExec service to be fully operational
    7/22/2010 11:16:57 AM CcmExec service is up and fully operational
    7/22/2010 11:16:57 AM Getting SoftwareDistribution pause cookie
    7/22/2010 11:16:57 AM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/22/2010 11:16:57 AM Error - could not get pause cookie for SoftwareDistribution. code 80070002
    7/22/2010 11:16:57 AM Getting SoftwareUpdates pause cookie
    7/22/2010 11:16:57 AM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/22/2010 11:16:57 AM Error - could not get pause cookie for SoftwareUpdates. code 80070002
    7/22/2010 11:16:57 AM Getting System Health Agent pause cookie
    7/22/2010 11:16:57 AM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/22/2010 11:16:57 AM Error - could not get pause cookie for System Health Agent. code 80070002
    7/22/2010 11:16:57 AM Getting active request access handle
    7/22/2010 11:16:57 AM Error opening HKEY_LOCAL_MACHINE\Software\Microsoft\SMS\Task Sequence. code 80070002
    7/22/2010 11:16:57 AM Error - could not get asccess handle for the active request. code 80070002
    7/22/2010 11:16:57 AM IIDFromString() failed.
    7/22/2010 11:16:57 AM Task Sequence Manager could not release active TS request. code 80004005
    7/22/2010 11:16:57 AM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/22/2010 11:16:57 AM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/22/2010 11:16:57 AM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/22/2010 11:16:57 AM Failed to open the task sequence key HKLM\Software\Microsoft\SMS\Task Sequence. Error code 0x80070002
    7/22/2010 11:16:57 AM Stopping Task Sequence Manager service

    Friday, July 23, 2010 6:00 PM
  • I created a new TS identical to the previous that did work then stopped working... and have kicked if off a few times and it seems to be working now leaving me with just a big giant question mark. SCCM is whacked.
    • Marked as answer by jjstok Friday, July 23, 2010 6:18 PM
    Friday, July 23, 2010 6:18 PM