Re: Sysprep in Factory mode for ADS Deployment?

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: RonB (anonymous_at_discussions.microsoft.com)
Date: 07/06/04 

Date: Tue, 6 Jul 2004 06:06:41 -0700

Jeff,

Thanks for taking the time to explain the process. We're
well past the capture process, and have a pretty good feel
for how that works. We're trying to "personalize" the
deployment without having to maintain 275 different images
(one for each server), and found lots of MS documentation
referring to the -factory switch of SYSPREP as a possible
way to personalize the deployment prior to running mini-
setup. In either case, we've come up with an alternate
approach and are no longer going down the path of trying
to run sysprep in factory mode. Thanks again for your
time and assistance.

-Ron
>-----Original Message-----
>SYSPREP.EXE is an executable that is run once before
capture. You don't use
>SYSPREP after it is deployed, rather only before it is
captured.
>
>More detail:
>
>The ADS sample sequences document at the top the process
to follow before
>calling the capture task sequence. For example, if you
have a server:
>
>1. Install the ADS agent and add the certificate. Confirm
on the controller
>the server and controller will connect. Maybe run a
simple job.
>
>2. Create DEPLOY.CAB files to the server on C:\SYSPREP.
See sample header.
>
>3. Copy SYSPREP.INI from the ADS sample area. Also,
bring it up in notepad
>and notice the ^string^ that are delimited. For each one
of these, you'll
>need to add a device variable back on the controller for
substition.
>
>4. You may optionally add other info to SYSPREP.INI, but
I recommend getting
>the sample to work first.
>
>5.run the capture sequence. It will automatically run
SYSPREP.EXE and use
>the flags for factory mode etc. It will auto-reseal the
OS. Then it reboots
>the server and the volume is captured.
>
>6. To test it out, I would suggest you use the deployment
sequence. Remember
>to add device variables. See on-line docs
>
><anonymous@discussions.microsoft.com> wrote in message
>news:20e0c01c459e8$592f18c0$a501280a@phx.gbl...
>> Hi Jef,
>>
>> I appreciate your response to the question, but it still
>> leaves me with lots of questions. In your response, you
>> said to review the sample file for capturing a volume.
>> I've done that, but it doesn't provide me with any
>> guidelines on running sysprep in factory mode during the
>> DEPLOYMENT of an image. What I want to do is take an
>> image that I've already captured, deploy it to a new
>> server, but then prior to running mini-setup I want to
>> launch the server into sysprep factory mode to copy
over a
>> custom sysprep.inf file. How do I launch the sysprep in
>> factory after deploying the image, but prior to running
>> mini-setup?
>>
>> RonB
>>
>> >-----Original Message-----
>> >Look at the samples provides for capturing volumes. In
>> the sample, there is
>> >a task with command line parameters. More importantly,
>> you'll need to copy a
>> >few files from the i386 directory to be directly under
>> c:\sysprep\.
>> >Jeff
>> >
>> >"RonB" <anonymous@discussions.microsoft.com> wrote in
>> message
>> >news:209f501c45926$ed529c60$a001280a@phx.gbl...
>> >> Hi all,
>> >>
>> >> We're trying to deploy an image that was collected
using
>> >> ADs to 250 sets of drives for new servers. Ideally,
>> we'd
>> >> like to use the ADS Deployment Agent to script the
>> >> deployment of the images, but we want
to "personalize" a
>> >> lot of the specific settings. According to the
>> >> documentation, an easy (ha ha) way to do this would
be
>> to
>> >> use sysprep in factory mode to set those values
>> (computer
>> >> name, admin password, ip addresses, etc.). Using the
>> >> Sequence Editor, we've modified the XML script that
>> >> deploys the image, but we're having major problems
>> trying
>> >> to script the new system to go into the "factory
mode"
>> of
>> >> sysprep.
>> >>
>> >> Does anyone have any experience with this? If so,
>> should
>> >> the commands to launch sysprep in factory mode occur
at
>> >> the end of the XML file, or closer to the middle
where
>> the
>> >> the image has been deployed. The documentation
simply
>> >> says to "run" sysprep in factory mode, but doesn't
give
>> >> any details on how to actually do that. I know that
>> after
>> >> the image is deployed and mini-setup has run, I can
>> >> manually run sysprep in factory mode, I was hoping
to be
>> >> able to make it do that automatically via the XML
>> script.
>> >> Anyone have any clue about this?
>> >>
>> >>
>> >> Thanks,
>> >> RonB
>> >
>> >
>> >.
>> >
>
>
>.
>

Relevant Pages

  • RE: Simple Windows incident response methodology
    ... Phase I - Preparation (Update forensics toolkit) ... What is the server used for? ... Capture the date and time of the system i. date /t> a:\datetime.txt ii. ... echo Net Accounts:> a:\net.txt ...
    (Incidents)
  • Re: Sysprep in Factory mode for ADS Deployment?
    ... SYSPREP.EXE is an executable that is run once before capture. ... SYSPREP after it is deployed, rather only before it is captured. ... the server and controller will connect. ... I would suggest you use the deployment sequence. ...
    (microsoft.public.windows.server.setup)
  • RE: WINS Error 4204
    ... You may test if your WINS server works properly by using the nblookup.exe ... Click Capture -> Buffer Settings, and then set the Buffer Size to 30 MB. ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)
  • Simple Windows incident response methodology
    ... What is the server used for? ... Prepare for analysis of volatile information (Floppy Disk analysis) ... Capture information about running processes using pslist: ... echo Net Accounts:> a:\net.txt ...
    (Incidents)
  • RE: Simple Windows incident response methodology
    ... this is not an assessment methodology that will be easy to ... An incident response CD is just a bootable CD with boot disk images ... What is the server used for? ... Capture information about logged on users using psloggedon: ...
    (Incidents)