/build/static/layout/Breadcrumb_cap_w.png

Best Practice for Adobe Creative suite Deployment SCCM Win7


Hi All

I have access to Adobe Admin Console 
My task is to create at deployment for a "Design package" including  Adobe Creative Suite product

Design 1.0
Included apps:

Creative Cloud Desktop Application
Acrobat DC (18.0)
Bridge CC (8.1)
Dimension CC (1.1.1)
Illustrator CC (22.1)
InDesign CC (13.1)
Light room CC (1.4)
Media Encoder CC (12.1.2)
Photoshop CC (19.1.5)
Camera Raw CC (10.4)
STI_ColorCommonSet_RGB_HD (1.1)

They are all in MSI format and Adobe builds it as a bundled package you may install as setup—silent
but is this best practice to Use this install method. ?
My question is to you, what is best practice to deploy 

Is a better way to take product one by one in a Power shell deployment tool kit fashion
The reason I ask, my installation fails on windows 7 64 bit.

Regards
Sweede













2 Comments   [ + ] Show comments
  • I think you'd be better off packaging them individually. It makes it easier to customize for the people who need everything listed above, but also want Dreamweaver or one of the other Adobe products. The Adobe packager works fine, but from what I've seen it will install a lot of files that were already installed in your first package, making the new Dreamweaver package a lot larger than it really needs to be. - kalucas 5 years ago
  • Is the same installation process working on Windows 10 machines? - sarahmurray 5 years ago

Answers (1)

Posted by: nagendrasingh 5 years ago
Black Belt
0
We just give out the creative cloud application + Adobe Federated ID and don't package applications anymore. Our workplace has purchased licences for everyone.

In case your installer is not working as expected, open a case with adobe. It should be free.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