Last night I had my first run at a production Lync Server 2010 installation, complete with OCS 2007 R2 coexistence with pools in 3 continents. To date I’ve done something north of 25 Lync Server installations, starting with Beta and moving through Beta Refresh, Release Candidate, and finally RTM. Needless to say the experience improved significantly through those pre-release builds. Most of those were test environments designed for various uses and only a couple of them included OCS coexistence, so I was curious to see how things actually went in a production environment with a number of OCS servers, Edge, Mediation, media gateways, etc.
I guess because the installation experience is so drastically different from OCS I expected that in an actual production environment I’d run into something unexpected that would require me to more closely examine the documentation, so I was pleasantly surprised when this didn’t happen. After getting the topology published and merged, everything went very well. In fact the only snag I hit at all was when I tried to move my first user and I incorrectly read the error message telling me that I needed to run Import-LegacyConfiguration (I got a little tab happy in CSCP and ran Import-LegacyConferenceDirectory instead).
Once that was worked out I moved my account from OCS to Lync. To find OCS users in CSCP make sure to add the Legacy user filter:
Because we had UM integration with OCS I needed to update Exchange to recognize the Lync pool. All this took was re-running ExchUCUtil.ps1 from Exchange and the Lync pool appeared in the gateway list with the correct associations.
The entire system is behind an R2 Edge which points to an R2 Director, all of which works fabulously with Lync (make sure your OCS R2 servers are minimally on the April 2010 updates). We also have an Audiocodes Mediant 1000 (upgraded to the 6.0 build that supports Lync) which is pointed to the Lync pool. Enterprise Voice services were retained for both Lync and OCS users in this configuration (as a point of reference it also worked for all users when the gateway was still pointed at OCS).
Overall a great start to a production Lync Server deployment!