VMware Horizon Community
jsinclair
Enthusiast
Enthusiast

AV 2.11 and Office 365 (Office 2016)

I've seen this question asked already, but no clear response yet. We are looking to use Office 365 with Office 2016 and App Volumes. Is there support for this version in 2.11? If not, when can I expect it?

Thanks!

15 Replies
Lakshman
Champion
Champion

Office 2016 is not officially supported in App Volumes 2.11. Hope the next release will have the support.

Reply
0 Kudos
cH1LL1
Enthusiast
Enthusiast

Although it does work - you may need to make a few tweaks to each appstack in order for them to work and not have VB conflicts.

office 365 (2016 32bit office client) and Appvolumes 2.11

650 users + no problems,.

Reply
0 Kudos
sjesse
Leadership
Leadership

What did you do to get it to work. I'm trying to fix the need for the initial reconfiguration everytime. In the past you could delete the office setup controller setup file but doing that now looks like it won't be licensed correctly.

StormFlowers
Contributor
Contributor

I'm also interested to see how you got this to work and what VB conflicts you had to correct.

Reply
0 Kudos
Tomas_Iskra
Contributor
Contributor

Hi,

can please share how you made it work.

We are seeing some issues, usually seeing error message below:

pastedImage_0.png

When we open Outlook and try to preview any other Office product file type (docx, xlsx, pptx etc) we are getting an error:pastedImage_1.png

Other files types (txt, pdf) are previewing just fine.

Thank you.

Reply
0 Kudos
cH1LL1
Enthusiast
Enthusiast

sjesseStormFlowers‌ @Tomas_Iskra

Hello -  This is how I installed Office365 into the base image:

How-to configure Office 365 Pro in a non-persistent VDI environment | SvenHuisman.com

With that done- I have Appvolumes Manager 2.10 installed (to be upgraded to 2.11) -  however the VMware Agents within the VDI desktops are already 2.11  (this is where all the Virtualization is done)

We noticed All  inhouse Word and Excel addins simply would not load,VBA in office was effectively broken:

We had to update each Appstack with the following :

If you are using office 2013 use the article published here :

Microsoft Office 365 32-bit version does not work with Writable/AppStack volume on 64-bit version op...

If you are using Office 2016 the REgistry path you need to exclude is the following:

################################################################

# Office 365 Virtual Registry exclusions

################################################################

exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY

And one last thing it looks like you now need to use VCREDIST2015_64x in order for Preview and send to outlook, snipping tool etc to integrate with office correctly.

Just install it.

Happy to help if i can.

Reply
0 Kudos
Tomas_Iskra
Contributor
Contributor

Hi cH1LL1,

I've tried both O365 ProPus 2013 and 2016 and previewer doesnt work on neither of them.

Exclusions mentioned in your post and in articles are already in place on our template but the issue still persist.

Also opening Office file from outlook message doesnt work as well, it throws an error.

Any ideas/suggestions would be highly appreciated.

Thank you.

Tom.

Reply
0 Kudos
TDJB3
Enthusiast
Enthusiast

I found out that this was caused by the writable disk.  I have Office 365 2013 installed on my image and not as an AppStack. 

Reply
0 Kudos
Tomas_Iskra
Contributor
Contributor

Thanks to VMWare support, issue with O365 2013 preview handlers can be easily resolved following this KB - Some applications delivered in appstacks which require network connectivity may not be able to conne...

Reply
0 Kudos
jtupeck
Contributor
Contributor

This is EXACTLY what is happening to me in our environment and all of the solutions above have not made a lick of difference.  I used the VMware recipe to install O365 (2013) and made the necessary tweaks, but nothing has changed. I get the 'Something went wrong' error almost every time I open Word or Excel and then the whole machine locks up.  Outlook works OK, but is VERY slow and sometimes locks up as well.

When I use the MSI installer and KMS activation, we have next to no issues with Office at all.  Anyone with any further advice?  I have opened a ticket with VMware, but dont expect them to jump right on this anytime soon.

Reply
0 Kudos
cH1LL1
Enthusiast
Enthusiast

I wouldn't suggest you appstacking office 2016 its very chunky -  this should be in the base image.

you can however attach 2010 appstacks alongside this like MSProject2010 or MSVisio 2010. with no problem.

the only previewer issue i am having is with Excel only:

this resolved it.

http://www.outlook-tips.net/tips/outlook-2016excel-files-wont-preview/

jtupeck
Contributor
Contributor

THIS!

This fixed the issue.  I reproduced the solution on 4 separate vDesktops and I am testing it now via adding the registry entry to the base image and composing new machines.  THANK YOU!  My support rep and I stumbled upon this today (for some reason I never got an alert that you had responded to my last comment) and found that it works.


Thank you!

szilagyic
Hot Shot
Hot Shot

We are having the exact same problem with Office 2016 and AppVol 2.12, along with being the latest version of the Horizon platform, 7.0.3.  Office 2016 will work for a while, then all of a sudden just stop and the error "something went wrong" which is about as useless as it can get.  Nothing shows up in the Windows logs.  I've currently got a ticket open with VMware and so far no luck.  I posted at this thread, hoping to find a resolution to this soon:

Re: Office 2016 (O365) and Writable Volumes, constant application crashing

The temporary solution I posted there has helped somewhat.  It seems that Office will run for a while, then when it breaks, logging off/on will get it working again.  I suspect because I have it blocking from writing the clicktorun files to the Writable Volume.   It sure seems like an issue with Writable Volumes and whatever clicktorun is doing to run Office apps and try and activate them.  Supposedly AppVol 2.12 is fully compatible, but this issue is still happening.  If somebody got this working it would be nice to share the details.

Reply
0 Kudos
LJMCP
Enthusiast
Enthusiast

I am also seeing a similar issue.  Office 2016 click-to-run in 2.12 AppVol appstack, Outlook cannot open Office attachments.  Receive error from Click-to-Run client "Something Went Wrong".   See a number of Software Protection Service errors in App event logs.  Disabling Protected View did not resolve.


Adding exclude_registry=\REGISTRY\MACHINE\SOFTWARE\Microsoft\Office\ClickToRun\REGISTRY to the appstack did fix a number of other issues, namely with Skype presence integration not working in Outlook.


Otherwise, anyone have a fix for this?  I have a SR open with VMware but no solution has been provided.

Reply
0 Kudos
szilagyic
Hot Shot
Hot Shot

We ended up finding a permanent solution to this.  I provided the solution in my post, that worked for us:

Re: Office 2016 (O365) and Writable Volumes, constant application crashing

Hope this helps.

Reply
0 Kudos