Posts tagged "imaging"

AAMEE 3.1…or why puffer fish is a delicacy

Imagine the feel of fine chopsticks between your fingers. Imagine picking up a thinly sliced fugu sashimi and bringing it to your mouth.  You can hear the koto strings being plucked off in the distance. You breathe deeply as you place the fugu in your mouth. You have faith that the chef has properly removed the liver with his special fugu hiki knife. This will not kill you. This is safe. You have to believe in the mastery of the chef; that he knows his trade. And as you swallow, you know that the puffer fish has met its match.

Four months, almost to the day I posted the blog post “AAMEE 3.0 for CS6 available now! Removes puffer fishes!” in which I strangely used the puffer fish as a metaphor for the anti-piracy licensing and serialization that Adobe introduced with CS6. These new policies were really a pain for IT admins, especially in education that use old-school methods of monolithic imaging like Ghost or Deep Freeze. Get it, old-school?  I really didn’t realize how many classroom environments did not have any infrastructure in place to remotely push out files or run our new serialization executable. So Adobe, in traditional Adobe mode, made IT admins mad and then told them to use a work-around that didn’t work. So a no-work-around. A not-going-to-work-for-us-around. An Adobe-is-giving-us-the-run-around. You get what I am saying.

And for four months, four crucial months in which schools were preparing their labs and classrooms for fall, IT admins struggled and spent extra hours at night and the weekends just to get their installs of CS6 to work in a serialized state. And many of the folks had never used AAMEE, and were forced to use AAMEE and cursed having to learn another tool. And they cursed Adobe, and they cursed AAMEE, and they cursed me. And this was personally really disheartening. I come to work to each day to make sure IT admins don’t curse Adobe. And to beat Joe Chilcote in foosball. Which makes Joe, who is in our IT, curse at me. Irony?

The puffer fish/fugu metaphor turns out to be a really good one for this release. The final version of AAMEE 3.1 removes the machine-to-license relationship that I outlined in the “Imaging CS6-Attack of the Clones” blog post in June.

This means that any serialized package created by AAMEE 3.1 that is installed in a master image will still be serialized on a cloned system. Why? Because we have removed the toxic liver of the fugu/puffer fish. If you are just tuning in, we are using the puffer fish’s liver as a metaphor instead of the puffer fish. Let me recap this: use AAMEE 3.1 to create a package and the machine-to-license relationship that was introduced in CS6 has been negated, neutralized, and ostensibly: neutered. Therefore, the imaging workflow/workaround that I outlined in that imaging post is no longer relevant. There is no longer any need to create an unserialized trial package and jump through the hoops. You can now create a serialized package like you should have been able to do in the first place.

NOTE: The AAMEE 3.1 beta did not remove the machine-to-license relationship. Only, the final version of AAMEE 3.1. So, if you were someone who downloaded the beta of AAMEE 3.1 from Adobe Labs please upgrade to AAMEE 3.1 today.

Wait, so AAMEE 3.1 beta was not feature-complete? Nope. There are three main features of AAMEE 3.1 that were not outlined in the AAMEE 3.1 beta post which listed out ten new things in the beta. The three new ones not present in the beta:

1) Removal of the CS6 machine-to-license relationship to improve imaging

2) AAMEE 3.1 MSI now double-clickable with basic installation Windows UI

3) Running of AAMEE 3.1 uninstall package now removes Software ID tags (SWID)

That brings the number of changes from AAMEE 3.0 to AAMEE 3.1 up to 13. Thirteen significant changes that I am very proud of. I am very proud of the AAMEE crew for turning out such a major release (despite the dot release nomenclature) in just four months. I also have to thank Adobe’s Provisioning team who helped implement the removal of the machine-to-license relationship components and helped making sure the SWID tags were cleaned up properly. A lot of hard work went into this release. Dot releases are not supposed to be this hard, this epic, this important. But this one was. And at the end of the day I know this release is what we should of provided to the IT community in the first place. That wasn’t possible, and I apologize. It took Adobe four months to right some wrongs. Nobody is going to give us a medal for speedy response to the IT community. No one is going to shake our hands for building software that negates something that shouldn’t of been in place for our Enterprise customers in the first place. I know this. That doesn’t mean this fugu sashimi isn’t delicious.

Oh, and before I forget: must give a shout out to our AAMEE Quality Engineering folks who with this release certified two additional workflows: Symantec Ghost for imaging and LANDesk for deployment. Thanks to both for Symantec and LANDesk for helping out on this process. Providing more and more testing workflows is never a popular request and I am really glad to have the support of our QE team and their management to continually support so many OS configurations, language testing, deployment and now, imaging workflows. Working out the kinks and documenting known issues behind the scenes is pretty much a thankless job. Except I just thanked them.

As stated in our previous post, AAMEE 3.1 is live on our Licensing Web Site  (LWS) and in Technical resources section of Adobe CS IT site. You’ll find the 3.1 Read Me and updated Deployment Guide there as well.

http://www.adobe.com/products/creativesuite/it.html

Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

Who you gonna call? -Imaging CS6 with Ghost

Update for Sep 13, 2012: The workflow outlined in the Ghost video is no longer relevant when using the final AAMEE 3.1 release which removes the machine-to-licensing which was introduced with CS6. See the blog post AAMEE 3.1…or why puffer fish is a delicacy for more info.

____________________

