is there any disadvantage / problem, if the Hyper-v role is added afterwards on an active physical Windows server (for example fileserver/dhcp server...) ?
It would be better to install it before going productive, for sure. But is there any real problem if it is done afterwards? The server needs to be rebooted afterwards, which is mandatory.
Hyper-V is a type 1 hypervisor, so I assume there is some major change underneath, wenn done.
best regards!
Disadvantage when adding Hyper-V Role on active server?
Re: Disadvantage when adding Hyper-V Role on active server?
No, there are no drawbacks (unless you have a very specific and very rare scenario like f.e. your OS / application needs an access to some proprietary hardware etc). These days all of the "generic" workload should be virtualized, there's no sense in going bare metal. Things like backup, DR and mgmt are simplified greatly.