Hello!

Can anyone give us some suggestions on the fallowing.

We have a few problems with a Windows 2000 domain. We have just added a
Windows Server 2003 to it with all the preps. that was needed! Didn't
notes any errors when we added the Windows Server 2003 server to the
domain.

We get the following errors in the Event Logg:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1058
Date: 01.02.2005
Time: 11:24:53
User: NT AUTHORITY\SYSTEM
Computer: VAKT1
Description:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-
945F-00C04FB984F9},CN=Policies,CN=System,DC=SD-Anlegg,DC=nss. The file
must be present at the location <\\SD-Anlegg.nss\sysvol\SD-Anlegg.nss
\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>.
(Configuration information could not be read from the domain controller,
either because the machine is unavailable, or access has been denied. ).
Group Policy processing aborted.

And!

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1030
Date: 01.02.2005
Time: 11:24:53
User: NT AUTHORITY\SYSTEM
Computer: VAKT1
Description:
Windows cannot query for the list of Group Policy objects. Check the
event log for possible messages previously logged by the policy engine
that describes the reason for this.

When we try to open Group Policies we get Access is denied on the 2003
server and The system cannot fined the path specified on the 2000 sever.
We had to regenerate the GP. Now we can open the PG on the 2000 server,
but not on the 2003 server.

Tried to uninstall 2003 server form the domain, but it only gives me an
error message. The message is as follows:

The operation failed because:
Active Directory could not transfer the remaining data in the directory
partition CN=Schema,CN=Configuration,DC=domain,DCdomain to domain
controller DC.domain.domain.

"Access is deniade"

It also asks for a user name and password to the Active Directory! Know
mater what we used as user name it did not accept it!

Trond A. Tømte wrote:
are replicating with your partners. I use REPLMON because it's easy,
but you can use REPADMIN or another tool if you like. From the sounds
of the error messages, your not able to replicate Group Policy from
VAKT1 and usually this is indicative of replication problems.

--
Legal Disclaimer:
This posting is provided "AS IS" with no warranties, and confers no
rights. Use of included script samples are subject to the terms
specified at http://www.microsoft.com/info/cpyright.htm Please do not
send e-mail directly to this alias. This alias is for newsgroup purposes
only.

Hi,

Had the same issue some time back, it was not a replication issue but a
error in the group policy being applied to the workstation. I used a
comparison tool with windows 2003 and it pointed me to the failed item
in the group policy.

Demoting a server would not resolve the issue, you could also dcpromo
/forceremoval or even edit the AD with ADSIEDIT.

Cheers

In article <1107466332.487785.3090@z14g2000cwz.googlegroups.c om>,
quakesh@msn.com says...
Hello!

You where right. I Used RSoP and found the problem! There is an "x" over
the Computer Configuration. I found the following error under properties
and error information:


8. februar 2005 12:57:12

Group Policy Infrastructure failed due to the error listed below.
Logon failure: the user has not been granted the requested logon type at
this computer.

Note: Due to the GP Core failure, none of the other Group Policy
components processed their policy. Consequently, status information for
the other components is not available.
Additional Information:
Windows cannot access the file gpt.ini for GPO CN={31B2F340-016D-11D2-
945F-00C04FB984F9},CN=Policies,CN=System,DC=SD-Anlegg,DC=nss. The file
must be present at the location <\\SD-Anlegg.nss\sysvol\SD-Anlegg.nss
\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\gpt.ini>. (Logon
failure: the user has not been granted the requested logon type at this
computer. ). Group Policy processing aborted.

Windows cannot query for the list of Group Policy objects. Check the
event log for possible messages previously logged by the policy engine
that describes the reason for this.


The problem now is to fix it! Any ideas???