Update Create-ZertoRole.ps1

Corrected the format of the Propagate switch of the New-VIPermission example command. Removed the $true variable and used a boolean value of 1, for true.
This commit is contained in:
ryan-zerto
2022-01-31 16:42:32 -07:00
committed by GitHub
parent 08a90a98b8
commit 9d15bf7cb8
+2 -2
View File
@@ -39,7 +39,7 @@ if (New-VIRole -name $RoleName -Privilege $VMwarePrivileges)
Write-Host "NOTE: After this, you can go into vCenter GUI and assign the service account the ZVM will use to this role and place it at the top level of vCenter."
Write-Host " Or if you wish to do via PowerCLI, here's an example command to use:"
Write-Host
Write-Host " e.g., New-VIPermission -Role `"Zerto - Least Privilege Service Account Role`" -Principal `"vsphere.local\svc-zerto`" -Entity (Get-Folder Datacenters) -Propagate:$true"
Write-Host " e.g., New-VIPermission -Role `"Zerto - Least Privilege Service Account Role`" -Principal `"vsphere.local\svc-zerto`" -Entity (Get-Folder Datacenters) -Propagate 1"
Write-Host
Write-Host " In this example, an existing account (svc-zerto@vsphere.local) is assigned the newly created role at the vCenter top-level, with propogation to all children."
Write-Host " Please consider the appropriate action for your environment based on your own internal security and management guidelines."
@@ -47,4 +47,4 @@ if (New-VIRole -name $RoleName -Privilege $VMwarePrivileges)
else {
Write-Host "ERROR: Could not create role -" $roleName
Write-Host " Check your permissions to create a role and if the name already exists."
}
}