You can check the below KB to check if your client has the correct schema & to fix if it doesnot have
NSM client hangs after DMI schema is updated.
Summary:
After the NSM DMI schema update, the NSM Windows client seems to hang while loading.
Problem or Goal:
NSM client hangs after DMI schema is updated.
Solution:
If the NSM Windows client hangs when loading after a DMI schema update it could be a problem with the client retrieving the information from the NSM server. To resolve this:
First, navigate to the /tmp directory on the NSM Server. There should be a Schemas-GDH directory with a version number folder that matches the recent schema version upgrade. If the server doesn't have this directory, you cannot perform this fix.
- On the Windows PC, navigate to C:\Documents and Settings\<username>\Local Settings\Temp\Schemas-NSM
- This folder will have a numbered folder for any previous DMI schema versions. If you have not updated the DMI schema before, only a folder named “null” will be present.
- If the version you just upgraded to has a folder, create a backup of that folder. No backup is needed if there is not a folder for the DMI schema version.
- If there was an existing schema version folder, clear it out. If there was not an existing folder, create one with the correct version number.
- Go to /tmp/Schemas-GDH/<schema version number> on the NSM server. Copy all of the binary files in this directory and paste them to the directory on Windows with the corresponding schema version number.
- Restart the NSM gui client.
Purpose:
Troubleshooting