I also checked that I had a working ADCS (not setup by me), so I could get internal certificates assigned on the front-end. As usual, it didn’t quite work as planned 🙂 I’ll now try to explain the process in detail, including some problems along the way.īefore starting the actual setup, I double checked that my network and AD infrastructure was setup correctly. After that I’ll continue with the Edge and Reverse Proxy installation.įor the front-end installation I followed TechNet’s deployment article with some twists. The next chapter will present the actual front-end installation, including some dilemmas/gotchas. Front-end DNS entries haven’t been discussed earlier however, so here goes: Front-end DNS That said, use these two blog posts as a compliment for this guide – they include some deeper information not discussed here. I’ve also previously written a blog post titled “Test Lab Guide: Windows Server 2016 with Integrated Exchange 2016, SfB Server 2015 and SharePoint 2016”, where I deployed a front-end server for Skype for Business Server 2015.
#SKYPE FOR BUSINESS ON PREM END OF LIFE PLUS#
However, as I’ve deployed Lync Edge plus Reverse proxy servers before, much of the planning/homework was already done. General information about planning for Skype for Business Server 2015 can be found at: This blog post will be quite massive, so I’ll split it into several chapters.
I’ll end the post with some check-up/misc. In this blog post I’ll discuss the deployment process in general, and also the problems (and solutions) that were discovered during/after the deployment. The deployment also included an Edge Server and a Reverse Proxy server (IIS with ARR). I was given the task of deploying a full-blown on-premise deployment of Skype for Business Server 2015 for a small company.
0 kommentar(er)
