NOTE: This solution applies also for both Lync 2013 and Skype for Business
Although we highly recommend organizations deploying Skype for Business upgrade to Quicklaunch Ultimate Edition (UE) for its tighter integration, you can still run either application with Quicklaunch Standard Edition (SE).
One drawback is that SE will not manage signing the Skype for Business client on behalf of a shared room account. Most organizations using Quicklaunch SE should have users to sign into Windows using their personal credentials, and starting Quicklaunch SE under their own credentials.
Some organizations may choose to create a generic "Quicklaunch Room" account that remains signed in, but because Quicklaunch SE does not manage the Skype for Business client, any user will normally be allowed to save their credentials -- and a person walking into the room may use these cached credentials to impersonate them if the owner does not delete them before leaving.
You can prevent Windows from allowing Skype user account credentials to be saved for any user using the PC by setting a group policy.
1. Exit all Microsoft Office applications.
2. Start the Registry Editor.
3. Locate and then select one of the following registry subkeys depending on your Office version. If the subkeys do not exist, you will have to create them.
- For Lync 2013: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\15.0\Lync
- For Skype for Business 2016: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Office\16.0\Lync
4. If there is no existing entry for AllowSavePassword listed in the Details pane, right-click and create a
new DWORD (32-bit) Value named AllowSavePassword.
5. Right-click on the AllowSavePassword entry, and then select Modify.
6. In the Value data box, enter 0, and then select OK.
7. Exit Registry Editor.
8. Reboot the PC
For more information, please refer to Microsoft KB3088665.
For more information about adding Office 2010 and Office 2013 Group Policies to your Windows network, please refer to the Microsoft Technet article "Use Group Policy to enforce Office 2010 settings". Although written for Office 2010, the same applies to Office 2013.