I remember when I used to have a whole row of PCs being reimaged on a regular basis to support testing that that can now be done on one PC with far more speed thanks to tools like VMware Workstation. I create a snapshot of a clean system and just roll back again and again to create packages, test packages, etc. I think this is fairly common practice today, but I wonder if anyone has any special tips they can share on the matter?

One thing I'll often do is map a drive to the network share where I keep my packages and have that window open when I take my snapshot. This way when I start up a new session, I need only refresh the page to have quick access to what I'm most commonly going to be working with.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hey Bob.

Just as you describe, this is the standard and most effective way to package applications. We use the Microsoft App-V to pacakage some of our applications, so I usually have all the common folders and tools that I will need while sequencing the application and take a snapshot of that, once I finish packaging, I revert to the "clean" stated and start over again :-).
Answered 11/17/2010 by: mast3rm1nd
Senior Yellow Belt

Please log in to comment
0
Yes!! I know what you mean. VMware make things a lot easier. You may want to check this blog for more tips: http://blogs.vmware.com/thinapp/2008/10/how-to-make-a-t.html
Answered 06/08/2011 by: elenahernandez
Yellow Belt

Please log in to comment
0
Just reading this over again I noticed that I didn't put the technolgy I was using to run my virtualizations, lol. At work we use VMware ESXi, and at home I use MS Virtual PC 2007, which is free from Microsoft...
Answered 06/28/2011 by: mast3rm1nd
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity