double-click in Windows?

Report · Jul 23, 2012

Is there any way to create a double-click Windows installer so that the user is not required to put in a serial number or Adobe ID? Using AAMEE, it seems you can only create a "silent" installer. But, since we don't push applications, I don't need that.

Incidentally, the Acrobat customization tools are much more in line with what I would like from Adobe. Too bad they didn't just extend that to the Suite.

Report · Sep 14, 2012

Hi,

AAMEE 3.1 created packages supports UI based installation also. AAMEE 3.1 can be downloaded from http://www.adobe.com/devnet/creativesuite/enterprisedeployment.html . UI based installation is supported only for packages created using AAMEE 3.1 and not AAMEE 3.1 beta or earlier versions. I have written a forum post to explain this in more detail. The link for the post is http://forums.adobe.com/message/4698390#4698390.

Please use AAMEE 3.1 and let us know if you see any issues in UI based installation,

Thanks,

Saransh Katariya | Adobe Systems | skatariy@adobe.com

Report · Sep 14, 2012

This is a very useful development. However, it's not working for me. I have uninstalled all Adobe products (except for AAMEE) on a Windows 7 machine. I built an installer using AAMEE 3.1. I can double-click the installer, but it runs for a few seconds and then backs out and quits. I see this fatal error: "Administrative Privileges required to continue," but I am logged in as an administrator. The log file is below.

Thanks,

Mark

==============================================================

