Link to home
Create AccountLog in
Avatar of randolph batoon
randolph batoonFlag for United States of America

asked on

Windows 2016 Hyper V - static IP address changes on DC

We have a Windows Sever 2016; AD, Domain Controller; DNS; DHCP handled by Meraki MX64; Server has a static IP Address; we have several remote desktop users.
Tried to implement (add role) Hyper V. When adding the role and after rebooting server the static IP address for the Server is changed to another address and is listed as receiving it via DHCP; DNS also shows the change.
Tried this on a test server prior to live production server and the static IP Address did not change so tried it on the production server and now we have this issue; on removal of the Hyper V role the original static IP address returns.
Anyone have any idea.
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

If your server only has one NIC and you are setting up a virtual switch when you install Hyper-v then this is completely expected. The NIC is no longer available to the OS, as the virtual switch took it over.  Instead a new virtual NIC (meaning new Mac address, driver, and all) is in the OS and thus has the default settings any new NIC would in windows. Aka, DHCP, etc.  So this is TOTALLY expected.

A fee ithet tangential observations about your post.

Running Hyper-v on a DC is not supported and DOES break things beyond just the NIC. *Don't do it!*

Running RDS (remote users) on a DC is actively against best practice and also breaks a few things if you don't know what you are doing. And is impossible to secure properly also *don't do it!*

That is all.
Avatar of randolph batoon


Sorry, clarification: rdp users rdp to their desktop and need to know the address of the server in order to access resources (file shares);
we have only one server (non-profit so restricted budget) and so we have no choice but to implement Hyper V on this server.
The test server exactly duplicated roles on production server so we do not understand why on the production server the IP Address changed and not on the test server. It is essential for other reasons that server address not change.

Thank you for your comments. We need a solution that maintains ip address; did not want to go in to the virtual switch to make changes as this is beyond our expertise and since we cannot duplicate the issue on our test server we are seeking assistance.
Avatar of Cliff Galiher
Cliff Galiher
Flag of United States of America image

Link to home
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
will do; thank you for your assistance.
I would create a team (with the one NIC), enable converged networking and carve out a NIC for each role
Why can't you just change the network address after installing the hyper-v role?
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

Accept: 'Cliff Galiher' (https:#a42992745)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer