Could Windows update have updated the other VM's?
--
Bob Comer
--
Sincerely,
Daniel Petri
MVP, Senior IT consultant, trainer
www.petri.co.il
-----------------------------------
"Bill" <Bi...@discussions.microsoft.com> wrote in message
news:3171703A-52D2-4C85...@microsoft.com...
However it may have happened, you can uninstall SP3 from whichever vms you
need to. If any of the vms were running in the background then they might
have been automatically updated by WU if the settings for WU permit that,
but upgrading to SP3 is a fairly noticeable process. Be sure to reinstall
the virtual machine additions in the vms you leave upgraded to SP3 if you
are using VPC SP1.
As for your host, make sure Windows update is set to not run if you
want to make sure SP3 doesn't get installed.
--
Bob Comer
--
Bob Comer
Bill:
I think the .vmc has both absolute paths and relative paths for the associated
.vhd's. If it cannot find them using the absolute path, then it uses the
relative path. In your case, it found the vhd's using the absolute path, which
is not what you wanted.
It would be better, IMHO, if it warned you when the absolute and relative paths
were inconsistent.
--
David Wilkinson
Visual C++ MVP
>What I did originally was to configure a VM with Windows XP Pro SP2. Then I
>copied that folder and renamed it to XP Pro SP2 with Dot Net and added a new
>existing VM and installed Dot Net 2.0. I did this for the 3rd machine only
>named SP3 and installed SP3. The 3rd machine lost Dot Net 2.0 and all 3
>machines became SP3.
>I'm hoping that it hasn't hit my host machine.
You cannot do it in that way!
What has hit you is that you copied the vmc file from the original
install and this file contains among other things the full path to the
vhd file. So even though you have copied everything to a new folder
you are in reality running the *same* virtual machine from all three
vmc files!!!
The proper way to make a *copy* for testing is this:
- Make a new folder for the copy
- Copy the vhd file(s) over to this folder from the original
- Use the VPC Wizard to create a new machine and point it to the
copied vhd file whan asked for the virtual disk
Now you have a new machine with its own hard disk (the vhd file) and
its own MAC address for the network. If you copy like you did you will
have the *same* disk and the *same* MAC address which will screw up
the networking too...
Alternately in your situation:
Start with making the vhd file of the original install readonly
Then create differencing disks from this original. (File/Virtual Disk
Wizard/....)
Finally create a new virtual machine and point it to the differencing
disk rather than the copied vhd as above.
This saves space on the host disk drive because the original will be
used for all copies without changing anything on the original.
How 'bout turning off the HTML and learning to bottom post.
>> How 'bout turning off the HTML and learning to bottom post.
>
> Whining about top posting laughed at.
He's right, though...
--
Mark Rae
ASP.NET MVP
http://www.markrae.net
So you also think you're among the cognoscenti but you choose to ignore
common courtesy. You're among the ones to be laughed at.
----------------------------------------------------------------------------------------------------
Because it makes for easier reading to see the answer AFTER the question.
Why is bottom posting so widely accepted as proper "netiquette"?
YES! Open wide!