Last week Microsoft released a new version of the Office Communications Server 2007 R2 Workload Architecture poster. You can download it here (free, MS login required):
OCS 2007 R2 Workload Architecture Poster
The timing on this might seem odd. After all, we're charging full-on toward Lync Server 2010's release right?
Even so, this is a handy reference tool to have. For OCS 2007 and for Lync 2010.
The reason I say that is because it divides architecture up into four distinct functions: IM and Presence Workload, Application Sharing Workload, A/V and Web Conferencing Workload, and Enterprise Voice Workload.
Having these functions split up does several things for you:
- Easy reference for discussion
- Implementation aid if you don't use OCS
- Troubleshooting aid if you do use OCS
- Preparation for Lync
Now, the architecture in Lync Server is bound to differ from this. What I mean BY well, anyommunications system like Lync will need.”
Lync 2010 will need fewer servers than OCS 2007, to boot. So it should be a simpler architecture.
Familiarize yourself with OCS' architecture and be pleasantly surprised when Lync rolls out!
A couple additional points I want to make about the OCS 2007 R2 poster:
- Make a list of all the ports you'll need to use and keep it handy during implementation (OCS or Lync). Port collisions can cause a lot of trouble fast; head them off ahead of time.
- Note the positions of the hardware load balancers. There are that many for a good reason.
- If there's a part of this that will change the most in Lync Server, I'd say it's “Certificate Requirements.” Virtualization, altered server roles,and the integrated PBX capabilities will all change that.
I recommend this to all companies who use OCS 2007 right now,as well as any companies considering Lync Server 2010. Download and keep it handy!
Any other downloadable OCS/Lync resources you know of? Post them here and I'll highlight them in future posts.