Deploying software through AD means i have to log on!

[HodgeHi]

Hello,

 

I don't know if this is right but it sure as hell don't sound like it...

I have just started to dabble in the deployment of software through AD. I have set up a GPO specifically for this and linked it to the main OU which has the OUs for the rooms where the PCs are kept.

 

I have managed to get the software out to one computer since configuring the policy and thought it odd that it hasn't deployed to the rest. I started restarting the pcs to allow them to start installing the software during start up but they didn't so i logged into one and just restarted the machine, nothing else was touched. Once restarted the managed software started to deploy.

 

This was the case for each machine that i logged into.

 

Am i missing something?

[MK-2]

Maybe logging in forced a refresh of the machine_policy which saw that software is waiting to be installed, and next reboot it did it?

 

I don't know, it sounded logical in my head but its probably wrong!

[contink]

You probably have your GPO to only apply to authenticated users so that forces you to login first..

 

I can't remember what you have to change it to but playing with that aspect of settings should help

[ajbritton]

Assuming you have XP workstations, it can take 3 boot cycles before managed software installations take place because of the way XP attempts to get the logon box up before even starting the network. Roughly, here is what happens.

 

1 - You assign the software in AD

2 - You reboot a PC. It refreshes the machine policy.

3 - You reboot the PC again. It notices that there is some software to install and forces a synchronous boot

4 - You reboot the PC AGAIN and it finally installs the software.

 

If you look in the event logs, you should see messages relating the application installation which may help you figure out what is going on.

 

I use a group policy setting which forces 'wait for network at computer startup'.

[djm968]

Type gpupdate /force at the command prompt on the XP client to refresh the policy. You should be prompted to reboot.

[ajbritton]

I use the following form of GPUPDATE;

 

GPUPDATE /SYNC /FORCE /BOOT

 

This will force a synchronous boot.

[alonebfg]

i have found the same problem it only does it if i log in as admin and if i let the cmd promt to restart it it does not work i have to restart as admin. i can gpupdate /force as much as i like it dont work unless i restart as admin.

[ajbritton]

Anything in the event logs?

 

If you really want to know what is going on with Group Policy, then you need to install Policy Reporter on the server, configure verbose logging on a PC which exhibits the problem, do a 'GPUPDATE /sync /force /boot', then capture the log from the PC using Policy Reporter on the server. This will give you a blow by blow account of everything that happens GP related on the PC.