Controlling the Client Experience with Skype for Business Microsoft Corporation Scott Stubberfield Nick Smith Version 1.2

Overview What is changing Required customer actions Lync 2013 will become Skype for Business after April 14, 2015 as part of regular Office monthly updates You will be able to control the experience via client policies and first run client registry values to choose which user interface a user will see This presentation provides detailed configuration steps required in all scenarios Required customer actions Determine your client experience requirements and the associated configuration steps that are needed to achieve those requirements Implement the necessary configuration steps in advance of client updates being deployed Leverage the Adoption and Awareness materials to reduce the impact of the UI switch

How to leverage this presentation Default Client Experiences Review the expected default client experiences of a Skype for Business client build 4711.1002 (or later) when connected to different user registrars The table assumes that no client policies have been set and that no first run experience changes have been made Desired Client Experiences If the expected experiences do not meet your requirements then proceed to the desired client experiences slide to determine what configuration changes you require Choose your target registrar version from the first column and then follow along to the desired client experience column to determine what configuration changes you require Click on the icon under the configuration steps column to see the details for that scenario

Definitions Client Policies First Launch Client Behaviors Configuration settings that can be controlled a Skype for Business or Lync administrator Used to control which user interface (UI) will be displayed when a user signs in using a Skype for Business client build 4711.1002 (or later) Specific server builds are required on Lync Server 2013 and Lync Server 2010 in order to set client policies First Launch Client Behaviors Initial client experience a user will have when the client starts up for the first time after a Skype for Business client build 4711.1002 (or later) has been installed on their computer This experience is controlled by a registry key or GPO Skype for Business Welcome A seven step tutorial that is shown to the end user the first time that the client is run in Skype for Business mode

Client Experiences Skype for Business UI Lync UI The Skype for Business UI is the new interface that is available when Skype for Business client build 4711.1002 (or later) has been installed This UI is a fresh new interface with simplified controls and some great new additions The interface will be familiar to users of Lync 2013 as well as regular users of the consumer version of Skype Lync UI The Lync UI is an alternative interface that is available when Skype for Business client build 4711.1002 (or later) has been installed This UI is the same interface that was present in the previous Lync 2013 client Lync UI (Skype for Business UI on first run) The Lync UI (Skype for Business UI on first run) occurs when a user signs in for the first time using Skype for Business client build 4711.1002 (or later) and the Skype for Business UI is shown and followed by an immediate request to switch to the Lync UI

Default Client Experiences This table shows the expected default client experiences of a Skype for Business client build 4711.1002 (or later) when connected to different user registrars The table assumes that no client policies have been set and that no first run experience changes have been made Review the expected experiences below and if they do not meet your desired experiences then proceed to the next slide to determine what configuration changes you require User Registrar Client Experience Skype for Business / Lync Online Skype for Business UI Skype for Business Server 2015 Lync Server 2013 Lync UI (Skype for Business UI on first run) Lync Server 2010

Desired Client Experiences Skype for Business UI Lync UI Skype for Business / Lync Online Skype for Business Server 2015 Lync Server 2013 Lync Server 2010 Note: Click on the icon under the desired client experience to see the configuration details for that scenario. Clicking on the client experience title will take you to details on what that experience looks like. Client experience showing Lync UI switching to Skype for Business UI can be found here Client experience showing Skype for Business UI switching to Lync UI can be found here

Skype for Business UI Previous Slide Step 2 Lync 2013 updated to Skype for Business Step 4 Skype for Business welcome screen is shown Step 1 Running Lync 2013 Step 3 Client starts in Skype for Business UI Previous Slide

Client starts in Lync UI Step 2 Lync 2013 updated to Skype for Business Step 1 Running Lync 2013 Step 3 Client starts in Lync UI Previous Slide

Lync UI (Skype for Business UI on first run) Step 2 Lync 2013 updated to Skype for Business Step 4 Skype for Business welcome screen is shown Step 5 Client is prompted to restart to switch to Lync UI Step 1 Running Lync 2013 Step 3 Client starts in Skype for Business UI Step 6 Client starts in Lync UI Previous Slide

Lync UI switch to Skype for Business UI Step 2 Client is prompted to restart to switch to Skype for Business UI Note: This prompt to switch will only be shown after the client has restarted once after the change in policy. Step 1 Running Lync UI Step 3 Client starts in Lync UI Previous Slide

Skype for Business UI switch to Lync UI Step 2 Client is prompted to restart to switch to Lync UI Note: This prompt to switch will only be shown after the client has restarted once after the change in policy. Step 1 Running Skype for Business Step 3 Client starts in Lync UI Previous Slide

Skype for Business UI – Skype for Business / Lync Online Step 1 – Deploy client build 4711.1002 (April, 2015) or later Note: You do not need to deploy client policies in this scenario to achieve the desired UI. Previous Slide

