Select virtual environments support Box Drive, Box Sync, Box Tools, and Box for Office, with certain services subject to limitations.
To verify that Box applications work properly, have your administrators test the Box applications in their virtual environments before deploying to production.
Supported Configurations:
| Configuration | Box Drive | Box Sync | Box Tools | Box for Office |
| Published apps | No | No*** | No | Yes** |
| Remote Desktop | Yes | No*** | Yes* | Yes |
| VDI (persistent) | Yes | Yes | Yes | Yes |
| VDI (non-persistent) | Yes | No | Yes | Yes |
Limitations:
* Box Tools and the browser you're using must both be running on the RDS/Terminal Server. Also, in virtual environments, we support only Box Tools admin installations via the MSI installer.
** If you're deploying Microsoft Office as a virtual app, Box for Office works only if it's properly packaged and accessible in the virtual app environment. Consult your app virtualization provider for the appropriate way to package Microsoft Office Plugins.
*** Box Sync works only if you're operating it on a client PC, and not on an RDS/Terminal Services server. Also, to save content in Box, you must enable client drive mapping from the RDS/Terminal Services server.
Note: Box Drive automatically detects when you're using it with Writable Volumes as part of VMware App Volumes, and makes the necessary configuration changes to enable it to work seamlessly. No configuration needed on your part. But you must be using Box Drive v 2.1 or later, and VMWare App Volumes 2.15.0 or later. For more information, please refer to the VMWare support site.
Known Issues
-
Incompatibility with Microsoft Server Fair Share Disk Filter for Remote Desktop Server (RDS) installations may cause a session deadlock during Box Drive usage. If you run into this issue, please raise a support ticket for resolution steps.
Related Links
tech_writers_swarm_kb