T
T
Tech2018-02-28 08:56:52
Virtualization
Tech, 2018-02-28 08:56:52

Withdrawal from Hyper-V infrastructure?

I inherited an office of 8 people and a zoo. Analysis of the current IT infrastructure is not encouraging. For example, Win Srv 2012 R2 as AD. Hyper-V is also raised there, on which linux spins as a gateway for the entire local network. I plan to extinguish this gateway and install an iron router.
In the list of network adapters of the win-server:
-two physical cards (in the properties of both ipv4 and ipv6 are disabled).
-two virtual cards. One of them with a configured Windows server address.
If I remove the Hyper-V role, will the virtual cards be removed? What pitfalls can be in general?
Or is it easier to leave hyper-v and just turn off the virtual linux?

Answer the question

In order to leave comments, you need to log in

2 answer(s)
S
Sergey, 2018-02-28
@bioid

I see one problem right away, when changing adapters, trust between AD and PCs can be lost.
Otherwise, make the router iron, and turn it on by shutting down the hyper-v machine. In the settings of the latter, specify NOT turn on on reboot and live with the new router. Then take on AD.
One at a time.

I
impvision, 2018-03-23
@impvision

I do not see a problem in the virtual gateway in principle.
Many questions - what kind of gateway, how are the interfaces wrapped, how does the virtual network work through the gateway?
Virtualization on Hyper-V means that first of all we “wean” the main OS from the external (WAN) network adapter and configure VLANs on the gateway’s internal interface as separate network adapters - that’s all, in this case, this alignment will throw the skates away only in the event of a nuclear war .
The downside of such a decision, which is wrong only in the fact that you can’t touch it? If he flies out, then it seems like with the entire infrastructure, from which it will be absolutely parallel for everyone - whether he exists or not.
You always need two pieces of iron - one fails, we put another.
As gateways, depending on the requirements, I used - m0n0wall, OPNsense, Juniper, Fortinet, sometimes Kerio Control - everyone felt great in Hyper-V (only OPNsense did not like the disk subsystem with default settings).
Have a nice day, everyone!

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question