Users may receive a "Signing in to the SIP Communications Service failed because your program is not configured to use the TLS Transport while in high-security mode" error message when they try to sign in to Office Live Communications Server 2003 (837383)

RESOLUTION

To troubleshoot this issue, use one or both of the following methods in the order that they are presented.

Method 1: Disable Session Initiation Protocol (SIP) high-security mode by using Group Policy

Create a Group Policy object to disable high-security mode for SIP communications. To do this, follow these steps:

1. On a domain controller, start Active Directory Users and Computers.
2. Right-click the domain or the organizational unit that contains the user accounts that you experience this problem with, and then click Properties.
3. Click the Group Policy tab, and then click New.
   
   Note If you already have a policy that is configured to modify Windows Messenger communications, modify that policy instead of creating a new Group Policy object.
4. Type a name for the Group Policy object, and then press ENTER.
5. Click Edit, expand Computer Configuration, right-click Administrative Templates, and then click Add/Remove Templates.
6. Click Add, open the Setup\I386 folder on the Office Live Communications Server 2003 CD, click rtcclient.adm, and then click Open.
7. Click Close.
8. Under Computer Configuration, expand Administrative Templates , expand Windows Messenger Policy Settings, and then click SIP Communications Service Policies.
9. In the right pane, double-click Require SIP high-security mode, click Disabled, and then click OK.
10. Quit Group Policy Object Editor, and then click Close.
    
    Note If a Group Policy object is configured to require high-security mode for SIP communications, and if that Group Policy object is at a higher level than the Group Policy object that you created, you must modify or temporarily disable that Group Policy object so that it no longer requires high-security mode for SIP communications.
11. Restart the client computer that Windows Messenger is running on, and then try to sign in to Live Communications Server .

Method 2: Disable high-security mode in the Windows registry

If the Windows Messenger user cannot sign in to Live Communications Server successfully, verify that high-security mode is not specified in the registry. To do this, follow these steps.

Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

1. On the client computer where the Windows Messenger user cannot sign in to Live Communications Server, start Registry Editor. To do this, click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate and then click the following registry subkey:

   HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Messenger\Client\{GUID}\_Default

3. On the File menu, click Export.
4. Type a name for the exported registry file, and then click Save.
5. Delete the EnableSIPHighSecurityMode registry entry if it exists. To do this, right-click EnableSIPHighSecurityMode, click Delete, and then click Yes to confirm the removal of this registry entry.
6. Quit Registry Editor, and then restart Windows.
7. Sign in to Live Communications Server.