This article describes a new policy that is available for an environment in which Microsoft Office Communicator 2007 users use Microsoft Office Outlook together with Lotus Notes or with other mail systems.
This new policy lets an administrator override the default behavior of the Personal Information Manager feature. By default, this feature uses Outlook. An administrator can configure a policy to specify the Contacts store that Communicator 2007 uses. The choices for this policy include Outlook (this is the default choice), Windows Address Book, or None.
A new policy is available for use with Communicator 2007. This policy is named DefaultPersonalContactStore. Communicator 2007 integrates with the specified store if the following conditions are true:
The DefaultPersonalContactStore policy is present.
The DefaultPersonalContactStore policy is set to a non-NULL value.
The correct location for this registry key is HKLM\Software\Policies\Microsoft\Communicator.
The DefaultPersonalContactStore policy is a DWORD value. You can set the value to 0 for "Outlook," to 1 for "Windows Address Book," or to 2 for "None."
The latest Communicator client must be installed.
The Communicator 2007 account must never have logged on to Microsoft Office Communications Server 2007 before.
The Personal Information Manager setting in the SQL database is now stored in Communications Server 2007 for multiple logons. After a user has a Personal Information Manager entry in the SQL database, the DefaultPersonalContactStore registry key is ignored. The only way to override the SQL database entry is to manually set the Personal Information Manager in the Communicator 2007 client and then log off.
You can "reset" the SQL database account. To do this, use the Delete Communications Server User command in the Communications Server 2007 Admin Tools (DSA.msc) utility, and then re-enable the account.
How to obtain the hotfix
This issue is fixed in the Communicator 2007 Hotfix Package that is dated October 5, 2007. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
941441 Description of the Communicator 2007 hotfix package: October 5, 2007
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.