MSI installation from a UNC path

  • nivek03
    Senior White Belt
  • How helpful is this to you?
  • Average Rating 3
  • 11808 views
  • 06/28/2012

Is it possible to install an .msi via a UNC path? I've tried the following with no luck. Anyone know if this syntax is even supported?

msiexec.exe /quiet /lv c:\install.log /i \\xxx.xxx.xxx.xxx\folder\install.msi /norestart

Answer Summary:
I eventually figured out that you have to put quotes around the UNC path. Thanks for all the responses!
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

3

msiexec /i "\\xxx.xxx.xxx.xxx\folder\install.msi" /lv c:\install.log REBOOT="ReallySuppress" /qn

Answered 06/29/2012 by: asman
Purple Belt

  • I eventually figured out that you have to put quotes around the UNC path. Thanks for all the responses!
  • So this works via the command prompt under my domain admin account which has access to the UNC path. I would ideally like this to be able to run under the local Administrator account. In the local Administrator account I have to authenticate to the .msi location before I can run the command or it won't find the .msi. How can I get around this?
Please log in to comment
3

You only need the quotes if there is a space in the unc path.  I run msi's from my server share all the time without quotes

Answered 06/29/2012 by: SMal.tmcc
Red Belt

Please log in to comment
2

To run from a UNC as local account do a (or add to your script):

net use \\server\share password /user:domain\user

this will connect you to the server.  You can always map a drive letter and call the msi via drive:\ instead of unc.

Answered 06/29/2012 by: SMal.tmcc
Red Belt

  • create a domain user "kinstaller" that has only rights to the shares and use this for any task like this.
  • Great idea, thanks!
Please log in to comment
1

Suggestions made in previous replies to inspect the verbose log file are obviously a good idea, but have you seen what happens if you try your install with a full User Interface, any error messages ?

Spartacus

Answered 06/29/2012 by: spartacus
Black Belt

  • This was definitely helpful! I changed /quiet to /qr which helped me identify how to structure my UNC path.
Please log in to comment
1

Just a thought...

You should have checked it in the install.log file first.. I don't know for what reason you have created it..

Anyway, Glad to hear that you have found the solution..

 

Answered 06/29/2012 by: jagadeish
Red Belt

Please log in to comment
0

What does your install.log says? Please check and let us know..

Answered 06/28/2012 by: jagadeish
Red Belt

Please log in to comment
0

I've used unc paths before and I can confirm that it works. What exactly does it do when it fails? How are you running the command, Kace, batch script, other?

Answered 06/29/2012 by: Ben M
Ninth Degree Black Belt

Please log in to comment
0

Are you running the command in SYSTEM context or as an administrator?

The SYSTEM account might not have access to the share where your installer is located.

Answered 06/29/2012 by: andemats
Second Degree Black Belt

Please log in to comment
Answer this question or Comment on this question for clarity