| Author | Messages | |
dmarelia
Posts:394
 | | 12/16/2009 3:48 PM |
| Yea, PDC emulator. So, if all DCs are the same SYSVOL version then probably all are in a consistent state, albeit different from AD (which generally shouldn't be the case). My guess is that you had a failed change somewhere along the line. Given that your problem is not related to this GPO however, I don't know that its your issue.
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Shane Williford
Sent: Tuesday, December 15, 2009 11:33 AM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] PC - Lockup/Active Desktop issue
"server8"...I assume you mean PDC Emulator?
Shane M. Williford
Systems Administrator
VCP, MCSE, MCSA Sec, Sec+, Net+, A+
Mazuma Credit Union
9300 Troost
Kansas City, MO 64131
xxxxxxxxxxxxxxxx<mailto:xxxxxxxxxxxxxxxx>
816-361-4194 x6012
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia
Sent: Tuesday, December 15, 2009 1:22 PM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] PC - Lockup/Active Desktop issue
Looks like your DDCP is not consistent, however, it may not be a problem per-se. Which of those DCs below is the PDC?
Darren
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Shane Williford
Sent: Tuesday, December 15, 2009 11:11 AM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] PC - Lockup/Active Desktop issue
Ooops...I lied...everything did come back ok EXCEPT the following:
============================================================
Policy {6AC1786C-016F-11D2-945F-00C04FB984F9}
Error: Version mismatch on server1.mazuma.org, DS=1153, sysvol=1134
Friendly name: Default Domain Controllers Policy
Error: Version mismatch on server2.mazuma.org, DS=1153, sysvol=1134
Error: Version mismatch on server3.mazuma.org, DS=1153, sysvol=1134
Error: Version mismatch on server4.mazuma.org, DS=1153, sysvol=1134
Error: Version mismatch on server5.mazuma.org, DS=1153, sysvol=1134
Error: Version mismatch on server6.mazuma.org, DS=1153, sysvol=1134
Error: Version mismatch on server7.mazuma.org, DS=1153, sysvol=1134
Error: Version mismatch on server8.mazuma.org, DS=1153, sysvol=1134
Error: Version mismatch on server9.mazuma.org, DS=1153, sysvol=1134
Error: Version mismatch on server10.mazuma.org, DS=1153, sysvol=1134
Error: Version mismatch on server11.mazuma.org, DS=1153, sysvol=1134
Details:
------------------------------------------------------------
Thanks 
Shane M. Williford
Systems Administrator
VCP, MCSE, MCSA Sec, Sec+, Net+, A+
Mazuma Credit Union
9300 Troost
Kansas City, MO 64131
xxxxxxxxxxxxxxxx<mailto:xxxxxxxxxxxxxxxx>
816-361-4194 x6012
From: Shane Williford
Sent: Tuesday, December 15, 2009 1:08 PM
To: 'xxxxxxxxxxxxxxxx'
Subject: RE: [gptalk] PC - Lockup/Active Desktop issue
I was finally able to run the GPOtool and everything came back "OK". I checked the permissions for the gpt.ini file in the below referenced UID GP and it was fine. I'm stumped!
Shane M. Williford
Systems Administrator
VCP, MCSE, MCSA Sec, Sec+, Net+, A+
Mazuma Credit Union
9300 Troost
Kansas City, MO 64131
xxxxxxxxxxxxxxxx<mailto:xxxxxxxxxxxxxxxx>
816-361-4194 x6012
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Shane Williford
Sent: Wednesday, December 09, 2009 12:58 PM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] PC - Lockup/Active Desktop issue
Ilene...I'm not entirely sure what netmon would do for this...could you elaborate as to why to run that tool?
Darren...my director actually created the screensaver. What he did was have several .jpg files (photos for security awareness) referenced to 'scroll' as a slideshow, which can't be used in the current screensaver config in GP. I'm not sure about GPP as I don't have that implemented in my org yet (but working on getting this in place). It's not really bad. The only bad part about it is users need admin rights to modify registry settings, which is where the batch file came into play. (using the free tool "lsrunas")
I haven't run the GPOtool yet. I'll try that to see what it says. I did run dcdiag /e on my DC and everything came back normal (DNS, Replication/FRS, etc), so I know there isn't a replication issue.
Thanks.
Shane M. Williford
Systems Administrator
VCP, MCSE, MCSA Sec, Sec+, Net+, A+
Mazuma Credit Union
9300 Troost
Kansas City, MO 64131
xxxxxxxxxxxxxxxx<mailto:xxxxxxxxxxxxxxxx>
816-361-4194 x6012
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia
Sent: Wednesday, December 09, 2009 12:38 PM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] PC - Lockup/Active Desktop issue
Shane-
Have you run GPOTool.exe for that GPO referenced in the error to see if its synchronized across all DCs? If you are having FRS replication problems then GPOTool.exe should show that. That would be the first step. Just as an aside, do you really need to use a logon script to configure their screensavers? Is the built-in screensaver control not sufficient? It just seems pretty convoluted for something like screensaver management.
Darren
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Rosner, Ilene
Sent: Wednesday, December 09, 2009 8:37 AM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] PC - Lockup/Active Desktop issue
Try the netdom reset command.
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Shane Williford
Sent: Wednesday, December 09, 2009 11:30 AM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] PC - Lockup/Active Desktop issue
All/Darren,
I could really use some help on this one, and I think my problem "may" stem from an error I've noticed in the App Evt Log (reattached for reference)
[cid:image001.png@01CA7D92.8C454E90]
At first I thought it was just 1 user having this happen to, but now I believe it's on several PCs. Let me give a little background. I implemented some settings in a current GP for a screensaver. How I created this part of the GP was -> a batch file in the login script section, that then calls a .reg file that's in the netlogon directory that configures all the settings for this screensaver (which is a slideshow type screensaver). The reason for the batch file is because it calls an utility that enables local admin rights. When I tested it out, it was its own GP and no problems were found, so I added the settings to a current GP. About 1-2wks after I implemented this, I've had a handful of users call with a problem with their desktop -> white background/Active Desktop message on the desktop, as well as their PC's locking up and saying stuff like "out of system resources", etc. Well, we have the desktop/display locked down so users can't change their wallpaper...it's only the default blue (I had config'd in Users Config: Enable Active Desktop, Prohibit Changes, as well as Active Desktop Wallpaper config'd with a bogus image so backgrounds were only set to the default blue color). I also config'd to Prevent Changing Wallpaper. When I began receiving these calls about the Active Desktop issue I obviously assumed something with the screensaver. To test to see if this was my problem, I removed the script (bat file) from the login script part of the GP (altho the file is still in the login script directory in the GPO...I didn't delete the file itself). That didn't seem to fix things for me. So, I began playing with Active Desktop settings in my GP. I unconfigured everything on the Active Desktop side and it still didn't resolve this issue. I then unconfigured the 'prevent changing wallpaper' setting and made sure "None" was set on the Desktop tab and the white Active Desktop background went away. I also noticed on 1 user's PC that under the Customize Desktop setting in display properties -> Web tab, there was a UNC path to an image file and I have NO idea how it got there. When I deleted/removed it, I went back in to that tab and it reappeared. WEIRDNESS. So, my question is...has anyone seen or dealt with this kind of mess before and, if so, how did you resolve it? I checked permissions on this GPO and they are ok, so I'm not sure there is a permission issue, unless I'm getting that error above due to permissions with something in the GPO, but not even sure where to begin to look for that.
I did a little research and saw this KB: http://support.microsoft.com/kb/314494. Maybe there's something wrong with DFS in our environment? In addition, I saw this: http://forums.techarena.in/active-directory/734454.htm, which advises to run a DFSutility (this suggestion is for a server, but these errors I'm seeing are on a client workstation). So, not sure if this even will take care of my Active Desktop issue, but I guess it may be at minimum a beginning step to try?
Any help would most greatly be appreciated.
Thanks.
Shane M. Williford
Systems Administrator
VCP, MCSE, MCSA Sec, Sec+, Net+, A+
Mazuma Credit Union
9300 Troost
Kansas City, MO 64131
xxxxxxxxxxxxxxxx
816-361-4194 x6012
-----Original Message-----
From: Shane Williford
Sent: Monday, December 07, 2009 8:27 AM
To: Christian Marcussen
Subject: FW: Eric's PC - Lockup
Christian...below is what I recv'd in reply from Darren Mar-Elia...GP MVP.
Shane M. Williford
Systems Administrator
VCP, MCSE, MCSA Sec, Sec+, Net+, A+
Mazuma Credit Union
9300 Troost
Kansas City, MO 64131
xxxxxxxxxxxxxxxx
816-361-4194 x6012
________________________________________
From: xxxxxxxxxxxxxxxx [xxxxxxxxxxxxxxxx] On Behalf Of Darren Mar-Elia [xxxxxxxxxxxxxxxx]
Sent: Thursday, December 03, 2009 5:00 PM
To: xxxxxxxxxxxxxxxx
Subject: RE: [gptalk] PC - Lockup
Shane-
The GPT.INI file is the base version file within the SYSVOL portion of a GPO. That error typically can occur for any number of reasons, including network problems, DNS problems or permission problems on the GPO, to name a few. What's probably happening is that a background GP refresh is occurring and that is causing this error to appear. Hard to say whether that is causing the lockup or is being impacted by the lockup. If its only one machine, I suspect its probably the machine or user account rather than the GPO.
Darren
****
Darren Mar-Elia
CTO & Founder
SDM Software, Inc.
"The Group Policy Experts"
www.sdmsoftware.com
Founder- www.gpoguy.com - The Group Policy Resource Site
Blog: www.sdmsoftware.com/blog
Twitter: www.twitter.com/grouppolicyguy
Group Policy Automation Engine - 2009 Windows IT Pro Magazine Editors Choice Winner for Best Active Directory and Group Policy Product
-----Original Message-----
From: xxxxxxxxxxxxxxxx [mailto:xxxxxxxxxxxxxxxx] On Behalf Of Shane Williford
Sent: Thursday, December 03, 2009 2:43 PM
To: xxxxxxxxxxxxxxxx
Subject: [gptalk] FW: PC - Lockup
All, I have a user with issues of his PC freezing up... I did find this error in his system log about the same time he began having issues. Do you guys/gals know what the gpt.ini file is and if this error would cause a PC to freeze?
Thanks!
Shane Williford
VCP, MCSE, MCSA Sec, Sec+, Net+, A+
Systems Administrator
Mazuma Credit Union
Kansas City, MO 64131
xxxxxxxxxxxxxxxx<mailto:xxxxxxxxxxxxxxxx>
________________________________
Notice: The information transmitted in this e-mail may contain confidential and/ or legally privileged information intended only for the use of the individual(s) named above. Review, use, disclosure, distribution, or forwarding of this information by persons or entities other than the intended recipient(s) is prohibited by law and may subject them to criminal or civil liabilities. Statements and opinion expressed in this e-mail may not represent those of Mazuma Credit Union. All e-mail communications through Mazuma's corporate email system are subject to archiving and review by someone other than the recipient. If you have received this communication in error, please notify the sender immediately and delete/destroy any and all copies of the original message from any computer or network system.
UHS Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution of this information is prohibited, and may be punishable by law. If this was sent to you in error, please notify the sender by reply e-mail and destroy all copies of the original message.
| | | |
|
|