Posted on 01-17-2013 10:08 AM
Hello All,
I am testing the install of CS6 with policys. I created two packages to test. 1. CS6 Web prem with the updates installed created with AAMME 3.1 and 2. CS6 Web prem with no updates with AAMME 3.1.
The policys I have in place are: 1st policy to cache, 2nd policy to uninstall cs5 and restart, & 3rd a policy to install from cache
With I push the first PKG (with updates) with the above method I get two policy logs for the computer:
1st stating it was successfully installed
2nd The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
From there I check the console logs and I see errors for indd error code dw023
For the 2nd pkg (no updates) with the above policys method again two policy logs:
1st stating it was successfully installed
2nd The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
I check console no install errors to be found.
Anyone come across this? Any help would be very helpful, Thanks
Solved! Go to Solution.
Posted on 02-04-2013 12:58 PM
I figured out the issue. I was kicking off the policy with "any" while it was running every15 ran in the back ground and failed.
Posted on 01-18-2013 11:22 PM
Possibly there may be a problem with the uninstall of cs5 in your workflow.
What happens on a dev box if you don't uninstall cs5 and first just try a cache cs6 and then install it.
Posted on 01-18-2013 11:32 PM
This is something I going to need to do at some point.
I downloaded the Adobe Creative Suite Cleaner Tool and have that in Self Service.
It is possible to run it in silent mode but I think you may need to faff about creating an xml file. Best to look at the Read Me after you download it.
http://www.adobe.com/support/contact/cscleanertool.html
Posted on 01-28-2013 06:44 AM
thanks I will take a look today
Posted on 02-04-2013 12:58 PM
I figured out the issue. I was kicking off the policy with "any" while it was running every15 ran in the back ground and failed.