Jude's Blog

Posts Tagged ‘skype for business

Step by Step Guide for Installing Skype for Business Server 2015

with 4 comments

Microsoft is now all set to roll out of Skype for Business Server 2015. The client is officially out and the Public Release for the Skype for Business Server 2015 is set for 1st May 2015. If you are an Office 365 user, not to worry, Skype for Business is being rolled out as we speak. So let’s go ahead and check how the installation is performed. Note that this post focuses on a fresh deployment of S4B Server 2015. If you are looking at an Upgrade, please see my How to Upgrade post here. Before starting, ensure that you have your hardware all ready. To see the hardware requirements, visit here. For this guide, we will be using Windows Server 2012 R2 server.

Prerequisite Installation

  1. Open Windows PowerShell.
  2. Ensure you have Windows Server 2012 R2 Installation Media is inserted.
  3. Run the following command

    Add-WindowsFeature NET-Framework-Core, RSAT-ADDS, Windows-Identity-Foundation, Web-Server, Web-Static-Content, Web-Default-Doc, Web-Http-Errors, Web-Dir-Browsing, 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, Server-Media-Foundation, BITS -Source D:\sources\sxs

  4. Restart server if prompted.

 Note: Ensure that the below Operating System Hot fixes are installed.

Install Skype for Business Server Admin Tools

  1. Insert the Skype for Business Server 2015 installation media.
  2. Navigate and run Setup.exe
  3. On the prompt that asks you to install Visual C++, click Yes.
  4. On the next window, if you want the setup to download and install the latest updates for Skype for Business, click Update. If you do not want to install updates and want to continue with the installation, click on Install.

  1. On the License Agreement page, select I accept the terms in the license agreement and click OK.

  2. Wait till the installation is completed. If you opted to download for Windows Update, the setup will display the below window.

  3. Go to Start Menu
  4. Run ‘Skype for Business Server Deployment Wizard’
  5. On the ‘Deployment Wizard’, click on ‘Install Administrative Tools’.

  1. On the Installation window, click Next to begin installation of the Topology Builder and Control Panel.

  1. On the Completion page, click Finish.

Active Directory Preparation

The concept of the Active Directory preparation is pretty much the same as it was in Lync Server deployments.

  1. Go to Start Menu
  2. Run ‘Skype for Business Server Deployment Wizard’

Prepare AD

  1. Click on ‘Prepare Active Directory’

  1. On the ‘Active Directory Preparation’ page, click Run on the ‘Step 1: Prepare schema’ section

  1. On the ‘Prepare Schema’ wizard, proceed with the setup by clicking Next.

  1. Once the schema preparation is completed, review the log and click Finish to close.

Prepare Forest

  1. On the ‘Active Directory Preparation’ page, click Run on the ‘Step 3: Prepare Current Forest’ section.

  1. On the ‘Prepare Forest’ wizard, select Local domain and enter the local domain of your environment and click Next.

  1. Once the setup is completed review the log and click Finish to close.

Prepare Domain

  1. On the ‘Active Directory Preparation’ page, click Run on the ‘Step 5: Prepare Current Domain’ section.

  1. On the Prepare Domain wizard, click Next.

  1. Once the setup is completed review the log and click Finish to close.

Configure Service Accounts

  1. Log on to the Domain Controller as a member of the Domain Admins group.
  2. Open the Active Directory Users and Computers.
  3. Navigate to Users container and right click on the CSAdministration, select Properties.
  4. On the CSAdministrator Properties window, click the Members tab.
  5. Click Add, On the ‘Enter the object names to select’, Type the user name add to the group CSAdministrators.

  1. Click OK.
  2. Verify and that the Members section includes the added user names and click OK.
  3. Go to the Server that will be used for the Front-End.
  4. Log off and login from the account that was used earlier.
  5. Go to Start Menu and open Skype for Business Server Deployment Wizard.
  6. On the Deployment Wizard, verify that Prepare Active Directory section is marked as Complete.

