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
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
Problem You’ve recently updated the certificates for your Exchange 2016 servers: You notice that the ECP / EAC page no longer load properly upon successfully logging in after reassigning the new certificate, deleting the old certificate and restarting the server: Reviewing the event logs show
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
I’ve been asked several times in the past about how to block subdirectories when a website is published with a NetScaler and the most recent request was for blocking Exchange Server 2016 /ecp access. As most Exchange administrators are aware, Exchange 2013 and 2016 allows
Problem You attempt to run the Test-ExchangeServerHealth.ps1 health check script found at the following Microsoft TechCenter: Generate Health Report for an Exchange Server 2016/2013/2010 Environmenthttps://gallery.technet.microsoft.com/office/Generate-Health-Report-for-19f5fe5f … but notice that the report generated is indicating that the mail flow test is failing for your Exchange servers:
Problem You attempt to reassign an Exchange UM extension that was previously assigned to a user who you have disabled for UM but receive the following error: error Extension xxxx is already assigned to another user on dial plan UMDialPlan or on an equivalent dial
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 have an account that was recently disabled in Active Directory and need to access it via OWA so you proceed to enable in Active Directory Users and Computers then log on via the webmail webpage but receive the following error: 🙁something went wrongYour
