Skip to content
This repository has been archived by the owner on Dec 6, 2024. It is now read-only.

Commit

Permalink
Merge branch 'scommidocs' of https://github.com/Azure/FTALive-Sessions
Browse files Browse the repository at this point in the history
…into scommidocs
  • Loading branch information
josefehse committed Apr 16, 2024
2 parents d1cd4ef + d7c4b38 commit 6806c67
Show file tree
Hide file tree
Showing 3 changed files with 11 additions and 6 deletions.
Binary file added content/management/scom-mi/SCOMMIAgents.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added content/management/scom-mi/SCOMMIAgents.vsdx
Binary file not shown.
17 changes: 11 additions & 6 deletions content/management/scom-mi/agents.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,12 +18,17 @@ The following are the supported monitoring scenarios:
- On-premise Windows & Linux agent VMs that have Line of sight connectivity to Management Server.
- On-premises Windows agents with no Line of sight connectivity (must use managed Gateway) to Azure

Note:
## Diagram

![alt text](SCOMMIAgents.png)

- Linux VMs in Azure and Linux VMs that sit behind a gateway are not currently supported.
- Agent multi-homing isn't supported to multiple SCOM Managed Instances. However, it can have a multi-home configuration for on-premises System Center Operations Manager and a SCOM Managed Instance.
- Agents that are directly connected to the SCOM MI need to be able to reach <region>.workloadnexus.azure.com on port 443.
- .NET 4.7.2 and TLS 1.2 is required for agent install.
>[!NOTE]
>
>- Linux VMs in Azure and Linux VMs that sit behind a gateway are not currently supported.
>- Linux VMs in Azure and Linux VMs that sit behind a gateway are not currently supported.
>- Agent multi-homing isn't supported to multiple SCOM Managed Instances. However, it can have a multi-home configuration for on-premises System Center Operations Manager and a SCOM Managed Instance.
>- Agents that are directly connected to the SCOM MI need to be able to reach region.workloadnexus.azure.com on port 443.
>- .NET 4.7.2 and TLS 1.2 is required for agent install.
## Managed Gateways

Expand All @@ -32,7 +37,7 @@ Managed Gateways need to be Arc-enabled with the Gateway extension installed, it
Note:

- Currently, multi-homing for gateway servers isn't supported.
- Arc-enabled Gateways require line of sight to <region>.workloadnexus.azure.com on port 443.
- Arc-enabled Gateways require line of sight to region.workloadnexus.azure.com on port 443.
- Initial authentication is performed by a managed identity, then certificates are used to manage Managed Gateways by Microsoft.

#### [Previous](setup.md) | [Home](readme.md) | [Next](newfeatures.md)

0 comments on commit 6806c67

Please sign in to comment.