The following error is ever so common for users of both Exchange and Outlook 2016:

A lot of users are getting this error, and the general conclusion is that Microsoft is to blame.

Microsoft is constantly updating and upgrading its services, and oftentimes doesn’t update the configurations for its users. _[1] This issue usually affects Outlook 2016 but can happen with other versions as well. The message will lead you to believe that you need to update information in your profile, which is impossible to do since Outlook refuses to open and you can’t do anything with it. This occurs because the root domain server is responding to the autodiscover request and as a result, you will not be able to open Outlook, or use your account with it.

What is happening is that Outlook 2016 is hanging when performing the HTTPsAutoDiscoverDomain method. Outlook uses the root domain of your SMTP address to attempt to locate the AutoDiscover service. It tries to connect to the following URL based on your SMTP address in the following xml file: https://<smtp-address-domain>/autodiscover/autodiscover.xml. _[2]

If Outlook is slow finding the autodiscover records, you can tell Outlook to exclude the root domain and other records (SCP lookup, AD domain query, HTTP redirect, and SRV record query) with the following registry entries:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Outlook\AutoDiscover\
 DWORD: ExcludeHttpsRootDomain
 Value: 1

“ExcludeScpLookup”=dword:00000001

“ExcludeHttpsAutoDiscoverDomain”=dword:00000001

“ExcludeHttpRedirect”=dword:00000001

“ExcludeSrvRecord”=dword:00000001

The reason for individually disabling each of these records is because Outlook’s default settings uses one or more of these methods to reach the AutoDiscover service. If Outlook fails to connect to the predefined URL based on your SMTP address, Outlook tries the HTTP redirect method. If that does not work, Outlook tries to use the SRV record lookup method. If all lookup methods fail, Outlook cannot obtain “Outlook Anywhere” configuration and URL settings. _[3]

This simple solution will help you work around the nasty issue.

References:

Arrows, Kevin. “Fix: Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name.” Appuals.com. N.p., 29 Jan. 2017. Web. 29 May 2017. <https://appuals.com/solved-outlook-cannot-log-verify-connected-network-using-proper-server-mailbox-name/>. [1]

Bayley, James. “Registry hack to enable Outlook 2016 to connect to Office 365.” Blog.jamesbayley.com. N.p., 01 Dec. 2015. Web. 29 May 2017. <https://blog.jamesbayley.com/2015/12/01/registry-hack-to-enable-outlook-2016-to-connect-to-office-365/>. [2]

“Posts about ExcludeScpLookup on John Yassa’s Blog.” John Yassa’s Blog – Microsoft till the end. N.p., Web. 29 May 2017. <https://johnyassa.com/tag/excludescplookup/>. [3]

Its one of those things that the entire department, from CIO to the tech support guy, know is essential. Yet often system diagrams and documentation are either outdated or non-existent. That one day when something in the network goes south, everyone is scrambling for the recent documentation and it becomes the centre of attention.

Proper network documentation is essential for IT operations. This is more true as enterprise architecture grows larger and more complex. But even for SMEs with moderate IT budgets, the IT department can put together a very detailed and flexible document. The documentation should be a reference and guide to help the company in many ways:

• Train new recruits;
• Analyse and troubleshoot networks;
• Better capacity planning;
• Audit;
• Report underutilized resources and improve efficiency of the network;
• Less downtown.

What to include

Here are some of the important aspects to keep in mind while documenting networks and systems:

1. Keep it simple and clean.
2. Use standard equipment images to depict each device in the network.
3. Label each device (Hostname, IP address, Date of Manufacture, etc.).
4. Clearly mark different network location on the diagram with location addresses and IP scheme.

Value Added

Let’s think of it from the client’s perspective. When you get in touch with you IT service provider to sort out an issue, all you need is immediate resolution. Your business is slowing down because of a system that is not working and all you care is that it be up and running ASAP.
On the IT side, if a network diagram and documentation of all configurations of the client’s equipment is available, all you need to know is what the trouble is. With all relevant information available in documentation, you will be able to troubleshoot in much less time and minimise potential losses. Sort that out, call the customer back and things are back to normal. Happy customer, satisfied you…

The value this brings to the customer is tremendous in terms of low downtime and hassle-free experience. As the IT side of the business, anytime an audit happens, having all those documents and diagrams will help deal with network compliance issues easily. And as you update and grow the documentation, it will also become a guide in finding unallocated or underused resources and help make efficient technical and business decisions.

Examples of Network and Systems Diagrams that we have prepared for our clients:

—-

No? Its time to think of creating one.

Having multiple means of communication with vendors and customers, it is difficult to maintain a standard throughout the company. A style guide will provide a reference point to set standards for logos, documents and other communication within and outside of your organisation.

Purpose

It should define what your corporate identity looks like in print, internet and any other visual media. The Style Guide will help create a clear and unified corporate identity that will reflect a consistent style to promote your brand.

The guide can also be used as a resource to solve concerns and issues regarding preferred style. So it is important to keep the structure clear and have a self explanatory Table of Contents page.

The Style Guide will help you save time, ensure consistency and guarantee professionalism.

What needs to be included

The Style Guide should include every aspect of the company identity in the media. Some of the necessary topics to include are:
1. Logo: Examples of standard logos defining amont of clear space and minimum usable size are important to standardize documents. If your company uses diferent logos, providing examples of usage can be helpful. Various formats such as color, black and white, transparent, etc. and rules around placement and size of taglines are some other aspects that can be included.

2. Color Palette: Providing HEX, RBG, HTML and Pantone color palette to be used in logos, web pages and other media related documents will remove a lot of inconsistencies.

3. Fonts: In each category of the style guide, define font types, sizes, color, line-spacing, etc.

4. Links and Buttons: Define the size, color and style for links and button that are used on webpages. Illustrate these with relevant examples.

Sample Style Guide Pages

DO NOT consider the Style Guide as a design guide, instead consider it as a reference. The company must have design templates in place.

A first page example. Precise and easy to understand and browse through the document.

The page describing the company logo and usage.

Defining the logo sizes and white spaces around the logo.