![office 365 outlook settings speed office 365 outlook settings speed](https://content.spiceworksstatic.com/service.community/p/post_images/0000209002/58122704/attached_image/9.png)
- #Office 365 outlook settings speed how to
- #Office 365 outlook settings speed install
- #Office 365 outlook settings speed windows
Remember that a flush does not remove HOSTs file entries. By clearing the cache, you're resetting the DNS resolver contents to the most up-to-date entries. Why? By flushing out the DNS cache you're starting your tests with a clean slate.
#Office 365 outlook settings speed how to
If you're accustomed to doing this kind of network capturing, you can skip to How to collect baselines, which describes filtering and reading the logs. If you're not familiar with running the tools mentioned in this article, don't worry because we provide those steps next. Again, be sure to include the date and time of the capture and whether it demonstrates good or bad performance. Be sure to include the date and time of the capture and whether it demonstrates good or bad performance. Stop the Steps Recorder and save the video. Reproduce the exact steps that cause the performance issue.Īt the command line, run a trace route to your Office 365 subscription by typing the following command and then pressing ENTER: tracert. Optional: If you are testing Exchange Online, run the Exchange Client Performance Analyzer tool from the Office 365 admin console. Start a new browser session and turn on HTTPWatch.
![office 365 outlook settings speed office 365 outlook settings speed](https://www.codetwo.com/admins-blog/wp-content/uploads/2018/07/IMAP_To_Office365_Migration.png)
Start your Netmon capture (or network tracing tool).Ĭlear your DNS cache on the client computer from the command line by typing ipconfig /flushdns. Start the Steps Recorder, or another screen recorder.