In part 1 of this series we went through the deployment prerequisites, prepared the servers and prepared the environment for the deployment. In this part we will go through the planning tool, topology building and the server deployment.

1. First we need to create the necessary DNS records, we need the below records:

2. The next step will be creating a simple internal only topology using the planning tool and export it to the central store using the topology builder. Using the planning tool I selected the Getting Started option

And used the below parameters:

So my Central site will look like that

3. Then in the next page I added mbdomain.ad as my SIP domain as shown below

4. For the Bandwidth capacity planning, I changed the profile to be light (it’s a labJ) and left the rest as is

5. Skip the branch office page as it’s only one central site

6. For the External user access, I selected No since I’ll build this lab with no external access then I’ll discuss enabling the external access later in another series…

7. Click Draw and here is the topology

8. Double clicking my site showed the expanded topology as below

9. Now to export our topology to the Lync topology builder where we will modify few parameters and then export the topology to the central management server… Select File, Export, Export to Topology Builder

10. We need to import the topology using the Lync topology builder. Select the ‘Open Topology from a local file’ and choose the lab topology

11. As you see there are few points that needs attention and they are marked in Red-X

12. Expand the File Stores and Edit the configuration to use the Lync Server share that we created before

13. Now we need to configure the administration URL by editing the Lync Server 2010 (RC) root object from the left hand pane, click Simple URLs, under Administrative access URL type https://admin.mbdomain.ad

14. So now you should have the below

Now with the configuration in the builder we need to publish the configuration to the management server.

15. From the Lync root object select ‘Publish Topology’

16. Select Next

17. Ensure that the pool is the correct one and then Next

18. And finish

In the next part, we will deploy a local configuration store with the published configuration in the central management store on our Lync server.