9/14/2012 14:02:30 [INFO] DeploymentManager - Build Version - 3.1.105.0
9/14/2012 14:02:30 [INFO] DeploymentManager - Logging Level verbosity Set to 4
9/14/2012 14:02:30 [INFO] DeploymentManager - Executing immediate custom action for install mode.
9/14/2012 14:02:30 [INFO] DeploymentManager - The CustomActionData string is : mode=install;sourceDir=D:\adobe\adobe_cs6\test\CS6\Build\;installDir=;origDB=D:\adobe\adobe_cs6\test\CS6\Build\CS6.msi
9/14/2012 14:02:30 [INFO] DeploymentManager - Successfully executed the immediate custom action for install mode .
9/14/2012 14:02:36 [INFO] DeploymentManager - Build Version - 3.1.105.0
9/14/2012 14:02:36 [INFO] DeploymentManager - Logging Level verbosity Set to 4
9/14/2012 14:02:36 [INFO] DeploymentManager - Executing the deferred custom action.
9/14/2012 14:02:36 [INFO] DeploymentManager - Obtained the following as CustomActionData
9/14/2012 14:02:36 [INFO] DeploymentManager - mode=install;sourceDir=D:\adobe\adobe_cs6\test\CS6\Build\;installDir=;origDB=D:\adobe\adobe_cs6\test\CS6\Build\CS6.msi
9/14/2012 14:02:36 [INFO] DeploymentManager - mode=install;sourceDir=D:\adobe\adobe_cs6\test\CS6\Build\;installDir=;origDB=D:\adobe\adobe_cs6\test\CS6\Build\CS6.msi
9/14/2012 14:02:36 [INFO] DeploymentManager - Original database path is : D:\adobe\adobe_cs6\test\CS6\Build\CS6.msi
9/14/2012 14:02:36 [INFO] DeploymentManager - OptionXML saved at location :: C:\Users\MARK_M~1\AppData\Local\Temp\{AF6AF1CC-1F2C-40DF-A52F-9F1A043E8F43}\\{F97A39EF-C38C-49CE-AAD5-C514AC13B81B}
9/14/2012 14:02:36 [INFO] DeploymentManager - Build Version - 3.1.105.0
9/14/2012 14:02:36 [INFO] DeploymentManager - Logging Level verbosity Set to 4
9/14/2012 14:02:36 [INFO] DeploymentManager - Initializing Custom Action Data from parameters
9/14/2012 14:02:36 [INFO] Utilities - Folder does not exist
9/14/2012 14:02:36 [INFO] DeploymentManager - Provisioning Tool path is (C:\Users\MARK_M~1\AppData\Local\Temp\{AF6AF1CC-1F2C-40DF-A52F-9F1A043E8F43}\\{39DC3BF9-5B23-4416-B765-5C3FECC39EE8}).
9/14/2012 14:02:36 [INFO] DeploymentManager - Starting to run the custom action for install mode
9/14/2012 14:02:36 [INFO] DeploymentManager - STEP 1: Starting to parse Option XML.
9/14/2012 14:02:36 [INFO] DeploymentManager - Deployment XML created at path :: C:\Users\MARK_M~1\AppData\Local\Temp\{378BC9D0-AE88-496C-A707-A8B24EFD3247}\\{839CB9E7-05C5-4121-A1EB-C5DB8F73D180}
9/14/2012 14:02:36 [INFO] DeploymentManager - Deployment Manager is running in Install Mode.
9/14/2012 14:02:36 [INFO] DeploymentManager - Self-Update BootStrapper Relative Path doesn't exist.
9/14/2012 14:02:36 [INFO] DeploymentManager - Failure in getting Self-Update Folder Path.
9/14/2012 14:02:36 [INFO] DeploymentManager - Override XML created at path :: C:\Users\MARK_M~1\AppData\Local\Temp\{378BC9D0-AE88-496C-A707-A8B24EFD3247}\\{0D9798AB-2F3D-42C4-BB17-AB1CDD2DE59D}
9/14/2012 14:02:36 [INFO] DeploymentManager - No of updates found (15).
9/14/2012 14:02:36 [WARN] DeploymentManager - Failed to find the pdb database.
9/14/2012 14:02:36 [WARN] DeploymentManager - Failed to get the local payload database handle.
9/14/2012 14:02:36 [INFO] DeploymentManager - STEP 2: Starting to launch media Bootstrapper.
9/14/2012 14:02:36 [INFO] DeploymentManager - Bootstrapper launch location is :: D:\adobe\adobe_cs6\test\CS6\Build\Setup\Set-up.dat
9/14/2012 14:02:36 [INFO] Setup - Build Version - 6.0.335.0
9/14/2012 14:02:36 [INFO] Setup - Logging Level verbosity Set to 4
9/14/2012 14:02:36 [INFO] Setup - Start Adobe Setup
9/14/2012 14:02:36 [INFO] Setup - TimeLog: Bootstrapper Start
9/14/2012 14:02:36 [INFO] Setup - TimeLog: Start initial checks
9/14/2012 14:02:36 [INFO] Setup - Action specified - "install"
9/14/2012 14:02:36 [ERROR] Setup - Error parsing command line arguments at - "DISABLE_CCM_DESKTOPSHORTCUT".
Expected arguments are -
--mode=silent
--overrideFile="<FilePath>"
9/14/2012 14:02:36 [FATAL] Setup - Administrative Privileges required to continue
9/14/2012 14:02:36 [FATAL] Setup - End Adobe Setup. Exit code: -10

