Skype for Business Server 2019 deployment Step-by-Step – Part -3

0
305
Reading Time: 7 minutes

Skype for Business Server 2019 deployment Step-by-Step – Part -3

In this section (Part-3), we are going to cover step-by-step deployment of Skype for Business Server 2019 Public Preview edition adding Skype for Business Server 2019 into existing topology.

Till Part-2 we have prepared the base OS, Installed the Skype for Business Server 2019 dependencies and installed Administrative tools.

Now I am starting the Introducing Skype for Business 2019 into existing Skype for Business 2015 topology.

Open Skype for Business Server 2019 Topology builder. I would prefer to run as admin.

Click on the “Download Topology from existing deployment” and click “OK” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-54.png

Once you click “OK” button, Topology builder will contact Central Management Server and ask you to save the fetched topology.

https://tech24online.com/wp-content/uploads/2018/08/word-image-57.png

Now navigate your favorite location and name it and click “Save” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-60.png

Once topology successfully downloaded, we can see, Lync Server 2013, Skype for Business Server 2015 and Skype for Business Server 2019 along with other supported components which can be defined:

https://tech24online.com/wp-content/uploads/2018/08/word-image-63.png

While my existing Skype for Business Server 2015 deployment, I mentioned “Australia” as central location. I would prefer to add Skype for Business Server 2019 into same central site, you may choose according to your lab scenario:

Expended the Skype for Business Server 2019 in to Topology builder. Here you can choose your desired option, Standard or Enterprise. I choose Enterprise for my lab:  https://tech24online.com/wp-content/uploads/2018/08/word-image-66.png

Right click on Enterprise Edition Front End Pools > Select New Front-End Pool to define a new Front End pool:  https://tech24online.com/wp-content/uploads/2018/08/word-image-69.png

Once you click on New Front-End Pool, a Define New Front End Pool wizard will open and will ask you select your options. In here you can define, your pool name, add front-end server, select features like conferencing, enterprise voice, archiving, monitoring, mediation server choice (either you wish to collocate or deploy separately), edge server, sql store, file share, office web app server etc.

Click “Next” button

https://tech24online.com/wp-content/uploads/2018/08/word-image-72.png

Here you may name your Skype for Business Server 2019 pool and click “Next”.

Note: Please do not forget to setup DNS records for this entry.

https://tech24online.com/wp-content/uploads/2018/08/word-image-74.png

Now it’s time to add ready Windows 2016 domain joined servers, those are reserved for Skype for Business Server 2019 pool. Enter your Server FQDN and click on “Add” button. Once you added all the servers, you may need to click on “Next” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-78.png

Here, setup wizard will ask you to select features which you want to enable in this pool.

In my lab, I have selected all the available features.

Once selection completed, you may hit the “Next” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-82.png

Here you need to define your choice for Mediation Server. Mediation server is a role which enables integration between Skype for Business and IP VOIP gateway. I have marked tick box because I want to collocate this into pool. A separate section (Enterprise Voice) will cover more about Mediation Server planning and deployment.

Click “Next” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-86.png

Here you can associate this new pool with your existing deployed Edge Server. I don’t have Edge in my lab therefore I kept it unselected.

You may decide as per your infrastructure scenario and click “Next” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-89.png

Here wizard will ask you to define Server database. You will not see this option in case of Standard edition deployment.

I have installed SQL Server 2016 Developer edition for my lab, for more details and planning please refer product documentation.

Please define the running SQL Server 2016 or newer version instance here. Click on “New

https://tech24online.com/wp-content/uploads/2018/08/word-image-91.png

Define your SQL Server FQDN and SQL Instance name. For example, I am running SQL Server 2016 on SQL19.TECH24ONLINE.COM machine and Instance I have defined while SQL Installation was SQL19.

After defining your SQL Server details, click “OK” and then “Next” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-93.png

https://tech24online.com/wp-content/uploads/2018/08/word-image-94.png

Here you need to define your file share. A detailed planning is required for production environment, please make sure you refer planning guide before doing it into production.

For my lab, I just created a folder share on domain controller DC2 and defined it here.

Define your share location and click “Next” button.

