1. You need to supply the username and credentials of an Administrator user with RUNAS. As this provides a plaintext security breach, you might use a wrapper application to hide this information: thread779-676827
2. Make certain there is no Group Policy preventing a logon as a batch process.
3. If you like, you can do this through Scheduled Tasks. One schedule option is 'at Logon.' You can put the Administrator name and password in the Logon section of the Scheduled Task. I use a 'temporary' Administrator account for just this purpose, and change the password frequently.
4. You can use Group Policy to publish the application and push the installation.
5. You can do the installation remotely. While there are resource kits that would permit this, I use the terrific utility PSEXEC from sysinternals: (freeware)
If the username/password used has Administrator rights, and there are no Policy restricting logon as a batch (or possibly service), any of these 5 methods will work.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.