anthonyvmartin
asked on
How do I remove SBS 2003 server and promote Server 2003 to have Active Directory
I have a domain with a SBS 2003 server and a Enterprise Server 2003 that will not become an Active Directory Server.
I need to remove the old SBS 2003 server from the domain, and the only thing that looks like stopping me demoting/removing the SBS2003 box is the the SYSVOL is not shared or populated.
In the event logs I get this;
NTFRS event id 13549
The File Replication Service is unable to replicate from a partner computer because the event time associated with the file to be replicated is too far into the future. It is 30 minutes greater than the current time. This can happen if the system time on the partner computer was set incorrectly when the file was created or updated. To preserve the integrity of the replica set this file update will not be performed or propagated further.
The file name is: "Policies"
The connection to the partner computer is:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\DMC-SERVER\C1D1A4A1
Note: If this time difference is close to a multiple of 60 minutes then it is likely that this file may have been created or updated on the partner computer while the computer was set to the incorrect time zone when its computer time was initially set. Check that the timezone and time are correctly set on the partner computer.
Both servers are on the same time zone and time sync together.
I dcpromoted the Server 2003 box to remove active directory and then re dcpromo the server 2003 box and 10 minutes later I still get this.
How do I manually force the Server 2003 box to be have FSMO as I urgently need to do a SCHEMA master change for the email system.?
How to I just disconnect the SBS server and have an active directory on the 2003 SERVER?
What do I need to do if I turn off the SBS server and have Active Directory.?
I need to remove the old SBS 2003 server from the domain, and the only thing that looks like stopping me demoting/removing the SBS2003 box is the the SYSVOL is not shared or populated.
In the event logs I get this;
NTFRS event id 13549
The File Replication Service is unable to replicate from a partner computer because the event time associated with the file to be replicated is too far into the future. It is 30 minutes greater than the current time. This can happen if the system time on the partner computer was set incorrectly when the file was created or updated. To preserve the integrity of the replica set this file update will not be performed or propagated further.
The file name is: "Policies"
The connection to the partner computer is:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\DMC-SERVER\C1D1A4A1
Note: If this time difference is close to a multiple of 60 minutes then it is likely that this file may have been created or updated on the partner computer while the computer was set to the incorrect time zone when its computer time was initially set. Check that the timezone and time are correctly set on the partner computer.
Both servers are on the same time zone and time sync together.
I dcpromoted the Server 2003 box to remove active directory and then re dcpromo the server 2003 box and 10 minutes later I still get this.
How do I manually force the Server 2003 box to be have FSMO as I urgently need to do a SCHEMA master change for the email system.?
How to I just disconnect the SBS server and have an active directory on the 2003 SERVER?
What do I need to do if I turn off the SBS server and have Active Directory.?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi
i am going throu the dcdiag report. in the interim please enable ntfrs service from the services mmc and check inform whether if it runs succesfully. in case of error send me the error details from the event log
i am going throu the dcdiag report. in the interim please enable ntfrs service from the services mmc and check inform whether if it runs succesfully. in case of error send me the error details from the event log
ASKER
Every 30 Minutes I get;
Event Id 13051
The File Replication Service is starting.
Event ID 13566
File Replication Service is scanning the data in the system volume. Computer DMC-SERVER cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the scanning process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.
Event ID 13549
The File Replication Service is unable to replicate from a partner computer because the event time associated with the file to be replicated is too far into the future. It is 30 minutes greater than the current time. This can happen if the system time on the partner computer was set incorrectly when the file was created or updated. To preserve the integrity of the replica set this file update will not be performed or propagated further.
The file name is: "Policies"
The connection to the partner computer is:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\DMC-SERVER\C1D1A4A1
Note: If this time difference is close to a multiple of 60 minutes then it is likely that this file may have been created or updated on the partner computer while the computer was set to the incorrect time zone when its computer time was initially set. Check that the timezone and time are correctly set on the partner computer.
Event ID 13502
The File Replication Service is stopping.
Event ID 13503
The File Replication Service has stopped.
I have the time zones identical and I have sync the clock aganst each other.
Help urgently required as the SBS powered down this morning and users can not login.
Event Id 13051
The File Replication Service is starting.
Event ID 13566
File Replication Service is scanning the data in the system volume. Computer DMC-SERVER cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the scanning process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.
Event ID 13549
The File Replication Service is unable to replicate from a partner computer because the event time associated with the file to be replicated is too far into the future. It is 30 minutes greater than the current time. This can happen if the system time on the partner computer was set incorrectly when the file was created or updated. To preserve the integrity of the replica set this file update will not be performed or propagated further.
The file name is: "Policies"
The connection to the partner computer is:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\DMC-SERVER\C1D1A4A1
Note: If this time difference is close to a multiple of 60 minutes then it is likely that this file may have been created or updated on the partner computer while the computer was set to the incorrect time zone when its computer time was initially set. Check that the timezone and time are correctly set on the partner computer.
Event ID 13502
The File Replication Service is stopping.
Event ID 13503
The File Replication Service has stopped.
I have the time zones identical and I have sync the clock aganst each other.
Help urgently required as the SBS powered down this morning and users can not login.
ASKER
How do just turn off the SBS server and do something to the Server 2003 server and force it to be the domain controller.?
ASKER
I modified the "Enable Journal Wrap Automatic Restore" to 1
I moved all five roles over but the SYSVOL is still sharing and populating and the NTFRS starts and then stops
If i run dcdiag i get the following, can this help you help me;
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DM
Starting test: Connectivity
......................... DMC-SERVER passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DM
Starting test: Replications
......................... DMC-SERVER passed test Replications
Starting test: NCSecDesc
......................... DMC-SERVER passed test NCSecDesc
Starting test: NetLogons
Unable to connect to the NETLOGON share! (\\DMC-SERVER\netlogon)
[DMC-SERVER] An net use or LsaPolicy operation failed with error 1203, Win32 Error 1203.
......................... DMC-SERVER failed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for \\MELSERV02.dmc.local, when we were trying to reach DMC-SERVER.
Server is not responding or is not considered suitable.
Warning: DMC-SERVER is not advertising as a time server.
......................... DMC-SERVER failed test Advertising
Starting test: KnowsOfRoleHolders
......................... DMC-SERVER passed test KnowsOfRoleHolders
Starting test: RidManager
......................... DMC-SERVER passed test RidManager
Starting test: MachineAccount
......................... DMC-SERVER passed test MachineAccount
Starting test: Services
NtFrs Service is stopped on [DMC-SERVER]
......................... DMC-SERVER failed test Services
Starting test: ObjectsReplicated
......................... DMC-SERVER passed test ObjectsReplicated
Starting test: frssysvol
......................... DMC-SERVER passed test frssysvol
Starting test: frsevent
......................... DMC-SERVER passed test frsevent
Starting test: kccevent
......................... DMC-SERVER passed test kccevent
Starting test: systemlog
......................... DMC-SERVER passed test systemlog
Starting test: VerifyReferences
......................... DMC-SERVER passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : dmc
Starting test: CrossRefValidation
......................... dmc passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... dmc passed test CheckSDRefDom
Running enterprise tests on : dmc.local
Starting test: Intersite
......................... dmc.local passed test Intersite
Starting test: FsmoCheck
Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
A Time Server could not be located.
The server holding the PDC role is down.
Warning: DcGetDcName(GOOD_TIME_SERV
A Good Time Server could not be located.
......................... dmc.local failed test FsmoCheck