Is it possible to move this somewhere else....or add an 'Are you sure?" box or something?

It's a little too easy to accidently turn off the server.

I know I had this request seen before. 🤔

After some searching I found this post: VC Application Stop Button 

I also like the warning message so lets implement it! [-o<

Regards,
Erik

---

Erik I could not agree with you more … this request has been around now for a while. Maybe the VC developers just don’t get the impact it has to the operations of a business if anyone can just turn the server off. How difficult can it by to put a warning message on the button when a click event is fired?!!! Ideally I would like this button only to be visible by the Admin user; the user is hard-wired into the system in anycase.

This is becoming clichéd but I don’t understand the aversion the VC developers have to tightening up their system. In the last 2 years there has been considerable movement with functionality, API interface and you even now get a “drop and drag” interface. But when last has any user/job/system security feature been added to the system even though when you trawl through forum users are actively requesting it.

Hi all,

we need to get more professional and don't put too much feelings into this forum. It is not that we have ignored this request at all - we just do have a lot of requests. I mean the feature request forum is almost as big as the problem solving forum.

One thing that we think about when implementing this is how you use the Stop button. Personally, I see it as quick way of stopping all Job activity if there is some kind of problem. If we add a messagebox to that it will not be as quick anymore.

Anyway, we will add this feature but please do think about how you write posts in the future.

---

Hi Henrik / dev team,

I'm happy with:
- the tool you provide to the big world;
- the fast support response;
- the ability to talk/help to all the forum guys;
- the fact that feature request are being taken seriously;
- the ability to test beta versions;
- etc..

My feelings are only positive and as a developer I know that some request aren't that easy to implement if you want to solve it as generic as possible.
Also, I think, you have a lot of development going on from your own agenda, like version 5 of this tool. And don't forget some maintenance/bug fixes/talk to forum people giving/ect. So in others words, you're all busy in making the best tool there is out there.

I was already writing this message as a response to adutoit's post. Ok, the world isn't a nice flower, but spitting on it doesn't make it a better flower.


Regards,
Erik

---

If my post came across too strong I do apologize. Appreciate however the concern that has been expressed over the vulnerability that any VC user can inadvertently terminate a VC service; please understand the ramifications of that.

“I see it as quick way of stopping all Job activity if there is some kind of problem. If we add a messagebox to that it will not be as quick anymore.”

That is great but why would you want every VC user to be able to do this? It is then implied then that every VC user should have an administrator’s status. VC was architected to allow multiple users to access the service but there must be an understanding that there should be a division of powers. I may have rights in my organization to view the AD Tree but that should extend by default to right for me to stop the organizations Windows servers.

I am not saying we want every user to do this. In fact, changing status (clicking Stop) is restricted by the Settings->Edit permission. If you want to prevent users from stopping execution you should deny this permission.

You are right, we have prioritized new Task functionality and not security features. We believe that users rather want to be able to do something rather that be limited in doing something. That said, we are not thinking that security is unimportant but the messagebox on Stop button is just the "top of an iceberg". There are a lot of things that needs to be implemented on the security side:

* more detailed security permissions and Job permissions - see this  post
* more warnings - like this stop button
* translations to the above
* possible AD connection - see this  post
* etc

This is just security parts and there are a lot of stuff to consider. We ask you to be more constructive and add ideas to the discussion.

We try do to our best prioritization. Sometimes, when our customers have not felt that we follow their priority list and when they are in a hurry they have paid us for custom development. We will take care of the requested security issues as well as other requests. We are not ignoring them or think they are bad in any way. Development just take time and we ask for your understanding.

---

Henrik thanks for the reply. As we delegate our operational jobs to VC from a management perspective I am required to control that functionality. For example, I cannot make use of the functionality to reboot servers in VC if I know that any VC user could start that job. It is abit like giving some-one a loaded gun without a safety catch and saying, careful don’t press the trigger. I have to temper all functionality VC could provide us with-out compromising the business; hence my contributions have mainly been focused on the security issue.

It would be useful to see some kind of roadmap of what you guys are planning to release in the next 1/3/6 months.

It is hard to publish a roadmap without giving away too much information to our competitors. We need to think about this and will possibly publish something sticky in the request forum.

About the confirmation box - it is added in version 4.9.29.

---

I noticed that in the release of .29 this morning. Downloaded, tested in our dev env. and is working as advertised. Thank you very much for the quick response.