Past few days now I've been trying to add the CS6 Master Collection suite to my OS deployment in my K2000 box with no success.
I've done the "backdoor" approach to it as the files are greater than 1-2gb, hence the webgui won't take them as a normal upload.
So, I did the PO-task, made a dummy zip with the same name as the installation msi & zip file I'd normally use but instead of having it filled with the installer I just added a txt file in order to create the PO.
Afterwards I exported it, copied it down to my machine from my KBOX\Restore - Opened it with 7zip, went into the Payloads folder and started doing stuff in there.

Note: I did package everything through the packaging tool from adobe, version 3. Meaning I got the build folder with the msi inside and div. folders such as ASU, Patches and Setup.
This package works if I deploy it through K1000 or simply run the msi through command line on the machine with msiexec /i setup.msi /qn 

Basically what I've tried:
Removing everything in the payload folder and just adding all the installation files and folders and closing the zip, re-upploading it, overwriting the current pkg file on the share, then removing the PO from my list inside the KBOX before importing the newly added PKG from restore. - Did not work, Installation of the OS goes through, the Java installation I added goes through and then it's done, no sign of it ever attempting to do anything with the CS6. (same with or without the added java in the PO list)

I tried doing the same as above but rather than adding the installation files in a unzipped format I thew them together into a zip file with 7Zip and just added the entire ZIP inside the payloads folder, did all the same importing, still nothing happens.

I tried keeping the dummy zip inside the payloads folder and unloading whatever the real installer contains into the "contents" folder, but still the same, no sign of anything happening with the CS6.

All of this above I tried last year with CS5 Production Premium suite, which it's only difference being, it's a few gig smaller. How I made that one work, I simply cleared the payloads folder, inserted all the setup files, the msi, the folders and imported it and huzzah, it worked. CS6 however doesn't want to.
As said, the only real difference is the fact that the CS6 package is almost 8 gig, is there any known size limit? 

Also while deploying I do not use my old Kcleanup tasks, yet no folder appears in %programdata% on the machine after installing the OS with other programs, meaning I've got no logs to check if something happened on the machine or perhaps why it skipped.

As of now I'm running Version 3.5.76460 on the K2000 and we haven't fiddled anything with bigger deployments since I updated the box, but the older CS5 deployments still work properly the way they're packaged.

Any ideas?

0 Comments   [ + ] Show Comments


Please log in to comment

Community Chosen Answer


For what it's worth when I did CS5 I used a net use and mapped a drive to where my install was on a share. I'm not sure if that's possible in your environment, or even something you would consider doing?

Answered 05/15/2013 by: dugullett
Red Belt

  • I agree with this, run it externally from the k2000. you do not fill the drive up with install that way. If you do not have drive space to place this on a share, mount the DVD on a server/workstation and run it with a post script install net use call from the DVD
  • I'll have to give that shot, what I'm wondering tho is, where does the machine keep the logs after deployment? Is there any way I could see which programs and why they successfully deployed or not? The folder in %programdata%\DELL\KACE usualy contained all the packages after the deployment was over unless I used the Kcleanup task to clear everything, this seems to be done automatically now?
    • Take a look at Smal's answer here. This might help.
      • Those logs only show me that the image has been applied and nothing about the PO tasks failing in the middle of it, as the image deployment is all successful, it's just that the Master Collection suite is missing in the end when I'm back inside windows on the machine with no trace of it ever being copied over to the machine or attempted to install.
      • I haven't updated to 3.5 yet, but this still should be doable. Can you add a pause, or exit post install batch script? This should stop the tasks so you can at least get in and verify the logs Kace creates.

        If it is the same path maybe you could add a copy post install, and copy it somewhere else on the local machine or a network share.
Please log in to comment



It is better to install it manually from a shared drive. Package it but install it manually not through Kace.

Answered 05/21/2013 by: piyushnasa
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity