Was anyone sucessfull into virtualizing Adobe Creative Suite 6.0?
I tried but, while the applications do run, they show up as trial on machines that are not the one it was installed.
I don't remember. What is the correct way to capture it? Should I launch any component before post scan?
By the way, one strange thing was that the thinapp trial had something like 33509 days until expiration. Is ThinApp messing with any of the licensing components?
Maybe the key provided is hardware dependant, making it only valid for the machine where the software was installed.
If it's working in the machine where you captured it, even after uninstalling the application and removing all traces from it (license information from the registry) then it's probably the case I describe.
The key is a regular volume licensing one, so nothing is HW dependant. I can physically deploy it multiple times without a problem.
My capture machine is disconnected from the network, so nothing like online activation will take place.
It starts as trial with a excessivelly large trial time.
I'm working on this myself. I suspect that something special will need done with AAMEE. See this post from Adobe for about all of the useful info on the subject that exists at the moment.
I've already tried creating an installation package and capturing that, but I see the same behavior as you. Next step is to try to create a Serialization File and see if that works. I'll report back with the results if I get anything useful working.
My thoughts are
1) Create trial package with AAMEE
2) Create Serialization exe with AAMEE
3) Capture trial package installation
4) Include the Serialization exe and xml files in the Thinapp package and cook up a vb script to run the serialization exe when the thinapp launches. (I presume that this will be the tricky part)
After some playing around, the process looks like it should work. I was hoping that I might be able to build the trial thinapp and then use sbmerge, but there's something unique in the registration information. Looks like CS6 needs to be registered individually on every PC. So far, I'm only trying to build Photoshop CS6, but I would assume that the rest of the suite will behave the same.
Here's what I've got so far, maybe someone can chime in and help finish this up.
1) Build a "Trial Install" package with AAMEE
2) Build a "Serialization" package with AAMEE
4) Install the trial package
5) DO NOT LAUNCH PHOTOSHOP
(It looks like it runs some optimizations for the specific hardware that it's living on when launched, if you launch it before the postscan the thinapp will take MUCH longer to execute after it's built.)
7) After building the package, put your AdobeSerialization.exe and prov.xml somewhere convenient. I stuck it in a subfolder of the thinapp directory.
😎 Create a batch file that executes adobeserialization.exe. I called mine "register.bat" and it contains the following: "%~dp0Serialization\AdobeSerialization.exe" --tool=VolumeSerialize --provfile="%~dp0Serialization\prov.xml"
9) Cook this script into your thinapp to launch the .bat file when the thinapp launches:
Building something into the vbscript to check to see if adobeserialization.exe has been called yet to register the app would speed up the speed of things a touch, but I'm still looking into that bit.
The above *almost* works. I'm having trouble with dynamiclinkmanager.exe spawning multiple copies of itself when the thinapp is launched.
If I set ChildProcessEnvironmentDefault=Virtual in package.ini, it works fine but Adobeserialization.exe does not work properly when called by the vb script.
Is there a working solution to this yet? I am packaging CS6 Design Premium.
I had a lovely working package without licensing messages just from doing an initial capture of a licensed install, but of course the users were able to update their installs.
Now I'm using the AAMEE tool and following the full guidance here I now have a package that can't be updated, but it's not applying the licensed exe and so I'm getting 00 days remaining. Is there a fix for this. Nice try by the way...I thought applying the serialized exe on to the trial version would do it, but clearly not.
I was able to get it working a while back with the process mentioned above but it doesn't run all that well once it's together anyhow so I ended up going with thick installs, unfortunately.
I read in an Adobe post a little while ago AAMEE has been updated to "allow the use of disk imaging software like Symantec Ghost" and Thinapp has been updated as well, so I may give it another whack. I actually found this thread in the first few Google Results searching for "Photoshop CS6 Thinapp" which means that either we're both going about this all wrong or nobody has figured it out yet.
I'm about to start down this road as well and was wondering if people found a way to thinapp CS 6 usimg AAME 3.x
Has anyone tried the Adobe Provisioning Toolkit enterprise ed to serialize via command line instead of using the serialisation exe created with AAME?
Serialization Example 6 on the 2nd last pg of the guide above migh be useful in that is a way to deploy an Win 7 image that includes CS 6
Update: From further reading AAME 3.1 and CS6.1 would appear to have removed the machine to license relationship which might mean its possible to just create a serialsed .msi using AAME but will have to test it
I want to share my experience:
I captured CS6 on WinXP SP3.
I have started all apps before postscan and I have updated all CS6 Apps.
Then I started postscan.
All is running fine even on Windows 8.1 🙂
one more hint: starting Adobe Photoshop as admin does accellerate the starting of the app extremely. But this must be done only one time.