Friday, December 11, 2009

Update Rollup 1 for Exchange Server 2010 (KB976573)

get it here

Issues that the update rollup fixes.

Update Rollup 1 for Exchange Server 2010 fixes the issues that are described in the following Microsoft Knowledge Base articles:

977439 (http://support.microsoft.com/kb/977439/ ) Exchange Server 2010 users cannot open certain attachments when they access their mailboxes by using Outlook Web App

977551 (http://support.microsoft.com/kb/977551/ ) Meeting requests that are sent to a room mailbox are not processed in Exchange Server 2010

977552 (http://support.microsoft.com/kb/977552/ ) Exchange RPC Client Access service crashes in the Handler.dll that is located on an Exchange 2010 Client Access service server

977553 (http://support.microsoft.com/kb/977553/ ) Exchange RPC Client Access service crashes in Parser.dll on the Exchange Server 2010 CAS server

977554 (http://support.microsoft.com/kb/977554/ ) The subject or body of a message that is hosted in an Exchange Server 2010 mailbox is not set as expected

977555 (http://support.microsoft.com/kb/977555/ ) The message body is inaccessible when the property conversion from PR_BODY_HTML to PR_BODY fails

977556 (http://support.microsoft.com/kb/977556/ ) The body text of an e-mail message is invisible after you create exceptions for a recurring appointment or for a recurring meeting by using a CDO application together with Exchange Server 2010

977557 (http://support.microsoft.com/kb/977557/ ) An E_FAIL error occurs when you create an exception to a meeting request by using a CDO application for a Microsoft Exchange Server 2010 mailbox

977558 (http://support.microsoft.com/kb/977558/ ) A folder name is not changed when you try to move and then rename the folder in an Exchange Server 2010 mailbox by using the CopyFolder method of the IMAPIFolder interface

977559 (http://support.microsoft.com/kb/977559/ ) The location of a meeting or an appointment is not updated on an Exchange Server 2010 mailbox

977560 (http://support.microsoft.com/kb/977560/ ) Update fails when you use a CDO application to update a recurrence task on Exchange Server 2010

977561 (http://support.microsoft.com/kb/977561/ ) VSS backup process stops responding when you try to perform a Volume Shadow Copy Service (VSS) backup for Exchange Server 2010 databases

Monday, December 7, 2009

Microsoft and Cisco: Joint Interoperability Support Statement

Get it here

Communications server team’s Blog on the subject

Very good blog here on “Make sure you know what you’re buying.”

Cut and paste from this document*************************

Cisco UC IntegrationÔ for Microsoft Office Communicator

Microsoft provides support for its published APIs[1] for Microsoft Office Communications Server and Microsoft Office Communicator to all its ISV partners.  Cisco, a Microsoft Gold Certified Partner, uses these published APIs to develop the Cisco UC IntegrationÔ for Microsoft Office Communicator product.  Microsoft is pleased that Cisco has chosen to leverage Microsoft API’s to provide functionality for our mutual customers as an ISV. 

Cisco, as the developer of the Cisco UC IntegrationÔ for Microsoft Office Communicator, provides support for this product.  Microsoft will provide ongoing support for the published APIs for Microsoft Office Communications Server and Microsoft Office Communicator to our ISV’s, including Cisco.   Microsoft does not provide direct support for the Cisco UC IntegrationÔ for Microsoft Office Communicator.  The Microsoft UC platform will continue to evolve as the industry evolves and customer requirements change, and as with our broader ISV community, Microsoft is fully committed to working with Cisco so they can provide quality support for our mutual customers with future versions of Microsoft Office Communications Server and Office Communicator.

Remote Call Control is supported by Microsoft in Office Communications Server 2007 and Office Communications Server 2007 R2 and will continue to be supported for customers upgrading their Remote Call Control deployments to the next release of Office Communications Server. Microsoft has announced the deprecation of Remote Call Control in Office Communications Server. As a result, in the next release of Office Communications Server, new deployments of Remote Call Control will not be supported by Microsoft.

Direct SIP Interoperability

Microsoft has tested and supports Direct SIP interoperability between Cisco Unified Communications Manager versions 4.x and 5.x and Office Communications Server 2007 and Office Communications Server 2007 R2, as documented on the Microsoft Unified Communications Open Interoperability Program website. While Cisco offers and supports a SIP interface with Cisco Unified Communications Manager versions 4.x and 5.x, interoperability using this interface is only supported for systems that have been tested and documented on the Cisco Interoperability Portal. Cisco has not tested Direct SIP interoperability between Office Communications Server 2007 and Office Communications Server 2007 R2 and Cisco Unified Communications Manager versions 4.x and 5.x.

Cisco has tested and supports Direct SIP interoperability between Microsoft Office Communications Server 2007 and Cisco Unified Communications Manager versions 6.1 and 7.02. Microsoft has tested and supports Office Communications Server 2007 and Office Communications Server 2007 R2 with Cisco Unified Communications Manager version 6.11.

To facilitate interoperability support for our joint customers, both Cisco and Microsoft are members of TSANet, an independent third-party organization that helps coordinate multi-vendor support.


 

Sunday, November 15, 2009

Running Microsoft Office Communications Server 2007 R2 in a Virtualized Topology

Overview

Office Communications Server 2007 R2 can be deployed onto Windows Server 2008 Hyper-V, or onto any virtualization solution that is a certified partner through the Server Virtualization Validation Program (SVVP) certified partners for the following workloads:

  • Presence
  • IM (including conferencing, remote access, federation, and Public IM Connectivity)
  • Group Chat

This whitepaper:
  • Identifies which server roles are supported in a virtualized environment
  • Provides guidance for scaling users and workloads in a virtualized environment


This document describes the results of a series of configurations that were run in a Hyper-V environment to validate that Office Communications Server on Hyper-V provides stable performance and scalability for production use.

get it here

Wednesday, October 28, 2009

Microsoft Office Communications Server 2007 R2 Hotfix KB 975611

Get it here

Version:
6907.56

Knowledge Base (KB) Articles:
KB975611

Date Published:
10/27/2009

Language:
English

Download Size:
378 KB - 53.8 MB*

Issues that this update package fixes
This update package fixes the following issues:

975892 (http://support.microsoft.com/kb/975892/ ) Error message when you send a meeting request for a conference call that is hosted in Office Communications Server 2007 R2, Enterprise Edition

975894 (http://support.microsoft.com/kb/975894/ ) Event ID 44031 for trusted domains is logged frequently in Office Communications Server 2007 R2

This cumulative update also includes the following previously released updates:

968955 (http://support.microsoft.com/kb/968955/ ) A computer that is running Office Communications Server 2007 R2, Audio/Video Conferencing Edge Server crashes when it tries to process a Relay NAT message

972714 (http://support.microsoft.com/kb/972714/ ) Two users unexpectedly join the same conference when they try to join separate conferences in Office Communications Server 2007 R2

972709 (http://support.microsoft.com/kb/972709/ ) Error message when a SIP message request is sent from a federated partner in Communications Server 2007 R2: "500: Server Internal Error"

972700 (http://support.microsoft.com/kb/972700/ ) When Office Communications Server 2007 R2 routes a voice mail call to an Exchange Server 2007 Unified Messaging server, the corresponding invitation message does not indicate that the request originates from Office Communications Server

971844 (http://support.microsoft.com/kb/971844/ ) No calling party name appears in Communicator 2007 R2 when a Private Branch Exchange telephone user calls a Communications Server 2007 R2 user

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

968879 (http://support.microsoft.com/kb/968879/ ) You cannot forward a call between federated users in Communications Server 2007 R2

968938 (http://support.microsoft.com/kb/968938/ ) The Communications Server 2007 R2 - A/V Edge Authentication Server does not recognize a token request if the locale for RTCProxyService is not en-US/409

969010 (http://support.microsoft.com/kb/969010/ ) Communications Server 2007 R2 performance counters are missing in Performance Monitor

968910 (http://support.microsoft.com/kb/968910/ ) Communications Server 2007 does not detect the changes when Unified Messaging dial plans or UM servers are added

This update package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

  • The license expiration date for Office Communications Server (OCS) 2007 R2 Evaluation Edition was calculated incorrectly. This causes OCS 2007 R2 Evaluation Edition to expire on July 13, 2009. This update fixes the license expiration date calculation for the OCS 2007 R2 Evaluation Edition. By downloading this update, the expiration date will be calculated correctly, based on the installation date of the server.
  • Earlier updates of OCS 2007 R2 required Microsoft Message Queuing to be installed on OCS 2007 R2 Enterprise Edition Distributed – Front End or the OCS 2007 R2 Standard Edition. This update removes that requirement.
  • The RTC Media Relay driver in OCS Edge Server has also been updated this update.

Microsoft Office Communicator 2007 R2 Hotfix KB 972884

Get it here

Version:
6907.56

Knowledge Base (KB) Articles:
KB972884

Date Published:
10/27/2009

Language:
English

Download Size:
9.9 MB

Issues that this update fixes
This cumulative update fixes the following issues:
  • 976045 (http://support.microsoft.com/kb/976045/ ) Error message when you try to add a contact to Outlook in Communicator 2007 R2: "Cannot connect to Microsoft Office Outlook to add a contact because Outlook is not responding"

  • 976046 (http://support.microsoft.com/kb/976046/ ) Hyperlinks are converted to lowercase if you send them in an instant message as text in Communicator 2007 R2

  • 976048 (http://support.microsoft.com/kb/976048/ ) Error message when you log off, restart, or shut down a computer that is running Communicator 2007 R2: "End Program - Communicator"

  • 976050 (http://support.microsoft.com/kb/976050/ ) When you answer an incoming call on a device that uses a simultaneous ring number, Office Communicator 2007 R2 generates a missed call notification

  • 976051 (http://support.microsoft.com/kb/976051/ ) The Communicator 2007 R2 screen freezes intermittently for several seconds when you are in an audio or a video conferencing session

  • 976052 (http://support.microsoft.com/kb/976052/ ) The display name of a contact is unresolved when you send a meeting request in Communicator 2007 R2

  • 976054 (http://support.microsoft.com/kb/976054/ ) Audio skips in Communicator 2007 R2 during Communicator calls or during Public Switched Telephone Network calls on a computer that is running Windows Vista

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 must 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 updates:
  • 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

  • 971844 (http://support.microsoft.com/kb/971844/ ) No name appears in Communicator 2007 R2 when a Private Branch Exchange telephone user calls a Communications Server 2007 R2 user

  • 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

New version: Office Communicator Phone Edition (2007 R2)

get it here

Version:
6907.55

Knowledge Base (KB) Articles:
KB977065

Date Published:
10/27/2009

Language:
English

Download Size:
12.9 MB

Issues that this update package fixes
This update package fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:
  • When you connect your IP phone through the Internet, the telephone call logs are not populated with received or dialed calls.
  • When you block a contact, you cannot call that contact from the Contact List.
  • After you apply the update package in KB 972398 to your IP phone, the telephone performance becomes slow. The response time of the dial pad also becomes slow
Overview

This download was originally released on February 1, 2009. For a complete list of fixes and changes in this latest version, please see KB article 977065.
Office Communicator Phone Edition, which provides a rich, Office Communicator-like user experience on select standalone IP phones from Microsoft partners (e.g., LG-Nortel IP 8540 and Polycom CX700), has been updated with new functionality that provides an enhanced user experience on these phones:

  • Single sign-in. Users can now connect their Office Communicator Phone Edition phone to their computer with a USB cable and sign in to both their phone and Office Communicator 2007 R2 at the same time.
  • Integration with Office Communicator 2007 R2 on the PC. Users can now click a contact or phone number in their Office Communicator 2007 R2 contact list on their PC to place a call using their Office Communicator Phone Edition phone. Call controls are synchronized on both the phone and Office Communicator on the PC. If their PC is configured with a webcam, users can escalate the call by adding video.
  • Support for new Office Communications Server 2007 R2 voice features. New call delegation, team calling and Response Group service functionality in Office Communications Server 2007 R2 are also supported in Office Communicator Phone Edition.
  • Audio quality enhancements. Latency, audio quality and call setup time have all been improved.
  • User interface enhancements. The user interface has been improved and streamlined. For example, a Redial button enables users to easily redial the last dialed number, searching through the corporate directory is easier, and users can select from one of four ring tones.
  • Office Live Meeting support. Users can now use their Office Communicator Phone Edition phone as an audio device in Office Live Meeting.

FIX for OCS: kb974571 MS09-056: Vulnerabilities in CryptoAPI could allow spoofing

Resolution for the known issue
A fix that resolves this issue is available for download from the Microsoft Download Center. To obtain the fix, visit the following Microsoft Web page:

http://go.microsoft.com/fwlink/?LinkId=168248 (http://go.microsoft.com/fwlink/?LinkId=168248)

The fix (OCSASNFix.exe) is governed by the Microsoft Software License Agreement for Office Communications Server 2007 R2, Office Communications Server 2007, Live Communications Server 2005, Office Communicator 2007 R2, Office Communicator 2007, and Office Communicator 2005.
This fix works for both clients and servers, and it is applicable to the following roles for all versions of Office Communications Server and Live Communications Server 2005 SP1 and for evaluation versions of Office Communicator:

  • Standard Edition Server
  • Director server role
  • Enterprise Edition Consolidated
  • Enterprise Edition Distributed – Front End
  • Edge Server
  • Proxy server role
  • Office Communicator 2007 Evaluation version only
  • Office Communicator 2007 R2 Evaluation version only
  • Office Communicator 2005 Evaluation version only
To run the fix, type the following command at a command prompt, and then press ENTER:

ocsasnfix.exe

When you run the command on a computer that is running Office Communication Server 2007, Office Communication Server 2007 R2, or Live Communications server 2005 Service Pack 1, you receive a message that resembles the following:

http://support.microsoft.com/kb/974571

If you are using non US Explorer, this is the link
http://support.microsoft.com/kb/974571/en-us

Saturday, October 24, 2009

Microsoft Unified Communications Business Value Assessment Toolkit

Download the Unified Communications Business Value Assessment Toolkit (BV Toolkit) and leverage the included resources to drive your customer engagements. Resources include: Customer Engagement Data Sheet, E-mail Invitation Templates, Sales Presentations, Kickoff Presentation Templates and more.

get it here (40mb)

Office Communications Server 2007 Visio stencil

Use the Office Communications Server 2007 Visio stencil to create your own diagrams of Office Communications Server topologies using Visio.

get it here

Thursday, October 22, 2009

New: Office Communications Server Public IM Connectivity Provisioning Guide

Updated: October 2009

This document describes the requirements and processes for provisioning public instant messaging (IM) connectivity for Microsoft® Office Communications Server 2007 R2, Office Communications Server 2007, and Live Communications Server 2005 Service Pack 1 (SP1).

get it here

Office Communications Server Public IM Connectivity Provisioning PIC

and the site to do the provisioning is here

Saturday, October 17, 2009

After installing KB974571 the OCS server might stop working

After installing KB974571 the OCS server might stop working with events like this (se below)

The solution for now, is to remove KB974571 again and stop automatic install update if it’s turn on. just do the setting “download but let me choose when to install them” for now.

After removing KB974571 you need to restart the server.

Event Type:    Error
Event Source:    OCS Server
Event Category:    (1000)
Event ID:    12290
Date:        16-10-2009
Time:        19:47:41
User:        N/A
Computer:    XXXXXXXX
Description:
The evaluation period for Microsoft Office Communications Server 2007  has expired. Please upgrade from the evaluation version to the full released version of the product.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:    Error
Event Source:    OCS Server
Event Category:    (1000)
Event ID:    12299
Date:        16-10-2009
Time:        19:47:41
User:        N/A
Computer: XXXXXXXXX   

Description:
The service is shutting down due to an internal error.

Error Code: C3E93C23 (SIPPROXY_E_INVALID_INSTALLATION_DATA)
Resolution:
Check the previous event log entries and resolve them. Restart the server. If the problem persists contact Product Support Services.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Update Update :)

Update: client update, this is not the case (or at least not on my XP client)

But on my Windows 7 it’s a problem having kb974571 installed  

User desktop that has the KB974571 installed will not be able to login.
Remove the KB974571 from the desktop PC and restart, this should fix the problem.

Source for some of the information on this blog: http://golumolu.in/blogwp/2009/10/ocs-front-end-service-stopped-with-service-specific-error-3286842403-0xc3e93c23-due-to-windows-update-kb974571/

Friday, October 16, 2009

Unified Communications Presentation for Technical Decision Makers

This presentation introduces the Microsoft unified communications value proposition and business value, and helps you to drive customer interest in unified communications solutions.

get it here

Get the white paper: The Total Economic Impact™ Of
Microsoft Unified Communications
Products and Services

In July 2007, Microsoft Corporation commissioned Forrester Consulting to examine the Total
Economic Impact (TEI) and potential return on investment (ROI) that enterprises may realize by
deploying UC products and services (UC products). To understand the financial impact of
Microsoft’s UC products, Forrester conducted in-depth interviews with 15 Microsoft customers and
compiled their results into a composite case study of a 4,000-person digital marketing services
company.
In conducting these in-depth interviews with Microsoft

get it here

Friday, October 9, 2009

Operations Manager 2007 R2 Management Pack

The Operations Manager 2007 R2 Management Pack alerts you to problems with components such as agents, management servers, the Operations Manager database, agents, modules used by workflows and services so that you can continue to monitor the servers and clients that your business depends on.
The management pack includes tasks that you can automate to get easy access to common diagnostic tools, such as restarting a health service or reloading an agent configuration.
Feature Summary
The Operations Manager 2007 R2 Management Packs includes the following features:

  • Local and Remote Monitoring of an Agent’s Health
    • Operations Manager agents monitor themselves for events and performance indicators that signal an issue with the agent’s health.
    • Management servers also maintain an external perspective of an agent’s health via the Health Service Watcher.
    • The ‘Agent Health State’ view provides a side-by-side dashboard of both perspectives on the agent.
  • Optional, Automatic Agent Remediation Capabilities
    • If the Health Service Watcher determines that an agent is unhealthy, a series of diagnostics and recoveries can be enabled to further diagnose the problem and event take actions to attempt to fix the problem (e.g. Ping the server to see if it is completely offline, start a stopped agent, trigger a reinstall, etc.). Refer to the management pack guide for more details.
    • Agents are monitoring their own process to ensure that memory utilization is not sustained at unacceptable levels. If this condition is detected then the agent will automatically restart itself to force the freeing up of memory.
  • Detection of Problems and Misconfigurations with Run As Accounts and Profiles
    • Checks are run on a regular basis to detect if any of the management group’s “Windows” type Run As Accounts have credentials which are about to expire. Alerts will be raised, and where possible this will be done in advance of the credentials expiring to avoid outages.
    • Alerts will be raised if any errors are encountered during the distribution of Run As Accounts.
  • Monitoring of problems with Running Workflows in Management Packs
    • Numerous rules are provided to detect if workflows within management packs are failing. Examples of workflows include discoveries, rules, monitors, etc. Failures can range from bad configurations on the workflows themselves, script failures, permissions problems, etc.

 

get it here

Friday, October 2, 2009

Microsoft Office Communications Server 2007 R2 XMPP Gateway

Office Communications Server 2007 R2, Extensible Messaging and Presence Protocol (XMPP) Gateway enables users to share presence information and communicate via instant messaging (IM) between Office Communications Server and XMPP-based providers and servers, such as Google Talk and Jabber. After XMPP Gateway is deployed in an Office Communications Server environment, users hosted on Office Communications Server can do the following:

· Add or delete users of an XMPP environment as contacts.

· Communicate with users of an XMPP environment through one-on-one IM conversations.

· For details about XMPP Gateway, see http://go.microsoft.com/fwlink/?LinkID=141529.

clip_image002

Sunday, September 27, 2009

New: Office Communicator Mobile 2007 R2 for Java (Nokia S60 240X320 resolution)

Brief Description

Microsoft Office Communicator Mobile for Java is an enterprise client software for Microsoft Office Communications Server 2007 R2 optimized for Java enabled cell phones. The client allows you to view colleagues availability using presence status, initiate single/multi-party IM sessions and get updated contact information from your company directory.

Get it here

Remember that you need CWA running for the Mobile Java client to work and you need to point the client to that (CWA) website and not the Edge server.

more info here

Tuesday, September 15, 2009

UC White Paper

Over the past year, Microsoft and associated research companies have interviewed hundreds of technology professionals at organizations around the world that are either preparing to deploy or in the midst of deploying unified communications (UC). From these discussions, a picture has emerged of the far-reaching impact of UC on the structure of the IT organization, how this affects evaluation and preparation for deployment, and how the resulting changes in IT’s structure may be leveraged to promote increased efficiency, collaboration, and employee satisfaction.

get it here

Unified Communications in Retail

Microsoft offers solutions that connect information, systems, and people to provide retailers a true competitive advantage with compelling customer experiences, improved employee productivity, better inventory utilization, and more efficient store operations.

Get it here

Quick Start Guide for Outlook Voice Access 2010

Overview

Outlook Voice Access lets UM-enabled users to access their Exchange 2010 mailbox using analog, digital, or cellular telephones. By using the menu system found in Outlook Voice Access, UM-enabled users can read e-mail, listen to voice messages, and interact with their Outlook calendar. This quick reference sheet shows the navigational tree and the options that are available to UM-enabled users when they are using Outlook Voice Access.

get it here

Saturday, September 5, 2009

Microsoft Forefront Security for Office Communications Server Best Practices Analyzer

Overview

The Forefront Security for Office Communications Server (FSOCS) Best Practices Analyzer compares your existing FSOCS deployment against recommended best practices to identify configuration setting changes that could help you improve FSOCS performance and malware detection rates. The Best Practices Analyzer is installed alongside the FSOCS administrative console and can query configuration settings on both local and remote server installations. The Best Practices Analyzer does not modify any configuration settings, rather, it alerts the administrator to potential configuration issues and provides guidance on managing gaps in configuration best practices.

get it here

Sunday, August 30, 2009

Exchange 2010 E-Learning

Collection 6899: Exploring Features of Exchange Server 2010

Overview

This two-hour collection provides you with an overview of the new features in Exchange Server 2010. It also describes the enhancements made over Exchange Server 2007.
The clinics within this collection cover:

  • New features in Exchange Server 2010
  • Technology enhancements
  • Management tools used in Exchange Server 2010
  • Managing a Mailbox server
  • Unified Messaging in Exchange Server 2010
  • High availability features in Exchange Server 2010

Users completing this collection should have three or more years of experience working with previous versions of Exchange Server, including the implementation of Exchange Server 2007. They should be familiar with Active Directory, Exchange messaging, and SharePoint and fundamentals of Microsoft Office 2003, Microsoft Office 2007, Windows Server 2003, and Windows Server 2008. It is beneficial if they have experience with a Windows or command-line scripting.

Activate This Collection

Subscription: 1 Year

I have read and accept the End User License Agreement.

This offer includes the following:

Clinic 6900: Introduction to Exchange Server 2010

Clinic 6901: Exchange Server 2010 in an Enterprise

source for this information (Peter Schmidt):  http://www.iis-digest.com/index.php/2009/06/free-exchange-2010-e-learning/

Update to: Unified Communications Phones and Peripherals Datasheet

The datasheet provides the following information about each device:

  • A thumbnail photo of the device
  • Hardware type
  • Name of the partner that produces the device
  • Product name
  • A brief description of the device
  • URL for the partner's Unified Communications landing page

Whitepaper on Deploying Certificates in OCS 2007 and OCS 2007 R2

In this document, you will learn about the properties and attributes of certificates when working with Office Communications Server 2007 and Office Communications Server 2007 R2. This document contains a walkthrough of most of the common, and some optional, tasks that you need to perform to realize the full value of the system. All roles that require certificates for deployment and operation are discussed. The properties are presented along with information to describe what they are and how they are used. This document shows you how to request the right certificate with the right parameters to make sure that you are delivering value to your users, rather than just troubleshooting problems.

Source: http://msgoodies.blogspot.com/2009/08/whitepaper-on-deploying-certificates-in.html

New/more:Office Communications Server 2007 R2 VHD

Date
Revision
Description
April 2009
1.0

Initial Release
June 2009
1.1
Addition of two new VMs, OCS-QMS & GroupChat

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=3ae2a175-d534-4d7f-ad9d-664a448eac31

New version of: Planning Tool for Microsoft Office Communications Server 2007 R2

What’s New in the Planning Tool for Office Communications Server 2007 R2?

· Now supported on Windows Server 2008 (32-bit and 64-bit)
· Exports the topology to the Microsoft Office Visio drawing and diagramming software
· Exports the hardware for all sites to Microsoft Office Excel
· Includes hardware requirements and port information on each server role as well as port information for your firewalls
· Includes Enterprise Voice
· Saves the topology to a location and file name of your choice so that you can reload it at your convenience
· Provides the ability to add, edit, and delete sites
· Provides the ability to print topologies, server information, and planning and deployment steps
· Allows customizing design of each site
· Allows to specify whether you have a perimeter network for a site
· Dynamically draws the topologies faster
· No longer need to run as administrator on Windows Vista
· Introduces new features and topology recommendations for Microsoft Office Communications Server 2007 R2
· Provides a way to bypass the interview questions if you already know what features you want
· The latest update of the Planning Tool includes corrections to ensure the screen can be viewed in the 1024x768 resolution, with the default dpi, on a 14’ and 15’ monitor.

http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=fdf32585-c131-4832-8e27-67e70636c1e8

Sunday, August 23, 2009

Communicator for Iphone or Ipod

What is iDialog?

Microsoft Office Communications Server is revolutionizing the way workers communicate and collaborate.

iDialog is an exclusive product from Modality Systems that enables users to find and communicate with their Microsoft Office Communications Server (OCS) contacts using Apple iPhone or iPod Touch devices.

image

iDialog supports the following features:

  • Display OCS contact list and presence information
  • Set presence information, including custom note and location data
  • Search corporate Global Address List (GAL)
  • Send and receive Instant Messages (IM)
  • Add multiple participants to an IM conversation
  • Manage and participate in multiple IM conversations simultaneously
  • Control incoming OCS Voice calls (forward/redirect an incoming OCS call to another device, such as an iPhone, voice mailbox, or another phone number)
  • Call a phone number listed on a contact card (This feature is not available on iPod Touch devices)
    Send an email to an address listed on a contact card
Deployment Requirements

iDialog is supported on Apple iPhone and iPod Touch versions 2.0 and higher. The user must also have an account that can sign-in to a corporate or hosted OCS 2007 or 2007 R2 system. An OCS Communicator Web Access (CWA) Server must be deployed to support iDialog connectivity. No proprietary server infrastructure is required.

get more info:

http://www.modalitysystems.com/blog/?p=92

and

http://www.modalitysystems.com/idialog/

Action! LifeCam Cinema Introduces 720p HD Widescreen Video

REDMOND, Wash. Aug. 20, 2009 Widescreen technology is everywhere these days, built into virtually every new notebook, desktop monitor and flat-panel TV,1 and today Microsoft Hardware sets a new standard for webcams with the launch of LifeCam Cinema, the first consumer webcam on the PC to offer widescreen video with a native 720p sensor.2 The timing couldn’t be better, with more and more people going online to share videos with friends and family; in fact, more than 10 million videos are uploaded each month to Facebook alone.3 LifeCam Cinema webcam’s 720p widescreen sensor will deliver clear, quality videos — without leaving anyone out of the shot.

lifecam hd

* Basic Video & Audio Functionality with Windows Live™ Messenger, AOL Instant Messenger, Yahoo! Messenger,Skype, QQ and Microsoft® Office Communicator.

More info: http://www.microsoft.com/hardware/digitalcommunication/ProductDetails.aspx?pid=008

http://www.microsoft.com/presspass/press/2009/aug09/08-20cinemapr.mspx

Thursday, August 20, 2009

New device :OCS Device CX300 from Polycom

Okay new rumors :) in my old blog regarding this device and on this picture it has a display, to my knowledge the new CX300 won’t have a display but the number keypad is included and it will be USB connected.

Released (Q3 2009), hope I can get one for test :)

image

Polycom is planning to release more OCS devices ethernet-connected CXxxx in Q1 2010.

Thursday, August 6, 2009

What is a OCS R2 Proxy server?

What is a OCS R2 Proxy ?
I have heard some say: OCS Proxy is a Front without users, but there is more to it than that.

Then only OCS service running on a OCS Proxy is: Office Communications Server Proxy. on a OCS Front-end you will normaly have serval other service running.

On a OCS Proxy server there is no Scripts/Application filers installed.
on a OCS R2 Front end server there is 8 scripts/applications filters installed by default

image

In this screendump the OCS proxy is used for Nortel MCM application and thats the only script/filter installed.

image

The only way that a OCS proxy server can be installed is by commandline (LCSCMD)

On a OCS Proxy you normaly need to do some Host Authorization for the other “normal” OCS server can connect to it. and a OCS proxy server dosen’t need to be in same “Actic directory/Domain” it can be a workgroup server, if needed.

Activating Proxy Server

LCSCmd.exe /Server /user:RTCProxyService /password:<password> /action:activate /role:proxy

Activating WorkGroupProxy Server 

lcscmd /server /user:<user> /password:<password> /action:activate /role:workgroupProxy

Remember on Windows 2008 you must run lcscmd as administrator (“right/click run as”) for the OCS server to register correct.

The only application that I know using OCS proxy, is Nortel MCM.

Nortel Converged Office: http://www142.nortelnetworks.com/mdfs_app/enterprise/cs1000/6.0/pdf/NN43001-121_03.06_Fundamentals_CO_OCS2007.pdf

Wednesday, August 5, 2009

Displayname from OCS R2 kb972721

Then description on how to set it up http://support.microsoft.com/kb/972721/
Please remember you must restart the server for the fix/setting to be applied.

Adam has a blog on what is showing in the toast/popup.

I ran in to some minor issues due to the fact that this fix must be applied “Download the UcmaRedist.msp package now” (http://support.microsoft.com/kb/970679/) my experience is that this fix isn’t applied if using Microsoft autoupdate. 

On Cisco CUCM device->phone->Line”X” setting,  it’s the “ASCII Display (internal Caller ID)” that OCS show in the popup/toast

image 

In Exchange 2007 UM if you get Missed call og Voicemail notification mail, it’s still the phone number, so no Displayname without your create contact with that phone number, more information in this blog.

Monday, August 3, 2009

Microsoft Office Communications Server 2007 R2 Group Chat SDK

get it here

Overview

The Group Chat feature lets organizations set up searchable, topic-based chat rooms that persist over time, allowing geographically distributed teams to better collaborate with one another while preserving organizational knowledge.
The Microsoft Office Communications Server 2007 R2 Software Development Kit (SDK) includes documentation and sample applications developed with the Office Communications Server 2007 R2 platform.

Microsoft Office Communications Server 2007 R2 Group Chat Hotfix KB 969819

Get it here

Issues that this hotfix package fixes
This update package fixes the following issues:
  • 972951 (http://support.microsoft.com/kb/972951/ ) A compliance server reports incomplete or inaccurate information about user JOIN and PART events in Microsoft Office Communications Server 2007 R2 Group Chat Server

  • 972944 (http://support.microsoft.com/kb/972944/ ) You may experience performance issues in a channel server in Communications Server 2007 R2 Group Chat Channel Server

  • 973384 (http://support.microsoft.com/kb/973384/ ) The Group Chat service does not work after you restart a computer that is running Office Communications Server 2007 R2 Group Chat Server

  • 973385 (http://support.microsoft.com/kb/973385/ ) Users in a secured organizational unit (OU) named "Blocking Inheritance" cannot use the Group Chat Admin Tool

  • 973386 (http://support.microsoft.com/kb/973386/ ) A compliance XML output file is not generated by a compliance server in Microsoft Office Communications Server 2007 R2 Group Chat Server

Saturday, August 1, 2009

OCS Connectivity test tool

I my blog on Exchange Connectivity test tool  I mentioned that it would be smart for such a tool for OCS.

So here it is: https://www.testocsconnectivity.com/

My recommendation is to not use your normal account, but perhaps make a test account that you can use to test on this site.

The site is still in Beta !

image

The Exchange connectivity test tool link is here

Friday, July 31, 2009

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

Thursday, July 30, 2009

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

Wednesday, July 29, 2009

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

Tuesday, July 28, 2009

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

Monday, July 27, 2009

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

Sunday, July 26, 2009

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

Friday, July 24, 2009

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.

image

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> )

image

<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>

image

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

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)image

<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>

image

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.

Tuesday, July 21, 2009

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

image

image

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

Saturday, July 18, 2009

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