Windows 10 Managed Installation with MSI Will Not Run
I've got a Managed Installation that points to a software record with an associated file (MSI), but it will not install on a Windows 10 PC. I selected Override Default Installation and entered /a Surface_Dock_Updater_v1.0.8.0.msi /qn /L*V "install.log" in the Full Command Line: field. It downloads to the Windows 10 PC, but it will not complete the install and does not even generate a log. I am able to get it to complete the install and generate a log if I manually launch a command prompt As Administrator  and run the exact same command as above.
Am I doing something wrong or does Windows 10 require a different method of running MSIEXEC via the K1000?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
8 years ago
The command line argument '/a' performs an administrative install, i.e. if the MSI contained an internal cabinet, it extracts the files to a target folder and creates a "new" MSI with flags that it is now an uncompressed MSI. If it was already uncompressed, the files are merely copied to the target location, along with the MSI.
Comments:
-
missed that... well spotted... - Pressanykey 8 years ago
-
I've tried it without the /a switch, but that didn't start the install or create a log file either. - JonCampbell81 8 years ago
Posted by:
anonymous_9363
8 years ago
>I've tried it without the /a switch, but that didn't start the install or create a log file either.
Remember to use explicit paths rather than relying on the system to "find" the files. The most efficient way to do that would be to wrap the command line into a command file and use the '%~DP0' prefix to the file names:
Remember to use explicit paths rather than relying on the system to "find" the files. The most efficient way to do that would be to wrap the command line into a command file and use the '%~DP0' prefix to the file names:
msiexec /i "%~dp0Surface_Dock_Updater_v1.0.8.0.msi" /qn /l*v "%windir%\temp\install_Surface_Dock_Updater_v1.0.8.0.log"
Posted by:
Pressanykey
8 years ago
Hi,
as you can install it manually using an Administrator account, I suspect it has something to do with the "system" account of the deployment tool. Have you tried using a "system" account (psexec) and manually installing it?
Cheers
Phil
as you can install it manually using an Administrator account, I suspect it has something to do with the "system" account of the deployment tool. Have you tried using a "system" account (psexec) and manually installing it?
Cheers
Phil
Comments:
-
I'm not saying it's an administrator account. I'm saying if I launch a command prompt AS ADMIN (right-click Start button > select Command Prompt (Admin). - JonCampbell81 8 years ago
-
That is an account with administrative permissions...
Please try my suggestion regarding the psexec tool and see if you have the same result as you do with your deployment tool. There are many msi based installation packages that do not install (correctly) using the system account. If you can conform that this is not the case we will be a step further.
Phil - Pressanykey 8 years ago-
When I psexec into the PC and run the same command with a local admin account it at least attempts the install as the log file is created, but the software does not actually install. - JonCampbell81 8 years ago
Posted by:
Cldstrife
8 years ago
Hello,
I believe with MSI files you need to use msiexec.exe with " /a Surface_Dock_Updater_v1.0.8.0.msi /qn /L*V "install.log" ".
So it should be :
msiexec.exe /a Surface_Dock_Updater_v1.0.8.0.msi /qn /L*V "install.log"
Hope this helps,
Robert
