Office Communications Server 2007 R2 « Microsoft UC (Unified Communcation)

Enable Users for Lync Server 2010

April 11th, 2011 Posted in Lync Server 2010, Office Communications Server 2007 R2

Apr, 11 2011

No Comments »

This post will help you for enabling users for Lync Server 2010 from CommandShell,

and it will be series of post where we will find different cmdlets used by Lync Management Shell

for Administration.

Enables one or more users for Microsoft Lync Server 2010.

Because you need to enable Users for logging in to Lync 2010,

and Microsoft is pushing PowerShell for administration,

that’s why we are going to enable our users from PowerShell not from Lync Control Panel.

Enable-CsUser -Identity “Shafaquat Ali. Awan” -RegistrarPool “Lync.WhatDoUC.net” -SipAddressType SamAccountName -SipDomain WhatDoUC.net

Enable-CsUser is the cmdlet which enables the user account with the display name Shafaquat Ali. Awan.

In this example, the user is assigned to the Registrar pool lync.WhatDoUC.net,

and Lync Server auto-generates the SIP address by using the user’s SamAccountName (shafaquat.ali)

followed by the SIP domain WhatDoUC.net.

Here we are using this command with some different scenario.

Enable-CsUser -Identity "Shafaquat Ali. Awan" -RegistrarPool "Lync.WhatDoUC.net"
-SipAddress "sip:shafaquat.ali@WhaoDoUC.net"

If you want to enable more than one users with single cmdlet than you need to use this command in below method.

Get-CsAdUser -LDAPFilter "department=Sales" | Enable-CsUser -RegistrarPool "Lync.WhatDoUC.net"
-SipAddressType SamAccountName  -SipDomain WhatDoUC.net

I hope this will be informative for you and I would like to Thank you for viewing.

Lync Server, Lync Server 2010, Shafaquat Ali, SIP

Lync 2010 v/s OCS 2007

October 13th, 2010 Posted in Lync Server 2010, Office Communications Server 2007 R2

Oct, 13 2010

21 Comments »

What is different in Lync Server 2010

OCS 2007 / 2007 R2	Lync Server 2010
Virtualization not supported accepts some roles.	Every role can be either virtual or physical.
A/V conferencing service cannot work separate.	A/V conferencing service can run in a standalone server role which we can call A/V Conferencing Server.
No specific limits for A/V conferencing pool.	If site has more than 10,000 users, we recommend that you deploy a separate A/V Conferencing pool.
No Survivable Branch Appliance.	Survivable Branch Appliance, which is a new device introduced in Lync Server 2010.
Mediation role cannot be collocated with FE.	Collocation of mediation with FE is recommended if you are not using SIP trunking or Direct SIP.
No Topology Builder.	Lync 2010 giving you the opportunity to create your own topology for deployment.
No Central Management Store kind of thing.	In Microsoft Lync Server 2010, configuration data about servers and services is moved to the Central Management store. Read-only copies of the data are replicated to all servers in the topology, including Edge Servers and survivable branch appliances
No Management Shell accept LCSCMD command.	The Lync Server 2010 Management Shell is a new method of administration and management.
No Role base access control.	Lync introduces role-based access control (RBAC). Lync Server 2010 includes 11 predefined roles that cover many common administrative tasks, also you can create custom roles.
MMC for Administration.	Administration console is no longer using MMC, Lync Server Control Panel replaces the MMC administrative interfaces
No load balancing for SIP traffic.	The Lync Server 2010 introduces DNS load balancing for SIP and media traffic (you will still need hardware LB for other traffic such as HTTP however this is the easiest part in configuring a HW load balancer)
Edge Server is separate and in DMZ.	You manage Edge Servers from the internal network. All configuration data for servers and services resides in the Central Management database, which you can manage by using internal administrative tools.
No Support for hosted Exchange UM.	Lync Server 2010 introduces support for integration with hosted Exchange UM.
No Support for Enhanced 9-1-1.	Lync supports Enhanced 9-1-1 (E9-1-1) as part of your Enterprise Voice deployment.
1 Mediation means 1 Gateway.	New for the Mediation Server in Microsoft Lync Server 2010 is the ability for a single Mediation Server to route outbound calls through multiple gateways.
No separate pool for Mediation.	Lync Server 2010 has the ability for a Mediation Server to be deployed as a pool; this pool can be collocated with the Front End pool, or can be a standalone pool.
MOC cannot be updated through WSUS.	Lync client can be updated through WSUS.
No support for Analog devices.	Lync Server 2010 provides support for analog devices. Specifically, the supported analog devices are analog audio phone and analog fax machines. Now you can configure the analog gateways and devices in your organization to use Lync Server 2010.

I tried to collect all the information but if there is something missing I will try to update it as I will get any more information.

I hope this will informative for you and I would like to Thank you for viewing.

Lync Server, Lync Server 2010, OCS, SIP

Communicator Error “404 Bad request”

September 6th, 2010 Posted in Office Communications Server 2007 R2

Sep, 06 2010

7 Comments »

I was getting issues, where a single user was not able to receive chat (messages) in communicator and it worked if he was initiating a chat session.

Scenario:

Client is online in communicator there seems no problems.
When somebody tries to initiate a chat session, it fails.
When the client initiates session from his MOC, it works then.

How to resolve the ‘issue’:

