It is a combination of things, psexec wants quotes around your command and
windows wants quotes around the filename which has spaces in it. You also have
to put \" infront of embedded quotes (quotes within quotes).
something like this:
c:\PsTools\psexec -u usdsu.local\username -p password @ucs
I don't like to add yet another remote access tool (psexec etc.) to the
clients.
I use the remote scheduling features of schtasks. From a central
administration server (only this one gets through the clients' firewall)
I schedule the run of the installation on the clients (running as the
clie
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
> SETTINGSFIL
I have never gotten that working. I traced it down at one point, and it
turns out when executed in that manner the process doesn't have access to
the network ( at least, in my situation ), so obviously the install failed.
I just wrapped the msi into a script and pushed it out via a startup script
I use it as intended - wpkg client installed, wpkg etc living on a NAS share.
I automate software wherever I can - not because it saves time at that point
(often it is quicker to manually install on smaller LANs) but because, when a
PC fails or I need to add an additional PC it saves masses
