Question : ADMIN ACCOUNT

ATT: leew

Ha Ha, well at least i will be sitting down for 10 days.

Thanks

Once i have done that, all my clients will have local admin rights to their local machines.

My Question:

All my updates via login scripts will work now but how am i going to stop the guys from installing anything onto there pc's?

With them having admin rights i see that some of the things that applied before in the system pol. is no longer applying.

Basicly, the only reason i wanted them to have admin rights to the local machine is so that updates and installs via login scrips or install paths set on our in-house (local) website where they can pick what they need.

I am happy with that but i am not happy with the thought in my mind about them going to install and change things as they want.  

I know that you can set the system to request credentials on msi install packages but what about some exe, bat, com, zip and so on...?

with them not having admin rights, nothing will install which i founf very useful but then now automatic upates and me running around like a chicked with it's head cut off..


PLEASE HELP GUYS, THERE MUST BE A WAY

Answer : ADMIN ACCOUNT

Often you'll have to reboot for installs.  Often you won't be around. Being logged in is not necessary.
AT command - the scheduler will run its jobs with system authority, so you won't need to be present to logon or anything like that.  What is required is that you have the authority to set up the jobs in the first place, and have the platform in place that will run them.