bkmemeo's Posts

Hey Everyone, My problems were compounded by: 1) My PC had multiboot option, where it would boot into a Media Player mode (which refused to copy out.) 2) My UAC settings had to be stepped down... See more...
Hey Everyone, My problems were compounded by: 1) My PC had multiboot option, where it would boot into a Media Player mode (which refused to copy out.) 2) My UAC settings had to be stepped down to "Do not Notify" 3) My Remote Access had to be "less secure" 4) My firewalls had to be disabled. 5) And the one which is most relevant to the thread, is "If your vCenter server has to be accessed via VPN, then the VPN has to be UP on your Source Machine." Or it fails with the error above.... Enjoy, and I hope my reply was helpful!
I am going through a similar dilemma. Before you do anything, I recommend taking a look at the Interoperability Matrix first. VMware Product Interoperability Matrices Simply put ESXi v5.0... See more...
I am going through a similar dilemma. Before you do anything, I recommend taking a look at the Interoperability Matrix first. VMware Product Interoperability Matrices Simply put ESXi v5.0 will not be supported on vCenter v6.5 version, as ESXi v5.5 is the last one to be "included" under that formula. So, review your versions carefully, and your options, and then either purchase another vCenter license to support your older VM Hosts, or upgrade all v5.0 hosts to at least 5.5.0 U3 and extend your life cycle, but probably only until v7.0 vSphere shows up.... Regarding your question about upgrades - You can either upgrade, then migrate the license to another host, Or, Not upgrade at all. The old licenses *might* still work, for just the reason you are describing, (bring up new host on 6.x eval , migrate VMs, decommission 5.0 box, upgrade license, apply to new host) but probably only for a very limited time (60 days or less in total.) You ought to be able to connect the new vSphere hosts under eval licenses, and then push the VMs over, and then apply the new upgrade license once the migration has completed, and the 5.x box is offline.  I think that I would put a ticket into Support to validate this method, unless you have time to test the theory yourself....
The UNIX interface asks for an "account UPN", here's the default: account UPN : Administrator@vSphere.local
The UNIX interface asks for an "account UPN", here's the default: account UPN : Administrator@vSphere.local
The UNIX interface asks for an "account UPN", here's the default: account UPN : Administrator@vSphere.local
For those who do not get this resolved by changing SATA to IDE, the "correct" answer is that it's a bug, and that it is now supposedly fixed: Resolution:- Upgrade the ESXi to 6.0 U1b http://pub... See more...
For those who do not get this resolved by changing SATA to IDE, the "correct" answer is that it's a bug, and that it is now supposedly fixed: Resolution:- Upgrade the ESXi to 6.0 U1b http://pubs.vmware.com/Release_Notes/en/vsphere/60/vsphere-esxi-60u1b-release-notes.html           Windows 10 VM VMX fails        The Windows 10 VM vmx process fails with an error message similar to the following in the vmware.log file:     NOT_REACHED bora/devices/ahci/ahci_user.c:1530          This issue is resolved in this release. If it does not resolve the problem, I will update this posting. For those who aren't ready to upgrade, the workaround for me has been to shutdown the VM, and remove the CDROM altogether, and reboot.