There is something tricky about this issue, and Windows XP solves that problem with "Run As..", which unfortunately is not in Windows 2000.
This applies to many computers on our network:
On a Windows 2000 machine, I have an "Administrator" account and the account of the person currently using it. Let's say John Doe has the account "jdoe". John does not have administrative rights so he is not able to install programs. Only the admin account can. Also, "jdoe" is set up on his machine as a domain user.
But here's the problem. I need to be connected to the network while installing that program. And to be connected to the network, I need to login to Windows with an account that resides on the domain, in this case "jdoe". But, "Administrator" (which is the only account that can install programs) is not on the domain, and thus, when logged in Windows with Administrator, I'm not on the network, thus not be able to install the program correctly.
So, I'm looking for one of these two solutions (it would be helpful to know how both would work, if possible):
* If logged in Windows with "Administrator", how do I temporarily connect to the network (using an account that resides on the domain)?
* If logged in Windows with "jdoe", how do I temporarily achieve administrative rights to be able to install the program?
Note: John Doe should not have permanent administrative rights, nor be a "Power User" (which isn't even helpful with some programs that need full admin rights).
My workaround (which I need to avoid): Log off "jdoe" (which will most likely require me to close all John's programs currently running, which can be a hassle and sometimes not be able to close them at the moment), and then logon with "Administrator" (at which point I'm not on the network anymore). Change jdoe's account to include it in the "Administrators" group (that way when he's logged on the network, he's also administring his local machine). Log back on with jdoe. Install the program. Change jdoe's account back to exclude it from Administrators group. Log off and on with jdoe for the change to take effect.
As you see, my workaround is tedious and sometimes should be completely avoided, since John Doe cannot close some of his programs.
Any input is welcomed.
Thank you for reading thus far.