Packaging Large, Larger, the Largest Applications!
I have a challenge.
Your company decided to use Adobe CS3 for five of their graphic designers. You have to install the suite on all 5 PCs, and all the installations have to be identical.
To add complexity to the challenge, you have to get the suite on the Terminal server for one of the co/workers that needs to access it via Terminal Services.
You know you have a few ways to face the challenge. You (naturally) start with Wise Package Studio.
First Attempt
It's at this point that you run into disapointment number one. Wise cannot handle packages larger than 2.4 GB.
The package is almost 4 GB for the fullinstall.
Second attempt is to do it in, let's say, Softgrid!.
Yes I know, this is like a curse, but okay.
Let's get it done.
Second Attempt
Disappointment 2 comes up.
It's not working?
Why?
Softgrid cannot handle packages over 3.8 GB, and during install the buffers get full and the packaging stops.
Third Attempt
Is there a third way?
Yes there is. It involves SVS and will not be a disappointment because it just does the job for you.
Let's prepare for this.
Installing on Windows 2003 will not work, because Adobe does not support it. Later I will tell you more about it.
I'm a very big fan of packaging VSAs on Windows 2003, but for this particular setup I have to use Windows XP. Please, never use Vista for this.
I start the capturing, and then capturing stops just before the real setup starts.
Let's face it. We have to throw all tips overboard and do it like we never should do.
Start a global capturing. Did I really mention that?
Yes, I have to.
Start a new layer and select global capturing.
Start the setup.
Select all the software you want.
The setup will start, and the next 40 minutes your machine is occupied. Don't even think of doing anything else, because it will show up in the layer making it necessary to clean it out completely.
After setup is finished, leave the capturing on, and start one of the apps.
Fill out the licensing, but do not -- and I really mean do not -- register it on the Adobe website.
Stop the capturing, and export your layer.
Then activate the layer and see if everything starts up.
If yes, then the biggest, largest step is done.
Now we have to take the second step.
Deactivate the VSA, and edit the layer.
Remove the following settings:
Everything that has anything to do with the Internet Explorer. It will be in the package, and you need to get rid of it.
Second, find everything that has anything to do with your virus scanner.
I stopped mine before doing this.
Prevents you from a lot of search work.
Now test the layer. Just start all the apps, and see if they function.
If yes, go to the next step.
If not, delete the VSA, and take the exported one, and start again.
Next step in the task is to export the clean layer, and import it on another machine. Activate and test again.
Then you are ready to roll it out like you always roll out your VSA packages.
I use Altiris Deployment Solution for this but you can also use AD or what ever you normally use.
The PCs are done, but you still need it on the Terminal server.
On the terminal server you can use dvs4sbc to get SVS terminal server ready, and you import it.
And even that Adobe states this will not work, you will get surprised, because it just works.
Very well.
Wise and SoftGrid can't do it.
SVS can. What is the trick?
No, there is no trick. SVS just does not have a limitation in the size of the VSA. It has no limitation in the files in the layer.
It has no limitation in the size of the registry.
It will do the job for you.
Your boss will be happy, and you will be too. It only took me two hours to create the package, and two more hours to install on five clients and on a Terminal Server.
Thanks to SVS.
- Login or register to post comments
- 4315 reads
- Printer-friendly version
















