The reason for the number of complicated posts, is that there seems to be a small amount of confusion on this matter

Mostly concerning NT4.0 and if a user has local admin rights or not. If the user has local admin rights, then you can simply run the superdat file to upgrade Mcafee.

For users that don't have local admin rights, this is where the many different solutions have evolved. I personally do not suggest using SU method, since you would have to place a username/password that has at least local admin rights, in a clear text file that everyone can read.

I instead have chosen the more complicated but very secure method. This is using a standard domain user account, granting this domain user account local admin rights, and logon as a service rights. Modifying Mcafee to run under this domain user account, and finally modify/use Mcafee's own built in autoupgrade to use the superdat file to schedule and preform upgrades.

Of course with my approach you end up with a solution that you can't implement very well through a logon script, but works great when treated as an administrator script. By this I mean a script that is ran on a domain administrators computer, that connects to and makes changes on a list of target computers. It is also a use only once type of script, because when everything is all set and done the system takes care of it's self.

I am curious to see what approach you took to secure the username/password that is used in the RUNAS command for win2k computers.

Bryce