Skype for Business External Domain the Action Couldnt Be Completed Please Try Again Later

Skype for Business Server 2015 Deployment – Part two

Continuing from a previous post this article moves into the installation and configuration of the Skype for Business Server components for a Standard Edition Front end End server.  As with the previous commodity whatever mandatory steps are identified past bulleted paragraphs while not-indented steps for validation and educational purposes are optional.

Deployment

The 2nd article in this series volition embrace the following deployment steps:

• Defining the Topology

• Deploying the Server Components

• Verifying the Installation

Before performing these steps in this commodity brand sure to successfully consummate all of the prerequisite actions covered in Part ane of this series.

Define Topology

Before installing any additional server components the Skype for Business topology must be defined.

Create New Topology

• Launch the Skype for Business Server 2015 Topology Architect and and so select New Topology.

• Salvage a new .tbxml file with whatsoever desired proper noun (e.1000. 06072015.tbxml).
• For the Master SIP domain enter the desired domain namespace (e.g. jdskype.cyberspace).

Add together any additional desired SIP domains at this point , but a single SIP domain is sufficient for most deployments equally well as this series of articles.

• Select a Name for the kickoff site to be created in the topology (e.g. Lab) and enter a Description if desired.
• Specify the locality information associated with the first site and so complete the wizard.

At this point the Define New Front end End Pool sorcerer should exist automatically launched.

• On the Ascertain Forepart Puddle FQDN folio select Standard Edition Server and so enter the Fully Qualified Domain Name (FQDN) of the Windows domain fellow member server where the SFB prerequisites were installed (e.g. fe.jdskype.cyberspace).

• Select the features which should exist installed and enabled on this Front End server.  Later articles will comprehend the deployment of some of these additional features.

• Retain the default enabled setting of Collocate Mediation Server on the Select Collocated Server Roles page.
• On the Associate Server Roles with this Front Finish Pool page get out the option bare every bit an Edge Server does non yet exist.  This setting will be addressed when an Border Server is deployed in a after article.
• Every bit this is a Standard Edition server and so there will be no configurable options available on the Define the SQL Shop page.  Take note of the automatically defined SQL Server shop which is comprised of the server'south FQDN (iron.jdskype.net) followed by the previously installed SQL Limited instance proper noun (RTC).

• On the Define a File Store page enter the name of the Windows file share created in the previous section (e.g. SFBShare).

• On the Specify the Web Services URL folio the External Base URL will automatically exist gear up to the same FQDN equally the internal Front End server (eastward.chiliad. fe.jdskype.cyberspace).  For the purposes of this commodity the default setting will exist retained and in the future when external services are published this will be updated to reflect the external namespace.

• The adjacent folio Select an Role Web Apps Server is used to either define a new OWAS pool FQDN or associate this server with an existing OWAS puddle.  The side by side article will cover deploying this server role so but uncheck this selection and and so click Finish to complete the sorcerer.  (Note that until this server is deployed that PowerPoint content sharing will exist unavailable as this service is not handled by the Skype for Business Front Finish server role.)

  Upon completion the Topology Architect window should refresh and the defined settings volition exist populated as shown.

