Sep 7 2016

Find a duplicate e-mail address in Active Directory

We recently started seeing a lot of mails stuck in the submission queues and found that there were a few duplicate e-mail addresses in the environment. Most of the time we could not find the duplicate addresses in Exchange and had to search for the duplicates in Active Directory as some addresses were bound to AD objects.

To search for a duplicate address do the following:

  1. Open Active Directory Users and Computers
  2. Right click on your domain name and click on find
  3. Next to find choose custom search (see below screen shot)
  4. Then click on the Advanced tab (see below screen shot)
  5. Under “Enter LDAP query:” type the next search query (see below screen shot)
  7. Click find you you should find all objects with the duplicate address.

Screen Shot of the LDAP query in when looking for a duplicate address

Aug 12 2016

Unable to see remote mailbox on the on premises Exchange servers but can see it in Exchange Online

We’ve had a few instances where a user could not receive mail into their Exchange Online mailbox. Upon investigation we noted the address is the primary SMTP address for the user and that the remote mailbox object is not available in Exchange on premises.

To resolve this do the following:

  • Open Active Directory Users and Computers (dsa,msc from start -> run)
  • Click on View -> Advanced Features
  • Do a search for the user who has the issue as per above
  • Right click on the user and choose properties
  • Click on Object and make a note of the path
  • Close the search you made.
  • Now navigate in Active Directory Users and Computers to the user by dropping down through the OU’s etc.
  • Right click on the user and choose properties
  • Click on Attribute Editor (Note that changes made here could break something so make sure you compare it to a working user just in case)

Now you need to look for the below entries and change them or ensure they are set correctly as per below:

  • homeMDB – <not set>
  • homeMTA – <not set>
  • msExchHomeServerName  – <not set>
  • msExchRemoteRecipientType – 6
  • msExchRecipientDisplayType – (-2147483642)
  • msExchRecipientTypeDetails – (2147483648)
  • proxyAddress – check SMTP addresses are all there and correct
  • targetAddress – (check this against a working user in your environment)

Mar 9 2016

Newly migrated mailbox to Office 365 does not receive new e-mail

We had an interesting issue where  user’s mailbox was migrated to Office 365 but he could not see any new mail in the mailbox. Even sending himself mail did not show the new e-mail items.

We sent a few test mails and tracked the mail from on premises Exchange to Office 365 which showed that the mail delivered to the cloud.
We then traced the mail items from within the Office 365 admin portal and confirmed that the mails delivered to the mailbox but we could still not see the items.
Thinking that it might be desktop related we asked the user to logon to Outlook Web App and we could still not find the mail items that showed as being delivered to the mailbox.

I then ran the Get-InboxRule cmdlet against the mailbox to see if a rule might be interfering. Suddenly the new test mails sent after I ran the cmdlet delivered to the mailbox and we were able to see them. Testing all new mail to and from the mailbox seemed to have worked after I ran the Get-InboxRule cmdlet as if it reset the rules somehow.

This still boggles my mind but it’s worth a try if you have the same issue.

Mar 9 2016

Moving an on premise mailbox to Office 365 gives the error “Transient error StoragePermanentException has occurred. The system will retry (6/640).”

One of my colleagues battled to migrate an on premise Exchange 2010 mailbox to Office 365. After trying to repair the mailbox and numerous other things he still received the below error:

Transient error StoragePermanentException has occurred.

                                           The system will retry (6/640).

Eventually he appended the -SkipMoving:FolderRestrictions to the New-MoveRequest cmdlet and managed to migrate the user’s mailbox to Office 365.

Feb 24 2016

Messages awaiting directory lookup – Queue Build up on Exchange

We had an Exchange 2003 server that had a queue build up. The messages were building up in the “Messages awaiting directory lookup” queue.

After investigation we found that the server had old DNS entries which were removed and new entries were added. The queue cleared almost immediately.

If you see build up in the Messages awaiting directory lookup queue then be sure to check DNS is working as expected.

Feb 18 2016

