Forum Discussion

Aurelien59's avatar
Aurelien59
Level 4
6 years ago

How to rename a list of clients that do not have the correct name

 
I deployed the Netbackup 8.0 client (using SCCM) on about 200 clients by making a mistake: in the "silentclient.cmd" file, in the line "SET CLIENT =%COMPUTERNAME%" I made the error of leave "SET CLIENT=PC-TEST-NBU" ...
 
And so, the name of all deployed NBU clients is "PC-TEST-NBU" on all machines. :smileyfrustrated:

I am afraid of making a new mistake so I come to ask for help here so I can rename all NBU clients correctly according to their machine name.
 
Can you help me please ?
(I would like to avoid having to reinstall each client completely, and so I would like if possible to just modify this entry)
  • You cannot directly execute custom code via NetBackup Client.  (well, that's not strictly true, as you can via pre and post scripts surounding backup jobs - but that might not work in a moderm certificated environment with clients that have an incorrect internal name).  And, you might be able to change/update the client name of all the clients from the Master using the bpsetconfig or nbsetconfig commands, again as long as certificated authentication does not get in the way (because the internal client names are wrong) - but you would need to know the intended client names beforehand.

    Instead, I would think it would be a lot easier if you got SCCM to execute some custom code to change the "client_name" NetBackup Client registry entry... or wrote your own custom PowerShell to do the same.

  • You cannot directly execute custom code via NetBackup Client.  (well, that's not strictly true, as you can via pre and post scripts surounding backup jobs - but that might not work in a moderm certificated environment with clients that have an incorrect internal name).  And, you might be able to change/update the client name of all the clients from the Master using the bpsetconfig or nbsetconfig commands, again as long as certificated authentication does not get in the way (because the internal client names are wrong) - but you would need to know the intended client names beforehand.

    Instead, I would think it would be a lot easier if you got SCCM to execute some custom code to change the "client_name" NetBackup Client registry entry... or wrote your own custom PowerShell to do the same.