MicrosoftDocs
diff --git a/‎azure-stack/hci/manage/manage-arc-virtual-machines.md
Lines changed: 5 additions & 5 deletions b/‎azure-stack/hci/manage/manage-arc-virtual-machines.md
Lines changed: 5 additions & 5 deletions
diff --git a/‎azure-stack/user/azure-stack-storage-connect-se.md
Lines changed: 0 additions & 2 deletions b/‎azure-stack/user/azure-stack-storage-connect-se.md
Lines changed: 0 additions & 2 deletions
diff --git a/‎azure-stack/user/media/azure-stack-network-howto-backup-replicator/image2.png
-40.9 KB b/‎azure-stack/user/media/azure-stack-network-howto-backup-replicator/image2.png
-40.9 KB
diff --git a/‎azure-stack/user/media/azure-stack-network-howto-backup-replicator/image6.png
-33.3 KB b/‎azure-stack/user/media/azure-stack-network-howto-backup-replicator/image6.png
-33.3 KB
diff --git a/‎azure-stack/user/media/azure-stack-network-howto-vnet-to-vnet-stacks/image13.png
13 KB b/‎azure-stack/user/media/azure-stack-network-howto-vnet-to-vnet-stacks/image13.png
13 KB
diff --git a/‎azure-stack/user/media/azure-stack-network-howto-vnet-to-vnet/image13a.png
-2.3 KB b/‎azure-stack/user/media/azure-stack-network-howto-vnet-to-vnet/image13a.png
-2.3 KB
diff --git a/‎azure-stack/user/media/azure-stack-solution-template-service-fabric-cluster/image5.png
-9.7 KB b/‎azure-stack/user/media/azure-stack-solution-template-service-fabric-cluster/image5.png
-9.7 KB
diff --git a/‎azure-stack/user/media/azure-stack-storage-connect-se/add-certificate-azure-stack.png
-137 KB b/‎azure-stack/user/media/azure-stack-storage-connect-se/add-certificate-azure-stack.png
-137 KB
diff --git a/‎azure-stack/user/media/event-hubs-quickstart-cluster-portal/2-view-cluster-create-namespace.png
-945 Bytes b/‎azure-stack/user/media/event-hubs-quickstart-cluster-portal/2-view-cluster-create-namespace.png
-945 Bytes
diff --git a/‎azure-stack/user/media/event-hubs-quickstart-cluster-portal/2-view-cluster-with-namespace.png
-198 Bytes b/‎azure-stack/user/media/event-hubs-quickstart-cluster-portal/2-view-cluster-with-namespace.png
-198 Bytes
@@ -6,7 +6,7 @@ ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-stack
 ms.subservice: azure-stack-hci
-ms.date: 09/09/2024
+ms.date: 09/13/2024
 ---
 
 # Manage Arc VMs on Azure Stack HCI
@@ -15,7 +15,6 @@ ms.date: 09/09/2024
 
 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.
 
-
 ## Prerequisites
 
 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
 
 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.
 
-Based on whether a guest agent is running on your Arc VM, the steps to enable guest management are different.
+Here are some key considerations for enabling guest management on a VM after provisioning it:
 
-> [!IMPORTANT] 
-> Make sure that your Azure Stack HCI cluster is running 2311 or later to run this procedure.
+- Make sure that your Azure Stack HCI cluster is running 2311 or later.
+- Enabling guest management after VM provisioning isn't supported for Windows Server 2012 and Windows Server 2012 R2.
+- The steps to enable guest management differ based on whether a guest agent is running on your Arc VM.
 
 ### Verify if guest agent is running
 
 
@@ -49,8 +49,6 @@ Export and then import Azure Stack Hub certificate for disconnected integrated s
 
 4.  Under **Console Root\Certificated (Local Computer)\Trusted Root Certification Authorities\Certificates** find **AzureStackSelfSignedRootCert**.
 
-    ![Load the Azure Stack Hub root certificate through mmc.exe](./media/azure-stack-storage-connect-se/add-certificate-azure-stack.png)
-
 5. Right-click the certificate, select **All Tasks** > **Export**, and then follow the instructions to export the certificate with **Base-64 encoded X.509 (.CER)**.
 
     The exported certificate will be used in the next step.