Enabling DSCP Marking on MS Windows clients for MOC

16 01 2010

To enable QoS for Communicator clients

1. Log on to the desktop, laptop, or Attendant client as a member of the
Administrator group or an account with equivalent user rights.
2. Open the Registry Editor.
3. Create the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RTC\Transport
“QoSEnabled”=dword:00000001
4. Restart the Office Communicator 2007 R2 service.
5. Repeat the preceding steps on each desktop, laptop, and attendant
client.
After the reboot, RTP Media will be marked with the following default values
1) Audio calls will be marked with DSCP 40
2) Video will be marked with DSCP 24

Note:
This procedure only enables DSCP on the client. After completing this procedure, ensure that the QoS Packet Scheduler is installed and that Group Policy settings are appropriately configured on each computer, and then restart the services.
___________________________________________________________________________________________________________

Installing the QoS Packet Scheduler on Computers

The QoS Packet Scheduler needs to be active and configured properly in order for Office Communications Server 2007 R2 servers and clients in order

to make the marking active. For details about the QoS Packet Scheduler service, see Voice Quality of Service (QoS) in the Technical Reference for Office Communications Server 2007 R2 in the Reference documentation.
By default, the QoS Packet Scheduler is installed on computers running Windows XP, Windows Vista, and Windows 2008.
By default, the QoS Packet Scheduler is not installed on Windows Server 2003. Use the following procedures to determine whether the QoS Packet Scheduler is installed and, if not, install it.
To install the QoS Packet Scheduler on Windows XP or Windows Server 2003
1. Log on to the computer as a member of the Administrators
group or an account with equivalent user rights.
2. Click Start, and then click Control Panel.
3. Click Network Connections.
4. Right-click the network interface on which you want to
enable the QoS Packet Scheduler, and then click Properties.
5. Click Install.
6. In Select Network Component Type, click Service.
7. Click Add.
8. In Select Network Service, click QoS Packet Scheduler, and
then click OK.
To install the QoS Packet Scheduler on Windows Vista or Windows Server 2008
1. Log on to the computer as a member of the Administrator
group or an account with equivalent user rights.
2. Click Start, and then click Control Panel.
3. Click Network and Sharing Center.
4. Right-click the network interface on which you want to
enable the QoS Packet Scheduler, and then click Properties.
5. Click Install.
6. In Select Network Feature, click Service.
7. Click Add.
8. In Select Network Service, click QoS Packet Scheduler, and
then click OK.

___________________________________________________________________________________________________________

Use the following procedure on each client and server to ensure that the Group Policy settings for the two service types are set correctly.
To verify service type settings on a computer
1. Log on to the computer as a member of the Administrators group or an
account with equivalent user rights.
2. Click Start, and then click Run.
3. In the Open box, type gpedit.msc.
4. In the Group Policy Object Editor dialog box, expand Computer
Configuration, expand Administrative Template, expand Network, expand
QoS Packet Scheduler, and then click DSCP value of conforming packets
.
5. In DSCP value of conforming packets, verify that Guaranteed service
type and Controlled load service each have one of the following
settings:
Not configured.
Enabled with a nonzero value (default -> 40=audio, 24=video).
To see the value, right-click the setting, and then click
Properties.
Disabled.





Office Communicator Phone Edition (2007 R2)

16 01 2010

Direct download here

Issues that this hotfix package fixes
(KB not Available yet)

Version: 6907.82
Knowledge Base (KB) Articles: KB978737
Date Published: 1/7/2010





Microsoft Office Communications Server 2007 R2 Hotfix KB 968802

9 01 2010

Direct download here

Issues that this update package fixes.

I recommend to use the tool ServerUpdateInstaller.exe for installing the patches on the dedicated OCS servers.

