This message was deleted.
# citrix-vad
s
This message was deleted.
🤨 1
👍 3
r
In a lab? I’ll wait about 1 week for my lab just in case.
Wasn’t this the main thing that was a pain? When you attempt to connect to a VDA running version 2203 on a multi-session OS, the logonui.exe process might become unresponsive with a black screen or get terminated. However, event logs might appear. [CVADHELP-20338]
d
I'm going lab first, then production on Sunday, assuming nothing pops up in the lab.
👍 1
r
Keep me posted man
d
There are a lot of things that are a pain for us and I have to get it pushed out for license server upgrade in order to upgrade XenMobile on-site. Played with the pre-release version version already as well in the lab without issues, so I'm fairly comfortable with it. We have a long standing ticket for Windows Search issues that we need to get on current supported release to get Citrix to really get involved in helping troubleshoot and CU1 with private hotfixes has been the only stable release, but need to go with CU2 to really put the hammer down on testing.
I'll let you know how things go, in this thread.
r
Good luck , and I appreciate the communication
👍 1
f
Pushed on preproduction Friday morning, works fine
👍 2
d
Had issues with Storefront upgrades due to Performance counters that I'm not sure how they got corrupted, but other than taking a while to figure out the issue in test and working through it in production, it went pretty smooth. Director was a non-issue, no problem upgrading. Test delivery controllers had no issue upgrading. Then hit the first production site upgrade and it died a horrible painful death. Reverted the DB and checkpoints. Will schedule with Citrix before attempting again. Never had an issue with the DB upgrades in the past, and this just took out the entire site. Was an interesting time. VDA upgrades went fine on the few test and (internal - non-client) production systems pushed to. Will monitor for issues there as well.
🙏 1
Upgraded two sites successfully with no issue using Set-LogSite –State “Disabled”. The KB says Enabled or Disabled should work, but was set to Enabled, not Mandatory, already when failed.