UNC and Drive Letter issue in Package
I have an in house build software thats gives me error of Drive H:\ i checked the Property Manager and there is a drive H:\ already been there so i map the drive H:\ with the same UNC, after mapping that application is installing through the GUI (double click on the application and go through step by step) and installed perfectly fine after that Mapped UNC but if I run it through command line (msiexec /i <path of the app> /qb!) gives me error of drive H:\ ... I wonder if anybody can help me on this issue ...
Community Chosen Answer
Chances are the mapped drive is mapped to the local user context; since the agent executes against local system account there may be a priveleges issue. Does it work if you supply the full UNC path?
I always recommend using full UNC, and maybe even IP's in command lines; why? It can't go wrong if I run it from a station that has fiddled with their H: mappings.