Windows Server

Bertrand · Guest

Hi

2 years ago, we migrate Server1 from NT4 to W2K.
we promote server2 as DC and then transfer roles from server1 to server2.

we keep online the 2 DC.

we have downgraded server 1.

but we have the 13559 error :
----------------------------------------------------------------------------
--------------------------------------------------------------
Type de l'événement : Erreur
Source de l'événement : NtFrs
Catégorie de l'événement : Aucun
ID de l'événement : 13559
Ordinateur : server2
Description :
The File Replication Service has detected that the replica root path has
changed from "c:\winnt\sysvol\domain" to "c:\winnt\sysvol\domain".
If this is an intentional move then a file with the name
NTFRS_CMD_FILE_MOVE_ROOT needs to be created under the new root path.
This was detected for the following replica set: "DOMAIN SYSTEM VOLUME
(SYSVOL SHARE)"
Changing the replica root path is a two step process which is triggered by
the creation of the NTFRS_CMD_FILE_MOVE_ROOT file.
----------------------------------------------------------------------------
--------------------------------------------------------------

what can we do now ?

thanks

Glenn LeCheminant · Guest

For some reason FRS gets confused rather easily.
All you need to do is follow what the description says to do.
stop ntfrs
create a file with the name NTFRS_CMD_FILE_MOVE_ROOT under the root path
"c:\winnt\sysvol\domain"
start ntfrs

problem solved :-)

Glenn

"Bertrand" <thebeb@hotmail.com> wrote in message
news:eFViw3psEHA.1220@TK2MSFTNGP10.phx.gbl...

Bertrand · Guest

Hi

ok, that's what i want to do but i've found this article and it disturb me :

http://www.adminlife.com/247reference/msgs/16/83581.aspx

"Ok so I created the NTFRS_CMD_FILE_MOVE_ROOT file and it
totally destroyed our Active Directory. "

what do you think about ?

thanks

"Glenn LeCheminant" <the.only@gmail.com> a écrit dans le message de
news:ujJ0jK6sEHA.3772@TK2MSFTNGP10.phx.gbl...

Glenn L · Guest

FRS will not destroy AD.
this other network clearly had other issues going on.
This is a perfectly safe maintenance operation.

Of course, you can also ignore it.
It is nothing more than a nuisance error.

In the unlikely event it causes FRS any grief, then you can perform a
non-authoritative restore of the repica set on that server.
In fact, this is an alternate method (al-be-it more drastic) to get rid of
the error.

--
Glenn L
CCNA, MCSE 2000, MCSE 2003 + Security

"Bertrand" <thebeb@hotmail.com> wrote in message
news:OyHftCOtEHA.3564@tk2msftngp13.phx.gbl...

Bertrand · Guest

i've tried to create the file and restart the ntfrs sevice.
the server has made some changes, log some events and then AD will not work.

we were unable to connect the AD console.

i've decided to bring it back by V2i image.

the server is working now but had always the same errors with ntfrs.

"Glenn L" <the.only@gmail.com> a écrit dans le message de
news:ekl9RxOtEHA.1040@TK2MSFTNGP10.phx.gbl...

Glenn L · Guest

Sorry to here things did not go as planned.

I really don't know what you mean by AD will not work.
and 'we were unable to connect to the AD console'

you will have to elaborate on this.

I have put that file in place on many domain controllers experiencing the
identicle error, and have had 100% success.

If you want to get rid of it, you can use the alternate method of performing
a non-authoritative restore of sysvol.
let me know and I'll describe the process.

Note: be very careful with restoring an image of a domain controller.
If you created it just before putting that file in place, then the risk is
small.
But if it is aged at all, you can cause problems with active directory.

--
Glenn L
CCNA, MCSE 2000, MCSE 2003 + Security

"Bertrand" <thebeb@hotmail.com> wrote in message
news:OQIcvdatEHA.2808@TK2MSFTNGP14.phx.gbl...

	Windows Server Forum Index -> DFS and FRS	All times are GMT
Page 1 of 1