Order things startup in XP

[Jordan]

I use AD GPO to deploy a lot of software in MSI files. I also use RIS to

deploy Windows XP Pro. I also use WSUS to deploy all my Windows Updates.



My goal is to deploy XP with RIS, Office and a bunch of other apps with GPO

and fully patch the system as quick as possible. Right now when I use RIS

to setup my XP Clients they are able to install XP fully and on their first

boot after XP Setup they start getting all the apps I have setup via GPO's

managed software, but the last step is to apply all the patches



I downloaded a VBS that will start Windows Upate and download and install

all the waiting updates and then if the computer needs it, it will reboot

the computer. This works great. The thing I need to know is if the Windows

startup script (not user login script) runs before or after the GPO managed

software deployment and if it runs in WScript or CScript.



The reason being that I want to be sure things like Office and other

programs are installed first then the VBS script runs, because if the VBS

runs then issues the reboot and then the GPO managed software starts to

deploy it could cause problems. And I need to know if the startup script is

Cscript or Wscript so I know if I should remove some of the statements that

echo the output.

 

[Pegasus [MVP]]

"Jordan" wrote in message

news:#D$PR9ZDLHA.5476@TK2MSFTNGP06.phx.gbl...

> I use AD GPO to deploy a lot of software in MSI files. I also use RIS to

> deploy Windows XP Pro. I also use WSUS to deploy all my Windows Updates.

>

> My goal is to deploy XP with RIS, Office and a bunch of other apps with

> GPO and fully patch the system as quick as possible. Right now when I use

> RIS to setup my XP Clients they are able to install XP fully and on their

> first boot after XP Setup they start getting all the apps I have setup via

> GPO's managed software, but the last step is to apply all the patches

>

> I downloaded a VBS that will start Windows Upate and download and install

> all the waiting updates and then if the computer needs it, it will reboot

> the computer. This works great. The thing I need to know is if the

> Windows startup script (not user login script) runs before or after the

> GPO managed software deployment and if it runs in WScript or CScript.

>

> The reason being that I want to be sure things like Office and other

> programs are installed first then the VBS script runs, because if the VBS

> runs then issues the reboot and then the GPO managed software starts to

> deploy it could cause problems. And I need to know if the startup script

> is Cscript or Wscript so I know if I should remove some of the statements

> that echo the output.



By default, Windows uses wscript as its engine. Since this can be changed by

anyone you need to enforce then engine of your preference by invoking your

script explicitly with wscript.exe instead of just invoking the script file

itself. This method would remove any doubt.

 

[Jordan]

How about the order of things that start up. Does the startup script run

first or does the deployment of Managed Software via GPO start first?



Because Startup scripts are something that can be deployed via GPO my

assumption is that the Managed Software installations will happen first, but

I don't want to assume.



"Pegasus [MVP]" wrote in message

news:eSKmKMaDLHA.4636@TK2MSFTNGP02.phx.gbl...

>

>

> "Jordan" wrote in message

> news:#D$PR9ZDLHA.5476@TK2MSFTNGP06.phx.gbl...

>> I use AD GPO to deploy a lot of software in MSI files. I also use RIS to

>> deploy Windows XP Pro. I also use WSUS to deploy all my Windows Updates.

>>

>> My goal is to deploy XP with RIS, Office and a bunch of other apps with

>> GPO and fully patch the system as quick as possible. Right now when I

>> use RIS to setup my XP Clients they are able to install XP fully and on

>> their first boot after XP Setup they start getting all the apps I have

>> setup via GPO's managed software, but the last step is to apply all the

>> patches

>>

>> I downloaded a VBS that will start Windows Upate and download and install

>> all the waiting updates and then if the computer needs it, it will reboot

>> the computer. This works great. The thing I need to know is if the

>> Windows startup script (not user login script) runs before or after the

>> GPO managed software deployment and if it runs in WScript or CScript.

>>

>> The reason being that I want to be sure things like Office and other

>> programs are installed first then the VBS script runs, because if the VBS

>> runs then issues the reboot and then the GPO managed software starts to

>> deploy it could cause problems. And I need to know if the startup script

>> is Cscript or Wscript so I know if I should remove some of the statements

>> that echo the output.

>

> By default, Windows uses wscript as its engine. Since this can be changed

> by anyone you need to enforce then engine of your preference by invoking

> your script explicitly with wscript.exe instead of just invoking the

> script file itself. This method would remove any doubt.

>