/build/static/layout/Breadcrumb_cap_w.png

Distribute Windows Server 2003 Serivce Pack 1 Administration Tools Pack

I'm about to distribute 'Windows Server 2003 Serivce Pack 1 Administration Tools Pack' (or Windows Admin Pack for short) to some users via AD.
The users have two different accounts each. One 'user account' that they log in with and one 'admin account' that they use when they do administrative tasks (using run as).

I need to distribute the Admin Pack to these users (not to their computer accounts), but the problem is that when I do so, doesn't matter if I assign or publish, the users doesn't get the shortcuts on their start menues. However, the program appears in 'Add/remove programs -> Add program', so they can go there and click 'install'. The problem is that their user accounts doesn't hava the permission to install the admin pack. And they can't use 'Run as' to start add/remove programs, because then they see the programs for the admin account and no Admin pack shows up.

Setting the application to be installed automatically on logon does not solve the problem. The result is that the installation fails with the same lack of permssion (shows up in the event viewer).

Is there any way to solve this problem without editing the MSI or creating an MST?

0 Comments   [ + ] Show comments

Answers (4)

Posted by: AlexM 18 years ago
Yellow Belt
0
I have the same problem. The MSI installation process fails everytime, saying the user doesn't have enough privileges to complete the install.

I want to do this to allow certain users to do administrative taks, such as resetting passwords. I'm sure I'm not the only one who wanted to do something like that, so is installing the Admin Pack the only way to do this, or is there something better?
Posted by: wicket 18 years ago
Senior Yellow Belt
0
I ended up installing the admin pack on machine level instead of user level. That works fine.
Posted by: Gastro 18 years ago
Senior Yellow Belt
0
Sounds very strange. I used the msi-package and had no problem with installing it per user. It installs when the user logs on.
Posted by: wicket 18 years ago
Senior Yellow Belt
0
And your users are not local daministrators on their machines?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