Staff using command prompt

[jcs808]

Hello

 

Does anyone give staff access to the command prompt?

 

We currently don't. I had a member of staff who wants to be able to create a couple of hundred folders at a time (a whole year groups worth) and then copy and rename a file into each folder. I offered to help them in the first case but I got a kind of "OK, but I want to be doing this as and when I need to" response. Which is fair enough.

 

They had found a website which gave them the starting blocks for creating the code which I helped them correct but I'm wondering which is the best way to give them what they need. Thanks.

[jtoland]

I would not give staff access to cmd personally and if they need anything doing like that do it yourself

[abillybob]

At the end of it, it's your network so if you think you can trust them with a tool such as CMD go for it. Though if your asking for my opinion on what to do it would definitely be a nono in my book, CMD is too powerful of a management tool it would be fine if you could ensure that's all they'll do with CMD though you can't and it'd worry me.

[Simcfc73]

Like giving a baby a blowtorch

[localzuk]

Our staff have access to it. Can't see a reason not to let them to be honest. Staff are a different bunch to students, so restrictions don't need to be as strong. Staff don't have local admin rights here, so they can't break their local machine with it, and our network is secure enough that it won't be any use to try and fiddle around with it. Edited December 2, 2014 by localzuk

[dhicks]

CMD is too powerful of a management tool it would be fine if you could ensure that's all they'll do with CMD though you can't and it'd worry me.

 

Is there any specific security issue that blocking access to the command prompt fixes, or is it just considered the easiest way to solve some security issues that could be solved by other means but would take more time / work? Can anyone actually give examples of security issues that involve the use of the command prompt?