SureshKumarMuth's Accepted Solutions

Login to both ESXi nodes directly using host client and check where are VMs are actually running from. It could be a sync issue. then you can decide on which node the management agent has to be restarted. If doesn't help you may try restarting the VC services.

I think you have your vcenter database on external SQL server. Take a backup of Database and try to reinstall the vCenter server pointing to same database. It may fix the issue. User permissions are stored in vCenter database.  If you want to restore only the user permission , then you have to look at the appropriate database tables which contains the information user information but this may mostly wont work as there could be some database primary or foreign key constraints and fixing them would be tedious. Else you have to manually assign permissions again. I don't have any running 5.5 setup to find the table information for you. 

After changing the root password, the host will not immediately disconnect from the vCenter server. However, if the host gets disconnected from the VC in future for some reason, it will not connect back to VC automatically unless you give the new password.  I would suggest not  to get into that situation in future unexpectedly , since the hosts are in cluster,  try to evacuate VMs using vmotion and change password, reconnect the host with new password . do this for all the hosts, you may avoid issues in future.

By default XP machine should have intel driver which supports E1000, however you may try using VMXNET3 type of card so that the driver comes with vmware tools and check if that works for you. --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.

Vmware official document says "you might need to place the host in MM" for some settings instead of must, still you can try it on one host, if maintenance mode is required while remediating the host , it will stop until the host enters maintenance mode . https://docs.vmware.com/en/VMware-vSphere/6.5/vsphere-esxi-vcenter-server-65-host-profiles-guide.pdf  Check "  remediate a host " section You can test this in vmware hands on lab host if you can't do it on prod environment. --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.

Yes, you can do this. But you are going to lose DRS features. --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.

Yes, creating trunk ports will work. But you said one host in secure zone, so generally network team wont club DMZ with normal zone... Still it is possible by trunk. --------------------------------------------------------------------------------------------------------- Was it helpful? Let us know by completing this short survey here.

The VM network what your see there is the port group name comes from the virtual switch, it doesnt indicate your virtual nic (VNIC) type. Inorder to change the vnic while creating the VM you have to click the down icon and change the nic type as given in the attached image .

Can you  check the scratch partition settings Connect to ESXi host using Host Client. Click Storage. Right-click a datastore and click Browse. Create a uniquely-named directory for this ESXi host. For example: .locker-ESXHostname Close the Datastore Browser. Click the Manage tab Under System, click Advanced System Settings. The setting ScratchConfig.CurrentScratchLocation shows the current location of the scratch partition. If it is configured with current datastore, try to change it to /tmp and check to unmount the DS again. Also check "lsof | grep '/vmfs/volumes/'" , it will show the current open files in the filesystem.

Yes, if the nic driver is already in place. ESXi should detect the card. In your case, you already have the similar NIC which is working fine, so it will be good to add the card. You will see these cards under host --> configuration --> network adapters list Later they can be added to vSwitch manually.

https://www.vmware.com/resources/compatibility/sim/interop_matrix.php#upgrade&solution=1 Check the above link , you can consider this as official support. The reason is because 6.7 released before 6.5 U2.

Have you made any other software changes (patching or vib installation) after march 20 ? If no, then you can use shift + R option to revert the OS to previous state before patching. VMware Knowledge Base