Skip to content

Commit f950ff0

Browse files
committed
Slight text changes
1 parent fb217d8 commit f950ff0

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

defender-endpoint/linux-deploy-defender-for-endpoint-using-golden-images.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ ms.collection:
1515
ms.topic: install-set-up-deploy
1616
ms.subservice: linux
1717
search.appverid: met150
18-
ms.date: 09/01/2025
18+
ms.date: 09/02/2025
1919
---
2020

2121
# Deploy Microsoft Defender for Endpoint on Linux using golden images
@@ -73,15 +73,16 @@ This guide walks you through:
7373
mdatp health
7474
```
7575

76-
After you've successfully deployed Defender on the golden image, there is no need to deploy it separately on each virtual machine clone.
76+
> [!NOTE]
77+
> Once Defender is successfully deployed on the golden image, there's no requirement to install and onboard it individually on each cloned machine.
7778
7879
## Step 2: Prepare the golden image for cloning
7980

80-
Before making a snapshot of the virtual machine, follow these steps to ensure that each virtual machine clone gets a unique hardware UUID:
81+
Before making a snapshot of the virtual machine, ensure that each virtual machine clone gets a unique hardware UUID, as described in the following sections.
8182

8283
### On-premises machines
8384

84-
For on-premises virtual machines, make sure that the golden image generated from it is configured in such a way that when it is cloned, each virtual machine clone will have a unique hardware UUID.
85+
For on-premises machines, make sure to configure the golden image so that each clone gets a unique hardware UUID.
8586

8687
If you're using **KVM/libvirt** or **VMware/Hyper-V** as the virtualization platform, it's recommended to use the following instructions:
8788

0 commit comments

Comments
 (0)