Is there any way, while running your msi with mst silently, to ask it to prompt you for a specific field? In other words, stop or pause while it waits for user input? [8|]

This is in regard to Adobe Acrobat 7 Professional, and we dont have a site license but I still need to deploy. I would like the install to ideally stop and wait for user input of the single-user serial number and upon advancing to next window have the silent install pick-up and continue?

Thanks in advance....
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
Gee, it's a good thing there are no Adobe Agents out there patrolling the web for license violations [:D]
Answered 11/30/2005 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
ORIGINAL: aogilmor

Gee, it's a good thing there are no Adobe Agents out there patrolling the web for license violations [:D]

This is legit. We are deploying single user licenses but what ends up happening is the package gets created with an single user license, and the activation code kicks off after 30 days. So we currently have to manually un-install then re-install from the CD (which, by-the-way, we've had all along). But this isnt exactly automation at it's best.

Anyone have some helpful ideas, or at the very least can appreciate the problem?? [8D]
Answered 11/30/2005 by: pumagaju
Senior Yellow Belt

Please log in to comment
0
Is there any way, while running your msi with mst silently, to ask it to prompt you for a specific field?

Running the install silently - by it's very nature means that there is no UI. The only way I can think that you might get around this is to use a public property in the MSI then launch the MSIEXEC command line from a VBScript - which first prompts the user for the serial number via an input box. This input can then be passed to the MSIEXEC command line...

Otherwise you may be able to add a custom action (with an input box) early in the install - again to complete a property for the serial number. Not sure if this would pop up with a silent install though..

Good luck,
Rob.
Answered 12/01/2005 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
I still think you've got the wrong type of license. We've deployed reader to thousands of desktops with no problem. The other adobe products required that we buy the correct license to install properly and stay silent. I remember having problems like you describe, trying to fit the single user install to multiple computers.
Answered 12/01/2005 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
0
What I would do if I were in your shoes is:

1. Attempt to update the licence code using command line properties. I've done this successfully with SnagIT 7.2.4.
All I did was look at the properties table, and located where in the MSI it updates the registration codes. Once these
were isolated, I was able to figure out what property values to set.

--- If the above doesn't work ----

2. Try to locate the registrys keys where the licence codes are stored, and then using custom actions or an MSI wrapper
you could update these keys by adding the the Registry table. You could add public properties to your installer, and
then you'd be able to use the command line to auto-register the product.

3. If you really want to get 'hi tech', you could create a new table that stores all your licensing information.

EG Licensing Table
Computername, License Code.

You would then be able to update the properties, or registry keys through custom actions. I've done this type of
thing with our Outside View 7.2 deploy. We have 40 install keys, all individually licensed by the workstation.


Regards,
----- Robb -----
Answered 12/02/2005 by: Robb Thomas
Senior Yellow Belt

Please log in to comment
0
There are many details written into license agreements. If we really want to follow every line in every agreement, it would often mean that repackaging itself is a violation.

There are several applications (which I will not go on the record and name) in our environment that have stipulations about "re-engineering" or "re-compliling" in their legal ease, so we broke the agreement by repackaging them.

Have we broken the letter of the law by doing so? Yes. Have we broken the spirit of the law by doing so? I don't think so. Software vendors are not going to pursue every part of their agreements with every customer. When it gets down to it, they only want to know two things: How many licenses have you purchased, and how many times do you have it installed.

Craig --<>.
Answered 12/03/2005 by: craig16229
Third Degree Brown Belt

Please log in to comment
0
If you REALLY want to get fancy, hack the interface dialogs and don't run it silently. Bypass all dialogs except for the "enter license key" dialog (or create your own). As long as your MST supplies the appropriate responses, then you can get away with bypassing dialogs. The only trouble you'll have is if the dialogs kick off CAs. Adobe loves to stick CAs in their installs, so keep a sharp eye out for them.

Like I said, this is rather complex. Don't attempt unless you know how MSI Dialogs work, or have the time & gumption to figure it out.
Answered 12/05/2005 by: VikingLoki
Second Degree Brown Belt

Please log in to comment
0
Thanks all for the replies. What I ended up doing was scripting the install out the old fashioned way (with visible dialogs) since the site license is on the way and I didnt/dont have the time to re-engineer another solution.

regards,
Answered 12/15/2005 by: pumagaju
Senior Yellow Belt

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