Steven said:
If you are not using automatic updates then you need to logon as an
administrator to install the updates. Runas may not work because of the
complexity involved with the installation of security updates. I don't see a
problem logging on as an administrator for the sole purpose of checking for
and installing security updates but when done it is a good idea to logoff as
administrator to do regular internet activity. The main risk with being on
the internet as an administrator is when opening email, using chat programs,
and browsing websites that may contain malicious code.
Steve
Thanks Steve. What I am trying to do it make the machine behave more
like a *nix machine (Red Hat or SUSE desktops with GUI) when it comes to
updating and patching.
In deploying this in a non-AD managed environment (they are very small
environments and do not justify implementing AD or WUS/SUS), I am trying
to make the users stay logged in as users all the time and creating
runas shortcuts to perform admin tasks from within the logged in regular
user session. The admin credentials are buried into the shortcuts so
they don't have to type anything in and this helps discouraging them
from knowing or finding out the credentials.
Once I start telling them the administrator account credentials and
advise them to login as that once in a while, they will just start
getting into the habit of logging in as an administrator all the time.
I have collected various tips and advice from different MS experts sites
and blogs and seem to have a system setup where one is almost all of the
time using the desktop as a regular user.
What I am really fishing for here is... I have managed to get around
various application program issues that crept up when trying to run them
as a regular user by tweaking registry ACL's.
Are there any tips/advice/ways to tweak the registry ACL's to make
windows update work in IE?