@Dashrender said in Hyper-V Guest - Unidentified Network:
@pchiodo said in Hyper-V Guest - Unidentified Network:
@Dashrender I totally agree, and if this was a required production server, I'd be right on board. This particular server is not required for production, and I have moved its load to another Hyper-V server. Yes, I would like it back in the mix for load balancing and as a backup, but I still would like to take a little time to try and nail down the exact issue and solution before I just wipe it and reload.
Right - but you missed the part about how this is possibly not beneficial to your company.
Like you, my 2003 server isn't in production either, I'm trying to make a CYA fully working/tested backup to put into the safety deposit box. Fixing the boot problem fully doesn't really help my company in any way since I have a usable solution for the boot issue. Fixing it takes me away from doing something of real value for my company, the same goes for you and solving this issue.
In the end, you and I both personally gain by having additional knowledge we didn't have before, but what we don't know is if that knowledge will have any outward value in the future. While your situation has a higher likeliness of having future value, people are still deploying Hyper-V 2012, and it's likely a very similar setup probably exists in Hyper-V 2016. My situation is completely different in that 2003 is old, does booting in a completely old manner - using P2V that's a mostly dead situation (very little P2Ving done anymore, most of it was already done), so I have very little chance of ever using this knowledge in the future.
Agreed! In my particular case, I can see this happening again. We will likely not move off Server 2012 for the next 2-3 years depending on how fast our 3rd party apps adopt server 2016. This being the case, having a solution that takes minutes vs hours would be very valuable.