Software Deployment

yes... normaly with a bad table. or some times some clever appbuilder has put a shortcut in an odd place for it to be called by the app it self but they are nomaly located in common files.

check your Shortcuts and Directory Tables.
the shortcut table will tell u if it's a real shortcut or if it's a .lnk file that u captured in error.
if it's a real shortcut then check the directory it's installing under
then check the Directory table to find how the pathing works. the error will problably be there someware.
run the "check for tabble error or validate tables" or what ever the equivent is in your software first. you might find the error faster then trying to translate your tables.

if it not in the shortcut table then check your file table for the *.lnk file. if it's a dub. (IE u have it in startmenu allready) then it's prob an error and remove it from the table, recomple...

hopefully that will help.

Wait.. you didn't repackage this app did you? I'm assuming we're talking about the original MSI and an MST you created?

I hope you did repackage it.

I did :)

It's a mongrel of an app because it won't work with redirected My Documents and User Profiles as a native msi.

Adobe will never learn regardless of how many times I tell them to not hard code :(

Jasonj86,

Please send me a detailed description of the problem and I will report it to Adobe in Santa Cruz for you. I am on the BETA team for Acrobat and any new info will go directly to the packagers.

My email is listed below.

Jim, I took two points off for repackaging a vendor MSI.

Well we all know the rules.....but sometimes depending on the platform your working with.....vendor msi's must be repackaged.

I do it all the time because of the rules I'm bound to by the company I'm with.

I have recaptured and repackaged just about ALL of the Adobe apps because of it.

Thats the way it is sometimes.

I will have to agree with Jim here.

Vendor installations is preferred not to be modified due to support for later patch releases from the vendor.
But when they do not manage to do a nice job with the installation breaking the rule may be the only alternative to be able to install the application through the distribution tool you're using.

Rules exist to be broken ;)

Hi folks,
agree with (part of) the comments about the packaging of the adobe applications.
But correcting errors with a new error?
That can't be the best solution.
We deploy most of the Adobe apps by GPO with slightely altered orginal packages.
And especially the Acrobat apps have gotten a lot better with version 7.
I'm more and more confident, not to repackage original packages, because of various reasons (a lot of them are discussed regularly on this platform).
My experience is, your initial workload is maybe higher to analyse and correct an original package, but when updates and new versions arrive, you get back more than that.
Nick

ORIGINAL: turbokitty

Jim, I took two points off for repackaging a vendor MSI.


Hmmm - If you can get this app advertising per user and deployed via AD GPO then you can take the points off... [;)]

I agree with Jim, depending on your environment there is nothing wrong with repackaging the odd vendor MSI if you have no alternative.

Cheers,
Rob.