NT Replicator - does it work?

[Jono]

I've heard that to get NT replicator working you need to go into the registry (H_KEY_LOCAL_MACHINE - SYSYEM - CONTROLSET(XXX) - COTROL - SECUREPIPESERVICES - WINREG) and enable the BackUP account name with read permissions.<br>
Is this correct? Does it work?

 

[waynemaples]

NO. Directory replication service needs to be started. The account used to do the replication needs to be a member of Backup Operators, Domain Users, and Replicator domain groups, and make sure that the account is available for logon at all times. The account can be any name but Replicator (which is a groupname).<br>
<br>
The files to be replicated are in the PDCs export directory.<br>
We use it for login scripts/profiles.

 

[Jono]

thanks wayne,<br>
I'd already done this - but i'm getting a message<br>
saying : The replicator cannot update directory<br>
c:\winnt\system32\repl\import\scripts.<br>
It has tree integrity and is the current directory of<br>
some process.<br>
any ideas ?<br>
We do have seagate backup exec installed - do we <br>
have to disable this totally?

 

[Zelandakh]

check the access privs on the scripts directory. Have a replicator account that has FC access to both scripts directories then it should all work.

 

[Jono]

it works. it works.<br>
thanks guys !

 

[wietersr]

We get the "tree integrity" error often also, but I have found the trend--it only seems to appear after I make some changes to the export\scripts directory and there is still a connection open when replication tries to write back to the export server. my work-around has been to disconnect the session manually and all is well. I dont know why the session doesnt get broken automatically when I close the explorer.