[389-users] Pass Sync Doesn't Work

[Jeff Moody]

It should.
The BDC will replicate the change to the PDC and that should register as a password change to PassSync and that will then replicate the change to the 389 server.

I have PassSync running in our environment and have had users change their password from the office which is running a secondary DC and the change gets reflected in the 389 system within <5 minutes of the AD replication.

----

Jeff Moody
Senior Systems Engineer
 
EVS Corporation
5050 Poplar Avenue ,Suite 1600
Memphis, Tennessee 38157
(901) 259-2387 - 24x7 Helpdesk

(901) 881-0919 - Office
(901) 497-1444 - Cell
jeff.moody at evscorporation.com

-----Original Message-----
From: fedora-directory-users-bounces at redhat.com [mailto:fedora-directory-users-bounces at redhat.com] On Behalf Of Doug Tucker
Sent: Tuesday, September 08, 2009 9:05 AM
To: General discussion list for the 389 Directory server project.
Subject: Re: [389-users] Pass Sync Doesn't Work


> >> would be greatly appreciated.
> >
> > 1 - In windows registry-HKLM-Software-PasswordSync,
> > change the "log level" setting from "0" to "1"
> >
> > 2 - Restart the passsync service
> >
> > 3 - look for passsync.log under C:\Program Files\*Password 
> > Synchronization\
> >
> >
> > --Chandra
> >
Thanks, I'll ask the windows guy to set this.  I haven't seen anything
about this, but merely thinking.  If the passync service is installed on
the PDC host, if a windows user changes their password, but are
connected to the BDC when they do so, will passync still catch the
change?

--
389 users mailing list
389-users at redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users