VMware Horizon Community
TDJB3
Enthusiast
Enthusiast
Jump to solution

O365

We have struggled mightily with creating a stack for O365.  We are using the click-to-run version of O365.  Our setup is Windows 7 64-bit, O365 32-bit, App Volumes 2.12, and View 7.01.  For those that have successfully done this, did your bit version for O365 match up with the bit version of your OS?

Reply
0 Kudos
1 Solution

Accepted Solutions
TDJB3
Enthusiast
Enthusiast
Jump to solution

Windows 7 SP1 App Volumes 2.12  View 7

So, we have resolved this issue with VMware's help.  We had to use a registry line to two places.  One line was added to the snapvol.cfg on the AppStack and the other to the snapvol.cfg writeable disk.  This was necessary for O365 2013.

The line that we used is

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

# Office 365 Virtual Registry exclusions

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

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


I just added it to the bottom of the config file. C:\snapvolumestemp\MountPoints\GUID\snapvol.cfg for the AppStack. 

I have not changed the template for a writeable disk, but I changed my own to prove this out.  I added the same line.  To make the change, I had to go into Disk Management to assign a drive letter to the writeable disk.


We did decide to move to O365 2016 and it was not necessary for us to change the writeable disk template.


View solution in original post

Reply
0 Kudos
8 Replies
Lakshman
Champion
Champion
Jump to solution

Worth reading this document though it was written for 2.10 version:

VMware App Volumes Provisioning Recipe for Microsoft Office 365

Reply
0 Kudos
MikeC3964
Enthusiast
Enthusiast
Jump to solution

Hi,

I'm running appvolume 2.12, and was able to create a stack for office 2013 C2R, without any issues. I'm utilizing shared activation, but not using it worked also. What issues are you having?

Thanks,
Mike

Reply
0 Kudos
TDJB3
Enthusiast
Enthusiast
Jump to solution

Windows 7 SP1 App Volumes 2.12  View 7

So, we have resolved this issue with VMware's help.  We had to use a registry line to two places.  One line was added to the snapvol.cfg on the AppStack and the other to the snapvol.cfg writeable disk.  This was necessary for O365 2013.

The line that we used is

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

# Office 365 Virtual Registry exclusions

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

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


I just added it to the bottom of the config file. C:\snapvolumestemp\MountPoints\GUID\snapvol.cfg for the AppStack. 

I have not changed the template for a writeable disk, but I changed my own to prove this out.  I added the same line.  To make the change, I had to go into Disk Management to assign a drive letter to the writeable disk.


We did decide to move to O365 2016 and it was not necessary for us to change the writeable disk template.


Reply
0 Kudos
Lakshman
Champion
Champion
Jump to solution

Thanks for sharing the steps that will help other customers indeed.

Reply
0 Kudos
wojcika
Contributor
Contributor
Jump to solution

Hello,

Were you following the recipe for Office 2013 to appstack Office 2016?

VMware App Volumes Provisioning Recipe for Microsoft Office 365

Thanks!

Reply
0 Kudos
TDJB3
Enthusiast
Enthusiast
Jump to solution

wokcika,

We did follow the recipe and some other information.

1. Microsoft Office 365 32-bit version does not work with Writable/AppStack volume on 64-bit version op...  This talks about O365  2013, but I changed it to work with 2016.  The KB refers to adding the information below to the writeable disk and the AppStack.

  1. ################################################################
    # Office 365 Virtual Registry exclusions
    ################################################################

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

     I was told by VMware to add the information above to the AppStack before I installed O365 2016.

2. Installing and Using Microsoft Office Products with VMware App Volumes 2.x (2146035) | VMware KB This article talks about licensing and a prerequisite that needs to be loaded onto the virtual machine that you use for building your AppStack.

3. Some applications delivered in appstacks which require network connectivity may not be able to conne...  This article talks about adding a registry entry to virtual machine that you use for building your AppStacks.


FYI


We are still having problems.  We can't open Office attachments and 2016 crashes every hour.  We have been in conversations with VMware concerning this.  They believe that they will have a fix sometime this month.


Reply
0 Kudos
LFC
Enthusiast
Enthusiast
Jump to solution

Hello

Can you please confirm if the path in the 'Correct Answer' is actually correct?

In the correct answer, the path is listed as, the below (which is relitive to O365 2013)

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

However, in the body of the conversation it is listed as (i.e. no office Version)

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

We are using O365 2016. Could you please confirm the correct exclude registry path?

Thanks

Sean

Reply
0 Kudos
TDJB3
Enthusiast
Enthusiast
Jump to solution

Sean,

The first line is for 2013 and the second line is for 2016.

Dave

Reply
0 Kudos