Skype for Business UI – Skype for Business Server 2015 Step 1 – Deploy client build 4711.1002 (April, 2015) or later Note: You do not need to deploy client policies in this scenario to achieve the desired UI. Previous Slide

Skype for Business UI – Lync Server 2013 Step 1 – Deploy server build 5.0.8308.857 (December, 2014) or later Step 2 – Complete configuration of any of the 3 following scenarios Step 3 – Deploy client build 4711.1002 (April, 2015) or later Scenario 1 – Skype for Business UI via Global Policy set-csclientpolicy -EnableSkypeUI $true Scenario 2 – Skype for Business UI via new client policy instance new-CsClientPolicy -Identity EnableSkypeUI -EnableSkypeUI $true grant-csclientpolicy user1@contoso.com -PolicyName EnableSkypeUI Scenario 1 – Set Skype for Business UI for all users via Global Policy Scenario 2 – Create a new client policy instance, set Skype for Business UI = $true and assign to a user Scenario 3 – Update existing client policy instance, set Skype for Business UI = $true Note: Depending on your specific scenario you may end up configuring one, two or even all three of the scenarios described here. Scenario 3 – Skype for Business UI via existing client policy instance Set-csclientpolicy ExistingClientPolicy -EnableSkypeUI $true Previous Slide Note: It is not possible to enable the Skype for Business UI for users that are registered to Lync 2010 and Lync 2013 servers that do not meet the minimum required patch levels. Details on downloading server updates can be found here.

Skype for Business UI – Lync Server 2010 Step 1 – Deploy server build 4.0.7577.710 (February, 2015) or later Step 2 – Complete configuration of any of the 3 following scenarios Step 3 – Deploy client build 4711.1002 (April, 2015) or later Scenario 1 – Skype for Business UI via Global Policy set-csclientpolicy -EnableSkypeUI $true Scenario 2 – Skype for Business UI via new client policy instance new-CsClientPolicy -Identity EnableSkypeUI -EnableSkypeUI $true grant-csclientpolicy user1@contoso.com -PolicyName EnableSkypeUI Scenario 1 – Set Skype for Business UI for all users via Global Policy Scenario 2 – Create a new client policy instance, set Skype for Business UI = $true and assign to a user Scenario 3 – Update existing client policy instance, set Skype for Business UI = $true Note: Depending on your specific scenario you may end up configuring one, two or even all three of the scenarios described here. Scenario 3 – Skype for Business UI via existing client policy instance Set-csclientpolicy ExistingClientPolicy -EnableSkypeUI $true Previous Slide Note: It is not possible to enable the Skype for Business UI for users that are registered to Lync 2010 and Lync 2013 servers that do not meet the minimum required patch levels. Details on downloading server updates can be found here.

Lync UI – Skype for Business / Lync Online Step 1 – Complete configuration of any of the 3 following scenarios Step 2 - Set "EnableSkypeUi"=hex:00,00,00,00 via registry or GPO Step 3 – Deploy client build 4711.1002 (April, 2015) or later Scenario 1 – Lync UI via Global Policy grant-csclientpolicy –PolicyName ClientPolicyDisableSkypeUI Scenario 2 – Lync UI via client policy instance grant-csclientpolicy user1@contoso.com -PolicyName ClientPolicyDisableSkypeUI Scenario 3 – Lync UI via existing custom client policy instance grant-csclientpolicy user1@contoso.com -PolicyName ClientPolicyNoIMURLDisableSkypeUI Scenario 1 – Set Skype for Business UI for all users via Global Policy Scenario 2 – Grant client policy instance to a specific user Scenario 3 – If you have currently assigned an existing custom client policy instance to a user you can grant them the equivalent custom policy instance that has the value of EnableSkypeUI set to $False (See Appendix A – Online custom policies) Note: Depending on your specific scenario you may end up configuring one or both of the scenarios described here. Previous Slide Note: If you do not complete Step 2 of this configuration the client experience will be as shown on the slide Lync UI (Skype for Business on first run). Note: Any existing custom policy can be used in Scenario 3 – See Appendix A – Online custom policies for the full list.

