locked
Office 2019 Standard with Skype for Business 2016 RRS feed

  • Question

  • Sigh...back at the MSI vs click-to-run vs retail installation woes.

    Scenarios: the entire office (~50 computers) has Office 2013 Standard with Skype for Business 2016. An analyst needs Excel 2019 for some of the new charting capabilities. But when I installed Office 2019 Standard via the deployment tools, it forced me to first uninstall Skype for Business 2016 and will not let me install it now that Office 2019 Standard is installed.

    Now, the problem is that none of the overly-simplistic answers will work:

    • Office 356: this desk, like all others in this client's operations, may be used by other staff, making the per-user-license-assignment inherent in Office365 an untenable solution. Office 365 is fundamentally an all-or-none proposition in an environment where users may share computers, even occasionally.
    • Office Pro 2019: while it does include Skype for Business, is 1) more expensive, with no gain and 2) includes Microsoft Access, not something we want in our environment. We have some system-wide ODBC DSNs that are required for some core database functionality, and the last thing we need is a clever users opening Access, connecting to the database in simple table views, and typing over existing data or deleting records. So we do not generally allow any Access installations except the standard Access 2013 Runtime (since neither Office 2019 does not have an Access Runtime and even Office 2016 Standard will not install side-by-side with Access Runtime 2016).
    • Retail: even though it might co-exist nicely with Skype for Business, we are not about to jump through all the mandatory Live account configuration/registration hoops required to implement a retail version.

    My next effort will be to try to download & install Skype for Business 2016 Basic. Perhaps that will play fair. But if not, how do I get Office 2019 with some version of Skype for Business on the same computer?

    Monday, March 11, 2019 7:23 PM

