Restrict where staff can install from

[daverage]

Hi there.
Is it possible using windows 2000 server and clients to restrict where a staff member can install from.

At the moment they have no install rights and for reasons to complicated to explain we can't send out msis over the network.
It would be nice to have an Authorized download and install area on the intranet.

Any ideas?

[Ric_]

If you wrap the app up as an MSI and publish it in AD, your users should be able to see it in the Add/Remove Programs list. You would still need to give them permission to install IIRC.

[daverage]

For the same reasons as we cant send out the msi over the network, we can't produce them either!

[Geoff]

what reasons that then?

[daverage]

lol comes down to the network manager. Nuff said.

[Geoff]

Hmm?

[daverage]

He wont do it, full stop.

[E1uSiV3]

Thats screwed up :S It would be interesting to hear his views on as to why he wont do it, most of my software goes out via MSI or scripts on the RIS, it saves me about 3hrs per workstation on manual installations. RIS + MSI deployment means where it used to take a week to prep and rebuild a computer room, it now takes 1/2 a day... i cant see ANY reason as to why this is a bad thing...

Sorry this does not hep you out daverage but there is no real solution that i know of apart from group policy deployment (MSI publishing/assignment or scripting unattended setups) or SMS(expensive), and it seems your NM has a bugbear with something to do with the process so is cutting off his nose to spite his face.

[Geoff]

He wont do it, full stop.

Would he like to post his reasons?

[ChrisH]

I would also like to hear some good reasons. Is this network manager a teacher as well or are they a dedicated manager?

[daverage]

Wont go into it, but thanks for the suggestions so far.

[ChrisH]

Probably wise

[SpuffMonkey]

Hi there.
Is it possible using windows 2000 server and clients to restrict where a staff member can install from.

Any ideas?

Spose it depends what and why the software is being installed. If its kosher licensed softeware - it ought to be (imho) part of your build and update procedures - not just ad hoc. If its to trial and play with new software - you could do what we do and stick an old standalone on the staff room and refresh it every month or so...

[alan-d]

I think what Daverage is trying to say is that his NM doesn't trust his technicians or staff enough to allow them to carry out their jobs properly by giving access to download and/or install programs.

What he needs is proof that he can show his NM that permissions can be granted to carry out certain actions to individuals or groups without comprimising the security of the network.

Daverage - this thread may go some way to help you - albeit - in reverse of course

http://www.edugeek.net/index.php?nam...iewtopic&t=675