You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -104,7 +104,7 @@ Run the `Set-VMStoragePolicy` cmdlet to modify vSAN-based storage policies on a
104
104
Run the `Set-LocationStoragePolicy` cmdlet to Modify vSAN based storage policies on all VMs in a location where a location is the name of a cluster, resource pool, or folder. For example, if you have 3 VMs in Cluster-3, supplying "Cluster-3" would change the storage policy on all three VMs.
105
105
106
106
> [!NOTE]
107
-
> You cannot use the vSphere Client to change the default storage policy or any existing storage policies for a VM.
107
+
> You can't use the vSphere Client to change the default storage policy or any existing storage policies for a VM.
@@ -140,14 +140,18 @@ Run the `Set-ClusterDefaultStoragePolicy` cmdlet to specify default storage poli
140
140
|**Timeout**| The period after which a cmdlet exits if taking too long to finish. |
141
141
142
142
1. Check **Notifications** to see the progress.
143
+
> [!NOTE]
144
+
> Changing the default cluster policy will only affect new VMs. Existing VMs will retain the policy they're currently configured/deployed with.
143
145
144
146
## Create custom AVS storage policy
145
147
146
148
Run the `New-AVSStoragePolicy` cmdlet to create or overwrite an existing policy.
147
149
This function creates a new or overwrites an existing vSphere Storage Policy. Non vSAN-Based, vSAN Only, VMEncryption Only, Tag Only based and/or any combination of these policy types are supported.
148
150
> [!NOTE]
149
-
> You cannot modify existing AVS default storage policies.
151
+
> You can't modify existing AVS default storage policies.
150
152
> Certain options enabled in storage policies will produce warnings to associated risks.
153
+
> Modifying existing storage policies will make existing associated vsan objects (vms/vmdks/iso/etc) appear as 'out of compliance'.
154
+
> This simply means existing objects are running against premodified policy settings. Reapply storage policy to objects to update to match modified policy settings.
0 commit comments