Auto-Update 2020.2.0 -> 2020.2.1 doesnt work
these are on 2 freshly set up W10 PCs so aside from stuff microsoft brought along there's basically nothing to interfere.
when I installed 2020.2.0 about an hour ago from writing this (as that was what I had) it asked upon launch whether I want to update wayk, I said yes, let the UAC do its thing and after a bit the windows installer popup came briefly, went away and then wayk started again as 2020.2.0.
are there any installer logs I can give out to help?
Edit it gets crazier:
apparently 4 machines (of which 3 are registered) got the update to 2020.2.1 (also from 2020.2.0), with the same 3 registered ones not supposed to have admin permissions (and in fact have random-ish admin passwords), so no one should have randomly got in these 3, but all 4 of them apparently got a new ID, and are now listed twice (the registered ones in registered and unregistered once each, and the unregistered once just appearing once more in that list with the same name.
this leads to 2 problems:
1) the 53 Laptops in that group are getting doubled up leading to quite a bit of chaos
2) as the new IDs are obviously unregistered, the Laptops lose their groupings, which cannot be re-assigned, until I can get hand to them and go through registration again.
so in the end there are 3 questions:
1) why did the Update fail on the 2 Machines I have at hand
2) how did an update happen on 3 machines that shouldnt have happened (as the update dialog does spawn UAC
3) what happened with the IDs? new certs in some way?
All Comments (3)
Hi,
1) The manually triggered update (the one you when you are asked to update Wayk Now) calls a our PowerShell cmdlet under the hood, which may fail on some systems.
2) The update happened because it was the automatic update done in the background by the unattended service. The auto update doesn't use the PowerShell cmdlet, which is why it worked while the manual update failed.
3) This is an issue we just fixed with the Wayk Now 2020.2.2 (released a few minutes ago)
Best regards,
Marc-André Moreau
you need to install the update manually sadly
OR
if you have unattended running, make sure wayknow.exe is CLOSED AND NOT RUNNING, then wait 30mins, and it will automatically download the msi and update itself
the was a bug in the powershell 2020.2.0 where it was using the wrong msi file
see my post - https://github.com/Devolutions/WaykNow-ps/issues/27
okay that's nice to know.
although I have to admit that it's a little weird that it can auto update without UAC but when you get asked to do so you have to do UAC
the bug also explains a lot.
all the machines I install run unattended service because of the need to get into UAC so when that handles updates by itself that's nice.
3) This is an issue we just fixed with the Wayk Now 2020.2.2 (released a few minutes ago)
how will machines that got 2.1 interact? do they regain what they had in 2.0 or do they keep what they have in 2.1 or do they get something entirely new.