Install Microsoft Volume Licence application with Office 365
-
That the conflict isn't totally surprising, because of the way that MS has long handled MS Office as a single thing, having two versions of the same edition would cause problems. This doesn't come up often, so people tend not to really think about the complexities of the central installer and management system.
My guess, but this isn't my area, is that finding a way to containerize or "virtualize" as people sometimes say the Access install so that it can't see the other install is what is needed.
-
There's gotta be an easier way.
-
@Carnival-Boy said:
There's gotta be an easier way.
Maybe, but I think given the issue, there may not be.
-
At least it tells you what the problem is for once.
I've got a 2010 copy of Visio stand alone, on a click to run Office 2013 365 working fine. Maybe if you had 2013 click to run and then stand alone 2016 access it would work.
Or, 2013 access with 2016 click to run.
It's not ideal but that's what I would try off the top of my head.
-
@Breffni-Potter said:
I've got a 2010 copy of Visio stand alone, on a click to run Office 2013 365 working fine. Maybe if you had 2013 click to run and then stand alone 2016 access it would work.
I would expect that to work. Office interacts well with two wholly different versions.
-
OK. I've installed Access 2010 and that works fine.
-
I've had 2016 Pro Plus and 2016 Business Premium (0365) on the same system before with no issues.
-
@Jason said:
I've had 2016 Pro Plus and 2016 Business Premium (0365) on the same system before with no issues.
That's probably because they're both Click-to-run. It's trying to install Click-to-run and Windows-installer versions of the same suite that seems to be the issue.
We have got 2013 versions of Office 365 and standalone Access 2013 installed, so this seems to be a 2016 issue.
-
@Carnival-Boy said:
@Jason said:
I've had 2016 Pro Plus and 2016 Business Premium (0365) on the same system before with no issues.
That's probably because they're both Click-to-run. It's trying to install Click-to-run and Windows-installer versions of the same suite that seems to be the issue.
We have got 2013 versions of Office 365 and standalone Access 2013 installed, so this seems to be a 2016 issue.
Pro Plus was not a Click to Run... it was Volume. Business Premium was.
-
we ran into the same issue. Install both with the MSI files and everything will work the way it should .
-
@david.wiese said:
we ran into the same issue. Install both with the MSI files and everything will work the way it should .
He wasn't able to location MSI files for non-Access, though.
-
@david.wiese said:
we ran into the same issue. Install both with the MSI files and everything will work the way it should .
Where can you get an MSI for Office 365?
-
Office 2013 installs fine. so I'll stick with that for the time being. Annoying though as I was looking forward to trying out Access 2016.
-
Can you do Office 2013 and Access 2016?
-
Dunno, but I'm loving the new black theme in Office 2016, so I'm never going back to 2013.
-
Slightly different issue but looks like microsoft is willing to help out with these type of issues:
-
Interesting - I didn't know there was an Office 365 version of Office that didn't include Access.
-
@Dashrender said:
Interesting - I didn't know there was an Office 365 version of Office that didn't include Access.
I don't think my personal office 365 business premium has it
Edit: checked it does not.
-
You need the Office 2016 Deployment tool to get a .msi:
https://www.microsoft.com/en-us/download/details.aspx?id=49117
You set up a folder on your server, configure the .xlm file, run the command line to download the install, and then run it again with a different switch to install Office on the client. -
@Jason said:
@Dashrender said:
Interesting - I didn't know there was an Office 365 version of Office that didn't include Access.
I don't think my personal office 365 business premium has it
Edit: checked it does not.
What do you know - I just checked mine, you're right.
