After you are finished setting up the machine, do a full shut down of the virtual Windows operating system. Then go to the folder in which the virtual hard drive is stored and make a copy of it. If Internet Explorer should ever become infected with anything, you can delete the virtual machine. After doing so, make a copy of your backup virtual machine (always leave the backup pristine and untouched).
Now all you have to do is to create a new virtual machine. As I showed you when I walked you through the process earlier, the New Virtual Machine wizard has an option to use an existing virtual hard drive. By pointing the wizard to the copy that you just made of the backup virtual hard drive, you can be back up and running in a matter of minutes without having to reinstall or reconfigure Windows.
Running Internet Explorer in a virtual machine won't prevent Internet Explorer from becoming infected with
Requires Free Membership to View
When you register, you’ll also receive targeted alerts from my team of editorial writers and independent industry experts with the latest news, tips, and advice to help you do your job more efficiently and effectively. Our goal is to keep you informed on the hottest topics and biggest challenges faced by IT professionals today working with desktop management and security technologies.
Margie Semilof, Editorial Director
Running IE on a virtual machine
Home: Introduction
Step 1: VMware versus Microsoft Virtual PC
Step 2: Deploying Microsoft Virtual PC
Step 3: Setting up Internet Explorer
| ABOUT THE AUTHOR: |
|
Brien M. Posey, MCSE, is a Microsoft Most Valuable Professional for his work with Windows 2000 Server and IIS. He has served as CIO for a nationwide chain of hospitals and was once in charge of IT security for Fort Knox. As a freelance technical writer, he has written for Microsoft, TechTarget, CNET, ZDNet, MSD2D, Relevant Technologies and other technology companies. You can visit his personal Web site at www.brienposey.com.
. Copyright 2005 TechTarget |
This was first published in June 2006
Join the conversationComment
Share
Comments
Results
Contribute to the conversation