Advertisements

Month: March 2018

In your Exchange 2016 environment, you might have noticed that you are getting a lot of errors logged in the application log regarding PowerShell.exe, here is the error message: Event 4127, MSExchange ADAccess Process powershell.exe (PID=11952). Component: Microsoft.Exchange.Data.Directory.ConfigurationSettingsADNotificationException: Error running AD operation. —> Microsoft.Exchange.Data.Directory.ADTopologyUnexpectedException: Unexpected error when calling the Microsoft Exchange Active Directory Topology service […]

Advertisements
Read more

In Exchange in general, having an outbound connector setup with the address space of * should allow mail to flow to the internet, this being said, your MX records need to be in place and DNS has to be set correctly but you may encounter a problem regarding IPv6 and sending out mail. Here is […]

Read more

In Exchange 2016 when you try and access OWA or the Exchange Admin Center (EAC), you might be presented with the following error: The webpage at https://mail.domain.local/owa might be temporarily down or it may have moved permanently to a new web address. ERR_SPDY_INADEQUATE_TRANSPORT_SECURITY This is due to a cipher and/or hash issue and can be resolved with […]

Read more

As an Exchange Admin, you may be wondering what commands are run when you click on different areas in the Exchange Management Console, this can be Accepted Domains or Mailboxes under the Recipient Configuration section in the EMC. It is actually very easy to find out what has been run. Launch the Exchange Management Console […]

Read more

In Exchange, when running a the search-mailbox command and you have a large user base, you might encounter the following error: Sending data to a remote command failed with the following error message: The total data received from the remote clien t exceeded allowed maximum. Allowed maximum is 524288000. For more information, see the about_Remote_Troubleshooting […]

Read more

In Exchange 2010, the following error logs quite often in the application log but no noticeable impact to users. The error in question: Exchange 2010 – Event ID 108 Outlook Web App couldn’t connect Exchange Web Services due to a configuration error. Response code = “500” The strange thing is, no follow up error is […]

Read more

In Exchange, you might have a number of accepted domains and manually editing the information can be a daunting task. The PowerShell script below updates the Name value with the new name. If you use a 3rd party provider like Ensim, they generally add a bracket () with a number behind the name and this […]

Read more