Admin studio
I am new to packaging and Adminstudio concepts.
I was given AdobeAirinstaler.exe vendor package and was told to convert into Adminstudio package.I exctracted a msi by installing this exe from the temp folder and also support files.I created transform for that msi through adminstudio.I opened a new ism and chained this msi and added this msi,mst and support files in the streamed files.I compiled and got an exe.when i am installing that exe im getting an error as
"The wizard was interrupted before Adobe air installer could not be completely installed.
Your system has not been modified".
I was given AdobeAirinstaler.exe vendor package and was told to convert into Adminstudio package.I exctracted a msi by installing this exe from the temp folder and also support files.I created transform for that msi through adminstudio.I opened a new ism and chained this msi and added this msi,mst and support files in the streamed files.I compiled and got an exe.when i am installing that exe im getting an error as
"The wizard was interrupted before Adobe air installer could not be completely installed.
Your system has not been modified".
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
anonymous_9363
13 years ago
Adobe apps need to be customised using the appropriate customisation tool, downloadable from the Adobe web site. I think you should also find plenty of guidance in the 'Package KB'.
Posted by:
Arminius
13 years ago
One thing I learned (pretty quickly) is to check this site the first time I do a package. It can save a ton of time that would otherwise be spent spinning your wheels and getting frustrated.
Posted by:
anonymous_9363
13 years ago
I forgot to add that it usually helps to specify a summary the actual problem in your 'Subject' line. Someone who doesn't know Admin Studio might completely ignore your post, purely because of your wording.
Posted by:
spartacus
13 years ago
ORIGINAL: Goutham
.I compiled and got an exe.
Just a personal view, but why compile to an exe ? In my opinion, you would be much better off using straight MSI's and associated transforms. Even if you end up with multiple MSI's and transforms, chaining them is something your deployment tool can handle, surely ?
In the packaging world, heaps of time is spent decoupling MSI's from vendor provided bootstrapper executables, so why compound the problem ?
Spartacus
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
