Forum Widgets
Latest Discussions
How to re-enable Teams auto-update in Windows 365
In someWindows 365 Cloud PCs, the ability for the installed Teams client to automatically update has been affected along with the ability to check for updates.To rectify the problem, Teams Machine Wide Installer and the Teams client must be uninstalled, and then reinstalled. Reinstalling Teams can be a difficult task to accomplish if one doesn’t wish to disturb end users at work. Further complicating the matter is that the Teams client automatically installs only on user logon. To lower the complexity of fixing the problem while not impacting end users, we have written a Proactive Remediation package that takes end users into account. More information on Proactive Remediation Link to the Teams Fix - Proactive Remediation Package The detection script is checking to see if the Teams client is installed in the Users’ profile, which exists under c:\users\[user name]\appdata\local\Microsoft\Teams. If it is not found there, it will return non-compliant. The remediation script first checks to see if it has successfully run to completion before. If it has not, it then checks to see if a user is logged in and in an inactive state. If the user is logged in and active, the script exits, and Proactive Remediation will try again later. If the user is not logged in or active, the remediation process begins. The remediation script downloads the latest version of the Teams Machine Wide Installer MSI, uninstalls the Teams client, uninstalls the existing Machine Wide Installer installation, checks for a Registry Key than can cause issues with Teams client installations, then checks the user state again. If the user is not logged into their Cloud PC, the script will return compliant. Once the user logs back into their Cloud PC, the Machine Wide Installer will trigger the Teams client installation automatically. If the user is logged in but inactive, the remediation script creates a child PowerShell script, and XML file used to create a scheduled task, and registers the scheduled task that will initiate the Teams client installation when the user reconnects to their Cloud PC. All files are downloaded to C:\Windows\Temp. The amount of time that the scheduled task stays active is configurable in the Remediation script by modifying the $DateOffset variable. The child script checks for the existence of files it is supposed to remove, and this is done to ensure that the Teams client isn’t reinstalled every time the user connects. If the files exist, the script assumes it hasn’t successfully run before and launches the Teams client installer. Once the installation is complete, the script will attempt to delete the scheduled task. If the user doesn’t have administrative rights, it will not be able to remove the scheduled task and it will expire at its given time. The script will then remove the files used in this process. If the user does not reconnect to their Cloud PC by the time the scheduled task expires, the remediation script will run again and recreate the scheduled task. All the scripts in this solution generate their own logs to help admins troubleshoot issues. These logs are all written to C:\Windows\Temp. These logs are: Detection Script - Teams-MWI-detect.log Remediation Script - Teams-MWI-remediate.log Child Remediation Script - Teams-MWI-remediate-child.log The remediation script automates the whole process but if you want to manually fix this issue, you can do so by following these steps: On the Cloud PC, navigate toSettings>App>Apps and features. Search for Microsoft Teams. UninstallMicrosoft TeamsandTeams Machine-Wide Installer. Download the latest version of Microsoft Teams from here. Open a command prompt and install the Teams client using the following command: msiexec.exe /I %Filepath to the downloaded Teams MSI% ALLUSERS=1 Restart the Cloud PC. The Teams client is now installed with automatic updates turned on.177KViews1like2CommentsHow do I turn off read only mode in Powerpoint
Hi, I have been working on a PowerPoint presentation slideshow. I have been using the same PowerPoint for the last 7 years ie adding new slides each year. However, this year It's not letting me save my work and states can't save because it is in read only mode. I still have another 200 slides to add, but have had to redo my work for the last 3 days. Since it not saving my work. Please advise. I need to have this slideshow done by next week. BTW: I've tried following instructions via the internet etc.Helen_TardibuonoNov 10, 2022Copper Contributor139KViews0likes7CommentsWindows 365 and Multiple Monitors
I have searched far and wide for information on how to use the Windows Remote Desktop client to use the supposedly supported multiple monitor configuration but without any success. We reached out to Microsoft support responded that this functionality isn't supported. Documentation seems to suggest that support for it does exist. Using 64 bit version of the Microsoft Desktop Client, per the recommendations in the Windows 365 client web page. Not sure where to go here, anyone have any idea or suggestions? Anyone get this to work? Update: Adding the referenced documentation:Get started with the Windows Desktop client | Microsoft DocsSolvedDodge-1350Jan 21, 2022Brass Contributor72KViews0likes15CommentsMicrosoft 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.63KViews1like10CommentsOptimizing RDP Connectivity for Windows 365
The use of VPN or Secure Web Gateway (SWG) client software or agents to provide tunneled access to On-Premises resources in addition to providing protected internet access via a cloud based Secure Web Gateway (SWG) or a legacy VPN & on-premises proxy path is very commonly seen in Windows 365 deployments. This is especially the case when deployed in the Microsoft Hosted Network (MHN) model where the Cloud PC is located on a network with direct, open high-speed internet available. The more modern, cloud based SWG solutions fit very well with this modern Zero-Trust approach and generally perform at a higher level than traditional, legacy VPN software, where internet browsing is hairpinned through On-Premises proxies and back out to the internet. As we have many Windows 365 customers using such solutions as part of their deployment, there are some specific configuration guidelines which are outlined in this post which Microsoft recommends are applied to optimize key traffic and provide the highest levels of user experience. What is the Problem? Many of these VPN/SWG solutions build a tunnel in the user context, which means that when a user logs in, the service starts and creates the tunnels required to provide both internet and private access as defined for that user. With a physical device the tunnel is normally up and running before or shortly after the user sees their desktop on screen, meaning they can then quickly get on with their work without noticing its presence. However, as with any virtualized device which needs a remote connection to access, the above model poses several challenges: 1. Additional Latency Firstly, the remote desktop traffic is latency sensitive, in that delay to the traffic reaching its destination can feasibly translate into a poor user experience, with lag on actions and desktop display. Routing this traffic through a tunnel to an intermediary device to reach its destination inevitably adds latency and can restrict throughput regardless of how well configured or performing said device is. Modern SWG solutions tend to perform at a much higher levels than a traditional VPN/Proxy approach, but the highest level of experience is always achieved via a direct connection and avoiding any inspection or intermediary devices. Much like Teams media traffic, the RDP traffic in the Windows 365 case should be routed via the most optimal path between the two endpoints so as to deliver the very highest levels of performance, this is almost always the direct path via the nearest network egress. 2. RDP Connection Drops An additional challenge comes from the use of user-based tunnels. As the user initiates a connection to the Cloud PC, the connection reaches the session host without issue and the user successfully sees the initial logon screen. However, once the user login starts, and the client software then builds the tunnels to the SWG/VPN for the user, the user then experiences a freeze of the login screen. The connection then drops, and we have to go through the reconnection process to re-establish the connection to the Cloud PC. Once this is complete, the user can successfully use the Cloud PC without further issue. Users however may also experience disconnects of the remote session if there is any issue with the tunnel, for example if the tunnel temporarily drops for some reason. Overall, this doesn’t provide a great user experience with the Cloud PC, especially on initial login. Why does this occur? It occurs because the tunnels built to route internet traffic to the SWG generally capture all internet bound traffic unless configured not to do so, a forced tunnel or ‘Inverse split tunnel’. This means the initial login works without issue but as soon as this tunnel is established upon user logon, the RDP traffic gets transferred into it and as it’s a new path, requires reconnecting. Equally, as the traffic is inside this tunnel, if the tunnel drops momentarily and needs to reconnect, this also causes the RDP session to require reconnecting inside the re-established tunnel. In the diagram below, you can see a simplified representation of this indirect connectivity approach with a forced tunnel in place. RDP traffic has to traverse the VPN/SWG resources before hitting the gateway handling the traffic. Whilst this is not a problem for less sensitive traffic and general web browsing, for latency critical traffic such as Teams and the RDP traffic, it is non-optimal. What’s the Solution? Microsoft strongly recommends implementing a forced tunnel exception for the critical RDP traffic which means that it does not enter the tunnel to the SWG or VPN gateway and is instead directly routed to its destination. This solves both of the above problems by providing a direct path for the RDP traffic and also ensuring it isn’t impacted by changes in the tunnel state. This is the same model as used by specific ‘Optimize’ marked Office 365 traffic such as Teams media traffic. The diagram below shows this direct path being taken to the RDP Gateway for the RDP traffic whereby any other internet/On-Premises bound traffic continues via the VPN/SWG. What exactly do I need to bypass from these tunnels? The critical traffic which carries the RDP stream is contained within the following endpoints: Wildcard FQDN: *.wvd.microsoft.com IPs: WindowsVirtualDesktop Service Tag. You can obtain the IP information for the WindowsVirtualDesktop tag manually via the Azure IP Ranges JSON file. However, to make this process simpler and quicker, my talented colleague Donna Ryan has written a PowerShell script to obtain this information and format it in a CSV format which is what’s needed for most solutions. In some network equipment/software we can configure bypass using wildcard FQDNs alone, and we’d recommend that this method is used if available, as the FQDN does not change over time. However, some solutions do not deal with wildcard FQDNs so it’s common to see only IP addresses used for this bypass configuration. How do I implement the RDP bypass in common VPN/SWG solutions? Microsoft is working with several partners in this space to provide bespoke guidance but thanks to assistance from our friends at Zscaler, the guide for bypassing the RDP traffic in the Zscaler Client Connector can be found below. We’ll add detailed guidance for other solutions here as we get them confirmed. Zscaler Client Connector In some network equipment/software we can configure bypass using FQDNs alone, however it’s common to see IP addresses used for this functionality and this is the case for use with the Zscaler Client Connecter and Tunnel 2.0 which can do the bypass very efficiently using the ‘Hostname or IP Bypass for VPN Gateway’ function. a. Firstly, we’d recommend you are running the latest version of the Client Connector available to ensure you have all the latest updates from Zscaler. b. Next, you’ll need to obtain an up to date list of IP addresses and get them into the right format to cut and paste into the Zscaler Client Connector Portal. The PowerShell script found here will provide this information for you in the right format programmatically. It outputs a CSV file which you can then use ‘Select All’ to copy the contents after opening in notepad. c. In the Zscaler Client Connector Portal go to ‘App Profiles’ then choose the policy to be applied to the Cloud PCs and click Edit d. In the App Profile you’ve selected, copy and paste the IP addresses from step two into the ‘HOSTNAME OR IP ADDRESS BYPASS FOR VPN GATEWAY’ field and click the plus sign. Within a few seconds the IP addresses should be successfully added to the configuration. e. It is also required to offload two IP addresses used for critical communication to the Azure fabric so these should be added to the configuration also. 169.254.169.254 - Azure Instance Metadata Service endpoint 168.63.129.16 - Cloud PC Health Monitoring f. Once this is done, simply update the policy on the Zscaler client connector. If you have persmissions you can do this instantly in the More > About section of the client connector. If Zscaler is already connected, you’ll find a disconnect occurs if this is successful as the traffic gets redirected out of the tunnel. Once reconnected it will remain outside of the tunnel. Other VPN/SWG solutions Microsoft is currently working with other partners in this space to provide detailed guidance for other VPN/SWG solutions and will list them here as they are complete. Please let us know in the comments if you’d like us to list a particular solution and we’ll aim to prioritize based on feedback. FAQs: Q: In a Microsoft Hosted Network deployment, is there anything else I need to do? A: Unless the local firewall is configured to block access to the IP addresses noted, there should be nothing else required, the network the virtual NIC sits in has direct, high speed connectivity Microsoft’s backbone and the internet. Q: In an Azure Network Connection scenario, is there anything further I need to do? A: In this scenario the recommended path for the traffic is directly out of the VNet into Microsoft’s backbone. Depending on the configuration it may require allowing the IP addresses noted in this article through a firewall or NSG. The WindowsVirtualDesktop service tag or FQDN tag may help with automating rules in firewalls or configuring User Defined Routing. Q: Do I need to configure the bypass on just the Cloud PC? A: It is strongly advised that the bypass is applied to both the Cloud PC and the connecting client if that also uses the SWG/VPN to connect. If both are using the same configuration profile then this should happen automatically. Q: How often do the IP addresses Change? A: The Gateway addresses change roughly once a month. We aim to improve the script over time to provide better assistance with automation of a check for changes in this data. Q: Can I add more than the RDP traffic to the bypass. A: Microsoft only provides IP addresses for the RDP connectivity at present. However if your solution is capable of configuration by FQDN alone, then you can add other service endpoints to your optimized path, these can be found on this Microsoft docs page. Q: Im using a true split tunnel, does this impact me? A: The above advice is for a forced tunnel scenario (inverse split tunnel) where the default path is via the tunnel and only defined exceptions are sent direct, which is often referred to as a split tunnel in common parlance and is the most commonly seen deployment model of such solutions. However a split tunnel in the technically accurate sense of the words, where the default path is the internet and only defined endpoints (such as corp server ranges/names) are sent down the tunnel, shouldn’t need such configuration as the RDP traffic should follow the default path to the internet. Q: Does this also optimize RDP shortpath? A: RDP shortpath for Public Networks is currently in public previewand works to provide a direct UDP connection between the client and Cloud PC if enabled and achievable. This connection is in addition to the TCP based connection described above and the dynamic virtual channels such as graphics, input etc are switched into the UDP connection if deemed optimal. The diagram below shows this in place, with the TCP based connection continuing via the Gateway and an additional direct UDP connection. UDP shortpath will only work if direct UDP connectivity to any public IP address is available on both the client and the Cloud PC, so may not be possible in some enterprise environments where tunnels such as those above are in use (as all UDP traffic would have to be offloaded from the tunnel). More detail can be found here on endpoint requirements for this feature.53KViews7likes13CommentsProblems authenticating from Remote Desktop Client
Hello, Does anyone have any suggestions for problems connecting from the RDP client? I downloaded the app fromWindows 365 (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.Greg EschingerAug 03, 2021Copper Contributor39KViews0likes27CommentsOutlook 2007 exchange admin has blocked the version
This morning Outlook stopped working with the message 'Your MS Exchange administrator has blocked the version of Outlook that you are using. Contact your administrator for assistance' I have read a few articles but its not clear, is there a simple fix or do i need to upgrade? My Google account associated with the desk top Outlook still works, however my mail associated with 365 has stopped. Using web based 365 for mail still works Best IanSolvedIanpalmerarchitects365Nov 11, 2021Copper Contributor26KViews0likes5CommentsCisco AnyConnect VPN Not Working!
Hi, I am trying to connect to client network using Cisco AnyConnect VPN and after successful authentication I am getting below error message: VPN establishment capability for a remote user is disabled. A VPN connection will not be established. I understand this is a restriction from Cisco server configuration however I support multiple clients and some of them use Cisco server while others use a different software entirely so it doesn't seem reasonable to ask each one of them to update their configuration for my sake alone. I already checked below explained hack however it doesn't work anymore. https://blog.expta.com/2020/04/how-to-enable-cisco-anyconnect-vpn.html Is there anyway on Windows 365 appliance to overcome this? Without this my Windows 365 setup would be useless. Please help! I have created ticket #27044074 for this issue. Thanks!snevasAug 16, 2021Copper Contributor25KViews0likes4CommentsExchange Account Settings greyed out
Just got my WIndows365 Cloud PC up and running. I don't seem to be able to download all my email (slider is greyed out)SolvedeasykeyAug 27, 2021Copper Contributor24KViews0likes7Comments