No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


The TSM hasn’t synchronized the new OU created in the AD causes the new OU’s user has been validated unsuccessfully

Publication Date:  2012-11-20 Views:  72 Downloads:  0
Issue Description
Version: 0R001C01SPC105
Add users in the new OU, and assign these users to the virtual machine, login in the virtual machine via the domain account, there will prompt the TSM validating failed.

Alarm Information
Handling Process
1. We can ping through the TSM server from the virtual machine, it proves that the network hasn’t problem.
2. Check the “Department” in the TSM, and we find there isn’t corresponding “Department” with the new OU, so we need to add new “Department” manually and synchronize with the new OU’s users.
3. To see the detail steps please refer to the attachment.
Root Cause
The possible reasons are two:
1. The network between the virtual machine and the TSM server isn’t *;
2. The TSM should synchronize with the new OU’s user in the AD, if hasn’t synchronized successfully, the user can’t get the TSM’s validation.