Join David Elfassy for an in-depth discussion in this video Troubleshoot the deployment of Office 365, part of Office 365: Deployment.
- [Instructor] When everything works great Office 365 purrs along, and all your users can send and receive emails, can access their documents and have online meetings, but when there are problems it can be a little challenging to identify the source of your issues with Office 365. Mainly because most of what goes on in Office 365 happens in the Cloud. You don't have any servers to maintain, to troubleshoot, or to verify that all the lights are on. So there are several tools that we can use to troubleshoot all our services that live in the Cloud.
One of those is the Outlook and Office 365 recovery assistant. Now this is a little tool that you download and install and it runs you through a set of tests and wizards to actually help you identify the source of the issues. Now these are very client centric. These are focusing on the issues that are happening on the client applications, on the desktop computers, and anything that can be preventing your clients from connecting to an Office 365 service. As well there could be issues that are happening in the portal of Office 365.
So you could be looking at a service degradation that is related to a Microsoft outage. Now if you go into your Office 365 admin center and click on service health you would be able to easily identify that a service is currently down now. We've looked at advisories in another video in this course, but if the service was completely unavailable then it would show up in red and it would present a clear explanation as to what is causing the problem and what is the expected recovery time.
Now you'll remember that you have a service level agreement or an SLA with Microsoft when it comes to Office 365 and there is a financial penalty for Microsoft for having the service down for more than a specific period of time. Now if you go to testconnectivity.microsoft.com, you go to this URL, do you see a multitude of tools that are available if you have an infrastructure on premise of Exchange Server, Skype for Business, Lync, Office 365 Configurations, all of those can be troubleshooted from the testconnectivity.microsoft.com.
So for my Office 365 deployment I can run various checks to verify that my DNS is configured properly to connect to Office 365 for Exchange or for Lync, that my single sign on is working right and that specifically checks for ADFS configuration, Active Directory Federated Services. Active Sync, is that configured properly? Can my mobile devices connect correctly? Sometimes they can, sometimes they can't and I need to see if, are they able to connect at all, are they able to even find their server with the auto discover services.
So this will run a number of verifications both in DNS, the availability of service, and also in TCP ports. The Exchange Web Services, or EWS, something that's used, for example, by the Mac client for Outlook, how are these working and running specific tests for those can be useful in troubleshooting that connectivity. Outlook connectivity, so basic MAPI connectivity or RPC over HTTP connectivity, is there any issues with that, are they related to certificates, some encryption that's not working? Auto discover, enable Outlook auto discover.
Auto discover is that service that will just discover your server and does not require any server name or configuration in your profile, simply a user name and password and it configures Outlook for you using this amazing auto discover service. Well it's great when it works, when it doesn't work it's a little bit complex to troubleshoot. What's great about the auto discover test over here is that it runs a step by step test and if there's a problem it really in a granular way displays where that problem is found and suggests different ways to fix it.
Internet tests, this is testing the inbound and outbound SMTP connectivity to your organization as well as calendar sharing. Now in the next tab I specifically have my client and now this is for the Outlook clients that are connecting to Office 365 or connecting to Exchange. Now one of those tools here is the Office 365 client performance analyzer that I just showed you. So if you want to download it this is where you can download it from. I'm going to go back to my Office 365 tab and I'm going to run one of those tests to show you what it looks like.
How about the Outlook auto discover test. So I'm going to click next. It's going to ask me for my email address, which I'm going to provide and my Microsoft account, which is the same. Then it's going to ask me for my password and it asks me about SSL, now SSL again is the certificate that is being used. We need to trust that certificate for auto discover to work or at least for Outlook to work correctly. So I can allow to ignore the trust if I have some SSL issues so that I can see the other issues that can be preventing my connection.
I'm accepting the disclaimer and then I'm confirming that I am not a machine. Verify, perfect, I entered, that went well. Now I'm going to perform the test. So the test is running, it's going to take a few seconds. While this is running I'm going to return to my clients performance analyzer and look at all of my tests over here. So here it show that I'm currently located in California. It's showing the version of Windows that I'm running and some diagnostic about my computer, the ISP that it's connecting through, the name of the DNS server.
I see my latency over here. So you see the latency to Office 365 using ICMP, so ICMP is ping. So I see my latency here and it's give me some guidance as to what it's looking for. So my ping is 13.25 millisecond and it's telling me that anything lower than 275 millisecond is acceptable. You see here this is in green. So if I went down this listing and I found some listings in red then those would be red flags and those would specifically display that there is a latency issue that will connect to the latency issue between my client to my Office 365 tenant.
I can download these results to an Excel spreadsheet and then analyze them over time. Now you can use this tool when you're preparing your deployment to Office 365 or you can use this tool in a troubleshooting episode. So now let me go back to my auto discover test to see if it ran, and it ran successfully. So I'll actually look at the test steps more in details so I can see the actually steps that ran. Now I'll show you that there's failures that are showing here, but my test shows successful.
Actually what it does is that it runs through the various permutations of possibilities of ways to connect over auto discover. Some work, some don't, as long as one of them does work that's what's important. So it connects the various URLs, it looks for various DNS records, it tries to connect on various ports, because it has multiple options for connections. As long as it finds a valid method of connecting and therefore that the test will pass with success then it shows me a successful final result.
However, if I go at it in the specific sub tests then I find tests that did fail, but that's all right, because my connection will still be successful. So these are troubleshooting tools that you can use in troubleshooting your Office 365 connections or your clients connections to Office 365.
This course details the process of moving your network to Office 365 by deploying a new Office 365 subscription. David Elfassy covers creating user accounts, adding domains, and configuring email, directories, conferencing, file sharing, and valuable business services such as PowerShell and SharePoint. Watch these tutorials to deploy your own implementation of Office 365 or to see if this technology fits your enterprise needs.
- Using FastTrack to prepare for Office 365
- Creating Office 365 user accounts
- Adding domains
- Configuring Outlook and Skype
- Configuring sharing and shared mailboxes
- Troubleshooting an Office 365 deployment
- Configuring PowerShell
- Creating SharePoint services