![]() 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 |