Hyper-V Compatibility | Voters

Hyper-V Compatibility

launched

Mikey @DNSFilter

Upgrade the Roaming Client to be compatible with Microsoft Hyper-V. We'd like to get feedback on this issue and determine demand from our user base.

December 13, 2019

Nick Saunders

marked this post as

launched

After a successful beta, WinRC v1.12.0 with Hyper-V compatibility is now available in the Production channel.

https://dnsfilter.canny.io/changelog/january-10-2024-winrc-v1120-production-release-new-installs-hyperv-support

Nick Saunders

marked this post as

beta

WinRC v1.12.0 with Hyper-V compatibility is now available to all users in the new Beta release channel. For details please see our Changelog https://dnsfilter.canny.io/changelog/december-18-2023-winrc-v1120-beta-release-hyperv-support

Please let us know on this post or via email if you face any issues with the beta.

Steve Staden

We now have an early access build available for anybody who would be interested in testing out the support for Hyper-V. Feel free to like this comment or email [email protected] and we will get you access.

Florian

Steve Staden: It would be great, to get access. Thank you.

Steve Staden

Florian: Should be in your email now, thanks for the interest!

Steve Staden

As promised, we wanted to follow-up from 11/20 on a timeline for releasing a fix to address the Windows Roaming Client working on Hyper-V. We have identified and written a probable fix and have started our regression testing efforts to ensure a production ready release (v1.12.0). The timeline we’re looking at is:
Week of 12/11 - Early access build available to any customers interested in validating in their environment. Please email [email protected] with “Hyper-V Early Access” in the subject line.
Week of 12/18 - Based on successful testing and early access feedback, it is likely that the week of 12/18 will see a release candidate completed.
TL;DR - we believe we have created a fix and now we will be working through the appropriate release cycle step by step until it’s fully certified for GA production.

Steve Staden

marked this post as

developing (live in <90 days)

First off, we recognize the challenges with Hyper-V and apologize for the issues experienced and our slow response to address running the Windows Roaming Client on Hyper-V systems. Although many of you have voted on this issue in our tracking system along with raising concerns about it not working in forums, our team mistakenly reviewed the request as an enhancement (it was upon original request) instead of recognizing evolution and increased use of Hyper-V since and the less than ideal workaround to function on Hyper-V.
As a result, our Engineering team has begun working on it this (Nov 20th) afternoon. Along with development work, their effort includes investigating feedback suggested from both Hyper-V users as well as our own research to ensure we can provide a solid and reliable solution moving forward. It is our commitment that after this initial week of work, our Engineering team will be able to provide a confident date for release/fix on November 27th. We will update this post at that time.
This has also highlighted gaps in how we listen and respond to our customers and industry experts. To that end, we are also:
1.) Going through our feature request system to ensure no other bugs are categorized as enhancements
2.) Reviewing our support process to ensure repeat items without a proper solution are prioritized
In addition, we have recently hired a Customer Experience leader who is chartered to work across DNSFilter to enhance our view of customer insights and shore up processes to amplify your voice.  We have also started a Customer Advisory Board to ensure we are listening to our customer’s needs along with sharing our roadmap. If you would like to be considered for the Customer Advisory Board please email [email protected] with CAB in the subject line.

Steve Staden

Merged in a post:

Windows Roaming Client and Virtual Machines

Mikey @DNSFilter

The Windows Roaming Client is not designed to allow usage of virtual machines. We'd like to gauge the need for such an improvement.

November 20, 2023

Joseph J.

This is rather sad and I feel a black eye for DNSFilter (since competitors don't seem to have this issue). Why is making the client compatible with a growing number of Windows installations (Microsoft is using the HyperV services for more and more security in the OS) even a feature request? This should just be done.

Graham

Update please. This thread is 4 years old and has not been addressed. Removing Hyper-V is not a solution. Please make the roaming client functional when Hyper-V is installed.

Sebastian

Is it possible to get an update on this issue?

Sebastian

Hello, any news on this? Hyper-V is an essential component to a lot of Microsoft virtualization-based security and this incompatibility is still causing issues for us.

Nachman

Sebastian: Im not sure if this is open or closed its a bit confusing!

→