Manually uninstall NetWorker in Windows

I try to upgrade NetWorker on one of the Windows client and find out NetWorker is no longer in Add / Remove Program.  If I try to upgrade, it will complain an existing version exist.  Do a bit google search and find the following article in EMC community on how to uninstall NetWorker manually in Windows.

Remove the Upgrade Code from the following registry keys:
HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\Upgrade Codes

HKCR\Installer\UpgradeCodes

Windows Installer uses a GUID (Global Unique Identifier) to uniquely identify products being installed. They call it an Upgrade Code. This is used to identify that NetWorker is installed on this machine.

NetWorker has three upgrade codes (the first for NW 6.0, the second for all other NW versions (except X64), the third for the X64 package):

3EB2C626C9BC4D118811000972CCA7DF
2827A1B508153D114831000A9C877BD1
1D09C7743451200439D99949BD5A9F1E

It may also be necessary to remove the NetWorker services from the registry. They are located in:

-HKLM\SYSTEM\CurrentControlSet\Services
-Delete the following keys: nsrd, nsrexecd, nsrpm, hagentd, lgtolmd
-For NMC, the key to look for is: gstd
-After removing the services, reboot the machine.

Also run the below commands on the command prompt before you reboot the machine

sc delete nsrexecd
sc delete nsrd

All installed products have an entry in the following registry key:
-HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall

-Control Panel Add/Remove programs gets its information from this key.
-If an entry under this key is deleted, it will not be displayed in Add/Remove Programs.

The above steps work for me.  The version of NetWorker on my box is 7.6.1.  You may need to delete the following key.


HKLM\Software\Legato\NetWorker

To manually remove the old binary.  Be very careful if it is a NetWorker server.
If it is a NetWorker server running on Windows, NEVER delete res and mm folders (that's where the NetWorker config and media database located).  I normally keep the logs folder too.  I believe the dedupe folder contain the cache info for Avamar.  

Again, backup your registry keys before making changes to your registry.

HP Advisory on 10G NC522SFP with connectivity issue

Recently, one of the servers with 10G NIC starts to show the following error message. 

DEVICE: HP NC522SFP Dual Port 10GbE Server Adapter #2
PROBLEM: Tx path is hung. The device is being reset.
ACTION: Adapter recovers from this error automatically.

Search from the web and see this HP advisory.  When I attempt to upgrade the firmware, I get the following error. 

"Dependencies Failed -- Driver and firmware set are not allowed for update. Please install driver version 4.3.11.407 prior to performing firmware upgrade on devices with firmware version 4.0.550 or earlier installed. See nxflash.log for further details"
Upgrade to the latest driver and update the firmware.  Failed!

Upgrade to driver version 4.3.11.407 and then update the firmware.  Failed again!

Call support and they have me redo the same thing again.  Testing different firmware version and going nowhere.  After 3 hrs of troubleshooting, HP tells me it is a bad NIC.  I refuse to get a replacement NIC since the NIC is functioning fine.  So, I arrange another downtime and use my a spare 10G NIC.  I still have the same issue.  Eventually, we put the driver back to 4.3.11.407.  After that, they escalate to next level.  Suggestion is to use Local Admin account but it is still going nowhere (it is true that even domain admin account will return the same error.  You need to login as local admin to complete the firmware upgrade).

Check back on HP site and see firmware version 1.3.9.7 is available.  Run the installation and it passes the dependencies check.  So, I know it must be dependencies issue on firmware not driver. 

The solution is to stay at driver 4.3.11.407 and update firmware to 1.3.9.0.  Reboot.  Then update firwmare to 1.3.9.6.  Reboot.  Run the driver update and issue is now resolved.  If your NC522SFP firmware is too old, upgrade to firmware 1.3.9.0 first.