All replies

  • Hi,

    Unfortunately, it's true that we can't install Office 2019 and Skype for Business 2016 in the same computer because they share the same version 16.0 and use different installation technologies.

    For the volume licensed version of Office 2019, only Office Professional Plus 2019 includes Skype for Business. If you pick the plan and don't want Access to be installed, you could deploy Office Professional Plus 2019 via the ODT. You can use ExcludeApp element in configuration.xml to remove Access application when installing. For more information, please refer to Configuration options for the Office Deployment Tool.

    In addition, if you have any questions on Office licensing, I suggest you contact Microsoft and Volume Licensing Service Center support directly  for help.

    If you have anything unclear, please feel free to post back to let us know.

    Best Regards,

    Herb


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Office 2019.


    Tuesday, March 12, 2019 3:11 AM
  • So you're saying these two things, right, Herb?

    1. We just throw away our $400 Office Standard 2019 license, which we purchased without any reason to suspect that the licenses would conflict like this, and which will now be useless anywhere in the organization due to the conflict with Skype, and spend another $500+ Office Professional Pro, install it with Skype but without Access, then install Access 2013 Runtime (the only version that will work with click-to-run Office 2019--if it can even co-exist with Office 2019 Professional Plus w/o Access).

    2. That Microsoft has no intention of either making versions of these products that actually work together or, at the very least, providing clear guidance up front in the licensing process to prevent the hundreds of dollars of contracted IT expense and lost productivity for users just trying to get one product to work with another.

    And here is my core need now: please give me the URL that lists the Microsoft Office product version inter-compatibility. I do not have time to call Microsoft licensing to determine potential conflicts every time I want to purchase a license; I need a single source that will show me the compatibility across all office applications and versions.

    The cost of this $400 Office Standard license is now at perhaps $750 and growing with all the contracted IT services we have put--and continue to put--into this one installation.

    Tuesday, March 12, 2019 4:29 AM
  • Hi,

    I think the article Supported scenarios for installing different versions of Office, Project, and Visio on the same computer is what you are looking for. 

    Best Regards,

    Herb


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.

    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Office 2019.

    Tuesday, March 12, 2019 5:49 AM
  • No, that link does not help me, because it does not address standalone Skype for Business 2016, either as a product or in terms of installation technology. In fact, this link, also here on TechNet and from MSFT CSG, indicates that one can install Office 2016 Standard alongside the MSI version of Skype for Business 2016:https://social.technet.microsoft.com/Forums/en-US/cddb2504-feeb-427e-b131-408954ef7e17/unable-to-install-skype-for-business-2016-with-office-standard-2016-installed?forum=Office2016ITPro.

    But I tried that and could not get it to work.

    Now, though, I do have a bit more information after several further iterations. The actual failure message a couple of times was not an installation technology conflict, but an architecture conflict: after installing Office 2019 32-bit, when I tried to install Skype, it came up saying it could not install a 32-bit product while the 64-bit Office Extensibility... was installed. So it claims the conflict is not even about installation technology.

    So, in addition to the ~$300 in contracted IT time so far trying to sort this out, I had to revert the customer workstation to Office 2013 Standard, Access 2013 Runtime, and Skype for Business 2016--with no solution except perhaps the purchase of a new Office Professional Plus 2019 license. Not to mention the now-wasted $400+ cost of the unused Office 2019 Standard license. This is extremely frustrating and, in my opinion, absolutely pathetic as a business practice. Microsoft needs to get their act together; I, for one, do not mind paying what it costs to buy and use MS software, but when the vendor is effectively making it impossible to proceed, I wonder why I bother.

    Tuesday, March 12, 2019 5:03 PM
  • We have the same issue at our company. Worse is being a Non-profit we are being forced from our donated (almost free) version to Microsoft's SAAS offerings at a cost of thousands of dollars per annum. This has us looking at other companys' offerings, you might consider the same...
    Monday, April 15, 2019 2:57 PM
  • You can use the 2013 Lync 'Basic' installer to get you through.

    Its freaking ridiculous that MS greatly increases the price of Office (via Techsoup, we are a non-profit as well) so we had to convert to Standard after years of using Pro.  We muddled through with 2016 and the same issues finding the right standalone S4B client to work with it.  

    This is the icing on the cake though, that we now have to run a version older than with 2016 for 2019, even though our plan is supposed to PROVIDE a working application.

    I've yet to see any disclaimer or warning that states that you can't run the standalone Skype4Biz installers with 2019 Standard VL.

    I'm calling VLSC just to scream at someone.  




    • Edited by CFMASTL Tuesday, April 16, 2019 8:28 PM
    Tuesday, April 16, 2019 8:26 PM
  • Any traction from yelling?  I have office 2019 standard and E1 licenses that use Skype for business and have had issues getting the two to coexist using their installer.  It requires me to uninstall Standard to put skype on, but if I had PRO licenses I could use what I already pay for? Kinda ridiculous.  All we need is an MSI based standalone skype installer for 2019, and it seems like it would be fine. 


    • Edited by GregLVPC Monday, April 22, 2019 6:06 PM
    Monday, April 22, 2019 6:06 PM
  • Hello.

    Install Lync 2013 Basic from there:

    32 bit: https://www.microsoft.com/es-es/download/details.aspx?id=35451

    64 bit: https://www.microsoft.com/en-us/download/details.aspx?id=35450



    You can install this update too:

    • kb2760512-fullfile-x64-glb.exe
    • kb2768004-fullfile-x64-glb.exe
    • kb2817465-fullfile-x64-glb.exe
    • kb2817621-fullfile-x64-glb.exe
    • kb2825630-fullfile-x64-glb.exe
    • kb2889853-fullfile-x64-glb.exe
    • kb3191873-fullfile-x64-glb.exe

    I have the same problem in my company, and this is my solution.

    Tuesday, April 23, 2019 1:57 PM
  • So the solution is to go to even older software to work with the newer software?  Obviously Skype works with 2019 - they bundle it with the PRO version of office.  Microsoft, there's a simple solution here - just give us a standalone installer for the Skype that is bundled with OfficePro so that we can use our Office 365 subscription, which by the way we also pay for.  

    I've taken out all the options to remove MSI versions of software from the xml file and the 2019 installer STILL automatically removes Skype for Business from the PC when I run the installer for 2019 Standard.  

    Tuesday, April 23, 2019 4:25 PM
  • Been trying to find a solution for this like forever and just when I thought I had it solved, I got kicked in the ass again. My solution was to install Office 2019 Standard Volume License with Skype for Business 2019 Volume License from the Click-to-Run installer. However, it now prompts Skype for Business 2019 needs activation key which I thought the login credentials would provide it initially cause there was no prompting for activation.

    Fast forward 1 month later, there's a nagging prompt saying Skype for Business needs activation. Back to square one. Thanks Microsoft.

    Monday, May 27, 2019 4:14 AM
  • we had a dutch installer for SFB 2016 basic that not only worked (setupskypeforbusinessentryretail.x64.nl-nl_.exe 16.0.7967.1318) but installs the version corresponding office install (16.0.10350.20019)
    The german and english installers, downloaded at the same time but different versions, gave us the same errors as mentioned above.
    Today however, I found that when i edit a string in the exe (with resource tuner), i can modify the culture locale and it will install in the modified language. 
    If you don't have an old installer, i can send you a copy.
    • Edited by MDM276 Tuesday, October 8, 2019 4:00 PM
    Tuesday, October 8, 2019 3:59 PM
  • Turns out you don't need the old installer. With process explorer you can capture the OfficeClick2Run.exe command line parameters. take the "addproduct" parameter from the standalone installer and replace it in the command from the Volume license install. (make sure Display level="Full" or the C2R component runs hidden)  You could even install all of them together, but since you need the click2Run component for that, you need to deploy office first, and then you can install skypeforbusiness from the same resource with a command line.

    • Edited by MDM276 Friday, October 18, 2019 5:13 PM
    • Proposed as answer by MDM276 Friday, October 18, 2019 5:13 PM
    Friday, October 18, 2019 5:06 PM
  • Turns out you don't need the old installer. With process explorer you can capture the OfficeClick2Run.exe command line parameters. take the "addproduct" parameter from the standalone installer and replace it in the command from the Volume license install. (make sure Display level="Full" or the C2R component runs hidden)  You could even install all of them together, but since you need the click2Run component for that, you need to deploy office first, and then you can install skypeforbusiness from the same resource with a command line.

    Hi, can you explain in detail how you install skype for business with MS Office 2019 standard. Will really appreciate your explanation. Thanks!
    Thursday, January 16, 2020 6:39 AM
  • Turns out you don't need the old installer. With process explorer you can capture the OfficeClick2Run.exe command line parameters. take the "addproduct" parameter from the standalone installer and replace it in the command from the Volume license install. (make sure Display level="Full" or the C2R component runs hidden)  You could even install all of them together, but since you need the click2Run component for that, you need to deploy office first, and then you can install skypeforbusiness from the same resource with a command line.

    Hi, can you explain in detail how you install skype for business with MS Office 2019 standard. Will really appreciate your explanation. Thanks!

    Not sure if this helps anyone, but after days of fighting to get our Office 2019 standard installation and Skype for Business to work side by side, I finally have something that works for us. This configuration file will install Skype for Business 2019 Basic, and works when Office 2019 Standard is installed already on the device.

    <Configuration>
      <Info Description="Installs Skype for Business 2019 Basic" />
      <Add OfficeClientEdition="32">
        <Product ID="SkypeforBusinessEntry2019Retail">
          <Language ID="en-us" />
        </Product>
      </Add>
      <Display Level="None" AcceptEULA="TRUE" />
    </Configuration>

    Thursday, March 12, 2020 11:48 AM
  • Hi Sir,

    May I know how to use ur configuration file?

    Does i need to create a batch script or what?

    Thks

    Thursday, March 26, 2020 9:15 AM