Skip to main content
C
clay_at_cox
Participating Frequently
June 7, 2012
Question

Unable to customize the installation location of Acrobat through Creative Cloud

  • June 7, 2012
  • 1 reply
  • 10504 views

It would appear after speaking with Adobe tech support and escalation team that AAM can't install acrobat to any drive other than C: (hard coded).  THIS level of incompotence is amazing.  I'm asking for a refund, if they are this incompentent on the install, imagine how bad the actuall code is.

    This topic has been closed for replies.

    1 reply

    Jeffrey_A_Wright
    Jeffrey_A_Wright
    Legend
    June 7, 2012

    Branced this to a new discussion thread.  Clay at cox the majority of the Acrobat components are required to be installed on the volume containing your operating system.  This is due to the level of system integration employed by Acrobat.  You should still be able to install Acrobat executeable to a custom location though.

    Did you try modifying the installation location under preferences in the Adobe Application Manager?  Do you receive an error message when attempting to install Acrobat?  What version of Windows are you using?

    C
    clay_at_coxAuthor
    Participating Frequently
    June 7, 2012

    Jeff;

    Your answer is condesending and wrong.  The CS6 stand-alone product and the trial product both install and run correctly from my D: drive.  Basically what you are telling me is that this product can't be installed on any kind of SSD/HDD combo or any kind of remote (Citrix/Xen, VMWare desktop, etc) desktop.  Which of course would mean your whole staff is UTTERLY INCOMPETENT, instead of the one or two people in charge of the AAM msi.  Serriously, who tested and signed off on this?

    Other than Windows AS, Microsoft has supported installing software to alternate drives since it's creation.  Whoever told you that there is "Product Integrations" is likely the lazy/incompent programer that failed to complete the code in AAM.  The only files required on the OS drive are files that have to be in the "system32" drive tree.   (If you don't know what these are, then go look it up, because I do).

    I spent 3 hours on the chat/phone with your tech support.  We tried re-installing (because it somehow would not register with adobe, tried changing the directory in preferences to "D:\program files" vs "D:\program files (x86)", tried moving the files and changing the registry (I had to do it, they are not quite savy enought to search and replace a drive letter in the registry).  

    My system specs are pretty standard.  Win7/64  60GB SSD for OS, 500GB hhd for profiles and software.  All settings are set correcttly for the programs to install by default in drive D:  (the windows registry and the profiles are all on D:)

    Please be aware, I'm spending 3 more hours posting this everywhere.

    Mylenium
    Mylenium
    Legend
    June 8, 2012

    Adobe products always have installed shared components on the root drive in the Program Files branch no matter where you choose to install the main programs. Even a standalone install does that. It's the only way to make sure that some components are loaded properly. Installing on another drive always carries the risk of accidentally moving or renaming stuff. as to the specific matter at hand I'm not sure what advise to give you looks like some oversight/ bug in the AAM installer, but I would assume that even on a 60 GB drive you could possibly spare those 700 MB and just leave it at that. Also you could still try to run the standalone installer. All AAM does is serve the license and hide the actual install process from your eyes with a quiet install, but the installers themselves are the same, so it doesn't realyl matter how a software got on your system...

    Mylenium

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices