"Web Components" CCTV Plugin for IE - stop upgrade check

Joined
Nov 28, 2016
Messages
2
Reaction score
0
Hi
We have a very locked down work desktop. WE use the "Web Component" CCTV plugin for IE. However, it seems to do a check for new versions everytime it starts and then refuses to work unless it is upgraded. The normal users cannot upgrade it.

Apart from blacklisting the server it is checking for upgrades, anyone any idea how we can stop this happening? We can then upgrade it when we chose, and have the users stil lbeing able to do their job

Many thanks

ACM
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,966
Reaction score
6,795
Location
Scotland
However, it seems to do a check for new versions everytime it starts and then refuses to work unless it is upgraded.
My understanding is that it's only checking the loaded version versus what's available in the camera or NVR that the browser is connecting to, as opposed to going out on the internet.
And I've not seen it refuse to work - it's just a nagging prompt that can be cancelled, at least on a PC not locked down.
We can then upgrade it when we chose
Would it not be the simplest solution to just roll out a package with the updated version to users, that would eliminate the prompts, and get the benefits of the update too?
 
Joined
Nov 28, 2016
Messages
2
Reaction score
0
Thanks

Odd - we've not touched the cameras, yet had two updates in the last 2 months, and it does seem to stop the page working.

Yes, we can push out a new version, but if the site simply stops working when an upgrade is detected we then have to treat this as a "system down" - if it carried on working, despite the nag, we could then treat it as "Planned upgrades"

Cheers

ACM
 

alastairstevenson

Staff member
Joined
Oct 28, 2014
Messages
15,966
Reaction score
6,795
Location
Scotland
Odd - we've not touched the cameras, yet had two updates in the last 2 months, and it does seem to stop the page working.
If the cameras have not been updated - is it possible the PC images have had webcomponents downgraded? Something must have changed.
if it carried on working, despite the nag, we could then treat it as "Planned upgrades"
Maybe the reason for the block could be determined and handled, reducing the impact of whatever has changed.
 
Top