Hack to Force new Skype for Business UI over Lync


Microsoft recently released an update that rebrands Lync as Skype for Business. Many got the update automatically through Windows Update, but not everyone gets the new user interface (UI). There is a Lync Server setting that tells the client to use the either the old Lync or the new Skype for Business UI. If the server doesn’t have this setting, such as older Lync servers that haven’t been updated yet, then the default is to show the old Lync UI. One frustrating part of this update/change from a user perspective is that you have no real choice of which UI version you want to see/use everyday; or is there? Fortunately, I figured out a hack to allow you to use the new Skype for Business UI even if your organizations Lync server hasn’t been updated, or the admins just want you to use the Lync UI instead. The hack involves making a small edit to the Windows Registry for the app.

Steps to Enable Skype UI

Follow these simple steps to enable the new Skype UI:

  1. Make sure the Skype for Business client application is closed
  2. Make sure your user account on the local computer is an “Administrator”
  3. Run “regedit.exe”
  4. Navigate to the registry key
  5. Change the value to “00 00 00 01”
  6. Run Skype for Business client application
  7. When prompted to restart, click “Restart Later”

Note: Modify the Windows Registry at your own risk. If you modify the wrong setting it could have bad, unintended consequences. It is always a good idea to backup the registry before modifying it.

Registry Key to Change

To force the Skype for Business UI you need to update the following registry key to be a value that equivalent to “True.” HKEY_CURRENT_USER\Software\Microsoft\Office\Lync\EnableSkypeUI The “False” value is “00 00 00 00”. So updating this to “00 00 00 01” will set it to “True”. Here’s a screenshot of the Registry Editor:

 reg

Requirements and Pitfalls

There are a few things to keep in mind for this hack:

  1. “Administrator” access to your local computer is required in order to use the Registry Editor (regedit.exe)
  2. You need to make this registry edit before you launch the app each time. Every time the app is closed, the value will be forced back to the setting sent from the Lync server.
  3. Some of the new Skype for Business features may not work since they require the new Skype for Business Server Update. If the server is an old Lync server, then the new features will not be supported even though the Skype for Business client application may show them available.
  4. If your admins are forcing the Lync UI, then they will not be happy with any support calls regarding the new Skype for Business UI. So, implement this hack at your own risk.

And to mantain the same look every time you reboot; Goto to your username and select the Deny tick mark and Save

and you are good to go Source: http://pietschsoft.com/post

How to use Lync 2010 client in Office Communications Server 2007 R2 environment – Bypass version Check.


“Cannot sign in because the server version is incompatible with Microsoft Lync 2010. Contact your support team with this information.

The simplest way to passing a version check and use the Lync 2010 client in Office Communications Server 2007 R2 environment, is very simple. You only have to create a new registry entry:

Key: HKEY_CURRENT_USER\Software\Policies\Microsoft\Communicator
Name:  DisableServerCheck
Type: DWORD
Value: 1 (00000001)

That´s it :).

Allow domain users to connect to Lync 2010 or OCS 2007 from Clients running on non-domain computers.


Few days ago I had a situation with some collegues. User´s wich don´t have their computer in domain, only in Workgroup.

When they install the Microsoft Lync 2010 client in their computers and tried to login with the same behavior as mail using DOMAIN\UID, they not be able to log on , they received the below event log warning:

“Communicator was unable to authenticate because an authenticating authority was not reachable.”

Resolution:

The server may be asking for Kerberos authentication and Communicator is not able to find the Kerberos Domain Controller in order to generate credentials and authenticate. The network administrator will need to change the configuration on the server to utilize only NTLM authentication before Communicator can login from this location properly, or connectivity will need to be made available to an authenticating authority”
I know it is not supported scenario. After installed the certificate, the user was able to login but it disconnects after 10 seconds then reconnects again , it keep in this loop. I also found the same warning in the event log.
I know why this is happening and I know it would have been solved from the beginning if i forced the OCS to use NTLM only rather than Kerberos but this was not something i can force.
So in the end the Solution was this problem was simple:
Ensure that the users when singing in to communicator 2007 or Lync 2010 to include the “.local” in the domain.local\username part of the authentication and not DOMAIN\username.