Configure DNS

  1. Log on to the Domain Controller as a member of the Domain Admins group.
  2. Go to Start and open DNS
  3. On the DNS Manager window, navigate to your domain container under the Forward Lookup Zones.
  4. Right click the domain, select New Host (A or AAAA).

  1. On the New Host window, enter the appropriate FQDN’s and associated IP addresses.
    1. Skype for Business Auto Discover
    2. Internal Web Services FQDN
    3. Pool FQDN
    4. Meeting Simple URL
    5. Dial-in Simple URL
    6. Admin Simple URL
    7. Mobility FQDN

  1. Once completed, click Done to exit.
  2. On the Domain container, right click and select Other New Records

  1. In ‘Select a resource record type’, click ‘Service Location (SRV)’, and click ‘Create Record’
  2. Enter the below values
    1. Service: _sipinternaltls
    2. Protocol: _tcp
    3. Priority: 0
    4. Weight: 0
    5. Port Number: 5061
    6. Host offering this service:

  1. Click OK and click Done to close the window.
  2. Verify DNS entries by using nslookup.

Define Topology

  1. Go to Start Menu
  2. Run Skype for Business Server Topology Builder
  3. In the Topology Builder window, select New Topology and click OK

  1. Provide a name and path to the new Topology
  2. Create New Topology Wizard will open.
  3. On the Define the primary domain page, enter your organizations Primary SIP Domain and click Next.

  1. On the Specify additional supported domains page, enter any other SIP domains that you would like to enable with Skype for Business and click Next.

  1. On the Define the first site page, enter a Name and Description for your deployment and click Next.

  1. On the next page, enter the Site details.

  1. On the New topology was successfully defined page, select the ‘Open the New Front End Wizard when this wizard closes’ option and click Finish.
  2. On the new window, Define the New Front End pool click Next.
  3. Enter the FQDN that will be used to address the Front End pool. Note: If Enterprise Edition is selected the FQDN should be the pool name (ex: pool.domain.name) and if Standard Edition is selected, the FQDN should be the FQDN of the Front End server.

  1. Click Next to proceed.
  2. Enter the FQDN’s of the servers that will be used as Front-End Servers and click Next.

  1. On the Select features page, select the services that you want to associate with the Front End servers. (For this lab, we will only select Conferencing)

  1. Skip the Select collocated server role by clicking Next.

  1. On the Define the SQL server store page click New, you need to provide the information of your SQL server.

  1. On the Define New SQL Store, enter the SQL Server FQDN
  2. Select Default instance. (This will use existing instance from your SQL)
  3. Click OK to close the window.

  1. On the Define the SQL server store page, click Next to proceed.
  2. On the Define the file store page, select Define a new file store.
  3. Enter the FQDN of the computer that will be used as the File Store on the File server FQDN text box.
  4. Enter the Folder Name that is created under the File Share text box and click Next.

  1. On the Specify the Web Services URL page,
    1. select the Override Internal Web Services pool FQDN and enter the Internal URL that will be used to access your Skype for Business Web Services.
    2. Under the External Base URL, enter the public URL that will be used to access Skype for Business web services from internet.

  1. Click Next.
  2. On the Select an Office Web Apps Server page,
    1. Click New to associate a new OWA server.

  1. Enter the FQDN of the Office Web Apps Server and the URL and click OK.

  1. Select Finish to complete the Front End Pool provisioning.

  1. On the Topology Builder, right click the Skype for Business Server on the top left corner, click Edit Properties from the menu.

  1. On the Edit Properties window, navigate to Simple URLs section and enter the Administrative Access URL and click OK.

Publish Topology

  1. On the Skype for Business Server Topology Builder, right click on Skype for Business Server and click on Publish Topology from the menu.

  1. On the Publish the topology page, click Next

  1. On the Select Central Management Server page, select the Front End pool from the drop down list and click Next.

  1. On the Select databases page, select the database you have assigned, click Next.

  1. On the Publishing wizard completion page, review and click Finish to exit.

Deploy Front End

  1. Go to Start and run Skype for Business Server Deployment Wizard
  2. On Deployment Wizard page, click Install or Update Skype for Business Server System.

Install Local Configuration Store

  1. In order to Install the local configuration store for the front end server, Click Run on Step 1: Install Local Configuration Store

  1. On the Configure Local replica of Central Management Store page, select Retrieve directly from the CMS and click Next.

  1. Once the installation is completed, review and click Finish to exit.

