- Mar 13, 2007
- 1,100
- 0
- 76
So im trying to add a new domain controller to our network so I can replace our aging one.
The old domain server is 2003, the new one is server 2008 r2. After I installed the OS on the new server I ran dcpromo to add it as a domain controller and everything seemed to work fine. The problem im having is that the sysvol and netlogon shares are not getting setup correctly, im getting these errors in the event log for the new server. Windows server is the DC running 2003, windowsserver2 is running 2008 r2.
File Replication Service is initializing the system volume with data from another domain controller. Computer WINDOWSSERVER2 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
The File Replication Service successfully added this computer to the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Information related to this event is shown below:
Computer DNS name is "WINDOWSSERVER2.projectreality.local"
Replica set member name is "WINDOWSSERVER2"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
The File Replication Service successfully added the connections shown below to the replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Outbound to "windowsserver.projectreality.local"
Inbound from "windowsserver.projectreality.local"
The File Replication Service is having trouble enabling replication from WINDOWSSERVER to WINDOWSSERVER2 for c:\windows\sysvol\domain using the DNS name windowsserver.projectreality.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name windowsserver.projectreality.local from this computer.
[2] FRS is not running on windowsserver.projectreality.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
When I do net share sysvol is not showing up as being shared, these are the only errors im seeing in the logs, I ran dcdiag on both computers windowsserver passed all the tests. Windows server 2 failed the netlogon test, and I got an error saying DsgetDCname only gave windowserver as being a domain controller. Any advice?
The old domain server is 2003, the new one is server 2008 r2. After I installed the OS on the new server I ran dcpromo to add it as a domain controller and everything seemed to work fine. The problem im having is that the sysvol and netlogon shares are not getting setup correctly, im getting these errors in the event log for the new server. Windows server is the DC running 2003, windowsserver2 is running 2008 r2.
File Replication Service is initializing the system volume with data from another domain controller. Computer WINDOWSSERVER2 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
The File Replication Service successfully added this computer to the following replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Information related to this event is shown below:
Computer DNS name is "WINDOWSSERVER2.projectreality.local"
Replica set member name is "WINDOWSSERVER2"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"
The File Replication Service successfully added the connections shown below to the replica set:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
Outbound to "windowsserver.projectreality.local"
Inbound from "windowsserver.projectreality.local"
The File Replication Service is having trouble enabling replication from WINDOWSSERVER to WINDOWSSERVER2 for c:\windows\sysvol\domain using the DNS name windowsserver.projectreality.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name windowsserver.projectreality.local from this computer.
[2] FRS is not running on windowsserver.projectreality.local.
[3] The topology information in the Active Directory Domain Services for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
When I do net share sysvol is not showing up as being shared, these are the only errors im seeing in the logs, I ran dcdiag on both computers windowsserver passed all the tests. Windows server 2 failed the netlogon test, and I got an error saying DsgetDCname only gave windowserver as being a domain controller. Any advice?
Facebook
Twitter