Running task as sysprep finishes

I'm pretty new to sysprep. I'm looking to run a task AS syspre
finishes, but before a user logs in. Basically I would like to make
web service call from a .vbs file to announce that the computer ha
finished sysprepping. I want the time to be as accurate as possible

If I run this in the specalize pass, it's too early since sysprep stil
has a lot to finish. In the OOBE step, it's too late since it require
a user to login

Are there any suggested ways to have something triggered as a fina
sysprep step

Thanks

--
OWScott

"OWScott" <> wrote:

> I'm pretty new to sysprep. I'm looking to run a task AS sysprep
> finishes, but before a user logs in. Basically I would like to make a
> web service call from a .vbs file to announce that the computer has
> finished sysprepping. I want the time to be as accurate as possible.
>
> If I run this in the specalize pass, it's too early since sysprep still
> has a lot to finish. In the OOBE step, it's too late since it requires
> a user to login.
>
> Are there any suggested ways to have something triggered as a final
> sysprep step?

Not part of sysprep, but what about a self-deleting (i.e., one-time) set in
place in the specialize pass? (Don't just delete the script; get rid of the
call to it as well. Recall that a startup (or shutdown) script runs in the
system context.)

The devil, as usual, would be in the details. If you would post just what
you're trying to do someone might suggest a less complex way to achieve the
desired result but without knowing the parameters of the task it's hard to
know what could be done.

Joe Morris

Joe Morris;1088673 Wrote:
>
> Not part of sysprep, but what about a self-deleting (i.e., one-time
> set i
> place in the specialize pass? (Don't just delete the script; get rid o
> th
> call to it as well. Recall that a startup (or shutdown) script runs i
> th
> system context.
>
> The devil, as usual, would be in the details. If you would post jus
> wha
> you're trying to do someone might suggest a less complex way to achiev
> th
> desired result but without knowing the parameters of the task it's har
> t
> know what could be done
>
> Joe Morri

Thanks for the reply. I tried a RunSynchronousCommand in Specialize bu
there appeared to be a lot of work still to do, including a reboot an
the performance check. I'm hoping to delay the execution of that comman
even more so that it coincides with the last step of sysprep

Basically I'm just running this

Code
-------------------
<RunSynchronousCommand wcm:action="add"
<Order>1</Order
<Path>c:\windows\system32\cscript c:\windows\system32\sysprep\computercheckin.vbs</Path
</RunSynchronousCommand
-------------------

This will run a vbs file that does a web service call across th
network and checks the server in and says that it's ready. What it doe
isn't the important thing. That part I can do. What I don't know is ho
to run it when sysprep finishes. Specialize is too early though and th
computer isn't really ready yet

--
OWScott

"OWScott" <> wrote in message
news:...
>
> I tried a RunSynchronousCommand in Specialize but
> there appeared to be a lot of work still to do, including a reboot
> and
> the performance check. I'm hoping to delay the execution of that
> command
> even more so that it coincides with the last step of sysprep.
>
> Basically I'm just running this:
>
>
> Code:
> --------------------
> <RunSynchronousCommand wcm:action="add">
> <Order>1</Order>
> <Path>c:\windows\system32\cscript
> c:\windows\system32\sysprep\computercheckin.vbs</Path>
> </RunSynchronousCommand>
> --------------------
>
>
> This will run a vbs file that does a web service call across the
> network and checks the server in and says that it's ready. What it
> does
> isn't the important thing. That part I can do. What I don't know is
> how
> to run it when sysprep finishes. Specialize is too early though and
> the
> computer isn't really ready yet.
>

In the Microsoft-Windows-Shell-Setup component of the oobeSystem pass
you could setup AutoLogon (and set LogonCount to 1 to disable it once
it is done) and move your RunSynchronousCommand to the
FirstLogonCommands. It would look something like this:

<settings pass="oobeSystem">
<component name="Microsoft-Windows-Shell-Setup"
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">
<AutoLogon>
<Password>
<Value>MyPassword</Value>
<PlainText>true</PlainText>
</Password>
<Enabled>true</Enabled>
<Username>MyUserName</Username>
<LogonCount>1</LogonCount>
</AutoLogon>
<UserAccounts>
<LocalAccounts>
<LocalAccount wcm:action="add">
<Password>
<Value>MyPassword</Value>
<PlainText>true</PlainText>
</Password>
<DisplayName>MyUserName</DisplayName>
<Name>MyUserName</Name>
<Group>Users</Group>
</LocalAccount>
</LocalAccounts>
</UserAccounts>
<FirstLogonCommands>
<SynchronousCommand wcm:action="add">
<CommandLine>c:\windows\system32\cscript
c:\windows\system32\sysprep\computercheckin.vbs</CommandLine>
<Order>1</Order>
<Description>Computer Checkin</Description>
</SynchronousCommand>
</FirstLogonCommands>
</component>
</settings>

Hope this helps!

--
Zaphod

Pan-Galactic Gargle Blaster: A cocktail based on Janx Spirit.
The effect of one is like having your brain smashed out
by a slice of lemon wrapped round a large gold brick.

Absolutely brilliant! That was exactly what I was looking for. I ran a
test and it worked just as you promised.

Thanks!

Scott


--
OWScott

"OWScott" <> wrote in message
news:...
>
> Absolutely brilliant! That was exactly what I was looking for. I
> ran a
> test and it worked just as you promised.
>
> Thanks!
>

Glad I could help.

--
Zaphod

Vell, Zaphod's just zis guy, ya know? - Gag Halfrunt