Install Front-End services

  1. Back on the Deployment Wizard, Click Run on Step 2: Setup or Remove Skype for Business Server Components. This will install the services that are assigned to the Front End server from the Topology.

  1. On the Set Up Skype for Business Server Components page, proceed with the installation.

  1. Once the setup is completed, review the log for additional information and click Finish to exit.

Assign Certificates

  1. On the Deployment Wizard window, click run under ‘Step 3: Request, Install or Assign Certificates’

  1. This will open the Certificate Wizard, select all the three ticks under Default Certificate section and click Request.

  1. On the Certificate Request window,
    1. Select the CA from the drop down list.
    2. Enter a friendly name
    3. Enter the Organization name and unit
    4. Select the Country and provide other geographical information required
    5. Under the SIP domain list, select the domains that will be used under the certificate.

  1. Click Advanced.
  2. A Certificate Request window will open.
  3. On the Delayed or Immediate Requests page, select ‘Send the request immediately to an online certification authority’ and click Next.

  1. Check the ‘Select a CA in your environment’ option and from the drop down list, select the Certificate Authority in your Active Directory Environment, click Next.

  1. If the Certificate Authority requires alternate credential, select the checkbox and enter the details.

  1. On the Name and Security Settings page, review if the Friendly Name given earlier is present for the certificate. Make sure to select 2048 as the Bit length and to tick the ‘Mark the certificate’s private key as exportable’. Click Next.

  1. On the Configure Additional Subject Alternative Names page, enter new and review the FQDNs listed and click Next. For this lab I will use the Web Services URLs inside the Primary Certificate.

  1. On the Certificate Request Summary page, review all the information and click Next to start the certificate request process.

  1. Select ‘Assign this certificate to Skype for Business Server certificate usages’ from the Online Certificate Request Status page and click Finish.

  1. A new window will open. Click Next.

  1. On the Certificate Assignment Summary page, review the certificate information and click Next.

  1. Once the execution is completed, review the status using view log and clock Finish to exit.

  1. To request and assign a certificate for the OAuthTokenIssuer repeat the process under the Certificate Wizard.
  2. Once completed your Certificate Wizard should be completed.

Start Services

Now we have completed the installation and assigned certificates and has come to the point of starting up Lync services for this server. You can do a server restart where at this point which will make all the services run Automatically. But if you want to start the services manually follow the below steps.

  1. Go to Start.
  2. Open Skype for Business Server Management Shell

  1. Type the below command and press enter

    To start the entire Front End Pool     – Start-CsPool

    To start only a single Front End Server     – Start-CsWindowsService

  2. Once the startup is completed navigate to Windows Services MMC and verify that all Skype for Business Server Services are in a Running Status.

  1. Now go to Start, open Skype for Business Server 2015 Control Panel. (Ensure Silverlight is installed)

Now you can perform enabling users and perform other configuration tasks.

    Please note that the above information is provided “AS IS” with no warranties, and confers no rights. The content may be changed as and when the finalized information is been publicly announced by Microsoft.

Advertisements

In Place Upgrade Skype for Business Server 2015 Step by Step

with 15 comments


Introduction

The below section describes a step-by-step guide for upgrading a Microsoft Lync Server 2013 to Microsoft® Skype for Business Server 2015. Unlike previous versions of Lync, Skype for Business now supports in-place upgrading. Meaning that you can use your existing Lync Server 2013 hardware to be used for Skype for Business. Read more here.

The installation considers a single server environment with a Lync Server 2013 with the basic roles collocated. Additional details of the topology and architecture of the lab environment which was used in the installation is described here;

Domain Controller
Operating System Windows Server 2012 R2
Forest func Level Windows Server 2012 R2
Domain func Level Windows Server 2012 R2
Lync Server 2013
Operating System Windows Server 2012 R2
Server Edition Lync 2013 Standard Edition

Note: The in-place upgrade requires all Lync Server 2013 services to be stopped. Therefore a mandatory user downtime will be required for an approx. of 60-90 minutes (may vary). So as a best practice;

  1. Choose a weekend for your upgrade.
  2. Notify all users of the downtime.
  3. Take backups.
  4. Get some pop-corn, a movie and a Red Bull.

