Skip to main content

ESXi Ad Integration: Something to watch out for


dips
Forum|alt.badge.img+7
  • Veeam Legend
  • 808 comments

Hey Folks, 

An interesting configuration issue that recently popped up affecting:

  • VMware vSphere ESXi 7.0
  • VMware vSphere ESXi 8.0

If you have an AD Group called “ESX Admins” in your AD Environment, it is automatically given the VM Admin role when ESXi is joined to the AD domain. 

To mitigate:

  • Config.HostAgent.plugins.hostsvc.esxAdminsGroupAutoAdd from true to false
  • Config.HostAgent.plugins.vimsvc.authValidateInterval from 1440 to 90
  • Config.HostAgent.plugins.hostsvc.esxAdminsGroup from "ESX Admins" to "" 

Resource: https://knowledge.broadcom.com/external/article/369707/

Be safe out there!

13 comments

coolsport00
Forum|alt.badge.img+20
  • Veeam Legend
  • 4139 comments
  • July 30, 2024

Yeah... Saw that yesterday. Thanks for sharing this Dipen.

Out of all my years of using vSphere, I never understood having the Hosts bound to AD 🤷🏼‍♂️


dips
Forum|alt.badge.img+7
  • Author
  • Veeam Legend
  • 808 comments
  • July 30, 2024

Same, never saw the need for it especially when they were managed by vCenter. 

Mitigations are easy to apply anyway without downtime which is one saving grace I suppose.


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8494 comments
  • July 30, 2024

Our VMware team patched this yesterday and never saw it like I usually do before them. 😂


dips
Forum|alt.badge.img+7
  • Author
  • Veeam Legend
  • 808 comments
  • July 30, 2024

They beat you to it @Chris.Childerhose ;) 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8494 comments
  • July 30, 2024
dips wrote:

They beat you to it @Chris.Childerhose ;) 

Yes they did.  😜


Hey, thanks for the headsup! I just double-checked and our ESX hosts are not connected to AD. So I’m not affected, right? Our vCenter is connected to AD, but this is specifically only for the ESX hosts, correct?

Thank you!


dips
Forum|alt.badge.img+7
  • Author
  • Veeam Legend
  • 808 comments
  • July 30, 2024
Leonard.Pieper wrote:

Hey, thanks for the headsup! I just double-checked and our ESX hosts are not connected to AD. So I’m not affected, right? Our vCenter is connected to AD, but this is specifically only for the ESX hosts, correct?

Thank you!

Yes, that is correct. However, it is worth applying the mitigations if you are on all versions prior to ESXi 8.0 U3.


dips wrote:
Leonard.Pieper wrote:

Hey, thanks for the headsup! I just double-checked and our ESX hosts are not connected to AD. So I’m not affected, right? Our vCenter is connected to AD, but this is specifically only for the ESX hosts, correct?

Thank you!

Yes, that is correct. However, it is worth applying the mitigations if you are on all versions prior to ESXi 8.0 U3.

Yeah, actually you’re absolutely right. I just applied the fix to all our ESX hosts. Thanks and have a nice day everybody!


dips
Forum|alt.badge.img+7
  • Author
  • Veeam Legend
  • 808 comments
  • July 30, 2024
Leonard.Pieper wrote:
dips wrote:
Leonard.Pieper wrote:

Hey, thanks for the headsup! I just double-checked and our ESX hosts are not connected to AD. So I’m not affected, right? Our vCenter is connected to AD, but this is specifically only for the ESX hosts, correct?

Thank you!

Yes, that is correct. However, it is worth applying the mitigations if you are on all versions prior to ESXi 8.0 U3.

Yeah, actually you’re absolutely right. I just applied the fix to all our ESX hosts. Thanks and have a nice day everybody!

Welcome, glad we could help :) and welcome to the Community Forums!


Dynamic
Forum|alt.badge.img+10
  • Veeam Vanguard
  • 383 comments
  • July 30, 2024

Thanks for this information @dips. We also would never join an ESXi to the AD. But this behaviour is difficult to understand how such a thing could be intentional. Also i sending your post to my colleagues, to be aware of that. 


dips
Forum|alt.badge.img+7
  • Author
  • Veeam Legend
  • 808 comments
  • July 31, 2024
Dynamic wrote:

Thanks for this information @dips. We also would never join an ESXi to the AD. But this behaviour is difficult to understand how such a thing could be intentional. Also i sending your post to my colleagues, to be aware of that. 

Welcome, glad it was of help.

I have been thinking about why an ESXi host would end up in AD and I think it may be at smaller places where they run just one host or prefer to login to the host via AD authentication. Just a thought


DavideAbrigo
Forum|alt.badge.img+1
  • Experienced User
  • 118 comments
  • July 31, 2024

Quick PowerCLI to change the settings on all hosts in a cluster:

Get-Cluster 'ClusterName' | Get-VMHost | Get-AdvancedSetting -Name 'Config.HostAgent.plugins.hostsvc.esxAdminsGroupAutoAdd' | Set-AdvancedSetting -Value 'false' -Confirm:$false
Get-Cluster 'ClusterName' | Get-VMHost | Get-AdvancedSetting -Name 'Config.HostAgent.plugins.vimsvc.authValidateInterval' | Set-AdvancedSetting -Value 90 -Confirm:$false
Get-Cluster 'ClusterName' | Get-VMHost | Get-AdvancedSetting -Name 'Config.HostAgent.plugins.hostsvc.esxAdminsGroup' | Set-AdvancedSetting -Value "" -Confirm:$false

 


Chris.Childerhose
Forum|alt.badge.img+21
  • Veeam Legend, Veeam Vanguard
  • 8494 comments
  • July 31, 2024
DavideAbrigo wrote:

Quick PowerCLI to change the settings on all hosts in a cluster:

Get-Cluster 'ClusterName' | Get-VMHost | Get-AdvancedSetting -Name 'Config.HostAgent.plugins.hostsvc.esxAdminsGroupAutoAdd' | Set-AdvancedSetting -Value 'false' -Confirm:$false
Get-Cluster 'ClusterName' | Get-VMHost | Get-AdvancedSetting -Name 'Config.HostAgent.plugins.vimsvc.authValidateInterval' | Set-AdvancedSetting -Value 90 -Confirm:$false
Get-Cluster 'ClusterName' | Get-VMHost | Get-AdvancedSetting -Name 'Config.HostAgent.plugins.hostsvc.esxAdminsGroup' | Set-AdvancedSetting -Value "" -Confirm:$false

 

Thanks for sharing that one.  Love using PowerShell for automating things.  😎


Comment