Official Download links for Microsoft Edge Stable Enterprise
I'm not 100% sure it's final but anyone who wishes/wants can test it. Microsoft Edge Stable Enterprise X64.msi http://go.microsoft.com/fwlink/?LinkID=2093437 X86.msi http://go.microsoft.com/fwlink/?LinkID=2093505 MicrosoftEdgePolicyTemplates.cab http://go.microsoft.com/fwlink/?LinkID=2099616 MicrosoftEdgeIntunePolicyTemplate.cab http://go.microsoft.com/fwlink/?LinkID=2099617 macOS.pkg http://go.microsoft.com/fwlink/?LinkID=2093438 Blocker Toolkit to disable automatic delivery of Microsoft Edge https://docs.microsoft.com/en-us/deployedge/microsoft-edge-blocker-toolkitMicrosoft Teams Secondary Ringer is now generally available on Windows 365
We are happy to announce that Microsoft Teams Secondary Ringer is rolling out this week to the public on Windows 365. Secondary Ringer is a voice calling feature that allows Teams to signal an inbound call on multiple devices. Previously, only one sound output device was used to notify users of an incoming Teams call. For example, if the default device was a headset, the user may miss incoming calls when not wearing it. Secondary ringer allows Teams to signal the arrival of an inbound call on two devices, which means you can have two sound output devices of your choice to ring (e.g., your PC and headphones) when there is an incoming Teams call. Setting a Secondary Ringer To set a secondary ringer, go to the “Devices” section of Teams settings and select a device from the “Secondary Ringer” drop-down list. Secondary ringer will not work: If you are not connected to more than one suitable device, you cannot set a secondary ringer. If a device is not online (like a Bluetooth headset that is powered off), it cannot be used either. If you remove your PC from a situation where the secondary ringer is unavailable (for example, unplug a laptop and move out of the range of the headset’s Bluetooth connection), Teams removes the secondary ringer, and you’ll have to reconfigure it after you reconnect. Getting Started To use Microsoft Teams Secondary Ringer, the minimum Windows Desktop Client version 1.2.3004 is required to enable the feature on Windows 365. Set up Teams on Windows 365 Microsoft Teams comes included in the Windows 11/10 images optimized for Microsoft 365 apps. For more information on how to enjoy the best Teams experience, refer to the Teams on Cloud PC documentation.
Problems authenticating from Remote Desktop Client
Hello, Does anyone have any suggestions for problems connecting from the RDP client? I downloaded the app from https://windows365.microsoft.com/ and used the subscription URL. Then when I login I get the following error when using Windows Hello: An authentication error has occurred (Code: 0x8007013d). If I instead use the Password it gets to the point of Securing Remote Connection and then it pops up the error: The logon attempt failed. The same credentials work fine initiating the connection from the browser.
Windows 365 disconnects on lock, possible to change timeout?
We enabled the SSO/MFA preview and now when our Windows 365 RDP sessions time out they are booting the user off of the RDP session with the message "Windows Remote Desktop Client - You were disconnected because your session was locked." This is apparently by design because of the ability to use passwordless authentication and the fact the lock screen can't support this. The timeout appears to currently be 15 minutes which is fairly short if the VDI is not your only system you are working in. I am wondering if anyone knows of a way to extend this timeout to 30 or 60 minutes. This timeout does not occur if the SSO option is disabled in the provisioning policy. This is on Windows 365 not Azure VDI so there are no backend RDP server settings to change. Also, if anyone at Microsoft is reading this why does it pop up 2 of the exact same message boxes at the same time for this disconnection message? Kind of annoying.
