Install an MSI using a different user ID and password - VB Script
I am using SCCM to deploy and install MSI, but the program requires elevated privelages in order to install correctly. I need a script to call the MSI and install it under a different user ID and password. Any assistance would be greatly appreciated. Thank you in advance.
Answers (3)
What version of SCCM are you using? Anyway in both, you should be able to specfy the user account to use to install the product *in SCCM*, but in all honesty you should be fine with the Local System Account.
SCCM2007 Program
When you create the program you should select "Run with Admin Rights", this is the local system account.
http://www.windows-noob.com/forums/uploads/monthly_09_2008/post-1-1221205265.jpg
SCCM2007 Task Seq
You will need to use the task sequence to deploy a
product with diff username and password. see link below to get an idea.
http://social.technet.microsoft.com/Forums/systemcenter/en-US/50e1655d-d71d-41af-aa3c-e078eded4d50/uninstall-software-using-different-credentials
SCCM2012
No idea, someone else will need to answer that Q. But one would assume it would like 2007...almost.
Trying to figure out if your new to SCCM, or that you have a specific requirement to use another user context.
I agree with the above, but I know that sometimes you have to install it with a NON system acc.
This will happen one day, so, create a AD acc that is NOT a system account, make sure it is a member of the LocalAdministrators group of the clients.
I have had something similar, where I had to deploy via CD, (in the post) an application to remote users, I created a VBS that ran the install command with a local user acc (that was an administrator). Don't worry, the VBS was encrypted.
But as I told my client. The encryption will take approx. 1.5 seconds to crack, assuming it takes you 1 second to log in and run the decryption hack tools. They were happy with the risk. (It would prevent to overly curious people from editing the unencrypted VBS in a text editor.)
Not a proud day for me.... But it got the job done.
If your SCCM doesn't have the rights to install an MSI, you've broken something. No script is needed to install anything - SCCM has the appropriate security rights to manage everything.
