Are the LTSR 2402 CU2 download links broken for ev...
# citrix-vad
d
Are the LTSR 2402 CU2 download links broken for everyone else? This gets me a Page Not Found error: http://www.citrix.com/downloads/citrix-virtual-apps-and-desktops/product-software/citrix-virtual-apps-and-desktops-2402ltsr-cu2.html
😲 1
p
Hmmm. Literally just built a bunch of images with CU2 and it does seem to have been disappeared...
m
downloaded it yesterday, today its missing.
image.png
j
I have copies, but do we have information on if there are issues with the binaries, or just issues with the SDN download site.
k
I'd hold off. According to this there's an expired cert in the build, which can cause site-level failures: https://support.citrix.com/s/article/Citrix-Virtual-Apps-and-Desktops-2402-CU2-expired-certificate?language=en_US
m
nice..........................
image.png
p
Well that's just lovely.
m
File: [ISO]\AutoSelect.exe // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\AutomatedConfiguration\AutoConfig_PowerShell_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\ADIdentity_PowerShellSnapIn_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\ADIdentity_Service_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Analytics_PowerShellSnapIn_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Analytics_Service_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\AppLibrary_PowerShellSnapIn_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\AppLibrary_Service_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Azure_RM_Plugin_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Broker_PowerShellSnapIn_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Broker_Service_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Citrix.Provisioning.Gcp.Installer.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\CitrixPrivilegedService_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\ConfigMgr_WOL_Plugin_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\ConfigSync_Service_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\ConfigurationLogging_PowerShellSnapIn_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\ConfigurationLogging_Service_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Configuration_PowerShellSnapIn_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Configuration_Service_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\DelegatedAdmin_PowerShellSnapIn_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\DelegatedAdmin_Service_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\EnvTest_PowerShellSnapIn_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\EnvTest_Service_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Host_PowerShellSnapIn_x64.msi // Expiration Date: 03/08/2025 005959 File: [ISO]\x64\Citrix Desktop Delivery Controller\Host_Service_x64.msi // Expiration Date: 03/08/2025 005959 etc etc..
d
worked yesterday morning
j
Yes, they found the problem last night.
d
well VDA download worked yesterday morning
p
I got this from our account TA. "_What are the implications/areas of impact for customers that have already deployed CU2 VDAs or otherwise upgraded components in their environment? Will they need to re-deploy the new build?_ >> Yes, customers will need to redeploy unfortunately since multiple files are affected. Implications could be backend scripts not running (config sync), wdac preventing files from loading, lhc not working..." I guess i'm rebuilding the images i built yesterday.
🤯 3
d
🙂
well shit... I am glad I only updated one image 😄
so much for using LTSR
p
At least my images are in non-prod testing. Frustrating though.
d
The only reason I updated was because I was troubleshooting an issue that turned out to be unrelated 🤦‍♂️
c
What is the purpose of "Trending Topics" on the home page of support.citrix.com or browsing to Citrix and not seeing this in the Urgent or Trending area for issues like this? Seems like the perfect spot for it
👍🏻 1
💯 3
m
is this releated to VDA only? or also DDC components?
j
everything on the is
iso
And it looks like the VDA only exe are also compiled with the wrong cert
j
Just extracted some files and the brokeragent.exe from the ISO is also signed with the expired one from 8th march 😵
m
nearly every msi or exe is, see my list above
💯 1
e
Well, I'm going to have to update 20 remote PC's including my own. First had to deal with 2411 and 2402 CU1's HDX Webcam driver crashing just about any program that accesses webcams and now the fix breaks 1 month later. I guess it could be worse and have to update all of our VM's
m
This is what I get waiting about a month to deploy a CU. Now I need to recalibrate to 2 months!
m
This is from my 2411 DDC... Are we screwed? #AskingForAFriend
m
can sbdy explain why the cert in 2402CU0 is valid and in 2402CU2 is invalid? Cert has the same thumbprint, Base64 of both certificate and intermediate certificates are identical EDIT => The timestamp is missing, so it cannot be checked if the cert was valid while signing.
👀 1
👍 1
The timestamp is missing, thats the issue. It worked as long the cert was valid. (Here compared to CU0 where the timestamp was there)
m
Not that I am complaining, but I only upgraded the VDA and haven’t seen any issues. Hoping they release the fix soon.
m
Existing Citrix Virtual Apps and Desktops CU2 customers can proceed with their deployment, while all new deployments and upgrades should use this Citrix Virtual Apps and Desktops 2402 LTSR CU2. That means all sites that are on CU2 already have to use the non-signed files and wait on CU3?!
m
That is bizarre if true
j
I would upgrade, since it looks like they upped the build number, so it should be viewed as an update.
m
youre correct. but then i dont get this statement posted above..
m
I don’t think the storefront standalone .exe link has been changed
a
Great job with verbiage Citrix, "Issue reported in CTX692777 is addressed with latest version of CU2 release. Customers can upgrade to this new version. Existing CU2 deployments will continue to function." So upgrade to newest release if you're already on CU2 or not? EDIT: From my AM's internal resources: • VDAs with old-CU2, do not need to be upgraded. Although we suggest using the new binaries, they could continue to use old-CU2 VDA s/w. • Any customer that installed DDC with old-CU2, MUST upgrade to the new CU2 for the LHC fix • Upgrade Web Studio if not installed on Delivery Controllers • Upgrade FAS • Not affected and do not require an upgrade: Storefront, license server version 51000, PVS
m
i updated a CU2 site yesterday, no issues.
a
Article is updated to include updates to VDA and Delivery Controllers only: https://support.citrix.com/s/article/CTX692777-citrix-virtual-apps-and-desktops-2402-cu2-expired-certificate?language=en_US EDIT: I'll add you'll need to upgrade Web Studio if it's not installed on your Delivery Controllers, as well as upgrade FAS.