A very well documented
A very well documented article.
Thanks Erik for this self-explanatory steps :)
Cheers'
Vijay
Here's an internal trick we
Here's an internal trick we use on the SVS team to get around global capture, which you should never use because you never know what windows is doing when you are capturing, and that's do a single capture on Command EXE and then what ever you launch via the command line will be captured--and it won't close, and end the capture, until you exit cmd.exe.
You can also do this by creating an empty layer, or one you already have, and then updating it and execing cmd.exe via SVScmd.
I should probably write this up as a tech tip
You're right
Jordan, you are completely right. This is the best way to prevent windows from damaging you're package with all the ... in it.
Thanxss for pointing me again on this. A techtip of this should remind us again.
Ps are you going to Malta?
Regards
Erik
www.svs4u.nl
Tempting..
HI Erik...
Your posts on SVS really drives me to have hands on SVS. So far, I have been only with Wise package studio and few deployment tools.
It would be great if you could give me an overview to SVS and its features...because it's just too tempting.. :) :)
Cheers'
Viju
I submitted one but since
I submitted one but since this has been posted on the Juice before so they didn't approve of it, though it's buried so far in the site most people don't remember.
Juicemaster should cycle through tech tips (reposts somehow) to remind people because there are some good things mentioned in them but unless you're using them you forget rather fast.
And no, sadly, I'm not going to Malta--I didn't even get to go to Orlando. In fact most of the SVS team doesn't go to ManageFusion, we're just too busy.
Jordan, I remember very
Jordan, I remember very well your "Saving Time, Money (and Your Sanity) with SVS" post ...
Also why not mention "VAMPP: Virtual Apache, MySQL, PHP, Perl ... and More" a perfect web environment to download and work in few minutes!
Size Limitation
Yes it is true there is no Size Limitation I bumped into a problem with VSA's when I Tried to "Layer" Rational Applciation Developer from IBM the Folder Structure EXCEEDED the 255 character length in folder structure and it was a NO GO. Thats the only Limitation I have found so far...
Thanks
Tom Fronza
State of Ohio
Dept. of Taxation
255 character limitation?
Scott, Randy or anyone else,
Is this indeed a limitation in SVS?
Regards
Erik
www.svs4u.nl
Yes, that is correct.
Yes, that is correct.
There's no size limit on the actual file size of a VSA but there is on on the names.
Size Limitation?
That's interesting to hear because every time I try to import a VSA greater than 2Gig I get an Error 28 during the import process. From reading the forums, it appears that is a generic Zip error. Standard Zip does have a limitation of 2Gig, but there are ways programatically of getting around that.
As I'm new to SVS, I very well could be doing something wrong. Has anyone else noticed a problem importing a VSA greater than 2Gig using v2.1?
I did not see this before,
I did not see this before, and i have a couple of VSA's that are larger then 2GIG?
Regards
Erik
www.svs4u.nl
Re: Size Limitation?
We updated to the latest DynaZIP libraries (for large archive support) during the original betas, well before SVS officially released in March, 2006. So unless you are using one of the 2005-era betas, there is no limitation on archive size. Please post your issue to the support forum and see if you can get some help (or open an incident w/Symantec tech support).
Scott Jones
Product Manager
Altiris, Inc.
Now Part of Symantec
Hmmm
I'm really glad to hear this. For me it seems very consistent accross any package I make. It seems like it exports just fine, but when I move the VSA to a different machine and import the error happens.
I'll have to do more research on it. Thanks everyone.
Any trial on SAP in SVS?
Hi Erikw,
Even thought I don’t know anything on SAP, I hear from my friends in IT keeps telling me that, installing SAP is the biggest night mare as it takes almost 16 hours to install and configure it properly and it needs at least 80GB of hard disk space. By any chance has any one come across installing SAP in a VSA? I’m just curious to know about it.
Thanks & Best Regards,
Swami.
Installing SAP
SWAMI,
Installing SAP is a real nightmare, and no do not try this in a VSA.
SAP is divided in modules. The module you are talking about is the server component.
It is like Exchange or SQL not a good idea to do this in a VSA.
The client on the other side is a good way to implement by using SVS.
Regards
Erik
www.deltaisis.nl
Adobe Creative Suite 3 - Patches
Thanks for the information here.
I've got a couple of problems that I cannot solve virtualising Adobe Creative Suite 3 - Design Premium. First of all I've only been successful using a Single Program Capture as when I use the Global Capture I've found that it takes about 10 minutes to activate the layer (as compared to about 30-40 seconds using the Single Program Capture) and because when I use the Global Capture and export/import to new machine I get messages regarding new hardware devices being found (which disappear once I activate the layer which takes about 10 minutes).
When using the Single Program Capture I've run cmd.exe and launched everything I need to from within the command prompt. All good. I can run up all the apps, configure preferences, etc and it runs beautifully. The problem I am having is installing the myriad of patches that CS3 requires (approximately 16). Now I've tried running the Adobe Updater application but it bombs out on about 4 of the patches. So I've stripped out the 16 odd patches and am still having trouble with the following ...
BridgeStartMeeting101.exe
ColorCommon190.exe
Illustrator13_0_1_en_US.exe
VC_Server310.exe
I've also had trouble with the two msp's ...
AcrobatUpd810_efgj_incr.msp
AcrobatUpd811_all_incr.msp
... in that when the layer is activated after being patched with the above two and imported to another workstation it complains about being unable to see the msp sources.
Has anyone successfully patched CS3 using Single Program Capture? Can anyone offer any advice? I've been working on this for a couple of weeks and I'm pretty close to getting it all working.
Many thanks for your help in advance.
Cheers
Craig
few comments 1) the reason
few comments
1) the reason you're getting the long activation time and device drives with a global is when you run a global capture you get everything windows is doing at the time so you're picking up all that extra crap that you don't want. This is why I recommend the cmd.exe capture trick since it doesn't do that and can be used about 90% of the time that global captures could.
2) What OS are you on? I've got Flash CS3 in a layer and I can only get a few of the updates to install via the adobe updater and I on Vista. I've seen less issues with this on XP via some tests I've done which make me think there are file transactions going on with the vista installs (I don't have a tool for checking this yet though) which would explain the updates erroring out.
There are many Adobe products who's updates don't work with SVS (there's several acrobat reader patches that won't install either) I'm fairly sure the cause of the known update failures are the same as the CS3 ones you're experiencing.
The only idea I can offer, and I haven't tried this, is to set the adobe layer you need updated back into capture mode (via update layer in SVSadmin) by capturing the command prompt then running the patches manually via command line. Doing this will move those changes (and any thing in the write layer) into the read only layer and could cause problems if there's a failure so I recomend exporting your layer as a backup before trying this.
Patching Creative Suite 3
Thanks for your reply Jordan.
The operating system is Windows XP SP2.
I have basically done what you've advised above. I used a Single Program Capture to install Creative Suite 3 from cmd.exe. At the end of that I did some tidying up (shortcuts, fixing up the Bonjour Service entry in Services, uninstalling the old version of Adobe Flash Player plugins that are installed by CS3 etc) all within cmd.exe and then finished the capture. I've used this as my base (which is currently being tested by a couple of users in production) so that I've got something to come back to if I stuff up. Believe it or not but this is my first virtualised application. I don't think I could have picked a larger application to start with ;-) Unfortunately our normal methods of distributing software are struggling with CS3 and virtualising looked liked the way to go.
To get the patches onto the layer I have done an Update Layer in SVS Admin and run cmd.exe. From there I have run up all of the patches that I've extracted on another machine when the Adobe Updater program is run (the Updater dumps all of the patches into the Local Settings area of the user profile just prior to installation). I can install the majority of them but I'm struggling with the ones detailed above.
I'm seriously thinking of using Wise Packaging Studio to create an msi of the troublesome patches being installed onto a workstation that has had Adobe Creative Suite 3 traditionally installed. I would then use this MSI to install the troublesome patches into the layer (the troublesome patches don't appear to use MSI technology during installation but I haven't fully researched this).
Any thoughts on this?
Appreciate the help.
Cheers
Craig
Give it a shot, it can't
Give it a shot, it can't hurt.