SCCM 2012 OSD - unattended XML problem?

Hi,
I am having an issue with SCCM 2012 SP1 / MDT OSD task sequence. The issue is
with the Apply Operating system step. It applies the OS reboots and boots into
the new OS. We are trying to install Windows 2008 R2.
The first dialog I see is:
"Windows could not parse or process the unattende answer file for pass [specialize].
The settings epcified in the answer file cannot be applied. The
error was detected while processing for component [Microsoft-Windows-Shell-Setup]"
Then in the black background under the dialog".
"Setup is applying system settings"
-- So I click "OK" the computer reboots..
Then I get
"The computer restarted unexpectedly or encounted an
unexpected error. Windows Installation cannot proceeed. To install
Windows, click "OK" to restart the computer, and then restart the
installation.
The in the black background see:
"Setup is preparing your computer for first use"
If I click on "OK" here it reboots and presents the same dialog again - so it gets stuck and loops
around and does not progress.
Questions
1. So from the "Apply OS step" I can see you can see you can specify a specific "unattended.xml" file.
Is there a log file I can look at that can give me more specific detail on what the exact setting it does
not like in that XML file so I can correct it?
2. If I don't specicy anything how is that XML generated and where would its log file be? I assume the same
as question 1?
3. For question 2 - where can I find the unattended XML on the target OS.
4. Since I am not in PE anymore and F8 does not work is there anyway I can bring up a command prompt?
Thanks,
Ward.

1. You'll have to check the Windows setup logs files because at this point, that's what's running.
2. There is a default XML file generated/used.
3. You will only find the file on deployed systems and I think you can traditionally find it under the panther folder.
4. Actually, you can use F8 to launch a command-prompt in the target OS during the TS as long as you enabled it in the boot image. However, as mentioned, you are in Windows setup at this point (which is actually another instance of WinPE) and so F8 doesn't
work here. Shift-F10 should though.
Jason | http://blog.configmgrftw.com

