David Boreham wrote:
Paxton, Darren wrote:
Unfortunately, our current strategy is to have Active Directory as
the single Directory for user management so as to make our Service
Desk more efficient. We also have a policy of removing all single
points of failure from within our enterprise, ther
Paxton, Darren wrote:
The other question though, regarding one-way from AD to FDS - anyone
got any thoughts on that?
The sync code wasn't designed to allow this. However
there are a couple of things you could consider :
1. configure FDS access control to disallow modifications
on attributes th
On Mon, 2007-03-19 at 08:11 -0600, David Boreham wrote:
Eddie C wrote:
> I can not give an authoritative answer, but if your active
directory
> is 2003 server your active directory itself is multimaster (
no more
> PDC and SDC ). It seems theori
Eddie C wrote:
I can not give an authoritative answer, but if your active directory
is 2003 server your active directory itself is multimaster ( no more
PDC and SDC ). It seems theorically possible to install active
directory sync on both nodes but leave it running only on one domain
controll
I can not give an authoritative answer, but if your active directory is 2003
server your active directory itself is multimaster ( no more PDC and SDC ).
It seems theorically possible to install active directory sync on both nodes
but leave it running only on one domain controller. Something like t
Paxton, Darren wrote:
Unfortunately, our current strategy is to have Active Directory as the
single Directory for user management so as to make our Service Desk
more efficient. We also have a policy of removing all single points of
failure from within our enterprise, therefore I was looking at
Hi again all,
Managed to get myself to a pretty good place with my configuration, but
would appreciate another pointer from yourselves.
Currently I have the system up and running with two servers (master1 and
master2) in a 2-way multi-master replication mode.
Master1 also has a Windows Synchron
