28 Feb

Step-By-Step Guide to Deploying Lync Server 2010 Standard Edition Published

The installation of Lync Server 2010 is a fairly task-intensive process. In this article, I walk you through each of the tasks, at a step-by-step level, required to deploy a Lync Server 2010 Standard Edition Server lab environment.

The focus of this article is the following:

  • Prepare the Lync 2010 Standard Edition Server Infrastructure
  • Define the Topology for Lync 2010 Standard Edition Server in Topology Builder
  • Implement the Topology for Lync 2010 Standard Edition Server
  • Set Up the Lync 2010 Standard Edition Server
  • Run the Lync Server 2010 Control Panel

The article can be downloaded from here:
http://policelli.com/Files/Deploying_Lync_Server_2010_Standard.pdf. I will port this over to a blog post in the coming days.

I am also working on a similar step-by-step guide for Lync Server 2010 Enterprise Edition.

    15 thoughts on “Step-By-Step Guide to Deploying Lync Server 2010 Standard Edition Published

    1. Excellent Article. I have a bit of a dope question. I have set up a lync server standard edition and it seems to work. Because I followed similar lab suggestions my server naming is based on mostly internal use.
      One polycom phone I am testing will not add-on because it does not like the certificate I created in house. So I tried to purchase a true certificate but my configuration shows the “subject name” as the internal DNS name for the lync server (ex. lync.mydomain.local)
      My certificate will not issue because the subject name has to be a public domain name. (for example lync.mydomain.com )
      The certificate wizard does not allow me to change the values so I have set it elsewhere.
      Is there an easy way to change the public name of this lync server so when I generate the certificate request it will have its external/public name in the “subject name” field?

      Thanks.

        • Thanks John,
          Good link. I still get somewhat confused by Micrsoft’s examples of FQDN’s. It would be easier at least for me if they stuck with referring to internal domains as contoso.local and external as contoso.com. I am sure there is a miriad of reasons in large scale networks to not use that distinction but for smaller orginizations it sure would make the configuration easier to understand.
          I would then know when to refer to the server by its FQDN internal name srv1.contoso.local versus its external name like lync.contoso.com.

    2. U hav been a great help man…………..thanks a lot for helping us in the Deploying the Lync Server…………Really appreciate it man…..Thanks….Thanks a lot……

    Leave a Reply

    Your email address will not be published. Required fields are marked *

    You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>