Microsoft Supported Method to Move from Pure Lync Online to #Lync Server On-Premises/hybrid deployment
This is a scenario we are hitting more and more, and are working with a number of customers on right now. Microsoft are increasingly offering Office 365 licencing, which means customers who haven’t previously had Lync can quickly enable Lync Online for basic IM/P and a bit of voice and video (there is still no PSTN/Enterprise Voice in Office 365).
Customers get to X seats in Lync Online, then decide they want to deploy Lync Server on-premises, reasons include:
- Enterprise Voice (True PSTN numbers, Response Groups etc.)
- Network/QoS/Bandwidth/CAC Reasons
- Server Side Application Development/3rd Party Application Integration
- A certain country/region/office/department cannot be “in the cloud”
- Customer has bought E4 licences, giving them user rights for Enterprise voice On-Premise
Until now, unfortunately, there has been no clean way to do this. The official Microsoft guidance was to disable the Lync Online deployment (disabling all the users) then deploy Lync Server, then re-enable Lync Online/hybrid, then re-enable the Online and On-prem users. This wasn’t very practical both in terms of downtime and there was no easy way to export users buddy lists (other than exporting them one by one with the users password). There were hacky ways around this, but nothing supported. The other option was to have a different SIP domain on-prem, again, this was messy.
Now there is an officially supported process to move from pure Lync Online to on-premise/hybrid: Moving users from Lync Online to Lync on-premises
Note Scheduled meetings for Online users are not migrated and need to be recreated, but users can be moved with their complete buddy list.
I have yet to test the final documented process, but have a number of projects coming up involving this and will report back on the blog, sign up for RSS/email updates. If you have feedback please let me know.