I used Adobe Application Manager Enterprise Edition 2.0 to create .MSI file for "Adobe CS 5.5 Design Standard 1.2.0000" and "Adobe Acrobat X Pro 10.0.0" on x64 bit machine.
I used MSI created for Design Standart and Adobe Acrobat.
While creating package I inserted Serial Key.
Then installing Acrobat, then Design Standart. Everything looks ok.
Launch Photoshop or any another CS5.5 product - everything is OK - Serial key is applyed and works.
So, where problem comes?
Install Acrobat, then Design Standart.
Launch "Adobe Acrobat Distiller X" - it loads, after it has finished loading everything I close it.
Then launch for example Photoshop and it asks for serial.
Why? Do Distiller refresh/drop or somehow else looses Serial Key?
So, I have question - Do I have forgot to include something or is this deployment toolkit bug?
Thanks in advance!
Please, let me know if this is my fault and I can do something with this bug I experienced.
If there is needed more information - let me know.
Have a nice day!
You will want to follow the workflow in Scenario 1. When the Creative apps are launched, in Creative Suite 5.5, they will serialize Acrobat at that time. We tried having a separate serial number for Acrobat with Creative Suite 5 but this seemed to cause more confusion for customers.
Thanks for reply!
I were trying to import property like ISX_SERIALNUMBER with Design Standart serial key, but it just caused error on installation and after reading Your reply - I'm happy that it is ok to leave it like that.
At least now I will know what to answer to customer if that issue arrise.
Have a nice evening
hi, i have a problem with my Acrobat activation: i installed CS5.5. and every programm except Acrobat works fine, acrobat keeps asking for the serial, which it sometime accepts, sometimes not, but either way, it just pops open the same window again and again, wanting a serial.
what do i do to solve this???
thanks for any help!
PS: i already tried deleting the CS trial and installing the downloaded CS5.5. version, i deleted the cache.db once.... still the same problem.
I found the solution in another forum:i just switched the language of the operating system (aka my macbook) to the same as the language of the purchased CS, and suddenly it works, no problems. WEIRD, but good to know.