Trying to deploy an Adobe CC package to Mac, deploying to wrong directory.
Hi,
I am deploying the full Adobe CC package to MAC OS X. I have uploaded the 21GB file to the K1000 clientdrop folder. When it goes to download the folder onto the Mac, it is going into a folder labeled 15662, but when I look in the K1000 adminui, the package is associated with a folder named 16992 or something similar. I am writing this from offsite, so I cannot verify that name right now. When I go in through adminui the associated package for 15662 is a Google Chrome package. So, as of right now, it downloads the file, all 21.07 GBs to 15662, which via the k1000 is Chrome and does not deploy. My theory is it doesn't carry out the deployment because it does not see the right folder. Any ideas on this one? Also, is there a way to see what's in the clientdrop folder? As of now, whenever we put something in there and the K1000 recognizes it, it becomes invisible? Is that the way it is supposed to work or was our server set up incorrectly?
Thanks for any ideas or help on this one.
I am deploying the full Adobe CC package to MAC OS X. I have uploaded the 21GB file to the K1000 clientdrop folder. When it goes to download the folder onto the Mac, it is going into a folder labeled 15662, but when I look in the K1000 adminui, the package is associated with a folder named 16992 or something similar. I am writing this from offsite, so I cannot verify that name right now. When I go in through adminui the associated package for 15662 is a Google Chrome package. So, as of right now, it downloads the file, all 21.07 GBs to 15662, which via the k1000 is Chrome and does not deploy. My theory is it doesn't carry out the deployment because it does not see the right folder. Any ideas on this one? Also, is there a way to see what's in the clientdrop folder? As of now, whenever we put something in there and the K1000 recognizes it, it becomes invisible? Is that the way it is supposed to work or was our server set up incorrectly?
Thanks for any ideas or help on this one.
0 Comments
[ + ] Show comments
Answers (4)
Answer Summary:
Please log in to answer
Posted by:
chucksteel
7 years ago
Top Answer
The folder that is created should match the software ID, not the managed install ID. Are you looking at the software ID for both the Creative Cloud software title and Google Chrome?
Also, are you uploading the PKG or a DMG containing the PKG? I have had the best luck with putting the PKG inside of a DMG (making sure it is the only thing on the DMG) and uploading that. When the appliance sees a DMG it will mount it and then run any PKG files inside of it. This has been the most reliable method for me.
Posted by:
tjw61
7 years ago
Thanks for answering. I am not sure which one I am looking at, sorry. Can you explain how I would look at each one so I can verify? I am also deploying it as a PKG, not DMG. Sorry, not really a MAC guy, just trying to recreate wht the former Mac guy did to get the package running.
Comments:
-
Login to the admin interface using the /adminui url. Open the managed install for the Creative Cloud distribution.
The ID for the managed install will be in the URL (we don't really care about this one at the moment).
Scroll down to the Installation Command section and click on the link for the Software Details.
This will take you to the software title for the associated item in the software inventory. The ID for the software title will be in the URL.
This is the number that will be used to create the folder in the download location.
To create a DMG containing your package you can use disk utility or the hdiutil command in Terminal.
Also, the generally accepted best practice for Adobe CC products is to create individual packages and not one that includes all of the applications. - chucksteel 7 years ago
Posted by:
tjw61
7 years ago
At least I was doing that right. The ID on Kace is 16990, the ID on the folder on the computer where the download is 15662. Any ideas how this happens? Is there a way to see the files in the clientdrop folder? I was thinking of going to individual installs and will try that next. Thanks for your help, will let you know how I make out.
Comments:
-
I believe that once you associate a file with a managed install it is moved to another location and is no longer associated.
Is the managed install associated with a software title? - chucksteel 7 years ago-
It is. - tjw61 7 years ago
Posted by:
tjw61
7 years ago
Thanks for your help, I spent many hours on the phone with Quest, but we got it going. They helped me create a command line, which surprisingly needed to have a local admin password in it to work. But it is now working. Thanks again for your help.