Hmm...no way that I’m aware of ​@Hammer . I think the only thing you can do is remove it from the PG, then re-add it, then go into the Backup Job, go to the Computers and probably need to re-add. You of course would have differing Restore Point (Backup) Chains. 

Maybe someone else can chime in with a suggestion I’m overlooking..

Best.

Did you try going through the wizard for that machine to see if there are connection issues?  If you use DNS properly with DHCP then it should update and pick it up.  Might need to remove and add again as Shane said.

Okay, thanks…I did try the rescan and it found the machine, but when I go back to the list of machines in the PG, it still had the old IP.

I am sure support could help with that at this point.  Not sure what else to suggest.

Hmm...ok; not sure what else to try besides a re-add

Thank you.

Is your DNS prefix set on the VBR server? I had a similar thing in the past where the rescan had issues when you run a non domain-joined VBR with domain-joined PG objects. Can’t remember the details but worth a shot to set the prefix and try rescanning as Shane suggested.

You don’t use DNS FDQN name?   My VEEAM CE uses my Fortinet DNS Server for all IPv4 and IPv6 addresses of every VM and physical machine to back up.

That’s the correct way (to use a proper DNS sever) but you can either use FQDN or the simple hostname. The difference is that for non domain-joined systems you might struggle resolving the FQDN since default workgroup servers don’t attach the correct suffix by default as long as you don’t set it in the IP settings (advanced section).