You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1.Installed latest version of product as per instructions on both AD DC's.
(Twin site AD setup running on 2003 x64 DC's)
2. Change a users password. The correct entry is added to AD and running the
Google Apps Directory Sync tool sees the users password correctly changed in
Google Apps to match the AD password.
3.The 'real time' updating of the password fails and produces the log entry:
[2010/09/01 13:45:43:011]:Changed password for user "dave.smith"
[2010/09/01 13:45:43:058]:Error during LOgonUserEx: Logon failure: unknown user
name or bad password.
[2010/09/01 13:45:43:058]:Error during Unload User profile: The parameter is
incorrect.
The .ini file looks like below:
[Main]
;name of you google apps
appsDomain=glassesdirect.com
;name and password of an administrator account of google apps
appsAdmin=nameofadminaccount
appsPasswd=adminaccountspassword
;DN and password of an AD user that can write the “hashedPassword” field
ldapAdminBindDn="CN=syncAppUser,OU=Admin,DC=pe,DC=local"
ldapAdminPasswd=*********
;LDAP query to find your AD users
ldapSearchBaseDn="OU=Google,DC=pe,DC=local"
;path of sync application executable (GoogleHashUpdater.exe)
processPath=C:\windows\GoogleHashUpdater.exe
;name and password of a local account to use to run the sync application
processUser=PE\syncAppUser
processPasswd=********
;settings for the proxy to use to connect to google apps
;leave blank if not needed
proxyAddress=
proxyUser=
proxyPassword=
The accounts have been setup with the correct authority and appear to be able
to logon correctly - would you be able to help me out with the specific error
I'm getting so I can get 'real time' password syncing working?
Thanks for your help - and for taking the time to work on a solution to get AD
passwords syncing!
Original issue reported on code.google.com by [email protected] on 22 Sep 2010 at 3:22
The text was updated successfully, but these errors were encountered:
Original issue reported on code.google.com by
[email protected]
on 22 Sep 2010 at 3:22The text was updated successfully, but these errors were encountered: