Installed ADS on 2k3 Enterprise Server and after following the quick start guidelines with some success for capturing and deploying images I've run into 3 glitches that hopefully someone can help with.

First, my source image contained an admin password and now if I try to change it in the user variable for the device created in the ADS console it does not change. I'm guessing I should've left it blank on the source. Also on that note, is there a way to execute an auto log on?

Second, also in the user variable for the device I set a value for the machinename and the deployed image keeps the machinename of the source image.

Finally, at the end of the deploy script it calls for a reboot to hd and two boot to hd commands. After the reboot it gets hung after discovering and installing new devices and promts to click Yes to reboot to make changes take affect. Is there a way around this to autoreboot after new devices are found?

Thanks for any assistance.

I've tried this myself, no success ... I think you have to set it un
Variables on the device, and modify the XML sequence file, called
"da-deploy-image-wg.xml" or the domain one. Set it in there, I mean.

/rob



"Tom G" <(E-Mail Removed)> wrote in message
news:6B6A5333-A1E6-4E4A-9DBE-(E-Mail Removed)...
> Installed ADS on 2k3 Enterprise Server and after following the quick start
guidelines with some success for capturing and deploying images I've run
into 3 glitches that hopefully someone can help with.
>
> First, my source image contained an admin password and now if I try to
change it in the user variable for the device created in the ADS console it
does not change. I'm guessing I should've left it blank on the source.
Also on that note, is there a way to execute an auto log on?
>
> Second, also in the user variable for the device I set a value for the
machinename and the deployed image keeps the machinename of the source
image.
>
> Finally, at the end of the deploy script it calls for a reboot to hd and
two boot to hd commands. After the reboot it gets hung after discovering
and installing new devices and promts to click Yes to reboot to make changes
take affect. Is there a way around this to autoreboot after new devices are
found?
>
> Thanks for any assistance.
>

Hi all,
to try to answer the question about sysprep.
Do you have a sysprep.inf file on the hard disk? Is it one you have created
or did you use the one that came with ADS? The one that has;
machinename=^ADS_MachineName^
(can not remember the exact word between the ^s)
You need to make sure that the sequance task that updates the sysprep.inf
file a) referances the right user variable assigned ot the machine and b)
searches for the right string in the right sysprep.inf file in the right
location.



--
regards,

Richard

Please reply to the newsgroup so all may benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Rob Bolbotowski" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> I've tried this myself, no success ... I think you have to set it un
> Variables on the device, and modify the XML sequence file, called
> "da-deploy-image-wg.xml" or the domain one. Set it in there, I mean.
>
> /rob
>
>
>
> "Tom G" <(E-Mail Removed)> wrote in message
> news:6B6A5333-A1E6-4E4A-9DBE-(E-Mail Removed)...
> > Installed ADS on 2k3 Enterprise Server and after following the quick
start
> guidelines with some success for capturing and deploying images I've run
> into 3 glitches that hopefully someone can help with.
> >
> > First, my source image contained an admin password and now if I try to
> change it in the user variable for the device created in the ADS console
it
> does not change. I'm guessing I should've left it blank on the source.
> Also on that note, is there a way to execute an auto log on?
> >
> > Second, also in the user variable for the device I set a value for the
> machinename and the deployed image keeps the machinename of the source
> image.
> >
> > Finally, at the end of the deploy script it calls for a reboot to hd and
> two boot to hd commands. After the reboot it gets hung after discovering
> and installing new devices and promts to click Yes to reboot to make
changes
> take affect. Is there a way around this to autoreboot after new devices
are
> found?
> >
> > Thanks for any assistance.
> >
>
>

You see, that's just it ... I can do a capture, after a sysprep, with
my sysprep.inf all set, etc .... even a reboot thru the Admin agent
(when OS is up) works fine .... but when u get to the DA, it seems to
be limiting what commands you can send to it, one of which - and
important one, is a reboot !!!

/rob


"Richard Trusson [MSFT]" <(E-Mail Removed)> wrote in message news:<(E-Mail Removed)>...
> Hi all,
> to try to answer the question about sysprep.
> Do you have a sysprep.inf file on the hard disk? Is it one you have created
> or did you use the one that came with ADS? The one that has;
> machinename=^ADS_MachineName^
> (can not remember the exact word between the ^s)
> You need to make sure that the sequance task that updates the sysprep.inf
> file a) referances the right user variable assigned ot the machine and b)
> searches for the right string in the right sysprep.inf file in the right
> location.
>
>
>
> --
> regards,
>
> Richard
>
> Please reply to the newsgroup so all may benefit.
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Rob Bolbotowski" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
> > I've tried this myself, no success ... I think you have to set it un
> > Variables on the device, and modify the XML sequence file, called
> > "da-deploy-image-wg.xml" or the domain one. Set it in there, I mean.
> >
> > /rob
> >
> >
> >
> > "Tom G" <(E-Mail Removed)> wrote in message
> > news:6B6A5333-A1E6-4E4A-9DBE-(E-Mail Removed)...
> > > Installed ADS on 2k3 Enterprise Server and after following the quick
> start
> > guidelines with some success for capturing and deploying images I've run
> > into 3 glitches that hopefully someone can help with.
> > >
> > > First, my source image contained an admin password and now if I try to
> > change it in the user variable for the device created in the ADS console
> it
> > does not change. I'm guessing I should've left it blank on the source.
> > Also on that note, is there a way to execute an auto log on?
> > >
> > > Second, also in the user variable for the device I set a value for the
> > machinename and the deployed image keeps the machinename of the source
> > image.
> > >
> > > Finally, at the end of the deploy script it calls for a reboot to hd and
> > two boot to hd commands. After the reboot it gets hung after discovering
> > and installing new devices and promts to click Yes to reboot to make
> changes
> > take affect. Is there a way around this to autoreboot after new devices
> are
> > found?
> > >
> > > Thanks for any assistance.
> > >
> >
> >