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*. Citrix workspace app chrome install#
Configuring User settings to force install the application:. Now go to Device Management > Chrome Management > App Management & search for ‘Citrix Workspace’ and click on the application title. Add Citrix Workspace app to your domain:. 
*Note the ‘users’ distinction, as applications can not be forced to a particular device in Chrome. In the case of this guide, we’ll be creating our own OU called ‘ Citrix Lab OU’
Launch the console and goto Device Managementĭefine who is your target organizational unit (OU) for deployment. Pushing the Citrix Workspace application to your users: All the configuration steps below are performed within your google-managed domain and must be done with a user account with these administrative rights. This (short) guide will cover the deployment of the Citrix Workspace (formerly known as Citrix Receiver) Chrome extension on Neverware CloudReady or Chrome OS devices running in a Google Enterprise Managed domain.
0 kommentar(er)
