Return
-
Title
What is the mechanism to keep the IMU console, AD, and local servers in sync? -
Description
What is the mechanism to keep the IMU console, AD, and local servers in sync?
When a server is profiled in Quest Identity Manager for Unix console, it brings information about users to the console. If a change is made to the user on the unix server, this change is not reflected in the console. For example, user 'Test User' has a uid of 123 on server ABC when the server is profiled in the console. Locally on server ABC, Test's uid was changed to 456. The console still reflects Test's uid as 123.
Similarly, when server XYZ is joined to AD, Quest gathers information about users who are unix-enabled in AD. If a change is made to that user in AD, it is not reflected on server XYZ. For example, when server XYZ joined AD, user 'Test User' had a primary group of Linux Admins. Test's primary group was changed in AD to Unix Admins. If I lsuser Test on server XYZ, his primary group still reflects Linux Admins, not Unix Admins as it shows in AD. -
Cause
The information in IMU is only as current as the last profile
-
Resolution
Currently the only way to get the data in sync is to run another profile.