[Citrix Workspace app for Android on a managed Chromebook]

It is no longer the way to go.  Stick to workspace app for chrome. 

[Citrix Workspace app for ChromeOS on a managed Chromebook Network printing does not show in Windows]

I’m assuming you mean in session?  The only in session printer that will work for ChromeOS is the Citrix PDF printer, which will map back to any of your managed printers on chrome os, including network printers. However, no other printers will show up in session.  When printing from a published app you will use the citrix pdf printer. 

[always on vpn before windows logon with user certificate as user tunnel]

I’m going to say no, because you have to enable the client certificate policy on the AAA. Not sure the AOService is going to react well to that, and you can not split out to multiple gateways. 
However, if you are looking to do a seamless machine to user tunnel transition if you have Azure AD you could either AAD join or Hybrid join the machine to the Azure AD tenant, then set the next NFactor after AOService to SAML.  I have an EPA scan looking at the registry to determine hybrid join status and if successful using SAML, if not then fail back to LDAP. 

[How do I change the Client name on a specific store using Storefront 3.12?]

Are you changing to a static client name?  If so you can change the default.ica of the store.  You can also use a rewrite rule if you are using the Citrix ADC(Netscaler) to make the modifications on the fly.  

[Clientname not setting when enterprise enrolled]

Issue corrected by re-enrolling device into enterprise policy. 

[Chrome Workspace 19.10.0.27 touchmove scrolling wont work without touch-events flag enabled]

Tested functionality against Windows Workspace app 1909. Functionality parity is pretty close between OS’s

[Chrome Workspace 19.10.0.27 touchmove scrolling wont work without touch-events flag enabled]

Issue confirmed to be fixed in Workspace 19.11.x.x released 11/15. Thank you Citrix team. 

[Chrome Workspace 19.10.0.27 touchmove scrolling wont work without touch-events flag enabled]

Bug Submitted: https://bugs.chromium.org/p/chromium/issues/detail?id=1014448

[Chrome Workspace 19.10.0.27 touchmove scrolling wont work without touch-events flag enabled]

Thanks Nick good call on Shruthi she was a huge help with an SSO issue with workspace. I’ll also post over there in google forum.  

[Chrome Workspace 19.10.0.27 touchmove scrolling wont work without touch-events flag enabled]

When running ChromeOS 74.0.3729.159 or higher, Published applications on XenApp 7.15 LTSR and Storefront 3.12 require the flag chrome://flags/#touch-events to be set to Automatic in order for a touchmove scroll to occur (for example, scrolling through emails in Outlook by dragging your finger).  This has been tested with a few Win32 apps with the same behavior.  Once enabled, apps perform as expected.

 

Is this a documented issue and if so what is ETA for remediation.

[Chromebook kiosk mode battery status]

Looking into that.  Regardless of session desktop, virtual desktop, or published app it’s going to take up the whole screen because of kiosk mode. I’m looking to see if it’s possible to hang the indicator off of the session window. 

[I need help solving an issue with Chromebook in Kiosk mode to publish applications.]

First, turn off auto desktop launch on storefront. Then, in script.js in the storefronts custom web folder add in this code and replace AppName with the name of your published app:

 

CTXS.Extensions.noteApp = function(app) {

 

    if (app.encodedName.indexOf('AppName') != -1) {

 

        CTXS.ExtensionAPI.launch(app);

 

    }

 

};

[Auto login for Citrix Reciever in Chromebox Kiosk mode]

Anonymous store is your only option at this time for Kiosk mode.  There is no pass through SSO like Windows client unless you use SAML, but that would require the user to log in. 

[Chromebook kiosk mode battery status]

[Chromebook kiosk mode battery status]

I modified my storefront for this exact case. Add this custom code to Script.js on Storefront 3.x. 

 

This displays clock and battery life for Workspace on chromeos. Note: Battery isn’t supported for Windows client, but clock will work. 
 

 

