none
JoinDomain, Name Change, Product Key, Mini setup fail RRS feed

  • Question

  • HI 

    I have been doing well with my MDT and WDS setup and most issues I have been able to overcome. But I have now hit a stumbling block and need some assistance. I apologies if this has been posted elsewhere. 



    using server 2012 with MDT 2012 update 1

    Everything boots fine the machine deploys ok but its like none of the mini setup details are applied along with the state restore.

    Only changes i have made is with selection profiles and creating a custom task to inject drivers with a value of Windows 7\x64\%Model%

    Once I login after the failed restore the machine is as it was before i sysprep'd it with the original hostname etc..

    Once i go to start the deployment again i get "Dirty Environment found" "An existing in-progress deployment was found but is in an expected state. would you like to ignore this in progress deployment and start a new one."

    My custom settings.ini are as follows

    Priority=Default
    Properties=MyCustomProperty

    [Default]
    OSInstall=Y
    SkipCapture=NO
    SkipAdminPassword=NO
    SkipProductKey=NO
    SkipComputerBackup=YES
    SkipBitLocker=YES
    EventService=http://BE-Deployment:9800

    UserID=user.name
    UserPassword=password
    UserDomain=domain.local

    SkipAdminPassword=YES
    AdminPassword=[Adminpassword]

    SkipDomainMembership=YES
    JoinDomain=domain.local
    DomainAdmin=user.name
    DomainAdminPassword=password
    DomainAdminDomain=domain


    SkipComputerName=NO
    OSDComputerName=%SerialNumber%

    TimeZoneName=GMT Standard Time

    SkipLocaleSelection=YES
    UILanguage=en-US
    UserLocale=en-GB
    KeyboardLocale=0809:00000809
    WSUSServer=http://be-dc01.causeway.local:8530
    WUMU_ExcludeKB001=KB976002 ;Microsoft Browser Choice Screen Update for EEA

    The logs dont really show anything obvious.  what am i missing. 

    Tuesday, May 21, 2013 2:52 PM

All replies

  • If the newly deployed machine has the same hostname as the machine you captured your WIM from, then it sounds like Sysprep wasn't run with /generalize.  How did you Sysprep the machine before you captured the WIM you are deploying?

    Also, minor, but you may need to remove the comment on the WUMU_ExcludeKB001 line.  Some people have reported issues with that variable working if there is a comment on the same line.


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

    Tuesday, May 21, 2013 3:24 PM
    Answerer
  • I just Ran the capture task from MDT. 

    Should I be running sysprep manually and then entering winpe? 

    Thanks. 

    Raj

    Tuesday, May 21, 2013 3:36 PM
  • No, the Sysprep and Capture Task Sequence from MDT should be fine.  However, it still sounds like something with Sysprep failed.  Do you have a snapshot of the reference machine prior to running the Sysprep and Capture?  If you do, then you can try to run Sysprep manually and see if any errors are generated.

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

    Tuesday, May 21, 2013 3:40 PM
    Answerer
  • Thanks DCthegeek,

    Let me try and tun the sysprep task again and I will let you know how i get on. 

    Raj
    Wednesday, May 22, 2013 8:07 AM