Lync UI - Skype for Business Server 2015 Step 1 – Deploy Skype for Business Server 2015 Step 2 – Complete configuration of any of the 3 following scenarios Scenario 1 – Lync UI via Global Policy set-csclientpolicy -EnableSkypeUI $false Scenario 2 – Lync UI via new client policy instance new-CsClientPolicy -Identity DisableSkypeUI -EnableSkypeUI $false grant-csclientpolicy user1@contoso.com -PolicyName DisableSkypeUI Scenario 3 – Lync UI via existing client policy instance Scenario 1 – Set Skype for Business UI for all users via Global Policy Scenario 2 – Create a new client policy instance, set Skype for Business UI = $true and assign to a user Scenario 3 – Update existing client policy instance, set Skype for Business UI = $true Note: Depending on your specific scenario you may end up configuring one, two or even all three of the scenarios described here. The link provided for configuring the registry or GPO value here points to Lync Server 2013. The Skype for Business Server links have not yet been published however the information on configuring the registry/GPO is the same. Set-csclientpolicy ExistingClientPolicy -EnableSkypeUI $false Step 3 - Set "EnableSkypeUi"=hex:00,00,00,00 via registry or GPO Step 4 – Deploy client build 4711.1002 (April, 2015) or later Previous Slide Note: If you do not complete Step 3 of this configuration the client experience will be as shown on the slide Lync UI (Skype for Business on first run).

Lync UI – Lync Server 2013 Step 1 - Set "EnableSkypeUi"=hex:00,00,00,00 via registry or GPO Step 2 – Deploy client build 4711.1002 (April, 2015) or later Notes: You do not need to deploy client policies in this scenario to achieve the desired UI. If you do not complete Step 1 of this configuration the client experience will be as shown on the slide Lync UI (Skype for Business on first run). Scenario 1 – Set Skype for Business UI for all users via Global Policy Scenario 2 – Create a new client policy instance, set Skype for Business UI = $true and assign to a user Scenario 3 – Update existing client policy instance, set Skype for Business UI = $true Note: Depending on your specific scenario you may end up configuring one, two or even all three of the scenarios described here. Previous Slide

Lync UI – Lync Server 2010 Step 1 - Set "EnableSkypeUi"=hex:00,00,00,00 via registry or GPO Step 2 – Deploy client build 4711.1002 (April, 2015) or later Notes: You do not need to deploy client policies in this scenario to achieve the desired UI. If you do not complete Step 1 of this configuration the client experience will be as shown on the slide Lync UI (Skype for Business on first run). Scenario 1 – Set Skype for Business UI for all users via Global Policy Scenario 2 – Create a new client policy instance, set Skype for Business UI = $true and assign to a user Scenario 3 – Update existing client policy instance, set Skype for Business UI = $true Note: Depending on your specific scenario you may end up configuring one, two or even all three of the scenarios described here. Previous Slide

Additional Content Lync/Skype for Business Online - Switching between the Skype for Business and the Lync client user interfaces https://support.office.com/en-us/article/Switching-between-the-Skype-for-Business-and-the-Lync-client-user-interfaces-a2394a4c-7522-484c-a047-7b3289742be0?omkt=en-us&ui=en-US&rs=en-US&ad=US Lync Server 2013 - Configure the client experience http://go.microsoft.com/fwlink/?LinkId=532732 Lync Server 2010 - Configure the client experience http://go.microsoft.com/fwlink/?LinkId=532733   Lync is now Skype for Business — see what's new https://support.office.com/en-us/article/Lync-is-now-Skype-for-Business-%e2%80%94-see-whats-new-aba02d7e-c801-4a82-bccd-e7207240f612?ui=en-US&rs=en-US&ad=US Skype for Business change management and adoption https://support.office.com/en-us/article/Skype-for-Business-change-management-and-adoption-d8d85da6-52e7-4819-8451-45c103fb5ccb?omkt=en-us&ui=en-US&rs=en-US&ad=US

Advanced Scenarios

Desired Client UI Matrix Client Configurations Options Required Desired Client UI Lync Server 2010 Lync Server 2013 Skype for Business 2015 Skype for Business Online Configuration Steps Client Experience CP FR Default Behavior N/A Lync UI (Skype for Business UI on first run) Skype for Business UI FR Not Achievable Lync UI CP Lync UI (Skype for Business on first run) Note: In the table above there are a few cells marked as not achievable. What this means is that the desired UI is not available for that specific server version when only using the first run registry values. For example we have marked Lync UI/Skype for Business online cell as Not Achievable. The reason for this is that if you configure the first run key to show the Lync UI and then sign in to a Skype for Business Online server your client will want to switch to the Skype for Business UI. When the user clicks on restart now the client will restart in the Skype for Business UI and will override the first run key that was set. There is no way to override this behavior therefore this particular configuration is not achievable. CP – Client Policy values configured– must be at latest server patch level to configure these policies FR – First run values configured– requires PC level configuration Client experience showing Lync UI switching to Skype for Business UI can be found here Client experience showing Skype for Business UI switching to Lync UI can be found here Note: Click on the icon under the configuration steps column to see the th details for that scenario

Lync UI (Skype for Business on first run) – Lync Server 2010 Step 1 – Deploy client build 4711.1002 (April, 2015) or later Notes: You do not need to deploy client policies in this scenario to achieve the desired UI. Previous Slide

