If you create disk images and duplicate to the PC’s, the ideal way for you should be –ġ. I recently put a post on one of the adobe blogs: Third and final, if you are imaging then AAMEE 3.0 has a special unserialized/trial workflow and a new serialization executable that can be used to serialize once the image has been applied to the machine. The end user’s system does not have to activate because you have already done it using AAMEE. Second, the serial number is validated and activated within AAMEE 3.0. Okay, so how well does AAMEE 3.0 reduce the pain of this puffer fish? First, using AAMEE 3.0 makes it so you only have to create/login with one Adobe ID on behalf of your organization therefore negating the need for your end users to have an Adobe ID at all or even know what one is. No place within Composer to validate the Adobe ID or the online serial number validation. Let’s say you used a third party packaging tool like the venerable JAMF Composer tool. There is now a relationship between the machine and the licensing in CS6. Login in with an Adobe ID and serialize it. Now maybe you do imaging for your organization. Once again, not connected to the internet or behind an overly secure firewall? Won’t work. Also, the systems HAVE to activate on a regular basis. Wait, the systems aren’t online or behind a secure firewall? Won’t work. Your end users HAVE to login with an Adobe ID account or they can’t use the software. If you do a manual install of CS6 on a system the following will happen: An Adobe ID request will come up.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |