/build/static/layout/Breadcrumb_cap_w.png

MSI installation from a UNC path

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


0 Comments   [ + ] Show comments

Answers (8)

Answer Summary:
I eventually figured out that you have to put quotes around the UNC path. Thanks for all the responses!
Posted by: asman 12 years ago
Purple Belt
3

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


Comments:
  • I eventually figured out that you have to put quotes around the UNC path. Thanks for all the responses! - nivek03 12 years ago
  • 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? - nivek03 12 years ago
Posted by: SMal.tmcc 12 years ago
Red Belt
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

Posted by: SMal.tmcc 12 years ago
Red Belt
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.


Comments:
  • create a domain user "kinstaller" that has only rights to the shares and use this for any task like this. - SMal.tmcc 12 years ago
  • Great idea, thanks! - nivek03 12 years ago
Posted by: spartacus 12 years ago
Black Belt
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


Comments:
  • This was definitely helpful! I changed /quiet to /qr which helped me identify how to structure my UNC path. - nivek03 12 years ago
Posted by: jagadeish 12 years ago
Red Belt
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..

 

Posted by: jagadeish 12 years ago
Red Belt
0

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

Posted by: Ben M 12 years ago
9th Degree Black Belt
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?

Posted by: andemats 12 years ago
2nd Degree Black Belt
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.

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