Disable Updates

[msigurus]

Does anyone know how to disable the "Check for Updates" Tab under Help/XYplorer on the web? Please keep me posted

[TheQwerty]

Does anyone know how to disable the "Check for Updates" Tab under Help/XYplorer on the web? Please keep me posted

All it does is opens the website when clicked... there's nothing enabled to disable.

[msigurus]

In our corporate we don't want users to click on the "Check for updates" tab & request for an update. We want to be able to control this & automate the update process. There must a registry key entry of some script to disable the Tab, any advice

[admin]

XYplorer has currently no way to disable anything that could not be re-enabled by the current user.

A possibility that comes near to this would be to add an INI-tweak (DisableCheckUpdates or so), that could not be modified via the UI.

BTW, how many users has your corporate?

[msigurus]

This is actually going out to about 30 users so if i was to tweak this through an ini file where should i insert DisableCheckUpdates & what should be it's value?

[admin]

This is actually going out to about 30 users so if i was to tweak this through an ini file where should i insert DisableCheckUpdates & what should be it's value?

Well, first I would have to add this functionality to the app. But currently I'm having problems to understand the use of this feature. You say "we don't want users to click on the "Check for updates" tab & request for an update." Who are these users? Your employees? Sorry, but I don't get it.

[msigurus]

Yea they are regular users & some of them have admin rights. All the updates are handled by the admin team i just want the "check for updates" tab to be greyd out

[admin]

Yea they are regular users & some of them have admin rights. All the updates are handled by the admin team i just want the "check for updates" tab to be greyd out

But "check for updates" just calls a website. Everybody can easily do the same thing with a web browser...

[msigurus]

Even though they can but our organization standards are to remove any updates or update check tab. Please let me know if this can be done. Thanks for your help on this

[admin]

Even though they can but our organization standards are to remove any updates or update check tab. Please let me know if this can be done. Thanks for your help on this

OK, I could see some sense in adding something similar to a "safe mode", say an "employee mode"... In this mode, the whole "XYplorer on the Web" submenu would not exist, and maybe a number of other things.

Does this make sense? Any ideas anybody for other things that employees should not be able to do?

[SkyFrontier]

Read Only Navigation Mode and Disallowing Navigation to Upper Directories/interface restrictions may give some ideas - both received a positive impression from yours, Don, just needing the time-thing to come! Perhaps this has arrived...?

[SkyFrontier]

License and Scripts protection also could be considered regarding this matter (I'd *really* not want some of the co-workers having access to the scripts structure!), but perhaps the best idea on this matter is not allowing any changes via GUI (so "Open Config File..." must be grayed, too) except if a master password is inserted to unlock access to Config options, and should be split in: 1) no access to Tools > Config panel, 2) disallowing the save of settings, 3) both.
And by denying access to Config options I mean: they must not even see how the options are set, so the password prompt must show instead when they go to Tools > Config!

[j_c_hallgren]

And by denying access to Config options I mean: they must not even see how the options are set, so the password prompt must show instead when they go to Tools > Config!

I can't conceive of any organization not allowing user to make some basic user customization so I think that idea is way overkill.

[RalphM]

Since we're talking corporate environments here, I would like to bump this thread again.

http://www.xyplorer.com/xyfc/viewtopic. ... g&start=15

I still believe cascading catalogs would make sense especially in multiuser / multi-department installations.

[SkyFrontier]

And by denying access to Config options I mean: they must not even see how the options are set, so the password prompt must show instead when they go to Tools > Config!

I can't conceive of any organization not allowing user to make some basic user customization so I think that idea is way overkill.

The problem is: what's "basic" among so many features XY has?
Also, I don't think Don would take the time to deny access to certain areas and allow it to others, all "admin-defined". So instead of having no such a feature at all, I'd rather prefer to have it massive - if one wants a customization, ask admin (it's their job, after all!). One day all will be (individually) set, and smart admins will always have the option to configure sets of deploy installments based on common feature/config requests per groups of users observing their different needs. Office people basically do the same tasks one day after the other, and I agree that granularity/flexybility matters - but again: how much?