This posting is provided "AS IS" with no warranties, and confers no rights.The opinions expressed herein are my own personal opinions and do not represent my employer's view in anyway. Please use the Microsoft Forums for support requests.
Microsoft announced this week the next version of Office Communications Server 2007, codename Wave 13, but that will be officially named as Office Communications Server 2007 Release 2 (R2).
Key new features of Office Communications Server 2007 R2 include the following:
Enhanced Voice and Mobility
New Developer Tools for Business Applications
Other Cool Features
Office Communications Server 2007 R2 will launch in a worldwide online event Feb. 3, 2009. People can register to participate in the launch at http://www.microsoft.com/communicationsserver.
Q: What is Microsoft announcing today? A: We are unveiling OCS 2007 R2, an update to the award-winning OCS 2007. OCS 2007 R2 will deliver a variety of new capabilities including:
Q: What is Microsoft Office Communications Server 2007 R2? A: Office Communications Server 2007 R2 delivers streamlined communications for users so they can find and communicate with the right person, right now, from the applications they use most. Without expensive infrastructure and network upgrades, you can deliver streamlined communications, including software-powered VoIP (voice over IP), conferencing, and enterprise instant messaging, while maintaining operational control.
Q: When will Office Communications Server R2 be available? A: OCS R2 will launch via a worldwide online event on Feb 3, 2009. People can register to participate in the launch at http://www.microsoft.com/communicationsserver/.
Q: Is OCS 2007 R2 available in public beta for customers and partners? A: Due to the compressed development cycle, we don’t have a public beta program for this release. The product will be broadly available for download in February.
Q: Why is this announcement significant? A: This announcement is significant for two reasons:
In my job, I do a lot of UC pilots. Before heading to a potential customer, I usually write a small technical document with the hardware and software requirements.
Over time, I noticed that these pilots are very similar, that's why I decided to write this post. My objective is to list a small Bill of Materials for a UC pilot capable of delivering the following features:
The image below depicts the reference architecture for a pilot like this:
Finally, here's a table with the recommended Bill of Materials:
The architecture figure shows a single Edge server, because, for simplicity, we use the consolidated edge topology: the Access Edge Server, Web Conferencing Edge Server, and A/V Edge Server are collocated on a single computer.
Since the Edge server is placed on a perimeter network (or DMZ), the firewalls must be configured in order to allow the OCS network traffic. All the required ports are depicted on the next picture (the different Edge roles are shown as separate machines for better understanding, but only one server will be used).
Although Exchange Server 2007 is part of the Microsoft Unified Communications portfolio, it isn't listed here. I intentionally left it out, because usually the Exchange infrastructure is already in place. And after all don't forget, this is just for reference, there isn't such a thing as 2 equal customers with equal business needs.
What are the next steps? The immediate one is to gather the necessary technical information. I strongly recommend the following documents:
This pretty much covers the requirements for a successful UC pilot. If you already have all this stuff in place, hey, give me a call and I'll pay you a visit!