Re: published software: Unabled to extract deployment information.

Never mind - I figured out how to do it with a .zap file. I do remember
being able to publish an .exe file directly using group policy. Or maybe my
mind is slipping faster than I realize. Thanks for your help.

"Jim Dykes" wrote:

So is this a change with Server 2003? A few years ago I deployed a lot of
software with .exe extensions using group policy. I even used wscript.exe to
call vbscript files that then ran installations. Is there a way to "write"
an msi file using text editor that will point to the .exe I want to install?

"Anthony" wrote:

Documentation!
It also says msp's, but you can't run an msp in GPO. I don't know what they
were smoking.
Its an interesting background, because a lot of industry has spent a lot of
time converting to msi's. IBM took a long time to do this properly with
Domino/Notes. A lot of people have only managed to convert to msi's by
re-writing their setups as custom actions. Now MS introduce Office 2007 that
can not be installed properly by GP using msi! If we have to use a
deployment tool for Office, we may as well use it for everything and forget
GP and Windows Installer. So it is back to installshield and /r to create
answer files!
Anthony,
http://www.airdesk.co.uk



"Mathieu CHATEAU" <gollum123@xxxxxxx> wrote in message
news:u4dL%23Wh5HHA.2312@xxxxxxxxxxxxxxxxxxxxxxx
Hello,

I was thinking as you, but this indicates that exe are supported:

File types that you use with Group Policy Software Installation
http://technet2.microsoft.com/windowsserver/en/library/3512b600-5bb4-4dae-8b2c-7b71ef9951a01033.mspx?mfr=true

they mention setup.exe & install.exe


--
Cordialement,
Mathieu CHATEAU
http://lordoftheping.blogspot.com


"Anthony" <anthony.spam@xxxxxxxxxxxxxx> wrote in message
news:%232FZaVh5HHA.4164@xxxxxxxxxxxxxxxxxxxxxxx
Jim,
Group Policy software installation is in effect a set of commands for
WIndows Installer, and requires an msi file.
To use an exe you need to:
- Unwrap it if it actually contains an msi
- Repackage it as an msi
- Use a custom action inside an msi to execute it (a "wrapper")
- Use a different deployment method like SMS or Altiris
Hope that helps,
Anthony,
http://www.airdesk.co.uk




"Jim Dykes" <JimDykes@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D88DFE2E-E26E-45AD-8804-C60262D32EE7@xxxxxxxxxxxxxxxx
I set up a domain DFS root, copied an .exe file to it and tried to
publish it
using a group policy. I keep getting the error "Add operation failed.
Unable to extract deployment information from the package." I've seen
the
article saying that inadequate space on the volume containing the sysvol
folder can cause this, but the system partitions on both of our DCs have
about 60 GB each. I am able to sucessfully publish files with an .msi
extension. We run Server 2003 R2 and our DFS structure is as follows

root: \\domainname\software
replica: \\domaincontrollerA\software
replica: \\memberserver\software

I don't think this is a DFS issue, though, as the msi files work.
Thanks in
advance for your assistance.







.

Relevant Pages
Loading