Quantcast
Channel: Adobe Community : Discussion List - Deployment for Creative Cloud for Team, Enterprise, & CS
Viewing all articles
Browse latest Browse all 5337

serializing CS 6 (Mac) for deployment via an image

$
0
0

I'd like to install and serialize CS 6 D&W Premium (Mac) on a master system, then image the hard

drive and deploy the image to a number of other Macs. Item 5. page 136 of the AAMEE Deployment

Guide for AAMEE v3.1 says

 

  1. Suppose you want to deploy a Windows 7 image containing Adobe Creative Suite Master Collection software. Follow these broad steps:
    •   Deploy the trial package of Creative Suite Master Collection on a Windows 7 installation.

    •   Generate the prov.xml file using the following command:

      adobe_prtk --tool=VolumeSerialize --generate --serial=<serialnum> --leid=MasterCollection-CS6-Win-GM --regsuppress=ss --eulasuppress

Serialize and activate the package by running the following command:

adobe_prtk --tool=VolumeSerialize --stream

Using standard imaging tools such as Ghost, the enterprise admin can now create an ISO image of the Windows 7 operating system containing

fully-provisioned Adobe Creative Suite Master Collection software. This ISO image can be restored on multiple secondary systems across the

enterprise. No additional provisioning is required on these secondary systems.

 

I'd rather not install AAMEE, or the like, on the master system. If I generate a trial package of CS 6

D&W Premium and a separate, executable serialization file using my workstation, then install the

trial package on the master system and serialize that installation with the serialization file, will the

serialization of CS 6 remain intact when an image from the master system is restored to another Mac?

How about if CS 6 was installed on the master system using a package that is serialized at the time

the package is generated?


Viewing all articles
Browse latest Browse all 5337

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>