Skype For Business 2016 Client Deployment Tricks

I’ve been mucking around with Skype for Business 2016 and wanted to document what I’ve found.

First, there’s two seperate installs. A standalone Skype for Business 2016, and then as part of the Office 2016 suite, it’s one of the components (just like Word or Excel).

This is important, because if you install the standalone version then try to install Office 2016, it won’t like that Skype for Business is installed already, and tell you to uninstall before continuing. I’m not sure what reason you’d install Skype for Business 2016 standalone if you can just install that single component of Office 2016, but it’s a gotcha that might affect someone down the track.

I’ve also seen a few screen nags after deploying the client. There’s the ‘First things first’ screen which you most likely don’t want users to see:

first things first

To turn this off, set this key to ‘1’:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Common\General
REG_DWORD: ShownFirstRunOptin
Value: 00000001

Next is the ‘Welcome – Skype for Business’ screen. Can be annoying, and you can just surpress it from running the first time too, but let people read it on demand instead.

welcome to skype

To stop this one showing at first launch, set this key to ‘1’:

HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Lync
REG_DWORD: IsBasicTutorialSeenByUser
Value: 00000001

The final one I saw was after making calls, asking “How was the call quality?”. Most users won’t want to be hassled by this unless there’s an actual problem, so you may want to disable it.

call quality

This setting is actually controlled at the sever end, and has a % chance of showing up after each call. By default, it’s 10%, so I suggest setting it to 0%.

To do so, launch the Skype for Business Server Management Shell and run the commend ‘Get-CSClientPolicy’. This will show you how many policies you have, and you may want to change the value for just some or all, depending which users are against which policy. The field for this setting is called “RateMyCallDisplayPercentage”.

Once you’ve worked out which policy you want to change, run this command: ‘Set-CSClientPolicy -identity “policyname” -RateMyCallDisplayPercentage 0’

If you find any other tricks, feel free to share and I’ll update the post.

 

 

20 thoughts on “Skype For Business 2016 Client Deployment Tricks

  1. Dear Adam,

    Thanks for sharing your observation.

    I am currently struggling with another scenario, not sure if you can help me.

    I installed ONLY (excluded all other apps via exclude ID element) Skype for Business (SFB) via click 2 run method. So far so good. All works well.

    Now, I want to install all the remaining component (word,excel,PowerPoint,One-drive) on the same PC where I earlier installed SFB. However, The installation will start and then just do nothing. Seems like it finds office (which is not the case as ONLY SFB is installed) is installed and quits.

    Do you have experience on the topic I explained above mate? Thanks in advance and keep sharing your knowledge and experience – It helps a lot!

    Regards
    Ashish Wadhawan

    1. Hi Ashish,
      Thanks for the feedback. Have you tried finding Microsoft Office Professional Plus 2016 in Programs and Features, and using the ‘Change’ option?

      I haven’t tried with the click 2 run method yet, you’re doing this with your Office 365 sub?

    2. Hi Ashish,

      As you have already used the Office Deployment Tool to deploy Skype, you will need to use the same tool to deploy the rest of office.

      You should create a new XML file which removes the exclude sections from the original XML file and allowing Word, Excel etc and then use the Setup.exe /configure against the new XML file.

      It will automatically download and update the Office installation adding the components you require.

      1. Dear Andrew,
        You are correct. I have to use the .xml files to the installation for the renaming components. I am currently starting the deployment in my company and initial test with office 365 installation are looking good. Though there is a bug with the language on skype for business title bar. In case you have more than 1 language id let us say dutch then skype for business title bar will say that in dutch all the time and you can not take it back to english even if you change the language back to english under office 2016 language tool. I opened a ticket with MS and they confirmed this to be a bug :( for which MS will release a patch “soon” no ETA :)

  2. Another great post Adam – here are another few keys that I have found useful and often implement depending on requirements for app open/close on start up, call quality, windows firewall rules and monitoring.

    HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Lync
    “EnableEventLogging”=dword:00000000
    “CallMonitorEnabled”=dword:00000001
    “MinimizeWindowToNotificationArea”=dword:00000000
    “AutoOpenMainWindowWhenStartup”=dword:00000000
    “AlwaysShowMenu”=hex:01
    “AddToFirewallExceptionList”=dword:00000000
    “FirstRun”=dword:00000001
    “EnableTTY”=dword:00000000
    “TracingLevel”=”Full”

    Plus there is always the global Office 2016 settings for accepting the EULA.

    HKEY_CURRENT_USER\SOFTWARE\Microsoft\Office\16.0\Registration
    “AcceptAllEulas”=dword:00000001

    1. Dear Andrew,
      This reg key information looks interesting. Is there a place where I can find detailed description on what each key does or what change to be expected when these keys are implemented as shown above.
      Looking forward to your response. Thanks
      Best Regards
      Ashish Wadhawan.
      wadhawan.ashish@gmail.com

  3. I will definitely use this page as I am currently deploying Skype for Business Basic 2016 (we use Office 2010). I look forward to implementing some of these settings via GPO! Thank you!

    1. @ Eric – I am on the similar journey. Keep sharing your experiences with deploying Office 365. I am currently deploying (via SCCM 2012 SP1) it to all sites and have learned little bit during this journey. Feel free to email me wadhawan.ashish@gmail.com if you have any question or face any challenge during deployment.

  4. Hi, we currently have volume licensing for Office 2013 deployed to company computers.
    But we have Skype For Business O365 licenses as well.
    What client do I deploy and where are instructions for that, in order to deploy without causing a conflict to upgrade to Office 2016 (volume licensing) later on?

    1. I’m running SfB on prem sohaven’t done an install that way – but I believe an O365 license under EA lets you install Office 2016. In your scenario, I’d be using the Office 2016 suite as I did above and only installing the SfB component, but that’s as long as the licensing makes sense. This MS article talks about the standalone install and licensing requirements which might help:

      https://support.microsoft.com/en-au/kb/3139711

  5. If I’m deploying this with SCCM, then will the HKCU registry keys in the Office Customization Tool not work for all users on the target PC’s?
    Would it be best to implement these registry tweaks via Group Policy Preferences instead?

    1. If you’re triggering the install via setup.exe silently, it should still do all the customizations you’ve configured – just make sure that file that contains them is part of your source package.

      I’d do it that way rather than GPP, because then you have a baseline of the registry settings changed as part of the install.

      1. Ok. I guess I wasn’t sure if HKCU entries in the customization tool worked when running setup.exe as a network install account. Or if it only modified the user’s HKCU if THEY were the user actually running setup.exe.

      2. Oh,, good point :) It’ll change the default user HKCU but not existing users. Yes, GPP would be good for that, and maybe make the updates against the existence of a file that turns up as part of the install.

      3. Yea and now that you mention it, I could probably deploy a required app to the computer to run as user that applies registry as well, before then running subsequent Skype installer. Use GPO as well as additional layer.

      4. Yes, but what if multiple users use the same PC?
        Trigger a gpupdate and reboot (if required) as part of your deployment :)

    2. If you use SCCM to deploy any Office (MSI) product, keys and settings that you create that are current user will get dropped properly. They utilize Microsoft’s special active setup routines to create them at first launch. I have all of our Office apps customized per business requirements and they all work fine. I wouldn’t actually create all of those that Andrew calls out above as regkeys tho – just use the OCT and define them as settings…better that way :).

Leave a Reply