https://tech24online.com/wp-content/uploads/2018/08/word-image-96.png

Here you can define your external web services url and also override internal webservices.

For my lab, I kept it default, however you may edit it according to your infrastructure.

Once defined it, you may click on “Next” button.

https://tech24online.com/wp-content/uploads/2018/08/word-image-97.png

This window will ask you to select Office Web App Server. This role is required to handling presentation stuff while web conferencing, for more details please refer https://docs.microsoft.com/en-us/webappsserver/office-web-apps-server-overview

In my lab I don’t have Office Web App Server running, thus I left it unselected.

You may chose if you wish, and click “Next” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-99.png

Here you have opportunity to define Archiving database. You will not see this option, if you have not selected on “Select Features” page. I choose it and now have chance to define it.

You may define it any time, even after the deployment of the Skype for Business Pool/Server.

This role enables enterprises to record conversation, refer https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/archiving/archiving?toc=/SkypeForBusiness/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json

Select/Define your SQL Server and click “Next” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-101.png

Here you have opportunity to define Monitoring database. You will not see this option, if you have not selected on “Select Features” page. I choose it and now have chance to define it.

You may define it any time, even after the deployment of the Skype for Business Pool/Server.

This role enables enterprises to collect usages and call quality data which helps to monitor, plan utilization and even identifying issues , refer https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/monitoring?toc=/SkypeForBusiness/toc.json&bc=/SkypeForBusiness/breadcrumb/toc.json

Select/Define your SQL Server and click “Finish” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-103.png

Here we have successfully defined our Pool, Servers, features etc and now topology is ready to upload into Skype for Business Central Management Store.

https://tech24online.com/wp-content/uploads/2018/08/word-image-105.png

Now, we can publish the topology.

Go to Action > Topology > click on Publish button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-108.png

Once you click on “Publish” Publish Topology wizard will open. Here we have guidance from product team before publishing topology, please make sure:

  • A validation check on the root node did not return any errors.
  • A file share has been created for all file stores that you have configured in this topology.
  • All simple URLs have been defined.
  • For Enterprise Edition Front End pools and Persistent Chat pools and for Monitoring Servers and Archiving Servers: All SQL Server stores are installed and accessible remotely, and firewall exceptions for remote access to SQL Server are configured.
  • For a single Standard Edition server, the “Prepare first Standard Edition server” task was completed.
  • You are currently logged on as a SQL Server administrator (for example, as a member of the SQL sysadmin role).
  • If you are removing a Front End pool, all users, common area phones, analog devices, application contact objects, and conference directories have been removed from the pool.

To start publishing the Topology, click on “Next” button:

https://tech24online.com/wp-content/uploads/2018/08/word-image-109.png

Here Publish Topology wizard will ask you to select databases. In my lab, I have SQL19.TECH24ONLINE.COM as SQL Store with SQL19 instance.

You need to click on Advance to select the database file location:

https://tech24online.com/wp-content/uploads/2018/08/word-image-110.png

Here we must select 1 option out of 3.

I have selected “Use SQL Server instance default” which means, Skype for Business Deployment wizard will fetch file location based on running sql instance configuration.

You may select appropriate options according to your Lab/Dev environment.

Post selection, click “OK” button.

https://tech24online.com/wp-content/uploads/2018/08/word-image-111.png

And now Publish Topology wizard will try to contact backend sql servers and will add newly created Skype for Business Server 2019 Pool.

https://tech24online.com/wp-content/uploads/2018/08/word-image-112.png

https://tech24online.com/wp-content/uploads/2018/08/word-image-113.png

File access was failing because of DNS issue and once I updated the correct record, it was resolved.

https://tech24online.com/wp-content/uploads/2018/08/word-image-114.png

https://tech24online.com/wp-content/uploads/2018/08/word-image-115.png

Now topology publishing has been completed successfully and I am going to run Deployment Wizard.

Please Continue……. Part 4

In case you missed previous post, links given below:

Skype for Business Server 2019 deployment Step-by-Step – Part -1

Skype for Business Server 2019 deployment Step-by-Step – Part -2

LEAVE A REPLY

Please enter your comment!
Please enter your name here