No issues with the same license file on multiple VC's. Remove and Add
pretty much basically
From: richardmccl...@aspca.org [mailto:richardmccl...@aspca.org]
Sent: Wednesday, November 04, 2009 10:36 AM
To: NT System Admin Issues
Subject: RE: Moving VMWare management suite
Thanks! We
P2V the server, shut down the old server, connect to the newly created VM from
VI client (just type in the IP address in a browser) tweak your settings and
scrap the box. I did it like this and had absolutely no issues.
John W. Cook
Systems Administrator
Partnership For Strong Families
315 SE 2n
We've got 2 DCs, one 2K3, one 2K8, both virtual. :)
>>> 11/4/2009 7:06 AM >>>
Thanks for the info on the license!
By "starting from scratch", would this mean a database would get guest
information from the ESX servers (two of them) and populate the
client?
Meanwhile, as far as P2V, having thi
pca.org [mailto:richardmccl...@aspca.org]
> Sent: Wednesday, November 04, 2009 10:07 AM
> To: NT System Admin Issues
> Subject: RE: Moving VMWare management suite
>
>
> Thanks for the info on the license!
>
> By "starting from scratch", would this mean a databa
09 10:07 AM
To: NT System Admin Issues
Subject: RE: Moving VMWare management suite
Thanks for the info on the license!
By "starting from scratch", would this mean a database would get guest
information from the ESX servers (two of them) and populate the client?
Meanwhile, as far as
Thanks for the info on the license!
By "starting from scratch", would this mean a database would get guest
information from the ESX servers (two of them) and populate the client?
Meanwhile, as far as P2V, having this as a VM makes me a bit nervous. (So
does virutalizing ALL my domain controlle
Don't worry about the Host's they maintain a license for some time when
they can't communicate with a License server. While you can do a
migration export the DB and re import, I always find it's best to start
over fresh if you have all the pieces you need. Also you can do a P2V of
the server itself
