2 Replies Latest reply on Dec 7, 2011 2:26 PM by CallMeCoop

    Provisioning + Windows 7 issue


      Hi all,


      In LDMS 9.0 SP2, I am trying to use Provisioning to deploy our golden Windows 7 image. My template is set up so that after CTOS runs and the machine boots for the first time it joins our domain, installs an agent and then distributes software packages.


      The issue comes in after "Setup is preparing Windows for first use" when it runs the c:\windows\system32\sysprep\sysprep.exe /oobe /generalize /reboot command from our answer file, our provisioning template tries to continue at this point (ie it tries to join the domain) and fails, what we want is it to continue once Windows is done with its setup and we have logged in for the first time.


      Thanks in advance!

        • 1. Re: Provisioning + Windows 7 issue

          It sounds like you have set up the domain join  during the specialize phase in your unattend.xml.  Remove that part and have it auto join a workgroup.  Then add an action under System configuration in your provisioning template to join the domain

          • 2. Re: Provisioning + Windows 7 issue

            Thanks for the input. What you just explained is how it is currently set up. The Join Domain action is in the Provisioning Template, not in the unattend.xml.


            For some reason the ldprovision.exe is being run while the Windows setup is executing the c:\windows\system32\sysprep\sysprep.exe /oobe /generalize /reboot command, instead of the first Autologon.


            As a workaround I've added a Wait action before my Join Domain action, so sysprep runs while the template is on the Wait action, the machine reboots from the sysprep and then the template continues after the autologon from the Wait action. If the Wait wasnt there it would try to join the domain while sysprep.exe is working and fails.


            Anyone else experience something like this? Even if its some other actions besides Join Domain.


            Also for some reason it seems like the part of the answer file where I define <NetworkLocation>Work</NetworkLocation> is not being applied. I have it within the oobeSystem section.