Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, February 26, 2018 10:04 PM
All,
I'm attempting to remotely deploy the Microsoft Local Admin Password Solution client software, named laps.x64.mis
We are installing on Windows 10 clients with all patches and updates applied.
I've tried using group policy software deployment as well as a login script. The script looks like this:
msiexec /q /a \servername\laps\laps.x64.msi /l*v c:\temp\admin_install.log
in the script, I included a verbose log file, which indicates the software installed correctly:
MSI (s) (AC:C8) [13:58:02:412]: Product: Local Administrator Password Solution -- Installation completed successfully.
MSI (s) (AC:C8) [13:58:02:412]: Windows Installer installed the product. Product Name: Local Administrator Password Solution. Product Version: 6.2.0.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 0.
But when I check in Programs and Features, the software isn't listed.
I have kicked off the script manually rather than use logon process. It runs without any errors either visibly or in the provided log file.
Also, I have installed the software manually and clicked through the options to verify. When I do it this way, it DOES appear in Programs and Features.
I'm at a bit of a loss as to why its not deploying either via GP or script. Any help is greatly appreciated!
All replies (10)
Monday, February 26, 2018 10:11 PM
Hi ZeeDee24,
Try to put the quotes "" around the UNC path
msiexec /q /a "\servername\laps\laps.x64.msi" /l*v c:\temp\admin_install.log
<file location="">Simon</file>
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. Regards Simon Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.
Monday, February 26, 2018 10:18 PM
Hi ZeeDee24,
Try to put the quotes "" around the UNC path
msiexec /q /a "\servername\laps\laps.x64.msi" /l*v c:\temp\admin_install.log
<file location="">Simon</file>
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. Regards Simon Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.
thanks for the idea. I made that change but I get the same result.
I think the install is starting because I get a whole slew of info in the log files, but for some reason its not completely installing via script or GP...and the log files don't include anything that looks like a warning or error.
Monday, February 26, 2018 10:27 PM
Hi ZeeDee24,
I tested it on my pc, the msiexec line works when the command prompt is run as administrator.
You should use this GPO setting
GPO setting "Always Install with Elevated Privileges" in Admin Templates/Windows Components/Windows Installer.
Regards
Simon
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. Regards Simon Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.
Monday, February 26, 2018 10:44 PM
Hi ZeeDee24,
I tested it on my pc, the msiexec line works when the command prompt is run as administrator.
You should use this GPO setting
GPO setting "Always Install with Elevated Privileges" in Admin Templates/Windows Components/Windows Installer.
Regards
Simon
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. Regards Simon Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.
ok, so I manually opened a command window, using "run as administrator". I then pasted in the line from the script. it appears to run very quickly, no errors.
but it still doesn't show up in "Programs and Features".
Monday, February 26, 2018 11:24 PM
another update: I tried my script on a PC that was freshly imaged, it also didn't install.
Tuesday, February 27, 2018 8:29 AM
I used
msiexec /i "\servername\laps\laps.x64.msi" /quiet
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. Regards Simon Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.
Tuesday, February 27, 2018 4:57 PM
I used
msiexec /i "\servername\laps\laps.x64.msi" /quiet
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. Regards Simon Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.
Simon, thanks for that! it works...kinda.
This only works for me when I type it in directly into a cmd window. With this method, the software installs and I can see it in Programs and Features.
I created a script with that line in it. I right-click the script and run as admin but the install doesn't complete.
what am I missing?
Tuesday, February 27, 2018 6:55 PM
I created this .bat and it works
pushd \servername\laps
msiexec /i "laps.x64.msi" /quiet
popd
Simon
If you find that my post has answered your question, please mark it as the answer. If you find my post to be helpful in anyway, please click vote as helpful. Regards Simon Disclaimer: This posting is provided AS IS with no warranties or guarantees, and confers no rights.
Tuesday, February 27, 2018 10:02 PM
It shouldn't be this difficult. I deploy it using a GPO. Computer Configuration > Policies > Software Settings > Assigned Applications. I added the unc path to the share and done,e.g. \myserver\deployments\lapsx64.msi. Transparent to the user and no noticeable delay at login. The only time I could see using the commandline parameters is maybe if you are using SCCM.
Friday, March 9, 2018 9:39 PM
It shouldn't be this difficult. I deploy it using a GPO. Computer Configuration > Policies > Software Settings > Assigned Applications. I added the unc path to the share and done,e.g. \myserver\deployments\lapsx64.msi. Transparent to the user and no noticeable delay at login. The only time I could see using the commandline parameters is maybe if you are using SCCM.
this method doesn't work for me
At this point, here is what works:
1. created .bat script
2. run powershell or cmd as administrator manually
3. run the .bat script within powershell/cmd
this process installs the software.
things that haven't worked:
GPO using computer logon script
GPO using user logon script
GPO using Software Installation as mentioned above.
manually double-clicking the .bat script
right-clicking the .bat script and choosing "run as administrator"
I should mention that in the script I am doing some other things such as creating a folder on the local computer, copying the .msi to that folder, then using msiexec to run the install. Finally, I'm deleting the files and the folder that was created by the script. All of this works except the actual software installation. I have verified this by leaving the folder on the local drive.
At this point, I've tried so many things I'm completely confused by the process.