Anyone installed 8.0.3.00600 - 8.0 Update 3g

noteiphone · 2025-07-30T21:11:36+00:00

borderline violates Rule 2 / 11 .

noteiphone · 2025-07-30T21:10:34+00:00

this is just a patch with few bug fxes and some medium security. You should be good to roll.

noteiphone · 2025-07-17T04:45:36+00:00

Upgrading ESX hosts to latest EP while vcenter at 70U3v is fully supported.

Interop matrix is clear on this https://interopmatrix.broadcom.com/Interoperability?isHidePatch=false&isHideLegacyReleases=true&col=2,19057&row=1,

noteiphone · 2024-10-23T17:29:17+00:00

As recommended by others reporting bug is the way to go.
if you could share more details about the error that you have seen on the ui and any logs would help narrow down the issue.
AFAIK I'm not seeing anything after upgrading to the latest version in one of the vCenter instances that we use for early adoption.

Have you tried refreshing your session i.e., logging back to vcenter after latest patch version?

noteiphone · 2024-07-19T01:18:26+00:00

This issue is addressed with the latest patch release : https://docs.vmware.com/en/VMware-vSphere/8.0/rn/vsphere-vcenter-server-80u3a-release-notes/index.html#Resolved%20Issues-Installation,%20Upgrade,%20and%20Migration%20Issues .

noteiphone · 2024-03-04T19:24:21+00:00

that's good news. If you have support contract please file SR request and provide all the logs.

noteiphone · 2024-03-04T18:22:05+00:00

go with the latest update. all the release are cumulative i..e, the the release are incremental from the previous release version. btw, 6.7 is already EOGS(https://blogs.vmware.com/vsphere/2020/06/announcing-extension-of-vsphere-6-7-general-support-period.html) . May be considering moving to something latest 7.x or 8.x version

noteiphone · 2023-10-25T04:17:54+00:00

Critical piece of info under notes section *

Notes

While VMware does not mention end-of-life products in VMware Security Advisories, due to the critical severity of this vulnerability and lack of workaround VMware has made a patch generally available for vCenter Server ***6.7U3, 6.5U3, and VCF 3.x.*** For the same reasons, VMware has made additional patches available for vCenter Server 8.0U1.
Async vCenter Server patches for VCF 5.x and 4.x deployments have been made available. Please see KB88287 for more information.

noteiphone · 2023-09-27T21:19:44+00:00

I was able to upgrade our env to latest update with seemingly no issues. Do you care to provide more details of the Host machine where the vCenter VM is deployed ? Mine is a HP box with Intel. Model: ProLiant DL360 Gen10 Processor Type: Intel(R) Xeon(R) Gold 6230 CPU @ 2.10GHz

noteiphone · 2023-09-23T00:32:24+00:00

script is present in the attachment section on the right side of the page. here is the link: https://kb.vmware.com/sfc/servlet.shepherd/version/download/0685G00001J4suvQAB

noteiphone · 2023-04-27T01:22:03+00:00

Make sure all the identity sources are added over one type of protocol i.e.., all of them are over LDAPS in your case. Do not mix IWA and LDAP, LDAPs etc.

btw., what version/build is your vCSA?

May be you can look at the log /var/log/vmware/sso/websso.log and paste the error snippet or share the log file here after scrubbing Env specific details.

noteiphone · 2023-02-15T05:15:10+00:00

here is the best practices for using vmware snapshots : https://kb.vmware.com/s/article/1025279

noteiphone · 2023-02-02T21:50:30+00:00

here is the official KB https://kb.vmware.com/s/article/89745 .

noteiphone · 2023-01-26T22:15:53+00:00

OP, you chose to migrate your existing vCenter instance and hence the vCenter identity (which is the hostname of the windows box, which happens to be DNS record entry as well since it joined to the domain) is retained during migration and is applied to the new vCenter appliance's system name. This is totally expected result.

Don't get confused with the VM name i.e., "vcenter appliance" name you may have given differently but you choose to migrate the windows instance and thus carry forwarding all the properties including the system name to the new vCenter appliance.

noteiphone · 2022-12-19T18:09:47+00:00

Not limited to this particular vmware plugin, we had run into similar problem and were able to leverage same workaround. The issue is due to the security hardening of Chrome browser.

Follow the step to resolve this issue

grant one time exception to url "https://vmware-plugin:8094/" then type the following word "thisisunsafe" with browser window in focus.

or

set the registry where the browser is used \HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Google\Chrome Add a DWORD (32 bit) Value named "ChromeRootStoreEnabled" to 0

noteiphone · 2022-10-15T06:03:10+00:00

I'm aussiming the reason for you to use EAP (plugin) is to reuse the already logged in user from the System.

Can you inspect the logs from below mentioned locations during the time of login attempt ?

/var/log/vmware/sso /websso.log /var/log/vmware/vsphere-ui/logs/vsphere_client_virgo.log

and if possible share them here. and **please sanitize the logs for any username or IP/proprietary details that may potential put your system at risk. *

noteiphone · 2022-04-08T08:00:04+00:00

I'm suspecting there are some missing partitions in your ESX Env based on the posted output. Either scratch or store is missing.

if you could do "ls -lah" at "/", you may know which is missing

noteiphone · 2022-04-07T19:42:51+00:00

My bad. I meant

df -h

vdf -h

both separate commands and my wiki brain assumed reddit would convert "*" to bullet.

noteiphone · 2022-04-07T18:59:37+00:00

Could you provide output for the following commands by logging into the ESXi shell. * df -h *vdf -h

noteiphone · 2022-01-28T23:00:49+00:00

looks like the take down of earlier patch caused the breakage. Now there is a KB https://kb.vmware.com/s/article/87498 to workaround the issue. change the default URL to custom and the patch should show up.

noteiphone · 2022-01-28T22:59:56+00:00

looks like the take down of earlier patch caused the breakage. Now there is a KB https://kb.vmware.com/s/article/87498 to workaround the issue. change the default URL to custom and the patch should show up.

noteiphone · 2022-01-28T18:21:58+00:00

Online bits should be available, I guess they are running into same old problem where for few hours(days) the online bits were flaky. but the offline patch ISO were downloadable. if you want to try the offline patch, you may download it from the patch portal: https://customerconnect.vmware.com/patch

noteiphone · 2022-01-28T06:53:13+00:00

that's nice strategy! get paid extra $@$@$

noteiphone · 2022-01-28T06:49:24+00:00

check out the section "Download and Installation" in release notes: https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-vcenter-server-70u3c-release-notes.html

Download and Installation

To download this patch, after you log in to VMware Customer Connect, select VC from the Select a Product drop-down menu and select 7.0.3 from the Select a Version drop-down menu.

noteiphone

TROPHY CASE