OCS 2007 R2 Now VS. OCS 2010 Later: What's the Plan?
Filed under: Conferencing, OCS 2010, Unified Communications, Voice over IP
(Sorry about the delay on this post. WordPress didn't want to cooperate last week, and I didn't have the time to fight with it.)
A few days ago we were asked a question. This question, I felt, deserved its own post. Because it brings up a very important OCS version point.
“Should we upgrade now, or wait for OCS 2010?”
In this case “upgrade” referred to the fact that this client had no present OCS system. The choice was between putting in a brand new OCS 2007 R2 system, or waiting a few months for the upcoming release of OCS 2010.
What Do You Need from OCS Now? Later?
This question comes down to two concerns: present need and future planning. What communications tools do you need? And how far in the future do you want to (or typically) plan?
These questions can help determine which is best. Upgrading to OCS 2007 R2 now, or waiting until the end of this year when OCS 2010 arrives. I'll address both while comparing the advantages of each approach below.
A couple things to keep in mind while we consider:
- Voice is a big upgrade issue.
- So is cost.
- Planning time is always dependent on how big an organization is.
Advantages in Upgrading Now
- You'll get a jump on preparation. It takes time to survey and prepare.
- You'll need an inventory of the user pool, and what they want.
- You'll need to decide which services you want to use (VoIP or no, which servers are needed).
- You'll need to decide what architecture to use (all local, all hosted, virtual?).
- And you'll need to add necessary server hardware. (Or go with a hosted option, of course.)
Deciding to start an OCS 2007 R2 implementation plan now gives you an option. Do we spread it out over a couple months? Or take a week and get it all done? The choice is yours.
- “OCS 2007 now, OCS 2010 later” is NOT mandatory. You don't have to upgrade again (at least not right away) if your new OCS 2007 R2 system works for you.
- An OCS 2007 R2 system removes the need for (and cost of) third-party conferencing solutions.
Advantages in Waiting for OCS 2010
- It's intended to replace the PBX. OCS 2007 R2 can replace a PBX, but it requires some add-ons (ex., media gateway). OCS 2010 however is intended as a full PBX replacement.
- Fewer servers needed. As I pointed out the other day, OCS 2010 will run on fewer physical servers than 2007 R2.
- Even more prep time. If you have a larger organization, it will (obviously) take longer to prepare for a major communications change than it would a small business. Especially since you'll be moving people over to OCS, not just technology. Fortunately, you still have plenty of time to ease in.
Based on all this and the two questions I mentioned earlier, this is what I recommend:
If you intend to move to VoIP, plan for transitioning to OCS 2010.
If you're already using VoIP or don't want to use it, implement OCS 2007 R2 now.
What's your plan? Which OCS version are you moving toward?
A Peek at Next Year's Model - More Features of Communications Server 14
Filed under: OCS 2007 R2, OCS 2010, Unified Communications
I'm back! I'd talk about my trip, but it's not OCS-related.
However, we did get a few responses to last week's query. The majority were questions about Communications Server “14.”
And as luck would have it, we have something to discuss along those lines!
Brent Kelly of the “No Jitter” blog posted a VERY thorough overview of Communications Server 14 on Sunday. (With pictures!)
He obviously gleaned much from the TechEd conference. The six-page article is a comprehensive discussion of CS14's capabilities, changes from OCS 2007, and so on. Read it for yourself here (but after you finish this post!):
Under the Hood of Microsoft Communications Server 14 - NoJitter.com
Really, I can't do a better job. All I want to do today is give a thumbs-up to Brent for his good work. And highlight a few of the points from his article here.
Four More CS 14 Features to Note
- The “physical server requirement” that hampered OCS 2007 has been removed. CS14 allows you to host many of its servers on one physical server. Instead of four.
- (This is a separate consideration from the virtualization I mentioned last time. Virtualization is not necessary in this case - but you can still use it.)
- CS 14 will support E911.
- You'll be able to control the whole CS 14 from its new Silverlight-based Control Panel Interface. Configuration, routing, and policy rules are all accessible from there.
- The “contact card” that shows a person's information has been expanded. It also comes up when you hover over the contact's name, instead of hitting Alt+Enter as in OCS 2007.
Finally, just something for OCS fans to remember. An official name for the next version of OCS has not been officially announced yet. So far, all the names by which this version's going are:
- OCS 2010
- Communications Server 2010
- Communications Server “14″
- “CS 14″
When the official name is announced, you'll see it right here!
Rename and a Revamp - New Features of Communications Server 14
Filed under: Conferencing, OCS 2007 R2, OCS 2010, Unified Communications, Voice over IP
Last week at TechEd, Microsoft announced the new features of Communications Server 14. Frankly, I”m not sure why the new version is named “14.” But that's not what I wanted to write about anyway.
What I'm blogging about today is a few of the features announced. More specifically, how those features translate into new benefits for small business OCS users.
Many of 14's updates focus on simplification: Easier administration, more unified front-end interface (Unified Communication - get it?). The main small-business advantage comes from a more comprehensive client application. All communication channels ready and waiting for you.
1. The Rise of Communicator 14
Every service goes through the Communicator 14 client. Live Meeting was originally separate from the Office Communicator 2007 client. (They were developed separately at first.) Communicator 14 has it built in. All conferencing capabilities, in fact…along with IM, voice calls, Presence, even a visual Voicemail menu.
2. More Roles Virtually Capable
In 14 there's support for virtualizing almost all OCS server roles (AV Conferencing, Archiving, Edge Mediation, etc.). Putting in a new Communications Server 14 setup becomes more appealing if there are fewer physical servers needed than for OCS.
3. Web Client Following You Around
14 includes a new Silverlight-based web client version of Communicator. Very handy if you have people who live on netbooks or smartphones. I've played with Silverlight a little too; this client is almost guaranteed to be much faster than CWA.
4. Avoid the Media (Server) and Still Call the Office
There's a new media bypass, reducing the need for a mediation server. It allows a front-end server to go “direct SIP,” meaning you can call into (supported) PBX phone systems without mediation. In other words, simpler setup, and you can still call non-VoIP phones.
5. Alert! Call #2467 is Failing!
I really like this one. There's a new Monitoring Pack in Communications Server 14. If calls are failing or their quality drops, alerts will show in the Monitoring Pack. You can even boost the audio quality if it’’s degrading!
6. SQL Backend Moved to Express Lane
The Director server role will include a SQL Express database in 14. So there's no more need for a separate SQL backend. That means even fewer servers running.
There's even more features than these too. A very thorough overview is on the “Inside OCS” blog.
A smaller, more streamlined communications system. Appealing to small business cost and space concerns, wouldn't you say?
What are you looking forward to in Communications Server 14? Drop us a comment and let's talk.
