I need to create a deployable package of MSN Messenger 6.1 for deployment via GPO. I found some details in the Package KB and when I follow these instuctions I can deploy the msi from a Win 2003 server to XP clients. However when I try to add the same msi to a GPO on a Win2k server I get an error about being unable to extract deployment information. And the following error is placed in the Application event log:

Product: MSN Messenger 6.1 -- The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2228. The arguments are: , Extension, SELECT `Extension`.`Extension` FROM `Extension` WHERE `Extension`.`ProgId_` = ?

If anyone has any ideas they would be greatly appreciated.
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
Can you tell me how you deployed it onto XP clients from a Windows 2003 server. My MSI doesn't do that. I've followed the following article.

http://www.appdeploy.com/packages/detail.asp?id=213

It talks about fixing the MSI. How do I do this?
Answered 04/01/2004 by: Legendary
Yellow Belt

Please log in to comment
0
Yeah that is the article I followed. To edit the tables you need to use a tool like Orca which come as part of the Windows Installer SDK which you can download from the microsoft site.

Using Orca you open the MSI and edit the tables as mentioned in the article.

Hope this helps if not let me know where you are getting stuck.
Answered 04/01/2004 by: PuterFix.biz
Senior Yellow Belt

Please log in to comment
0
Well I encountered the same problem. I couldn't deploy the software package msnmsgr.msi through GPO in a Win2000 server/client situation even if I followed the instructions published on http://www.appdeploy.com/packages/detail.asp?id=213 .

There is a solution to this problem which is very simple but effective:

Remove "InstanceType"=dword:00000000 from the registry entry below:
[HKEY_CLASSES_ROOT\Installer\Products\C838BEBA7A1AD5C47B1EB83441062011]
"ProductName"="MSN Messenger 6.1"
"PackageCode"="637043860D71ACA4BA61C92FDF062011"
"Language"=dword:00000013
"Version"=dword:060100d3
"Assignment"=dword:00000001
"AdvertiseFlags"=dword:00000184
"ProductIcon"="C:\\WINDOWS\\Installer\\{ABEB838C-A1A7-4C5D-B7E1-8B4314600211}\\MsblIco.Exe"
"InstanceType"=dword:00000000
"Clients"=hex(7):3a,00,00,00,00,00

And use the complete stripped entry as a basis for a MSI to install these registry settings, which purpose is solely to advertise the package Messenger 6.1.
You could look upon this MSI as being a helper MSI (which can be installed through GPO)to give the user elevated rights to install the msnmsgr.msi either manually or through a commandline action triggered by a script with the command msiexec /i msnmsgr.msi /q

Rien van Lieburg
Systems Engineer
Wageningen University
The Netherlands
Answered 04/22/2004 by: Rvlieburg
Third Degree Blue Belt

Please log in to comment
0
I don't know if this applies to any of your situations, but keep in mind that you will also receive this message "not able to extract deployment information" if the application you are trying to deploy is already installed on the server from which you are working. Uninstalling the application, if possible, does not always correct the situation/clear the message.

A way around this: install the adminpak.msi for Windows 2000 Server (or for 2003, if that is your platform) on a computer that is a member of the domain, and use it to define your software package and Group Policy Object.

I worked on a server once that displayed this message when trying to deploy a WinZip package that had worked without fail in other environments. Uninstalling WinZip from the server had no impact. Installing the adminpak on a domain workstation and using it to set up the GP was the only way to get it done.

Craig --<>.
Answered 04/26/2004 by: craig16229
Third Degree Brown Belt

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