From 038742d872909068ff1384489d06c0679303f180 Mon Sep 17 00:00:00 2001
From: Chris <aldershotchris@googlemail.com>
Date: Tue, 26 Sep 2017 14:53:08 +0100
Subject: [PATCH] Update VMware.VMEncryption.psm1

Example for Get-Help was using $SetVMEncryptionKey rather than SetVMDiskEncryptionKey ($ sign and other command used)
---
 Modules/VMware.VMEncryption/VMware.VMEncryption.psm1 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Modules/VMware.VMEncryption/VMware.VMEncryption.psm1 b/Modules/VMware.VMEncryption/VMware.VMEncryption.psm1
index 8d19b50..e91b0c5 100644
--- a/Modules/VMware.VMEncryption/VMware.VMEncryption.psm1
+++ b/Modules/VMware.VMEncryption/VMware.VMEncryption.psm1
@@ -1034,7 +1034,7 @@ Function Set-VMDiskEncryptionKey {
        C:\PS>$KMSCluster = Get-KMSCluster | select -last 1
        C:\PS>$VM = Get-VM -Name win2012
        C:\PS>$HardDisk = get-vm $vm|Get-HardDisk
-       C:\PS>$HardDisk|$Set-VMEncryptionKey -VM $VM -KMSClusterId $KMSCluster.Id -Deep
+       C:\PS>$HardDisk| Set-VMDiskEncryptionKey -VM $VM -KMSClusterId $KMSCluster.Id -Deep
 
        Deep rekeys all the disks of the $VM  using a new key.
        The key is generted from the KMS whose clusterId is $KMSCluster.Id.