Box Desktop Applications And Installers: IT Instructions for Large Scale Silent (MSI/DMG) Installations

Follow

·

Get Training

Some Box desktop applications can be installed to a large number of computers by an administrator through programs such as Group Policy for Windows and Casper Suite for Mac.  Typically this is done by an MSI or DMG installer, or with instructions for how to do a silent install.

 

Deploying Box Sync

You can install Box Sync by downloading the install file from one of the following locations

Windows:

Mac:

    • Administrators can install the Box Sync DMG file for Mac users within their network.
    • The deployment differs based on the bootstrapper installation. View the /Library/PrivilegedHelperTools/ directory to verify if the com.box.sync.bootstrapper bootstrapper is installed.
      • If the bootstrapper is already installed in the user's system, the user can download and run the Box Sync DMG file at a later time without requiring administrator access.
      • If the bootstrapper is not installed in the user's system, follow this process:
        1. Copy the application bundle to the desired install location on the user's machine.
        2. Copy the bootstrapper from the application bundle to /Library/PrivilegedHelperTools/.
        3. Run the following command at the root level:
          sudo <path to bundle>/Contents/Resources/com.box.sync.bootstrapper --install

 

Deploying Box Edit

Windows

Note: After installation, logged in users will need to log out and log back in again before Box Edit will be enabled for those users.

Mac

 

Box Edit DNS and Proxy Configuration Guidelines

Box Edit originally used a plugin to allow communication between the browser and a desktop application. This plugin architecture is being aggressively deprecated in browsers, and will be deactivated entirely by the Chrome browser in September. The new version of Box Edit (v3) uses a loopback network interface connection rather than a plugin to communicate between the browser and the desktop, which may conflict with the DNS, proxy, and other network access configurations. 

If you're having trouble with Box Edit v3, make sure your user networks are configured to allow browsers to reach the boxlocalhost.com domain on https port 17223 or 17224, which resolves to 127.0.0.1. 

Below are a list of requirements and suggested mechanisms for configuring your DNS and proxies.

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, 5)=="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 7: 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: 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) 

 

 

Box for Office

Windows Only

  • We support pushing Box for Office as an unattended installation using an MSI.
  • Ensure that prerequisites are installed separately, prior to running the MSI:

 

Box also provides two different scripts for system administrators to remove Box for Office installations. One script removes the old Box for Office as well as the new Box for Office (https://app.box.com/s/9053q4mml05f43y7dwmd). The other script removes the old Box for Office but leaves the new Box for Office installed (https://app.box.com/s/4nxq3b94rd6beaag769p). The following procedure can be used to uninstall Box for Office installations: 

  1. Open the Group Policy Management Console.
  2. Expand Forest, Domains, and the domain. Right-click Group Policy Objects, and then click New.
  3. In the New GPO dialog, in the Script Name field, type Box for Office Uninstallation. Click OK.
  4. Right-click Box for Office Uninstallation under Group Policy Objects, and then click Edit.
  5. In the Group Policy Management Editor window, expand Computer Configuration > Policies > Windows Settings, and click Scripts (Startup/Shutdown).
  6. In the right pane, right-click Startup, and then click Properties.
  7. In the Startup Properties window, click Show Files...
  8. Download the uninstallation script, and save it to the folder that Show Files... opened. The script requires administrator privileges. To remove both new and old versions of Box for Office: https://app.box.com/s/9053q4mml05f43y7dwmd. To remove only old versions of Box for Office: https://app.box.com/s/4nxq3b94rd6beaag769p.
  9. Close Windows Explorer, and return to the Startup Properties window. Click Add...
  10. In the Add a Script dialog, in Script Name, click Browse..., and select the script you saved in the previous step. Click OK.
  11. In the Startup Properties window, click Apply, and then OK. Close the Group Policy Management Editor window.
  12. In the Group Policy Management Console, link the GPO to the domain or any organizational unit. 

 

 

Silently installing an MSI

See instructions at http://msdn.microsoft.com/en-us/library/windows/desktop/aa372024(v=vs.85).aspx

 

Was this article helpful?
8 out of 10 found this helpful