That’s right, I’ve summoned up the ghost of Ray Parker Jr. for a quick post on imaging CS6 with Ghost. What? Wikipedia tells you he is not dead? Fair enough. No offense meant Mr. Parker. Or is that Mr. Parker Jr.? Truth is he had a recording career before and after the Ghostbusters soundtrack but that was his big breakout hit. You can’t undue a hit. And maybe this Adobe TV video will be a breakout that our Systems Engineer, Karl Gibson has been looking for. Yes, the “Client Imaging With Symantec’s Ghost Suite” video is that good. That is, if you have the need to image CS6 and you are using Ghost. If not, probably about into the fifth minute you will ask yourself: “Why the heck am I watching this?”

This is the third video Karl has made for us around CS6. It’s a trilogy. Let us know if you would like us to cover other topics or want Karl to make a prequel. Speaking of prequels, if you need additional guidance on imaging/cloning systems with a CS6 install on them then please check out the previous blog entry “Imaging CS6-Attack of the Clones.”

Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe Systems

Imaging CS6-Attack of the Clones

Update for Sep 13, 2012: The steps outlined in this post for imaging are no longer relevant when using the final AAMEE 3.1 release which removes the machine-to-licensing which was introduced with CS6. See the blog post AAMEE 3.1…or why puffer fish is a delicacy for more info.

____________________

Invoking any of the Star Wars Prequels is surely starting this blog entry off on the wrong foot. I can practically hear the booing. Come on, Star Wars II- Attack of the Clones had some good parts in it. The whole part on Coruscant with the assassin, Zam Wessell, trying to kill Padmé? And I love the whole part of the film when they are on Kamino where the Kaminoans are making the clones. Admittedly, the movie falls apart once they go to Geonosis.

But back to the clones! Not the clones based off of Jango Fett, but rather the process of cloning a computer for a lab, classroom, event, new system, etc. Also known as imaging and for better or worse ghosting. I honestly don’t know if Ghost (presently a Symantec  product) was named after the process or people have made the application’s name a verb. Whereas “I ghosted that Mac with Disk Utility” is a wrong as “I Shopped that dog’s head onto my cousin’s body.” Little known fact, Ghost is an acronym for General Hardware-Oriented System Transfer. Time to tally up your Nerd Points™ and declare victory if you already knew that acronym AND you knew that Zam Wessell was a Clawdite from Zolan.

In CS6 we introduced a licene-to-machine relationship that breaks many traditional imagining methods whereas a master image is serialized and then cloned. Now the booing is a little more warranted. In fact, imagine the first line of this paragraph read by Jar-Jar Binks to really make your blood boil. Obviously you will want to add “Meesa thinks” at the front. And expect this decision to create this licene-to-machine relationship will be as popular as Jar-Jar. It was actually more of a bi-product of our activation changes and not really a planned assault on IT admins who have to imagine systems. But whatever Adobe Man, the damage is done! Well true, but we do have a workaround of sorts. Is this workaround lame? On a scale from 1-10 with 10 being the worst workaround ever, I’d give it a 6. Maybe a 5 if you are not familiar with AAMEE. Maybe a 4 if you ran into trouble with imaging CS6 on your own and Googled “Adobe broke imaging in CS6″ (but with some curse words sprinkled in the search words) and then you had to read through 3 paragraphs before I got onto the workaround steps.

Actually, before I give you workaround steps, for those who want a walkthrough of the process our Systems Engineer, Karl Gibson, has created a video on Adobe TV called “Client Imaging for CS6” which is quite helpful.

Steps for Client Imaging for CS6

1) Use AAMEE 3.0 to create an unserialized CS6 Trial Package

2) Use AAMEE 3.0 to create a Serialization file [Yes, you’ll need to be online and use an Adobe ID for your organization]

3) Install/deploy the AAMEE produced CS6 Trial Package to the master image

4) The installed CS6 software will be in Trial Mode but you could make any changes you wanted including defining preferences [Don’t serialize]

5) Take the master image and clone the image to the systems using your normal method

6) Copy the AAMEE 3.0 produced Serialization files (the executable and the prov.xml file) to the newly cloned systems [Manually, through a deployment method, first run script, etc.]

7) Execute the following command:

AdobeSerialization – -tool=VolumeSerialize – -provfile=Absolute_Path_of_prov.xml

Obviously you would want to verify that the CS6 software is serialized and opens fine without giving notice of the software being in trial mode. So that is theoretically Step 8 except depending on the scale of your imaging you may not want to do that on all the systems once you are comfortable the process is working. And you might also, depending on where you placed the files, remove them. So that could be theoretically Step 9, but obviously I was keen on having just 7 steps.

If you have issues with any of these steps, please use the Enterprise Deployment Forum to let us know. I realize that having to go through these extra steps are a pain but hopefully the Force will be with you. Seemed appropriate, right?

Jody Rodgers | Sr. Product Manager | Enterprise + Volume | Digital Media | Adobe

Note: The bulk of this post makes reference to Star Wars which is clearly TM & © 2012 Lucasfilm Ltd. and if Lucasfilm, LucasArts, or Skywalker Sound have ANY issues with imaging CS6 I will personally volunteer to head over there and help you out. After I get my photo taken with Yoda.

 

UPDATE: We have a new Adobe TV video that will walk you through the imaging steps if you are using Ghost: Client Imaging With Symantec’s Ghost Suite