OpenSSL is patched on this version
So the choice I have is upgrade to this version or do a another upgrade in 6 months when 5.2 is end of support or take the plunge on v6.0.1.
for those that went for this upgrade, any issues? we are at 5.2.11
I’ll be upgrading to this version once tac preferred and then hoping it buys me time until I have to roll out 6.x and has had more maintenance releases
I’ve noticed when we upgraded to 6.0.1-19 we lost the settings and then had to manually run the old msi of 5.2.10 and then the 6.0.1
This only effected users off the internal network. Anyone seen this similar behaviour?
Has anyone noticed any issues with transparent upgrade to 6.0.1? I deployed this to a few test users, majority ok but 1 person said they were unable to login to there windows machine for 1-2 min while GP was updating. Another mentioned they had to wait 2 minutes or so to sign into their windows laptop whilst GP was updating in the background?
You’re gonna have to update in a few months for the next 5.2 release anyways. Treat it like MS updates, going to have to update every few months.
Definitely go off of what’s recommended though. If 6.x isn’t recommended yet, don’t go there just yet. That’s burned me in the ass a few times before, being too overzealous on updating even within the same branch.
6.0 hasn’t given me any issues yet. I’ve been testing for a few months. My team has been testing for a couple weeks, and we are about to start deploying to the company.
I have been using 6.0.1, but my setup is very basic, dual stack full tunnel, nothing fancy… no hip… so far so good for both Mac and win10…
Have not seen this issue. We are using SCCM to deploy 6.0.1.