12 Replies Latest reply on Aug 5, 2011 7:11 AM by EMiranda

    sysprep.inf - are multiple ones used?

    Rookie

      Hello All,

       

      I have a question about the sysprep file(s) and LANDesk – we use Windows XP Professional SP3.

       

      So on the system you have built to be the image you unpack the deply.cab to C:SysPrep, in the folder you can place a sysprep.inf with all sorts of good information.

       

      Now in LANDesk, when you build you OSD, two files are used and one of the files looks a lot like a standard sysprep.inf with a few added items from LANDesk.

       

      So now for the question, are both sysprep.inf files used or does one take precedence of the other? Understanding this should help me with sorting out where to make changes for different offices.

       

      Thanks,

        • 1. Re: sysprep.inf - are multiple ones used?
          EMiranda Expert

          Both files are not used,  The LANDesk one will override your existing sysprep.  So you have options:

           

          • You can only use your existing sysprep and uncheck the checkbox in your OSD script that says "Image Uses Sysprep"
          • You can modify the sysprep that LANDesk injects to reflect your own by doing an Advance Edit on your OSD script
          • You can take the sysprep that you are using in your image and copy it to a server share and then point to that sysprep file in your OSD script under the Sysprep Options section - "Use existing SYSPREP file as template"
          • 2. Re: sysprep.inf - are multiple ones used?
            Rookie

            EMiranda,

             

            Thanks, so it sounds like I want to get the good bits from my sysprep and add it to the LANDesk one. I have my [SysprepMassStorage] section populated on the file I used on the system I imaged, I assume I want to keep this section on the one I use via LANDesk?

             

            Rgs,

            • 3. Re: sysprep.inf - are multiple ones used?
              EMiranda Expert

              ldehmer wrote:

               

              EMiranda,

               

              Thanks, so it sounds like I want to get the good bits from my sysprep and add it to the LANDesk one. I have my [SysprepMassStorage] section populated on the file I used on the system I imaged, I assume I want to keep this section on the one I use via LANDesk?

               

              Rgs,

               

              I would go with option 3.  That way you are already using "YOUR" sysprep and LANDesk will append the changes to it like installing the agent and adding ComputerName= replacements.

               

              but either way will work

              • 4. Re: sysprep.inf - are multiple ones used?
                Rookie

                Thanks again - I am going to give it a try and see what happens!

                • 5. Re: sysprep.inf - are multiple ones used?
                  Rookie

                  Just wanted to let you know it is going well – thanks!

                  • 6. Re: sysprep.inf - are multiple ones used?
                    Rookie

                    Which SYS Prep setting combinations have you found that work the best? The project that I am working on calls for the users to be prompted for as little information as possible.  So far reseal and factory still display the SysPrep options screen when logging on. I am going to switch the auto logon to =No but the machine is supposed to be joining the domain and it isn't. Would I be able to insert a script into the runonce box that would domain the machine? I know the OSD script is supposed to be doing it but at this point it is not.


                    Any suggestions?????

                    • 7. Re: sysprep.inf - are multiple ones used?
                      EMiranda Expert

                      all your sysprep control can be done by manual editing the sysprep.inf and providing the info that you want. when you choose to use a sysprep.inf when creating an OSD script. After you save it, you can right click and advance edit the script and your sysprep.inf will show up and you can modify it further to fit your needs.

                       

                      you should go with reseal, mini-setup and shutdown when you are ready to seal your image.  If you plan to deploy to different types of hardware, you should also chech Detect non-plug and play hardware.

                       

                      things that will show prompts if you dont have them set in your sysprep.inf

                       

                      OemSkipEULA=

                      OEMSkipRegional=

                      TimeZone=
                      OemSkipWelcome=

                       

                      Domain information would be stored under [Identification]


                      JoinDomain=DOMAIN
                      DomainAdmin=sysprepadmin
                      DomainAdminPassword=password
                      • 8. Re: sysprep.inf - are multiple ones used?
                        Rookie

                        Awesome! Thanks for the fast reply I am going to try that right now. I'll keep you posted. Thanks again!

                        • 9. Re: sysprep.inf - are multiple ones used?
                          EMiranda Expert

                          Np, let me know how it goes and if you still need some help, when I get to work I can give you some examples of what my sysprep looks like for XP deployments.

                          • 10. Re: sysprep.inf - are multiple ones used?
                            Rookie

                            That combination of SysPrep settings worked great with my OSD script. Thanks for the help!!!

                            • 11. Re: sysprep.inf - are multiple ones used?
                              Rookie

                              Working on a similar project almost the same problem only a little bit different. The machine domains but at the end it logs on as the local administrator. I tried to insert at the end a false value for auto logon but it doesn't seem work. Any suggestions on how to stop the last auto logon?

                               

                              Here is the XML that LANDesk created: (production account, passwords have been changed)

                               

                               

                                <?xml version="1.0" encoding="utf-8" ?>
                              - <unattend>
                              - <settings pass="auditSystem">
                              - <component name="Microsoft-Windows-PnpCustomizationsNonWinPE" processorArchitecture="x86" publicKeyToken="3xbf3856ad364e35" 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="31bf3xx856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                              - <UserAccounts>
                              - <AdministratorPassword>
                                <PlainText>true</PlainText>
                                <Value>2000admin</Value>
                                </AdministratorPassword>
                                </UserAccounts>
                              - <AutoLogon>
                                <Enabled>true</Enabled>
                                <Username>Administrator</Username>
                              - <Password>
                                <PlainText>true</PlainText>
                                <Value>2000admin</Value>
                                </Password>
                                <LogonCount>1</LogonCount>
                                </AutoLogon>
                                </component>
                                </settings>
                              - <settings pass="auditUser">
                              - <component name="Microsoft-Windows-Deployment" processorArchitecture="x86" publicKeyToken="31bf38xx56ad364e35" 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="31bf3xx856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                              - <OOBE>
                                <HideEULAPage>true</HideEULAPage>
                                <ProtectYourPC>1</ProtectYourPC>
                                <SkipMachineOOBE>true</SkipMachineOOBE>
                                <SkipUserOOBE>true</SkipUserOOBE>
                                </OOBE>
                                <ProductKey />
                                <RegisteredOwner>badams</RegisteredOwner>
                                <RegisteredOrganization>William Adams</RegisteredOrganization>
                                <TimeZone>AUS Eastern Standard Time</TimeZone>
                              - <UserAccounts>
                              - <AdministratorPassword>
                                <PlainText>true</PlainText>
                                <Value>xxxxxxxxx</Value>
                                </AdministratorPassword>
                                </UserAccounts>
                              - <AutoLogon>
                                <Enabled>true</Enabled>
                                <Username>Administrator</Username>
                              - <Password>
                                <PlainText>true</PlainText>
                                <Value>xxxxxx</Value>
                                </Password>
                                <LogonCount>2</LogonCount>
                                </AutoLogon>
                              - <FirstLogonCommands>
                              - <SynchronousCommand>
                                <CommandLine>c:\ldsleep.exe 30</CommandLine>
                                <Description />
                                <Order>1</Order>
                                </SynchronousCommand>
                              - <SynchronousCommand>
                                <CommandLine>cmd /q /c del /q c:\ldsleep.exe</CommandLine>
                                <Description />
                                <Order>2</Order>
                                </SynchronousCommand>
                              - <SynchronousCommand>
                                <CommandLine>cmd /q /c del /q c:\unattend.xml</CommandLine>
                                <Description />
                                <Order>3</Order>
                                </SynchronousCommand>
                              - <SynchronousCommand>
                                <CommandLine>net use \\10.209.96.239\ldlogon Wadams1 /u:wadams\amartinez</CommandLine>
                                <Description />
                                <Order>4</Order>
                                </SynchronousCommand>
                              - <SynchronousCommand>
                                <CommandLine>cmd /q /c \\10.209.96.239\ldlogon\wscfg32.exe /F /L /STATUS /NOREBOOT</CommandLine>
                                <Description />
                                <Order>5</Order>
                                </SynchronousCommand>
                              - <SynchronousCommand>
                                <CommandLine>cmd /q /c del /q c:\ldiscan.cfg</CommandLine>
                                <Description />
                                <Order>6</Order>
                                </SynchronousCommand>
                                </FirstLogonCommands>
                                </component>
                                </settings>
                              - <settings pass="specialize">
                              - <component name="Microsoft-Windows-Shell-Setup" publicKeyToken="31bf3xx856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                                <ComputerName>%COMPUTERNAME%</ComputerName>
                                </component>
                              - <component name="Microsoft-Windows-UnattendedJoin" publicKeyToken="31bxxf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="x86">
                              - <Identification>
                              - <Credentials>
                                <Domain>wadams.com.au</Domain>
                                <Username>wadams\mallen</Username>
                                <Password>xxxxxx</Password>
                                </Credentials>
                                <JoinDomain>wadams.com.au</JoinDomain>
                                </Identification>
                                </component>
                                </settings>
                                </unattend>
                              • 12. Re: sysprep.inf - are multiple ones used?
                                EMiranda Expert

                                try changing <LogonCount>2</LogonCount> in your OOBE pass  to <LogonCount>1</LogonCount>