Skip to content

Commit 9ecbde1

Browse files
author
Manika Dhiman
committed
Resolved merge conflict
2 parents a7b2ca3 + dd3a8dc commit 9ecbde1

File tree

31 files changed

+9
-20
lines changed

31 files changed

+9
-20
lines changed

azure-stack/hci/manage/add-server.md

Lines changed: 0 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -98,11 +98,6 @@ On the new server that you plan to add, follow these steps.
9898

9999
1. Install the operating system and required drivers on the new server that you plan to add. Follow the steps in [Install the Azure Stack HCI, version 23H2 Operating System](../deploy/deployment-install-os.md).
100100

101-
> [!NOTE]
102-
> If your cluster is using a dedicated Network ATC intent for storage, and you are using custom storage IPs, you must configure the IPs on the storage network adapters before adding the new server.
103-
> If your cluster is using a shared network ATC intent for storage and other traffic type like compute and management, you will need to manually configure the IPs on the storage virtual network adapters after the server is added to the cluster.
104-
105-
106101
2. Register the server with Arc. Follow the steps in [Register with Arc and set up permissions](../deploy/deployment-arc-register-server-permissions.md).
107102

108103
> [!NOTE]

azure-stack/hci/manage/manage-arc-virtual-machines.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ ms.author: alkohli
66
ms.topic: how-to
77
ms.service: azure-stack
88
ms.subservice: azure-stack-hci
9-
ms.date: 09/09/2024
9+
ms.date: 09/13/2024
1010
---
1111

1212
# Manage Arc VMs on Azure Stack HCI
@@ -15,7 +15,6 @@ ms.date: 09/09/2024
1515

1616
This article describes how to manage Arc virtual machines (VMs) running on Azure Stack HCI, version 23H2. The procedures to enable guest management, start, stop, restart, pause, save, or delete an Arc VM, are detailed.
1717

18-
1918
## Prerequisites
2019

2120
Before you begin, make sure to complete the following prerequisites:
@@ -34,10 +33,11 @@ There are two agents that are important to understand in the context of guest ma
3433

3534
When you enable guest management on an Arc VM, the guest agent installs the [Azure Connected Machine agent](/azure/azure-arc/servers/agent-overview). The Azure Connected Machine agent enables you to manage Azure Arc VM extensions on your Azure Stack HCI VM.
3635

37-
Based on whether a guest agent is running on your Arc VM, the steps to enable guest management are different.
36+
Here are some key considerations for enabling guest management on a VM after provisioning it:
3837

39-
> [!IMPORTANT]
40-
> Make sure that your Azure Stack HCI cluster is running 2311 or later to run this procedure.
38+
- Make sure that your Azure Stack HCI cluster is running 2311 or later.
39+
- Enabling guest management after VM provisioning isn't supported for Windows Server 2012 and Windows Server 2012 R2.
40+
- The steps to enable guest management differ based on whether a guest agent is running on your Arc VM.
4141

4242
### Verify if guest agent is running
4343

azure-stack/hci/manage/monitor-hci-multi-azure-policies.md

Lines changed: 4 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ ms.reviewer: saniyaislam
77
ms.topic: how-to
88
ms.service: azure-stack
99
ms.subservice: azure-stack-hci
10-
ms.date: 07/30/2024
10+
ms.date: 09/12/2024
1111
---
1212

1313
# Enable Insights for Azure Stack HCI at scale using Azure policies
@@ -37,8 +37,7 @@ Before applying this policy, keep in mind the following things:
3737
- This policy is applicable only to Azure Stack HCI, version 22H2 clusters. Apply it before any other policies to ensure AMA picks up the correct resource ID.
3838
- Uninstall AMA before applying this policy to set the correct resource ID. If AMA isn't uninstalled first, data might not appear. For more information, see [Uninstall AMA](/azure/azure-monitor/agents/azure-monitor-agent-manage?tabs=azure-portal#uninstall).
3939

40-
<details>
41-
<summary><b>Expand this section to see the policy definition in JSON.</b></summary>
40+
Here's the policy definition in JSON:
4241

4342
```json
4443
{
@@ -455,7 +454,6 @@ Before applying this policy, keep in mind the following things:
455454
}
456455
}
457456
```
458-
</details>
459457

460458
### Policy to install AMA
461459

@@ -465,8 +463,7 @@ The policy to install AMA performs the following functions:
465463

466464
- Installs AMA on clusters that aren't compliant with the policy through a remediation task.
467465

468-
<details>
469-
<summary><b>Expand this section to see the policy definition in JSON.</b></summary>
466+
Here's the policy definition in JSON:
470467

471468
```json
472469
{
@@ -544,7 +541,6 @@ The policy to install AMA performs the following functions:
544541
}
545542
}
546543
```
547-
</details>
548544

549545
### Policy to configure DCR association
550546

@@ -555,8 +551,7 @@ This policy is applied to each server in the Azure Stack HCI cluster and perform
555551
> [!NOTE]
556552
> This policy doesn’t create Data Collection Endpoint (DCE). If you're using private links, you must create DCE to ensure there's data available in Insights. For more information, see [Enable network isolation for Azure Monitor Agent by using Private Link](/azure/azure-monitor/agents/azure-monitor-agent-private-link).
557553
558-
<details>
559-
<summary><b>Expand this section to see the policy definition in JSON.</b></summary>
554+
Here's the policy definition in JSON:
560555

561556
```json
562557
{
@@ -643,7 +638,6 @@ This policy is applied to each server in the Azure Stack HCI cluster and perform
643638
}
644639
}
645640
```
646-
</details>
647641

648642
## Enable Insights at scale using Azure policies
649643

767 Bytes
Loading
1.48 KB
Loading
1.68 KB
Loading
14.5 KB
Loading
-50.7 KB
Loading
-2.64 KB
Loading
-11.3 KB
Loading

0 commit comments

Comments
 (0)