NMC client wizard fails to list all valid NMM savesets

I've recently seen when trying to create new NMM clients using the NetWorker Management Console client wizard, that the wizard does not show all valid savesets (in some chases it doesn't show any savesets) for one or more Microsoft applications. In once instance the NMC client wizard failed to even display any of the clients file system savesets.

Cause

After some exhaustive checking and testing I gave up and ended up speaking with EMC NetWorker support who suggested that the main cause seems in most circumstances have been during silent installations, or when a failure occurred when registering the remote agent component for NMM. She also informed me that they have seen this issue occur when there are name resolution issues between the NetWorker client and server (especially within cluster environments).

After some more testing and debug data going to-and-fro support we resolved the problem by running a series of commands on the clients for the affected MS applications.

Here, I will share with you the commands to run for various NMM installs for MS applications in an attempt to resolve this issue:

Resolution

First make sure all writers information is correctly populated. To do it so run:

C:\> vssclupdate

Once the above command has completed, use the listing below to determine which commands need to run to manually register the Remote Agent for the affected Microsoft application:

MS Exchange Server
  • Firstly, unregister the MS Exchange Server Remote Agent on the Exchange server:
    C:\> nsrnmmexchra -u
  • Then re-register the MS Exchange Server Remote Agent on the Exchange server:
    C:\> nsrnmmexchra -i
MS SQL Server
  • Firstly, unregister the MS SQL Server Remote Agent on the SQL server:
    C:\> nsrnmsqlra -u
  • Then, re-register the MS SQL Server Remote Agent on the SQL server:
    C:\> nsrnmsqlra -i
MS sharePoint Server
  • Firstly, unregister the MS SharePoint Server Remote Agent on the SharePoint server:
    C:\> nsrnmmspra -u
  • Then re-register the MS SharePoint Server Remote Agent on the SharePoint server:
    C:\> nsrnmmspra -i
MS Hyper-V Server
  • Firstly, unregister the MS Hyper-V Server Remote Agent on the Hyper-V server:
    C:\> nsrnmmhypervra -u
  • Then re-register the MS Hyper-V Server Remote Agent on the Hyper-V server:
    C:\> nsrnmmhypervra -i
File System savesets

If the problem is with the File System savesets, run the following commands to unregister and re-register the remote agent:

  • To unregister it:
    C:\> nsrfsra -u
  • Then re-register it:
    C:\> nsrfsra -i