Install prerequisites

Frontend/Standard edition as well

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, Telnet-Client,

Windows-Identity-Foundation

From <https://technet.microsoft.com/en-us/library/dn951388.aspx>

Installing Director Prerequesties

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-Scripting-Tools, Web-Mgmt-Compat, Desktop-Experience, Telnet-Client

From <https://technet.microsoft.com/en-us/library/dn951388.aspx>

Check Powershell version

$psversiontable

clip_image001

Install prerequisites

clip_image002

clip_image003

Restart is required

clip_image004

clip_image005

clip_image006

clip_image007

Prepare Active Directory

clip_image008

clip_image009

clip_image010

clip_image011

clip_image012

clip_image013

clip_image014

Install Administrative tools

clip_image015

clip_image016

clip_image017

clip_image018

Prepare First standard edition server

clip_image019

clip_image020

clip_image021

clip_image022

clip_image023

clip_image024

clip_image025

clip_image026

clip_image027

clip_image028

clip_image029

clip_image030

clip_image031

I will create a shared folder

clip_image032

clip_image033

clip_image034

clip_image035

clip_image036

clip_image037

clip_image038

It’s time to publish the topology

clip_image039

clip_image040

Publishing failed with an error that states the following

clip_image041

So I will double check that I am member of the required groups

clip_image042

It seems not, I will add Csadministrator and RTCUniversalServerAdmins

clip_image043

Solution:

Still I get the same error every time I try to publish the topology. Apparently the way I solved this was by creating a new topology where the standard pool name must match the server’s hostname otherwise Topology won’t be able to access the SQL Express that’s installed by Lync setup.

So in this case I am going to re-create my topology as following

Moh10ly.com is my public domain which is going to be my sip domain in this case not my local one (Lab.com)

clip_image023[1]

clip_image024[1]

clip_image025[1]

clip_image026[1]

clip_image027[1]

Next I will put my server’s FQDN in the pool name, my FQDN Is

clip_image044

clip_image045

clip_image028[1]

clip_image029[1]

clip_image030[1]

clip_image046

clip_image047

clip_image034[1]

clip_image035[1]

clip_image036[1]

clip_image048

clip_image049

Now it’s time to publish the topology once again

clip_image050

clip_image051

clip_image052

Seems we have passed the permission issue as soon as the Standard edition FE server matches the FQDN of the server

clip_image053

clip_image054

We’ll look up at the open to-do list now

The to do list seems a bit different from Lync 2013 as it requires the part about the certificate

clip_image055

I will run the Local setup for the server since I only have one server now.

clip_image056

Before we run the local setup we need to make sure that our account has the required privileges which is shown under the Install local CS below. Since I already have configured the account’s privileges I will continue my setup.

clip_image057

clip_image058

clip_image059

clip_image060

There’s nothing new about the local store installation on S4B except that it checks and downloads updates during this process as the report shows below.

clip_image061

Detailed steps for the local store installation can be found in the sub page.

clip_image062

Now it’s time to move to the next step and check for the prerequisites

clip_image063

clip_image064

clip_image065

S4B says that a prerequisite is not meet, checking the link posted in the error information it seems that it needs a hotfix to be installed on the server

http://go.microsoft.com/fwlink/?LinkId=519376

clip_image066

I am attaching the hotfix after requesting and Installing as requested

<<478232_intl_x64_zip.rar>>

clip_image067

clip_image068

After finishing we’ll double check if the prerequisites are meet or not

Running the setup again it seems that the prerequisite has been satisfied.

clip_image069

The setup and in particular the next step could take approximately about 5-10 minutes depending on the resources you have assigned to the Skype for business server.

clip_image070

clip_image071

I will navigate to the MSI file location and try to install it without using the wizard.

clip_image072

The file path is as showed in the previous path:

C:ProgramdataMicrosoftSkype for Business ServerDeploymentcache6.0.9319.0

clip_image073

So the problem is that Windows Identity foundation is not installed. Although I have copied the prerequisite cmdlet from the official Microsoft Skype for business’s technet article but it seems they have missed out there so I will adjust the powershell cmdlet to include it which means you won’t face this issue.

clip_image074

clip_image075

Now I’ll re-run the setup again

clip_image076

We have passed the error already and now in the process of assigning accounts to SQL services.

The setup might take approximately 30-60 minutes installing all the required components.

clip_image077

clip_image078

In order to continue to the next step we must deploy CA (Certification Authority) to issue a certificate for Skype for Business Front end web services.

I already have one CA deployed on my CA so I will just go ahead and click run on the step 3

This process will be easy as it’s automated if you have configured your CA properly. First click on Request

clip_image079

Now S4B certificate request wizard provides new user interface that’s easier and faster to fill, I will fill it and go ahead with issuing the certificate.

clip_image080

clip_image081

clip_image082

clip_image083

clip_image084

clip_image085

clip_image086

And it’s done

clip_image087

I will do the same steps for the OAuthTokenIssuer

clip_image088

clip_image089

Now it’s time to start the Services and check eventviewer

Trying to start the services from the wizard fails with event ID 20002 so instead I am going to try Lync Management shell instead

clip_image090

Trying Management shell with the cmdlet start-cswindowsservices seems to work

clip_image091

clip_image092

All the services are running now

clip_image093

 

Stay tuned for the next article of deploying Edge server Winking smile

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.