Note: Option 1 and Option 2 open a security risk as they transmit a "clear text" password. If you want to encrypt this information - KiXtart encryption - UTILITY: KiXcrypt 3.00b
Option 1 - SU
In order to install an Application with Administrative privaleges under a non-Administrator Account, you will want to use the NT/2K/XP Resource Kit Utility SU.EXE.
Bryce has good documentation and scripts that do this.
Option 2 - RUNAS
You can install/run applications under a different user than the client may have rights for and that is RUNAS (Windows 200 or better).
See also - ADMIN install using Runas like SU... Scripted without console!!!
Option 3 - GPO (Group Policy Objects)
If you have a 2000 Domain, you can setup applications using GPOs and the MSI installer (WINSTALL LE). You can also create ZAP files (not as commonly used).
The other benefit to this is that you can build your own custom installs with registry/file settings already in place. For example, with Acrobat, you can accept the license agreement, turn off the Auto Update check, and turn off web buy. All of this information is recorded with a before and then an after snapshot which is then included in the MSI file. The MSI file can also be "self healing" too.
OK.. So, how do we build an MSI file? You can get the MSI Creator from either Veritas (which is what Microsoft includes on the 2000 Advanced Server CD), or you can get one from http://www.ondemandsoftware.com/FREELE2003/ and you can do this from there.
Examples - Windows Installer Examples
Training? This is a topic covered in -
2154- Implementing and Administering Microsoft Windows 2000 Directory Services
<small>[ 29. September 2003, 14:17: Message edited by: kdyer ]</small>
