Nice, will be my next package to deploy. Do you have a guide for best practice? To deploy CS6? -
tecrumors
11 years ago
No best practice needed... The AAMEE is very easy to use and for deployment when it comes to the CS suites, i normally publish it to my clients as "available" and not as "manditory" because some of these suites are very large and can bog down the clients machine when installing. By making it "available", the client can choose when to install it. We are using SCCM 2012 as our deployment method. -
KevinViolette
11 years ago
This was a big help. But I found a slightly different method for my situation. I have 30 XenApp 6.0 vm's deployed with PVS. The latest AdobeSerialization.exe has a switch '--stream'. Use the /? switch for info. Here is what I did and now I do not need to run a script or batch at startup or login. My XA reboot every night and next day users can access CS6 without warnings or nag screens. Hope this helps some one. Here is what I did.....
-put PVS image in Private mode
-uninstall any earlier CS6 bits
-use AAMEE (on another machine) to build a Trial version of your needed CS6 components
-use AAMEE to build a serial xml file (will also give you the exe needed)
-install the Trial to your Private mode PVS image
-copy the exe and xml to the image
-run the exe command listed in the blog, but add --stream
-complete your usual process to make the PVS in Std Image mode
-deploy the new image.
This worked great for me and pretty simple.
Holla back if it helped you ! :) @sboggs - twitter -
sboggs
9 years ago
This was a big help. But I found a slightly different method for my situation. I have 30 XenApp 6.0 vm's deployed with PVS. The latest AdobeSerialization.exe has a switch '--stream'. Use the /? switch for info. Here is what I did and now i do not need to run a script or batch at startup or login. My XA reboot every night and next day users can access CS6 without warnings or nag screens. Hope this helps some one. Here is what I did.....
-uninstall any earlier CS6 bits
-use AAMEE 3.1 (on another machine) to build a Trial version of your needed CS6 components
-use AAMEE to build a serial xml file (will also give you the exe needed)
-install the Trial to your Private mode PVS image
-copy the exe and xml to the image
-run the exe command listed in the blog, but add --stream
-complete your usual process to make the PVS in Std Image mode
-deploy the new image.
This worked great for me and pretty simple.
Holla back if it helped you ! :) @sboggs – twitter -
sboggs
9 years ago
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
-put PVS image in Private mode
-uninstall any earlier CS6 bits
-use AAMEE (on another machine) to build a Trial version of your needed CS6 components
-use AAMEE to build a serial xml file (will also give you the exe needed)
-install the Trial to your Private mode PVS image
-copy the exe and xml to the image
-run the exe command listed in the blog, but add --stream
-complete your usual process to make the PVS in Std Image mode
-deploy the new image.
This worked great for me and pretty simple.
Holla back if it helped you ! :) @sboggs - twitter - sboggs 9 years ago
-uninstall any earlier CS6 bits
-use AAMEE 3.1 (on another machine) to build a Trial version of your needed CS6 components
-use AAMEE to build a serial xml file (will also give you the exe needed)
-install the Trial to your Private mode PVS image
-copy the exe and xml to the image
-run the exe command listed in the blog, but add --stream
-complete your usual process to make the PVS in Std Image mode
-deploy the new image.
This worked great for me and pretty simple.
Holla back if it helped you ! :) @sboggs – twitter - sboggs 9 years ago