Re: Directory Sync
Take a look at NSI double take. It would replicate between the servers
and failover the server name if something happened. It would create
some what of a cluster so if one server failed the users would not know
as long as the data was good.
.
Relevant Pages
- Re: Event id 2042 /2041 (Directory service) + 12292/11 (VSS)
... The Active Directory cannot replicate with this server ... ime since the last replication with this server has exceeded the ...
(microsoft.public.windows.server.active_directory) - Re: Event id 2042 /2041 (Directory service) + 12292/11 (VSS)
... The Active Directory cannot replicate with this server because ... ime since the last replication with this server has exceeded the tombstone ...
(microsoft.public.windows.server.active_directory) - Re: DFS and RODC Windows Server 2008
... It sounds like you just want to replicate ... branch data from the branch offices back to corporate for backup. ... office server and you would use DFSR to replicate the shared folder back to ... to the head office goes down? ...
(microsoft.public.windows.server.active_directory) - Re: DFS and RODC Windows Server 2008
... Look into using the Enterprise version of Win 2k8 for the hub server. ... Think about putting all the shares on the branch office server into one ... It sounds like you just want to replicate ...
(microsoft.public.windows.server.active_directory) - Re: Event id 2042 /2041 (Directory service) + 12292/11 (VSS)
... I also have the same problems about the tombstone lifetime on all ... The Active Directory cannot replicate with this server because ...
(microsoft.public.windows.server.active_directory) |
|
