Lync 2010RC : Some lessons learned testing upgrade from OCS2007 R2 to Lync 2010RC
I have begun testing with Lync 2010 RC. In my environment, I have OCS 2007 R2 and Exchange 2010 with UM deployed. I added Lync 2010 to the environment. I can blog about that process if people are interested. Today, I learned some things about the process of moving people from OCS 2007 R2 to Lync and also some interop issues. Here is a brief summary:
- Only users homed on a Lync pool can use the Lync client. I upgraded a user workstation to the Lync 2010 client. The user was homed on the OCS2007R2 pool and they were longer able to login to OCS with the Lync 2010 client. See the following article for more information. OC2007R2 client works against Lync server. Thus, if you are planning to upgrade an enterprise environment, you will need to plan the move to Lync on the back-end and also the client side.
- Lync uses a web-based control panel to manage users. You can't move the users from OCS 2007R2 to Lync using the OCS 2007R2 tools. Need to use the Lync control panel
- If you search for OCS 2007 R2 users (called Legacy users), they won't show up unless you add "Legacy user equals true" to the search filter. There is some text explaining this, but the text disappears once you type a name into the search field. This caught me for a couple minutes since I couldn't find the OCS 2007 R2/Legacy users.
- When I selected to move the user to the Lync pool, I got the following error. You need to run the "import-cslegacyconfiguration" command in a Lync powershell window. Note, I needed to run this command even though in the topology Builder, i selected to "Merge 2007 or 2007 r2 topology".