This repository has been archived by the owner on Dec 6, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 121
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Update SCOM MI readme with new features and setup instructions
- Loading branch information
Showing
3 changed files
with
42 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
# Introduction to SCOM Managed Instance | ||
|
||
In this module, you will learn about SCOM Managed Instance (SCOM MI) and how it differs from SCOM. | ||
|
||
## What is SCOM MI? | ||
|
||
SCOM MI is a new deployment option for System Center Operations Manager (SCOM) that allows you to run SCOM in Azure. SCOM MI is a managed service that is fully managed by Microsoft. This means that Microsoft is responsible for the infrastructure, availability, and performance of the SCOM MI service. You are responsible for configuring and managing the SCOM MI service. | ||
|
||
## Diagram | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,5 +1,15 @@ | ||
# Setup | ||
|
||
## Pre-requisites | ||
|
||
### Network requirements | ||
|
||
Simpler diagram | ||
|
||
- SCOM MI requires a virtual network in Azure. This virtual network must have a gateway subnet and a virtual network gateway. The gateway subnet must be at least /29 and the virtual network gateway must be a VPN gateway. | ||
- The virtual network must have a DNS server configured. This DNS server must be able to resolve the SCOM MI domain name. | ||
|
||
|
||
|
||
https://learn.microsoft.com/en-us/system-center/scom/tutorial-create-scom-managed-instance?view=sc-om-2022 | ||
|