Sign in
 
HomeLibraryWikiLearnGalleryDownloadsSupportForumsBlogs
Resources for IT Professionals >
> 
> 
> 
Windows deployment service stops at command prompt- W2K8 R2 IBM HS 22

Answered Windows deployment service stops at command prompt- W2K8 R2 IBM HS 22

  • Wednesday, February 06, 2013 4:51 PM
     
     
    Sign In to Vote
    0

    hi,

    I'm using windows deployment workbench, and when dropping Win2K8 R2 on an ibm hs22 i can get to the Postinstall section of the task sequence, but when it gets to the end of that section it's supposed to "Restart computer", but instead it just shows a command prompt window.  if i type exit in that window, the machine restarts and finishes the deployment without an error.  I tried adding another "Run Command Line" step to either exit or taskkill /IM cmd.exe, but exit did nothing and taskkill is not available.

    Any idea why the machine fails the reboot?  any idea how to fix or work around this?

     

All Replies

  • Wednesday, February 06, 2013 11:19 PM
     
     
    Sign In to Vote
    0
    it just stops here.  if i type exit or close the cmd prompt then it will reboot and complete installation successfully.  any help?
     
  • Thursday, February 07, 2013 3:22 PM
     
     
    Sign In to Vote
    0
    is there a specific log i can look at?  does anyone have any advice on this?
     
  • Thursday, February 07, 2013 4:27 PM
     
     
    Sign In to Vote
    0

    There are a bunch of logs... take a look at these articles to find them:
     - http://blogs.technet.com/b/askcore/archive/2012/05/08/mdt-2010-amp-2012-my-deployment-failed-what-and-where-are-logs-i-should-review.aspx
         - http://blogs.technet.com/b/mniehaus/archive/2012/03/09/mdt-2012-new-feature-monitoring.aspx (MDT 2012 Feature: Monitoring Service)

    You could also set SLShareDynamicLogging in your CustomSettings.ini to a network path, but understand that doing so should never be done on a Production share because it actively logs everything in real-time to the share, so can use a LOT of bandwidth and slow down your deployment.

    David Coulter | http://DCtheGeek.blogspot.com | @DCtheGeek

     
  • Friday, February 15, 2013 7:33 PM
     
      Has Code
    Sign In to Vote
    0

    i looked through all the logs on the pxe client and only found this one error in the smsts.log.  i'm not sure it's an issue though.  it fails to create _SMSTaskSequence on a D: drive and then creates it later on the C:

    Each log that i looked at indicated that the restart computer command completed successfully.  so the machine should reboot, but it doesn't.  any further help?

    thanks.

    Clear local default environment	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
User specified local data drive D:	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
D:\_SMSTaskSequence does not exist	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
Creating directory D:\_SMSTaskSequence	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
uRet == ERROR_ALREADY_EXISTS, HRESULT=80070003 (e:\nts_sms_fre\sms\framework\tscore\utils.cpp,916)	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
Failed to create D:\_SMSTaskSequence (3)	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
Failed to create user-specified local data path D:\_SMSTaskSequence. Error 0x80070003	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
Volume C:\ has 71376769024 bytes of free space	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
Volume V:\ has 492572672 bytes of free space	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
Volume X:\ is not a fixed hard drive	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
Volume Z:\ is not a fixed hard drive	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
TSM root drive = C:\	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
C:\_SMSTaskSequence does not exist	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
Creating directory C:\_SMSTaskSequence	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)
Updated security on object C:\_SMSTaskSequence.	TSManager	2/15/2013 6:13:48 PM	1752 (0x06D8)

     
  • Friday, February 15, 2013 9:03 PM
     
     
    Sign In to Vote
    0

    Are you booting with a CD/DVD?

    You need to remove the disk after first boot. If you leave it in this can happen.

    /Andrew

    Blog: http://scriptimus.wordpress.com


     
  • Wednesday, February 20, 2013 1:55 PM
     
     Answered
    Sign In to Vote
    0

    It's a known issue with IBM hardware using IMM. The driver "netimm.inf" makes MDT crash and go into debug mode which is why you get the command window. The only workaround I know of is to remove netimm.inf (or rename it) from your boot image. This gets tedious after a while, a better workaround would be most appreciated!

    • Marked As Answer by hA9RApa Saturday, February 23, 2013 7:32 PM
    •  
     
  • Saturday, February 23, 2013 7:39 PM
     
     
    Sign In to Vote
    0
    i marked the above as the answer bc it's correct.  more info here:  http://social.technet.microsoft.com/Forums/en/mdt/thread/f36c4fe7-fb2e-4f03-9773-868282238faa

    note that when we were sifting through logs we found the winpe.log (very near name if not the actual name) file on the client.  it was in the root folder when the command prompt would pop up.  that log told us that a driver failed to load.