All Posts

my vCenter doesn't have an FQDN, so when deploying I don't include any FQDN. once it finished deploying, the hostname by default will be "phaton-machine". Is it possible to add an SSL Certificate without using an FQDN?

Previously my vcenter was functioning normally, then an error appeared. "[400] An error occured while sending an authenticationrequest to the vCenter Single Sign-On server - An error occured when processing the metadata during vCenter Single Sign-Onsetup - Failed to connect to VM ware Lookup service Back to login screen https ://IPvCenter/lookupservice/sdk - SSL certificateverification failed"     I then checked my ssl certificate and the result is "Not Such File or Directory)  (image 1). Then I tried regenerating the VMCA SSL certificate. certificate added successfully, but still unable to login to vCenter. error 503 Endpoint appears in login (image 2)

Hey guys, we try to generate an OVA appliance for VMware player/Fusion as well as ESXi/vSphere. We build the OVA manually, using an OVF based on an ovftool or ESXi export, a VMDK and a manifest (.mf) file with SHA1 hashes for the other two files, then adding those three into into a gzipped tarball with OVA ending. Our first attempt was with an OVF generated via ovftool from a VMX that we successfully used on VMware player before. This OVA could be imported into VMware player successfully, but it failed to be imported to ESXi, directly or via vSphere, throwing an error about a mismatch between manifest file and content. The manifest file looked like this: SHA1 (<name>.ovf) = <sha1> SHA1 (<name>.vmdk) = <sha1> We compared it with an export from ESXi and found the spaces around the filename parenthesis to be missing. Removing them from the one above, generated by ovftool, allowed the appliance to be imported in ESXi. We then generated a new OVF with some tuned hardware settings based on an ESXi export, where the spaces were missing expectedly. It imports fine on ESXi and vSphere, but fails with the manifest mismatch error on VMware player. Interestingly, adding the spaces does not solve it. We tried to compare with another ovftool VMX conversion with newer VMX version, which then as well didn't contain those spaces anymore, but SHA256 hashes instead. Trying to use SHA256 hashes within the other appliance (of course with correct hashes for the two files, double checked), with or without spaces still failed. This all makes me think that the exact format as well as the used hashing algorithm highly depends not only on the VMware product, but also on the used OVF and VMX version strings defined in the OVF file: The latter is defined within the OVF as well, e.g. via <vssd:VirtualSystemType>vmx-13</vssd:VirtualSystemType> which indicates hardware version 13. Is there an overview of the exact expected/functional manifest file format and supported hashing algorithm for each project, depending on OVF version, VMX version? Best regards, Micha

Hello everybody, I have a problem regarding the choice of an UPS managing our ESXi servers. All of them that I have seen, use the vMA to send network shutdown commands to the ESXi server and gracefully shutdown all virtual machines and then the ESXi itself. For security reasons I cannot use the VMware vMA installed on the ESXi, and as well I cannot use SSH to send shutdown commands via scripts to the ESXi, also with a direct USB connection instead of a network connection. It is a big problem, but has somebody experienced that problem and found a good UPS that doesn't use vMA or a working solution ? Thanks in advance

We have built VMWare Health Analyzer appliance from image provided by VMWare. This appliance automates the collection of VMWare Inventory, configuration and utilization data. Qualys Scan is reporting vulnerability with this appliance. Here is the detail; please help us remediate this issue. HTTP Security Header Not Detected X-Frame-Options or Content-Security-Policy: frame-ancestors HTTP Headers missing on port 8080. GET / HTTP/1.1 Host: pvmhchka1.theocc.com:8080 Connection: Keep-Alive HTTP/1.1 200 Accept-Ranges: bytes ETag: W/"98-1553772262000" Last-Modified: Thu, 28 Mar 2019 11:24:22 GMT Content-Type: text/html Content-Length: 98 Date: Sun, 07 Jun 2020 02:29:45 GMT X-XSS-Protection HTTP Header missing on port 8080. X-Content-Type-Options HTTP Header missing on port 8080.

Hey everyone, is it safe to just delete vCSA from vSphere? My vSphere Client works but the The vSphere web client doesn't work, the vCSA can't start inventory service, etc. So I would like to start from scratch. If I delete the vCSA straight from vSphere, there's no fear that this would cause issues with VMs, right? I just need to know that all the VMs will keep running with no interruptions. Cheers