We had an issue in our lab, after we used Metro to upgrade from 5.3.2 to 5.3.3.
Both the old and the new VSD VMs were still present on each server, and both were set to 'autostart'. Upon a server reboot, both versions came up, causing IP address conflicts
The upgrade process should enable autostart on the new VSDs after the upgrade succeeds, and disable it for the old VMs at the same time
We had an issue in our lab, after we used Metro to upgrade from 5.3.2 to 5.3.3. Both the old and the new VSD VMs were still present on each server, and both were set to 'autostart'. Upon a server reboot, both versions came up, causing IP address conflicts
The upgrade process should enable autostart on the new VSDs after the upgrade succeeds, and disable it for the old VMs at the same time