chall32's Posts

It would appear that vCenter 8 is very fussy when it comes to importing certificates CSR derived or otherwise. I managed to get my CSR derived internally signed cert accepted by vCenter by not addin... See more...
It would appear that vCenter 8 is very fussy when it comes to importing certificates CSR derived or otherwise. I managed to get my CSR derived internally signed cert accepted by vCenter by not adding or changing any subject alternative name information. For me the issue looked like it was something to do with this. If I added any, the import would fail. I’ve documented the process I followed here https://polarclouds.co.uk/vsphere-certificates-vmca-hybrid-mode/#configuring-vmca-hybrid-mode From memory, when signing the CSR, the subject alternative info from the CSR had an “IP Address” field added that was blank (that is no IP address set).  Deleting the IP address field and continuing to sign the CSR resulted in a certificate vCenter was happy to import. Finally, when importing the signed certificate and the root certificates, try copying and pasting the vCenter certificate and CA certificate crt file contents into step 2 of the replace certificate wizard, rather than using the browse file buttons. Hope this helps!
Nice one, thanks William   
Seems to be a PowerCLI v13 issue.  Works fine for v7.0U3i with PowerCLI v11.2 (yeah old version, but it's all I had to hand to test with!!) 
Found the error in /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log: [2022-11-03T15:31:03.619Z] [ERROR] http-nio-5090-exec-4 com.vmware.vise.mvc.exception.GlobalExceptionHandler ... See more...
Found the error in /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log: [2022-11-03T15:31:03.619Z] [ERROR] http-nio-5090-exec-4 com.vmware.vise.mvc.exception.GlobalExceptionHandler Exception handled while processing request for /ui/certificate-ui/ctrl/certificates/tls: com.vmware.vapi.std.errors.Error: Error (com.vmware.vapi.std.errors.error) => { messages = [LocalizableMessage (com.vmware.vapi.std.localizable_message) => { id = com.vmware.certificatemanagement.error, defaultMessage = Exception found (0), args = [0], params = <null>, localized = <null> }], data = <null>, errorType = ERROR } Full error attached.
OK good to see some have got it working using public certs.  I'm still struggling to replace the machine cert with a cert generated by an internal CA. acursory look through the logs in /var/log/vmwa... See more...
OK good to see some have got it working using public certs.  I'm still struggling to replace the machine cert with a cert generated by an internal CA. acursory look through the logs in /var/log/vmware/certificatemanagement and /var/log/vmware/certificateauthority isn't providing much help either!
The problem is not with the certificate, it is with the application of the newly generated certificate into vCenter 8.
Confirmed. vCenter 8.0, I'm seeing same error: Error occurred while fetching tls:0 when trying to replace machine certificate with certificate genrated using a CSR generated by vCenter itself.
Hey all, Following https://kb.vmware.com/s/article/2042141 Running PowerCLI v12.4 and trying to backup the config of a newly deployed 7.0U3 (build 18644231) host via the command: Get-VMHostFirmwar... See more...
Hey all, Following https://kb.vmware.com/s/article/2042141 Running PowerCLI v12.4 and trying to backup the config of a newly deployed 7.0U3 (build 18644231) host via the command: Get-VMHostFirmware -VMHost "192.168.25.130" -BackupConfiguration -DestinationPath C:\Temp   Receiving the following error via PowerShell: Get-VMHostFirmware : 07/10/2021 15:50:29 Get-VMHostFirmware A general system error occurred: Internal error At line:1 char:8 + $Bkp = Get-VMHostFirmware -VMHost "192.168.25.130" -BackupConfigurati ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : NotSpecified: (:) [Get-VMHostFirmware], SystemError + FullyQualifiedErrorId : Client20_SystemManagementServiceImpl_BackupVmHostFirmware_ViError,VMware.VimAutomation.ViCore.Cmdlets.Commands.Host.GetVMHostFirmware   Checking the hostd.log on the host being backed up, the following can be seen: 2021-10-07T14:50:26.929Z info hostd[67218] [Originator@6876 sub=Vimsvc.TaskManager opID=54b7e8b1 user=root] Task Created : haTask--vim.host.FirmwareSystem.backupConfiguration-22 2021-10-07T14:50:26.933Z error hostd[68361] [Originator@6876 sub=SysCommandPosix opID=54b7e8b1 user=root] Failed to ForkExec /sbin/firmwareConfig.py: No space left on device 2021-10-07T14:50:26.933Z error hostd[68361] [Originator@6876 sub=SysCommandPosix opID=54b7e8b1 user=root] Invocation of process: '/sbin/firmwareConfig.py' failed: Resource error - Process Creation - Error: VmkuserCompat_ForkExec - Error No space left on device 2021-10-07T14:50:26.933Z error hostd[68361] [Originator@6876 sub=Default opID=54b7e8b1 user=root] SysCmd [/sbin/firmwareConfig.py ++group=hostd-tmp,mem=120 --backup /usr/lib/vmware/hostd/docroot/downloads/52ff03dc-1824-6e7e-f0fd-2483fed1618a] invocation failed: Resource error - Process Creation - Error: VmkuserCompat_ForkExec - Error No space left on device 2021-10-07T14:50:26.933Z info hostd[68361] [Originator@6876 sub=AdapterServer opID=54b7e8b1 user=root] AdapterServer caught exception; <<5262a00e-bc88-43d6-23ae-26badb42c225, <TCP '127.0.0.1 : 8307'>, <TCP '127.0.0.1 : 31631'>>, ha-firmwareSystem, vim.host.FirmwareSystem.backupConfiguration>, N5Vmomi5Fault11SystemError9ExceptionE(Fault cause: vmodl.fault.SystemError --> ) --> [context]zKq7AVICAgAAAAd9HAELaG9zdGQAAOJCF2xpYnZtYWNvcmUuc28AAbhMT2hvc3RkAAEA21EB5raSgkeLGQFsaWJ2aW0tdHlwZXMuc28AAbB/UgCcxS0AJAEuANIOPwM7fQBsaWJwdGhyZWFkLnNvLjAABL2nDmxpYmMuc28uNgA=[/context] 2021-10-07T14:50:26.935Z info hostd[68361] [Originator@6876 sub=Vimsvc.TaskManager opID=54b7e8b1 user=root] Task Completed : haTask--vim.host.FirmwareSystem.backupConfiguration-22 Status error 2021-10-07T14:50:26.935Z info hostd[68361] [Originator@6876 sub=Solo.Vmomi opID=54b7e8b1 user=root] Activation finished; <<5262a00e-bc88-43d6-23ae-26badb42c225, <TCP '127.0.0.1 : 8307'>, <TCP '127.0.0.1 : 31631'>>, ha-firmwareSystem, vim.host.FirmwareSystem.backupConfiguration> 2021-10-07T14:50:26.935Z info hostd[68361] [Originator@6876 sub=Solo.Vmomi opID=54b7e8b1 user=root] Throw vmodl.fault.SystemError 2021-10-07T14:50:26.935Z info hostd[68361] [Originator@6876 sub=Solo.Vmomi opID=54b7e8b1 user=root] Result: --> (vmodl.fault.SystemError) { --> reason = "Internal error", --> msg = "", --> }     I'm using a 32GB HDD as discussed https://core.vmware.com/resource/esxi-system-storage-changes#section6  [root@bob:/bin] df -h Filesystem Size Used Available Use% Mounted on VMFS-6 99.8G 17.8G 82.0G 18% /vmfs/volumes/local VMFS-6 24.5G 1.4G 23.1G 6% /vmfs/volumes/datastore1 VMFS-L 6.2G 2.8G 3.4G 45% /vmfs/volumes/OSDATA-615f02a7-6d1518f5-113b-000c291c4ec3 vfat 499.7M 203.6M 296.1M 41% /vmfs/volumes/BOOTBANK1 vfat 499.7M 0.0B 499.7M 0% /vmfs/volumes/BOOTBANK2 [root@bob:/bin]   If found some old posts related to backup issues and /scratch/downloads folder not existing.  Not the same issue here: [root@bob:~] cd /scratch/downloads [root@bob:/vmfs/volumes/615f02a7-6d1518f5-113b-000c291c4ec3/downloads] ls [root@bob:/vmfs/volumes/615f02a7-6d1518f5-113b-000c291c4ec3/downloads]   Reinstalling the host with 6.7 U3  (build 17700523), the command completes without issue and a backup file is generated. Does anyone have any ideas?
Quick post to chime in - seeing this issue too.  Get-SpbmEntityConfiguration -VM MyVM Entity Storage Policy Status Time Of Check ------ ... See more...
Quick post to chime in - seeing this issue too.  Get-SpbmEntityConfiguration -VM MyVM Entity Storage Policy Status Time Of Check ------ -------------- ------ ------------- Get-SpbmEntityConfiguration : 17/03/2021 09:12:28 Get-SpbmEntityConfiguration Rule set has other line of service rules without any persistence line of service rule. At line:1 char:1 + Get-SpbmEntityConfiguration -VM MyVM + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidArgument: (:) [Get-SpbmEntityConfiguration], VimException + FullyQualifiedErrorId : Spbm_Impl_ProfileServiceImpl_RuleSetNoPersistenceNamespace,VMware.VimAutomation.Storage.Commands.Cmdlets.Spbm.GetSpbmEntityConfiguration MyVM compliant 17/03/2021 01:28:48 Seems to be the Storage Policy name that its having a problem returning.   Also running with Pure Storage, PowerCLI 12.2.0
Excellent, thanks Sivaramsharmar and LucD! I had spotted syncTimeWithHost although I hadn't realised it was the same as tools.syncTime Thanks again
Hey, I have a 5.5 vCenter full of VMs that I need to test compliance with KB1189 - Disabling Time Synchronization Using Get-AdvancedSetting I can test and receive results for all settings e... See more...
Hey, I have a 5.5 vCenter full of VMs that I need to test compliance with KB1189 - Disabling Time Synchronization Using Get-AdvancedSetting I can test and receive results for all settings except "tools.syncTime".  Is there a way to query this setting? Thanks
Yeah, no worries. Was looking for a "friendly" name.  Looking at http://packages.vmware.com/tools/versions it would appear that build 1892794 is referenced as "esx/5.5p02" - ESXi 5.5 Patch 2. ... See more...
Yeah, no worries. Was looking for a "friendly" name.  Looking at http://packages.vmware.com/tools/versions it would appear that build 1892794 is referenced as "esx/5.5p02" - ESXi 5.5 Patch 2. Top banana, that'll do for me.
OK, I wonder what the 1892794 build is referred to as then?  Would be handy to know for documentation purposes
Looking to create a custom ISO build for deployment (also including updated Cisco UCS drivers in the ISO to match UCS compatibility matrix), using PowerCLI. Looking at ESXi patch portal, there... See more...
Looking to create a custom ISO build for deployment (also including updated Cisco UCS drivers in the ISO to match UCS compatibility matrix), using PowerCLI. Looking at ESXi patch portal, there appears to be a patch available, patch ESXi550-201407001 that brings ESXi 5.5 to build 1892794 (VMware KB: VMware ESXi 5.5, Patch Release ESXi550-201407001) However when looking at VMware KB: Correlating VMware products build numbers to update levels build 1892794 is not listed. What is this patch and should I be using as a basis for my custom media? Cheers
Yep, working from the UK too! Cheers Rick.
Yep, link still broken.  Alternative link http://ftpsite.vmware.com/download/vSphereClient/VMware-viclient-all-4.1.0-799345.exe also now useless! Funny that: http://vsphereclient.vmware.com... See more...
Yep, link still broken.  Alternative link http://ftpsite.vmware.com/download/vSphereClient/VMware-viclient-all-4.1.0-799345.exe also now useless! Funny that: http://vsphereclient.vmware.com/vsphereclient/7/9/9/3/4/5/VMware-viclient-all-4.1.0-799345.exe does not work, yet http://vsphereclient.vmware.com/vsphereclient/7/8/6/1/1/1/VMware-viclient-all-5.1.0-786111.exe works just fine! Come on VMware sort it out!
must08 wrote: Check out the link for downloading VMware-viclient-all-4.1.0-799345.exe https://my.vmware.com/group/vmware/details?downloadGroup=ESXI41U3&productId=230&rPId=2876# OK.  Th... See more...
must08 wrote: Check out the link for downloading VMware-viclient-all-4.1.0-799345.exe https://my.vmware.com/group/vmware/details?downloadGroup=ESXI41U3&productId=230&rPId=2876# OK.  That is not a problem for me as I have a VMware logon. However, it isn't all that practical for everyone that simply need to download a VI client to access a vSphere environment (developers etc) create their own account on the VMware website simply just to download the v4.1U3 client. Sure the logins are free etc etc but it's still a hastle all the same. https://YourESXServerIP This in turn links you through to http://vsphereclient.vmware.com/vsphereclient/7/9/9/3/4/5/VMware-viclient-all-4.1.0-799345.exe which results in "File not found"  Try for yourself!!! All other v4.1 & v5.0 clients download ok from their respective http://vsphereclient.vmware.com/vsphereclient/.... links, it's only v4.1U3 that does not. Smacks of someone within VMware not uploading the client to correct place....
Agreed.  The link does not work. Please can someone @VMware check this out?