I am trying to deploy the Microsoft package called msdrmclient.msi using SMS 2003. And on every machine I push this too it hangs on Status Message 10005. Here is what it says:

Program started for advertisement "HII20460" ("HII0017D" - "RMS_MSDrmClient").
Command line: "C:\WINDOWS\System32\msiexec.exe" /i "\\NYC-SM-CRP01\SMSPKGD$\HII0017D\msdrmclient.msi" /i ALLUSERS=1 REBOOT=R /QN REINSTALLMODE=omus REINSTALL=ALL
Working directory: \\NYC-SM-CRP01\SMSPKGD$\HII0017D\
User context: NT AUTHORITY\SYSTEM

I have also run this same package with verbose logging and it still hangs and never runs and the log file never gets created so I have nothing to view.

What can cause this and where/what should I look at to fix it?

Thank you.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
did you try installing the app by dumping the files from DP Point to client machine and then triggering the install command.
Answered 12/27/2010 by: mekaywe
Brown Belt

Please log in to comment
0
Yes, I did try that and I get the same result.

What log files on the workstations might have the answer?
Answered 12/27/2010 by: mhsl808
Fifth Degree Brown Belt

Please log in to comment
0
The command-line in your post didn't look right (/i switch usage). Was that just a typo?
Answered 12/27/2010 by: sridtech
Senior Yellow Belt

Please log in to comment
0
/i is used to install a product. I've used it hundreds of .MSI deployments.

http://support.microsoft.com/kb/227091
Answered 12/27/2010 by: mhsl808
Fifth Degree Brown Belt

Please log in to comment
0
Agreed. If the command-line you posted is exactly what you have advertised, are you sure its not hanging because of the incorrect usage of the /i switch in the command-line (I see its being called twice). As you have the silent switch enabled, user is not going to be prompted with the window that displays all the siwtches when you run "msiexec.exe". Just a thought.
Answered 12/27/2010 by: sridtech
Senior Yellow Belt

Please log in to comment
0
Good eyes :-) I did not see the /i listed twice. Thank you !!! You deserve to go home for the week!!
Answered 12/27/2010 by: mhsl808
Fifth Degree Brown Belt

Please log in to comment
0
I spoke a little too soon. What we have now proven is a real PITA. We made 100% sure that our Package Properties command line had only "1" /i. We deployed the package again and sure enough in the Status Messages it reports back that our command line is this:

Command line: "C:\WINDOWS\System32\msiexec.exe" /i "C:\WINDOWS\System32\CCM\Cache\HII0017D.10.System\msdrmclient.msi" /i ALLUSERS=1 REBOOT=R /QN

We only have the first /i, not the second. In fact, here is our exact command line:
msdrmclient.msi /i ALLUSERS=1 REBOOT=R /QN REINSTALLMODE=omus REINSTALL=ALL

we have tested this 3 times now targeting different machines and each time this second /i is being added. Where on earth is that coming from?
Answered 12/27/2010 by: mhsl808
Fifth Degree Brown Belt

Please log in to comment
0
msdrmclient.msi /i ALLUSERS=1 REBOOT=R /QN REINSTALLMODE=omus REINSTALL=ALL

that's not right.

either it's msiexec.exe /i msdrmclient.msi ALLUSERS=1 etc.. OR just msdrmclient.msi ALLUSERS=1 etc...
you're using msiexec command line parameters while calling the msi directly.

since SMS will add the msiexec call, just drop the /i in your command line.

PJ
Answered 12/28/2010 by: pjgeutjens
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity