ZeroHour (3rd June 2010)
Well I have been waiting for this for a week or so now but looks like its here!
I had Major problems with CS4 and turns out it was because I didn't use the deployment kit (never knew about it)
So hopefully this will make the problems go away!
I have been following the run up on this blog by Eric Wilde
Anyway the link to the toolkit is HERE
I'm just going to have a play with it now so will let you know if I hit any problems etc.
ZeroHour (3rd June 2010)
Thanks for this, I had tried to get into the beta but it was full.
They are apparently calling the Mac version a 'Preview' at the moment as it won't install via ARD if the machines are not logged in, allegedly this will be fixed with a new version by the end of June...
Seems ok so far, just managed to make a package up for the Mac's so will try and push it out later this afternoon.
Any luck with this? need to deploy CS5 master collection. Anybody got any tips for deploying?
Last edited by chandan; 14th June 2010 at 12:22 PM.
ZeroHour (14th June 2010)
I'm using the AAMEE and have created a package, but attempting to deploy it fails. Checking the logs I see
"Unable to locate folder for token UserDocuments"
"Exit Code: 7 - Unable to complete Silent workflow"
I can't find anything on Adoe's website - anyone have any ideas?
Sorry! Windows - a CC4 network, but the msi I've created doesn't install on a vanilla machine either.
we used a .bat to install, just making sure it was run /quiet
worked here anyway. the only problem is you need to keep an eye out for when it finishes... or just leave it overnight.
By looking on the error you got, it seems that token "UserDocuments" is not present on the end-users' machine, that is, environment variable of UserDocuments is missing on client machine.
You might be encountering this error because you would have selected "Deploy To" option under "Installation Location". And in the text box next to "Deploy To", you might have mentioned "%UserDocuments%". Could you please confirm that you specified somehting similar to that?
If this is the case then you should opt for a token which is available on all the machines where you are deploying the MSI package. Or, alternatively you could select default location.
I'm afraid I did select the default location
Could you please share following logs with me at "csingh at adobe dot com" (please convert it into an email-id format) ?
1. %temp%/PDApp.log of the machine where you created the MSI
2. %temp%/PDApp.log of the machine where you are installing the MSI package
3. Please also share installer log created on the end-users machine at %commonprogramfiles%\Adobe\Installers\<install-product>.log
Also, please answer whether you are:
1. deploying MSI on end-users' machine using SCCM server?
2. Which product you are packaging?
3. What is the Windows flavor on which you are trying to install?
This information will help us in narrowing down the issue.
Thank you - I'll harvest the log files now. To answer your other questions:
I am currently testing the msi by running the command "msiexec /i <<path to package>> /quiet" at the command line, however I intend to distribute the package using the RM CC4 tools, which deploy msi's in a similar manner to SCCM.
I'm packaging Photoshop at the moment, but intend to package the other applications once successful with this one.
Windows XP SP3
There are currently 1 users browsing this thread. (0 members and 1 guests)