Archive

Posts Tagged ‘OCS’

Public IM Connectivity Provisioning Guide Released

November 9th, 2010 No comments

A few weeks ago Microsoft released the Public IM Connectivity Provisioning Guide for Microsoft Lync Server, Office Communications Server, and Live Communications Server.

This new guide cover all Lync/OCS/LCS products and the document describes the requirements and processes for activating and provisioning public instant messaging (IM) connectivity for Microsoft Lync Server 2010, Office Communications Server 2007 R2, Office Communications Server 2007, and Live Communications Server 2005.

Download it here.

OCS 2007 R2 updates Released

July 26th, 2010 No comments

Microsoft has released the latest Cumulative update 6 for OCS 2007 R2.

OCS 2007 R2 Server:

OCS 2007 R2 Client:

Group Chat:

  • Office Communications Server 2007 R2, Group Chat Server – KB 2032881Download
  • Office Communications Server 2007 R2, Group Chat Client – KB 2032922Download
  • Office Communications Server 2007 R2, Group Chat Admin Tool – KB 2032949Download

OCS Remote Connectivity Analyzer

January 8th, 2010 No comments

The OCS team has now made a Remote Connectivity Analyzer, like we know from Exchange. The tool is a great way of verifying that your remote access is configured properly.

The Office Communications Server Remote Connectivity Analyzer is a great tool for performing testing, troubleshooting, and diagnostics on OCS 2007 & OCS 2007 R2 deployments. The tool will assist you in finding answers to the before mentioned scenarios.  You should use the RCA as your initial stop when attempting to troubleshoot an OCS edge server connectivity issue. 

The Office Communications Server Remote Connectivity Analyzer is a web site for IT Administrators to validate and diagnose end-to-end Office Communications Server scenarios. The site simulates multiple Office Communications Server client access scenarios from outside the customer’s infrastructure and reports whether the test was successful.  If the test fails, we inform the IT Admin exactly where in the process it failed as well as provide troubleshooting tips on resolving the issue.

The OCS Remote Connectivity Analyzer is found here. Right now the tool is still a BETA release.

OCS 2007 R2 Web Service Provider Released

November 11th, 2009 No comments

Good news – the OCS service provider for Exchange is now released. The OCS service provider will enable IM connectivity to OCS 2007 R2 from Exchange 2010 Outlook Web App (OWA).

With Microsoft Office Communications Server 2007 R2 Web Service Provider, administrators can implement basic instant messaging and presence functionality for Microsoft Office Outlook®-Live users.

Download it here.

Categories: Unified Communications Tags:

Communicator 2007 – cannot synchronize address book

April 1st, 2009 No comments

When this error is seen in the Communicator 2007 and Communicator 2007 R2 client, it can be a number of issues.

Here’s a few steps to check:

  1. Validate the password for the service account (RTCComponentService) used on the AppPool “LSGroupExpAppPool”
  2. Make sure the AppPool is started “LSGroupExpAppPool”
  3. Make sure the default website running the /Abs – application has a SSL certificate applied and that it’s responding on port 443 (https)
  4. Shut down and restart the Communicator 2007 (R2) client

These steps helped for me, when seeing the failure “Cannot synchronize address book” on all Communicator 2007 clients.

Address Book regeneration:

In case the Address Book needs to be regenerated, it can be done using these steps:

From the OCS folder: “C:\Program Files\Microsoft Office Communications Server 2007\Server\Core”:

  1. Run: “abserver –regenUR” and wait 5 min.
  2. Run: “abserver –SyncNow” and wait 5 min.

A few references:

Communicator 2007 and Outlook 2007 integration error

April 1st, 2009 1 comment

Error seen in Communicator 2007 R2:

There was a problem connecting to Microsoft office outlook. Your profile is not configured correctly. contact your system administrator with this information.

It can be solved in several ways:

  1. Make sure the default Outlook profile matches the “profile” = e-mail used for signing into OCS, equal your sip address:
    Go to: HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows Messaging Subsystem\Profiles
    Change DefaulProfile to your default profile name (Control Panel > Mail > Profiles)  

    Or go to: Control Panel > Mail > Profiles, select “prompt for a profile to be used”, restart outlook, select the profile, and click options, and select default profile. Restart outlook.

Another solution can be to run fixmapi.exe on the computer having this problem, If the default profile is already set correctly.

This solved the problem for me on a client running Vista and Outlook 2007 and no Exchange Admin tools.

Further reference:

OCS – how to retrieve user information using SQL queries

November 14th, 2008 3 comments

There might be a situation where you would like an overview of the SIP URIs of the active users connected to one of the OCS servers in a pool, their last logon and what client version they are using.

All these kind of information can be retrieved using SQL queries in the SQL Management Tools, connect to the RTC database on the backend server and run the selected queries below.

Get a list of active users on the OCS Server (pool):

Select a.UserAtHost “Active-Users” from rtc.dbo.Resource

a,rtcdyn.dbo.DeliveryContext b where a.ResourceId=b.SubscriberId and b.FrontEndId=1

The FrontEndId is the ID of the OCS Frontend server where the users are connected to. In an environment with only one OCS, the value is 1.

The ID can be obtained from the FrontEnd table of the rtcdyn database.

Further more if you need the above information along with information about which Client App (communicator version) they use, the following query command will give you that result:

select count(*) as Occurrences, cast(e.ClientApp as varchar(128)) as 

ClientApp from rtcdyn.dbo.Endpoint as e group by cast(e.ClientApp as 

varchar(128)) order by cast(e.ClientApp as varchar(128)) select r.UserAtHost, 

cast(e.ClientApp as varchar(128)) as ClientApp from rtcdyn.dbo.Endpoint as e 

inner join rtc.dbo.Resource as r on r.ResourceId = e.OwnerId

Need to known when your enabled OCS users last logged in, run the following query below:

select res.UserAtHost as “SIP Address”, hud.LastNewRegisterTime as “Last Logon” from rtcdyn.dbo.HomedUserDynamic hud join
(Select ResourceId, UserAtHost from rtc.dbo.Resource
group by ResourceId, UserAtHost)
res
on hud.OwnerId=res.ResourceId
order by “Last Logon”

All SQL queries work for both OCS Standard and Enteprise Edition.

OCS – Communicator videos

October 24th, 2008 No comments

Microsoft has put online some small, but very informative videos, about how to use the Communicator client. Great for new users to the Communicator.

Subjects are: