How do I manually update a managed object on an AppManager Managed Client? (NETIQKB8365)

How do I manually update a managed object on an AppManager Managed Client?

To update an existing managed object:

1. Stop the NetIQ AppManager Client Communications Manager (NetIQccm) and NetIQ AppManager Client Resource Monitor (NetIQmc) services.
2. Navigate to the following directory to locate the managed object (q*.dll) to be updated:

   • Version 6.x: %\Program Files\NetIQ\AppManager\Bin
   • Version 7.0.x: %\Program Files\NetIQ\AppManager\Bin

   For example, the name of the file for the Windows NT managed object would be as follows:

   • Version 6.x: Qnta4.dll

3. Manually unregister the existing managed object.
4. Rename or remove the existing managed object (q*.dll) from the Bin directory.
5. Copy the new or revised managed object file to the same directory.
6. Manually register the new or revised managed object.
7. Restart the NetIQ AppManager Client Communications Manager (NetIQccm) and NetIQ AppManager Client Resource Monitor (NetIQmc) services.
8. Drag and drop the appropriate Discovery knowledge script onto the target Server to discover the new or revised managed object.

NOTE: This procedure assumes that the managed object file is available - either from another AppManager Managed Client in the environment that has this particular managed object installed or from NetIQ Technical Support for AppManager (for example, a revised managed object included in a patch or fix).

To manually unregister a managed object:

1. Stop the NetIQ Services on the target Server.
2. Launch a command prompt and change directories:
   
   Version 6.x: %\Program Files\NetIQ\AppManager\Bin
   Version 7.0.x: %\ProgramFiles\NetIQ\AppManager\Bin
   
   
3. Type the following command:
   
   regsvr32 /u FileName.dll
   
   Where FileName is the name of the managed object to be unregistered.  For example, the name of the file for the Windows NT managed object would be as follows:
   
   Version 6.x: qnta4.dll
   
   
4. Start the NetIQ Services on the target Server.
5. Run the appropriate Discovery knowledge script.

Formerly known as NETIQKB8365