Yes, the nsrpolicy command changed in 19.3 Found a KB about it, Knowledge Base Article: 000545650 Workaround is to temporarly add a vm to the group, then edit again and remove it to force a refresh. However this haven't worked 100% in the past for me
Occasionally, a VM that was deleted from vCenter (but which wasn't removed from a Networker group) would result in a backup "failure".   I have previously used this command to eliminate this error (that's not really an error):  nsrpolicy group update vmware -g -O    But, when I just ran this command, it comes back with this message: 195173:nsrpolicy: No items to add or delete. The syntax of this command is:nsrpolicy group update--group_name -g [--comment -c ] [--server -s ] [--debug -D ] [--help -h] Additional parameters to be specified for 'vmware' type are: nsrpolicy group update vmware [--vcenter_name, -V vCenter name] [--add_vmware_clnt_list, -o ex. /MyFolder, /DC/host/vm] [--del_vmware_clnt_list, -O ex. /MyFolder, /DC/host/vm] [--backup_optimization, -z capacity | performance]  [--help -h] (I'm pretty sure I had the group name and UUID correct when I ran the command)   Did something change in Networker 19.3?  Do I have the wrong command syntax?
nsrpolicy - did something change in ver 19.3?