Instalacion Lync 2013 Standard Edition

**********************INSTALAR PREREQUISITOS LYNC 2013*****************

Windows 2008 R2

Todos los roles requieren

 

Lync Standard and Enterprise FrontEnd Pool

  • .NET 3.5 (activated by default)
  • SilverLight (optional)

Import-Module ServerManager

Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-HTTP-Activation, Web-Asp-Net, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Telnet-Client, BITS, Desktop-Experience

Director

Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, NET-HTTP-Activation, Web-Asp-Net, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Telnet-Client, BITS

Mediation: No more additional prerequisites

Edge: No more additional prerequisites

pChat:; We need Microsoft Message Queuing (Server and Services) Add-WindowsFeature MSMQ-Services

 

Windows 2012 y 2012 R2

Todos los roles requieren

 

Lync Standard and Enterprise FrontEnd Pool

  • .NET 3.5 (must be manually activated)
  • SilverLight (optional)

Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, Web-Dyn-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Windows-Identity-Foundation, Telnet-Client, BITS -Source D:\sources\sxs

Reg Add “HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\SecurityProviders\Schannel” /V “EnableSessionTicket” /D 2 /T REG_DWORD /F

 

Director

Add-WindowsFeature RSAT-ADDS, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Asp-Net, Web-Net-Ext, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Http-Logging, Web-Log-Libraries, Web-Request-Monitor, Web-Http-Tracing, Web-Basic-Auth, Web-Windows-Auth, Web-Client-Auth, Web-Filtering, Web-Stat-Compression, NET-WCF-HTTP-Activation45, Web-Asp-Net45, Web-Mgmt-Tools, Web-Scripting-Tools, Web-Mgmt-Compat, Telnet-Client, BITS -Source D:\sources\sxs

 

Mediation:No more additional prerequisites

Edge: No more additional prerequisites

pChat: Add-WindowsFeature MSMQ-Services

 

MODO 2: Otra forma de instalar pre-requisitos es con el script CS2013features.ps1