Lync client drops voice calls

We had an interesting issue a while back where a user was able to use the Lync (Skype for Business) client for IM, desktop sharing etc. The problem was the user could not make/receive any peer to peer or Enterprise Voice calls. The call would try and connect and then cause the Lync/Skype for Business client to hang.

A malware scan was run after some troubleshooting and malware was found. The user was able to make and receive calls after we got rid of the malware

Dec 17 2015

Exchange 2010 Queue Build up with Event ID 1035

We had an interesting issue with queues building up to remote sites. In queue viewer we noted errors sending mail to different remote sites as per below:

451 4.4.0 Primary Target IP Address responded with: “235 00000xxxxxxxxx”


And in the Event Viewer we noticed event ID 1035 , MSExchangeTransport


At first we thought the issue has to be on the specific Exchange 2010 server trying to send the mail as it was the only server in the DAG that could not send mail to the remote servers. However, the problem was still present after restarting the Hub Transport Service on the server experiencing the above issues.

As a shot in the dark we restarted the SMTP and Hub Transport Services on the remote servers (to where the mail is destined) and the errors disappeared and the mail was sent to the remote servers.

Dec 17 2015

Provisioning Layer initialization failed error when running a cmdlet in Exchange Management Shell

I’ve had the below error a few times this year when trying to open the Exchange Management Shell or running a cmdlet.


To get this working browse to another Exchange 2010 server and copy the ScriptingAgentConfig.xml file from the working server and paste it in the same directory (as per below) on the non-working server.

The file can be found under your Exchange Installation by default c:\Program Files\Microsoft\Exchange Server\V14\Bin\CmdletExtensionAgents\

Nov 25 2015

How to install “Brackets” in Ubuntu 15.10 – Get around Dependency is not satisfiable: libgcrypt11 >=1.4.5 error

In this post I will show you how to install Brackets , an open source code editor from Adobe and how to get around the dependecy error (Dependency is not satisfiable: libgcrypt11 >=1.4.5) if it pops up when you try to install Brackets.

I’m using Brackets as part of a web development course and really like it.

Installing is quite easy as per below:

  1. Open your browser and go to the Brackets Website.
  2. Click on Download Brackets without Extract to download the deb package file.
  3. Browse to the downloaded deb package file and double click it. This action will open the Ubuntu Software Center.
  4. Brackets should install and you you will be able to use it after the installation finished. If you get the error below check the below Dependency installation section.


Installing the libgcrypt11 dependency:

  1. If you receive the above error clink on this link to download libgcrypt11
  2. Browse to the path where you downloaded the libgcrypt11 deb package and double click the deb package.
  3. This will open the Ubuntu Aoftware Center and install libgcrypt11
  4. Browse to the Brackets deb package and double click the deb package for Brackets.
  5. Brackets should now install without any errors.

For a visual guide please watch the below video I created to show how I installed Brackets on Ubuntu 15.10


Oct 13 2015

Old Out of Office message is sent even after a new message has been created

We had a few instances this year where users create a new Out of Office message but then report that the previous Out of Office message is sent instead of the new Out of Office message or both are sent to people that sent mail to them.

I found that most of the time running outlook.exe /cleanrules works if that does not work please see method 2 below.

Method 1

  1. Close Outlook
  2. Click on start and in run type Outlook.exe /cleanrules then hit enter
  3. Wait for replication and send a test mail to the mailbox to see if the old Out of Office message is not sent out anymore
  4. If the old Out of Office message is still sent check method 2 below

Method 2 (Only had to do this on one occasion)

  1. Open Outlook
  2. Open the Out of Office assistant
  3. At the bottom of the Out of Office assistant window, click on Rules
  4. Delete all rules
  5. Close Outlook, re-open Outlook and test sending a mail to the mailbox. You should not receive the old Out of Office assistant anymore


An Out of Office message is only sent once to a sender. It’s a good idea to send the test mails from different e-mail addresses that have not as yet received the Out of Office message from the mailbox that you are troubleshooting