This message was deleted.
# citrix-vad
s
This message was deleted.
w
No
You already are crazy
n
D'oh. 😞
d
not needed anymore. you can run the cwa installer with /forceinstall
n
It was a last ditch effort, as /forceinstall is also failing. Something must have gotten corrupted in my Platform layer (App Layering), because I was able to create a new one and install CWA 2006. I just didn't want to go that route.
I went as far as to uninstall VC++, .NET, run RCU, and then reinstall all... nada. Same error at install every time.
d
I'd recommend to wait with CWA 2006, there might come a fix very soon...
n
I saw the same thing with CWA 2002, and am about to try 1912 just to rule out one of the newer CWAs.
d
just saying: CWA 2006 has an issue and they are working on it
n
Already? lol. What issue?
d
detection of the CWA doesn't work if going through gateway to a Storefront Webstore
n
1912 LTSR failed, too, so it's definitely my layer. But that issue you posted is a hard stop for me, so I appreciate that.
I swear to god we're never going to be able to get off this god damn receiver client at this rate.
Out of curiosity, how consistent is that issue? We have that same setup, and I haven't had issues with client detection on CWA 2006 yet.
d
Not sure what exactly are the parameters to trigger the issue. But I worked with the engineers this morning and they just informed me, they identified the bug and therefore stopped auto update. So I suspect it might be an issue for a couple of folks.
n
They literally just pulled the download and docs for 2006.
d
that escalated quickly 😯
n
Progress. Tried building this layer based on a different OS layer, and was able to get it to install. Looks like my latest Windows Update revision OS layer is causing the issue.
@dready: Heard that the fixed CWA will be released tomorrow.
👍 1