Lync UI (Skype for Business on first run) – Lync Server 2013 Step 1 – Deploy client build 4711.1002 (April, 2015) or later Notes: You do not need to deploy client policies in this scenario to achieve the desired UI. Previous Slide

Step 1 – Deploy Skype for Business Server 2015 Lync UI (Skype for Business on first run) – Skype for Business Server 2015 Step 1 – Deploy Skype for Business Server 2015 Step 2 – Complete configuration of any of the 3 following scenarios Step 3 – Deploy client build 4711.1002 (April, 2015) or later Scenario 1 – Lync UI via Global Policy set-csclientpolicy -EnableSkypeUI $false Scenario 2 – Lync UI via new client policy instance new-CsClientPolicy -Identity DisableSkypeUI -EnableSkypeUI $false grant-csclientpolicy user1@contoso.com -PolicyName DisableSkypeUI Scenario 1 – Set Skype for Business UI for all users via Global Policy Scenario 2 – Create a new client policy instance, set Skype for Business UI = $true and assign to a user Scenario 3 – Update existing client policy instance, set Skype for Business UI = $true Note: Depending on your specific scenario you may end up configuring one, two or even all three of the scenarios described here. Scenario 3 – Lync UI via existing client policy instance Set-csclientpolicy ExistingClientPolicy -EnableSkypeUI $false Previous Slide

Lync UI (Skype for Business on first run) – Skype for Business Online Step 1 – Complete configuration of any of the 3 following scenarios Step 2 – Deploy client build 4711.1002 (April, 2015) or later Scenario 1 – Lync UI via Global Policy grant-csclientpolicy –PolicyName ClientPolicyDisableSkypeUI Scenario 2 – Lync UI via client policy instance grant-csclientpolicy user1@contoso.com -PolicyName ClientPolicyDisableSkypeUI Scenario 3 – Lync UI via existing custom client policy instance grant-csclientpolicy user1@contoso.com -PolicyName ClientPolicyNoIMURLDisableSkypeUI Scenario 1 – Set Skype for Business UI for all users via Global Policy Scenario 2 – Grant client policy instance to a specific user Scenario 3 – If you have currently assigned an existing custom client policy instance to a user you can grant them the equivalent custom policy instance that has the value of EnableSkypeUI set to $False (See Appendix A – Online custom policies) Note: Depending on your specific scenario you may end up configuring one or both of the scenarios described here. Previous Slide Note: Any existing custom policy can be used in Scenario 3 – See Appendix A – Online custom policies for the full list.

Appendix A – Online custom policies This table shows the existing Skype for Business/Lync online policies and the equivalent policy name that can be used to show the Lync UI. Any policy that has a value of False for EnableSkypeUI can be use to set the Lync UI. Identity EnableSkypeUI Tag:ClientPolicyDefaultPhoto   Tag:ClientPolicyDefaultPhotoDisableSkypeUI FALSE Tag:ClientPolicyNoIMURL Tag:ClientPolicyNoIMURLDisableSkypeUI Tag:ClientPolicyNoIMURLPhoto Tag:ClientPolicyNoIMURLPhotoDisableSkypeUI Tag:ClientPolicyNoSaveIMNoArchiving Tag:ClientPolicyNoSaveIMNoArchivingDisableSkypeUI Tag:ClientPolicyNoSaveIMNoArchivingNoIMURL Tag:ClientPolicyNoSaveIMNoArchivingNoIMURLDisableSkypeUI Tag:ClientPolicyNoSaveIMNoArchivingNoIMURLPhoto Tag:ClientPolicyNoSaveIMNoArchivingNoIMURLPhotoDisableSkypeUI Tag:ClientPolicyNoSaveIMNoArchivingPhoto Tag:ClientPolicyNoSaveIMNoArchivingPhotoDisableSkypeUI

Appendix B - Version Control Initial release on 4/10/2015 Version 1.1 Updated release on 4/13/2015 note added to client UI experience regarding when prompt will appear Version 1.2 additional Lync Online custom policy options

Appendix C – Verifying policy changes You can verify that a user has received the policy change by following the instructions below. During initial sign in you should see a SUBSCRIBE message sent with the following line: Accept: application/vnd-microsoft-roaming-provisioning-v2+xml The server will respond with a SIP/2.0 200 OK message with the following line: Content-Type: application/vnd-microsoft-roaming-provisioning-v2+xml If you look at the SDP content of this message you will see a grouping for <provisionGroup name="endpointConfiguration" > In this group you will see one the following two properties: <property name="EnableSkypeUI" >true</property> - This will enable the Skype UI OR <property name="EnableSkypeUI" >false</property> - This will enable the Lync UI If you do not see a value for "EnableSkypeUI" in this property group then it means that the user has been configured with a policy that has the value of EnableSkypeUI set to Null and the client will default to the correct UI based on what server version it is connected to.