Moving to Lync Server 2013: A Guide to the Installation Process (Part 1)

Lync Server 2013

Starting this week, I’m participating in a Lync Server 2013 install. I’m doing some of the install work, and recording the details step-by-step. I’ll blog about the entire process.

This post and the next few will form a guide, to help others see what’s involved in a Lync setup, so you can prepare for your own!

What to Expect: Reference Guide for Your Own Lync 2013 Install

I’m documenting each step in the setup process. Including the errors we encountered, why they occurred & how we fixed them.

This series is much like the “Path to Lync Server” posts I wrote in 2011.  With more screenshots!

Initial Prep: Server Hardware is Prepared

I’ll start with some talk about our preparations made before beginning Setup.
The office already has Lync Server 2010 running. It’s a 2010 Standard Edition, with Mediation Server (not collocated) and a PSTN gateway from Dialogic. Archiving and Monitoring were not enabled. Federation is active.

We’re installing Lync Server 2013 while 2010 is still active. On a fresh (virtualized) server, under the same domain. Once install is complete, we’ll migrate users over.

For Lync Server 2013, we’re expanding the available feature set. Archiving and Monitoring will be added, as will Web Apps Server and XMPP Federation. We’ll redirect the PSTN Gateway to the 2013 servers once the backend is fully in place.

We added 4 cores, and 32GB more RAM to the server. This is listed in the TechNet documentation, as the optimum values for a clean install. (We did it mostly because it speeds up the process.)

Coming Soon: The Install Path to Lync Server 2013!

So far, we’re still in the process. Next post will contain the reference links we consulted, and the beginning steps.

I may move to 2 posts a week for this series…so be sure to check back soon!

In the meantime, a question for my readers: Are you preparing for a Lync Server 2013 install or upgrade soon? If so, what obstacles (if any) are you encountering?

2 Comments

2 Comments

  1. Bill  •  Jan 26, 2013 @1:54 am

    Hi,
    We are considering “upgrading” to Lync Server 2013. I emphasize upgrading as “migrating” seems to be overkill for our organization. As you can imagine, having to purchase another set of servers to accommodate a “migration” is an obstacle all by itself. I am not sure I can justify the expense to my CFO, even if I could make the argument that we could repurpose the existing servers after the migration is complete. I have two questions.

    I wouldn’t place our current Lync 2010 deployment on the “Critical” business functionality list. We use it for IM, a/v, web conferencing, but we could survive if it was offline for a while. So, is it wrong to think that we could simply remove our Lync 2010 deployment and start fresh with a Lync 2013 installation?

    Secondly, we have a standard edition front-end server and an edge server in our deployment. I could make the argument to buy a new server to replace our standard edition front-end server, but we just bought the edge server recently to expand our existing deployment. So, could I do a co-existence with the existing standard edition server and then remove Lync 2010 Edge server and reinstall as a Lync 2013 Edge?

    If nothing else, I hope this sparks a conversion with other SMB owners out there and how they plan to “Migrate”.

    Thanks.

  2. Ivailo Tzenkov  •  Jan 26, 2013 @4:09 pm

    We did it already. As we migrated from a mixed OCS 2007-R2 environment, we moved all services to R2, decommissioned the R1 servers, then installed Lync 2013 SE with collocated mediation and Edge. Most of our issues were related to the response groups configuration – they migrated successfully but for some reason didn”t start to receive calls; it appeared that the OCS resgroup service didn”t want to “let go” the configuration and we had to delete all resgroups and recreate them from scratch. N.B. we exported them with the respective cmdlet but the import could not be completed :) At least the export actually exported the wav files and as we had documented the resgroup logic it was a matter of minutes to get them running. We also had some issues with the TMG publishing of the Edge – firstly, some wrong rules (damn TMG protocol direction!), secondly – the certificate reqs for 2013 are different from those in 2013 and we had to reissue (if you use the same cert with multiple SANs for everything Lync-related, as we are, you need two more sans – for the web apps server and the xmpp federation – it”s a total of 8 SANs for all Lync needs). Some issues with the direct SIP and our SIP provider but, hey – mediation in Lync is waaaaaay better the mediation in OCS and it was again a matter of several days and many wireshark captures to put it in production.
    We still cannot fully run the mobility and federation aspects – but they are somewhat “2nd” level features and not critical at all – will have to wait.

    Otherwise, everything went smoothly :)

Leave a Reply

Allowed tags: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>



  • Lync Insider Email Updates

    Skip the visit - get Lync Insider posts in your inbox! Emails delivered every Friday.

  • About the Lync Insider Blog

    The Lync Insider is a blog about the technology we use to communicate in business today. Here we talk about Microsoft Lync Server 2013, its predecessor Lync Server 2010, Unified Communications, Voice over IP and related technologies like Exchange Server. Written by Chris W., Tech Writer & SEO Engineer for PlanetMagpie IT Consulting.
  • Categories

  • Archives