Select virtual environments support Box Drive, Box Sync, Box Tools and Box for Office, subject to a few known caveats. To verify that Box applications work properly, administrators should test 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 | No*** | No*** | Yes* | Yes |
| VDI (persistent) | Yes | Yes | Yes | Yes |
| VDI (non-persistent) | Yes | No | Yes | Yes |
Known Caveats:
* 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 with your app virtualization provider for the appropriate way to package Microsoft Office Plugins.
*** Both Box Sync and Box Drive work only if you're operating them on a client PC, and not on an RDS/Terminal Services server. Also, to save content into 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. There is nothing you need to configure. 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 review the VMWare support site.
Related Links
tech_writers_swarm_kb