Disable instant messaging in the Lync 2013 client

My original December 2012 note showed a registry-based way to disable instant messaging in a Lync 2013 client. Its command writes a policy value in the local-machine hive.

Start with the scope

HKEY_LOCAL_MACHINE—abbreviated HKLM—is a machine-level location. Writing there is not inherently a setting for only the signed-in user. This corrects the original note’s description of the example as applying to a specific user.

Before using the technique in a legacy environment, establish the required scope, the installed client version and the policy that already manages the setting. A local registry write and a centrally managed policy are not interchangeable operating arrangements.

Record the existing value

reg query "HKLM\Software\Policies\Microsoft\Office\15.0\Lync" /v DisableIM

Record whether the value exists, its type and its data. That gives a concrete baseline for comparison and restoration. A missing value and a value explicitly set to zero are different registry states.

The original setting, formatted clearly

reg add "HKLM\Software\Policies\Microsoft\Office\15.0\Lync" /v DisableIM /t REG_DWORD /d 1 /f

The historical example sets DisableIM to the DWORD value 1. Its counterpart writes 0:

reg add "HKLM\Software\Policies\Microsoft\Office\15.0\Lync" /v DisableIM /t REG_DWORD /d 0 /f

Setting zero is the reversal described by the original post. For an exact restoration, return to the recorded prior state under the applicable policy. If a managed policy owns the value, make the change through that management process.

Verify behavior on the intended client

Use a pilot machine with the relevant legacy client. Confirm the resulting value and test the intended IM experience after the required client restart or policy refresh. Include other users of the same machine when assessing machine-level impact.

Microsoft’s archived client-policy documentation provides context for Office 15.0 policy management, but it is not a direct validation of every value in this note. The command is preserved as a historical technical example, not presented as a current Teams policy.