• Back at the master Topology Builder window select Edit Properties on the Lync Server root-level object.  Highlight the Simple URLs section and enter the desired Administrative Access URL (e.g. https://admin.jdskype.cyberspace).  Technically his is an optional step equally the authoritative access URL is not required, merely is a convenient style to admission the Server Command Panel via a spider web browser internally.
• Move down to the Primal Management Server section and select the new Front Terminate server (e.m. fe.jdskype.net) every bit the location to install the CMS component on.

Publish Topology

The final process is to publish the changes made to the topology into the Central Management Server database which too updates information in the RTC services container in Active Directory and sets upward the folder structure and permissions on the file share.

• From the Activity menu select Publish Topology.  The local server FQDN for the Fundamental Management Store location should already be populated in the drop-down menu due to the previous step.  If all configuration steps were performed correctly then the sorcerer should consummate without any errors or warnings.

Deploy Server

Unlike most other Microsoft server platform products were installation of the actual server components is i of the very first steps, the Communications Server family has historically been different.  The server installation itself is quite hands-off and can exist automated to a large degree.  The off-white amount of activity up until this point has been geared around providing the backend components to store the overall configuration of the environment, which is now bachelor for utilise past the server installation steps.

Install Skype for Business Server Components

The next step is to install a second SQL Limited named instance chosen RTCLOCAL on the local server which will comprise a replica of the existing RTC named instance.

Only the offset Standard Edition server in the organization would contain the authoritative RTC case installed in the previous commodity, while all other Forepart Terminate Servers (and fifty-fifty Edge Servers) would contain their own RTCLOCAL case to replicate the Cardinal Management Shop data.

As the Authoritative Tools have already been installed on the server then the Skype for Business Server Deployment Magician tin can exist constitute in the Start Menu on the local server.  The installation media is no longer required as the installation files have been copied to the server.

• On the Windows Beginning Menu search for 'Deploy' to locate and launch the Skype for Business organization Server Deployment Sorcerer.  From the main menu select Install or Update Skype for Business organisation Server System.
• On Footstep 1: Install Local Configuration Store select Run and go out the default setting of Think the configuration information direct from the Cardinal Management Store and consummate the magician.

Reviewing the results in the execution window should confirm that the second SQL Limited example of RTCLOCAL was installed every bit well as the core SFB Server components.

Checking prerequisite SupportedOSNoDC…prerequisite satisfied.
Checking prerequisite DotNet35…prerequisite satisfied.
Checking prerequisite SupportedSqlRtcLocal…prerequisite satisfied.
Checking prerequisite WMIEnabled…prerequisite satisfied.
Checking prerequisite NoOtherVersionInstalled…prerequisite satisfied.
Checking prerequisite PowerShell…prerequisite satisfied.
Checking prerequisite SqlUpgradeInstanceRtcLocal…prerequisite satisfied.
Installing SQLEXPR_x64.exe(/Q /IACCEPTSQLSERVERLICENSETERMS /UPDATEENABLED=0 /HIDECONSOLE /Activity=Install
/FEATURES=SQLEngine,Tools /INSTANCENAME=RTCLOCAL /TCPENABLED=ane /SQL…

Secondly the Local CMS replica was instantiated by importing the configuration from the existing CMS database an then replicating the database data itself.

Import-CSConfiguration -FileName "C:\Users\ADMINI~1.JDS\AppData\Local\Temp\2\CSConfigData-2015_06_08-13_19_39.null" -Verbose -LocalStore

> Enable local replica service

Enable-CSReplica -Verbose -Confirm:$fake -Report "C:\Users\administrator.JDSKYPE\AppData\Local\Temp\two\Enable-CSReplica-[2015_06_08][13_17_14].html"

Additionally the replication of any certificates stored in the CMS is performed.  Although no certificates have been installed yet for this deployment had there been one and then this action would have replicated any existing OAuthcertificates required for server to server MTLS communications.

> Replicate-CsCmsCertificates

Logging status to: C:\Users\administrator.JDSKYPE\AppData\Local\Temp\2\ReplicateCMSCertificates-[2015_06_08][13_17_14].html

To confirm the installation location of the RTCLOCAL database files on the server check the default SQL Server installation directory for the beingness of the xds files.

%ProgramFiles%\Microsoft SQL Server\MSSQL12.RTCLOCAL\MSSQL\DATA

• On the Skype for Business concern Server Deployment Sorcerer advance to Footstep 2: Setup or Remove Skype for Business Server Components and click Run to get-go the Set Lync server Components wizard.

Once once more the Bootstrapper application will execute and perform a prerequisite cheque before installing additional components.  These include a third SQL instance called LyncLocal and boosted Windows Speech communication components and foreign language packs.

Checking prerequisite KB2858668Installed…prerequisite satisfied.
Installing vcredist_11_x64.exe(/Q)…success
Installing WindowsFabric\v3\WindowsFabric.msi( REBOOT=ReallySuppress STARTUPTYPE=demand REMOVEDATA=yeah IACCEPTEULA=yes TESTMODESKIPPREREQUISITECHECK=yes)…success
Installing MicrosoftIdentityExtensions.msi( REBOOT=ReallySuppress ALLUSERS=ane)…success
Checking prerequisite SqlUpgradeInstanceLyncLocal…prerequisite satisfied.
Installing SQLEXPR_x64.exe(/Q /IACCEPTSQLSERVERLICENSETERMS /UPDATEENABLED=0 /HIDECONSOLE /Activeness=Install
/FEATURES=SQLEngine,Tools /INSTANCENAME=LYNCLOCAL /TCPENABLED=1 /SQL…

Immediately following will be the installation of the Lync server components which make up the different services and roles on the Forepart End server (e.g. AVMCU, Arbitration Server).

Verify that the installation task status was reported as successfully completed.

Create Default Server Certificate

Returning to the server deployment process the adjacent pace is to request and assign server certificates then that the Lync services tin can exist started.

If using an Enterprise Windows CA make certain that before whatever server certificates are requested that the guidance mentioned in the Environment department of the previous article is followed.  In order to properly support PowerPoint file sharing to any Office Web App attendees which are on workstations which are non domain-joined then the default Windows Certificate Authority configuration must be modified.

• Using the guidance covered in either of these two articles launch the Certification Say-so (certsrv.exe) application and under the CA's properties configure the CRL Distribution Betoken (CDP) and Authorisation Information Access (AIA) extensions to include the HTTP paths in whatever certificates issued and signed past this CA.

At this point any new certificate requests will include this disquisitional information in the issued certificate.

• Run Step 3: Request, Install or Assign Certificates and then expand the Default Certificate entry to verify that all roles are checked.  Click Request to offset the Document Request sorcerer.

• Populate the desired information making sure to select the SIP domain to add the sip.<sipdomain> record to the certificate.

The Friendly Proper name tin can be fix to annihilation and is non actually role of the certificate request, it can fifty-fifty exist changed after the certificate is returned and imported.  Note that although Lyncdiscover.<sipdomain> was not defined as an internal DNS record in the previous article the certificate magician still includes this FQDN as a requirement for external support.

• Submit the asking to the online certificate say-so and when the task completes successfully select the View Certificate Details button to validate the certificate status and that a individual key was correctly associated.

• Advance to the next wizard to perform the Certificate Consignment task.  In the event that the role assignment is accidentally lost between the request and assignment wizards and so the assignment chore might fail with an error that a Type has not been provided.  If that occurs simply abolish out of the wizard and return to the main wizard screen.  On the Certificate Magician principal screen If the checkboxes to the left of the Server Default, Spider web Service Internal, and Web Service External roles are no longer selected so reselect them and click Assign.
• Verify that the proper certificate is highlighted (in the event that this server already has any other server certificates installed on it) and so complete the wizard, verifying that the task status is reported equally Completed.

• Dorsum at the Certificate Sorcerer main screen the new document should now be listed on each of the three Default Document roles.

Create OAuth Certificate

Equally this is the first SfB server deployed into the environment then a new OAuth document needs to be created as well.  This is a erstwhile process as this certificate will be shared past any other SfB server which may be later installed.

• On the Certificate Wizard main screen select the OAuthTokenIssuer role and so click Request.

• Enter a descriptive Friendly Name and then submit the certificate request.

• Advance through the assignment wizard to finish the OAuth document configuration in the same mode as performed for the server certificate.

First Services

In previous releases the services could be started directly from the deployment magician as office of Step 4: Get-go Services.  With the addition of a new PowerShell cmdlet in SFB this task is now a manual one.  While SfB Server now includes a new cmdlet chosen Get-go-CsPool this is but intended for use with multiple node Enterprise Edition pools.  When dealing with a single server in a pool or a Standard Edition server every bit in this commodity and so the previous guidance of using the CsWindowsService cmdlets however holds true.

• Launch the Skype for Business organization Server Management Shell and execute the following Start-CsWindowsService cmdlet.

Start-CsWindowsService

To validate the server status the Get-CsWindowsService cmdlet can be issued to list the individual SfB services.

Go-CsWindowsService

Verify Topology

Utilizing the Skype for Business Server 2015 Control Panel the basic functionality of the new deployment can begun to exist tested.

Before opening the Skype for Concern Server 2015 Command Panel, only as with previous Lync Server releases, it is helpful to configure the local server's Internet Options to bypass the the prompt for credentials whenever the tool is launched.

• Open up Internet Options, navigate to the Security tab, select Local Net and click Sites, then click Advanced.
• Enter the local server'due south FQDN as a URL (e.thousand. https://fe.jdskype.net) and then save the changes.

• If Silverlight is not already installed on the server than the Control Panel volition report this fact.

• Use the provided link to immediately download and install Silverlight on the local server.

• Once the installation is complete the Home page of the control panel will exist displayed.  Select the Topology menu and verify that the new server is listed and the Status and Replication fields are healthy.

Summary

With the determination of this article a functional Skype for Business Server should now be deployed and is fix for further configuration.  The next article in the series will cover enabling a test user account and and so progress on with deploying boosted server roles like the Role Web Apps Server.

About Jeff Schertz
Site Administrator

adamspuladogaver.blogspot.com

Source: https://blog.schertz.name/2015/06/sfb2015deploy2/

Share this post