Fcolau's Posts

Guess I'll have to upgade my VCSA before upgrading my others ESX  xD I usually update my VC before the ESX, but I received a new ESX so I wanted to gain time and install it in 6.5 instead of 6.0... See more...
Guess I'll have to upgade my VCSA before upgrading my others ESX  xD I usually update my VC before the ESX, but I received a new ESX so I wanted to gain time and install it in 6.5 instead of 6.0, my bad. Thanks for the answers guys !
Hi ! I thought I could connect an ESXi 6.5 to a 6.0 Vcenter, was I wrong ? I thought between major version it was possible ? Each time I try I got an error in vsphere client : "timeout wait... See more...
Hi ! I thought I could connect an ESXi 6.5 to a 6.0 Vcenter, was I wrong ? I thought between major version it was possible ? Each time I try I got an error in vsphere client : "timeout waiting for vpxa to start" and on the host in vpxa.log I got : 2016-11-24T15:49:06.036Z error vpxa[AD6DB70] [Originator@6876 sub=SoapAdapter] Unsupported version URIurn:vpxa3/6.0"
After 1 day, of uninstall/reinstall/install, trying SSL things and lots of things I found online, the solution is the DUMBEST thing ever. WHY DO VMWARE USE C:\ProgramData\VMware\ls_url.txt to pr... See more...
After 1 day, of uninstall/reinstall/install, trying SSL things and lots of things I found online, the solution is the DUMBEST thing ever. WHY DO VMWARE USE C:\ProgramData\VMware\ls_url.txt to provide the URL of the LookupService to the Webclient ??? During install you provide the URL for registering with SSO, why the hell isn't it writing that URL somewhere and using it after ?! And why the hell with all the unstalling/reinstalling of ALL THE COMPONTENT of the Vcenter I made, that DUMB txt file wasn't updated with the new DNS name of my server ?? Anyway, my webclient is now working, but 1 day of work and mental torture not understanding why the hell my client wasn't working because of a fucking text file, it's depressing.
HI, I had a Vcenter server named virtualcenter.domain.com (192.168.1.10) with Vcenter 5.1 (With SSO, Inventory, Webclient) on a windows 2008 R2 with a MSSQL2012 db. I tried to update from 5.1... See more...
HI, I had a Vcenter server named virtualcenter.domain.com (192.168.1.10) with Vcenter 5.1 (With SSO, Inventory, Webclient) on a windows 2008 R2 with a MSSQL2012 db. I tried to update from 5.1 to 5.5u1 and it failed, Vcenter & Webclient installers were crashing before finishing update So I decided to make a clone of my Vcenter  and have my production still working while I was trying to update. my clone was virtualcenter2.domain.com with a new IP 192.168.1.12 I uninstalled everything, for the webclient I had to cleanup files and registery entries manually since it didn't want to find the uninstall program when I was clicking uninstall. Then the installation went well, everything except the webclient is working fine When trying to log in on the new vcenter : https://virtualcenter2.domain.com:9443/vsphere-client/ I got : Failed to connect to VMware Lookup Service https://virtualcenter.domain.com:7444/lookupservice/sdk - SSL certificate verification failed. Why the error message is with the old DNS name ? And why during install the webclient is connecting to the lookup service perfectly and then it's not working ?
The server is a Dell 2950. We tried this morning to reinstall ESX 3.5 with the option "Keep Virtual Machines & VMFS", the ESX is now booting but it don't have a datastore. But,... See more...
The server is a Dell 2950. We tried this morning to reinstall ESX 3.5 with the option "Keep Virtual Machines & VMFS", the ESX is now booting but it don't have a datastore. But, we followed another procedure we found on internet : with LVM Resignature, rescan the Storage Adapter, and create new UUID for the VMs and it works
Hi, First i would like to apologize for my english because it's not my mothertongue. Now my problem, we got today an electrical failure, all our servers went down, one of our ... See more...
Hi, First i would like to apologize for my english because it's not my mothertongue. Now my problem, we got today an electrical failure, all our servers went down, one of our ESX is impossible to book, he wants to enter in maintenance mode to repair a filesystem. But, when we try this, with fsck all filesystems are good, thus I suppose it's the vmfs wich is corrupted ? (you can see the error message on the attached file) Anyone can help me ?