Preparation

The first step to set up the machines for RTC Launcher installation is to run PowerShell scripts to manage Skype for Business Server applications and trusted third-party applications:

  1. Connect the machine with the installed Microsoft Skype for Business Server
  2. Open the Skype for Business Server Management Shell

  3. Run the following commands to register the machine as trusted application pool:

    New-CsTrustedApplicationPool -Identity rtclauncher01.dev.local -Registrar fe01.dev.local -Site Site:Main
New-CsTrustedApplicationComputer -Identity rtclaunher01.dev.local -Pool rtclauncher01.dev.local
Enable-CsTopology
    CODE

    Notes on the Script

    • Use own data for Uri, Identity, Site, Pool and TrustedApplicationPoolFqdn fields.
    • Use 'Get-CsSite' command to get information about the sites created as part of your Skype for Business Server infrastructure.
    • For more information about PowerShell commands, go to 'Application management cmdlets in Lync Server' section in the TechNet Library.

Installation

The second step is the installation of the Lync Server 2013 \ Skype for Business using Skype for Business Server - Deployment Wizard:

Configuration and Components

  1. Select "Install or "Update Skype for Business Server System" to proceed with installation.

    Skype for Business Server Deployment wizard

  2. On the next page select "Step 1: Install Local Configuration Store" and follow the instructions on screen.

    Skype for Business Server Deployment wizard: Step 1 and Step 2 selection

    Install Local Configuration Store choice

    Finish the installation wizard.

    Finishing of local configuration store installation

SfB Server Components

(tick) Preconditions: Step 1 is done, configuration storage is detected so Step 2 becomes enabled

  1. Start with "Step 2: Setup or Remove Skype for Business Server Components"
  2. Follow the instructions shown on screen and Finish the server components setup.

Certificates

(tick) Preconditions:   Step 1 and Step 2 are completed.
(warning) The "Run" button can be disabled if the machine is not registered as a trusted application pool on Skype for Business Server machine.

Proceed with Step 3 "Request, Install or Assign Certificates".

  1. In the "Certificate wizard" click on "Request" button and follow the instructions.

    Certificate wizard

  2. Enter a Certification Authority (CA) and specify a friendly name. 
    (lightbulb) These steps are depending on your local infrastructure and IT policy. Ask your security administrator for details

    Certificate request
  3. Finish the certificate installation.

(tick) Preconditions: Step 1-3 are all done. 

  1. After the certificate was received and assigned, get back to the Skype for Business Server Wizard and "Start Services" by selecting the Step 4.

  2. Verify that the services are correctly started.

Trusted Application Endpoints

Before starting the RTC Launcher installation, you need to prepare the trusted applications in the SfB Server.

Trusted Application Pool

Using the "Skype for Business server management shell" create trusted application pool.

New-CsTrustedApplicationPool -Identity lvse0142.dev.local -Registrar lvse0085.dev.local -Site Site:Main
New-CsTrustedApplicationComputer -Identity lvse0142.dev.local -Pool lvse0142.dev.local
CODE

Notes

  • Use own data for Identity, Registrar ,TrustedApplicationPoolFqdn and Site fields.
  • In case of using active/passive scenario two (or more) trusted appllication computers should be registered for one application pool.
  • For more information about PowerShell commands, go to "Application management cmdlets in Lync Server" section in the TechNet Library.

Trusted Applications and Endpoints

Using the "Skype for Business server management shell" create multiple trusted applications ....

New-CsTrustedApplication -ApplicationId rtclauncher -TrustedApplicationPoolFqdn rtclauncher01.dev.local -Port 6000
CODE

and one application endpoint per each trusted application. 

New-CsTrustedApplicationEndpoint -ApplicationId rtclauncher -TrustedApplicationPoolFqdn rtclauncher01.dev.local -SipAddress sip:rtclauncher01@dev.luware.com
CODE

Notes

  • Use own data for ApplicationId, Port, TrustedApplicationPoolFqdn and SipAddress fields.
  • Number of trusted applications will affect count of possible agent"s parallel sessions.
  • In case of active/passive scenario the same trusted applications should be used on each computer.

Minimum number: 2 applications.
Recommended number: 6 applications.

See more information: https://msdn.microsoft.com/EN-US/library/office/dn466115.aspx.


Grant conferencing policy to created application endpoints.

Run the following script to create a conferencing policy for RTC Launcher:

New-CsConferencingPolicy "Tag:RTCLauncher" -AllowIPAudio $true -AllowIPVideo $true -AllowMultiView $false -Description "RTC Launcher Conferencing Policy" -AllowParticipantControl $true -AllowAnonymousParticipantsInMeetings $true -AllowExternalUserControl $true -EnableDialInConferencing $true -AllowConferenceRecording $false -EnableDataCollaboration $true -MaxVideoConferenceResolution VGA
CODE


Run the following script to grant conferencing policy for every created application endpoint:

Get-CsTrustedApplicationEndpoint -Identity sip:rtclauncher01@dev.local | Grant-CsConferencingPolicy -PolicyName "Tag:RTCLauncher"
CODE
  • Use own data for Identity field.