locked
Deploying Lync 2010 client via SCCM RRS feed

  • Question

  • I am trying to distribute the new Lync client via SCCM (SCCM is not the problem here, this related to any software distribution product).

    I am getting frustrated at the way the new client has been packaged - LyncSetupEval.exe in particular. Why can't Microsoft provide a simple MSI file?

     

    I can run the LyncSetupEval.exe file with /Install /Silent, but this managed to crash OUTLOOK.exe when it runs. Also when it completes, it automatically starts communicator.exe in the SYSTEM context, meaning that unless you restart your machine, you cannot run the Lync client in the user context. 

     

    Is anyone else having the same frustrations? I've played around with the files in the OCSetup directory, but there are of no use.

     

    • Moved by Ben-Shun Zhu Tuesday, November 30, 2010 6:26 AM incorrect queue (From:Lync Clients and Devices)
    Tuesday, November 30, 2010 12:45 AM

Answers

  • You can extract the MSI from the exe file as it is mentionned in the getting started guide under "Lync 2010 Setup Executable". I cannot find how though, looks like it isn't documented yet?

    You also might want to look into this article: IT-Managed Installation of Lync 2010. Does this help?


    Technical Specialist Microsoft OCS & UC Voice Specialisation - http://www.uwictpartner.be
    • Proposed as answer by Ruben Nauwelaers Saturday, December 4, 2010 8:27 AM
    • Marked as answer by danovich_ Wednesday, December 8, 2010 3:29 AM
    Friday, December 3, 2010 10:42 AM
  • Yes you are right Ruben, it is not yet documented but the key piece of information is in the 'What's New in Client Deployment' section! 

     

    UseMSIForLyncInstallation to allow the .msi to run on client computers.

     

    Wow I really can't understand how this is left out of the product documentation. I ended up writing a VBScript with a popup to alert the user to close Outlook and IE, then the installation proceeds in the SYSTEM context, then at the end I kill the communicator.exe process that is running under SYSTEM. It's really disappointing that this client installation is so hard given how easy LCS and OCS clients were.

     

    http://blog.danovich.com.au

     

    • Marked as answer by danovich_ Wednesday, December 8, 2010 3:29 AM
    Wednesday, December 8, 2010 3:28 AM

All replies

  • You can extract the MSI from the exe file as it is mentionned in the getting started guide under "Lync 2010 Setup Executable". I cannot find how though, looks like it isn't documented yet?

    You also might want to look into this article: IT-Managed Installation of Lync 2010. Does this help?


    Technical Specialist Microsoft OCS & UC Voice Specialisation - http://www.uwictpartner.be
    • Proposed as answer by Ruben Nauwelaers Saturday, December 4, 2010 8:27 AM
    • Marked as answer by danovich_ Wednesday, December 8, 2010 3:29 AM
    Friday, December 3, 2010 10:42 AM
  • Yes you are right Ruben, it is not yet documented but the key piece of information is in the 'What's New in Client Deployment' section! 

     

    UseMSIForLyncInstallation to allow the .msi to run on client computers.

     

    Wow I really can't understand how this is left out of the product documentation. I ended up writing a VBScript with a popup to alert the user to close Outlook and IE, then the installation proceeds in the SYSTEM context, then at the end I kill the communicator.exe process that is running under SYSTEM. It's really disappointing that this client installation is so hard given how easy LCS and OCS clients were.

     

    http://blog.danovich.com.au

     

    • Marked as answer by danovich_ Wednesday, December 8, 2010 3:29 AM
    Wednesday, December 8, 2010 3:28 AM
  • Besides adding the UseMSIForLyncInstallation registry key to allow installation of the MSI file, you can also create a custom MST that will make it possible to deploy the Lync 2010 client software using a software distribution GPO or SCCM.

    Please check http://cecomputerexpertise.wordpress.com/2011/01/13/deploying-lync-2010-client-using-group-policy/ for additional information.

    Tuesday, February 8, 2011 7:14 AM
  • Yes you are right Ruben, it is not yet documented but the key piece of information is in the 'What's New in Client Deployment' section! 

     

    UseMSIForLyncInstallation to allow the .msi to run on client computers.

     

    Wow I really can't understand how this is left out of the product documentation. I ended up writing a VBScript with a popup to alert the user to close Outlook and IE, then the installation proceeds in the SYSTEM context, then at the end I kill the communicator.exe process that is running under SYSTEM. It's really disappointing that this client installation is so hard given how easy LCS and OCS clients were.

     

    http://blog.danovich.com.au

     

    Danovich,

    Is there anywhere we can access yor VBScript describing what you just said? I need the exact same thing, to let them know and also to close those other applications.

    Cheers

    Tuesday, February 22, 2011 4:24 AM
  • Hi Ryan,

    Happy to share. I do a simple messy batch file / VB Script combination like this:

    @echo off
    ECHO Set wshShell = CreateObject( "WScript.Shell" ) >> usermessages.vbs
    echo wshShell.Popup "The Microsoft Lync 2010 client is about to be installed.  Please close Microsoft Outlook and Internet Explorer before clicking OK to continue.", 300, "Microsoft Lync 2010 installation" >> usermessages.vbs
    ECHO WScript.Sleep(5000) >> usermessages.vbs
    WSCRIPT.EXE usermessages.vbs
    DEL usermessages.vbs /q
    ECHO Installing Microsoft Lync 2010...
    taskkill /F /IM communicator.exe
    taskkill /F /IM outlook.exe
    taskkill /F /IM iexplore.exe
    LyncSetup.exe /Install /Silent
    taskkill /F /IM communicator.exe
    msiexec.exe /p OUTLOOK.msp /qb-!
    office2007-kb936864-fullfile-x86-en-us.exe /passive /norestart
    msiexec.exe /update Lync.msp /qb-!
    
    ECHO Set wshShell = CreateObject( "WScript.Shell" ) >> usermessages.vbs
    echo wshShell.Popup "The Microsoft Lync 2010 client installation was successful and can now be run from the Start Menu.", 300, "Microsoft Lync 2010 installation" >> usermessages.vbs
    WSCRIPT.EXE usermessages.vbs
    DEL usermessages.vbs /q


    I'm sure it could be a lot nicer, there is no error passing or anything but it has served me well.

    blog.danovich.com.au

    Tuesday, February 22, 2011 6:00 AM
  • There is a KB Article available that describes this Registry Key:

    2477965 The installation of Lync 2010 by using Windows Installer (MSI) fails
    http://support.microsoft.com/default.aspx?scid=kb;en-US;2477965


    RW
    Monday, March 14, 2011 3:18 PM
  • danovich,

     

    Thanks for the bat file. I just have a couple of questions. When I run the bat from the computer just to test it before i put it into SCCM it works fine except for when I go to run it it ask for a username and password for the Outlook connection. Which I guess is the next question, is that what the OUTLOOK.MSP is and the office2007 file?

     

    The last question is when I set it up in SCCM and run the advertisement it looks like it goes all the way through but only installs LyncSetup.exe. How did you setup your package and advertisement?

     

    Thank you any help would be great.

    Wednesday, November 16, 2011 4:59 PM
  • You can extract the .msi file by running the client installation executable on a supported Windows client, which creates the Lync.msi file in %Program Files%\OCSetup\Lync.msi or %Program Files(x86)%\OCSetup\Lync.msi
    Thursday, July 12, 2012 7:41 PM
  • You can try this :- http://prajwaldesai.com/how-to-deploy-lync-2010-client-using-sccm-2012-r2/

    Prajwal Desai, http://prajwaldesai.com

    Saturday, March 8, 2014 6:43 PM