Jesus Lopez-1

Normally I would blame defender but the only thing that has changed is the build. As soon as we went to 2312.1 thats when the high CPU started.

Yes I did that and still the same error.

I have the same issue after upgrading from 2312.1 to 2406. I am using server 2019. I had not seen this was already a topic when I created my own.

Anyone else getting high CPU for the connection servers after upgrading to 2312.1? We hoped going to 2406 would fix that bug but it still remains the same. So far it is not affecting services but we have multiple servers all with the same issue after the upgrade. We tested adding more CPU's but that did nothing.

Thanks, the upgrade was successful and no major issues that could not be resolved on the fly.

Hi meant to put event log from the horizon console.

After upgrading from version 2312.1 to 2406 we can see the logs but we cannot download them and sort them. Anyone else have this issue?

Good Morning I was able to get it to work. Thank you all for the help it was combination of everyone response that did it for us. We did not have to use a UAG, the certificate we gave the Connection server had to be from CA and we used a wildcard cert, changes were done to the locked file and on the connection server we had to enable "Blast Secure Gateway for only HTML Access" along with change the url to the dns entry that we created to use so that the server itself would not randomly appear with the certificate error when selecting the VM which was what Victor mentioned on modifying the URLs on the server to math the certificate details since the certificate is a wildcard cert. Below are the changes to the locked file. enableCORS=false checkOrigin=false portalHost.1= url given to access bm portalHost.2= server FQDN allowUnexpectedHost=true

Thanks, I have added benchmarks and the past and like you mentioned it does break random things the same way the the Optimization tool does. Just wanted to see if there wan any template out there before trying again.

We are planning to upgrade from 2312.1 to 2406 soo. For anyone that has made the jump any issues that you may have encountered? When we went to 2312.1 we got all the fun bugs which is the blast protocol not working and the high CPU for all the Connection servers. I have been reading the cyphers are an issue is there a script that will check if they are needed or anything that anyone has encountered after the upgrade? We were down for about 7 hours last time.

I think I was able to get it working. I am going to monitor and make sure the error does not come back. If so Ill post what I did for it to work in case anyone else has the same issue.

Attached are screenshots of the wildcard cert where it shows it picks it up and what is configured on the .locked file along with the cert errors that we are getting. The error is coming from the connection server itself but if we use the dns example vdi.com it logs us in we pick the vm and it works fine no certificate error. At times we go to vdi.com logs us in we select the vm and when it launches we get that certificate error that is attached.

So I made the changes to the CS and I had to make some changes on the locked file in the connection server also. Now the issue is that the connection server is not really accepting the certificate but when I hit the DNS I get no issues. This would not be a problem except that at times the dns takes me to the VM and others it goes into the connection server to obtain the VM. I am using a wildcard certificate from Digicert since that was the only way to remove the initial certificate error when hitting the landing page to log in.

Oh ok that makes sense. So then spin up a UAG and use it and the VM should pick up the Certificate from the UAG. That makes more sense. I was under the impression that the UAG could only be used for external use.