9/14/2012 14:02:37 [INFO] DeploymentManager - Build Version - 3.1.105.0
9/14/2012 14:02:37 [INFO] DeploymentManager - Logging Level verbosity Set to 4
9/14/2012 14:02:37 [FATAL] DeploymentManager - The return code from the Bootstrapper Process is (1).Stopping the installation process.
9/14/2012 14:02:37 [INFO] DeploymentManager - The install workflow is terminating.
9/14/2012 14:03:57 [INFO] DeploymentManager - Build Version - 3.1.105.0
9/14/2012 14:03:57 [INFO] DeploymentManager - Logging Level verbosity Set to 4
9/14/2012 14:03:57 [INFO] DeploymentManager - Executing immediate custom action for install mode.
9/14/2012 14:03:57 [INFO] DeploymentManager - The CustomActionData string is : mode=install;sourceDir=D:\adobe\adobe_cs6\test\CS6\Build\;installDir=;origDB=D:\adobe\adobe_cs6\test\CS6\Build\CS6.msi
9/14/2012 14:03:57 [INFO] DeploymentManager - Successfully executed the immediate custom action for install mode .
9/14/2012 14:04:04 [INFO] DeploymentManager - Build Version - 3.1.105.0
9/14/2012 14:04:04 [INFO] DeploymentManager - Logging Level verbosity Set to 4
9/14/2012 14:04:04 [INFO] DeploymentManager - Executing the deferred custom action.
9/14/2012 14:04:04 [INFO] DeploymentManager - Obtained the following as CustomActionData
9/14/2012 14:04:04 [INFO] DeploymentManager - mode=install;sourceDir=D:\adobe\adobe_cs6\test\CS6\Build\;installDir=;origDB=D:\adobe\adobe_cs6\test\CS6\Build\CS6.msi
9/14/2012 14:04:04 [INFO] DeploymentManager - mode=install;sourceDir=D:\adobe\adobe_cs6\test\CS6\Build\;installDir=;origDB=D:\adobe\adobe_cs6\test\CS6\Build\CS6.msi
9/14/2012 14:04:04 [INFO] DeploymentManager - Original database path is : D:\adobe\adobe_cs6\test\CS6\Build\CS6.msi
9/14/2012 14:04:04 [INFO] DeploymentManager - OptionXML saved at location :: C:\Users\MARK_M~1\AppData\Local\Temp\{750554BB-9AED-4DE4-B328-244DA327A2C6}\\{116A6B68-D182-428A-BED1-77819A3E341C}
9/14/2012 14:04:04 [INFO] DeploymentManager - Build Version - 3.1.105.0
9/14/2012 14:04:04 [INFO] DeploymentManager - Logging Level verbosity Set to 4
9/14/2012 14:04:04 [INFO] DeploymentManager - Initializing Custom Action Data from parameters
9/14/2012 14:04:04 [INFO] Utilities - Folder does not exist
9/14/2012 14:04:04 [INFO] DeploymentManager - Provisioning Tool path is (C:\Users\MARK_M~1\AppData\Local\Temp\{750554BB-9AED-4DE4-B328-244DA327A2C6}\\{B0584C2B-29BC-4344-8625-F3F72952F30A}).
9/14/2012 14:04:04 [INFO] DeploymentManager - Starting to run the custom action for install mode
9/14/2012 14:04:04 [INFO] DeploymentManager - STEP 1: Starting to parse Option XML.
9/14/2012 14:04:04 [INFO] DeploymentManager - Deployment XML created at path :: C:\Users\MARK_M~1\AppData\Local\Temp\{D561AE85-545E-4912-A798-EBB2EEA41D94}\\{EDC2E988-8846-4B4F-95E5-9EA02880AE28}
9/14/2012 14:04:04 [INFO] DeploymentManager - Deployment Manager is running in Install Mode.
9/14/2012 14:04:04 [INFO] DeploymentManager - Self-Update BootStrapper Relative Path doesn't exist.
9/14/2012 14:04:04 [INFO] DeploymentManager - Failure in getting Self-Update Folder Path.
9/14/2012 14:04:04 [INFO] DeploymentManager - Override XML created at path :: C:\Users\MARK_M~1\AppData\Local\Temp\{D561AE85-545E-4912-A798-EBB2EEA41D94}\\{CFB7D0F5-E37A-4374-A783-A0342C1ED37B}
9/14/2012 14:04:04 [INFO] DeploymentManager - No of updates found (15).
9/14/2012 14:04:04 [WARN] DeploymentManager - Failed to find the pdb database.
9/14/2012 14:04:04 [WARN] DeploymentManager - Failed to get the local payload database handle.
9/14/2012 14:04:04 [INFO] DeploymentManager - STEP 2: Starting to launch media Bootstrapper.
9/14/2012 14:04:04 [INFO] DeploymentManager - Bootstrapper launch location is :: D:\adobe\adobe_cs6\test\CS6\Build\Setup\Set-up.dat
9/14/2012 14:04:04 [INFO] Setup - Build Version - 6.0.335.0
9/14/2012 14:04:04 [INFO] Setup - Logging Level verbosity Set to 4
9/14/2012 14:04:04 [INFO] Setup - Start Adobe Setup
9/14/2012 14:04:04 [INFO] Setup - TimeLog: Bootstrapper Start
9/14/2012 14:04:04 [INFO] Setup - TimeLog: Start initial checks
9/14/2012 14:04:04 [INFO] Setup - Action specified - "install"
9/14/2012 14:04:04 [ERROR] Setup - Error parsing command line arguments at - "DISABLE_CCM_DESKTOPSHORTCUT".
Expected arguments are -
--mode=silent
--overrideFile="<FilePath>"
9/14/2012 14:04:04 [FATAL] Setup - Administrative Privileges required to continue
9/14/2012 14:04:04 [FATAL] Setup - End Adobe Setup. Exit code: -10

