Failed to deploy VM: postNFCdata failed when deploying AlienVault to VMware ESXi 6.5

I have tried various browsers, including Edge, Chrome and Firefox but the error existed on all of them. I had no problem uploading the OVA file to the datastore but VMware just refused to import the damned OVA to a VM. I even asked nicely!

The Solution

There appears to be a few solutions but the one that worked for me was to use the VMware OVFTool to import the OVA file from the command line. Here’s the working command line.

1. Download Vmware OVF tool from its website and install.
https://www.vmware.com/support/developer/ovf/

2. If you istall OVF tool in C drive then,
            i. cd C:\
            ii. cd "Program Files"
            iii. cd VMware
            iv. cd "VMware OVF Tool"
3. Then for export VMware as this syntax
ovftool vi://username:password@vCenter1/Datacenter1/vm/SourceVM OVF.ovf

Eg. ovftool.exe vi://192.168.1.200/Test_Dev "W:TestOVF"
 Now its ask Esxi username and password type root user and password then continue to export ovf.

Note: The Special Characters used in the esxi password  are not supported so have to convert them to respective hex value followed by % using below link.

https://www.cisco.com/c/en/us/td/docs/ios/12_4/cfg_fund/command/reference/cfnapph.html

4. After exporting the VMware you can import to another esxi with the below syntax.


Eg. 
vftool.exe -ds=NAS_DATASTORE1 -nw="UAT" -dm=thin -n=Test_Dev "W:\NewOVF\Test_Dev\Test_Dev.ovf" vi://192.168.200.104



Hope this may help.

Configuring windows 10 as KMS server an activating other win 10 clients

Installing a KMS host key on a computer running Windows 10 allows you to activate other computers running Windows 10 against this KMS host and earlier versions of the client operating system, such as Windows 8.1 or Windows 7.

Configure KMS in Windows 10

1. Open an elevated command prompt.
2. Enter one of the following commands.
• To install a KMS key, type slmgr.vbs /ipk <KmsKey>.
• To activate online, type slmgr.vbs /ato.
• To activate by using the telephone, type slui.exe 4.
3. After activating the KMS key, restart the Software Protection Service.

Now the KMS Server is configured successfully you can activate your windows 10/8 Client using the following Command

1. Run> CMD (Run As Administrator)
2. Slmgr.vbs /dlv (Check KMS_Client Channel info, if not follow another steps shown below).
3. Slmgr.vbs /skms <Server IP> (to register KMS Server at client).
4. Slmgr.vbs /ato (to activate Client)

If there is no  KMS_Client Channel, follow this:

1. Slmgr.vbs /ipk <Convert Key> (to convert to KMS_Client Channel)
2. Slmgr.vbs /skms < Server IP> (to register KMS Server at client)
3. Slmgr.vbs /ato (to activate Client)