The download for ServerUpdateInstaller.exe is provided in the hotfix listing. You can use this tool to automatically install the latest patches for each component. Run ServerUpdateInstaller.exe with elevated permissions. I would also recommend creating a folder and put ServerUpdateInstaller.exe in there, as it extracts each of the individual patches to the same place as the .exe. The GUI then lists what updates are and aren’t installed. Click on the install updates button to install the latest updates. KB968802 (http://support.microsoft.com/kb/968802) has details on how to run via command line.





Microsoft Office Communicator 2007 R2 Hotfix KB 976135

9 01 2010




Microsoft Office Communications Server 2007 R2 Hotfix KB 975611

30 10 2009




Office Communicator Phone Edition (2007 R2) 6907.55 KB977065

28 10 2009




Microsoft Office Communicator 2007 R2 Hotfix KB 972884

28 10 2009




KB974571 Crypto-API Update may break Office Communications Server 2007 R2 installations

14 10 2009

Don’t install KB974571 Crypto-API Update on Office Communications Server 2007 R2 installations.

Note: If you use the Evaluation Communicator Client Version, the Client installation will break too. So do not install the Update on the Client as well.

After installing this Crypto-API Upadte Event log Message that OCS 2007 R2’s evaluation license has expired.
Now, this seemed very strange as we’ve installed from volume license media.

In Details:

Event source: OCS Server
Event id: 12290
Event text: The evaluation period for Microsoft Office Communications Server 2007 R2 has expired. Please upgrade from the evaluation version to the full released version of the product.

After some investigation it pointed us to the Crypto-API Update KB974571.
We removed the Update and after rebooting the machine, OCS 2007 R2 was up and running again.

Uninstalling the patch is the only way to currently fix this issue!
The issue is currently being escalated to Microsoft, but until a fix can be found, delaying the install of KB974571 is recommended.

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





Vodafone Germany and HTC Roll Out Windows Mobile 6.5 for Touch Diamond2

4 10 2009

Available now before the official Windows Mobile 6.5 launch date, HTC and Vodafone Germany has put up a ROM upgrade for HTC Touch Diamond2 today. The software upgrade will upgrade your HTC Touch Diamond 2 with Windows Mobile 6.5, plus an updated TouchFLO 3D with weather info integrated with home screen’s clock. Click HERE for the download link if you own a Vodafone Germany’s Diamond2





New PIC Licensing and released XMPP Gateway

1 10 2009

Excited news from the OCSTEAM!

Copy of the OCSTEAM Blog:

We are excited to announce changes to the Office Communications Server Public IM Connectivity (PIC) license that provides instant messaging and presence federation to the Windows Live, AOL and Yahoo! public IM networks. Starting October 1, 2009, the following licensing changes will be made:

1.A PIC License will no longer be required for federation with American Online (AOL). Customers qualify for federation with AOL if they have Office Communications Server 2007 R2 Standard CAL or active Software Assurance on their current LCS/OCS license.
2.Customers who want Yahoo! federation will continue to purchase PIC licenses. The price of PIC will be reduced by 50%, effective October 1, 2009, to reflect this change.
We are also excited to announce the release of the OCS 2007 R2 XMPP Gateway (http://go.microsoft.com/fwlink/?LinkID=141529). The Gateway provides Presence and two-party IM interoperability with the XMPP based systems of Jabber and Google Talk.

1.The Gateway interoperability has been tested against Jabber CXP Server version 5.4 and the current version of Google Talk. The OCS 2007 R2 XMPP Gateway is supported by Microsoft Support
2.This Gateway is licensed as Additional Software to OCS 2007 R2, meaning that there is no additional license cost associated with deploying the Gateway for OCS 2007 R2 licenses.
For more details about these two great announcements you can read the Microsoft Press Pass article with Eric Swift, General Manager of the Unified Communications Group at http://www.microsoft.com/presspass/features/2009/oct09/10-01ucinterop.mspx or in this Channel9 interview with the responsible Product Managers Ashima Singhal and Albert Kooiman http://channel9.msdn.com/posts/jccim/Instant-Messaging-Interoperability-extended-through-XMPP-Jabber/

Recap of June Announcement: In June 2009, we announced a similar change for Windows Live and renamed the OCS PIC license.

1.The LCS PIC license was renamed to Office Communications Server Public IM Connectivity.
2.A PIC License is no longer required for federation with Windows Live. Customers qualify for federation with Windows Live if they have Office Communications Server 2007 R2 Standard CAL or active SA on their current LCS/OCS license.
With these changes, customers qualify for IM/P federation with Windows Live and AOL with the Office Communications Server 2007 R2 Standard CAL or OCS 2007/LCS 2005 SP1 Standard CAL with Software Assurance. http://www.microsoft.com/communicationsserver/en/us/public-im-connectivity.aspx

We are thrilled about growing the network of users for Office Communications Server.