Software Deployment

a little more detail would help. If you mean the download from adobe, yes. what about it?

Sorry for the lack of detail. Im trying to see what others have done to get a package. I did a snapshot and whenever I install it the Digital Editions runs through its install all over.

Hm, still not clear on what you're trying to accomplish, what software it is, etc. Is Digital Editions the name of the software. Is there a reason you did a snapshot? Aren't most Adobe installations MSI's now?....

details, details!

This is the link to the software.
http://www.adobe.com/products/digitaleditions/#download

Does not come as an msi. Take a look at it. It installs through flash. So the only way to package it is through a snapshot.

OK, I see now what it is - but setup capture is not the way to do it. For one thing, this setup relies on entering a userid and password, which you never want to capture, and also seems to read computer hardware information - ditto on the capture -- don't do it. If it was just files that'd be different.

Contact Adobe and see if they have an MSI or an exe to download

Thanks for taking a look. I was using the other option. The one that did not use a user name and password. I really can't see a good approach to creating an msi for this software. I will just have to email them.

ORIGINAL: pisanom
Thanks for taking a look. I was using the other option. The one that did not use a user name and password. I really can't see a good approach to creating an msi for this software. I will just have to email them.


Maybe I missed something but IIRC you had to do username/pw for both options - IOW you have to have an adobe ID. When I tried continuing without entering an ID it failed. But even if you didn't need the userid the second option keys off of or reads hardware information, which is also a big no-no for repackaging. If it's at all like flash or shockwave they should have download versions for distribution.

There is no install for Digital Editions it just runs off of the executable. So not much you can do with it packaging wise....or Wise packaging :-)

According to the documentation, silent install can be run using the /S command line switch

http://www.adobe.com/devnet/digitalpublishing/pdfs/DigitalEditions_1x7_Standalone_Installation.pdf

However, when I contacted Adobe on their forums to report this didn't work
http://www.adobeforums.com/webx/.59b7cca8?@422.bOlmiw1N3p3@

The informed me that
"We didn't test against or design for silent mode (the switch handling came in from the installer framework).

I've entered in a bug so that we can decide to either properly support silent mode, or at least ignore the command line switch without causing an error.

In the mean time, as you noted the easy workaround is not to us the /s switch"

Ooops!

I have had a response from Adobe and they say the case of the switch is the trick. It requires and uppercase /S not a lowercase /s otherwise you see an error.

I have then found that Deployment Solution was not happy trying to run this command, so put together a simple VBscript to run the installation as follows

the varPackage variable is the network location of the Digital Editions EXE install file


Dim objFSO, objShell, objExec, varPackage, varSwitches, varInstallCommand

Set objFSO=CreateObject("Scripting.FileSystemObject")
Set objShell=WScript.CreateObject("WScript.Shell")

varPackage="\\server\source\DigitalEditions\digitaleditions1_7_setup.exe"
varSwitches=" /S"

varInstallCommand=varPackage & varSwitches

Set objExec=objShell.Exec (varInstallCommand)

Do While objExec.Status = 0
WScript.Sleep 100
Loop



The version 1.7.1 I downloaded from here ...
http://www.adobe.com/support/digitaleditions/ts/documents/kb403051/digitaleditions1x7x1.exe

... on this page ...
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb403051&sliceId=2

... seems to accept either upper or lower case '/s'.

Also if you get the following registry keys down before it is run, you avoid the EULA accept:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Adobe\Digital Editions]
"InstallPath"="C:\\Program Files\\Adobe\\Adobe Digital Editions\\digitaleditions.exe"
"FileVersion"="9.0.1085.27"
"EULA"="1.7"These keys are very specific to the version so would need to be double-checked before using them.

Daz.

It's a Nullsoft install, rather than an msi - go Adobe!

Did anyone get rid of the activation part?
Using the /S parameter it installed perfect... But on the first launch of the shortcut, an activation screen pops up and I am stuck here. We want to automate the option "Don't Authorize". Asking the users to finish activation can be tough. Any help would be appreciated.

I'm confused...

We want to automate the option "Don't Authorize".You want it to run unauthorised? Doesn't that mean it's crippled in some way?

Asking users to finish activation can be tough."Do you have a site license, then?

BTW, those searching the 'Package KB' for details...the entry is incorrectly titled 'Digital Additions'. I've emailed Bob with the details. Even so, when you get there, there's nothing about activation.

You can also avoid the EULA pop up while taking the second snapshot by clicking on the Accept License automatically the reg value will cahnge.Also in property table you can put Accept=Yes

I am sorry for the confusion.But let me try and tell you everything I know here.
This app is for the Library. They have a set of ebooks and the users would need Digital Editions to read these ebooks. The application is a very simple install and works fine until there.
When we first launch the shortcut, the activation screen pops up. There are two options for activation.
1. If you choose to authorize the computer and create/provide an adobe id, it allows you to download and read DRM protected items on upto 6 computers.
2. If you do not authorize the system, whatever ebooks you download are tied to that system

I dont think our library wants any users to download ebooks. They just need the software to read ebooks from the library. So we've been asked to choose "Don't Authorize Computer"
No matter which option is chosen, the system has to be online for activation to succeed.
Now from a packager perspective, the reg keys that get created after activation (HKEY_CURRENT_USER\Software\Adobe\Adept\Activation) are machine specific. If I capture these into my package, it would work only on the same system.
I am trying to somehow make it a part of my package or avoid the activation completely rather than leaving it to the users. I am starting to feel this is impossible.

This link here has all the screenshots. http://library.ellibs.com/help/ade-installation

Perhaps unpacking the set-up stub might provide a clue as to how the authorization is done? See this page http://innounp.sourceforge.net/ and particularly the -m switch mentioned.

Can anybody help me regarding the supression of the activation screen pops up after lunching the shourtcut...................
I tried with exporting the (HKEY_CURRENT_USER\Software\Adobe\Adept\Activation) regkey to msi but it did't wrked out :-( as u said it is machine specific......

please create a new post. do not resurect a 2+ year old post.