This document provides a technical overview of the architecture and new features of Office Communications Server 2007 and is divided into two main sections: "New Features" and "Architecture".

"New Features" discusses the new features of Office Communications Server 2007, including the following:

  • On-premise Web conferencing
  • Group IM
  • Audio and video
  • Enterprise Voice
  • Microsoft RoundTable™ communications and archival system
  • Enhanced presence
  • Federation enhancements
  • Client applications
  • Simplified deployment and management

"Architecture" discusses:

  • Enterprise Pool configurations
  • Front End Servers
  • Conferencing components
  • Perimeter network topology
  • Conference protocols
  • Call flows among conference components
  • VoIP components
  • VoIP configuration
  • VoIP call flow
  • Conference data storage
  • Perimeter network configuration
  • Protocols

Click here to download…

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

UPDATE (5/11/2012): This fix has been tested against Windows 7, Windows 8 CP and Windows Server 8 (2012).


You’ve installed VMWare Workstation on Vista or Windows 7 and the two VMNet adapters display as unidentified by the host OS.  This causes your firewall profile to switch to the Public setting and lock down your computer even on a trusted network.  Manually switching the virtual NICs to Private solves the problem only until the next reboot.


The root cause has to do with the way Vista and Windows 7 automatically identifies network types.  The information can be found on MSDN:

Windows Vista automatically identifies and monitors the networks to which a computer connects. If the NDIS_DEVICE_TYPE_ENDPOINT flag is set, the device is an endpoint device and is not a connection to a true external network. Consequently, Windows ignores the endpoint device when Windows identifies networks. The Network Awareness APIs indicate that the device does not connect the computer to a network. For end users in this situation, the Network and Sharing Center and the network icon in the notification area do not show the NDIS endpoint device as connected. However, the connection is shown in the Network Connections Folder. Also, if NDIS_DEVICE_TYPE_ENDPOINT is set, the Windows Firewall ignores the connection when Windows Firewall enforces public, private, or domain policies.


NOTE: This solution will also work on Server 2008 when you have multiple NICs installed (aka: cluster or backup network).

Option 1

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:

  • 322756 How to back up and restore the registry in Windows
  1. Click Start, click Run, type regedit, and then click OK.
  2. Click the follwoing subkey:HKLM\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}
  3. Browse through the 00xx subkeys until you find the REG_SZ VMNet subkey with a value of either “\DosDevices\VMnet8” or “\DosDevices\VMnet1” (default values)
  4. On the Edit menu, point to New, and then click DWORD Value.
  5. Type *NdisDeviceType, and then press Enter.
  6. On the Edit menu, click Modify.
  7. Type 1, and then click OK.
  8. Exit Registry Editor.
  9. Disable & re-enable the VMWare NICs
  10. DoneNote: In case simply disabling and re-enabling the virtual NICs doesn’t fix the problem immediately reboot your computer.

Option 2

If all this seems a bit confusing or you are unfamiliar with modifying your registry then you can download a powershell script that will automagically do the work for you.

Option 3

If you only use VMWare Workstation guests in a Bridged network then you can simply disable the NICs which will solve the problem all together.

This information was originally posted here…

1 Star2 Stars3 Stars4 Stars5 Stars (7 votes, average: 5.00 out of 5)

This update fixes the following issues:

  • 958659 When you use telephony mode=4, you can only manually set the URI information in Communicator 2007
  • 957793 A Communicator 2007 client is unusually slow at startup
  • 956734 The presence status of Communicator 2007 changes to "Away" for all Terminal Server users when one user locks the desktop on a Windows Server 2008-based computer
1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)

OCS R2 Attendant Video

October 17, 2008

in Microsoft, OCS

Spotted by Aaron (human computer) and worth a watch, this video give a short demonstration on the new Attendant feature of OCS R2 due out early 2009.

I’ve recently been spending a lot of time with the Office Communications Server (OCS) team, and they’ve shown off some of the new features coming in their next release, OCS R2.
In this interview, I met Jamie Stark, a Technical Product Manager that looks after VoIP in OCS. In this interview, we talked a little about integrating OCS into existing telecoms, and Jamie walked me through the new Attendant Console in OCS R2. If you’ve got a busy receptionist that spends a lot of time taking and routing calls, the Attendant Console was built with that job in mind.

Click here to watch the video…

Just in case you have read about OCS R2 just click here…

1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)