(function () {

    var div2 = document.createElement("div");

    document.getElementsByTagName('body')[0].appendChild(div2);

    div2.outerHTML = "<div id='txt' style='height: 50px; width: 150px; color: white; top: 0; left: 60%; border-left: 2px solid white; border-right: 2px solid white; border-bottom: 2px solid white;  background-color: #1378a6; font-size: 18px; font-family: Segoe UI, sans-serif; position:fixed; cursor: pointer;text-align:center'></div>"; 

    startTime();

function startTime() {

  var today = new Date();

  var h = today.getHours();

  var m = today.getMinutes();

  var s = today.getSeconds();

  m = checkTime(m);

  s = checkTime(s);

    

  document.getElementById('txt').innerHTML = "<b>The Time is Now <br>" + h + ":" + m + ":" + s +"</b>";

  var t = setTimeout(startTime, 500);

}

function checkTime(i) {

  if (i < 10) {i = "0" + i};  // add zero in front of numbers < 10

  return i;

}

}());

 

 

 

 

var div3 = document.createElement("div");

    document.getElementsByTagName('body')[0].appendChild(div3);

    div3.outerHTML = "<div id='batt' style='height: 50px; width: 150px; color: white; top: 0; left: 75%; border-left: 2px solid white; border-right: 2px solid white; border-bottom: 2px solid white; background-color: #1378a6; font-size: 18px; font-family: Segoe UI, sans-serif; position:fixed; cursor: pointer;text-align:center'></div>";

 

 

navigator.getBattery().then(function(battery) {

  var battDiv = document.getElementById('batt');

  var battL = battery.level;

  battL= battL.toFixed(2);

  document.getElementById('batt').innerHTML = "<b>Battery <br>" + battL*100 +"%</b>";

  if (battery.level > .75){

    battDiv.style.backgroundColor='green';

        battDiv.style.color='white'; 

  }

  else if (battery.level > .5){

      battDiv.style.backgroundColor='yellow';

      battDiv.style.color='black';

  }

  else if (battery.level > .25){

    battDiv.style.backgroundColor='orange';

    battDiv.style.color='white'; 

  }

  else {

    battDiv.style.backgroundColor='red';

    battDiv.style.color='white'; 

}

 

  battery.addEventListener('levelchange', function() {

    var battDiv = document.getElementById('batt');

    var battL = this.level;

    battL= battL.toFixed(2);

    document.getElementById('batt').innerHTML = "<b>Battery <br>" + battL*100 +"%</b>";

    if (this.level > .75){

    battDiv.style.backgroundColor='green';

        battDiv.style.color='white';

    }

    else if (this.level > .5){

      battDiv.style.backgroundColor='yellow';

      battDiv.style.color='black';       

    }

    else if (this.level > .25){

    battDiv.style.backgroundColor='orange';

    battDiv.style.color='white';

    }

    else {

    this.style.backgroundColor='red';

    battDiv.style.color='white';

    }

 

    

  });

});

 

[Clientname not setting when enterprise enrolled]

Yes it is. The account is a standard account in google enterprise that is federated to Azure AD for SSO. 

[Clientname not setting when enterprise enrolled]

I am in the process of evaluating ChromeOS with Citrix Workspace App for Chrome to replace Windows based laptops for my end users.  In speaking with my account management and sales engineers from Citrix, I was told that an enterprise enrolled chromebook with a force installed Citrix Workspace app will change the chrome client name to the Google Directory API ID, prefaced by CR-. I see that config in configuration.js on my 3.12 storefront.  The issue here is that the client name does not set.  Instead, the client is HTML-####-#### .  I have a use case where a persistent client name is required for one of my applications, so I need to get this working.  I have the Allow API access checked in Google Admin because I provision users through Azure AD, and SSO is through Azure AD.  Storefront is configured to SAML (Azure AD).   Storefront web.config is stock as well as configuration.js for HTML5.  Anything else i need to set through storefront or google policy?  

Thanks all!