Hyper-V Server 2016 to 2019 in-place upgrade failing

DavidYorkshire 91 Reputation points
2021-07-26T14:24:23.607+00:00

I have a test server (Dell Poweredge R710) running the free Hyper-V Server 2016. It's a very simple standalone setup - no shared storage (although it is domain-joined).

I am trying to do an in-place upgrade to Hyper-V Server 2019 - I'm shifting all our Servers to 2019, and it would make things easier for patching, etc, if this one was on the same version. When I run the installer from the command line it fails, and looking at the log file shows this as the cause:

<CompatibilityInfo BlockingType="Hard"/><Message Text="You have the Remote Desktop Virtualization Host (RDVH) role installed on this server. After you upgrade, you won’t be able to add the RemoteFX 3D video adapter to virtual machines."/>

It's just a test server running the standalone VMs I use for trying things out, so it's not a, RDVH host, and RemoteFX is not used or relevant.

Anyone know how to get around this? I could of course do a clean install but that's extra hassle.

Thanks

Windows Server 2019
Windows Server 2019
A Microsoft server operating system that supports enterprise-level management updated to data storage.
4,030 questions
Windows Server 2016
Windows Server 2016
A Microsoft server operating system that supports enterprise-level management updated to data storage.
2,633 questions
Hyper-V
Hyper-V
A Windows technology providing a hypervisor-based virtualization solution enabling customers to consolidate workloads onto a single server.
2,850 questions
0 comments No comments
{count} votes

11 answers

Sort by: Most helpful
  1. Anonymous
    2021-07-26T14:54:11.677+00:00

    The much simpler / safer method is to export / copy the VHDs to removable, clean install the new OS, patch fully, add hyper-v role, import virtual machines.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  2. DavidYorkshire 91 Reputation points
    2021-07-26T14:55:47.3+00:00

    Hi,

    Yes, I could do but as I say it's only a test server so I'd rather go with the quicker / easier upgrade option if possible - if the VMs get broken it isn't a major issue.

    Thanks

    0 comments No comments

  3. Anonymous
    2021-07-26T14:59:47.083+00:00

    Sounds good then, I'd check the logs for clues.
    https://learn.microsoft.com/en-us/troubleshoot/windows-client/deployment/windows-setup-log-file-locations

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

  4. DavidYorkshire 91 Reputation points
    2021-07-26T15:01:56.237+00:00

    It's the RDVH role issue - which apparently was included in Hyper-V Server 2016 but not 2019. What I don't know is how to get around that (the role is not needed).

    0 comments No comments

  5. Anonymous
    2021-07-26T15:09:13.553+00:00

    Probably the work-around is to clean install it.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.