In our lab instance of the environment, we’re using an windows-based and internally hosted CA to issue SSL certificates. BONUS Step: Deploying an Active Directory based internal certificate (or any certificate) to your ChromeOS devices.Click ‘ UPLOAD CONFIGURATION FILE’ and browse for your file:.Create a text file with the following details, substituting the URL and name for your actual environment. Create your policy configuration: For reference, our configuration to simply just point the app to our storefront environment is below.There is a nifty Citrix Workspace app for Chrome & HTML5 configuration utility which will do all the legwork for you. We can use the console to also configure a policy that contains a ton of settings on how the client will experience your Citrix environment, which we won’t cover now. Automatic configuration of your storefront or access gateway on the clients :.Here’s how we’re configured for reference: Configure Citrix Workspace application settings:įind your OU and configure the settings to your needs, making sure to ‘Force Installation’ and override inheritance if & where necessary.*For further reading on distinguishing between Chrome Workspace behavior in the 3 different configurations, see the blog article written here. (For the context of this article we’ll be using User settings since we want users to receive the application within their logged on session.) Once loaded, we’ll see a screen like below, with 3 categories of configurations User settings, Public session settings, and Kiosk settings*.