At the end of the take over and the "old" ad is switched off.

Univention goes on to configure a repointing of the interfaces in the new server.
however the system is flawed.

you take the network interface, then bum in an "alias" to match the old ip address of the replaced AD server.

This works fine, inside the vm, but if the actual server hosting the  AD vm is not in the same subnet, then the  "multi-homing" of the network card cannot be routed.

VMware does not allow multiple ip addresses in the same subnet to be routed via the correct gateways.

so what actually happens, is the "Alias" address does not reliably function.

What should happen is the option to "leave the network ALONE", tehn allow the user to manually reconfigure the base ip address to the new one.
THEN reboot.

I have not been able to reliably back out the changes on a completed install for the alias