I enabled logging in communicator got the trace with Snooper.exe. It showed me “404 Bad request”.

I took an LDP dump of the client with a working user and found that his setting was different in an entry of IP PHONE.

So, I opened ADUC > Telephones tab > IP Phone > Other > “Entry inside others” was not in place.

Snooper.exe will help you to analyze the SIP and C3P protocol logs, including those generated by OCSLogger.exe. Also want to let you know that it comes with the “Office Communications Server 2007 Resource Kit Tools” which can be found here.

The Resource Kit also includes documentation for using the tool. It’s not a big deal to find it.

I hope this will informative for you and I would like to Thank you for viewing.

ADUC, IP, Phone Entry, Resource Kit

OCS 2007 R2 CU6 has been pulled back

September 6th, 2010 Posted in Office Communications Server 2007 R2

Sep, 06 2010

No Comments »

As Microsoft said:

Due to recent discoveries in the July 2010 Cumulative Update for Office Communications Server 2007 R2, it is necessary to remove this update from the download site until it can be patched. The primary concern is an issue with the Response Group Service. When the cumulative update is applied, changes in agents and agent groups are not applied until after the Response Group Service is restarted. This, of course, is not acceptable in the quality of our products.

Reference can be found on (http://www.nexthop.info/)

I hope this will informative for you and I would like to Thank you for viewing.

Cumulative Update Office Communications Server, OCS, Response Group Service

OCS 2007 R2 Services not starting

August 16th, 2010 Posted in Office Communications Server 2007 R2

Aug, 16 2010

No Comments »

Today I came office and got call from some client that his OCS Server is not working and all the users are not able to connect to server.

I started work on it and found something interesting so I thought that I should share with all that what it was.

I got a message when I was trying to start services

Also getting error in event viewer which is below

I simply open Active Directory Users & Computers and RTCComponentService Account and checked the check box of Password never expire and every thing was green.

I hope this will informative for you and I would like to Thank you for viewing.

OCS 2007 R2 CU6 Errors

August 12th, 2010 Posted in Office Communications Server 2007 R2

Aug, 12 2010

1 Comment »

I was digging out with CU 6 of OCS 2007 R2 and was getting some problems for updating this so I searched on net and got some steps which I M sharing with you as well maybe this could help you.
One cause could be the web caches that Microsoft uses publish the updated bits are lagging behind. due to the updates always having the same filename from Cumulative Update to Cumulative Update, and it is really hard to determine what version you have downloaded without looking at the file dates stored in each individual update.

So found that if the front-end is updated without the proper back-end update, the front-end will complain about version mismatches in the SQL stored procedures.

Install the OCS2009-DBUpgrade.msi before the other CU6 updates.

I found some good stuff on this blog which is at http://www.confusedamused.com/

I found a little about the .NET 4.0 issue here a few days ago but now that .NET 4.0 is on Windows/Microsoft Update as a recommended update, it is hitting more users during OCS installation.

If you install .NET 4.0 Framework before installing any OCS server role, the OCS setup program will complain that .NET 3.5x is not installed, even if you have .NET 3.5x installed (x being equal to 0 or 1, meaning .NET 3.50 or .NET 3.51).

Solution? Uninstall .NET 4.0 Framework, install OCS server roles, and then install .NET 4.0 if necessary. The OCS product team is working with the Windows product team to get a hotfix/update out for this.

I hope this will informative for you and I would like to thank you for viewing.

OCS 2007 R2 CU6 Downloads

August 12th, 2010 Posted in Office Communications Server 2007 R2

Aug, 12 2010

4 Comments »

New updates for OCS 2007 R2.

OCS 2007 R2 Server:
Office Communications Server 2007 R2 – KB 968802 – Download
Office Communications Server 2007 R2 Back-end database update – KB 2032834 – Download

OCS 2007 R2 Client:
Office Communicator 2007 R2 – KB 2028888 – Download
Office Communicator Phone Edition 2007 R2 - KB 2267962 – Download

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

Installing OCS 2007 R2 on Windows Server 2008 R2

August 7th, 2010 Posted in Office Communications Server 2007 R2

Aug, 07 2010

2 Comments »

Since last 20 days I was sucked by OCS 2007 R2 Deployment on Windows Server 2008 R2 but all in vain. But Thanks to All Mighty ALLAH that I have did it completely and also I want to share that what is the main problem in this deployment.

First of all I started Deployment step by step everything was ok .

01. I started MOC and get login.
02. I started IM.
03. I started Voice & Video.
04. I started Desktop Sharing.

And done, nothing wrong so what’s the problem than?

When I started LiveMeeting I got error as below.

Now my work start and I cannot really tell you that how hard it was for me at that time but finally I got the solution and everything is up and running now but how?

I started with the help of these articles which are really very nice but I did not get done with these articles even I got a lot of help you can check them as well.

Installing OCS 2007 R2 Prerequisites on Windows Server 2008 R2

Office Communications Server 2007 R2

Supportability is available for Office Communications Server 2007 R2

So I read them carefully and I did all the things step by step but I got the same error again & again than I started brainstorming and figure out the meaning of cumulative update (it means the bunch of updates not complete updates till date) and I started updating my server with all the cumulative updates which I cannot find on internet because when I go through the link they get me on July 2010 update page which is the latest update yet. I got some updates from my old data which was released in Feb 2010 and I installed them on my server and then updated them to July update which you can find here