On Fri, Oct 9, 2009 at 1:56 PM, Petersen, Tom < tom.peter...@sduniversitycenter.org> wrote:
> I tried using this to push the client: > > c:\PsTools\psexec -u usdsu.local\username -p password @ucs186.xml -d > msiexec /i "\\usdsu.local\storage\its\uc-its\wpkg\WPKG Client 1.2.1.msi" /qb > SETTINGSFILE=\\usdsu.local\storage\its\uc-its\wpkg\settings.xml > When using psexec or beyondexec in this manner, the credentials are only used to authenticate on the remote workstation--they are not "passed through" to authenticate you to network resources. There is, however, a way around this. First, grant the "Domain Computers" group read access to the network resources you need. Then, use the "-s" switch with psexec or beyondexec to connect as the local system account. Now, you (or the system account, actually) should have access to the network share. This may or may not be worthwhile if you're only going to use it to install the wpkg msi. However, I run wpkg.js under the system account, so I use this method for all installs. Cheers, --Troy
------------------------------------------------------------------------- wpkg-users mailing list archives >> http://lists.wpkg.org/pipermail/wpkg-users/ _______________________________________________ wpkg-users mailing list wpkg-users@lists.wpkg.org http://lists.wpkg.org/mailman/listinfo/wpkg-users
