bounSky signs me out but the client shows the old site’s details when I bounce to a new site. Appears to not be working.

When you click to change to a new site the first thing bounSky does is pop the Lync / SfB client to the foreground and then send it a “sign out” command. The client then shows on-screen with the SIP

I keep getting a Group Policy error

Security-conscious corporate environments often use Group Policy to lock the Manual Configuration and hard-code their own Internal and External values. This is typically a data-leak prevention exercise to stop anyone signing in to another organisation’s instance of Lync or Skype

bounSky reports the client status is “Unknown”

This is a non-uncommon error, rendering bounSky (and other applications based upon the Client-side API) effectively useless. There can be a number of causes: some co-resident installations of both Office 2013 and Office 2016 versions of the Lync / SfB

I’ve upgraded and lost all of my previous sites/settings

Ouch! That’s not meant to happen (and I realise that’s cold comfort for you at this moment). The settings might not be lost. If you still have the .msi from the previous version, uninstall the version you’ve just installed, then

After I perform a File / Import / from Registry the values are incorrect

The Import from Registry process is far from perfect, purely because there’s not enough human-readable (or obviously decodable) information presented there to generate a workable set of ‘sites’. Think of it as more of a template to work from if

When I bounce to a new user or site, the wrong User Interface shows

If you’re using the Office 2013-based version of the Lync / Skype for Business client, patch version 15.0.4711.1000 (April 2015) introduced the ability for it to show either the Lync 2013 UI (skin) to the user, or the Skype for