This article contains information for administrators who want to deploy Box Tools to a large number of computers.
After you install with the .msi installer, people must log out of Windows and then log back in again before Box Tools is enabled for them.
The .msi installation location:
- C:\Program Files (x86)\Box\Box Local Com Server
We recommend the admin installer for mass deployments of Box Tools.
With the .msi installation, Box Edit.exe should be running as the end user and Box Local Com Windows Service.exe should be running as the SYSTEM user as a Windows service.
System Image Deployments
Deploying Box Tools on macOS
User installer vs. Admin installer
We offer two variations of Box Tools on macOS
- user installer (.dmg)
- admin installer (.pkg)
The functionality between the two variations is the same. Additionally, the admin installer is intended for mass deployment by an admin.
The standard Box Tools .dmg installer is available from https://www.box.com/resources/downloads. Next,
If the .app files are not started for a user, the Web app won't be able to verify that Box Tools is installed, and the user will be prompted to install Box Tools when they try to edit a file.
- Copy .pkg installer to
Box Tools uses a loopback network interface connection between the browser (Box.com) and the desktop. This interface may require you to configure your network to support Box Tools.
In addition to the information below, Internet Explorer may require additional configuration.
Box Tools v4:
Box Tools v4 requires browsers (Box.com) to communicate with the Box Local Com Server by making requests to 127.0.0.1:17223 (or 127.0.0.1:17224 if port 17223 is occupied) over HTTP. The ability to communicate to 127.0.0.1 over HTTP is acceptable by following the W3c standard.