User Profile
Carlos_Capellan
Brass Contributor
Joined 7 years ago
User Widgets
Recent Discussions
Re: WIndows 365 SSO preview disconnects on lock instead of showing lock screen
Hi DavidBelanger, Thank you SO MUCH for the detailed reply, I certainly appreciate the technical roadblocks you and the team are dealing with. Unfortunately, I feel this limitation substantially weakens the BYOD use case. In a mobile/WFH use case I would need to have an aggressive lock screen inactivity timeout, say 10 minutes, and I am concerned about getting very negative user feedback if we do this. A reconnect button helps, but does not solve this. I think to fully work around this limitation I would need to allow access to Cloud PCs only from corp-owned endpoints with inactivity timeouts enforced on the endpoints, but no timeout for the Cloud PCs themselves. But now we're losing part of the ease of use of the experience. I understand just surfacing the traditional RDP username/password prompt on the Cloud PC lock screen defeats all the SSO/passwordless auth methods you are trying to deliver. But I expect you will get this same feedback from many more customers that we still need a standard inactivity timeout experience with no reconnect needed. If there are any other approaches around this current limitation that I haven't considered here, a guidance or best practices page or blog post would be greatly appreciated! And still hoping this is a top priority on the roadmap!2.8KViews0likes0CommentsWIndows 365 SSO preview disconnects on lock instead of showing lock screen
HiChristiaan_Brinkhoffand team! We are loving the Windows 365 SSO Preview. It is a fantastic improvement but we have a major showstopper for deployment: when the session locks instead of the lock screen the session disconnects. Over all the years of on-prem RDP/AVD/etc., Windows has never behaved like this, unfortunately it is a poor user experience and I can't deploy it to my users like this. I understand why this is happening, today the SSO is happening outside the session and you will need to implement SSO unlock inside the session for this to work. I very much hope the team is hard at work on how to unlock an SSO session, otherwise I can't use one of the very best features, security or otherwise, of Windows 365!2.9KViews0likes2CommentsRe: App Sharing in Teams Meetings on Windows 365
Hi PavithraT, Congratulations on releasing this important feature for Windows 365! We were very happy to see it finally working after updating WebRTC. One additional question on this topic: Is the "Share any window from my taskbar" functionality supposed to be supported by Win365 Teams today? Or will this be enabled soon as a follow-on release? Thanks, Carlos1KViews1like0CommentsApp Sharing in Teams Meetings on Windows 365
HiPavithraTand the Windows 365 team! Just watched this month's informative AMA and, as suggested, I am reaching out about a key Teams on Win365 feature our team needs. We are going all-in on Windows 365 and so far, my users love their Cloud PCs! However, the single biggest complaint we get with our Cloud PCs is around the lack of application sharing in Teams meetings. We use ultrawide screens so today we can only share our entire screen, which is not legible in the meeting window. Any chance this is coming soon? We see it is launched for Citrix so hopefully Windows 365 is next! Otherwise, the meeting experience has been fantastic! Thanks! CarlosSolved1.2KViews1like2CommentsRe: How to re-enable Teams auto-update in Windows 365
Hi PavithraT! We are still encountering this issue (Teams MWI installed to Program Files with ALLUSER=1) on our Win 11 gallery images in July, one month after this post was made. When will the Win 11 gallery image come with Teams MWI installed using ALLUSERS=1 to go in the user profile? How can we tell which version of a gallery image we are getting when we deploy a new Cloud PC? Right now we are remediating this ourselves with our own Intune solution, but of course we would like to not have to run extra remediation steps that increase overall provisioning time. Thanks! Carlos177KViews0likes0CommentsWindows Autopatch: Patching Teams on Cloud PC from Win 11 gallery image
Hi Autopatch Team! We're very interested in Autopatch for our Windows 365 pilot. However, I'm a bit confused as to how Autopatch will patch Teams on Cloud PCs. The Cloud PC Windows 11 gallery image comes with the Teams Machine-Wide Installer; updating the Teams Machine-Wide Installer MSI is the only way to update Teams for per-machine installs. However, as stated in the Autopatch docs: "Windows Autopatch uses thestandard automatic update channelfor Microsoft Teams." This sounds like Autopatch can only work with per-user installs of Teams. So it seems like we need to uninstall the Teams Machine-Wide Installer on the Cloud PC Win 11 gallery image and do a per-user install instead for Autopatch to be able to handle Teams updates. Is that correct? Thanks in advance!Solved831Views0likes1CommentRe: Universal Print Connector registration failed
dnienhaushi there, for me the issue was that the machine I was trying to use it on was not AAD joined or AAD registered with our AAD tenant (it was just my personal home PC). When I tried on a different machine that was AAD joined (work laptop) I was able to register the printer with no issues. I did not see anything about the registration failures in the Sign-In logs for the AAD user I was using, so I can't say it was our Conditional Access policies that were blocking it (arguably, the CA policies were *not* blocking because I was able to sign in and get the register printers step). So, if you have the bandwidth, I'd say open a case and see if you can figure out what policy in the AAD tenant is blocking registering printers on non-AAD joined/registered machines. (Although to be fair, I'm only assuming AAD registered works, as it worked for me with an AAD joined machine) Hopefully we can figure this out! Carlos9.4KViews0likes2CommentsRe: Universal Print Connector registration failed
HiRani_Abdellatif,added the Printer Administrator role to my account per the Powershell commands you sent along, waited about 2 hours so I'm positive the role is applied to my account, and still getting the exact same 403 Forbidden response when I try to register the printer in UPC. Anything to try next?9.7KViews0likes3CommentsUniversal Print Connector registration failed
No luck so far! Got promo code added to O365/AAD tenant. Installed UPC on home Win 10 Pro 1909 machine. Logged in with corp AAD non-GA user which has UP license provisioned. Attempting to register printer fails each time, Event Viewer shows I get a 403 Forbidden event. Home printer is a Brother MFC-J825DW. Did I miss a provisioning step?9.9KViews1like13Comments