Printable View
One of our users is having issues with logging on to his machine. After the login prompt appears, it takes an age to get to the desktop. A quick trip to Event Viewer tells me:
"Execution of GPO scripts has timed out and have been terminated. "
What's the best way to figure out at which policy the thing's freezing at?
Cheers.
The only way to check this other than adding and removing the GPOs one by one to see which is the culprit is to turn on user environment monitoring.
A good tool for this is Policy Reporter which you can find here in the Wiki.
Try this in user log in script, at the end of script.
gpresult /USER {USER LOG IN NAME} >c:\111.txt
(gpresult /USER john >c:\111.txt)
:)
I love you both and will be happy to bear your children.
Funny reply :DQuote:
I love you both and will be happy to bear your children.
You may also want to download GPMC if you're using Windows Server 2003 so you can see what policies are being applied.
Due to the fantastic nature of a managed service I don't have administrative access to the DC. :(
Well alternatively you can install it on an admin workstation (Windows XP). I've never tried not installing it on a DC but just a workstation, although it should be possible.
If you're using Windows Vista, you'd download GPMC 2.0.
You may also want to install the Windows Server 2003 Administrative Tools Pack too on Windows XP.
In saying that you will need administrative access on the workstation and of course to the DC. It must be so frustrating when you cannot access anything :(
Then it's the managed service companies problem - not yours. You can't be held responsible for something you have no control over.
Tell me about it. Just basic things like DHCP settings alterations to set up a boot server. There have been occasions where I've wanted to walk out in frustration.Quote:
Originally Posted by Michael