Microsoft Knowledge Base Email Alertz

(834476) - Lists known documentation errors that exist in the documents that are located in the Documentation folder of the Live Communications Server 2003 CD.

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 834476 - Last Review: February 6, 2004 - Revision: 1.1

Errors in the deployment guide and the reference guide for Live Communications Server 2003

On This Page

INTRODUCTION

This article lists the known documentation errors that exist in the Microsoft Office Live Communications Server 2003 Deployment Guide and in the Microsoft Office Live Communications Server 2003 Reference Guide. These guides are located in the Documentation folder on the Microsoft Office Live Communications Server 2003 CD.

MORE INFORMATION

Microsoft Office Live Communications Server 2003 Deployment Guide

The following documentation errors exist in the Microsoft Office Live Communications Server 2003 Deployment Guide.

Page 6

The following information appears in the "Overview of Live Communications Deployment" section:
Live Communications Server is built on the Microsoft commitment to support industry standards. Both Microsoft Windows XP and Windows Server 2003 support the Internet Engineering Task Force’s (IETF) SIP and SIP Instant Messaging and Presence Language Extensions (SIMPLE).
In the second sentence, the phrase "SIP Instant Messaging and Presence Language Extensions (SIMPLE)" is incorrect. The following is the correct information:
SIP Instant Messaging and Presence Leveraging Extensions (SIMPLE)

Page 16

The following information appears in table number 5 in the "Live Communications Server Hardware Requirements" topic:
Collapse this tableExpand this table
Network adapter1 Gb/second
The number of bytes per second is incorrect. The following is the correct information:
Collapse this tableExpand this table
Network adapter100 MB/second

Page 17

The following information appears in the "Live Communications Server Software Requirements" topic:
Prerequisites to using the Microsoft Office Real-Time Communications Server include
The name of the product is incorrect. The following is the correct information:
Prerequisites to using the Microsoft Office Live Communications Server include

Page 42

In the "To enable user accounts in Active Directory for SIP" procedure, the following information appears in step 3 and in the note that follows step 6:
Real Time Communications tab
The name of the tab is incorrect. The following is the correct information:
Live Communications tab

Microsoft Office Live Communications Server 2003 Reference Guide

The following documentation errors exist in the Microsoft Office Live Communications Server 2003 Reference Guide.

Page 37

The following information appears in a heading:
Access Rights To The RTC Database
The name of the database in the heading is incorrect. The following is the correct information:
Access Rights To The Live Communications Database

Page 58

The following information appears in the "Global Registrar - WMI Class: MSFT_SIPESGlobalRegistrarSetting" table:
Collapse this tableExpand this table
MinRegistrationExpiryIntSpecifies the minimum expiry in seconds that may be requested by the client for a particular contact. If the value requested by the client in the Expires header is less than this value, then this value is returned in the response.Range: 300 (5 minutes) to 900 (15 minutes) Default: 300 seconds (5 minutes) Cannot be NULL
DefRegistrationExpiryIntSpecifies the default expiry in seconds that may be requested by the client for a particular contact. If the value requested by the client in the Expires header is less than this value, then this value is returned in the response.Range: 300 (5 minutes) to 900 (15 minutes) Default: 600 seconds (10 minutes) Cannot be NULL
The information in the third column of each of these rows is incorrect. The following is the correct information:
Collapse this tableExpand this table
MinRegistrationExpiryIntSpecifies the minimum expiry in seconds that may be requested by the client for a particular contact. If the client does not specify an Expires header then the default value is used.Range: 300 (5 minutes) to 900 (15 minutes) Default: 300 seconds (5 minutes) Cannot be NULL
DefRegistrationExpiryIntSpecifies the default expiry in seconds that may be requested by the client for a particular contact. If the client does not specify an Expires header then the default value is used.Range: 300 (5 minutes) to 900 (15 minutes) Default: 600 seconds (10 minutes) Cannot be NULL

Page 61

The following information appears in the "Servers - WMI Class: MSFT_SIPESServerSetting" table:
Collapse this tableExpand this table
HomeusersBooleanIndicates whether this server homes users or not. This allows differentiating HS and LD servers.Read only
The information about differentiating servers is incorrect. The following is the correct information:
Collapse this tableExpand this table
HomeusersBooleanIndicates whether this server homes users or not. This allows differentiating HS and FE servers.Read only

Appendix B

The following information appears in table number 36:
HKEY_CURRENT_USER\Software\Policies\Messenger\Client

HKLM_CURRENT_USER\Software\Policies\Messenger\Client
These registry subkeys are incorrect. If you create these registry subkeys, there will be no change from the default settings. The following are the correct registry subkeys:
HKEY_CURRENT_USER\Software\Policies\Microsoft\Messenger\Client

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Messenger\Client

APPLIES TO
  • Microsoft Office Live Communications Server 2003
Keywords: 
kbinfo KB834476
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate