The "proxyAddress" attribute is not populated with an SIP URI when you enable a user, contact, or inetOrgPerson object for Live Communications after you install Live Communications Server 2005 Service Pack 1

You enable a new user, contact, or inetOrgPerson object for Live Communications in the Active Directory directory service. When you view the proxyAddress attribute for that user, contact, or inetOrgPerson object by using a tool such as ADSI Edit, the proxyAddress attribute is not populated with a Session Initiation Protocol (SIP) Uniform Resource Identifier (URI). Instead, the proxyAddress attribute has a value of Not set.

You expect the proxyAddress attribute to have a value of SIP:username@domain.

Because this attribute is not set, Microsoft Office programs may not be able to detect the presence information of the object for which you enabled Live Communications.

This problem occurs if you are running Microsoft Office Live Communications Server 2005 Service Pack 1 (SP1). This service pack contains a code error that causes Live Communications Server 2005 to skip the initial population of the proxyAddress attribute for a new user, contact, or inetOrgPerson object.

To resolve this problem, install the software update that is described in the following Microsoft Knowledge Base article:

To work around this problem, modify multiple properties for the user, contact, or inetOrgPerson object in Active Directory.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

The installation of this software update will not populate the proxyAddress attribute for a new user, contact, or inetOrgPerson object that is already enabled for Live Communication Server 2005. Accounts that you add after you install the update will receive the correct attribute.