Endpoints in the Optimize category are the most sensitive to network performance, latency and availability. For instance, some traffic vendors have integrated with Office 365 REST APIs to get a list of webservice that catalogs and returns up-to-date information about all Office 365 front door service endpoints. Microsoft has organized O365 service endpoints into three categories: Optimize, Allow and Default. SD-WAN if required: If you have limited connectivity and combination of multiple ISP providers and connectivity such as MPLS in combination with regular internet connectivity you should look into SD-WAN to ensure optimal performance.Configure AppQoE if possible on the wireless and outbound connections for Office365 to be prioritized.Split tunnel for VPN solutions to bypass Office 365: Having solutions such as VPN with forced tunneling that makes all Office 365 traffic go through a VPN will also slow down the performance since this will also create IP fragmentation.Bypass outbound proxy servers: Microsoft recommends not having proxy servers for Office 365 traffic ( ).Try doing nslookup and ensure that you get a response that is part of your geographic region, can be verified using Also, ensure that DNS requests are not taking long to process. Check DNS: If you have a DNS server hosted in another region your endpoint might be routed to another Office 365 datacenter, ensure that DNS servers are located within the same region as your clients.Check TCP Connection – PowerShell: Test-netconnection –computername “” -port 443 and ensure that you have low latency here.Check ICMP: to and ensure that you have a low response time on the request.Because there can be many things that might be blocking Office 365 traffic.Īlso if you have limited public IP addresses, ensure that you make sure that you have enough for outbound TCP connection to Office 365, limitations with NAT and Office 365 Įnsure that you check the outbound connection speed and validate that you have low-latency connections to some of the Office 365 endpoints. It is important to understand that you should have a stable internet connection and should not have any “blockers” or inspection of the traffic going out. T he list of Office 365 URLs and IP address ranges can be found here –> When setting up access to Office 365 your security policies might require firewall openings for the different Office 365 which is a pretty long list. NOTE: Deploying a VDI/RDSH solution in Azure has also shown to improve the performance on Office 365 Applications such as load time and overall end-user experience since it provides lower latency connectivity to Office 365 endpoints. This service is available for OneDrive and Exchange which you can read more about here –> ( which requires a minimum of 500 uers) You can also read more about supported regions here –> Office 365 also has a Multi-geo service which allows you to store data closer to your users if they are in another geographic region. When using Office 365 data will be available in multiple regions across depending on where you set up your first subscription ( You can see where your data will be stored here –> ) The distance between your end-users with the Office applications and Office 365 services is important, if this distance is too far away it will affect the end-user experience. All these different services come from different datacenters and having multiple endpoints which Skype for Business, Outlook, and OneDrive use to connect and utilize the different services. However, this is not the case with Office 365 where you now have the data stored in Microsoft’s own datacentres and now having the applications installed on end-user devices which connects to these services from miles away. It is always common best practice to have the apps and the data as close as possible to get the best end-user experience and performance. Remote display protocols and when to use when.Troubleshooting and general tips for tuning.
#Xendesktop pvs kms office 2016 not activated windows
The article itself focuses on the deployment of Office 365 ProPlus on a VDI/RDSH environment but also applies to regular Windows endpoints.ĭeployment toolkit Office365: (Which now supports 2019) A lot has changed since I first wrote this article back in 2015 and updates it in 2016 and therefore I decided to rewrite the article to make it a bit clearer and give a bit more advice into each section. This is an updated article on the old one which is referenced here.
0 kommentar(er)
