Windows

Hi,
I'm guessing that you are a victim of slow link detection. When the group policy, for either machine or user, begins to be processed a test is done of the network response times. Anything under 500kbs is flagged as a slow link. If a slow link is detected, the gpo will literally drop parts of the policy. The security settings are always applied, but things like scripts and ie maintenance are dropped. The idea is that remote users don't suffer overly long logon \ startup times. this behaviour can be controlled either by tweaking the slow link detections settings to make it accept lower network response times as acceptable, or by turning off slow link detection altogether. You can do this for either the user or computer objects in thegpo via the admin templates \ system \ group policy area. Note that by default the slow link detection setting shows as 'not configuered' - somewhat confusingly this means that it is active with default settings, rather than not active.

A bit more info... After testing today, have found that the scripts run only after every other boot/logoff. After bringing the problem PC to HQ, the scripts run flawlessly...so I think you are onto something here. Do you know what the default settings are if the SLow Link setting is not configured? Also, do you know anything about the "Maximum Wait time for Group Policy Scripts"? The setting is defaulted to NOT CONFIFURED as well, but looks like the default is 600. Also, our connection varies b/ween 70-600ms. Average is approx 170ms.

hi,

just copy the path where the Scripts are stored, onto the other DC in the remote sites. Then it sould work.

regards

Frobo

This question was closed by the author