1 Reply Latest reply on Jan 24, 2009 8:48 AM by puercomal

    Sysprep and LANDesk options


      Hi folks..  Sorry, but I just don't get why LD OS deployment asks questions it does in Sysprep Options. 1.) Why ask for "Use existing sysprep.inf as template".  This is just a template, right? - and subsequent changes made will override this? 2.) If so, why does it ask, on the same screen, Location of SYSPREP file in the image being deployed.? 3.) Naming convention - doesn't seem to do anything. 3.) Sysprep Options\LANDesk agent - Path to wscfg32.exe - Doesn't seem to do anything!  I cannot get it to load the LDMS agent! 4.) Naming convention and first attempt to get and use... - Failure Right now, in testing, being a Sysprep to LANDesk NooB, I feel that if I choose NO to Sysprep and just put the image back the way I would regularly, I think I can do all I want via RunOnce and advanced batch/exe files tailored accordingly.

        • 1. Re: Sysprep and LANDesk options

          the sysprep.inf (or unattend.xml if Vista clients) is injected into the freshly imaged machine before it reboots into mini-setup, overwriting whatever .inf or .xml was in place before. The process assumes that the image you're deploying was sealed with sysprep before it was captured, we're just giving that image a new config.


          1) the template thing is so you can not retype information, should you be in the .05 percent of admins who kept and can find a copy of the sysprep.inf they're using. It's read once, but when you click OK a new one will be created and associated with this os deployment task. To edit that file directly, right-click the script and select advanced edit, and you'll get two notepads (one for the osd script, one for the sysprep).

          2) The location field you refer to is not editable, it's just informational.

          3) Naming convention -- first get the device's name from the LANDesk database, but make up something good if that didn't work. What are you seeing?

          4) That plus the other makes me think there's a name resolution problem... the image boots, but it can't see the core during mini-setup.

          1 of 1 people found this helpful