Where are the "new graphics acceleration options for virtualized environments"?
Your article promises new graphics acceleration options to replace Remotefx. Where are they? Discrete Device Assignment is not an option for us as the hardware needed to run this is in excess of $20,000 per server and then there are additional per user licensing costs on top of that from the GPU vendor. We were successfully running hyper-v vms with remote desktop session host on Server 2016 and they were running RemoteFX. Now we have Server 2019 and you have deprecated RemoteFX without providing any valid solutions or replacements. We need a work around so we can run RemoteFX on Server 2019 and on our RDSH vms. Please advise.
I am not happy with Microsoft's decision to move away from RemoteFX. I still run Virtual Machines that require graphics acceleration. DDA forces us to upgrade our already modern graphics cards and is more difficult to set up. I will not upgrade my infrastructure just to be able to have a niche tool that is absolutely necessary for my infrastructure. I might look into an open source alternative or switch to physical machines for my remote graphical infrastructure. Sounds backwards right? That's what Microsoft is these days. Backwards. Backwards with technology.
I have hundreds of on premise VDI's built around Hyper-V servers with thin clients running RDP utilizing RemoteFX. I was a complete devastated to learn that Microsoft was suddenly forcing all users to abandon RemoteFX in one of the recent Windows updates. And even more so to read that it cannot be used past Feb 2021, see Microsoft's link below. This is the biggest bait and switch I have ever seen.
Perhaps Microsoft cannot find a way to use RemoteFX in their hosted Azure solutions but, I don't see the need for all of the loyal longstanding Hyper-V customer to have to suffer and look for some outrageous overpriced DDA solution as an alternative.
I guess that's what happens when the loyal small to medium businesses that no longer matter to the bottom line.
Current availbility is only for DDA, here is good comparison on those: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/plan/plan-for-gpu-acceleration-in-windows-server
Of course, you can still run Windows Server 2016, it is supported until 2025.
The new option might be GPU-Partititioning (GPU-P) - while the technology is there and used in Azure/Windows Virtual Desktop, there is no official support in WS2019 right now (though some components are shipped).
See this blog for some good summary referring the Windows Server summit session on that: https://www.brianmadden.com/opinion/RemoteFX-vGPU-put-out-to-pasture-as-Microsoft-RDP-grows-up
Also note that graphics acceleration capabilities are available without the need to invest in server hardware and no GPU-vendor specific licensing costs in Windows Virtual Desktop on Azure - and in fact GPU-P (with the new NVv4 VM types)
We have to do this on premise for a client with sensitive data. We cannot use WVD. Microsoft promised that they "We're developing new graphics acceleration options for virtualized environments." Where is this new option for Server 2019 without spending $50,000 for a server with GPU?
As mentioned before, what has been developed so far is in WVD and not yet available for WS2019. As far as I know no specific ETA was promised and also no specific price range for a future solution. What stops you from using WS2016 since you obviously do want to stick the old RemoteFX vGPU feature?
We have built a hosting solution around RDSH and have many clients using it now. We didn't know that Microsoft was going to pull RemoteFX out of Server 2019 and we built that so that the users would have a Windows 10 like experience. Users had no performance issues when we had RemoteFX and now with Server 2019 they frequently complain about the poor graphics performance. I don't understand the reasoning behind the upgrade to 2019 with a downgrade in performance. From where I'm standing it looks like Microsoft and NVida are together in this to make money since they left and other RDSH customers us with no reasonably priced options and poor performance.
IMO it makes no difference if WS2016 or 2019 is used, both will not really have a Windows10-like experience - this where Windows 10 VDI and especially Windows 10 Multi-Session/WVD is for.
The reasoning is generally that the product team took it out - or more exactly - did not integrate it anymore - in order not having to support the code base for something that is no longer developed, will not work for Linux VMs ever - and has some by-design security challenges that can/will never be fully resolved - see https://support.microsoft.com/help/4570006 - and finally since 2016 is still available as alternative.
You can also give feedback directly to the PG via Uservoice: https://windowsserver.uservoice.com/forums/295050-virtualization
I would not assume that the motivation is to make additional money - as you mentioned before DDA and RemoteFX are in a different league from a pricing perspective, it is more likely even a decision that will likely hurt Microsoft's revenue since the alternatives in market are also provided by Citrix (on Xen) or VMware. Sometimes those decisions that lead to hard cuts and changes in direction have to be done because of changing market conditions, even though it will not be satisfying for all customers.
I can fully understand your frustration since you already have build this environment on WS2019 - and this does not change the fact that it was announced before WS2019 launch that those features will be removed, and any subsequent development will only be added to the next incarnation of Windows Server since WS2019 will not get any feature updates .
Hello - Janosch
I read your response to the others that have spent much time and money investing in HyperV VDI and was amazed at the answer. My company works exclusively in K12 and we were pushing for the past 4 years, using HyperV VDI for their AutoCAD and Adobe classes. We read that MS was dropping RemoteFX but replacing with GPU Partitioning. So now you have no option we can use that is acceptable. DDA is not and saying Azure is not. Everyone knows you did not provide GPU partitioning to try to force Azure so we have to pay SAS. You guys really need to consider your long time customers pushing your solution and provide us now a GPU sharing option. I am sitting in an Adobe class now that is suffering because of this. If it is in Azure/Server then give us the same for local 2019 server.
And this feedback needs to be directed to the Product group responsible for Windows Server, I mentioned the link above where the PG is looking at feedback: Virtualization: Hot (149 ideas) – Windows Server (uservoice.com) This is not something I can decide on or where I would have influence on - and currently there is no other information I can share as what I mentioned already on this thread.
Hello @JoeRainero ,
Thanks for your query!
As I see this post has not got a reply or solution, you might want to check on the Tech Community as well. Please see this forum: https://techcommunity.microsoft.com/t5/windows-server-for-it-pro/bd-p/WindowsServer