Migrate from Lync 2010 to Skype for Business Server 2015

For my environment I will be using a single Standard Edition Front End Server. The recommended hardware Requirements are as follows:

CPU – 64-bit dual processor, hex-core, 2.26 gigahertz (GHz) or higher
Memory – 32 gigabytes (GB)
Disk – At least 72GB
Network: 1 dual-port network adapter, 1 Gbps or higher (2 network adapters can be used, but they need to be teamed with a single MAC address and a single IP address).

To begin with I will go with half the recommendations as in my experience they always over egg these things! Our environment is quite small and we can always up the resources later.


    1.  Create NIC Team: http://blogs.technet.com/b/kevinholman/archive/2012/06/02/windows-server-2012-creating-a-nic-team-for-load-balancing-and-failover.aspx
    2.  Check for Windows Updates
    3. Install server roles:
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

4. Create a File Share on the server. Add the local Administrators group on the server hosting the file share, grant Allow: Full Control, Change, and Read rights, and then click Share.


5. Install Administrative tools from SFB Iso.

sfb iso

Once you have completed the updates and license agreement click “Install Administrative Tools”

admin tools

6. Click prepare Active Directory

Follow each step one by one.


prepare ad

7. Create DNS records – The existing Lync 2010 DNS records should be sufficient for the deployment. The traffic will be redirected through the 2010 server to SFB. The Web Scheduler Simple URL is a new record which does not exist in previous versions. We need to add this:

scheduler.domain.local  A record


8. Create and publish new topology

Click “Prepare first Standard Edition Server”

prepare first server

Once complete open Topology Builder and select “Download Topology from Existing Environment”

New Front End Pool

Expand Skype for Business Server 2015 and Right click Standard Edition Front End Servers then New Front End Pool.

define pool

Select the features you wish to use:


For my deployment I am choosing to Collocate the Mediation Server.


On the next page, ensure you UN-check Enable an Edge Pool

edge pool uncheck

Click next for “Define SQL Store”

Select Use previously defined file share and select the share you created earlier

Skype Share

Define Web Services URL:

web services url

I don’t have an Office Web Apps Server yet. We can add this later. Click finish.

web apps server

Go back to Topology builder and right click your Standard Edition Front End server and go properties.


Scroll down to Associate Edge pool and select the 2010 server.


Go to Action/ Publish to commit the changes. Click Next


9. Install Skype for Business Server System

Run the deployment wizard and click “Install or Update Skype for Business Server System”

Follow each step one by one

Step 1: Install the local configuration Store

Install the following KB before completing the next step: https://support.microsoft.com/en-us/kb/2982006

Step 2: Setup or Remove Skype for Business Server Components

Step 3: Request, Install or Assign Certificates

Step 4: Start Services

Right click SKB Management Shell and click “Run as Administrator”

from the PowerShell prompt execute:


Step 5: Enable Microsoft Update

10. Verify the Topology

For my tests I’m going to move a test user from 2010 to SFB and verify functionality.

Step 1: Open SFB Server 2015 Control Panel and go to Users. Search for a user you want to move


Go to Action / Move selected users to pool…

Change the Destination registrar pool to the FE on the new server


Test IM between users, calls and any other functionality you like to use.

Next Steps:

Migrate 2010 Edge Server
Deploy Archive Monitoring Role

Give users permission to call on behalf of a Response Group

Now you may get a request to allow users to call from response group in Lync. I did a bit of research on this and according to Microsoft it is possible, but I have found it doesn’t work by default.


The reason it doesn’t work is that by default response groups do not have any voice policy. Voice Policies determine if a user is allowed to call or not. To apply the policy we need to do a bit of Powershell!

1. Open Lync control panel/Response Groups/Group and go into the group to add any users you want to give access to.

2. Click on the “Workflow” tab then “Create or edit a workflow”.

3. Edit the workflow and make sure that “Enable Agent Anonymity” is checked (you can’t call from a response group without this).

agent anon

4. Open Lync Management Shell on your client machine or Lync Server and run the following command to get a list of response groups:


5. Then you can run this to find out what the voice policy of a specific group is:

Get-CsApplicationEndpoint -Identity “Response Group Name” | Format-List -Property VoicePolicy

This should return back that no voice policy is assigned.


6. We now need to give the response group a policy.

Get-CsApplicationEndpoint -Identity “Response Group Name” | Grant-CsVoicePolicy -PolicyName “Voice Policy Name”

7. Now check the policy was applied:

Get-CsApplicationEndpoint -Identity “Response Group Name” | Format-List -Property VoicePolicy


We should now have the permission to call on behalf of a response group. To test open Lync client and right click a user to see the call options:

lync client