Thanks for the quick response
We do have AD. I usually use gp to install things. The Patchlink is a new deployment software we are using for patches and installations. It Lets us do installs during off hours when no on is on the network or schedules them in advance for off hours. Machines are left on, and if not it boots the machines.
Maybe I miss read....will the AllUSERS=1 does it install for all users or does that check for admin priveleges and fail if they are not admins?
We have tested it with the silent intalls and that works too. I will give the ALLUSERS=1 a shot tomorrow when I get in.
I'm with you, don't like the runas or elevated privileges options.
Thanks....I'll give it a shot and give an update on the status
T
Main Topics
Browse All Topics





by: BeldoranPosted on 2007-09-27 at 17:25:19ID: 19975744
The command line switches for msiexec can be found here /en-us/lib rary/Aa367 988.aspx
http://msdn2.microsoft.com
In addition you must add the ALLUSERS=1 parameter to the command line.
msiexec /i [path] INSTALLDIR=[path] ALLUSERS=1
You may also want to use the silent switches
The issue you may be seeing is when the package is installed and who it is installed as (when the batch file runs). Eg If the package is being installed by a user without admin rights then it cannot do a full install.
We use group policy to install these packages at machine startup time and it works fine.
You could (and I do not reccomend this) use the runas command to change the user that the package is installed with, but this means embedding passwords that may be seen by people who should not.
If you use active directory there are a number of other options you can do, such as setting elevated privileges on the installer. (Again, some security risk here)