Search the VMware Knowledge Base (KB)
View by Article ID

Microsoft Office 365 32-bit version does not work with Writable/AppStack volume on 64-bit version operating systems in VMware App Volumes (2145079)

  • 3 Ratings

Symptoms

When you are using Microsoft Office 365 32-bit version with Writable/AppStack volume on 64-bit version operating systems in VMware App Volumes, you experience these symptoms:

  • The Macro-Record and Visual Basic features do not work in excel.
  • Word loses functionality, specifically the Save As dialog box does not show any locations to save to.
Note:

VMware App Volumes may restrict the functioning of other Microsoft Office 365 32-bit version applications.
This issue is fixed in App Volumes 2.12.1

Cause

This issue occurs due to the interference caused by launching the Microsoft Office 365 32-bit version by App Volumes Agent on 64-bit operating systems.

Resolution

To resolve this issue, update the snapvol.cfg file.

Writable volumes:

  1. Attach writable volumes to a virtual machine.
  2. Log in to the virtual machine as the administrator.
  3. Open the computer management on the Windows machine.
  4. Go to Storage > Disk Management.
  5. Right-click CVWritable and click Change Drive Letter and Paths.
  6. Assign a drive letter to the CVWritable.
  7. Copy the snapvol.cfg file from the root folder of CVWritable and paste it on other location, such as desktop.
  8. Open the snapvol.cfg file using a text editor.
  9. Add this entry:

    ################################################################
    # Office 365 Virtual Registry exclusions
    ################################################################

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


  10. Save and close the snapvol.cfg file.
  11. Zip the snapvol.cfg file.
  12. Go to the App Volumes Manager.
  13. In the Volumes tab, click Writables tab and click Update Writables.
  14. Upload the snapvol.cfg.zip file to Update Writable volume.

AppStacks:

  1. Attach AppStack to provisioning machine.
  2. Log in to the Provisioning Computer.

    Note: Ensure that the pop-up window displays information that you are now in the provisioning mode.

  3. Open the computer management on the Windows machine.
  4. Go to Storage > Disk Management.
  5. Right-click CVApps and click Change Drive Letter and Paths.
  6. Assign a drive letter to CVApps.
  7. Copy the snapvol.cfg file from the root folder of CVApps and paste it on other location, such as desktop.
  8. Open the snapvol.cfg file using a text editor.
  9. Add this entry:

    ################################################################
    # Office 365 Virtual Registry exclusions
    ################################################################

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

  10. Save and close the snapvol.cfg file.
  11. Install applications and finish Provisioning AppStack.
  12. Test AppStack functionality.
  13. Repeat same steps for remaining AppStacks.

Note: This issue is fixed in App Volumes 2.12.1. This resolution does not need to be applied when using App Volumes 2.12.1

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 3 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 3 Ratings
Actions
KB: