Moving hosts from a broken vCenter

[Pawel128564]

Hi,

After a power cut our old vCenter was no longer available, we could not log on to it via web, Windows client or even using the console.

The appliance has been deleted and we have installed a new vCenter 6.7. This is what I am getting when I am trying to add hosts to the new appliance:

"Assignment Validation for License 1

1. The license is present in another vCenter Server system. If you assign the license, the licensing configuration will become non-compliant.

2. Cannot decode the licensed features on the host. Changing its current license might fail or some features might become unavailable."

Unfortunately I have deleted the old system image, so the migration is necessary. Could you please advise what I have to do to:

1. Move the license to the new vCenter system having no access to the old one?

2. How to get rid of the second error "cannot decode the licensed features on the host"?

I have to move over three hosts.

Thank you for taking time to read this.

[IRIX201110141 · Accepted solution]

Cant you just click next?

Seen the first message in the past and its only to inform you not to double use a license. It just for compliance/legal and i am pretty sure you can ignore the message.

Unsure if i ever read the second message.

If there is a next button... just clickt it.

Regards,
Joerg

[a_p_]

Welcome to the Community,

some questions:

• what's the ESXi host's version/build number?
• which license/edition do you have for vCenter Server, and the ESXi hosts?

André

[Pawel128564]

I was tempted to do so, though it is a live system, and I do not want to experiment with it; hence the question.

[Pawel128564]

Hi André a.p.​

Thank you for your reply, our ESXIs are 6.0.0 version 600.9.3.30.2 and the new vCenter is 6.7.0.40000

Will the ESXIs need updating before they can be connected to the vCenter?

Regards

Pawel

[a_p_]

No need to upgrade, I just wanted to be sure.

You may do as IRIX201110141 said, and just ignore the warnings.

They show up because the new vCenter recognizes that the host has been connected to another vCenter before, and makes you aware of a possible compliance issue, which however doesn't exist in this case. Once the host is added to vCenter Server, the second message should go away too.

André

[Pawel128564]

Thank you, I will give it a try and tell you how it went.

[Pawel128564]

So you were right, I just needed to ignore the messages and click next. Thank you for your help.