Set static ip for Hyper-V Server 2016 virtual ethernet adapter.
-
Already tried changing the IP address using Windows Admin Center?
-
Probably faster to reinstall the host then import the VMs.
-
@jaredbusch Really don't know what they did. We figured out the host was using DHCP because after an outage some VMS were not coming back up and we had to remote in.
Tried connecting via the dns name, just to find out the static dns entry does not work because the server had been setup to use dhcp without even a reservation.
So we are trying to set the Hyper V host to have a static ip and here we are.
-
Did you reinstall the host OS yet? Takes only a few minutes, and then a few minutes to reconfigure the host settings, then a few minutes to import the existing VMs...
-
@obsolesce said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
Did you reinstall the host OS yet? Takes only a few minutes, and then a few minutes to reconfigure the host settings, then a few minutes to import the existing VMs...
Not even remotely feasible in this environment. They don't have any swing space to do anything of the sort. Nor can they be taken offline mid day. It just wasn't built for that kind of flexibility.
-
@scottalanmiller said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
@obsolesce said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
Did you reinstall the host OS yet? Takes only a few minutes, and then a few minutes to reconfigure the host settings, then a few minutes to import the existing VMs...
Not even remotely feasible in this environment. They don't have any swing space to do anything of the sort. Nor can they be taken offline mid day. It just wasn't built for that kind of flexibility.
No swing space needed, so long as the OS is it's own partition, typically the C drive, where all the VMs live on the D drive. You pop in the USB stick, and reinstall the OS. Once back, you right-click in Hyper-V Manager and import the VMs that are still there in the D drive. You don't format that D volume when you reinstall, only C. YOu leave D alone so it's there when it's back up.
It shouldn't take more than 30 minutes total, easily done end of day or after hours. Or, bring up another Hyper-V host to live-migrate to (if you have the space) to prevent any down time.
There are a lot of options rather than spending weeks figuring out such a dumb issue.
-
@obsolesce said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
You pop in the USB stick,
Already a problem, no local tech. Can't ask the site to do something like that unless there is a full blown outage underway.
-
@obsolesce said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
There are a lot of options rather than spending weeks figuring out such a dumb issue.
Having to bring in a local tech or get a swing machine are actually much more intensive than looking at it remotely for a while. But seems doubtful that it will take weeks. Only has had a few minutes of being looked at, and only today.
-
@scottalanmiller said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
@obsolesce said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
You pop in the USB stick,
Already a problem, no local tech. Can't ask the site to do something like that unless there is a full blown outage underway.
iDRAC/iLO/etc, USB stick not needed if that's available. I was just giving an example case, not an exclusive item.
-
@scottalanmiller said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
@obsolesce said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
There are a lot of options rather than spending weeks figuring out such a dumb issue.
Having to bring in a local tech or get a swing machine are actually much more intensive than looking at it remotely for a while. But seems doubtful that it will take weeks. Only has had a few minutes of being looked at, and only today.
Oh, didn't realize it was like that. No local IT, no other available infrastructure or anything kind of limits things a lot.
-
@obsolesce said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
@scottalanmiller said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
@obsolesce said in Set static ip for Hyper-V Server 2016 virtual ethernet adapter.:
There are a lot of options rather than spending weeks figuring out such a dumb issue.
Having to bring in a local tech or get a swing machine are actually much more intensive than looking at it remotely for a while. But seems doubtful that it will take weeks. Only has had a few minutes of being looked at, and only today.
Oh, didn't realize it was like that. No local IT, no other available infrastructure or anything kind of limits things a lot.
Yeah, a LOT. If we were local and it was one of two (or more) machines, yeah, we'd happily reinstall. As it is, we are scared of the backup device failing. Which isn't terrible as it is ONLY a backup device. But taking the server offline... we are pretty dependent on it.
