Recommended administrative practice dictates that an administrator should be logged on to a privileged account (one with administrative rights) only while doing chores that require privileges. For ordinary work, the administrator is supposed to log off from the privileged account and then log on again to an ordinary account.
However, inevitably a situation arises later on requiring use of the privileged account, making it necessary for the admin to log off from the ordinary account and log back on to the administrator account, with the process reversed again a few minutes later. After a few days of this, your typical harried admin will succumb to the temptation and stay in the privileged account most of the time.
Unfortunately, this practice makes Windows 2000 and Windows Server 2003 systems highly susceptible to Trojan horse attacks. Just running Microsoft Internet Explorer and accessing a non-trusted Web site can be very risky if done with an administrator account. A Web page with Trojan code can be downloaded to the system and executed. The execution, done in the context of administrative privileges, can cause considerable mischief, including such things as reformatting a hard disk, deleting all files or creating a new user with administrative access.
Microsoft finally addressed this problem in Windows 2000 with the Run As feature (enabled by the Runas service, which is on by default). This feature, also included in Windows Server
To use the Run As feature, create an ordinary user account for your own use (if you don't have one already). Make sure that the user account has the right to log on locally at the machine you want to use.
To open a program or system tool using a different user account (most likely an account with Administrator privileges):
- Hold down the Shift key and right-click the desired program, Control Panel tool, or Administrative Tools icon.
- Choose Run As from the shortcut menu.
- Enter the user name and password for the account to use.
- Click OK to open the program or tool using the specified account's credentials.
You can also choose to run the program using your current account, except with restricted access. Some administrative tasks, such as setting system parameters, require an interactive logon and do not support Run As.
About the author: Rahul Shah currently works at a software firm in India, where he is a systems administrator maintaining Windows servers. He has also worked for various software firms in testing and analytics, and also has experiences deploying client/server applications in different Windows configurations.
More information on this topic:
- Tip: Further
alternatives to using RunAs
- Topics: Windows
Server 2003 management
- RSS: Sign up for our RSS feed to receive expert advice every day.
This was first published in September 2006