How to make logon wait for startup scripts to finish

[mrstrong]

Hi,

 

I'm trying to deploy office 2010 via a group policy startup script as described here

PeteNetLive - KB0000464 - Deploying Office 2010 via Group Policy

 

However when a PC boots up it just goes straight to the login screen.

 

I can login and see (e.g. via process explorer) that setup.exe is still running

The .bat startup script calls

start /wait %DeployServer%\setup.exe /config %ConfigFile%

After about 20 minutes the PC just reboots and the .bat logs error code 1641 (ERROR_SUCCESS_REBOOT_ INITIATED).

After logging in again office 2010 seems to have been installed ok.

 

If I'm rolling this out to lots of PCs I want it to install fully before a user can login

(i.e. they will have to wait for 20 minutes!) as once they're logged in they could e.g. start word 2003 and mess up the install ?

 

So how can I force the startup scripts to finnish before the logon dialog is available ?

 

Thanks

[MattDLEA]

Dont know if this is on the right lines or not but I had to do this yesterday in a GP

Think they were both in the computer settings

Always wait for the network at computer startup and logon as disabled

Specify start up policy processing wait time enabled and set to 45 seconds.

[mrstrong]

Thanks,

I thought "always wait" should be enabled to "force synchronous processing"

This is what I have in the GPO but it appears to make no difference, i.e. PC boots straight up

to login box:

 

[mrstrong]

bump :-(

 

anyone got any further thoughts/ideas on this?

 

I've so far done about 20 office installs "manually"

 

I also need to deploy adobe air also probably via a startup script so I'd really like to get to the bottom

of this.

[Stuclark]

There's a setting in GP for synchronous / asynchronous execution of GP elements - make sure your script is running as a GP element, then enable synchronous execution - that will force the next GP element to wait for completion of the previous one

[mrstrong]

There's a setting in GP for synchronous / asynchronous execution of GP elements - make sure your script is running as a GP element, then enable synchronous execution - that will force the next GP element to wait for completion of the previous one

 

Sounds interesting, have you got any more info / links?

Can't see anything about "GP element" on technet