Before we jump in for more Lync Admin tasks, let me address a question that's probably come up in your head. “Why just 20? Lync has a LOT more things for us to do!”
And you're right on that. I may be missing several tasks many Lync admins will need to know. (If so, and you want to point it out, feel free to email it over or leave a comment!). The tasks I blog about in this series have come from two sources:
• Our own Lync installs
• Frequent online support requests
These 20 Tasks are what came up the most, and/or what I judge as the most viable. There are definitely a lot more out there. Some of which will show up on this blog eventually, I'm sure.
Part 4: How to Add New Servers to Lync
Now, with that said, let's talk about something crucial: Adding a new server to the Lync topology. I'll use an A/V Conferencing Server as the example.
You will need:
• A server, functioning and connected to the local network your Lync Server is on
• The Lync Server 2010 installation media
• 1-2 hours
(Note: I'm assuming a single computer pool here.)
1. Define the New Server in Lync Topology Builder
a. Log on to the server where you installed Topology Builder.
b. Open “Lync Server Topology Builder” from the Microsoft Lync Server 2010 menu.
c. On the Welcome page, click Download Topology from Existing Deployment. Click OK.
d. A “Save Topology As” box will come up. Choose a location, name the file whatever you'll recognize later and save it. (Keep the “.tbxml” extension.)
e. In Topology Builder, click to expand the Server Role tree view.
f. Right-click “A/V Conferencing Pools”.
g. Click New A/V Conferencing Pool.
h. On the “Define the A/V Conferencing Pool FQDN” page that comes up,select Single Computer Pool.
i. Enter your Lync FQDN and click Next.
j. On the “Associate Front End Pools” page,select the Front End pool you want to associate with the new A/V Conferencing Server. (You'll probably have only one option.)
k. Click Finish.
2. Publish the Edited Topology
Note: Before you start, make sure you're logged in as a SQL administrator.
• Right-click the Lync Server 2010 node.
• Click Publish Topology.
• Click Next on the first “Publish the Topology” page.
• Next you have the “Create Databases” page. Select the databases you want to publish.
• If you want to modify the default SQL setup, then click Advanced here. It's optional, but it gives you two data file placement options:
** “Automatically Determine Database File Location” – Determines the best performance options based on your SQL database configuration. Works by distributing log and data files to the best location.
** “Use SQL Server Instance Defaults” – Log and data files are left on the SQL Server for you to move as you see fit.
• Click OK once you've selected an option. Then click Next.
• Select a Front End pool on the “Select Central Management Server” page.
• Click Next to complete the publishing process.
• When it's done, click Finish. Now the new server needs a local configuration store.
3. Install the Local Configuration Store on the New Server
a. Grab your Lync Server installation media. Load it on the new server.
b. Browse to setupamd64Setup.exe and click OK.
(If you're prompted to install Microsoft Visual C++ 2008, click Yes.)
c. Click OK on the “Lync Server 2010 Installation Location” page. Accept the license terms.
d. Click Install or Update Lync Server System on the Deployment Wizard page.
e. Click Next until you get to “Step1: Install Local Configuration Store”. Click Run.
f. Make sure the “Retrieve Configuration Automatically from the Central Management Store” option is selected on the configuration page. Then click Next.
g. Click Finish when the install is done. Now, since we're here…
4. Install Lync Server 2010 on the New Server
• On the “Microsoft Lync Server 2010 – Deployment Wizard” page, click Next until you get to “Step 2: Setup or Remove Lync Server Components”.
• Click Run.
• Click Next on the “Setup Lync Server Components” page.
• Click Finish when the task status completes. Now we get to the detailed part: the certificate.
5. Configure a Default Certificate for the New Server
Note: A/V Conferencing, Stand-Alone Mediation and Survivable Branch Appliance servers only require one default certificate. Standard Edition, Enterprise Front-End and Director servers require three.
a. Back on the “Microsoft Lync Server 2010 – Deployment Wizard” page, click Next to get to “Step 3: Request, Install or Assign Certificates”.
b. Click Run. (Away we go…)
c. Click Request on the “Certificate Wizard” page. Click New on the “Certificate Request” page.
d. Select Send the Request Immediately on the “Delayed or Immediate Requests” page. Click Next.
e. Click the cert authority you want on the “Choose a Certification Authority (CA)” page. Click Next.
f. Enter some alternate credentials (if an account doesn””t have enough authority to request the certificate on its own) on the “Certification Authority Account” page. Click Next.
g. Click Next on the “Specify Alternate Certificate Template” page.
h. Next we come to the “Name and Security Settings” page. Start by entering a 'Friendly Name.' (I wonder what would happen if you entered an UNfriendly name…)
i. Click the Key Bit Length in the Key Bit Length list. Click Next.
j. It's optional, but you can specify organization and geographical information on the next two pages. Click Next either way.
k. Review the Subject Name and Subject Alternative Names on the next page. Make sure the right server FQDNs are shown before clicking Next.
l. Select Configured SIP Domains for all SIP domains in Your Deployment on the “SIP Domain setting” page. Click Next.
m. If you want to add more Subject Alternative names, the next page gives you the option. Click Next.
n. Next up are a series of pages you just need to check over and click through.
—Certificate Request Summary
—Online Certificate Request Status
—Certificate Assignment Summary page
—Executing Commands (Finish)
n. Finally, click Close on the “Certificate Wizard” page. Phew!
6. Start the New Server
• Once again on the “Microsoft Lync Server 2010 – Deployment Wizard” page, click Next to get to “Step 4: Start Services”.
• Click Run.
• Click Next to start the new Lync Server's services.
• Once all services start up, click Finish.
That should do it! You now have a functioning A/V Conferencing server deployed in your network. (Configuring a Conferencing Server is a whole other animal; I'll let TechNet help you with that one for now.)
With minor changes, you can use these steps to deploy several different Lync servers. Enterprise Voice, or Archiving for example.
Thoughts? Questions so far?