RC Compatibility with Windows 365 Cloud PCs
T
Trent Bartley
J
Jared Roy
At the risk of bring ignorant, what issue does this solves?
Just seems the point of the RC is mobile devices - and Cloud PCs would be the least mobile. Between RMM/intune/Built in tools, Cert managment, and point DNS servers would be very simple.
I ask this from an education standpoint - I would like to know the perks that I am not understanding. I am likley missing something, or not understanding a certain perk.
It may also be worth elaborating the business case and need/issue you are facing, as that would get this request more traction.
Minetta Gould
Jared Roy: Great question — and you’re right to point out that Roaming Clients are generally designed with mobile/off-network devices in mind. I'm going to take a couple leaps in assumption here for Trent, because he happens to work at DNSFilter (hi Trent 👋) and I'm tangentially aware of why he made this post:
Where Windows 365 Cloud PCs become relevant is in organizations moving toward a hybrid or fully cloud-based desktop model. Even though Cloud PCs aren’t “mobile” in the traditional sense, users still connect from many different locations and networks. In that scenario, the Roaming Client provides:
-Consistent policy enforcement regardless of where the Cloud PC session is accessed from
-Per-user reporting to tie activity back to the right identity, not just an endpoint
-Coverage gaps filled where built-in tools, cert management, or point DNS may not provide the same depth of visibility or filtering granularity
Right now, as you’ve seen, Cloud PCs aren’t officially supported because of the way their networking blocks the IPv4 connectivity checks our client depends on. There are workarounds, but we can’t guarantee consistent behavior until Cloud PC support is formally added.
Your point about sharing the business case is spot on — the more detail customers provide about why Cloud PC support would matter in their environments, the more traction this request will gain with our product team!