In a previous blog I have shown how ADSync can be monitored in this listing, we will look at some of the methods to the to resolve or reduce the amount of bad data needs to be sent to the API of CPSM ADSync.
Limits the number of bad attempts for an inquiry
by default when a request fails for any reason, the ADSync client is trying to send the request until it succeeds. This may cause a spam-like effect on the API.
Add ADSync v11 and above there is a possibility to adjust the maximum amount of repetitions that the ADSync client send the change. If the amount reaching the amendment disregard and will wait for the next change to the user to send a synchronization.
Application to a DC with ADSync.
Go ADSync install to directory (default C: Program Files AD Sync)
Open ADSync.exe.config in Notepad
for UploadMaxErrors search
change the value of 0 (unlimited) to 3
you save the file
repeat for all. Servers on which the ADSync client installed.
in ADSync logs or event viewer have the following error message is displayed when a user sync attempt the maximum amount of errors exceeded.
Default Source Error 2 Error upload user syncuser ': the user is not as the maximum number of retries are updated (3) has exceeded 23 12/08/2014: 51: 31Z
Common Mistakes
These are often mistakes that can be seen in the ADSync protocol. The logs are in the directory logs of ADSync and can be used for easier transport zipped, if you log a support request.
All servers with the ADSync client should be installed tested as their protocols are independent. [1945003gleichoderkomplexeralsdieCPSMAD]
Password complexity
is a requirement of the client ADSync that the AD password policy customers. This is to ensure that a user's password remains synchronized and is not validation problems have
. Example:
Default Source Error 2 failed users' uploaded syncuser because an error occurred, the minimum length is 7 characters 08/12/2014 23: 51: 26Z
Solution:
to resolve the single-user update user syncuser 'update the user in the customer AD with a complex password for a complete solution, provide customers with your requirements available and they receive their password complexity requirements ,
users in pending stuck
Sometimes a user is in a wait state (orange) plug because of previous provisioning request to restarting the provisioning server or for some other reason not completed due can so it does not fail, but not completely
. Example:
processing object 'syncuser' in the current state ????????? with the status of InProgress
Solution:
It is common for this message in the logs to see, but when a user in sitting for 5-10 minutes and other user requirements might be through it in a deadlocked state.
to resolve, CPSM UI open, go to the customer, to find the user.
, the user should an orange status icon next to them have to expand if so the user.
Click Reset Status
Accept the prompt
so that the status is unknown (blue) is set, and ADSync will then try to send the request and the status to green (unless the retry limit been reached) is
domain does not belong to the customer
When e-mail addresses of the sync or synchronization userPrincipalName, the customer must have registered the domain against them in CPSM.
Example:
Error users 'to post because Failed to update the user syncuser' syncuser: user email domain 'test.loca' not a customers [are
. Solution:
You can download the e-mail address removed by the user in the client AD or domain, the client in CPSM add
Conclusion [1945005Hoffentlich]
This will you solve some evidence of some of the common problems ADSync.
0 Komentar