Naturally Reddit won't help me because everyone there is a little bitch and I'm at my wits end with this. I'm trying to enable nested virtualization on a couple of domain-joined Windows Server 2022 hosts, and to do this I need to shut them off. Every time I shut them off, however, they forget their computer name, what domain they've joined and their static IPs. I've reset their network adapter several times and always had the same results, and even when I have the name, domain, and IP set (alongside successfully issuing commands to enable nested virtualization support), I can't install the Hyper-V role on the servers. This is for a school lab and I'm going to fail it if I don't figure it out, any advice is appreciated.
>>1561314they probably didn't help you because most regular people don't even know wtf hyperv is.i do know what it is, i work in this field, but i don't do windows server administration (yet) and just do basic helpdesk so i have no good answer for you offhand.if i had to give some answers, first i'd check whether the vms are persisting anything or if it's just the stuff you listed, if they're not persisting anything it's probably some sort of setting that's causing them not to retain changes. if the hyper-v role isn't installing, check windows event viewer to see if there's anything relevant there. try asking like five different LLM services about the issue and see if any of them point you in a meaningful direction (if you find a relevant log entry, feed them that).worst case, it could be a bug, just nuke everything and start over.i would strongly advise you to talk with your professor about this. in most universities, you're encouraged to go to your professor with issues like this and good ones will socratic method you in the right direction without just giving you the answer. if the thing is due too quickly, ask for an extension; sometimes they'll do it for free, sometimes they'll dock a grade level, some won't do it at all if they're fags, either way it's at least a shot.
