Recently, I was working an issue where IIFP (Identity Integration Feature Pack) was being used to execute a Global Address List Synchronization (GalSync). We knew the contact objects were being created, and that OWA could see these contacts. However, if we reviewed the GAL, we could not see the contacts.
This is because IIFP was distributed prior to Microsoft Exchange 2007. The release of Microsoft Exchange 2007 removed the RUS (Recipient Update Services), which IIFP relied on for the creation of mail-enabled contacts. Since the RUS was removed, the mail-enabled contact objects are created, but not stamped with the necessary attributes to allow the mail-enabled contact to be seen in the GAL.
The resolution resides in the Microsoft Knowledge Base article Identity Integration Feature Pack SP2 GalSync with Exchange 2007, to utilize the Get-MailContact Exchange PowerShell CmdLet.
This is a very common issue for support. In this issue I worked recently, I was asked about the permissions to the Get-MailContact PowerShell CmdLet. I was able to locate such permission in the Microsoft TechNet article for Microsoft Exchange 2007 Help. (http://technet.microsoft.com/en-us/library/bb676484(EXCHG.80).aspx)
This cmdlet retrieves all attributes of the specified contact. No parameters are required. If the cmdlet is run without a parameter, a complete list of contacts for the Exchange organization is returned.
To run the Get-MailContact cmdlet, the account you use must be delegated the following:
For more information about permissions, delegating roles, and the rights that are required to administer Microsoft Exchange Server 2007, see Permission Considerations.
I wanted to share this information with everybody, and ensure that all are aware of the Microsoft Knowledge Base article associated with this issue and the permissions needed to execute the Get-MailContact PowerShell CmdLet.