• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 22
  • Last Modified:

AD Migration policies not moving - 2003 to 2008 R2

I am migrating to new Domain Controllers.  The old controller was called SAA-2007 and is a Windows 2003 Servers.  The new servers are called DC1 and DC2.

I have been able to change the FSMO roles to DC1 but the domain is till looking to the old server for the policy files.  I know this becasue if I shut down the server I can no longer edit the policy files.

I've pickted up that the domain controller stores the policy files in \\<servername>\SYSVOL\<domainname>.  I can find this on the old server but not on DC1 or DC2.

I need to get the policyes onto the new servers so I can shut down the old one.
0
edawlem
Asked:
edawlem
  • 2
1 Solution
 
Mike KlineCommented:
have you verified that replication is working between the two servers, is  sysvol being shared out on the new DC?

What errors are you seeing in your logs?

Thanks

Mike
0
 
edawlemAuthor Commented:
I think I found the source of the problem.  The original DC only had external DNS servers listed (I just inherited this system).  I've fixed that and moved the operations master roles back to the original DC.

SYSVOL is not being shared from the new domain controllers.

I get this error:

Event Type:	Information
Event Source:	NTDS Replication
Event Category:	Replication 
Event ID:	1955
Date:		8/23/2012
Time:		8:51:20 PM
User:		NT AUTHORITY\ANONYMOUS LOGON
Computer:	SAA-2007
Description:
Active Directory encountered a write conflict when applying replicated changes to the following object. 
 
Object: 
DC=_ldap._tcp.dc,DC=_msdcs.SAA.net,CN=MicrosoftDNS,DC=ForestDnsZones,DC=SAA,DC=net 
Time in seconds: 
0  
 
Event log entries preceding this entry will indicate whether or not the update was accepted. 
 
A write conflict can be caused by simultaneous changes to the same object or simultaneous changes to other objects that have attributes referencing this object. This commonly occurs when the object represents a large group with many members, and the functional level of the forest is set to Windows 2000. This conflict triggered additional retries of the update. If the system appears slow, it could be because replication of these changes is occurring. 
 
User Action 
Use smaller groups for this operation or raise the functional level to Windows Server 2003.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

0
 
edawlemAuthor Commented:
And
Event Type:	Warning
Event Source:	MSDTC
Event Category:	SVC
Event ID:	53258
Date:		8/23/2012
Time:		9:13:04 PM
User:		N/A
Computer:	SAA-2007
Description:
MS DTC could not correctly process a DC Promotion/Demotion event. MS DTC will continue to function and will use the existing security settings. Error Specifics: %1

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0

Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now