I need to roll out MSN messenger to a few computers. I have the MSI and the Command Line command that will perform a silent unattended install (as listed on appdeploy - thx).

I have a couple of questions though; Where in group policy do I specify the command that I want to execute on the MSI file? Do I need an mst file? my command is of the format msiexec /i ***.msi (some parameters) /q. Can't be that difficult, surely? Please help.

On another note I have set up an SMS server which seems OK, but my question is 'Do all software installations in SMS have to be initiated by the client?'. I have set up SMS to distribute MSN Messenger - but I do not have any way of pushing the application out to the clients. I seem to only be able to advertise and then require user input to install. Not ideal as I cannot rely on any users to do anything quite as taxing... That is why I am now just going to push it out using group policy - If I can put a basic command line into it somewhere.

Any answers appreciated.
0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


If you want to push Messenger out to machines, you can follow a procedure that can be found in this thread:


What you are really doing here is to cause the app to install with elevated admin privileges as the computer starts up, but before the user logs in. Therefore, specifying a silent install is not necessary. The "push" of the software via GPO takes care of it. Customization of the app is taken care of by an .mst file, which you can specify when you define your software package.

craig --<>.
Answered 04/27/2004 by: craig16229
Third Degree Brown Belt

Please log in to comment
Thx for the reply, I am gradually getting there.

I do still have a problem however. I know that the MSI file will install from the command line with the following: msiexec /i MsnMsgs.msi IAGREE="Yes" ADDEXPLORERTOOLBAR="" SETSEARCHENGINE="" SETHOMEPAGE="" /q

Now, I thought this was what I was looking for. But what I actually need is an MST file to transform my MSI to the same effect as the command above. So I have downloaded Orca and attempted to make an MST file. In the Property table i have changed IAGREE from no to yes. In the checkbox table I have changed all values to "". Bit of a guess really and not to my surprise it was another thing that does not work.

When I implement this with GPO i get an Userenv error in the event log returning a failure status code of 1603. Same error I have been getting for quite some time now.

Does anybody know how to exactly how to create the MST file that will amend the MSN messenger MSI file so that it exhibits the same characteristics as the command above?

Help is appreciated - I may eventually be able to successfully rollout an app with GPO after long enough of trying.
Answered 04/27/2004 by: jc_501
Yellow Belt

Please log in to comment
What you have is a general error code

here is how to log further information:


And here is what the error could mean:


Before adding the MSI to a GPO allways try to run it first on a test mashine

This one would probably fail even that.

Sweede :-)

Answered 04/27/2004 by: Sweede
Second Degree Green Belt

Please log in to comment

Have you tried these modifications?


I battered my head off a brick wall with MSN Messenger for some time before I got help there from Carolyn Napier from Microsoft's Windows Installer team. I'd have never guessed the problem otherwise...

That was relating to 6.1, but I have been able to get 6.2 to work as well with the same modifications, and also a transform which removes the various junk they put in the installer this time...

Answered 05/04/2004 by: MarkS
Senior Yellow Belt

Please log in to comment
Thanks Mark,

That was indeed the method I used in the end. Had a few small problems as I hadn't used orca or created an MST file b4 but I can confirm that it does work for 6.2 and deploys well using group policy.[:D]
Answered 05/05/2004 by: jc_501
Yellow Belt

Please log in to comment