This message was deleted.
# citrix-netscaler
s
This message was deleted.
c
Hey leee hope your good take a look at this i used the md5 hash

https://youtu.be/Fkrx1DpxBAU▾

l
Cheers John. I'll have a look mate. I eventually settled on checking for the "Citrix Workspace Updater Service", obviously if that's there then you have it installed.
If this is more accurate though, I'll use it.
@c4rm0 my particular requirement is to make sure the client is workspace app or above to allow optimisation for teams.
c
Ahhh ok m8 my method looks for the md5 hash of a specific version if your not on that version you dont pass the EPA. You could probaly tweak the EPA expression with the md5 hash of other versions and use the or || statement
l
I originally went with the version reg entry under the Dazzle key but the versions are documented anywhere and it's a string value so the > or < operators don't work. Strangely I could get notcontains to work either though. When checking for hdxteams.exe or teamsrtc.exe it error with something to do with security. Been going round the houses with this one.
j
I looked at exactly the same issue with EPA scan and workspace version >= 1912 awhile back without success. I’d be interested to see if you make better progress. I can’t believe that more people don’t require this with non-managed BYOD devices for msteams optimisation. @Dennis has created a great powershell toast notification to attack this from “within” the VDA/session. It would be handy to solve at Netscaler source too.
l
The best way I've found which is 100% successful is to check for the "Citrix Workspace Updater Service" introduced in CWA 2010. I tried looking for hdxteams.exe inside the ICA Client folder with limited success across BYOD endpoints. Users will just have to upgrade to a release of 2010 or above that includes the service. Its frustrating that the OPSWAT library doesn't contain a check for reciever. This coupled with the reg entry thats disables teams fallback when there is no optimisation should do the trick though.
👍🏻 1
A cool way to work around these limitations would be to allow a script to be passed yo the client as a payload and executed before the EPA scan. We could then code anything to produce a file or reg output that could then be EPA scanned.
j
Only frustration with the ‘disable teams fallback’ reg key is that this only works with newer workspace versions!!!! Unlike Skype fallback, the client actually needs to be capable of optimisation before the regkey will work, which seems bonkers to me as what is the point? But was told this by Citrix and MS. 100% agree that the EPA scan process need a proper update/rewrite.
l
I'll be feeding that back too