Depending on the version of Chrome, and how Application Manager is configured with regards to Trusted Ownership, users may find that Google Chrome is blocked (denied) by Application Manager.
Due to the various ways in which Google Chrome can be installed and executed, it is likely that this will be blocked by the Trusted Ownership mechanism of Application Manager
To install Google Chrome in a production environment it is recommended that the "alternate Install" method is used to install Chrome as an Administrator. This allows all users of a particular machine to use Chrome:
Once installed you may notice that Chrome executes but web pages may not display correctly. To fix this issue, simply create a single rule in Application Manager as follows:
Add an Allowed item for Chrome.exe for either "Everyone" or a specific group of users using with Trusted Ownership turned off using one of the following methods:
Accesible File > Chrome.exe - the disadvantage of this is AM will allow any executable called Chrome.exe to execute from the machine. This is not recommended
Accesible File > C:\Program Files\Google\Chrome\Application\chrome.exe - Providing the full path is much more secure than specifying only the application name
Accesible Signature > C:\Program Files\Google\Chrome\Application\chrome.exe - This is the most secure method and will ensure that the hash of the executable must meet that of the pre-created signature. The disadvantage of this method is, depending on how often Chrome is updated you may find that the AM configuration needs to be updated regularly
In later releases of Application Manager, other methods are also available such Metadata for accessible files, or Trusted Vendors.
Note - On 64 Bit machines the above paths can be changed to C:\Program Files (x86) \. . .