Get-VMHostAuthentication | ft VMHost, DomainMembershipStatus
VMHost DomainMembershipStatus ---------- ------------------ vm1.briemle.lab vm2.briemle.lab Ok
Ihre IT in guten Händen
Get-VMHostAuthentication | ft VMHost, DomainMembershipStatus
VMHost DomainMembershipStatus ---------- ------------------ vm1.briemle.lab vm2.briemle.lab Ok
List mounted ISOs:
Get-VM | Get-CDDrive | select @{N="VM";E="Parent"},IsoPath | where {$_.IsoPath -ne $null}
Dismount all ISOs:
Get-VM | Get-CDDrive | where {$_.IsoPath -ne $null} | Set-CDDrive -NoMedia -Confirm:$False
Source: communities.vmware.com
Get-VIPermission -Principal "User/Group name" | FL
Output:
EntityId : Datacenter-datacenter-XXXX Entity : User/Group name Role : Role Name Principal : User/Group name Propagate : True IsGroup : True
There you can see the EntityID / Entity and Principal for the group also the orphand one will show up.
Get-VIPermission -Entity "vm1.briemle.lab" -Principal "briemle.lab\VMware-User" | Remove-VIPermission
Perform operation? Removing permission on entity 'vm1.briemle.lab' for principal 'briemle.lab\VMware-User' and role 'Administrator' [Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help (default is "Y"):
So you can verify the EntityId and delete your orphaned one and ignore the rest.
Source: blogs.vmware.com
The following method should be used to install PowerCLI through the PowerShell gallery for those systems which do not have access to the internet. You will need at least one system that has internet access and a way to move the files to the target computer. While on a system that has internet access, we will find the PowerCLI module with the same command we ran above:
Find-Module -Name VMware.PowerCLI
Then we can download the module for offline consumption with the following command:
Save-Module -Name VMware.PowerCLI -Path C:\Path\To\Desired\Folder
At this point, we’ll want to copy those downloaded folders and place them on the system without internet access in a location where PowerShell can find them, this is the modules folder and can be confirmed by typing $ENV:PSModulePath
at the powershell prompt.
Local User: $home\Documents\WindowsPowerShell\Modules
All Users: $pshome\Modules
Then import the VMware module into your Windows PowerShell:
Import-Module VMware.PowerCLI