/build/static/layout/Breadcrumb_cap_w.png

Disable autostart Lync 2013

In order to disable Lync 2013 to autoastart after installing you must add the following reg keys:
HKCU\Software\Microsoft\Communicator

AutoRunWhenLogonToWindows DWORD 0
FirstRun DWORD 1
MinimizeWindowToNotificationArea DWORD 1
AutoOpenMainWindowWhenStartup DWORD 1

Comments

  • Interesting.

    When we deployed Lync 2013 as part of Office 2013, Lync did not auto load by default. We actually had the opposite problem where we wanted it to, but had to come up with a solution to force it. - rschauer 9 years ago
    • Yes, you are right but I had a request to deploy only the Lync product and that was the requirement, to disable the autostart.... - EmanuelPopescu 9 years ago
  • i have a slightly different question :). we are in the process of upgrading from Lync 2010 to Lync 2013, on systems that are running Office 2010 (Win7 ent.). however, after the custom MSP is run to install the Lync 2013 component, the Add/Remove programs show both Office 2010 and Office 2013 as installed. this is a reporting nightmare for SCCM. any thoughts on getting the "Office 2013" tag out of there and put Lync 2013? or is this is a "Microsoft Feature" ? :)
    thanks. - paul.gurusinghe 9 years ago
    • Sorry but I only used the config.xml to install lync where I add two msi files to isntall and made the standard configurations. I don't understand if you just want to install only Lync componet or the all office suite??? - EmanuelPopescu 9 years ago
    • If it helps this is the folder structure for Lync 2013 that I used and worked ok: http://tinypic.com/r/2m4rps8/8

      P.S. ignore $SWI folder - EmanuelPopescu 9 years ago
  • thanks Emanuel! i only need to install Lync 2013. these are for the users who already have Office 2010, and they dont need the upgrade to Office 2013. however, when i install Lync 2013 ONLY (using the Office Customization Toolkit - Setup.exe /Admin), i still see Office 2013 in Add/Remove programs. i understand that Lync is part of the Office 2013 suite, thus appearing like this, but was looking for a way to remove it from there, so the SCCM reporting that looks for apps in the Add/Remove programs will not report a pc as having both Office 2010 and Office 2013. - paul.gurusinghe 9 years ago
  • So I made an install to with the msp file and I saw that in ARP office 2013 entry is present. I think that the easiest way to do it is to modify this entry: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\Office15.PROPLUS - DisplayName to what evere you want.... - EmanuelPopescu 9 years ago
  • I was under the impression that AutoRunWhenLogonToWindows was only used for Lync 2010. http://blogs.technet.com/b/rischwen/archive/2013/06/20/lync-2013-client-auto-start-registry-key.aspx.

    If I wanted to disable Lync autostart why would I set the second and fourth recommended entries to 1? I wouldn't want FirstRun or the main window to appear. If Lync was set to not autostart these settings wouldn't be needed anyway, correct?

    These recommended settings have no impact on Lync autostart from my testing.

    Can someone please explain?

    Removing it from the run line in the registry does work manually but my issue revolves around getting it removed BEFORE the user logs on for the first time. I tried a GPP to remove the entry but Lync.exe launches on first logon before the GPP is applied so it takes a second logon that does not meet my requirements.

    Thanks - mniccum 9 years ago
  • Trick to disable Lync 2013 autostart is that: under HKCU\Software\Microsoft\Office\15.0\Lync Set value FirstRun = 1
    Same method works for Lync 2016 (skype for business) ofcourse then reg key is HKCU\Software\Microsoft\Office\16.0\Lync

    For me this was working :) - wpi 7 years ago
This post is locked
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