locked
MDT 2012 Sysprep and Installation Failure RRS feed

  • Question

  • A few days ago I tried to install a clean windows 7 installation with updates on a dell optiplex 3010,

    it gave a failure and after that I didn't think much of it anymore
    The next day i tried to install another 3010 and got the same error

    Windows could not parse or process the unattended answer file for pass [specialize]. The setting specified in the answer file cannot be applied. The error was detected while processing settings for component [Microsoft-Windows-Shell-Setup].

    Since I am fairly new to MDT I am clueless, I went to c:/windows/panther/unattendedgc and

    got this log.

    2013-11-28 05:22:44, Info                         [windeploy.exe] ------------------------------------------------
    2013-11-28 05:22:44, Info                         [windeploy.exe] WinDeploy.exe launched with command-line []...
    2013-11-28 05:22:44, Info                         [windeploy.exe] Setup has not completed, adding pending reboot.
    2013-11-28 05:22:44, Info                         [windeploy.exe] Found generalization state [0x4], setup.exe completion flag [False] --> launching setup.exe.
    2013-11-28 05:22:44, Info                         [windeploy.exe] Launching [C:\Windows\system32\oobe\setup.exe]...
    2013-11-28 05:24:13, Info                         [windeploy.exe] Process exited with exit code [0x0]
    2013-11-28 05:24:13, Info                         [windeploy.exe] Found completion flag [True], reboot requested flag [True] --> rebooting computer before proceeding with deployment...
    2013-11-28 05:24:13, Info                         [windeploy.exe] Making sure that SystemSetupInProgress is cleared.
    2013-11-28 05:24:13, Info                         [windeploy.exe] An immediate reboot or shutdown was requested/required... rebooting / shutting down computer
    2013-11-28 05:24:13, Info                         [windeploy.exe] Flushing registry to disk...
    2013-11-28 05:24:13, Info                         [windeploy.exe] Flush took 640 ms.
    2013-11-28 05:24:13, Info                         [windeploy.exe] WinDeploy.exe exiting with code [0x0]
    2013-11-28 05:25:18, Info                         [windeploy.exe] ------------------------------------------------
    2013-11-28 05:25:18, Info                         [windeploy.exe] WinDeploy.exe launched with command-line []...
    2013-11-28 05:25:18, Info                         [windeploy.exe] Making sure that SystemSetupInProgress is cleared.
    2013-11-28 05:25:18, Info                         [windeploy.exe] Found no unattend file.
    2013-11-28 05:25:18, Info                         [windeploy.exe] WinSAT assessment failed with error 80040154
    2013-11-28 05:25:18, Info                         [windeploy.exe] Launching [C:\Windows\system32\oobe\oobeldr.exe /system]...
    2013-11-28 05:25:18, Info                         [oobeldr.exe] OOBELdr.exe launched with command-line [/system]...
    2013-11-28 05:25:18, Info                         [oobeldr.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_SPECIALIZE_RESEAL_TO_OOBE] --> [IMAGE_STATE_UNDEPLOYABLE]
    2013-11-28 05:25:18, Info                         [oobeldr.exe] Parsing command line arguments...
    2013-11-28 05:25:18, Info                         [oobeldr.exe] Parsing the following command line: [/system]
    2013-11-28 05:25:18, Info                         [oobeldr.exe] Status for unattend pass [oobeSystem] = 0x0
    2013-11-28 05:25:18, Info                         [oobeldr.exe] Found no unattend file for oobeSystem pass; skipping pass.
    2013-11-28 05:25:18, Info                         [oobeldr.exe] No reboot has been requested for oobeSystem unattend.
    2013-11-28 05:25:18, Info                         [oobeldr.exe] Successfully ran oobeSystem pass.
    2013-11-28 05:25:18, Info                         [oobeldr.exe] Launching [C:\Windows\system32\oobe\msoobe.exe]...
    2013-11-28 05:25:18, Info                         [msoobe.exe] Starting service sppsvc
    2013-11-28 05:25:21, Info                         [msoobe.exe] Service sppsvc reports as running
    2013-11-28 05:25:21, Info                         [msoobe.exe] Successfully created first boot reg key
    2013-11-28 05:25:21, Info                         [msoobe.exe] Server, exiting...
    2013-11-28 05:25:21, Info                         [msoobe.exe] Running mandatory tasks
    2013-11-28 05:25:21, Info                         [msoobe.exe] Doing background work directly in MandatoryTasks; eType=1
    2013-11-28 05:25:21, Info                         [msoobe.exe] Successfully installed product key
    2013-11-28 05:25:21, Info                         [msoobe.exe] Starting service netprofm
    2013-11-28 05:25:22, Info                         [msoobe.exe] Service netprofm reports as running
    2013-11-28 05:25:22, Info                         [msoobe.exe] Successfully signalled event to start up services
    2013-11-28 05:25:22, Info                         [msoobe.exe] Doing background work directly in MandatoryTasks; eType=0
    2013-11-28 05:25:22, Info                         [msoobe.exe] Starting service Schedule
    2013-11-28 05:25:23, Info                         [msoobe.exe] Service Schedule is already running
    2013-11-28 05:25:23, Info                         [msoobe.exe] Successfully verified and committed UI language settings
    2013-11-28 05:25:30, Info                         [msoobe.exe] Successfully notified UI language change
    2013-11-28 05:25:30, Info                         [msoobe.exe] Successfully installed Windows Recovery Environment
    2013-11-28 05:25:31, Info                         [msoobe.exe] Successfully removed administrator profile
    2013-11-28 05:25:31, Info                         [msoobe.exe] Exiting mandatory tasks... [0x00000000]
    2013-11-28 05:25:31, Info                         [msoobe.exe] Cleaning up background work
    2013-11-28 05:25:31, Info                         [oobeldr.exe] OrchestrateUpdateImageState: Updating image state from [IMAGE_STATE_UNDEPLOYABLE] --> [IMAGE_STATE_COMPLETE]
    2013-11-28 05:25:32, Info                         [oobeldr.exe] OOBELdr.exe exiting with code [0x0]...
    2013-11-28 05:25:32, Info                         [windeploy.exe] Process exited with exit code [0x0]
    2013-11-28 05:25:32, Info       [0x090008] PANTHR CBlackboard::Open: C:\Windows\Panther\SetupInfo succeeded.
    2013-11-28 05:25:32, Info       [0x090009] PANTHR CBlackboard::Close: c:\windows\panther\setupinfo.
    2013-11-28 05:25:32, Info                         [windeploy.exe] WinDeploy.exe exiting with code [0x0]

    This is from a sysprep on a vm in vmware workstation. I am clueless what to do next..
    I've read a lot of threads but I can't find any solution.

    Can anybody help me with analogizing log files?
    and which other log files might be helpfull?

    regards

    hidde

    • Moved by Yolanda Zhu Saturday, January 11, 2014 9:09 AM MDT issue
    Thursday, January 9, 2014 11:28 AM

All replies

  • have you read this thread:

    http://social.technet.microsoft.com/Forums/windows/en-US/c241c9cf-6507-4126-8af3-5c7d1e00dd73/sysprep-unattend-answer-file-problem?forum=itprovistadeployment

    It suggests a couple of different possible causes...

    Good luck!

    Monday, January 13, 2014 8:35 PM
  • This can sometimes happen when you have OSDComputerName=%SerialNumber% in the CustomSettings.ini. Because you are deploying an image to VMware, VMw has SerialNumbers that are different in characters... To make a long story short, use the replace the following command in CustomSettings.ini:

    OSDComputerName=%SerialNumber%

    to 

    OSDComputerName=#RIGHT("%SerialNumber%",15)#

    15= the max number of characters allowed in a computername. This should help fix your issue. 


    • Edited by _JoeG Tuesday, January 14, 2014 12:43 AM Grammar
    • Proposed as answer by Martin van Bellen Wednesday, January 15, 2014 11:04 AM
    Tuesday, January 14, 2014 12:43 AM
  • Sorry for the very late reply, I resolved the issue but its a good thing to know the cause. Thank you!
    Wednesday, March 12, 2014 10:34 AM