I’ve been a bit busy lately, but I am finally getting around to writing a few more in-depth articles that will hopefully be published in the near future. However just for a quick update, I’d like to share a tip about using Google Chrome with AppSense Environment Manager Personalization.
When whitelisted in Personalization Server, you may notice that chrome.exe doesn’t actually capture any Personalization settings. The reason for this is the “sandbox” setting in Chrome itself. It doesn’t play well with Personalization Server. I’ve just done a little bit of work with a client where just about everyone used Chrome for Internet browsing, so it would have been a major PITA for them if AppSense couldn’t personalize it.
However, there’s a simple solution. Just edit the properties of the Google Chrome shortcut and add –no-sandbox after the executable path in the Target box (with a space before the first hyphen).
Apparently running Chrome in this configuration opens up some browser flaws, however, so if security is of paramount importance you may want to reconsider your use of this browser alongside AppSense Environment Manager.
Share
