<div>
If it's an exact copy... how are you handling the conflicting IP addresses?<br />
<br />
I suspect that'll be the source of many of your problems... and if you are changing the address (or *shiver* using DHCP for the server address), there is a entry being made in DNS so that the clients can find the KMS server... and that could be getting stomped on when the two machines fight over the address. &nbsp; (But the problem might just be IP address conflicts... maybe with your switches getting involved in the fight as well.)
</div>


<div>
The VMware &quot;copy&quot; is powered off. &nbsp;Was meant to be 'inferred' by what I wrote above.. &nbsp;Sorry. &nbsp;It's a cold V2V'd copy of the Xen VM.
</div>


<div>
And as I think about it... if the copy is being turned on after being in cold storage for a few months while the original was still online... the computer account password may have also changed. &nbsp;That might also prevent an older machine brought out of storage (backup) from being able to do it's job too.)
</div>


<div>
<i>&gt; The VMware &quot;copy&quot; is powered off.</i><br />
<br />
It was powered off while you took the backup... but you're thinking about turning it on?<br />
<br />
You're asking about having an original machine and a copy made from it on the network at the same time. &nbsp;(? &nbsp;I think that's what you were originally asking.) &nbsp;They can't both be on at the same time. &nbsp;You need to do something like a sysprep (so that they aren't the same server from the point of view of active directory), and change the IP address of one of them. &nbsp;If that's a direction you want to pursue, I'd also need to look up how the KMS licensing would handle being moved to a new machine (which is what it would look like to KMS.)<br />
<br />
You _can_ have more than one KMS server in your environment though... and as long as you reach the minimum license counts on each of the servers to activate them... it'll work fine.
</div>


<div>
No. &nbsp;I want to retire the one on Xen because of these intermittent issues and bring the VMware one online that I V2V'd a few months ago to take its place. &nbsp;The computer account thing is valid, but rejoining it to the domain should fix that.<br />
<br />
Again, I V2V'd the Xen VM over to the VMware environment a few months ago...the VMware one has been off ever since.<br />
<br />
I'm more concerned about the KMS part. &nbsp;Whether or not that'll complain about anything or, worse, the clients don't like it.
</div>


<div>
I passed this on to our tech in charge of the KMS server and while most of this seems to be applicable, some of it was not. &nbsp;Also, he decided that some of our licensing wasn't *in* KMS and figured it would be better (as we all agreed) to move this functionality off the KMS and out to M.S. &nbsp;<br />
<br />
I'm sure that your suggestion is more or less spot on, though. &nbsp;Thank you for all your help!
</div>


<div>
<div class="content wysiwyg-content">
We have a VM running on a Xen environment acting as a KMS server. &nbsp;A few months ago, we V2V'd it to our VMware environment as sort of a 'backup' of the production KMS. &nbsp;Reason being was the Xen VM was acting flaky (everything on the environment is, not just the KMS server).<br />
<br />
It's acting weird again now, pinging on and off while powered up. &nbsp;Causing some licensing issues- not getting validated.<br />
<br />
Question is, if the VMware version is powered on in the Xen VM's place, how do the clients react? &nbsp;Is there something stored on the Xen VM that would prevent the VMware one from doing it's job? &nbsp;It's an exact copy of the Xen one, just 3-4 months old.<br />
<br />
Any insight would be appreciated.<br />
<br />
Thanks in advance!
</div>
</div>


We have a VM running on a Xen environment acting as a KMS server.  A few months ago, we V2V'd it to our VMware environment as sort of a 'backup' of the production KMS.  Reason being was the Xen VM was acting flaky (everything on the environment is, not just the KMS server).

It's acting weird again now, pinging on and off while powered up.  Causing some licensing issues- not getting validated.

Question is, if the VMware version is powered on in the Xen VM's place, how do the clients react?  Is there something stored on the Xen VM that would prevent the VMware one from doing it's job?  It's an exact copy of the Xen one, just 3-4 months old.

Any insight would be appreciated.

Thanks in advance!

Microsoft Key Management Server

Windows Server 2008 and Windows Server 2008 R2, based on the Microsoft Vista codebase, is the last 32-bit server operating system released by Microsoft. It has a number of versions, including including Foundation, Standard, Enterprise, Datacenter, Web, HPC Server, Itanium and Storage; new features included server core installation and Hyper-V.