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,
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
Check Powershell version
Restart is required
Prepare Active Directory
Install Administrative tools
Prepare First standard edition server
I will create a shared folder
It’s time to publish the topology
Publishing failed with an error that states the following
So I will double check that I am member of the required groups
It seems not, I will add Csadministrator and RTCUniversalServerAdmins
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)
Next I will put my server’s FQDN in the pool name, my FQDN Is
Now it’s time to publish the topology once again
Seems we have passed the permission issue as soon as the Standard edition FE server matches the FQDN of the server
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
I will run the Local setup for the server since I only have one server now.
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.
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.
Detailed steps for the local store installation can be found in the sub page.
Now it’s time to move to the next step and check for the prerequisites
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
I am attaching the hotfix after requesting and Installing as requested
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.
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.
I will navigate to the MSI file location and try to install it without using the wizard.
The file path is as showed in the previous path:
C:ProgramdataMicrosoftSkype for Business ServerDeploymentcache6.0.9319.0
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.
Now I’ll re-run the setup again
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.
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
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.
And it’s done
I will do the same steps for the OAuthTokenIssuer
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
Trying Management shell with the cmdlet start-cswindowsservices seems to work
All the services are running now
Stay tuned for the next article of deploying Edge server