![]() ![]() ![]() If you are electing to move users, depending upon the amount of downtime, you should consider moving your conference directories associated with the pool in question to retain PSTN dial in conferencing functionality for existing scheduled conferences. I could take the additional effort to introduce a small Standard Edition Pool to move users too to keep them online whilst I perform the in place upgrade – but in my lab I have no SLAs J Are you going to use the offline method?įor me, my decision is made for me, I have no available pools to move users to.Are you going to Move Users to a new pool, which in turn requires no (in reality, minimal) downtime for users during the upgrade, or.When performing an in place upgrade, there are two options I'm not going to go too much into the side by side approach in this article, but that approach would be required when moving from say Lync Server 2010, or you may wish to take that approach when Lync Server 2013 roles are hosted on Server 2008 R2 for example. A decision is to be made here, are you going to retain the existing DBs, or continue with new databases?Īre you going to perform an in place upgrade or side by side migration? ] My Monitoring and Archiving Stores are also installed on SQL 2012.My Backend database is currently installed on SQL2012.I am running a single Enterprise Edition pool, all Front Ends are running on Windows Server 2012 R2 and therefore support Windows Fabric v3 (Server 2008 does not).In my scenario, things are fairly simply There will be several applications that may not be supported within Skype for Business just yet, applications with the Lync Partner Eco System for example is your contact centre certified for Skype4B? Has your SBC been tested? Understanding the overall components that make up your topology is crucial. Now to begin with, to ensure any deployment no matter how big or small it's important not to overlook anything I have a single Kemp VLM load balancing my web service traffic, therefore my Internal Web Services FQDN points to a VIP presented by this appliance My Lync Server 2013 Topology is as follows Now an unfortunately a lab demon haunted me (in the form of a Windows Update to Server Technical Preview) on release day (1st May) that completely killed my lab, I did have mirrored databases along with persistent chat and an OWA farm deployed and it would have been interesting to see the Persistent Chat process.įor the purposes of this walkthrough this is what I will be starting off with: Good News - Skype for Business Server 2015 RTM components have been released!!īad News for some - VLSC\MSDN Subscription required at the moment :(Īs I haven't created a walkthrough post yet, I thought there would be no better time to get one on the board and kick off with my experience whilst migrating Lync Server 2013 to Skype for Business Server 2015. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |