How to auto run a few scripts during/after XP install for end user?

  • Thread starter Thread starter Barkley Bees
  • Start date Start date
B

Barkley Bees

I am in the process of creating a new Windows XP image to support some new
hardware models we will be deploying. After I have the OS build completed I
will sysprep it and then capture it via imagex for deployment.

In addition to this there are a few vbs scripts we want to run when the user
is completing their install. We have the following scripts:

1. Add domain user to local admin group.
2. Set SMS site code to SMS client.
3. Set servername and sign-in name on Office Communicator.

My question is, is there anyway to automate these scripts running once after
the install completes? Appreciate any advice. Thank you.
 
Barkley Bees said:
I am in the process of creating a new Windows XP image to support
some new hardware models we will be deploying. After I have the OS
build completed I will sysprep it and then capture it via imagex for
deployment.

In addition to this there are a few vbs scripts we want to run when
the user is completing their install. We have the following scripts:

1. Add domain user to local admin group.
2. Set SMS site code to SMS client.
3. Set servername and sign-in name on Office Communicator.

My question is, is there anyway to automate these scripts running
once after the install completes? Appreciate any advice. Thank you.
Click to expand...
First, ignore the reply from Andrew E. - out of his ignorance he often
posts inaccurate, misleading, or just plain dangerous things.

Anyway. You might have a look at the GUIRunOnce section of
sysprep.inf, it is what we use to complete the setup of things that
must be done post-reseal. For example, put the program you want to
execute in C:\Windows\Temp (in this example, I'll use MyProg.exe) and
use something like the following:

[GUIRunOnce]
; Once the computer has rebooted and we log in, execute these commands
;
Command0="C:\WINDOWS\Temp\MyProg.exe"

I'm pretty sure you can run multiple commands by using Command1, etc.,
but I've never done it. As an alternative, you could use a batch file
to kick off as many commands as you like.

Hope this helps!

--
Zaphod

Arthur: All my life I've had this strange feeling that there's
something big and sinister going on in the world.
Slartibartfast: No, that's perfectly normal paranoia. Everyone in the
universe gets that.
 
Zaphod said:
Barkley Bees said:
I am in the process of creating a new Windows XP image to support
some new hardware models we will be deploying. After I have the OS
build completed I will sysprep it and then capture it via imagex for
deployment.

In addition to this there are a few vbs scripts we want to run when
the user is completing their install. We have the following scripts:

1. Add domain user to local admin group.
2. Set SMS site code to SMS client.
3. Set servername and sign-in name on Office Communicator.

My question is, is there anyway to automate these scripts running
once after the install completes? Appreciate any advice. Thank you.
Click to expand...
First, ignore the reply from Andrew E. - out of his ignorance he often
posts inaccurate, misleading, or just plain dangerous things.

Anyway. You might have a look at the GUIRunOnce section of
sysprep.inf, it is what we use to complete the setup of things that
must be done post-reseal. For example, put the program you want to
execute in C:\Windows\Temp (in this example, I'll use MyProg.exe) and
use something like the following:

[GUIRunOnce]
; Once the computer has rebooted and we log in, execute these commands
;
Command0="C:\WINDOWS\Temp\MyProg.exe"

I'm pretty sure you can run multiple commands by using Command1, etc.,
but I've never done it. As an alternative, you could use a batch file
to kick off as many commands as you like.

Hope this helps!
Click to expand...


We had some probs with using this method with our syspreps, worked well
most of the time but did have some problems. Take a look at
"commandlines.txt" which you need to put into the sysprep/$oem$
directory. I think that you also need to have anything you're running
via this method in that directory also. This will run much earlier than
the guirunonce stuff and will avoid a number of problems by doing so,
but also may present different problems (for instance I don't think
network connectivity will be up by this point and so on).
 
Zaphod Beeblebrox said:
Barkley Bees said:
I am in the process of creating a new Windows XP image to support some new
hardware models we will be deploying. After I have the OS build completed
I will sysprep it and then capture it via imagex for deployment.

In addition to this there are a few vbs scripts we want to run when the
user is completing their install. We have the following scripts:

1. Add domain user to local admin group.
2. Set SMS site code to SMS client.
3. Set servername and sign-in name on Office Communicator.

My question is, is there anyway to automate these scripts running once
after the install completes? Appreciate any advice. Thank you.
Click to expand...
First, ignore the reply from Andrew E. - out of his ignorance he often
posts inaccurate, misleading, or just plain dangerous things.

Anyway. You might have a look at the GUIRunOnce section of sysprep.inf,
it is what we use to complete the setup of things that must be done
post-reseal. For example, put the program you want to execute in
C:\Windows\Temp (in this example, I'll use MyProg.exe) and use something
like the following:

[GUIRunOnce]
; Once the computer has rebooted and we log in, execute these commands
;
Command0="C:\WINDOWS\Temp\MyProg.exe"

I'm pretty sure you can run multiple commands by using Command1, etc., but
I've never done it. As an alternative, you could use a batch file to kick
off as many commands as you like.

Hope this helps!
Click to expand...

Thank you very much Zaphod. I will look into using this portion of the
sysprep answer file.
I found the following which should get me on my way:
http://technet.microsoft.com/en-us/library/cc961065.aspx
I look forward to testing it out.
 
Back
Top