The upgrade process for S4B is quite easy and features 5 steps;

  1. Prepare Environment and Install prerequisites
  2. Upgrade, Publish Topology and upgrade databases using Topology Builder.
  3. Stop all Lync Server 2013 services.
  4. Perform in-place upgrade.
  5. Start Services, verify and Go home!

Prepare Environment and Install prerequisites

Ensure that your Lync Server 2013 server has the latest patches. Download and install following hotfixes, patches;

  • Install CU5+ latest hotfix to Lync 2013 topology
  • PowerShell RTM version (6.2.9200.0) or later
  • Have at least SQL server 2012 SP1 installed*
  • Operating System Hotfixes:

*Lync Server 2013 comes with and installs SQL server 2012 express natively. However you may need to update your SQL express with the SP1 or later.

Note: In case you missed any S4B prerequisites, fear not. The Upgrade wizard will check and ask you do get the requirements installed and you can resume the setup.

Upgrade, Publish Topology and upgrade databases using Topology Builder

Note: It is required that the Skype for Business Topology Builder installation should be performed on a server or a workstation that has not been configured with any Lync Server 2013 components. For the demonstration of the lab, a Windows 8.1 workstation will be used.

  1. On a Server/Computer that has no Lync Server roles deployed, insert the Skype for Business installation media.
  2. Navigate to X:\Setup\amd64\ and run Setup.exe
  3. On the installation page, select the Update option and click Install.


  1. On the End User License Agreement page, select the I accept term and click OK.


  1. The Setup will install the core components.



  1. Once the installation is completed, click Finish to exit the wizard.


  1. Click Start, search and run Skype for Business Server 2015 Topology Builder.


  1. On the Topology Builder window, select Download Topology from existing deployment and click OK. This will download the existing Lync 2013 topology.


  1. Save the topology to a preferred location.
  2. On the Topology Builder, expand and navigate to Skype for Business Server > Lync Server 2013 > Standard Edition Front End Servers. (This is your existing front end pool)


  1. Right click on the FQDN of the Lync 2013 under the Standard Edition Front End Servers section and click on Upgrade to Skype for Business Server 2015.


  1. On the confirmation window, click Yes. (Please note that this step is not reversible)


  1. Once completed, note that your existing Lync 2013 Front End server(s) will be moved and listed under the Topology Builders’ Skype for Business Server 2015 section.


  1. On the topology builder, right click on the Skype for Business Server and select Publish Topology.


  1. On the Publish Topology window, click on Next.


  1. On the Select databases page, select the database that will be used to publish the topology and click Next.


  1. Now the new topology will be published.


  1. Once the wizard is completed, verify that the status of all steps are Successful. Click next to exit.


Stop Lync Server 2013 services

Now that the Lync topology is marked as ‘To be upgraded’, we will be shutting down all Lync services running on all Front End servers within the pool. Note that during this time users will be affected with a downtime. If you do not wish to have a downtime, you can move the users to a different pool as a temporary measure.

  1. Navigate to a Lync Server 2013 server.
  2. Open the Lync Server Management Shell.
  3. Type the below command and press enter. This will stop all Lync 2013 services on the server.

    Disable-CsComputer -Scorch


Perform In-place Upgrade

Now that we have stopped all Lync 2013 pool services in all the front end servers, we will move with the in-place upgrade of Skype for Business Server 2015.

  1. Navigate to the Lync 2013 Front End server.
  2. Locate the installation media on your computer, and then double-click \Setup\amd64\Setup.exe
  3. Microsoft Visual C++ setup will be installed.


  1. Once completed, the Skype for Business Upgrade Setup wizard will be loaded.
  2. You can choose an option to whether to install any updates at this stage or install them later. Click Next to proceed.


  1. On the License Agreement page, accept and click OK.
  2. Now a new window will be loaded that will give a real time status of your in-place upgrade.


  1. Each performed task and relevant information will be displayed on the lower part of the window.


  1. Skype for Business will now perform the upgrade process as shown in the upgrade window.


  1. If any prerequisites is missing, the installation will prompt for the missing bits. Install the missing bits and you can continue from Step 2 where the setup will resume from where it left off.
  2. Once the upgrade process is completed, ensure all tasks have been executed successfully and click on OK.


  1. On the Next Steps page, review and click OK.


