I've tried to get the latest release by following the instructions provided (running kinstall.exe)
My server goes through the process of installing the patch (it finds 184.108.40.206) and everything peachy.
After all is said and done I look in Kaseya and it says my current patch level is 220.127.116.11...?
The following may assist you:
Yep, that's the very document that I used as a guide...Still didn't work.
Can confirm, getting exactly the same thing. System->Configure shows 18.104.22.168 as current patch level, KInstall shows 22.214.171.124, seems to install 126.96.36.199 (but doesn't start all services back up) - re-running it gives the same result. Reboot didn't help.
I also can only seem to update the agent as far as 188.8.131.52. So it looks like I really don't have 0.2 or 0.3.
installed 184.108.40.206 but kinstall shows 220.127.116.11 and the web UI shows 18.104.22.168.
From reading the release notes, the System > configure update is part of 22.214.171.124 so Im do believe that 126.96.36.199 is installed but just showing incorrect version
Similar issues here. Apparently the process completed successfully (though there were no messages after the process completed to that effect) but opening the VSA shows some services are stopped and my version still shows as 188.8.131.52. Apparent the upgrade to 184.108.40.206 went as well as the upgrade to my Kaseya trust level. And so much for the "Consistent Versioning" mandate.
Just great. When I log into the VSA my screen says "System Version 220.127.116.11". After login I go to "System-Server Management-Configure" and it says "Installed Patch Level 18.104.22.168". If I run the KInstall again it tells me that I'm currently at "22.214.171.124" and tells me it's going to install "126.96.36.199" - which, of course, it doesn't.
The "Agent Upgrade" screen still gives the option to "Force update even if agent is at version 188.8.131.52 - 184.108.40.206" even though my agents are showing as "220.127.116.11". Why I would want to force them backwards is baffling.
I suppose this all makes great sense to the powers that be but it sure leaves me wondering what the heck is going on....
I'm seeing this myself on my own Kaseya server and will make sure our engineering team knows about these version inconsistencies and mismatches. Be sure you get tickets sent in to support so we can readily update you when the issue is resolved.
Sorry. I no longer submit tickets. But I do expect your "engineering team" would test these "patches" before they ship as part of the new "trust" initiative.
I'll do it if you will not. I don't care how frustrated you are - everyone else will benefit from submitting the ticket.
Request #3506 "Version Inconsistency" created
SMason has a point, this needs to be a collaborative effort on both sides of the party in order to push forward...
The fix appears to be released now (IP-74):
Testing on my 6.5 instance now to verify.
Our engineering team resolved this one -- running kinstall.exe this afternoon successfully updated me to 18.104.22.168 which is now accurately reflected in Kaseya.
I can verify that 22.214.171.124 does fix this particular issue.