Similar Messages

  • SCCM 2012 OSD Task Sequence - force Policy and SCEP update?

    Hi,
    How can I force a policy update to update machine policy and scep definitions at the end of
    SCCM 2012 OSD Task Sequence,
    Thanks,
    Ward.

    Hi,
    I normally use this solution from Chris Nackers to deploy the latest EP definitions during OSD and deploy a custom EP policy, it works great. The policy will be downloaded when the client is registered.
    Regards,
    Jörgen
    -- My System Center blog ccmexec.com -- Twitter
    @ccmexec

  • SCCM 2012 OSD task sequence condition

    Is there a way to set a condition on a step that looks to see if the machine is already known to SCCM / Active Directory?
    I have a step that names the PC using ITX Solutions AutoName function. I want to say only use this step if the machine is not known.

    This is essentially a follow on to: http://social.technet.microsoft.com/Forums/en-US/3c6f37ad-b3dc-4219-ae7f-e6c51f05d5bf/sccm-2012-osd-retain-computer-name-on-reimage-rebuild?forum=configmanagerosd
    To my knowledge, there is nothing explicitly built-in; however, you might be able to check _SMSTSMachineName to see if it matches the default WinPE naming convention of MINNIT_* or _SMSTSClientGUID to see if it has a value.
    You could also put a task in before the format and partition step to check for an existing installation.
    Jason | http://blog.configmgrftw.com

  • SCCM 2012 Update Group inconsistency Problem with Red marked Updates

    Hi everybody,
    we have a big Problem with our SCCM 2012 R2 CU3 Enviroment, regarding of Update Groups which got out of sync.
    we have a SCCM Site Infastructure with one CAS and 4 Primary Sites and on every Site is the SUP Role installed.
    I don't know when this failure occours but i think it was after the CU3 Installation. The Installation itself went smooth without any Errors or Warnings.
    The Problem is as following. We have some updates in Update Groups (all of them are Core XML Updates) which are out of sync and marked red as an invalid Update on 2 Primary Sites. On the CAS Site and the 2 other Primary SItes they are marked as green (downloaded
    yes and deployed yes)
    We have no Replication issues regarding the Replication Status (everything is synchronized to 100%) and the Replication Link Analyzer does also show no Problems at all.
    I now deleted the Deployments and the SW Update Group waited until the replication was fine and created a new one and downloaded these patches on one of the Primary Sites which had shown this Failure.
    The Result was not good. It looks like before. On the CAS and 2 Primary Sites the Deplyment is shown as downloaded but on the other 2 Sites the Status is again Downloaded=no.
    Does anybody have any idea what to do now ? I checked objmgr.log and rcmctr. log but found nothing what shows me the way in the right direction.
    Thx for your time, and it would be fine if anybody can share knowledge about this failure and how to fix it.
    All other Ideas are also welcome.
    Thx a lot in advance and have a nice bug free day :-)
    Bastian

    Hi,
    Please try to manually synchronize software updates from the CAS and monitor the WSUSCtrl.log, WCM.log and wsyncmgr.log on the CAS and Primary sites.
    Best Regards,
    Joyce
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • Helix gen.2 very slow with USB 3.0 and SCCM 2012 OSD

    Hello there, i have a problem with our Helix gen.2. i would like deploy the OSD with SCCM 2012 and so i insert the USB 3.0 Dongle driver in WinPE. The Download and WIM installation is very fast but slows down after the OSD TS insert all Drivers for the system an makes a reboot. After the reboot the machine runs very slow over the network (1GB) and over 20 Hours and breaks down with a unsigned Error Message 80004005. i change the driver to an old version for the UBS 3.0 but it doesn´t helps so i need help from you. with best regards andré

    What OS are you deploying on the box, 7 or 8.1?
    Did you import the drivers from the Helix2 SCCM driver pack for the appropriate OS into a Driver Package?
    Did you also add the USB 3.0 drivers specific to the OS being deployed into that same Driver Package?
    Do you have an Apply Drivers task that references this driver package in the task sequence?  If so, you should be able to find the task ID in the SMSTS.log file and verfiy it is running.

  • SCCM 2012 OSD Replace Scenario

    Hi,
    I am using SCCM 2012 with MDT integration. My MDT OSD task sequence works fine, except in a replace Scenario. I run the client replace task sequence on the old machine and the USMT back is successful. I then boot with a USB thumb drive with boot media on
    the new machine. I get the correct task sequence but it seems like the OS want to install on the BDE Drive, which I to small. My new computer and refresh works without problems and install on the correct drive. I don't understand why I get this issue in a
    replace scenario. I am very new to SCCM OSD and your assistance would be greatly appreciated.

    Hi,
    Have you checked the log file smsts.log? Maybe it can give us some clues.
    Here is a similar post for your reference.
    Replace Scenario alternative for USMT Migration
    http://blogs.technet.com/b/deploymentguys/archive/2011/09/01/replace-scenario-alternative-for-usmt-migration.aspx
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012 OSD; Not finding driver package during deployment

    I've been having some trouble setting up my OSD deployment using SCCM 2012 and hope someone can point me in the right direction.  Specifically I am having trouble with device driver deployment while deploying my reference image. 
    I am running SCCM Config Manager 2012 SP1 CU2. This is running on a Server 2012 VM with SQL 2012.  I am building an OSD deployment and have successfully captured my reference image.  I am not sure if it matters, but I manually built a reference
    PC and using capture media (USB stick), I successfully captured my reference image.  I have imported my drivers for the target PC into Config Manager and into a driver package.  The driver package has been deployed to the distribution point
    (DP).  I checked the status of the driver package within the console and verified it has been deployed to the DP.   I created a new task sequence (TS) to deploy the captured wim.  Within the TS, I added an "Apply
    Driver Package" step and pointed it to the aforementioned driver package.  I added a WMI query to the step as follows
    select * from Win32_ComputerSystem where Model like "HP Probook 6570b%." 
    Incidentally, I did a wmi query on the target PC to verify the model.  I deployed the TS to the unknown computers collection and PXE booted the target PC.  I ran through the OSD wizard and while OSD is verifying the deployment prerequisites,
    the deployment fails with the error, "The task sequence cannot be run because a package referenced by the task sequence could not be found."  I checked the smsts.log log and found the following:
    Failed to find CCM_SoftwareDistribution object for AdvertID="CT120043", PackageID="CT100044", ProgramID="*"
    After some research I found this error means Config Manager cannot find the driver package (PackageID="CT100044")
    for deployment.  After more research I have done the following:
    Deleted the Driver Package and recreated it and updated the TS step to point to this package.
    Deleted and recreated the TS along with the driver package.
    Recreated the driver package and distributed content, only importing the NIC drivers as a way to make a simple test.
    When distributing content I verified it was successfully completed each time as per the console.
    Each time I recreated the driver package and the OSD failed, smsts.log is showing the appropriate package ID in the error.  If I disable the Apply Driver Package step and configure a Apply Device Drivers step to install the best matched compatible drivers
    and limit the driver matching to the specific driver package, the OSD completes but the drivers do not install. It is as if Config Manager is not seeing the imported drivers at all.
    I have run out of options to try and hope someone can help point me in the next direction to take.  After reading numerous forums and guides, I am sure I am doing the OSD steps correctly but I am apparently missing something.
    Thanks in advance,
    Mike G.

    Thanks for responding.
    Yes after I posted the question I right-clicked on the driver package, and selected to update distribution points.  I checked now (about 12 hours later) and the package is showing it has not finished updating.  I checked the content status and
    it is "waiting for content."  I looked at distmgr.log and I found an error "Failed to start DP health monitoring task for package 'CT100044'. Error code: -1".  This error would occur every 30 min after each time the DP retried to process
    the package. After some research I found a post stating a file called "Microsoft" or "Program" on located on the root of the site server could cause this and renaming or deleting the file would resolve this. I renamed the file and after the next time
    it retried, the error cleared, however the package status is still waiting for content.  I tried doing a validation on the package but so far there has been no change.

  • SCCM 2012 OSD Task Sequence Fails "An error occurred while retrieving policy for this computer"

    We have SCCM 2012 R2. I amm trying to start OSD task sequence from bootable media.
    Hyper-v client gets DHCP ip and starts MDT bootable media, but could not find policy.
    From F8 I can ping SCCM/DP/MP server.
    What could be the cause?

    Yes, this DHCP client is in the same subnet as other working clients.
    smsts.log from client
    Request was successful. TSPxe
    21.03.2014 14:14:14 324 (0x0144)
    pNext != NULL, HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,1970)
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    reply has no message header marker TSPxe
    21.03.2014 14:14:14 324 (0x0144)
    DoRequest (sReply, true), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\osdmessaging\libsmsmessaging.cpp,5868)
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    Failed to get client identity (80004005)
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    ClientIdentity.RequestClientIdentity (), HRESULT=80004005 (e:\nts_sccm_release\sms\client\tasksequence\tsmbootstrap\tsmediawizardcontrol.cpp,1113)
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    failed to request for client
    TSPxe 21.03.2014 14:14:14
    324 (0x0144)
    Exiting TSMediaWizardControl::GetPolicy. TSPxe
    21.03.2014 14:14:14 324 (0x0144)

  • SCCM 2012 OSD: Import computer object fails

    Hi,
    Please see this post:
    http://social.technet.microsoft.com/Forums/en-US/6dbd2b38-4dbb-4de3-bb25-e3a30813f108/importing-computer-fails-unable-to-save-changes?forum=configmanagerosd
    We have exactly the same issue: we cannot import a computer object due to the error "Unable to save changes", a query which searches for mac-addresses doesn't reveal the pc-name (which is logic because the sccm 2012 should run an inventory first
    but the pc is not loaded).
    Please advise.
    J.
    Jan Hoedt

    Any chance that the object (where you are trying to add a MAC address) was added to the database by AD group discovery? So the name is already in the database? If so: that's expected.
    If not: CU1 for R2 might fix the problem (it is listed as being fixed)
    Torsten Meringer | http://www.mssccmfaq.de

  • SCCM 2012 OSD Retain Computer Name on re-image rebuild

    I am migrating our PC workstation Windows 7 build process from MDT 2010 lite touch to SCCM 2012 zero touch. Everything is working expect
    one thing. 
    When I re image a PC, if the PC is already known to AD I want it to keep the previous machine name, so that it retains its collection memberships
    for software. If I put the PC into the collection that the OSD task sequence is advertised to, the machine successfully rebuilds with the same machine name. Starting from Windows - i.e the configuration manager client.
    If I initiate the rebuild via PXE boot the machine gets a new name. 
    I have read that if the OS is booted from PXE or boot media then the deployment type is new computer. But if the TS is advertised to an
    existing client and initiated from the config manager client, the deployment type is refresh. 
    I'm currently using itx-solutions.nl AutoNameControl to get RIS style naming i.e. PC-123, PC-124 etc.
    When I used MDT and lite touch I used MaikKoster Deployment Webservice and obtained the machine name via the GetComputerNameByNetbootGuid
    service. This worked perfectly. I don't know what exactly sets this in AD, but have noticed the PC's built with SCCM have no value for NetbootGuid so this doesn't work.
    How do I always get the PC to retain the same name on rebuild?

    Thank you are correct - It turns out it was the AutoNameControl. It creates a new name regardless.
    I set a TS variable called ExisitngClient as the first step of my TS - but put a condition on it, to check for the existence of CcmExec.exe on the client. If it exists then I set the variable to TRUE.
    Then later on when the AutoNameControl runs, I put a condition of    IF ExistingCient not equals TRUE.
    Meaning it only runs if it didn't have Config Manager on before the format.
    It seems to work.
    Thanks for the help

  • SCCM 2012 OSD/MDT TS: Can I set the ComputerBackupLocation to d: (local) durin wim capture

    Hi,
    SCCM 2012 SP1 OSD w MDT 2012 /MDT TS:
    Can I set the ComputerBackupLocation to d: (local drive) durin OS wim capture?
    /SaiTech

    Hi,
    Please see if the article below helps:
    Understanding How MDT 2010 Automatically Determines a Backup
    http://www.migee.com/2011/03/10/understanding-how-mdt-2010-automatically-determines-a-backup-location/
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • SCCM 2012 OSD PXE, OS System disk is D:/ !

    HI !
    SCCM 2012 st.OSD PXE, OS System disk is D:/ !
    Deploing OS, resulting
    in system drive
    is D:/. How to achieve this
    would be C :/?
    cenubit

    Ok. 
    What are the steps and conditions
    are followed
    to establish a
    new  Reference Image ?
    cenubit

  • SCCM 2012 - OSD - HAL.dll error (windows XP) using USB

    Hi
    SCCM 2012
    I'm creating OSD for Windows XP  and create .iso files
    1. I create ISO files
    2. make the USB bootable
    3. Copy the ISO files in content in USB
    4. Boot from USB,  when it finish I;m getting the HAL.dll error
    Please advise
    Robert

    The hal.dll is missing?
    http://support.microsoft.com/kb/314477/en-gb
    Juke Chou
    TechNet Community Support

  • SCCM 2012 OSD and WinPE-StorageWMI?

    Hi,
    I am using SCCM 2012 SP1 OSD with MDT 2012. I am trying to work out how to use the command from the
    WinPE-StorageWMI.
    I have added them to my boot wim and am trying to invoke them from powershell from the F8 prompt first
    then once I get them going in there put them in my task sequence.
    However when I do not see them?
    Am I not seeing any extra modules is there something basic I am missing? Am I meant to see a module
    called WinPE-StorageWMI?
    Thanks,
    Ward.

    The module is a part of Powershell. You need to enable WinPE-PowerShell.
    http://technet.microsoft.com/en-us/library/hh824926.aspx
    Juke Chou
    TechNet Community Support

  • OSD: unattend.xml in capture conflicts with unattend in deploy?

    Hi,
    We need to remove some Windows components in our capture, so we created a small unattend.xml for it.
    Now we deploy this capture and apply an xml which contains totally other settings but it fails.
    Please advise what best practises is: only 1 unattend.xml in deploy? Then components are installed which we don't want (like Media Center), if we use the unattend.xml in capture only, we lose flexibility: each change we need to capture the image again.
    J.
    Jan Hoedt

    If you want to remove Windows features, you could just use DISM:
    In WinPE phase, after Apply Operating System Image Step
    Add run command line step
    Commandline: cmd.exe /c dism.exe /image:%OSDTargetDrive%\ /disable-feature /featurename:MediaCenter /scratchdir:%OSDTargetDrive%\Windows\Temp /norestart
    Just make sure that you use %OSDTargetDrive% -variable in your Partition Disk 0 and Apply Operating System Image -steps.

Maybe you are looking for