When we launched OCS R2 in Feb. the licensing for the product changed. Let’s talk about the client license first. OCS Standard CAL now includes Group Chat. OCS Enterprise CAL now includes desktop sharing, dial-in conferencing, Team Call, Delegation, Response Group and Single Number Reach.
We are changing the requirement for CAL as stated in the PUR.
You do not need CALs for unauthenticated access to your instances of the server software. Authenticated (direct or indirect) through Active Directory access requires CALs.
–CAL required for internal users. CAL not required for external users.
–External Connectors are largely unnecessary
As far as Server licenses are concerned we’ve made a few changes here as well. OCS Standard Server can be used for small pilots or small environments. When we use Enterprise Server we are looking for scale and high availability. In OCS R2 we now have 12 Server Roles. To reduce the complexity of deployment of these servers we only require licensing the Front-End Servers and the Edge Server Roles. So if you have a single Pool with two FE servers and 2 Edge Servers you would need 4 licenses. Regardless if you had other server roles deployed. The following Servers are considered additional software and don’t require licenses as long as the FE and Edge are licensed. They are:
Hopefully this reduces confusion in licensing of OCS and we can work on deployment. :)
I’ve spent the last few days working on a Mac and setting up Entourage with Exchange Web Services. This is still in beta but I am very impressed with how clean the experience is esp. considering the old method was WebDAV.
After downloading the beta bits I installed on a macbook with Mac OS X 10.5.6. I was determined to setup two identities in Entourage one with my Exchange account which is running the next version of Exchange, and the other with Exchange Online. This allowed me to look at Entourage connectivity to Exchange 14 and Exchange 2007.
Working with Exchange 14 and Entourage Beta code was very interesting and provided me with some false reads as I’m sure I was making changes and being in a dogfood environment corp was making changes. Exchange Online also was unique as I went to connect to autodiscovery services. I explain later.
I found the setup relatively easy. Typical next, next…
After starting Entourage I needed to configure an identity to work with. In this case I used my Exchange 14 account.
Here I put in my domain and account ID (alias) and password. Saved to Mac keychain.
I then clicked on verify my settings and the autodiscovery web service did it’s magic. I’m now configured to use Exchange Web Services for Entourage connectivity.
I found the client very easy to use and the response to server request very quick. I’m still reviewing but the functionality is great.
Now I also tried Exchange Online. The configuration for the identity was a little bit different. Instead of the FQDN for mail I needed to use the following format for the account ID:
This resolved to the autodiscover parameters for my Exchange server.
This is a common question I get since your PBX may not be in the same place as your mailbox servers.
Where do I put the Exchange UM components if I have a PBX in one location and an Exchange mailbox in another?
The typical rule of thumb to follow is:
The reason to keep Exchange UM server close to the Exchange mailbox server is the UM role talks to the mailbox server using RPC and over long distances the UM role does not behave well resulting in a poor end user experience.
If SIP Gateway/PBX is in one location and Exchange UM in another what bandwidth is needed?
The typical rule of thumb here is:
At Voicecon we announced that Polycom has licensed the ability to distribute Office Roundtable starting April 13. The device has been re-labeled as the CX5000. More info on the device can be found here. Microsoft will continue to support all Roundtables previously sold and Polycom will have front-line support for any devices sold after April 13.