- This topic is empty.
-
Posts
-
I’ve deployed the DST addon to our 3125 & 3150 terminals using the old and new versions of Rapport/WDM. However, in Rapport it said the package update ‘failed’ on every darn terminal, but when I look at the addon list on the terminals control panel the DST addon is installed. And the time zone is working correctly. In WDM it does the same thing?
A few terminals didn’t get the update, so this morning I’m pushing the addon out to those few…
Also, it seems to take hours(?) for the update to install (the terminal screen says “…reconfiguring this client”. The first time I pushed to the addon out to all the terminals I let it run overnight, so I’m not sure how long it actually takes.
Why does it take so long? Am I doing something wrong? Thanks for any help…
Yep, something is very wrong. What does the log say the reson for the failure is?
It was strange; I was getting ftp connect errors. A few of these 3125 devices would not show up in WDM at all. I could manually connect to them via VNC, perform an ‘upgrade’ using FTP from the devices control panel…it would then install the DST binary just fine and reboot. After rebooting, a couple terminals were completely reset…no connections, lost IP settings, etc…while other terminals were just fine. These are all the same 502.2 image.
I don’t know what the heck was going on, but manually updating them seemed to work.
Hi Rodd,
That’s very old firmware (502). It may be easier to bundle up the add on and firmware and send it out as one package. It sounds like to me the upgrade happened quickly but the WDM server did not realise it and the device did not re-boot. This is why they were stuck on the upgrade screen.
I have seen this happen with older versions of the Rapport agent. Generally try and keep images uniform across platforms, also sometimes it may be required to push a new image to devices that have been upgraded with many configs in the past.
-TT
- You must be logged in to reply to this topic.