Moved fsmo roles to different server

  • Thread starter Thread starter Guest
  • Start date Start date
Status
Not open for further replies.
G

Guest

Guest
Archived from groups: microsoft.public.win2000.active_directory (More info?)

I ran dcpromo on my new server and then made it a catalog server and
transfered the fsmo rules over to it from the other DC. Now I have an
warning from ntfrs that states
File Replication Service is scanning the data in the system volume. Computer
SERVER0 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.

I also ran dcdiag and received the following:

Doing primary tests

Testing server: Default-First-Site-Name\SERVER0
Starting test: Replications
......................... SERVER0 passed test Replications
Starting test: NCSecDesc
......................... SERVER0 passed test NCSecDesc
Starting test: NetLogons
......................... SERVER0 passed test NetLogons
Starting test: Advertising
Warning: DsGetDcName returned information for
\\server1.hospital.local,
when we were trying to reach SERVER0.
Server is not responding or is not considered suitable.
......................... SERVER0 failed test Advertising
Starting test: KnowsOfRoleHolders
......................... SERVER0 passed test KnowsOfRoleHolders
Starting test: RidManager
......................... SERVER0 passed test RidManager
Starting test: MachineAccount
......................... SERVER0 passed test MachineAccount
Starting test: Services
......................... SERVER0 passed test Services
Starting test: ObjectsReplicated
......................... SERVER0 passed test ObjectsReplicated
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
There are errors after the SYSVOL has been shared.
The SYSVOL can prevent the AD from starting.
......................... SERVER0 passed test frssysvol
Starting test: kccevent
......................... SERVER0 passed test kccevent
Starting test: systemlog
An Error Event occured. EventID: 0x00000457
Time Generated: 01/12/2005 11:05:44
Event String: Driver Xerox Phaser 8200DP required for printer
An Error Event occured. EventID: 0x00000452



Time Generated: 01/12/2005 11:05:44
Event String: The printer could not be installed.
......................... SERVER0 failed test systemlog

Running enterprise tests on : hospital.local
Starting test: Intersite
......................... hospital.local passed test Intersite
Starting test: FsmoCheck
......................... hospital.local passed test FsmoCheck


any ideas why I can not finish the replication?
 
Archived from groups: microsoft.public.win2000.active_directory (More info?)

Blandis,

Chriss took the words right out of my mouth! Install the Support Tools (
although using the Service Pack CD Media or the direct download from the MS
Site might be a better idea than using the Support Tools from the Server CD
Media ) and run repadmin /showreps /v as well as repadmin /showconn. You
can also use 'netdom query fsmo' - without the quotes - and use replmon.

I would also say that you could look in the Event logs on that DC.

--
Cary W. Shultz
Roanoke, VA 24014
Microsoft Active Directory MVP

http://www.activedirectory-win2000.com
http://www.grouppolicy-win2000.com



