This message was deleted.
# citrix-workspaceapp
s
This message was deleted.
e
This is also confusing
Setting Banned to "False" also works. This is from the ADMX:
"<enabledList>
<item key="Software\Policies\Citrix\ICA Client\AutoUpdate" valueName="Banned">
<value>
<delete />
</value>
</item>
</enabledList>
<disabledList>
<item key="Software\Policies\Citrix\ICA Client\AutoUpdate" valueName="Banned">
<value>
<string>True</string>
</value>
</item>
</disabledList>"
So when AutoUpdate is disabled Banned is created and set to True, and deleted when AutoUpdate is enabled. I am tempted to modify the ADMX to create Banned set as True when AutoUpdate is enabled. Just so I do not have to push out that value with GPP. This whole thing feels off though. I refuse to believe I am the first with this problem. CWA AU has been around for a while now.
m
@Eirik Vesterhus / Intility AS Does this also tackle the issue, that I have the feeling, all my Clients' Workspace apps, never seem to receive updates?
We never receive any update notification:
I now altered the ADMX as you suggested, but my 2210 Workspace app still doesn'T show updates, nor can I search for updates.
This is my log, am I excluded because we do Remote PC access and I have the VDA installed on my machine?
========================================
10-5-2023 65417
========================================
2023/5/10 85417 : Information : GetAutoUpdateState (397) : Receiver is running as conventional app
2023/5/10 85417 : Information : IsAutoUpdateDisabledOnVDA (4956) : This is a Pass through installation
2023/5/10 85417 : Information : GetAutoUpdateState (402) : Its a Pass Through scenario. Disable the AutoUpdate
2023/5/10 85417 : Information : GetAutoUpdateState (397) : Receiver is running as conventional app
2023/5/10 85417 : Information : IsAutoUpdateDisabledOnVDA (4956) : This is a Pass through installation
2023/5/10 85417 : Information : GetAutoUpdateState (402) : Its a Pass Through scenario. Disable the AutoUpdate
Boing. Reading the manual explains the product.
FML and scrolling down solves the issue, it now seems to work, omfg
👍 1
e
Took awhile for me to notice that one aswell, hehe. I am still confused by "Banned", though.