All, Further development, it is not a DNS/DFS
issue seems as though some attribute in my XP Workstation Baseline GPO is causing
this issue, other workstations in the domain can access the \\FQDN\Sysvol. Will
try and nut it out further... James From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
All, AD GPO issues. Have the dreaded Event ID 1030 &
1058 issues. DC's Windows 2003 and clients XPSP1. DC's had the issue but I was
able to resolve this using: dfsutil /PurgeMupCache, have been clean for a week
now...XPSP1 clients however still have the error messages and I have done the
following on the server side: *
Made sure DFS Service is
running. *
Made sure TCP/IP NetBIOS
Service is running. On clients: ·
Made sure TCP/IP NetBIOS
Service is running. ·
Made sure WMI Performance
Adaptor Service is running. In addition to the above ran NETDIAG and tested
replication on the DC's (no errors). Ran GPRESULT from the XPSP1 workstation
which implied that the policies were applied however if I run a GPUDATE /FORCE
from the same workstation the 1030 and 1058 errors return...It always seems to
be on the one policy which is my Global User Settings one. I deleted the old
policy and re-created a new one and get the same error to what is in essence
the same policy but different GUID. I also ran Group Policy Results from the
GPMC which insinuated that the network location cannot be reached. I also tried
the patch in Q329170 and as a last resort even installed XPSP2 on one of the
workstations. One thing I have not done is change our DC GPO below settings all
to disabled: Network Client: Digitally Sign Client Communications
Always - Disabled Network Client: Digitally Sign Client Communications
(If Server Agrees) - Enabled Network Server: Digitally Sign Client Communications
Always - Disabled Network Server: Digitally Sign Client Communications
(If Server Agrees) - Enabled Not sure if it is a DNS/DFS issue, if I run \\FQDN\Sysvol from the XPSP1 workstation I get
a network location cannot be reached error however if I do this from the DNS
server which is a DC I get a return...can ping the FQDN and NetBIOS names to
the right IP on the XPSP1 workstations...Any help would be appreciated... Event Type: Error Event Source: Userenv Event Category: None Event
ID: 1030 Date:
18/08/2004 Time:
3:52:29 PM User:
NT AUTHORITY\SYSTEM Computer:
BRIL-DEV-3 Description: Windows cannot query for the list of Group Policy
objects. A message that describes the reason for this was previously logged by
the policy engine. For more information, see Help and Event Type: Error Event Source: Userenv Event Category: None Event
ID: 1058 Date:
18/08/2004 Time:
3:52:29 PM User:
NT AUTHORITY\SYSTEM Computer:
BRIL-DEV-3 Description: Windows cannot access the file gpt.ini for GPO
cn={6A9D1B3F-6298-46CA-B2E4-2F2DC898BF66},cn=policies,cn=system,DC=test,
DC=com. The file must be present at the location
<\\upstream.originenergy.com.au\SysVol\upstream.originenergy.com.au\Policies\{6A9D1B3F-6298-46CA-B2E4-2F2DC898BF66}\gpt.ini>.
(The network location cannot be reached. For information about network
troubleshooting, see Windows Help. ). Group Policy processing aborted. For more information, see Help and James Blair |
- [ActiveDir] GPO Issue... james . blair
- james . blair