"Blandis" <Blandis@discussions.microsoft.com> wrote in message
news:7CB12708-EFD7-45EC-9299-B579B3ED63BB@microsoft.com...
>I ran dcpromo on my new server and then made it a catalog server and
> transfered the fsmo rules over to it from the other DC. Now I have an
> warning from ntfrs that states
> File Replication Service is scanning the data in the system volume.
> Computer
> SERVER0 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.
>
> I also ran dcdiag and received the following:
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\SERVER0
> Starting test: Replications
> ......................... SERVER0 passed test Replications
> Starting test: NCSecDesc
> ......................... SERVER0 passed test NCSecDesc
> Starting test: NetLogons
> ......................... SERVER0 passed test NetLogons
> Starting test: Advertising
> Warning: DsGetDcName returned information for
> \\server1.hospital.local,
> when we were trying to reach SERVER0.
> Server is not responding or is not considered suitable.
> ......................... SERVER0 failed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... SERVER0 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... SERVER0 passed test RidManager
> Starting test: MachineAccount
> ......................... SERVER0 passed test MachineAccount
> Starting test: Services
> ......................... SERVER0 passed test Services
> Starting test: ObjectsReplicated
> ......................... SERVER0 passed test ObjectsReplicated
> Starting test: frssysvol
> Error: No record of File Replication System, SYSVOL started.
> The Active Directory may be prevented from starting.
> There are errors after the SYSVOL has been shared.
> The SYSVOL can prevent the AD from starting.
> ......................... SERVER0 passed test frssysvol
> Starting test: kccevent
> ......................... SERVER0 passed test kccevent
> Starting test: systemlog
> An Error Event occured. EventID: 0x00000457
> Time Generated: 01/12/2005 11:05:44
> Event String: Driver Xerox Phaser 8200DP required for printer
> An Error Event occured. EventID: 0x00000452
>
>
>
> Time Generated: 01/12/2005 11:05:44
> Event String: The printer could not be installed.
> ......................... SERVER0 failed test systemlog
>
> Running enterprise tests on : hospital.local
> Starting test: Intersite
> ......................... hospital.local passed test Intersite
> Starting test: FsmoCheck
> ......................... hospital.local passed test FsmoCheck
>
>
> any ideas why I can not finish the replication?
 
Archived from groups: microsoft.public.win2000.active_directory (More info?)

Hello,
Install the Windows Support Tools found on your Windows Server CD, use the
command line based tool repadmin.exe with the syntax below.

repadmin /showreps /v

Correct any reported issues, or post the output back for assistance.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips

"Blandis" <Blandis@discussions.microsoft.com> skrev i meddelandet
news:7CB12708-EFD7-45EC-9299-B579B3ED63BB@microsoft.com...
>I ran dcpromo on my new server and then made it a catalog server and
> transfered the fsmo rules over to it from the other DC. Now I have an
> warning from ntfrs that states
> File Replication Service is scanning the data in the system volume.
> Computer
> SERVER0 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.
>
> I also ran dcdiag and received the following:
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\SERVER0
> Starting test: Replications
> ......................... SERVER0 passed test Replications
> Starting test: NCSecDesc
> ......................... SERVER0 passed test NCSecDesc
> Starting test: NetLogons
> ......................... SERVER0 passed test NetLogons
> Starting test: Advertising
> Warning: DsGetDcName returned information for
> \\server1.hospital.local,
> when we were trying to reach SERVER0.
> Server is not responding or is not considered suitable.
> ......................... SERVER0 failed test Advertising
> Starting test: KnowsOfRoleHolders
> ......................... SERVER0 passed test KnowsOfRoleHolders
> Starting test: RidManager
> ......................... SERVER0 passed test RidManager
> Starting test: MachineAccount
> ......................... SERVER0 passed test MachineAccount
> Starting test: Services
> ......................... SERVER0 passed test Services
> Starting test: ObjectsReplicated
> ......................... SERVER0 passed test ObjectsReplicated
> Starting test: frssysvol
> Error: No record of File Replication System, SYSVOL started.
> The Active Directory may be prevented from starting.
> There are errors after the SYSVOL has been shared.
> The SYSVOL can prevent the AD from starting.
> ......................... SERVER0 passed test frssysvol
> Starting test: kccevent
> ......................... SERVER0 passed test kccevent
> Starting test: systemlog
> An Error Event occured. EventID: 0x00000457
> Time Generated: 01/12/2005 11:05:44
> Event String: Driver Xerox Phaser 8200DP required for printer
> An Error Event occured. EventID: 0x00000452
>
>
>
> Time Generated: 01/12/2005 11:05:44
> Event String: The printer could not be installed.
> ......................... SERVER0 failed test systemlog
>
> Running enterprise tests on : hospital.local
> Starting test: Intersite
> ......................... hospital.local passed test Intersite
> Starting test: FsmoCheck
> ......................... hospital.local passed test FsmoCheck
>
>
> any ideas why I can not finish the replication?
 
Status
Not open for further replies.