Start Services

Prior to starting the services of your Front End Servers/Pool ensure that all servers within the selected pool is successful with the In-Place upgrade setup. Once this term is ensured, the following command will be run on a single Front End server that will start Skype for Business services on all the services within the pool

  1. Navigate to Skype for Business PowerShell console.
  2. Start all Skype for Business services on the server by running the following command.

    Start-CsPool

Now it’s time to test and verify that all services are up and running. You can use the Event viewer and Logs to collect information for any warnings and errors.

Keep calm and Skype on!!!

Note:Please note that the above information is pre-release content, therefore provided “AS IS” with no warranties, and confers no rights. The content may be changed as and when the finalized information is been publicly announced by Microsoft.

From Lync to Skype for Business, Upgrade or Migrate.

with one comment

[Update] – Upgrade to Skype for Business 2015 Step by Step Guide.

If you are on Lync 2013, Kudos! Microsoft’s V.Next UC line up, already named as ‘Skype for Business’ deployment now features an In-place upgrade path!

Lync Server 2013, compared to Lync Server 2010 had many architectural and backend differences. This led all Lync 2010 admins with only one option, go for a Migration; provision brand new servers, deploy Lync 2013 servers side by side, enable interoperability between the new Lync 2013 and Lync 2010 in a coexisting environment.

Untitled

The major downside here was the fact that you need to have new hardware provisioned, and that came with a cost! Larger your environment, less likely your budget will get approved. Worst case, you are going to end up with lot of un-used hardware as well after decommissioning the 2010 environment. However, the features and benefits of Lync 2013 always went way higher comparing the cost.

Lync vNext, Skype for Business now supports In-Place Upgrade. Meaning, if you have a Lync Server 2013 environment, you can use the existing hardware to upgrade into Skype for Business 2015. The in-place upgrade also ensures that your environment goes through a smoother upgrade process with minimum effort.

Ok so life’s good for everyone with Lync 2013, but what about Lync 2010? Let’s see what options you have in terms of moving from Lync to S4B.

Existing Environment In place upgrade supported? Migration supported? Service/User downtime required?
Lync 2010 No Yes No
Lync 2013 Yes Yes Required for in-place upgrade scenario
Lync 2013 + 2010 coexisting Yes, Lync 2013 to S4B upgrade (Step 02) Yes, Lync 2010 > 2013 migration (Step 01) Required for in-place upgrade scenario

Lync to S4B transition can be performed in two ways;

  • Migrate users mode (no downtime for users) – Users will be moved across pools or 2010/2013 to S4B pool while keeping all services running and therefore no downtime or impact for users.
  • Offline mode (downtime required for users) – In scenarios where am in-place upgrade is to be performed, the services on the server that will be upgraded needs to be stopped and therefore user downtime will be required until upgrade is completed.

 

 

 

Please note that the above information is provided “AS IS” with no warranties, and confers no rights. The content may be changed as and when the finalized information is been publically announced by Microsoft.

Written by judeperera

March 11, 2015 at 3:50 am

How to switch between Skype for Business and Lync Client UI

with 8 comments

We are all going to get a new client for Lync and it is going to look a lot more like Skype. But here’s an interesting thing. With this new client, named “Skype for Business Client” now you or in many instances the administrator of your organization has the ability to change the UI of the client, either to;

  • Skype for Business Client
  • Lync 2013 Client

This new Dual User Experience mode that controls the Lync/Skype UI is managed via in-band settings. The client is by default configured to check for the Server Version of the environment and set up the looks. The below table lists what you may see by default.

Server Version Default Client UI
Skype for Business on-prem Skype for Business
Skype for Business Online Skype for Business
Lync Server 2013 Lync 2013
Lync Server 2010 Lync 2013

 

