Permissions

Topic

New Reply

I’m trying to get some software to run on a users W2K workstation but unless they have full administrator rights, it doesn’t play ball.
I’ve tried every combination of installing as an admin, making them an admin for the install etc., but the only way it will run properly is if they either have full admin rights, or the program is “run as” the Administrator.

is there a way to set up the prog to always run as admin, without having to enter the password in each time?

(The software is electronic cad software, about 5 years old. It does exactly what we want and there is no need to upgrade to more recent W2K/XP-compatible versions which offer no benefits to us. Apart from which, upgrading the entire company would cost circa GBP20,000 / US$30,000…)

Reply | Quote

Replies

Is there a downside in giving their UserID local Admin rights over the machine – and not letting them be a member of the Domain Administrators group?

Reply | Quote

Ta-da!
This is what I ended up doing – I’d tried every combination *except* for giving them Local Admin rights AND then getting them to log in to the machine rather than the domain.
It all seems to work, except that they can’t see printers attached to other users pc’s.

Thanks for the nudge in the right direction

Reply | Quote

You can improve this solution by adding their domain account to the Administrators group on the local box. This will let them log into their normal account and still access printers etc.

StuartR

Reply | Quote

Aha! – thank you!

Reply | Quote

Aha! – thank you!

Reply | Quote

You can improve this solution by adding their domain account to the Administrators group on the local box. This will let them log into their normal account and still access printers etc.

StuartR

Reply | Quote

Ta-da!
This is what I ended up doing – I’d tried every combination *except* for giving them Local Admin rights AND then getting them to log in to the machine rather than the domain.
It all seems to work, except that they can’t see printers attached to other users pc’s.

Thanks for the nudge in the right direction

Reply | Quote

Is there a downside in giving their UserID local Admin rights over the machine – and not letting them be a member of the Domain Administrators group?

Reply | Quote

Yes there is a way to do this. The problem is that the application wants to make changes to the registry each time the app is used. Sysinternals have a free app that you can use. It is called regmon. Basically, you login as the administrator, then start the regmon process, open the application, and then close it again. Stop the regmon process. Now you will have to check the log to see what registry keys where changed when using the app by checking the regmon log. Once you have the keys that were changed, it is a simple matter of opening the regedt32 (registry editor) and assign that user rights to those specific keys.

The sysinternals site is here: http://www.sysinternals.com/ntw2k/source/regmon.shtml
Give me a shout if you need any additional help.
Sean

Reply | Quote

Thanks – that sounds exactly like what is happening. As above, I’ve got a working solution but I shall follow up your lead as soon as I have the (spare) time as it appears to be a more ideal long-term solution.
The W2K installation is temporary, I want to get everyone up to XP shortly and an initial test showed the same problem is going to occur.
Don’t worry, I’ll shout loudly if (when) I need more guidance!

Reply | Quote

Thanks – that sounds exactly like what is happening. As above, I’ve got a working solution but I shall follow up your lead as soon as I have the (spare) time as it appears to be a more ideal long-term solution.
The W2K installation is temporary, I want to get everyone up to XP shortly and an initial test showed the same problem is going to occur.
Don’t worry, I’ll shout loudly if (when) I need more guidance!

Reply | Quote

Yes there is a way to do this. The problem is that the application wants to make changes to the registry each time the app is used. Sysinternals have a free app that you can use. It is called regmon. Basically, you login as the administrator, then start the regmon process, open the application, and then close it again. Stop the regmon process. Now you will have to check the log to see what registry keys where changed when using the app by checking the regmon log. Once you have the keys that were changed, it is a simple matter of opening the regedt32 (registry editor) and assign that user rights to those specific keys.

The sysinternals site is here: http://www.sysinternals.com/ntw2k/source/regmon.shtml
Give me a shout if you need any additional help.
Sean

Reply | Quote