9/14/2012 14:04:04 [INFO] DeploymentManager - Build Version - 3.1.105.0
9/14/2012 14:04:04 [INFO] DeploymentManager - Logging Level verbosity Set to 4
9/14/2012 14:04:04 [FATAL] DeploymentManager - The return code from the Bootstrapper Process is (1).Stopping the installation process.
9/14/2012 14:04:04 [INFO] DeploymentManager - The install workflow is terminating.

Report · Sep 14, 2012

Hi,

Instead of double clicking the msi, please right click on the msi and select run as administrator. or else launch the command prompt with admin privileges, and run the follwing commond.

msiexec.exe /i <path of msi>

This will launch the msi in UI mode.

Thanks,

Saransh Katariya | Adobe Systems | skatariy@adobe.com

Report · Sep 17, 2012

Since I'm an admin on the machine, when I right-click on the msi, run as admin isn't one of the options. If I shift + right-click, I can choose run as a different user, but that doesn't seem like it would have an affect, since I'm already an admin.

If I run the msiexec command, the software installs fine. However, that takes away the goal (and stated functionality) of a "double-click" installer. To get around that, I created a batch file that has the msiexec in the command line. As expected, it's not enough to run the batch file as an admin, but you have to right-click the batch file and select "run as administrator." So, the goal of a "double-click" installer hasn't quite been achieved.

Thanks.

Report · Sep 14, 2012

Also, on the Mac, it takes me throught the normal prompts (though, oddly, it seems to want to install on the root of teh drive, rather than in the Applications folder). Once the progress bar starts, it makes it about 1/8 of the way through the process. At that point, the progress bar stops and the estimated time remaining just keeps getting longer, until I force quit. I didn't see anything useful in those logs.

Thanks,

Mark

Report · Sep 14, 2012

Hi,

For the mac OS, the progress bar is indefinate and does not reflect the true progress. Its a native progress bar of Mac which is shown by default. Installation will take some time and the time remaining shown on the UI is a false one.Splly when you are installing lot of products through one package, it takes time.. Please let it run for some time and do not force quit it. Regarding the options, again it is by default in Mac OS and cannot be suppressed. Just select the default options and things should work fine.

Thanks,

Saransh Katariya | Adobe Systems |skatariy@adobe.com

Report · Sep 17, 2012

I'm now also getting an error on the Mac-

"The installation failed. The installer encountered an error that caused the installation to fail."

Not very descriptive. I rebooted and tried again and got the same error.

Thanks.

Report · Sep 17, 2012

Hi,

Foe mac side, Can you please mail the PDApp.log file to skatariy@adobe.com. The log file is formed at /Users/Library/Logs. Logs will help us to find the root cause of the problem.

Thanks,

Saransh Katariya | Adobe Systems | skatariy@adobe.com

Report · Feb 14, 2013

Has there ever been a resolution to this? I'm having the same problem, with the same log file errors.

Report · Feb 14, 2013

John-

If you're referring to the Windows errors, we have to 'run as admin' for things to work properly. I finally resigned myself to that, unfortunately. That seems to be working okay for us, though. Good luck!

Report · Feb 14, 2013

"Run as admin" seems to work on some computers but not others. Is there something other than AAMEE for this situation? It worked great for our domain installation using SCE, but I need a way to install on computers outside our domain.

Report · Feb 14, 2013

I'm not aware of anything. At least for our environment, AAMEE was the best option, despite its flaws.

On Feb 14, 2013, at 1:40 PM, John V Sullivan <forums_noreply@adobe.com<mailto:forums_noreply@adobe.com

double-click in Windows?

Photos