Microsoft Office Communications Server 2007 R2 Client and Devices Technical Reference

Quick Details

File Name:
OCS 2007 R2 Technical Reference for Clients.doc

Version:
1.0

Date Published:
7/30/2009

Language:
English

Download Size:
1.1 MB

get it here

Microsoft Office Communications Server 2007 R2 Attendant Hotfix KB 970275

get it here

the desciption should be on this link but its not working ?

http://support.microsoft.com/kb/970275 some kind of bad/wrong link on this page, when clicking the “972402”

******from page*****

Issue that this update package fixes

This update package fixes the following issue:

• 972402 (http://support.microsoft.com/kb/972402/ ) Office Communicator 2007 R2 runs concurrently with Office Communications Server 2007 R2 Attendant

Office Communications Server 2007 R2 Capacity Planning Tool

Get it here

Udate/new Capacity Planning Tool

ssue Fixed: UserProfileGenerator load problem for AV and Appsharing scenario
Explanation: As mentioned in the release notes for the previous OCS 2007 R2 Capacity planning tools release, UserProfileGenerator was generating incorrect load for AV and Appsharing scenarios. This QFE fixes this issue and UserProfileGenerator should generate correct load for various load settings: low, medium & high.
Issue Fixed: Ocsstress needs a _Total instance
Explanation: A “_Total” performance counter instance was added to Ocsstress. This new instance makes it easier to monitor Ocsstress performance counters.
Issue Fixed: Ocsstress should not update the CallsFailed counter for 486 , 603 etc decline specific responses
Explanation: Ocsstress was wrongfully reporting calls which received valid responses such as 486 busy, 603 decline as calls failed. These calls are no longer marked as failed and are considered a successful call-routing scenario.

Microsoft Office Communicator 2007 Hotfix KB 969694

Get it here

File Name:
communicator.msp

Version:
2.0.6362.137

Knowledge Base (KB) Articles:
KB969694

Date Published:
7/28/2009

Language:
English

Download Size:
5.8 MB

Office Communicator Phone Edition (2007 R2) (6907.35)

New update

File Name:
UCUpdates.exe

Version:
6907.35

Get it here

Microsoft Office Communications Server 2007 R2 Hotfix KB 968802

Get more info here

Updates that are released for Communications Server 2007 R2

• Update for Application Host

  967832 (http://support.microsoft.com/kb/967832/ ) Description of the update package for Communications Server 2007 R2 Application Host: April 2009

• Update for Application Sharing Server

  971296 (http://support.microsoft.com/kb/971296/ ) Description of the update package for Office Communications Server 2007 R2, Application Sharing Server: July 2009

• Update for Administration Tools

  971289 (http://support.microsoft.com/kb/971289/ ) Description of the update package for Office Communications Server 2007 R2, Administration Tools: July 2009

• Update for Audio/Video Conferencing

  971793 (http://support.microsoft.com/kb/971793/ ) Description of the update package for Office Communications Server 2007 R2, Audio/Video Conferencing Server: July 2009

• Update for Core Components

  971299 (http://support.microsoft.com/kb/971299/ ) Description of the update package for Office Communications Server 2007 R2, Core Components: July 2009

• Update for Communicator Web Access

  969824 (http://support.microsoft.com/kb/969824/ ) Description of the update package for Office Communications Server 2007 R2, Communicator Web Access: July 2009

• Update for Conferencing Attendant

  968922 (http://support.microsoft.com/kb/968922/ ) Description of the update package for Office Communications Server 2007 R2, Conferencing Attendant: July 2009

• Update for Conferencing Announcement Service

  969823 (http://support.microsoft.com/kb/969823/ ) Description of the update package for Office Communications Server 2007 R2, Conferencing Announcement Service: July 2009

• Update for Monitoring Server

  971298 (http://support.microsoft.com/kb/971298/ ) Description of the update package for Office Communications Server 2007 R2, Monitoring Server: July 2009

• Update for Mediation Server

  969835 (http://support.microsoft.com/kb/969835/ ) Description of the update package for Office Communications Server 2007 R2, Mediation Server: July 2009

• Update for Outside Voice Control

  967835 (http://support.microsoft.com/kb/967835/ ) Description of the update package for Communications Server 2007 R2, Outside Voice Control: April 2009

• Update for Response Group Service

  967829 (http://support.microsoft.com/kb/967829/ ) Description of the update package for Communications Server 2007 R2, Response Group Service: April 2009

• • Update for Standard/Enterprise edition Server

  969821 (http://support.microsoft.com/kb/969821/ ) Description of the update package for Office Communications Server 2007 R2: July, 2009

• Update for Standard/Enterprise edition Server Back End

  969834 (http://support.microsoft.com/kb/969834/ ) Description of the update package for Office Communications Server 2007 R2 database: July, 2009

• Update for Unified Communications Managed API 2.0 Core Redist 64-bit

  970679 (http://support.microsoft.com/kb/970679/ ) Description of the update package for Office Communications Server 2007 R2, Unified Communications Managed API 2.0 Core Redist 64-bit: July 2009

• Update for Web Conferencing Server

  971297 (http://support.microsoft.com/kb/971297/ ) Description of the update package for Office Communications Server 2007 R2, Web Conferencing Server: July 2009

• Update for Web Components Server

  967830 (http://support.microsoft.com/kb/967830/ ) Description of the update package for Communications Server 2007 R2, Web Components: April 2009

Microsoft Office Communicator 2007 R2 Hotfix KB 969695

File Name:
communicator.msp

Version:
6907.37

Knowledge Base (KB) Articles:
KB969695

Date Published:
7/28/2009

Language:
English

Download Size:
9.9 MB

Issues that this update fixes

This cumulative update fixes the following issues:

• 971843 (http://support.microsoft.com/kb/971843/ ) Enterprise administrators cannot both set and enforce the Personal Information Manager settings for Outlook Integration to be able to turn off Outlook Integration for Microsoft Office Communicator 2007 R2

• 972085 (http://support.microsoft.com/kb/972085/ ) Error message when you start Microsoft Office Communicator 2007 R2: "Either there is no default mail client or the current mail client cannot fulfill the message request. Please run Microsoft Office Outlook and set it as the default mail client."

• 972087 (http://support.microsoft.com/kb/972087/ ) In Communicator 2007 R2 when you use Tanjay to call a user, you hear both the ringing and the audio from the user side

• 972090 (http://support.microsoft.com/kb/972090/ ) Your voice is discontinuous when you use Microsoft Office Communicator 2007 R2 to make a call on a Windows 7 or a Windows Server 2008 R2-based remote desktop

• 972091 (http://support.microsoft.com/kb/972091/ ) Error message in Communicator 2007 R2 when you try to join a conference call from Outlook: "Can't open the program because Office Communicator or Office Communications Server Attendant is already running on your windows user account"

• 971845 (http://support.microsoft.com/kb/971845/ ) The delegate permissions feature in Office Communicator 2007 R2 is unavailable to non-unified communications users

• 971846 (http://support.microsoft.com/kb/971846/ ) Video frames are not displayed in Office Communicator 2007 R2 on a Windows XP-based computer

• 972093 (http://support.microsoft.com/kb/972093/ ) Error message when you try to adjust the volume during a call in a Communicator 2007 R2 conversation window on a computer that is running Windows XP: "Cannot adjust the speaker volume"

• 972097 (http://support.microsoft.com/kb/972097/ ) Error message when distribution group expansion fails in Office Communicator 2007 R2: "Cannot save a local copy of your distribution groups."

• 972099 (http://support.microsoft.com/kb/972099/ ) A "Meet Now - Invite by Email" HTML e-mail message that is generated by Microsoft Office Communicator 2007 R2 has unreadable text in the message body

• 972403 (http://support.microsoft.com/kb/972403/ ) Communicator 2007 R2 users may experience network performance issues that are caused by Global address list (GAL) full file download or GAL delta file download

This cumulative update, together with update 969696 and update 969821, fixes the following issue:

• 971628 (http://support.microsoft.com/kb/971628/ ) When a delegate on behalf of a manager tries to use the Conferencing Add-in for Outlook to schedule a live meeting or to schedule a conference, the delegate's information instead of manager's information displays in the conferencing request unexpectedly

  Note To resolve this issue, you have to apply update 969695, update 969696, and update 969821.
  For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

  969696 (http://support.microsoft.com/kb/969696/ ) Description of the update for Live Meeting Conferencing Add-in for Outlook: July 2009

  969821 (http://support.microsoft.com/kb/969821/ ) Description of the update package for Office Communications Server 2007 R2: July, 2009

This cumulative update also includes the following previously released update:

• 971078 (http://support.microsoft.com/kb/971078/ ) An Automatic Update download is not initiated on a computer that is running Office Communicator 2007 R2 build 3.5.6907.9

• 968504 (http://support.microsoft.com/kb/968504/ ) Description of the Communicator 2007 R2 update for Microsoft Online Services

• 968623 (http://support.microsoft.com/kb/968623/ ) You experience one-way audio when LG-Nortel IP8540 or Polycom CX700 phones are used in an Audio Video call on Windows XP

• 968624 (http://support.microsoft.com/kb/968624/ ) Error events occur when you disconnect a computer that is running Communicator 2007 R2 from the network: "Event ID: 3" or "Event ID: 7"

• 968625 (http://support.microsoft.com/kb/968625/ ) Description of a hotfix that applies the initial changes for the integration of Office Communicator 2007 R2 and the next version of Office after the Office 2007 release

• 968628 (http://support.microsoft.com/kb/968628/ ) Communicator 2007 R2 stores the Actual Remote Number (The number that is dialed) for outgoing calls to a remote party

• 968631 (http://support.microsoft.com/kb/968631/ ) The font in the Conversation window is very small when you run Office Communicator 2007 R2 on a Windows Vista-based computer that has high DPI (120 DPI) with Internet Explorer 8 installed

• 968632 (http://support.microsoft.com/kb/968632/ ) You cannot click the password field and enter a password when you sign in to Office Communicator 2007 R2

• 968634 (http://support.microsoft.com/kb/968634/ ) Description of Office Communicator 2007 R2 update to support Polycom roundtable devices

• 968690 (http://support.microsoft.com/kb/968690/ ) In Office Communicator 2007 R2, User A gets a failure-to-deliver message after sending an IM to User B even though User B receives the message

CoMo and CLIP SA: (Calling Line Identification Presentation Special Arrangement)

Problem/issue regarding “caller number” when using simultan ringing and Calling Line Identification Presentation Special Arrangement  (CLIP SA).

When you have that service (CLIPSA) from your Telco provider, you have the possibility to see the Originate Caller number displayed on your Mobile phone.
But in OCS R2 it depend on if you are logged in to CoMo or not.

Problem:
Originate Caller number not sent to the mobile when logged in on CoMo, then it’s my company number (DID) as the caller number.
But the Originate Caller number is sent  when  not logged in on CoMo.

It’s not a problem if you see the “popup/toast” on your mobile, here you can see who the caller is, but if you like to use your call history on you mobile you will only see your own DID as caller ID. Okay then you can use the “last contact” in CoMo, but you haven’t any call detail (date-time) so this “last contact” list isn’t that useful.

Read more about CLIP SA here:

http://www.cept.dk/F580A011-3400-4C40-AB6E-40CAFE055F57?frames=no&

http://www.erodocdb.dk/Docs/doc98/Official/Pdf/ECCRec0301.pdf

http://www.anacom.pt/streaming/en_300089v030101p.pdf?categoryId=115679&contentId=201615&field=ATTACHED_FILE

http://www.niccstandards.org.uk/files/current/nd1202_2000_01.pdf?type=pdf

Microsoft Office Communications Server 2007 R2 Documentation

Communications_Server_2007_R2_Documentation.chm

Communications_Server_2007_R2_Documentation.zip

OCS 2007 R2 Administering CWA.doc

OCS 2007 R2 Administering Group Chat.doc

OCS 2007 R2 Administering OCS.doc

OCS 2007 R2 Backup and Restoration.doc

OCS 2007 R2 Command Line Reference.doc

OCS 2007 R2 Deploy Monitoring Server.doc

OCS 2007 R2 Deploying Archiving Server.doc

OCS 2007 R2 Deploying Communicator.doc

OCS 2007 R2 Deploying CWA.doc

OCS 2007 R2 Deploying Dial-In Conferencing.doc

OCS 2007 R2 Deploying Edge Servers.doc

OCS 2007 R2 Deploying Enterprise Edition.doc

OCS 2007 R2 Deploying Enterprise Voice.doc

OCS 2007 R2 Deploying Group Chat Server.doc

OCS 2007 R2 Deploying in a Multiforest Topology.doc

OCS 2007 R2 Deploying Monitoring Server.doc

OCS 2007 R2 Deploying Response Group Service.doc

OCS 2007 R2 Deploying Standard Edition.doc

OCS 2007 R2 Getting Started - Documentation Roadmap.doc

OCS 2007 R2 Getting Started - New Client Features.doc

OCS 2007 R2 Getting Started - New Server Features.doc

OCS 2007 R2 Getting Started - Technical Overview.doc

OCS 2007 R2 Getting Started - Unified Communications Glossary.doc

OCS 2007 R2 Migration from 2005.doc

OCS 2007 R2 Migration from 2007.doc

OCS 2007 R2 Planning.doc

OCS 2007 R2 Preparing Active Directory Domain Services.doc

OCS 2007 R2 Security.doc

OCS 2007 R2 Supportability.doc

OCS 2007 R2 Technical Reference for Clients.doc

OCS 2007 R2 Technical Reference.doc

OCS 2007 R2 Troubleshooting.doc

OCS 2007 R2 Upgrading the Evaluation to Full Released Version.doc

OCS 2007 R2 Walkthrough - Mediation Server Replacement.doc

OCS 2007 R2 Walkthrough - Scale to Load Balanced Edge Server.doc

OCS 2007 R2 Walkthrough - Scale to Load Balanced EE Pool.doc

OCS 2007 R2 Walkthrough – Small- to-Medium Business Deployment.doc

OCS 2007 R2 Walkthrough - Voice Deployment.doc

Get it them one by one here or get them all by downloading this ZIP file Communications_Server_2007_R2_Documentation.zip

Mobile Communicator vs Communicator

I often get this questions why isn’t it the same phone numbers that I see on my Company contact on my Mobil Communicator and my Communicator.
Or questions like this: on my Mobile Communicator I can’t see any phone number at all on company contact, but in my Communicator I can see Work-Mobile-Privat.

My quick answer is: The Mobile Communicator doesn’t have a Global adresse list locally. and the “publish this phone number” in Communicator isn’t set.

Conclusion: If you like other users to see your phone number, you must use the “Publish this phone number” and the “level of access” to choose what number they can see in Mobile Communicator, regardless of they are users from your AD/organization/OCS system.
This is not like the way “PC” Communicator normaly interact!

The way that the Mobile Communicator get phone number is when it’s gets the contactcard in the Presence XML document on its contacts, at logon or update.

This table show what you see and don’t see when numbers are publish in Active Directory, and have set the “publish this phone number” in communicator, in combination with access level.

This behavior is like when one of you contact is a Federated contact and you like them to be able to see your phone numbers.

In the presence XML Document that users publish to the front-end server is all the information on what the Mobile Communicator can see and can’t see.

Use Snooper to trace:

SIP Snooper trace of a posted presence XML document from client where no numbers have set the “publish this phone number” (notes the <publish>FALSE</publish> )

<userInformation xmlns="http://schemas.microsoft.com/2006/09/sip/options/userInformation"><phones>

<phonetype="work"><publish>false</publish><readOnly>true</readOnly><displayString>+4589490123</displayString><uri>tel:+4589490123</uri></phone>

<phonetype="mobile"><publish>false</publish><readOnly>true</readOnly><displayString>+4747474747</displayString><uri>tel:+4747474747</uri></phone>

<phonetype="home"><publish>false</publish><readOnly>true</readOnly><displayString>+4646464646</displayString><uri>tel:+4646464646</uri></phone>

<phonetype="other"><publish>false</publish></phone></phones><callHandlingList><lastPhone><displayString>90138</displayString><uri>tel:+4589490138;ext=90138</uri></lastPhone></callHandlingList></userInformation>

******************************************************************************

Snooper trace: this XML post is when work number is set to “publish this phone number” (notes the missing <publish>FALSE</publish> on work number)

<userInformation

xmlns="http://schemas.microsoft.com/2006/09/sip/options/userInformation">

<phones><phonetype="work"><readOnly>true</readOnly><displayString>+4589490123</displayString><uri>tel:+4589490123</uri></phone>

<phonetype="mobile"><publish>false</publish><readOnly>true</readOnly><displayString>+4747474747</displayString><uri>tel:+4747474747</uri></phone>

<phonetype="home"><publish>false</publish><readOnly>true</readOnly><displayString>+4646464646</displayString><uri>tel:+4646464646</uri></phone>

<phonetype="other"><publish>false</publish></phone></phones><callHandlingList><lastPhone><displayString>90138</displayString><uri>tel:+4589490138;ext=90138</uri></lastPhone></callHandlingList></userInformation>
</category>

Snooper trace: This part of the contactcard is what mobile Communicator get from the front-end server (notes the work number is in this)

</contactCard>
</category>
<category name="contactCard" instance="3" publishTime="2009-07-24T14:22:00.127">
<contactCard xmlns="http://schemas.microsoft.com/2006/09/sip/contactcard">
                <phone type="work">
                    <uri>tel:+4589490123</uri>
                </phone>
            </contactCard>

Here you can read a bit more on setting phone option.

In the text below from this link, it says that you can’t unpublish this number when its provided from Activ directory, thats not the case when you are using Mobil communicator, only when using “PC”Communicator, On Mobile Communicator you can’t see any numbers on your contacts if they haven’t set this “publish”

Text from link *********
About Active Directory and why some phone numbers cannot be modified or unpublished

Phone numbers that are provided to Communicator from Active Directory will appear in the Phones tab as inactive fields and cannot be edited. Additionally, these numbers cannot be unpublished. Clearing the Publish check box for numbers provided from Active Directory will not unpublish the number.

Setting access level

Snooper trace where a user set's access level for jan@ocsblogs.eu to Personal

Message-Body: <setContainerMembers xmlns="http://schemas.microsoft.com/2006/09/sip/container-management"><container id="400" version="8"><member action="add" type="user" value="jan@ocsblogs.eu"/></container></setContainerMembers>
$$end_record

Container ID Description 
100 Presence is accessible by all federated users.

200 Users from the same company can access the presence data of the publisher.

300 The team members of the publisher can access the presence data of the publisher.

400 Specified subscribers have unrestricted access to the presence data, including sending a potentially interruptive IM invitation when the publisher's status is displayed as Do Not Disturb.

32000 The specified members are blocked to view the presence data. The category instances should be empty category elements.

Exchange 2007 and Reverse number lookup RNL

When Troubleshooting Exchange UM and RNL (reverse number lookup) Jens has a blog on how Exchange behave and Glen has a  blog regarding diagnostic logging.

Then key takeaways in Jens blog on Exchange and RNL, is that Exchange UM use the Active Directory attribute msRTCSIP-Line and personal contacts for RNL.

When you need to troubleshoot Exchange UM you set the Loglevel on Exchange UM with Glen’s Powershell script and then you will get all the “debug like” information in the eventlog on Exchange

Event log Category: get info here

Jens blog on Exchang UM here

Glen’s blog about diagnostic logging here and the script to set loglevel is here

Nortel announced it has entered into a “stalking horse” asset and share sale agreement with Avaya Inc.

Today is an important day for Nortel Enterprise Solutions. Following our announcement on June 19th that Nortel is advancing in its discussions to sell its businesses, Nortel announced it has entered into a “stalking horse” asset and share sale agreement with Avaya Inc. for its North American, Caribbean, Latin American and Asia Enterprise Solutions business, and an asset sale agreement with Avaya for the Europe, Middle East and Africa portion of its Enterprise Solutions business, for US$475 million. These agreements include the planned sale of substantially all of the assets of the Enterprise Solutions business globally as well as the shares of Nortel Government Solutions Inc. and DiamondWare, Ltd.

get more info here

Update Rollup 9 for Exchange Server 2007 Service Pack 1 (KB970162)

Issues that the update rollup fixes

Update Rollup 9 for Exchange Server 2007 SP1 fixes the issues that are described in the following Microsoft Knowledge Base articles:

• 943073 (http://support.microsoft.com/kb/943073/ ) An image attachment appears as a red "X" when you send an RTF e-mail message from an Exchange Server 2007 organization to an external recipient

• 945877 (http://support.microsoft.com/kb/945877/ ) The "eseutil /k" command takes a long time to verify the checksum of transaction logs in Exchange Server 2007 Service Pack 1

• 947662 (http://support.microsoft.com/kb/947662/ ) The transport rule "when the Subject field or the body of the message contains text patterns" does not work accurately on an Exchange Server 2007 Service Pack 1-based computer

• 954739 (http://support.microsoft.com/kb/954739/ ) The Exchange Impersonation feature does not work if a cross-forest topology has only a one-way trust relationship between forests in Exchange Server 2007 Service Pack 1

• 957137 (http://support.microsoft.com/kb/957137/ ) The reseed process is unsuccessful on the CCR passive node after you restore one full backup and two or more differential backups to the CCR active node in Exchange Server 2007 Service Pack 1

• 957374 (http://support.microsoft.com/kb/957374/ ) The Microsoft Exchange Replication service on a Standby Continuous Replication (SCR) target server continually crashes when you enable SCR for a storage group on an Exchange Server 2007 Service Pack 1-based computer

• 959559 (http://support.microsoft.com/kb/959559/ ) Transaction log files grow unexpectedly in an Exchange Server 2007 Service Pack 1 mailbox server on a computer that is running Windows Server 2008

• 961124 (http://support.microsoft.com/kb/961124/ ) Some messages are stuck in the Outbox folder or the Drafts folder on a computer that is running Exchange Server 2007 Service Pack 1

• 961544 (http://support.microsoft.com/kb/961544/ ) Mobile users whose location is set to New Zealand cannot synchronize an exceptional occurrence after the daylight saving time (DST) update that is described in KB 951072 is installed on an Exchange 2007 Service Pack 1 Client Access server (CAS)

• 961551 (http://support.microsoft.com/kb/961551/ ) An error message is returned when you run the Get-Recipient command in the Exchange Management Shell that uses a Windows 7 domain controller

• 963679 (http://support.microsoft.com/kb/963679/ ) The Update-Recipient command does not update specified domain controller parameters when you use Identity Lifecycle Manager (ILM) 2007 to migrate mail users to mailbox users in Exchange Server 2007 Service Pack 1

• 967479 (http://support.microsoft.com/kb/967479/ ) Entourage clients cannot synchronize with mailboxes that are located on a computer that is running Exchange 2007 Service Pack 1 and Windows Server 2008

• 967525 (http://support.microsoft.com/kb/967525/ ) Error 4 is returned when you synchronize a supported list of contact properties by using Exchange ActiveSync in Exchange Server 2007 Service Pack 1

• 967605 (http://support.microsoft.com/kb/967605/ ) A non-delivery report (NDR) is returned when a user sends an e-mail message to an X.400 address that includes the slash field separator in Exchange Server 2007 Service Pack 1

• 967676 (http://support.microsoft.com/kb/967676/ ) E-mail address properties of contacts changed through Exchange Web Services (EWS) are not updated in Outlook or Outlook Web Access (OWA) in Exchange Server 2007 Service Pack 1

• 967739 (http://support.microsoft.com/kb/967739/ ) If a sender requests a delivery receipt in an e-mail message, a delivery status notification (DSN) message is returned that has a blank subject in the body even though the original message contains a subject in Exchange Server 2007 Service Pack 1

• 968081 (http://support.microsoft.com/kb/968081/ ) Monthly recurring meetings are declined if the "Schedule only during working hours" option is enabled in Exchange Server 2007 Service Pack 1

• 968106 (http://support.microsoft.com/kb/968106/ ) Outlook clients are directed to global catalogs from the wrong domain if you are using a split session configuration to enable Outlook clients to access their mailboxes through an RPC/HTTP proxy server in Exchange Server 2007 Service Pack 1

• 968111 (http://support.microsoft.com/kb/968111/ ) Event ID 4999 is logged when an administrator deletes a mailbox store on an Exchange Server 2007 Service Pack 1-based server

• 968205 (http://support.microsoft.com/kb/968205/ ) The Microsoft Exchange Information Store service crashes every time that a specific database is mounted on a computer that is running Exchange Server 2007 Service Pack 1

• 968224 (http://support.microsoft.com/kb/968224/ ) You still receive unexpected error messages when you run the Test-OwaConnectivity command or the Test-ActiveSyncConnectivity command after you apply hotfix KB954213 on an Exchange 2007 Service Pack 1-based server

• 968322 (http://support.microsoft.com/kb/968322/ ) An HTTP 500 error message is returned when you send a message that has a large attachment by using Outlook Web Access (OWA) with S/MIME installed in Exchange Server 2007 Service Pack 1

• 968350 (http://support.microsoft.com/kb/968350/ ) When you change the location field of a recurring calendar item to empty in Exchange Server 2007 Service Pack 1, the location field is set to the default value of the recurring series if this recurring item is synchronized on a Windows Mobile device

• 968621 (http://support.microsoft.com/kb/968621/ ) The Microsoft Exchange Information Store service crashes when you use a Data Protection Manager (DPM) 2007 server to perform a snapshot backup for an Exchange Server 2007 Service Pack 1 server

• 968626 (http://support.microsoft.com/kb/968626/ ) Event ID 1009 is logged when you use an application to access a shared mailbox by using the POP3 protocol in Exchange Server 2007 Service Pack 1

• 968651 (http://support.microsoft.com/kb/968651/ ) Exchange Server 2007 Service Pack 1 servers continue to contact a domain controller even after you exclude it by using the Set-ExchangeServer command

• 968715 (http://support.microsoft.com/kb/968715/ ) Both public logons and private logons that connect to a Client Access server (CAS) proxy are processed as private logons on an Exchange Server 2007 Service Pack 1-based server

• 969054 (http://support.microsoft.com/kb/969054/ ) Error message after an Exchange Server 2007 Service Pack 1 user replies to a message that has more than 300 recipients in Outlook Web Access (OWA): "Microsoft Exchange issued an unexpected response (500)"

• 969089 (http://support.microsoft.com/kb/969089/ ) Some databases are not mounted on the target server after you use the Move-ClusteredMailboxServer command to transfer a clustered mailbox server (CMS) to an available passive cluster node in Exchange Server 2007 Service Pack 1

• 969129 (http://support.microsoft.com/kb/969129/ ) HTML e-mail messages that have a charset META tag that differs from the MIME charset tag are garbled when they are processed through disclaimer rules in Exchange Server 2007 Service Pack 1

• 969324 (http://support.microsoft.com/kb/969324/ ) Outlook crashes when you try to use Outlook to view e-mail messages that are arranged by subject in Exchange Server 2007 Service Pack 1

• 969436 (http://support.microsoft.com/kb/969436/ ) You cannot log on to a hidden mailbox by using Base64 authentication for IMAP4 or for POP3 in an Exchange Server 2007 Service Pack 1 environment

• 969838 (http://support.microsoft.com/kb/969838/ ) An error message is returned when a user tries to change a recurring appointment in Office Outlook Web Access that was created in Outlook 2007 in Exchange Server 2007 Service Pack 1

• 969911 (http://support.microsoft.com/kb/969911/ ) Mailboxes do not follow E-mail Lifecycle (ELC) configuration or storage limitation policies in Exchange Server 2007 Service Pack 1

• 969943 (http://support.microsoft.com/kb/969943/ ) Memory leaks occur in the Powershell.exe process when you run the Get-MailboxStatistics command and the Get-PublicFolderStatistics command in Exchange Server 2007 Service Pack 1

• 969969 (http://support.microsoft.com/kb/969969/ ) Error message when an Exchange Server 2007 Service Pack 1 user tries to delete a calendar item in OWA: "Outlook Web Access has encountered a Web browsing error"

• 970028 (http://support.microsoft.com/kb/970028/ ) The Store.exe process crashes when you use a WebDAV application to connect to Exchange Server 2007 Service Pack 1

• 970086 (http://support.microsoft.com/kb/970086/ ) Exchange Server 2007 Service Pack 1 crashes when the Extensible Storage Engine (ESE) version store is out of memory on a computer that is running Windows Server 2008

• 970277 (http://support.microsoft.com/kb/970277/ ) The System Attendant (SA) resource is not brought online or offline during a failover in an Exchange 2007 Service Pack 1 cluster environment

• 970444 (http://support.microsoft.com/kb/970444/ ) A move operation between an Exchange Server 2003-based server and an Exchange Server 2007 Service Pack 1-based server fails if the SimpleDisplayName attribute of a mailbox in the Exchange Server 2003-based server contains a single quotation mark

• 970515 (http://support.microsoft.com/kb/970515/ ) You receive an error message when you try to use the "New-Mailbox" command to create more than 1000 users who have the same “mailNickname” attribute (alias) in Exchange Server 2007 Service Pack 1

• 970526 (http://support.microsoft.com/kb/970526/ ) The EdgeTransport.exe process on a computer that is running Exchange Server 2007 Service Pack 1 crashes when a MIME message that contains iCAL items for a recurring meeting has more than 999 occurrences

• 970725 (http://support.microsoft.com/kb/970725/ ) Public folder replication messages stay in the local delivery queue and cause an Exchange Server 2007 Service Pack 1 database to grow quickly

• 970993 (http://support.microsoft.com/kb/970993/ ) Error message when a user tries to perform an address book search by using Outlook Web Access in an Exchange Server 2007 Service Pack 1 environment: “The item that you attempted to access appears to be corrupted and cannot be accessed.”

get it here

FSOCS performance analysis and capacity planning document

Document provides insights into performance testing and analysis conducted for the Forefront security for Office Communication Server. The document also provides the user with the information needed to petform capacity planning for the deployment and installation of Forefront Security for Office Communication Server.

get it here

update for Communicator Mobile 2007 R2: July 2009 (kb969816)

Issues that this hotfix package fixes

• Homescreen support for new homescreens in Windows Mobile 6.5+ phones.
• Integration within the phone dialer for Windows Mobile 6.5+ phones.
• Communicator Mobile 2007 R2 now recognizes when the phone is roaming, and by default does not sign in to roaming networks.
• Additional support for joining conference calls from a Windows Mobile appointment. To do this, press Menu, and then press Join Conference.
• Enables users to log on with a username of the format user@example.com, in addition to domain\user.
• When placing Call via Work calls, callbacks are now automatically accepted.
• Microsoft Installer (MSI) installation on Windows XP Service Pack 3 (SP3) fails. In this situation, users should install Communicator Mobile 2007 R2 by using a .Cab installation.
• AT&T FUZE devices set for High-Speed Downlink Packet Access (HSDPA) connection cannot handle voice and data at the same time. This causes Call via Work calls to fail unless the device is reverted to 3rd Generation (3G) by disabling HSDPA.

get it here

FYI:
If you upgrade the old version of COMO and you have set remember password and the Mobile number for call back are reset/removed!

OCS R2 BPA and Windows 2008 sp2

I hope and I think that OCS R2 is supported on Windows 2008 sp2 but OCS BPA dosen’t like Windows 2008 sp2 (build 6.0.6002)

Server OCSR2-FE.domain.org is running a prerelease version of Windows Server 2008. Current installed build: 6.0.6002.

  

And OCS BPA dosen’t find missing KB972041

It must be time for a update for the OCS BPA !

btw: If you install windows 2008 sp 2 remote, don’t panic it takes time to update to sp2 and you will be able to connect remote after the reboot, but it takes a little longer that a normal boot ;)

Office Communications Server Public IM Connectivity Provisioning Guide

Information Required for Provisioning

To provision Office Communications Server public IM connectivity, you need the following information:

· Microsoft Agreement Number

· Access Edge service fully qualified domain name (FQDN)

· Primary Session Initiation Protocol (SIP) domain

· Any additional SIP domains

· Any additional Access Edge service FQDNs

· Contact information

get it here

OCS: MSN PIC for free :)

Windows Live: Customers with Office Communications Server 2007 R2 Standard Client Access License or Office Communications Server 2007/ Live Communications Server 2005 SP1 Standard CAL license with active Software Assurance (SA) qualify for federation with Windows Live Messenger without additional licensing requirements. Customers who do not meet the qualifying requirement should buy the Office Communications Server Public IM Connectivity license for federation with Windows Live Messenger.

AOL/Yahoo!: Federation with AOL and Yahoo! requires the Office Communications Server Public IM Connectivity (PIC) per user subscription license. The PIC License provides connectivity to both IM service providers. There are no license options for connectivity to only one provider, but administrators can choose which service provider they provision.

Get more info here

http://www.microsoft.com/communicationsserver/en/us/public-im-connectivity.aspx

http://blogs.technet.com/mikkelbn/default.aspx

http://www.microsoft.com/communicationsserver/en/us/public-im-connectivity.aspx