Chrome

The primary method for installation of the DOI Google Chrome package is using the DOI Google Chrome application in the DOI software library folder in MECM. The programs are restricted to run on Windows client operating systems (Windows 7/8/10, x86 and x64). It will not install on Windows server operating systems.  You can find the most current application under \Software Library\Overview\Application Management\Applications\_DOI\Tier 1

MECM: Distribute and Deploy the 1-DOI-BisonConnect 78.108.0 (x64) or newer application

1. Distribute the content to your distribution point
2. Deploy the application to your preferred Device Collection

Step by step instructions, with screenshots, on how to distribute and deploy a DOI application can be found here.

Note: Only systems that are not managed with MECM will need to use the manual installation method. (BWTST has not tested and is not supporting the use of group policy to deploy this package.)

Please note, if you are following these instructions to fix an issue with Chrome, first uninstall Chrome and then delete the following directory before continuing: Example: C:\Users\USER\AppData\Local\Google\Chrome

1. 1. Browse to \\iinsxfcmfs01.doi.net\sccm_source$\DOI\Software\Tier1\Google\Chrome
   2. Download the most current 64bit application
   3. Copy the content locally. In this example, the files have been copied to D:\DOIGoogleChromeInstall:
   4. Open an Administrative cmd prompt. (Even if you are logged on to a Windows 7/8.1/10 computer as an administrator, you MUST still open cmd in “Run as administrator” mode, otherwise pieces of the installation will fail).
   5. At the cmd prompt, browse to the directory where the install files were extracted, and run “BisonConnect_Install.bat” The installation runs silently. An installation log can be found at: C:\SoftwareLogs
   6. A new shortcut will be placed on the all users desktop – DO NOT OPEN UNTIL THE USER CONFIG PORTION IS COMPLETE:

1. Open a new cmd prompt, under the primary user’s regular credential. Browse to the directory where the install files were extracted, and run user_config.bat
2. The user config script sets Chrome to be the default mailto handler for the system.

Chrome can be obtained directly from Google at: https://www.google.com/intl/en/chrome/browser/

If a previous install of Chrome/Bison Connect is left open during the MECM application install, the install will fail and may get stuck in a failure cycle.

If you notice a BisonConnect install is initiating on your computer, the BisonConnect icon on your desktop should disappear when this is happening and then re-appear on your desktop when it is safe to use the product again.  During that time you will have to avoid going into chrome (not just email but also browsing the internet).

After a successful Chrome install, the program files directory should look like the following:

If you notice a second exectuable called new_chrome.exe and see folders for the older version of Chrome, your install was unsuccessful.  If you experience failures after installing the Bison Connect MECM application, follow these steps to repair the install.

1. Close out all running Chrome instances on the system. Also check task manager and kill off any chrome.exe processes.
2. Rename chrome.exe to old_chrome.exe
3. Rename new_chrome.exe to chrome.exe
4. Delete the old folder(s) from previous version
5. Delete old_chrome.exe
6. Re-run the Bisonconnect application in MECM Software Center (the detection logic will now work and it should succeed)
7. Launch Bisonconnect

If Chrome/Bison Connect consistently crashes after a few seconds upon opening, there is likely a corrupt file in the users profile.

This can be caused by a corrupt extension or another profile specific file that has become corrupt.

To stop chrome from crashing, you can delete the part users locally stored profile by using the following process:

• Close out all running Chrome instances on the system. Also check task manager and kill off any chrome.exe processes.
• Go to “C:\Users\”UserName”\AppData\local\Google\Chrome\User Data\”
• Rename the folder called “Default” to “Default.old”
• Go to the “Default.old” folder
• Copy the “Bookmarks” file
• Launch the Chrome/Bison Connect application
• A new “Default” folder should be created (the user will need to sign into their Email account again)
• Paste the “Bookmarks” file that was copied into the new “Default” folder
• Close then relaunch the Chrome/Bison Connect application
• The users bookmarks will be restored and the crashing issues will likely be resolved

The Chrome STIG GPO is linked to the regional OU levels of eAD and will be applied to systems within the domain. Changes to the GPO will be vetted through both the DOI Client CAB RFC process and the USGS eAD CAB RFC process.

Instructions coming soon.

Instructions coming soon.

It’s easy to add approved extensions to your Google Chrome web browser. Just follow these steps:
1. Click on a link for approved extensions listed here or visit the Google Chrome Web Store and search for an extension using the search bar as shown below:

2. Click on the extension you would like to add – more information will appear
3. Click the Add to Chrome button located on the right-hand side of the window as shown below: