Installing an MSI remotely psexec

I'm trying to install an MSI package using the following command:
psexec \\computername -u "domain\user" -p "password" cmd /c "msiexec.exe /i""C:\file.msi" /quiet

Nothing is happening at all..

If I try the WMIC version...

WMIC /node:PCNAME product call install true,"" , "c:\File.msi" I get a 1603 error.

I'm using a script to copy my msi files to the C drive on the remote machine.  I just can start the install.
WellingtonISAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Vadim RappCommented:
General reasons of error 1603 are at http://support.microsoft.com/kb/834484 . For more specifics, collect detailed installation log and post here. Specify /l*v c:\install.log in the command in addition to everything else. Make sure domain\user has permissions to write to c:\ , or make it another directory.

"nothing is happening" because of the switch "/quiet", otherwise you would probably see the same error.

There's no need to run cmd.exe, you can

psexec \\computername -u "domain\user" -p "password" msiexec.exe /l*v c:\install.log /i C:\file.msi /quiet
0
WellingtonISAuthor Commented:
Running the command - PSexec has executed on the machine I see this in the processes of task manager.  Its just sitting.  I can't even see the log file created.
0
NVITCommented:
Is it an interactive-only type of install?
0
Cloud Class® Course: Microsoft Office 2010

This course will introduce you to the interfaces and features of Microsoft Office 2010 Word, Excel, PowerPoint, Outlook, and Access. You will learn about the features that are shared between all products in the Office suite, as well as the new features that are product specific.

WellingtonISAuthor Commented:
It should not be.  It pops up and you hit next - then it installs until it finishes.
0
Vadim RappCommented:
/quiet ensures that there's no interaction.

You can run cmd.exe with the same psexec, then in cmd.exe window enter msiexec with /quiet and see what happens.

Check switch -i of psexec, maybe it will help.
0
WellingtonISAuthor Commented:
I'll try -i
0
WellingtonISAuthor Commented:
Nothing is working.  I'm not sure why but I'll try another way.
0
WellingtonISAuthor Commented:
i think I must be this file.  I even tried copying the bat file to the PC and running it and it will not start the MSI
0
Vadim RappCommented:
run process monitor on remote and see is msiexec starts, then if it finds the msi file.
0
WellingtonISAuthor Commented:
I did  and it does and so does msiexec.exe
0
Vadim RappCommented:
What happens if you manually run on the remote machine the same command as in psexec?
0
WellingtonISAuthor Commented:
OK head scratcher.. If I go to a cmd prompt and type msiexec /i "C:\file.msi" it pops up the installation, If i hit next it will install...  If I use the /qn It shows in in the processes, but it doesn't install the program.
0
serialbandCommented:
You can't install that one remotely, if /q is still popping up a dialog box that you need to hit next to.  Someone messed up that MSI package and forced it to be interactive.  When you run that remotely, it's still waiting for someone to hit next, even if it's not popping up a dialog box into a visible place.  That dialog box is waiting for someone to respond, so that's why it's stuck.

What is it that you're installing?  There may be answer files that need to be set up or possibly some other options that can be passed to the file, although with msiexec, those options may be limited.  Depending on the software, you could find an alternative .exe installer or you could extract the package and repackage it.
0
WellingtonISAuthor Commented:
It's called PowerMic Citrix Extension Client  and SpeechMagic Extension Client. I wonder if these were "self made" into msi files.  It's for Dragon Enterprise version.
0
Vadim RappCommented:
The two ways to deal with that are:

1. contact software vendor, complain on the problem, hoping that they would listen. Drawback: the chance is about 0.1%.
2. Repackage or fix the installation (because what serialband said is almost certainly the case). Drawback: this requires very nontrivial qualification and tools. You can hire someone who has both.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
WellingtonISAuthor Commented:
GOing to try to download the origional files and repackage them.  As long as I know the commands are correct eventually I'll get it to work.  thanks.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 7

From novice to tech pro — start learning today.