-
Title
Domain membership is not updated after computer was moved outside of QMM RUM (Resource Updating M -
Description
Computer Domain membership as shown in QMM RUM (Resource Updating Manager) is not updated after computer was moved to a different domain manually or by a tool other than RUM. This is especially noticeable during the testing when the same computers are moved between the source and the target frequently and sometimes Windows native way of joining domain was utilized. Can this behavior be changed? -
Cause
This is considered a product limitation in the new QMM 8.4 RUM console and going to be fixed in the next product release. Please refer to the Resolution section for a workaround.
-
Resolution
WORKAROUND:
Upon enumeration computer objects are stored in ADAM project database. You can modify or just delete it manually in ADAM under CN=Computers,CN=ResourceProcessing,CN=AMMProject_<GUID>,CN=<Project> using ADAMADSIEdit.
IMPORTANT: Quest does not provide support for problems that arise from improper modification of objects using ADSI Edit. The following statement about ADSI Edit was taken directly from Microsoft:
Warning: If you use the ADSI Edit snap-in, the LDP utility, or any other LDAP version 3 client, and you incorrectly modify the attributes of Active Directory objects, you can cause serious problems. These problems may require you to reinstall Microsoft Windows 2000 Server, Microsoft Windows Server 2003, Microsoft Exchange 2000 Server, Microsoft Exchange Server 2003, or both Windows and Exchange. Microsoft cannot guarantee that problems that occur if you incorrectly modify Active Directory object attributes can be solved. Modify these attributes at your own risk.