[Work Item] HealthChecker + HybridAgent

[johage]

Describe the work
Trying to add functionality to check for Hybrid Agent usage in Exchange Hybrid scenario.

Additional Context
So far it seems we have a few ways to check this: (Credit to Dylan Stetts)
$Servers = Get-ExchangeServer | ? {$_.ServerRole -notlike "Edge"}
$array = @()
foreach($server in $servers)
{
# Installed Programs location
$UninstallKey=”SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall”

# Create an instance of the Registry Object and open the HKLM 
$reg=[microsoft.win32.registrykey]::OpenRemoteBaseKey(‘LocalMachine’,$server.name) 

# Open subkeys for uninstalled programs
$regkey=$reg.OpenSubKey($UninstallKey) 

# Retrieve an array of string that contain all the subkey names
$subkeys=$regkey.GetSubKeyNames() 

# Open each Subkey and use GetValue Method & map server name & Key name
foreach($key in $subkeys){
    $thisKey=$UninstallKey+”\\”+$key 
    $thisSubKey=$reg.OpenSubKey($thisKey) 
    $obj = New-Object PSObject
    $obj | Add-Member -MemberType NoteProperty -Name “ExchangeServer” -Value $server.Name
    $obj | Add-Member -MemberType NoteProperty -Name “DisplayName” -Value $($thisSubKey.GetValue(“DisplayName”))
    $array += $obj
} 

}

$array | ? { $_.DisplayName -like "Hybrid Service"} | select ExchangeServer, DisplayName

According to our documentation we can also check this file path where the HybridAgent has been installed:
*\Program Files\Microsoft Hybrid Service*
https://learn.microsoft.com/en-us/exchange/hybrid-deployment/hybrid-agent#option-2-get-status-via-the-hybrid-management-powershell-module

[bill-long]

It might be easier to run Get-Service to find any Exchange Servers running the Hybrid Agent.

However, apparently it is common to install the Hybrid Agent on something that is not an Exchange Server. In that scenario, there's no realistic way to detect Hybrid Agent without reaching out to Azure with global admin creds.

[johage]

I think this is where we can check to see if it IS installed on Exchange servers, but the real fix would be the thing I assumed would just fail that would be getting HybridAgent added to the Get-HybridConfiguration output. Will discuss getting this WorkItem submitted with @nasir ***@***.***> when normal business hours resume tomorrow! Thanks, Josh Hagen Exchange Technical Advisor Tier 3 Business hours: 8:00AM-8:00PM Central Microsoft Exchange 701.492.6842 Working hours: Monday-Friday 7:00-4:00PM Central I am committed to providing excellent service and I value your feedback. I welcome comments about what I did right, as well as suggestions for how I can continue to improve my service in the future. Microsoft is committed to providing world-class service, so your input regarding the entire support process is highly valued. Please send your comments to me or my manager Travis Hedrick ***@***.******@***.***>) Exchange 2013 has reached End of Life as of April 11, 2023. If you want to see more information on this click here - https://docs.microsoft.com/en-us/microsoft-365/enterprise/exchange-2013-end-of-support?view=o365-worldwide#what-does-end-of-support-mean Exchange 2010 has reached End of Life as of October 13, 2020 please review this link if you have questions about this - https://docs.microsoft.com/en-us/microsoft-365/enterprise/exchange-2010-end-of-support?view=o365-worldwide

…

________________________________ From: Bill Long ***@***.***> Sent: Friday, February 16, 2024 2:36 PM To: microsoft/CSS-Exchange ***@***.***> Cc: Author ***@***.***> Subject: Re: [microsoft/CSS-Exchange] [Work Item] HealthChecker + HybridAgent (Issue #2005) It might be easier to run Get-Service to find any Exchange Servers running the Hybrid Agent. However, apparently it is common to install the Hybrid Agent on something that is not an Exchange Server. In that scenario, there's no realistic way to detect Hybrid Agent without reaching out to Azure with global admin creds. — Reply to this email directly, view it on GitHub<#2005 (comment)> or unsubscribe<https://github.com/notifications/unsubscribe-auth/AI5EASFOT2EPMVQPJT6EKLTYT67MZBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDONZTGEYTCNBXG6SG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJSHA2TMMRYGYYTRAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDEMJTHA4DINBYGU4YFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZDONZTGEYTCNBXG6TXI4TJM5TWK4VGMNZGKYLUMU>. You are receiving this email because you authored the thread. Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.