Zegeger.net

A site about games, computers, and life, at least my life…

Deploying Lync 2010 on Windows XP 64-bit

This is not supported by Microsoft, and never will be.  There may be issues with running the client on an unsupported OS.  Use at your own risk!

The Lync system requirements list Windows XP SP3 as the minimum that is supported.  This unfortunately leaves out Windows XP 64-bit as there is no Service Pack 3 for that version.

If you run the Lync Install on 64-bit XP you will get a nice error informing you of this fact.

Officially Windows XP 64-bit is not supported by Microsoft, but if you don’t mind running in an unsupported scenario, then you can use the following steps to work around this.  You will need at least one system that is a supported OS for this to work.

  1. Run the LyncSetup.exe on a supported (preferably 64-bit) workstation and it will indicate it is unpacking some files and then prompt you.  Leave the window alone and navigate into your Program Files (x86) folder and there should be a new folder called OCSetup.
  2. Copy the entire OCSetup folder and move it to the Windows XP 64-bit workstation.  You can cancel the install on the first workstation now.
  3. On the Windows XP 64-bit workstation, install silverlight.exe, vcredist_x64.exe and vcredist_x86.exe that are included in the OCSetup folder.
  4. Install MSXML SP1 if you do not already have it installed.  Download link.
  5. Run the OCSetupLauncher.exe to install the client.

I was able to log into the client and verify IM, presence, and conferencing appeared to work fine.

It does appear that the standard (self-healing) launch links have an issue in XP 64-bit. Each time you launch Lync through the shortcut it will run a repair install.    You can work around the issue by replacing the self healing communicator short cuts with standard shortcuts to communicator.exe.

There may be other issues with running the client on this OS, so your best option will likely be to just go ahead and upgrade to Vista/Windows 7.


Category: Lync
  • Ofer says:

    Have a winXP 64bit sp2. Tried your workaround, and failed. I installed everything, but when I run the luncher it fails with an error “Microsoft Visual C++ 2008 redistributable installation failed. Please review the log file for details, and try again”.
    What log file?
    The event viewer shows me nothing. Any clue?

    February 6, 2011 at 5:28 pm
    • Zegeger says:

      I believe there are 2 versions of the redistributable. Make sure you manually install both of them prior to running the msi. I’m not certain where it may be placing the log files, but you can run the msi from a command line and specify the log file location. Do a /? to get the switches you can use.

      February 22, 2011 at 12:39 pm
  • ncsb says:

    Worked great. thanks!

    April 8, 2011 at 8:40 am
  • JDuplant says:

    I had no luck either. The Lync installer keeps giving me the same message that @Ofer is getting: “Microsoft Visual C++ 2008 redistributable installation failed. Please review the log file for details, and try again”.

    I manually installed the C++ 2008 86/64 packages and the C++ 2010 86/64 packages. Still the same message.

    January 17, 2012 at 5:23 pm
  • knirsch says:

    Workaround is great.
    Many thanks

    March 22, 2012 at 10:05 am
  • Vinnyl says:

    Worked like a charm.
    Thanks

    May 25, 2012 at 8:31 am
  • Stuart says:

    This workaround did not work for me, however I successfully installed Lync 2010 using a different workaround method.

    First download Microsoft Application Verifier: http://www.microsoft.com/en-au/download/details.aspx?id=20028 and install the x64 version.

    Once this is installed, open the x64 Application Verifier (shortcut in start menu)

    Add the installation application LyncSetup.exe (File>Add Application)

    Select the Application in the left pane, then open the compadibility tree on the right pane and enable “HighVersionLie”.

    Click the save button then open LyncSetup.exe. The program should now install and run without a problem.

    January 30, 2013 at 8:22 pm
    • Les says:

      The Microsoft Application Verifier method worked great! Thanks.

      March 28, 2013 at 5:34 pm

Your email address will not be published. Required fields are marked *

*