Although this is the case, the Lync/S4B administrator always have the option to change the UI via changing in-band policy settings that will manually override the default UI. There will be a Client Policy parameter that will determine the default UI for users within the organization. To enable the Skype UI and Lync 2013 UI the following commands can be run from the server end respectively.

Set-CSClientPolicy -EnableSkypeUI: true

Or

Set-CSClientPolicy -EnableSkypeUI: false

So what happens from the users end? Head over to REGEDIT, Navigate to

HKEY_CURRENT_USER\Software\Microsoft\Office\Lync

and notice the value for EnableSkypeUI;

  • 00 00 00 01 – Skype for Business UI
  • 00 00 00 00 – Lync 2013 UI

 

However, there’s a catch. Based on the UI that you choose to have, the features may vary as show below.

Feature Skype UI Lync UI
First Run Experience Yes No
New Emoticons Yes Yes
Call and Video Monitor Yes No
Call via Work Yes No
RCC No Yes
Rate my call Yes Yes
Server side conversation history Yes Yes
Skype-Lync Video Interop Yes Yes

 

d

 

 

Update: Amanda Debler has written a nice piece of code that will help you to get the UI switched in seconds, you can grab the powershell script here.

Please note that the above information is provided “AS IS” with no warranties, and confers no rights. The content may be changed as and when the finalized information is been publically announced by Microsoft.

Written by judeperera

March 10, 2015 at 9:25 am

Skype for Business Server 2015 – Hardware/Software Requirements

leave a comment »

Hardware recommended for servers

Skype for Business Server supports the same hardware as Lync Server 2013

Hardware Component Recommended
CPU 64-bit dual processor, hex-core, 2.26 gigahertz (GHz) or higher.Intel Itanium processors are not supported for Skype for Business Server server roles.
Memory 32 GB
Disk 8 or more 10,000 RPM hard disk drives with at least 72 GB free disk space.-Two of the disks should use RAID 1, and six should use RAID 10.OR-Solid state drives (SSDs) which provide performance similar to 8 10,000-RPM mechanical disk drives.
Network 1 dual-port network adapter, 1 Gbps or faster (2 recommended, which requires teaming with a single MAC address and single IP address).

Operating System Support

Standard/Enterprise Edition or Datacenter Edition can use any of the following:

  • Windows Server 2008 R2 SP1 or latest service pack
  • Windows Server 2012
  • Windows Server 2012 R2

Note: Unlike the predecessors of the Lync family, the underlying Operating System will be playing a key role for Skype for Business Server 2015. This is due to the underlying architecture of the Lync High Availability in an Enterprise environment is based on Windows Fabric component, which is part of the Windows Server Operating System.

Operating System Default Windows Fabric version
Windows Server 2012 R2 Windows Fabric v3
Windows Server 2012 Windows Fabric v3
Windows Server 2008 R2* Windows Fabric v3
Windows Server vNext

*You should only be using Windows Server 2008 R2 when you have existing servers with Lync Server 2013 already installed, and you’re intending to do an in-place upgrade of them.

Therefore, Recommended Operating System: Windows Server 2012 R2

Additional software requirements

Prerequisites

  • Lync Server 2013 CU5+ or latest hotfix if Upgrading from Lync Server 2013
  • Powershell v 6.2.9200.0 or later
  • SQL Server 2012 SP1 for Enterprise Edition
  • Following Operating System hotfixes
    • Windows Server 2008 R2  – KB2633623
    • Windows Server 2012 – KB2858668
    • Windows Server 2012 R2 – KB2982006

Standard Edition server database

  • Microsoft SQL Express 2014 (bundled in the FE server(s))

Back-end database of a Front End pool, Archiving database, Monitoring database, persistent chat database, and persistent chat compliance database

  • Microsoft SQL Server 2008 R2
  • Microsoft SQL Server 2012
  • Microsoft SQL Server 2014

Database High Availability Support

  • SQL Mirroring
  • SQL Clustering
  • SQL Always On Availability Groups*
  • Synchronous Writes to Back End*

*New features

Please note that the above information is provided “AS IS” with no warranties, and confers no rights. The content may be changed as and when the finalized information is been publically announced by Microsoft.

Written by judeperera

March 7, 2015 at 7:17 pm