This article contain important instructions and considerations for admins who want to deploy Box Edit to a large number of computers. 

 

 

Deploying Box Edit on Windows

These instructions apply to physical Windows environments. While Box Edit may work in a virtual environment, including VDIs, there are certain known limitations. For more information, see Using Box in Virtual Environments.
  
Before installing, make sure that you've installed both .NET 4.0 Client Profile and .NET 4.0 Extended (go.microsoft.com/fwlink/?LinkId=181012) on all machines. The Box Edit MSI will not install these automatically. (Microsoft ended support for .NET framework 4.0, 4.5 and 4.5.1 on Jan 12 2016. We encourage customers to upgrade to the latest version of .NET in order to continue receiving technical support)
Note: After installation using the .msi, logged in users will need to log out and log back in again before Box Edit will be enabled for those users.
 
System Image Deployments
If you are using a system image to deploy Box Edit, verify that the Box Edit Documents folder on your source machine (C:\Users\[USERNAME]\AppData\Local\Box\Box Edit\Documents) is empty before capturing the image.
 
MSI vs EXE:
There are a few important differences between the .msi installer and the .exe installer for the Windows version of Box Edit. Having both versions installed on one computer can lead to problems with Box Edit. Before deploying the .msi, we highly recommend that Admins ensure that the .exe version is not installed on their users' machines
 
We provide a script that can be deployed via Group Policy to remove the per-user (.exe installed) version of Box Edit prior to installing the .msi version. The script verifies that the user has installed the per-user version of  Box Edit and if so, proceeds to uninstall it. The script can be downloaded from https://app.box.com/s/wibflm4qm8sgahy09fek
 
MSI
The multi user .msi installer installs Box Edit for all users on the computer and requires admin privileges to be installed.
 
The single user .msi installer requires admin privileges but is intended to be installed on a machine with a single user. Multiple users logged into the machine simultaneously will cause issues and unexpected behavior. If the target system may have multiple users, the multi user Admin Install of Box Edit should be used.
 
When installed with the .msi, Box Edit is installed into the following locations:
  • C:\Program Files (x86)\Box\Box Edit\Box Edit.exe
  • C:\Program Files (x86)\Box\Box Local Com Server\Box Local Com Windows Service.exe
The .msi is intended to be used only in certain circumstances: 
  • Multi-user computing environments
  • Virtual environments
  • Mass deployments of Box Edit by IT administrators
The .msi installed version will not work with browser modes that do not support cookies (Incognito, Private Browser, or InPrivate modes). 
 
EXE
The .exe installer installs Box Edit only for the current user and does not require admin privileges to be installed. The .exe installer will install Box Edit into the current user's profile: 
  • C:\Users\<USERNAME>\AppData\Local\Box\Box Local Com Server\Box Local Com Service.exe
  • C:\Users\<USERNAME>\AppData\Local\Box\Box Edit\Box Edit.exe
The .exe installer is intended for single user environments where there are no plans to deploy Box Edit with the .msi and can be found publicly available here: www.box.com/box-for-devices
 

Deploying Box Edit on Mac OS X

The DMG Mac installer (https://e3.boxcdn.net/box-installers/boxedit/mac/currentrelease/BoxEditInstaller.dmg) is designed to work with Mac deployment tools, such as Casper Suite. A Casper install of Edit requires the Box Local Com Server to be launched upon startup. See Deploying Box Edit with Casper for more info.
 
Prior to installing anything, the installer will do any necessary uninstalling, getting rid of any outdated plugins and .app files that might cause problems with Box Edit. The installer will then create the folder "~/Library/Application Support/Box/Box Edit/" and add the .app files "Box Edit.app" and "Box Local Com Server.appto that directory.
 
After this, the installer will launch both .app files, making sure that they are both running before exiting the installation. The .app files will register themselves to start up at login time for the user that they're running for.
 
Note: If the .app files are not started for a user, the web app won't be able to verify that Box Edit is installed, and the user will be prompted to install Box Edit when they try to edit a file. If you are using a deployment tool other than Casper Suite, or deploying Box Edit using a custom installer, be sure that the two .app files have been placed in the appropriate directory, and be sure to either start running them (as the user who will be logging in to that particular machine) or set them up to start running at login.
 

Box Edit DNS, Proxy, and Browser Configuration Guidelines

Box Edit uses a loopback network interface connection to communicate between the browser and the desktop. This interface may conflict with DNS, proxy, and other network access configurations. 
 
If you're having trouble with Box Edit v3, make sure your users' networks are configured to allow browsers to reach the boxlocalhost.com domain, which resolves to 127.0.0.1. 
 
Below are a list of requirements and suggested mechanisms for configuring your DNS and proxies.
 
Note: Internet Explorer may require additional configuration to allow Box Edit to work. Please see the Box Edit Internet Explorer Configuration Guide for more information. 
 
DNS: 
If the networking system filters or selectively caches DNS responses:
  • The domain *.boxlocalhost.com must be allowed to resolve. 
  • If wildcards are not allowed, edit.boxlocalhost.com must be allowed to resolve. 
Proxy: 
If the proxy configuration is specified by a PAC file or a wpad.dat file (i.e., a PAC file published via DNS WPAD discovery), the domain *.boxlocalhost.com should be allowed to connect DIRECT.
 
An example PAC file code snippet: 
 
// If the protocol or URL matches, send direct.
if (url.substring(0, 6)=="https:" && shExpMatch(url, ".boxlocalhost.com"))
        return "DIRECT";
 
Note: "Direct" should be in all uppercase: DIRECT
 
If the proxy is not configured through a PAC/WPAD file, but through DIRECT configuration in the operating system:
 
On Windows: Add an exception for *.boxlocalhost.com 
  1. Navigate to Control Panel > Internet Options > Connections > LAN Settings (or Settings for a selected Connection) >Advanced 
  2. Add *.boxlocalhost.com to the box under Do not use proxy server for addresses beginning with.
For more information, you can visit: https://technet.microsoft.com/en-us/library/dd361953.aspx 
 
 
 
On Mac OS: Add an exception for *.boxlocalhost.com 
  1. Navigate to System Preferences > Network > Advanced… > Proxies.
  2. Add *.boxlocalhost.com to the box under Bypass proxy settings for these Hosts & Domains.
(screenshot from Mac OS X 10.10.3)