Windows cannot access the file gpt.ini for GPO

[Michael Vincent Rapada]

Michael Vincent Rapada [http://community.zenoss.org/people/vincentrapada] created the discussion

"Windows cannot access the file gpt.ini for GPO"

To view the discussion, visit: http://community.zenoss.org/message/74112#74112

--------------------------------------------------------------
Hi,

After adding a new device (Windows Server 2003 R2). An event message appeared.

*Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=alnova,DC=accenture,DC=com. The file must be present at the location <\\alnova.accenture.com\sysvol\alnova.accenture.com\Policies\{31B2F340-0*

Please help me resolving and knowing what this event message means.

Thanks!

--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74112#74112]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jmp242]

jmp242 [http://community.zenoss.org/people/jmp242] created the discussion

"Re: Windows cannot access the file gpt.ini for GPO"

To view the discussion, visit: http://community.zenoss.org/message/74117#74117

--------------------------------------------------------------
That's actually a Windows event log entry that Zenoss has captured to notify you about. It looks like you have a GPO that is broken in your AD. You likely need to go into SYSVOL, locate that GUID and figure out which GPO that is, and then re-create it, restore from backup, or the like. Microsoft has details on using a vbscript to translate GUID to GPO name:
http://support.microsoft.com/kb/216359 http://support.microsoft.com/kb/216359

--
James Pulver
ZCA Member
CLASSE Computer Group
Cornell University
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74117#74117]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[Michael Vincent Rapada]

Michael Vincent Rapada [http://community.zenoss.org/people/vincentrapada] created the discussion

"Re: Windows cannot access the file gpt.ini for GPO"

To view the discussion, visit: http://community.zenoss.org/message/74120#74120

--------------------------------------------------------------
Hi,

Thank you for your answer.
Is there any indicator in the event log that shows that Zenoss detected it from windows side? What I am trying to say is that, the event is not related to the configuration of Zenoss to the devices that I added?

Thanks!
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74120#74120]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]

[jmp242]

jmp242 [http://community.zenoss.org/people/jmp242] created the discussion

"Re: Windows cannot access the file gpt.ini for GPO"

To view the discussion, visit: http://community.zenoss.org/message/74125#74125

--------------------------------------------------------------
The event is not related to the configuration of Zenoss. Look at the agent. "zeneventlog" is the part of zenoss that reads the Windows Event Log...

--
James Pulver
ZCA Member
CLASSE Computer Group
Cornell University
--------------------------------------------------------------

Reply to this message by replying to this email -or- go to the discussion on Zenoss Community
[http://community.zenoss.org/message/74125#74125]

Start a new discussion in zenoss-users at Zenoss Community
[http://community.zenoss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2003]