none
Updated wim file does not join domain/local admin disabled RRS feed

  • Question

  • Let me first explain how i work.

    I have VM's where i install windows/updates and some programs.

    Then i take a clone of that machine and i run the capture windows through the litescript, and i create a custom .wim file

    Then i import the new wim file in MDT and change my tasksequence that it installs the new wim file.

    Then i delete the cloned VM as it is sysprepped.

    When there are a lot of updates, i start my vm, update windows and make changes if necessary.

    Then i clone it again and create a custom wim file

    then i import it again in mdt and change my tasksequence.

    This always worked, untill my latest updated wim file

    When i assign my latest wim file in the tasksequence it hangs on 54% completion and becomes unresponsive in the mdt monitoring.

    When i look at the computer where i wanted to deploy the image, the OS has been installed, but it didnt join the domain(which is the next step) and the local admin account is disabled for some reason.

    When i assign my previous wim file to the tasksequence everything works again. the installation is 100% complete, it is in the domain, local admin acount is enabled, and all other programs i install with the tasksequence is without fault.

    So i am guessing something is wrong with my wim file or i did something wrong in the VM i updated, bu ti have no idea, what i did different then all other times.

    Monday, November 30, 2015 10:06 AM

Answers

  • After recreating my vm to capture, it worked.

    And i found out my problem. I changed 1 thing to many in the Default users profile, making a new userprofile like the administrator after deployment, unusble.

    So problem fixed
    • Marked as answer by UinguZero Friday, January 22, 2016 8:06 AM
    Friday, January 22, 2016 8:06 AM

All replies

  • You will need to look at your panther logs. If it isn't sysprepping properly or something that will be there too

    https://technet.microsoft.com/en-us/library/dd744583%28v=ws.10%29.aspx


    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Monday, November 30, 2015 9:46 PM
    Moderator
  • Hi,

    I am looking at the setupact.log file and i see a lot of different errors and also 4 times this message:

    Beginning of a new sysprep run.

    I am not sure what to look for exactly in the log files.

    Wednesday, December 9, 2015 4:04 PM
  • You have run out of rearms.  You have done a clone of a clone of a clone of a clone etc and that will fail eventually.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    • Marked as answer by Ty GlanderModerator Wednesday, December 9, 2015 7:58 PM
    • Unmarked as answer by UinguZero Thursday, December 10, 2015 8:42 AM
    Wednesday, December 9, 2015 7:58 PM
    Moderator
  • That is something i also thought.

    So i've created a brand new VM reinstalled everything from scratch. Made 1 clone to sysprep the device, but this also fails with the same issue mentioned in my first post.

    Any other ideas?

    Can you check how many reams are still available ** use this cmd code: slmgr /dlv

    It says: Remaining windows rearm count: 999




    • Edited by UinguZero Thursday, December 10, 2015 8:48 AM
    Thursday, December 10, 2015 8:42 AM
  • It also could be that something has failed during sysprep.

    Logs are very important. https://keithga.wordpress.com/2014/10/24/video-mdt-2013-log-files-basics-bdd-log-and-smsts-log/ Mention any customizations you have made.

    Thursday, December 10, 2015 7:22 PM
    Moderator
  • @UinguZero I don't understand what you are trying to do above. What does "Clone" mean in this context? Does that mean sysprep, /capture-image, or something else?

    If you are still having problems, most likely the cause is a failed sysprep run, please copy the Sysprep Panther logs to a public share like "OneDrive" and share the link.


    Keith Garner - Principal Consultant [owner] - http://DeploymentLive.com

    Thursday, December 10, 2015 10:17 PM
    Moderator
  • After recreating my vm to capture, it worked.

    And i found out my problem. I changed 1 thing to many in the Default users profile, making a new userprofile like the administrator after deployment, unusble.

    So problem fixed
    • Marked as answer by UinguZero Friday, January 22, 2016 8:06 AM
    Friday, January 22, 2016 8:06 AM