1 2 Previous Next 19 Replies Latest reply on Oct 13, 2010 5:43 AM by mikenewland

    LD9, Win 7, Sysprep headache

    Apprentice

      I know there have been several questions posted in regards to the headaches of getting the sysprep to work with LD9 and Win 7.  Here is my problem.  I cannot get sysprep to work properly - it will not add a computer to the domain, it will not name the computer correctly, and it will not install LANDesk.  (I haven't tried to see if the Driver Library portion works yet)

       

      I have applied the recommend patches to supposedly fix the problem with computers joining the domain.  Still doesn't work.  Here are the steps I take:

       

      Build a computer with Windows 7 Pro and install all applications.

      Run Sysprep from c:\windows\system32\sysprep.exe

      It gives me two options under system cleanup action (OOBE and Audit)

      There is a generalize box you can select and then of course the shutdown options

       

      I have tried OOBE and Audit without any success (I do not select generalize because I have read you do not want this option selected)

       

      So once sysprep has finished, I shutdown and create the image using WinPE.

       

      I can restore the image to any machine but it does not add to domain, does not set the correct computer name nor does it install the LAndesk Agent.

       

      Here are my script settings for Deploy Image:

       

      Under Methods and Credentials:

      I select classical download, image uses sysprep and use HII

      I enter the correct domain and user name and password

      Image type and path is all set up correctly

      Under sysprep options:

      I select Windows 7

      This is where I get confused - I can use the existing sysprep file as a template once I save the pe script (if I click browse it shows the script name.xml)

      Do I leave that blank or do I select teh scriptname.xml.

      The location of the sysprep file in the image being deployed points to c:\unattend.xml  ..After I create the sysprep and do not shut down, I try to browse for this file and it does not exist! ??

      Image Settings is set up correctly with time zone, MAK key and local admin password for this image (I assume they are talking about the administrator account for windows.  We actually rename the admin account to our own liking so I assume this shouldnt cause a problem if the password for it is correct.

      Under network credentials I have domain select with all information

      Naming convention is set up correctly using the computername.ini that i saved to \\core\program files\landesk\management suite) and the file looks like this (I want it to use the service tag of the Dell machine)

       

      [Rename Operations]
      tok0=ASSET TAG

       

      Under HII I set it to Auto Detect

      Under landesk agent - I point to the correct file and set the credentials.

       

      I save the script and add to PXE Boot Menu

       

      I can restore the image fine to any workstation, but it does not rename correctly, it does not add to domain and it does not run the landesk agent install.

       

      I hope someone can give me some insight on this.  Talk about frustrating...  I know there are several published docs about this issue but some are old and the newer ones are left with answers that are not fixing the issue.

       

      Thank you for your time.

        • 1. Re: LD9, Win 7, Sysprep headache
          Apprentice

          I tried going through the process again using SysPrep Audit with no generalization and it looks like after the image was dropped onto the machine, it is running the sysprep process...  Top left says :

           

          c:\windows\system32\sysprep\sysprep.exe /oobe /generalize /reboot

           

          We shall see what happens...

          • 2. Re: LD9, Win 7, Sysprep headache
            Apprentice

            Well.  It boot to the windows 7 pro set up screen. Clicked Next, entered a username and clicked Next, entered password and clicked next, accepted the license terms, Hmm - have a feeling its not working because I had to set up the time zone and I specified the time zone in the PE Script.

             

            After it made it to the Desktop, I checked system properties.  It appears it did give itself a computer name but its still using the MAC Address and not the ASSET Tag as I specified in the computername.ini

             

            I assume it took the MAK key because it says I have three days to activate.  It still is in workgroup

             

            Any ideas??  If I need to copy my sysprep.xml let me know and I will gladly do so.

            • 3. Re: LD9, Win 7, Sysprep headache
              Apprentice

              Screw it.  I don't even care anymore if I can get these workstations to join the domain - I don't think my naming scheme will allow it to happen.

               

              I wish someone would just give me the sysprep command line to run after the image is ready to be created and hope for the best.  As far as I'm concerned, I'm not impressed by HII becaues it is not working per the documentation found on here or within the application.

               

              Needless to say, I'm a little disappointed.

              • 4. Re: LD9, Win 7, Sysprep headache
                Apprentice

                Sounds to me like your unattend.xml file is invalid or at least partitally invalid.  The fact that you have to manually complete mini setup before Windows install completes is proof enough of that.  I would advise in the first instance that you leave LANDesk to create the unattend.xml for you, do this by leaving the sysprep template option unticked in your OSD script.  This will create a sysprep answer file based on the options you select in the sysprep section of the script creation wizard.  The LANDesk generated xml file will then be copied to the correct location on the target device (c:\unattend.xml I believe) automatically and should at least leave you with a fully unattended Windows installation.

                 

                Get to this point first, worry about HII and domain joining later.

                 

                Steve

                • 5. Re: LD9, Win 7, Sysprep headache
                  Apprentice

                  Sorry to sound frustrated....  Thank you for your assistance.

                   

                  Question - after I have Windows 7 Professional configured and all applications installed, I need to run sysrprep.  When I run sysprep from C:\windows\system32\sysprep

                   

                  What options do I choose?  OOBE or Audit?  Do I select Generalize?

                   

                  If you can let me know, I will get started.

                   

                  Thanks man!

                  • 6. Re: LD9, Win 7, Sysprep headache
                    Apprentice

                    ..or am I doing this backwards.  Should I create the winpe script and then take that XML file and place it on the C:\ of the machine being imaged and rename it to unattend.xml  ??

                    • 7. Re: LD9, Win 7, Sysprep headache
                      Apprentice

                      The generalise switch is what forces sysprep to strip out the security identifiers.  It also forces sysprep to run through the generalise and specialise passes (if you're familar with WAIK).  In other words it is essential for the generalise switch to be used at some point.  Prior to SP1 you had to run sysprep with the generalise switch once you prepped your reference PC ready to capture.

                       

                      A patch (thats included in SP1) changed things a little.  Now, when you create an OSD script (and a corresponding sysprep answer file - they both get created at the same time) it adds a sysprep command to the answer file so that sysprep is re-run for you during the audit pass.  This auto-rerunning of sysprep includes the generalise switch.

                       

                      The short answer regarding what options to use when running sysprep prior to capture is as follows:-

                      LDMS v9 - prior to SP1: use the generalise option

                      LDMSv9 - with SP1: do not use the generalise option

                      In both cases you must put the machine into audit mode.

                       

                      In answer to your second question - the sysprep answer file that is created as part of the script creation wizard is placed on the core server.  It is then copied automatically and renamed to c:\unattend.xml.  This happens after the image is been deployed but before the reboot out of WinPE. You do not have to do anything other than create the script and run it.

                       

                      Hope this helps

                       

                      Steve

                      • 8. Re: LD9, Win 7, Sysprep headache
                        Apprentice

                        Thank you very much Steve - appreciate all the information and it definitely clarifies my questions.  I will give this a shot and let you know the results.

                         

                        Much appreciated!

                        • 9. Re: LD9, Win 7, Sysprep headache
                          Apprentice

                          Well, getting closer.  It appears the process starts to work and it basically did the following upon reboot after deploying image:

                           

                          Windows Setup

                           

                          Windows is now setting up the following items:

                           

                          sysprep /oobe /generalize /reboot

                           

                          "Sysprep is working..."

                           

                          Logging off ....

                           

                          Restarted

                           

                          Setup is starting services...

                           

                          Setup will continue after restarting.......

                           

                          Setup is checking video performance....

                           

                          After this it said failed to log into windows.  Here is the problem (I think).  We change our administrator account to a different name and set the password before we image.  It is showing the correct user name but the password is not working??  Is there something I am doing that causes this behavior due to the Sysprep?

                          • 10. Re: LD9, Win 7, Sysprep headache
                            Apprentice

                            Yep, must be.  I try to log back in as administrator and enter the password we set up before image and it says my account has been disabled.  I noticed Windows 7 does that - why is it disabling the admin account?  Is there a way I can change that?

                            • 11. Re: LD9, Win 7, Sysprep headache
                              Apprentice

                              Looks like you're getting closer!  Once the system enters Audit mode during sysprep it will try to log on with the local administrator account so I'd suggest not disabling it yourself prior to capture.  In any case, Audit will disable the administrator account anyway once its done - which answers your second question.  This is by design - I guess they consider it to be for extra security.

                              • 12. Re: LD9, Win 7, Sysprep headache
                                Apprentice

                                Okay I got it working (for the most part).  Set up Windows 7 - ran sysprep (audit, no generalization).  Shutdown and captured.  When I restore, it appears to do everything except execute the LANDesk Agent and it does not set the time zone; however, it does name the computer name as I asked it too.  The local admin account is not disabled - thank goodness!

                                 

                                In the script settings as you suggested, I did not put a check next to "use existing sysprep file as a template"

                                 

                                Any reason why the landesk agent is not being installed or the time zone being set?  I verified the passwords I am using are correct.

                                 

                                --Getting so much closer...

                                • 13. Re: LD9, Win 7, Sysprep headache
                                  Apprentice

                                  Here is the XML file LANDesk creates - maybe this will help with the troubleshooting...

                                   

                                  <?xml version="1.0" encoding="utf-8"?>
                                  <unattend>
                                    <settings pass="auditSystem">
                                      <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                                        <DriverPaths>
                                          <PathAndCredentials wcm:keyValue="1" wcm:action="add">
                                            <Path>c:\windows\LDDriverStore</Path>
                                          </PathAndCredentials>
                                        </DriverPaths>
                                      </component>
                                      <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                                        <UserAccounts>
                                          <AdministratorPassword>
                                            <PlainText>true</PlainText>
                                            <Value>password</Value>
                                          </AdministratorPassword>
                                        </UserAccounts>
                                        <AutoLogon>
                                          <Enabled>true</Enabled>
                                          <Username>Administrator</Username>
                                          <Password>
                                            <PlainText>true</PlainText>
                                            <Value>password</Value>
                                          </Password>
                                          <LogonCount>1</LogonCount>
                                        </AutoLogon>
                                      </component>
                                    </settings>
                                    <settings pass="auditUser">
                                      <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                                        <RunSynchronous>
                                          <RunSynchronousCommand wcm:action="add">
                                            <Order>1</Order>
                                            <Path>c:\windows\System32\sysprep\sysprep.exe /oobe /generalize /reboot </Path>
                                          </RunSynchronousCommand>
                                        </RunSynchronous>
                                      </component>
                                    </settings>
                                    <settings pass="generalize">
                                      <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                                        <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
                                      </component>
                                    </settings>
                                    <settings pass="oobeSystem">
                                      <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                                        <OOBE>
                                          <HideEULAPage>true</HideEULAPage>
                                          <ProtectYourPC>1</ProtectYourPC>
                                          <SkipMachineOOBE>true</SkipMachineOOBE>
                                          <SkipUserOOBE>true</SkipUserOOBE>
                                        </OOBE>
                                        <ProductKey>XXXXXXXXXXXXXXXXX</ProductKey>
                                        <RegisteredOwner></RegisteredOwner>
                                        <RegisteredOrganization></RegisteredOrganization>
                                        <TimeZone>(UTC-05:00) Eastern Time (US &amp; Canada)</TimeZone>
                                        <UserAccounts>
                                          <AdministratorPassword>
                                            <PlainText>true</PlainText>
                                            <Value>password</Value>
                                          </AdministratorPassword>
                                        </UserAccounts>
                                        <AutoLogon>
                                          <Enabled>true</Enabled>
                                          <Username>Administrator</Username>
                                          <Password>
                                            <PlainText>true</PlainText>
                                            <Value>password</Value>
                                          </Password>
                                          <LogonCount>1</LogonCount>
                                        </AutoLogon>
                                        <FirstLogonCommands>
                                          <SynchronousCommand>
                                            <CommandLine>c:\ldsleep.exe 30</CommandLine>
                                            <Description></Description>
                                            <Order>1</Order>
                                          </SynchronousCommand>
                                          <SynchronousCommand>
                                            <CommandLine>cmd /q /c del /q c:\ldsleep.exe</CommandLine>
                                            <Description></Description>
                                            <Order>2</Order>
                                          </SynchronousCommand>
                                          <SynchronousCommand>
                                            <CommandLine>cmd /q /c del /q c:\unattend.xml</CommandLine>
                                            <Description></Description>
                                            <Order>3</Order>
                                          </SynchronousCommand>
                                          <SynchronousCommand>
                                            <CommandLine>net use \\landesk01\Packages\LD Agent 9 password /u:aero\svc_landesk</CommandLine>
                                            <Description></Description>
                                            <Order>4</Order>
                                          </SynchronousCommand>
                                          <SynchronousCommand>
                                            <CommandLine>cmd /q /c \\landesk01\Packages\LD Agent 9\wscfg32.exe /F /L /STATUS /NOREBOOT</CommandLine>
                                            <Description></Description>
                                            <Order>5</Order>
                                          </SynchronousCommand>
                                          <SynchronousCommand>
                                            <CommandLine>net use \\landesk01\Packages\LD Agent 9 /d /y</CommandLine>
                                            <Description></Description>
                                            <Order>6</Order>
                                          </SynchronousCommand>
                                          <SynchronousCommand>
                                            <CommandLine>cmd /q /c del /q c:\ldiscan.cfg</CommandLine>
                                            <Description></Description>
                                            <Order>7</Order>
                                          </SynchronousCommand>
                                        </FirstLogonCommands>
                                      </component>
                                    </settings>
                                    <settings pass="specialize">
                                      <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                                        <ComputerName>%COMPUTERNAME%</ComputerName>
                                      </component>
                                      <component name="Microsoft-Windows-UnattendedJoin" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                                        <Identification>
                                          <Credentials>
                                            <Domain></Domain>
                                            <Username></Username>
                                            <Password></Password>
                                          </Credentials>
                                          <JoinWorkgroup>WORKGROUP</JoinWorkgroup>
                                        </Identification>
                                      </component>
                                    </settings>
                                  </unattend>

                                  • 14. Re: LD9, Win 7, Sysprep headache
                                    Apprentice

                                    At a glance I'd say its because you're pointing to the wrong location when installing the LANDesk agent.  When you create the script, in the sysprep section where you install the LANDesk agent you MUST point it to \\<core server>\ldlogon.  I'm guessing you're trying to get it to install the agent from a self contained exe - this will not work, at least not without manually editting the xml file.

                                     

                                    Capture.JPG

                                    1 2 Previous Next