Wyaknow into Wayk Agent

Hello,

The Wayk Now / Wayk Agent verifies when you launch the application and periodically after if an update is available and prompts you to install it. In this major revision, Wayk Now (latest version was 2020.2.6) becomes Wayk Agent (2020.3.0). The option is located under General - Check for Updates.

If a Wayk Now did not update, it usually means it cannot connect to our servers. You can still remote into those computers, so it will not affect your workflow. If required, you can download the latest version manually: https://wayk.devolutions.net/home/download . If you still experience issues, we can verify the logs of the affected machine.

You can read more on our blog here: https://blog.devolutions.net/2020/10/a-whole-new-wayk-the-future-of-wayk-now

Best regards,

Hi Kris

Just to expand on what my colleague already answered:

If you have automated updates enabled, the service checks for updates every 24 hours (although this is configurable via the command line). So it's quite possible that you have some installations that didn't find the new version yet. If it's been a couple of days and you still have machines on 2020.2.6 but with automated updates enabled, please try to export the logs from the machine for us - as Richard wrote, it may be that automated updates are failing for some reason.

If you opt to download and install the new version manually; note that Wayk Agent is a direct replacement for Wayk Now. The product code, etc are all the same - it's basically just a rebranding. So Windows Installer sees them as the same product. You simply run the Wayk Agent installer and it will replace Wayk Now on your servers.

I connect at few customers computers I got popup about update from 2020.2.6 into 2020.3.0.. I push Yes, but nothing happen

The "user triggered" update regressed in 2020.2.4, apologies for the inconvenience. This is fixed for 2020.3.0 (Wayk Agent).

Let us know any questions or problems

ive had an annoying issue with the auto upgrade from wayknow into waykagent

the auto update has removed the wayknow.exe and all our shortcuts directed to that exe
so now i have shortcuts everywhere on loads of computers with BLANK images on desktop and in start menus
also when clicked says file not found, not a happy bunny!

also had to change our powershell install script as it used the old name which created these icons, not another happy bunny!

i would of HOPED they kept the old file name there (maybe a shortcut itself to the new waykagent.exe file to help users tranform to the new name)

Hi,

it was busy time for me, but I'll add few more words.

1. I've update problems at Windows Server 2012 R2 and many Windows 10 - I'll send logs from customers computers
2. For security reason I did allow at customer site Nowservice.exe from specific location.. when autoupdate was triggered twe weeks ago I wasn't able connect user computer.. because path to that service was changed - now one of directory was called Wayk Agent - I stop using tightvnc many builds ago, so... ;-)

I didn't have problems like Simon wrote. All old shortcuts at user desktops was removed by auto update and new one wayk agent was placed at user desktops.

--
KriS

Hi KriS02,
i use the option with the powershell scripts/msi installers to NOT install shortcuts on the desktop and start menu so i could create my own shorts with a custom name
so hense when the software auto upgraded from wayknow.exe to waykagent.exe the shortcuts stopped working which was very annoying!
Regards
Simon

Ahh ok, now it's clear :-)

Long time ago I change shortcuts into names like "remote suppor" etc.. but there was so many updates so I stop doing this.
People don't know how pronounce Wayknow and even don't understand what I say.. so many of them looking for "blue owl" when they need help :-)

Ahh ok, now it's clear :-)

Long time ago I change shortcuts into names like "remote suppor" etc.. but there was so many updates so I stop doing this.
People don't know how pronounce Wayknow and even don't understand what I say.. so many of them looking for "blue owl" when they need help :-)

i rename them to our remote support company "Anywhere Support" as its very simple :)

Hello

Please accept our apologies for the disruption Simon and Kris. We did our best to ensure a smooth transition from Wayk Now; edge cases like you both experienced do come about because of how the product actually gets used in the field and are not always easy to predict; or otherwise easy to overlook. Again, we are sorry for the disruption caused and assure you that the product name, paths, etc will stay consistent now.

Kris - are you referring to the auto update not working? I did take a look at the logs you sent and I think this is related to how we publish the CDN URLs. Coincidentally we received a similar report internally this morning. I've requested some changes to the CDN that should fix this; if you still notice out of date systems within the next day or two please let us know!

Thanks and kind regards,

Hello,

for me first thing when I see update is checking release notes.. I would like to see more detailed info what change/fixed was when new release came out.
It will be less digging for me if something don't work after update..

Yes at files you've logs where auto update don't work. (I've hop I don't mismatch diagnose logs - read my next post ;)

Yea... you didn't check logs... ;-) and now few customers computers with Win2012 and Win10 have new version ;-)
It was faaast - thx :-)))

Hi Kris

Great news; I'm glad to hear that is resolved. We will work on providing more detail where relevant in the release notes in future.

Thanks and kind regards,