Red Hat Bugzilla – Bug 467590
Passsync.msi fails to receive sync updates in win2008 x86_64
Last modified: 2015-12-07 12:08:04 EST
Description of problem:
passsync service doesn't seem to register password changes.
Version-Release number of selected component (if applicable): Passsync-20060330.msi
Steps to Reproduce:
1. Install passsync on Windows 2008 x86_64 domain controller
2. Follow instructions for setup: http://directory.fedoraproject.org/wiki/Howto:WindowsSync
3. Attempt password change in 'Active Directory Users and Computers' ... ie. right-click and 'reset password'.
10/19/08 01:37:01: Password list is empty. Waiting for passhook event
<<TIMESTAMP>> Received passhook event. Attempting sync.
Only 105 events in log file ... I can see the password sync bind to Fedora DS successfully ... however I never see the logfile indicate that a passhook event has occurred.
We have never tested passsync on a 64-bit system. We only support 32-bit windows right now. The code is open source, and the free visual studio compiler from microsoft can be used to compile the code.
This falls under the category of "support 32-bit and 64-bit windows 2003 and 2008 for both passsync and windows console"
*** Bug 489021 has been marked as a duplicate of this bug. ***
Fixed in PassSync 1.1.2
We're testing Win2k8 R2 64bits with PassSync 1.1.4 and logs don't show any password change event..
I see from Comment 4 that this should work on 1.1.2, but the description says now that the bug affects 1.1.3
(In reply to comment #5)
> We're testing Win2k8 R2 64bits with PassSync 1.1.4 and logs don't show any
> password change event..
> I see from Comment 4 that this should work on 1.1.2, but the description says
> now that the bug affects 1.1.3
Did you see any errors during PassSync installation?
Did you restart the AD box after installing PassSync?
Do you see anything in the log - http://directory.fedoraproject.org/wiki/Howto:WindowsSync#PassSync_Logging ?
There were no errors during installation... The Windows machine was restarted, we still see only "Waiting for passhook event"
10/21/10 11:54:26: PassSync service initialized
10/21/10 11:54:26: PassSync service running
10/21/10 11:54:27: No entries yet
10/21/10 11:54:27: Password list is empty. Waiting for passhook event
10/21/10 12:04:31: Received passhook event. Attempting sync
10/21/10 12:04:31: No entries yet
10/21/10 12:04:31: PassSync service stopped
10/21/10 12:04:32: PassSync service initialized
10/21/10 12:04:32: PassSync service running
10/21/10 12:04:32: No entries yet
10/21/10 12:04:32: Password list is empty. Waiting for passhook event
Looking at it right now it indeed lists an event. We tried again to change a password, but there are no new events registered....
Is there a more verbose log level?
Ok, the AD admin omitted the fact that there are more domain controllers in the lab. Leaving only this one (the one with PassSync) running made it catch all the updates.