Con el Script Set-Cs2013Features.v2.7.zip (http://www.ehloworld.com/1697) el cual instala muchas cosas para Lync, y entre ellas los prerrequisitos para un Lync 2013 Standard o Enterprise, un SQL Express, etc

Set-Cs2013Features.ps1 Ejecutara las opciones por defecto para Enterprise Edition (silverligth, sql express para la Standard edition, etc(


**********************CERTIFICATE REQUIREMENTS*****************






 

INSTALACION DE LYNC

 

Insert CD and Run Setup.exe. You will be prompted to install Visual C++, click “Yes” (below)


You can accept default location and click Install (below)


Accept Terms and click “Ok” to install.


When install is complete (3minute wait time) you will have below apps on your server and the Lync Server Deployment Wizard (below) will appear.


  • Lync Server Manager
  • Lync Server Deployment Wizard

    Deployment wizard

    Podemos instalar el topology builder (install administrative tools) u optar por preparar el Active Directory (esquema). Es indiferente el orden


    01.- Prepare Active Directory

    Click “Prepare Active Directory”. (As noted in prerequisites, you will need AD DS and AD LDS Tools Feature installed on your Front End to complete this step.)


     

    • Step 1: Prepare Schema. (takes 1minute, and you may need to wait a couple minutes before this and step 2) 
    • Step 2: Verify Replication of Schema is not necessary if this is a Lab and there is only one AD server—you can safely keep moving to step 3.
    • Step 3: Prepare Forest | Next | select Local Domain  | Next (5sec)
    • Step 4: just keep moving
    • Step 5: Prepare Domain | Next (5sec)
    • Step 6: just keep moving
    • Step 7 below: add a user to CSAdministrator role group to manage Lync 2013


    02.- Configure DNS Records y Permisos

    DNS

    Lets open DNS Manager on AD server. Right click on your domain (in our case lab.local) under Forward Lookup Zones, click “Other New Records” and scroll down to “Service Location (SRV)” and click Create Record.

    Will will add a DNS SRV record pointing at our Lync FE Server FQDN (FE01.lab.local in our case)

    • Service = _sipinternaltls
    • Protocol = _tcp
    • Port number = 5061
    • Host Offering the service =  FQDN of Lync Std. FE server or Pool. (If enterprise)



    • Crear los siguientes registros A que apunten Lync Estándar Server. El registro POOL no es necesario crearlo
    • dialin. domain.com
    • meet. domain.com
    • admin.domain.com

     


     

     Add Lync Administrative User To Admin Group

    Add the Administrator to CSAdministrator  group (shownbelow). By default, Domain Admins can’t manage Lync


     

    DISEÑAR TOPOLOGIA DEL LYNC STANDARD EDITION

    03.-Prepare First Standard Edition Server

    Ir a Deployment Wizard > “Prepare first Standard Edition server”.

    Solo usaremos esta opción si no vamos a crear un Enterprise Server (pool de servidores que proporcionan HA). Un estándar server es para implementaciones pequeñas el cual esta soportado en solo este servidor.

    Se instalara sobre una base de datos SQL Express (a diferencia de la Enterprise que es un un SQL server normal).

    Lo que hace el “Prepare first Standadr Edition server” prepara nuestro Lync Server para albergar el CMS (Central Management Store”, el cual en la versión Enterprise se almacena en el SQL server



    You will see the below “Prepare single Standard Edition Server” wizard window and you can just click “Next”. During this process the below will be installed:

    • SQL Server 2008 Express Edition will be installed
    • RTC databases will be created and populated
    • Lync Server installation files will be put in place
    • Etc

    (Note: as noted in prereqs, Windows Identity Foundation 3.5 must be installed for this process to complete successfully)


    (Time: on new AD with no users, 6-10 minutes to Prepare first Server)

     

    04.-Instalar Administrative Tools y crear Topologia (Topology Builder)

    Now lets go back to the Deployment Wizard and click “Install Administrative Tools”.


    This takes just a second to run. It will install Topology builder

     

     

     

    Build and Publish Topology

    Next we will go to Start and run “Lync Server Topology Builder” (below).


    Select New Topology (as shown below) and then give the topology some name (just any old name like “mylab.tbxml”)


    Now we will be define this topology.

    Primary SIP domain: lab.local | Next


    Specify additional supported domains: {nothing/none} | Next


    Define the First site


    Specify site details


     

    Con esto hemos definido la topología, pero debemos definir al menos un Front-end Pool. Se nos abrirá el wizard


     

     

     

     

    Next we will define a new Front End pool. click Next


    Define Front End Pool: Elegimos la opción de Standard Edition Pool, el cual solo instalara un único servidor, porque no habrá HA, también la base de datos será una SQL Express

    Note: if this is a Standard Edition, this FQDN will be exactly the same FQDN as your FE server  (FE01.lab.local in our case)

    Standard Edition Server


    Next we will select Features for this Front End Pool. Check these features:

    • Conferencing
    • Enterprise Voice
    • CAC

    Tip: What works best for me is to NOT define ARCHIIVE and MONITOR servers till you are ready to actually install them. I suggest to NOT select Archiving and Monitoring now. We will do that after we have actually installed the SQL server and are ready to define those roles in topology builder

     
     


     Select Collocated server roles: enable if is necessary the collocate Mediation Server:


     

    Associate server roles with this front End pool Enable an Edge pool…: unchecked


    Define SQL store: It’s automatically selected because we have installed SQL express before through script


    Define the file store: default, next (NOTE: You will need to manually create this network share and give rights to everyone. This wizard will not automatically create it for you)


    Let create the Lync file store share right now so we don’t forget.  You can create this folder where ever you want but for this lab we will create a folder called “Share” in C:\ of the Lync Server. Next go into the properties of the folder and give full access permissions to these groups:

    • RTCHS Universal Services
    • RTC Component Universal Services
    • RTC Universal Server Admins
    • RTC Universal Config Replicator

    Click on the “Sharing” tab, click on “Share”.


    In the “File Sharing” Wizard click the dropdown beside “Add” and select “Find People…” and in “Enter the object names to select” type RTC. Now press the CTRL key and select the above groups. Next you will need to change each group to “Read/Write” and click “Share” to finish the sharing Wizard.


     

     

     

     

    Specify the web services URL: Since this is a lab we can let the External Base URL the default.


    Specify where your Office Web App server is. (you probably don’t have one yet, just point to OWA.lab.local)


     

     

     

     

     

     

     

     

     

     

     

    05. -Editamos la topología para poner la URL de Admin

    Ya hemos terminado de construir la topología. Nos falta editarla para nadir la     URL de administración


    Edit properties of topology

    Right click on “Lync Server 2013 (Preview) and then “Edit Properties”


    Scroll down to “Administrative access URL” (as shown below) and define the admin url as https://admin.lab.local  and select Front End Server (FE01.lab.local in our lab)that will host the CMS


     
     

    06.- Publish Topology

    Action > topology >Publish


     

     

     

     

     

     

    Comienza la publicación. Aquí difiere de cuando instalamos una implantación Enterprise pool



    When finished you can “Click Here to open to-do list”. Since we are really good  we’ve already done these items. (if you took a shortcut, backup to see detailed step above)


     

     

     

    07.-Instalación del Lync (binarios)

    It will install Lync environment based in the topology create before

    Open Deployment Wizard | Install or Update Lync Server System


    Now we will install some Lync Server System components, put Certs in place and Start Services:

    • Step1 Install RtcLocal database
    • Step2 Install Speechfiles, etc.
    • Setup Certs
    • Start Lync Services


    • Step1 Install Local Configuration Store (will install RtcLocal): Retrieve Directly from the CMS…



    • Step2 Setup Lync Server components (will install Speechfiles, etc)



    (NOTE: if you designated the archive/monitoring server, this will fail because SQL for those stores is not there yet.)

    • Step3 Request Certs (Note: if this is a lab setup, and you have parallel installed AD and Lync FE OS’s, remember the FE needs to have “gpudate /force” run or be rebooted after you stand up the AD CA so the CA is authoritative)


    Como no tenemos certificado, en primer lugar hay que solicitarlos. Seleccionar “Default Certificate” then click “Request”


    Certificate Request: Next


    Send the request immediately to an online cert authority


    Choose a Certificate Authority (CA): Select a CA from the list


    Certification Authority Account: Next


    Specify Alternative Certificate Template: Next


    Name and Security Settings: some name


     

     

    Organization Information: fill in Org and Org Unit


    Geographical Information: fill in


    Subject Name/Subject Alternative Names: Next


    SIP Domain Setting on SAN: Select SIP Domain (example: puma.local) | Next


    Configure Additional SAN: Next


    Certificate Request Summary: Next


    Executing Commands: Completed: Next


    Ahora toca asignarlo a los servicio de Lync 2013. Finish


    Certificate Assignment: Next


     

     

    Certificate Assignment Summary: Next


    Executing Commands: Finish


    Como vemos ya se han asignado. Lo podríamos hacer de nuevo en “Assign”, pero ya no es necesario


    Vemos como ya lo ha asignado. Ahora como ya tenemos el certificado creado anteriormente mediante la request, ya simplemente a OAuthTokenIssuer le asignamos el certificado


    Seguimos el asistente Next, Next, Next y se asigna


    • Step 4: Start Services


    Le damos a start para que se arranquen


     

    Salimos del deployment wizard


     

     

     

     

    After services are started you can open the Services to verify all the Lync Services are running.


     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

     

    Lync Control Panel

    you will be asked to type in Administrator credentials. If this is new server you will also be asked to install Silverlight.

     


     


     
     

    Add and Enable AD Users

    Next, we will move to our AD server and add several users to Active Directory (I suggest for your first test users to NOT use the Administrator, but 3 other users). In our case I added:

    Now back to Lync Server Control Panel. Click on User | Enable Users. Now click the “Add” button and Add the 3 users.


    Click “Enable” and if you get no errors, you should have 3 Lync users ready to login. Let’s open Lync 2013 and login!


    Wow you have installed Lync Server 2013!

    Please note some pieces in Lync that you have not configured yet:

  • Monitor and Archiving Roles
  • Persistent Chat Server
  • Sharing PowerPoint requires a Office Web Apps Server deployed

Be the first to comment

Leave a Reply