Jump to content

Recommended Posts

Posted

Bit of a strange one I have a GP for our 2 simple install that contains about 20+msi's

All assigned in the computer config software settings. GP is at domain level ( was lazy and didnt know better when I started)

 

Security filtering I have Authenticated users.

 

ran gpupdate / force a few times on local computer, logged on as domain admin restarted * 5 times still nothing deployed.

This is on a windows 8.1 surface pro

 

I have 2 simple on other surface pro's dont know why this one is different

Posted

Is the operation timing out processing the GPO? What does the error log say about matters?

 

I'm not an expert in GPO, but I've never put more than 5 in a GPO without their being some sort of detrimental effect.

Posted
Could be caused by a slow link. If they are applying policy on very poor A/G wireless then the policy will most likely be skipped. You can change what is determined as "slow" in the policy as well.
Posted
Shouldn't the filtering be a computer-based one? I normally use Domain Computers unless it needs more precise targeting.

 

As you say, unless it needs more precise targeting... I've always just used authenticated users because as far as I was aware a computer account in AD was an authenticated user.

  • Thanks 1
Posted
rsop is picking up an error. Software installation did not complete install is pending and awaiting reboot. gp will attempt to apply the settings the next time the computer is restarted.
Posted
As you say, unless it needs more precise targeting... I've always just used authenticated users because as far as I was aware a computer account in AD was an authenticated user.

 

You're right - that will save me a bit of time in future, then!

Posted
rsop is picking up an error. Software installation did not complete install is pending and awaiting reboot. gp will attempt to apply the settings the next time the computer is restarted.

 

I'd have a butchers in the Event Viewer then to see why it is failing.

Posted

Ended up adding a new temp GP that set

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.

This finally gave the machine time to get it installed

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...