I’ve been asked several times in the past by colleagues how would they go about monitoring Exchange message queues so that they would be notified if a threshold is exceeded and while I usually recommend looking for this feature in their existing monitoring solution, an
Most enterprise environments have solutions that provide monitoring services to ensure Microsoft Exchange Server services are running and if they are not, restart the service and send an email notification to administrators but I have constantly come across smaller business that may not be able
I’ve noticed that many of my colleagues and clients have asked me about the following error that is thrown when they attempt to export an Exchange Server mailbox to PST so I thought it would be a good idea to quickly write a post about
I’ve recently had to migrate a client from Exchange 2010 to 2016 and quickly noticed that Outlook Anywhere no longer worked after redirecting Outlook Anywhere and other services such as autodiscover and webmail to the new server. Outlook Anywhere continued to work for users migrated
Problem You’re in the process of migrating mailboxes from Exchange 2010 to Exchange 2016 with both a live as well as an archive mailbox and while some mailboxes successfully move to the new databases, you noticed that others remains in Syncing status indefinitely: Expanding the
One of the scripts I’ve often used when trying gather information about a current Exchange environment prior to performing a migration is the Get-ExchangeEnvironmentReport.ps1 PowerShell script written by Steve Goodman. The information provided by the report provides great information that would allow me to get
One of the scripts I’ve used a lot over the past few years is the Test-ExchangeServerHealth.ps1 PowerShell health check script written by Paul Cunningham. The red, yellow and green colour coded report generated by this script allows me to easily review the status of critical
Problem You’ve noticed that your previously operational Microsoft Forefront Identity Manager 2010 R2 throws the error the following error when you execute an Export job: stopped-extension-dll-exception Exchange 2010 contacts in the are either no longer updated or created in the source domain. You proceed into
Problem You’ve used the following TechNet article to allow Exchange 2016 mailboxes to access your Exchange 2010 public folders during a migration: Configure legacy public folders where user mailboxes are on Exchange 2013 servershttps://technet.microsoft.com/en-us/library/dn690134(v=exchg.150).aspx You’ve confirmed that the configuration in the article has been completed
Problem You need to install the CAS (Client Access Server) role onto an existing Exchange 2010 server with SP3 Rollup 13 that has the mailbox role already installed. You’ve downloaded Exchange 2010 SP3, unpacked it, run setup.exe: … select the CAS role to be installed
