Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name

In the office we use a SonicWall to allow remote VPN users to access local resources. For the most part it works great, allowing access to our Outlook / Exchange server, mapped drives and other important network resources.

Recently I upgraded the SonicWall to a new device and recreated the rules from scratch (rather than roll old stuff over) a few days after the upgrade SonicWall users started to experience this odd error message:

ODD OUTLOOK ERROR MESSAGE:
Outlook cannot log on.  Verify you are connected to
the network and are using the proper server and mailbox name. 
The Mailbox Exchange information server in your profile 
is missing required information. 
Modify your profile to ensure that you are using the 
correct Microsoft Exchange information service.
Image result for Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name. The Mailbox Exchange information server in your profile is missing required information. Modify your profile to ensure that you are using the correct Microsoft Exchange information service
At first I thought the users profile had just gone corrupt, so I deleted the Outlook profile and just recreated it and all was well in the world. However next time that particular user took their laptop out of the office the message eventually returned.  I was able to put two and two together and figured it had to do with something the VPN tunnel on the sonicwall was doing to cause this issue.
The solution:

Continue reading “Outlook cannot log on. Verify you are connected to the network and are using the proper server and mailbox name”

Exchange 2016 – EVENT ID 15021- Blank ECP / OWA & Error connecting to Outlook

If you have been following my blog, I recently migrated my Exchange 2010 server to a new 2016 server. There have been a few hiccups along the way however for the most part  the experience has been good and user disruption minimal, until I encountered Event ID 15021.

ExchangeLast night during a maintenance window I applied my Microsoft updates and rebooted the server. Shortly after reboot I attempted to open Outlook and it failed with a server unavailable error. OWA and ECP both showed BLANK white screens. I began to panic a little because this is probably the IT guys worst nightmare! Working in the industry for over 20 years I put my panic aside and began my standard troubleshooting procedure.

STEP 1 – Event logs are your friend

Continue reading “Exchange 2016 – EVENT ID 15021- Blank ECP / OWA & Error connecting to Outlook”

My Experience Migrating to Exchange 2016

If you have ever taken the time to read my blog you would probably know by now that I am the IT director for a mid sized accounting firm in NJ. One project on my docket this year is to migrate from Exchange 2010 to Exchange 2016. This post is just going to be a basic log of what I encountered during my install. If you take the time to read this maybe you can find a useful tip to aid in your migration woes.

Having a small shop and wearing a lot of hats here in the office tends to create a slew of challenges. Most of the time I have a ton of projects brewing so focusing on one can be difficult at times. My migration to a new Exchange 2016 server will be gradual taking about 2 to 3 weeks to complete. During the initial setup I like to let certain steps “stew” overnight to make sure there are no disruptions. I also like to be sure I have a contingency plan to undo any unforeseen issues.

Is your directory active enough?

Continue reading “My Experience Migrating to Exchange 2016”