When failing over a Windows VM without Re-IP, when it boots up, the network shows up as a new network, and you get the popup upon login to allow network discovery on the new network (which changes the network from public to private).
This environment needs the network set to private for all applications/databases to communicate with each other properly. Logging in to each server and changing the "new" network to private and then rebooting the servers in proper order again is a clunky solution we would like to avoid. Is there a way Veeam can make the OS see the NIC on the failover VM to be the same one as the production? (for example: if the network is labled Network 4 in windows and we fail over, Network 5 is the name when it boots. interestingly it has the same ip info that network 4 did in production)
Or is there a way in Windows to make new networks Private by default?
I found a suggestion to change the local security policy of Unidentified and Identifying Networks location to private, but that didn't seem to solve the issue.