Sometimes the HostedMachineID of Citrix does not match that of VmWare. This is often the case when cloning or moving machines. In Citrix Studio you will see the Powerstate of this machines as unknow and you can’t do any VM actions like reboot in the console.
With this script snippet it can be checked. To do this the variable “Broker” must be adjusted in the Script and the PowerCli and CitrixModule (BrokerSnapIn) must be loaded. Furthermore, the connection to the vCenter must be initiated via “Connect-VIServer vCName“.
#25.09.2019by J.Kühnis - Verfiy HostedMachineID with VmWare ESXi Hypervisoer
$Broker = "Enter your BrokerName"
$Brokermachines = Get-BrokerMachine -AdminAddress $Broker | Select MachineName,DNSName,HostedMachineID
Foreach ($Machine in $Brokermachines){
IF(get-vm $Machine.DnsName -ErrorAction SilentlyContinue){
IF($Machine.HostedMachineID -eq (Get-View -id (get-vm $machine.DNSName).id).config.uuid){
Write-Host $Machine.DnsName "HostedMachineID is matching" $Machine.HostedMachineId -ForegroundColor Green
}Else{
Write-host $Machine.DnsName "Mismatch ID: VmWare UUID =" (Get-View -id (get-vm $machine.DNSName).id).config.uuid "; Citrix HostedMachineID =" $Machine.HostedMachineID -ForegroundColor Yellow
}
}Else{
Write-host $Machine.DnsName "MachineName not Found on ESXi" -ForegroundColor Yellow
}
}
Now that the machines have been read out, the connections can be fixed.
vCenter Cert thumbprint update:
# Open an admin POSH console, load the Citrix Modules (asnp citrix*) and cd to XDHyp:/Connections and run ls. Check the SSLThumbprints entry.
asnp citrix*
cd XDHyp:/Connections
ls
With the command Get-VMHost you can read values such as the current memory consumption or the total number memory of a host. But I didn’t find a way to read out the value of the allocated memory of the subobjects (the VMs).
Here is an example of how this can be done. The script outputs a list of all hosts. In the attribute “AllocatedVMMemoryGB” you can see how much memory has been over-provisioned or it shows how much memory you could still use.
With this script one or more servers can be deleted from the Citrix DeliveryController (Citrix Studio) and from the ESXi/vCenter.
To use The Script some variables and values need to be adjusted like the name of the Citrix DeliveryController and vCenter. Vmware (PowerCLI) and Citrix (SDK) powershellmodules need to be installed.
This only works if the VM name is identical to the Worker Server DNS name. If this is the case, the following string can be deleted in the script [-replace “.FQDN.address”,””]
In my case, the name of the VM is only the “hostname” of the machine and not the DNSname. So the script removes the FQDN name, in order to use the script successfully, this must also be adjusted.
This script changes the vLan name of each network adapter within a vCenter.
The script works with PowerCLI (tested with version 6.0 /6.5).
The following variables should be adjusted in the script.
$vcserver = “Specify FQDN.of.vcenter.”.
$VPGName = “Specify the current vLan name”.
$VPGNameNew = “Specify the new vLan name”.
# by Jeremias Kühnis
#check if vmware modules are loaded
function checkmodule {
If (!(Get-PSSnapin * | where { $_.Name -eq 'VMware.VimAutomation.Core'})) {Add-PSSnapin *}
if (-not (Get-PSSnapin -Name 'VMware.VimAutomation.Core')) {
write-host "VMWare PSSnapin is not loaded - PSSession/Windows will be closed in 10 seconds" -backgroundcolor "Yellow" -ForegroundColor "red"
sleep 10
exit
}
else{
Write-Host "VMWare PSSnapin loaded" -ForegroundColor "Green"
}
}
# VCenter you are connecting too
function connectserver{
$vcserver= 'any.vCenter.FQDN'
Connect-VIServer $vcserver
}
function renamevpg{
# Change VirtualPortGroup / VLANS
$VPGName = 'XD_2011' # Variable Vlan
$NewVPGName ='XD_2011_new'#Variable new VLAN Name
#Set the name of the "Standard-Virtual Switch"
$VPG = Get-VirtualPortGroup -Name $VPGName
Set-VirtualPortGroup -VirtualPortGroup $VPG -Name $NewVPGName
Start-Sleep 30
# Loop to make changes to new Network Adapter
ForEach ($adapter in (Get-NetworkAdapter * | where {$_.NetworkName -eq $VPGName})){
Set-NetworkAdapter -NetworkAdapter $adapter -NetworkName "$NewVPGName" -Confirm:$false
Write-Host $adapter
}
}
checkmodule
connectserver
renamevpg
This script allows you to restart an array of servers trough PowerCLI.
You will be prompted to specify your ESXi-Host /vCenter Environment. Ensure that you enther the FQDN.
The script will reboot your servers without confirmation.
#13.11.2018 Restart a list/array of Servers through vCenter/Powercli
IF(!(Get-Module vm* | where { $_.Name -eq 'VMware.VimAutomation.Core'})){
(Get-Module –ListAvailable VMware.VimAutomation.Core | Import-Module)
if (-not (Get-Module -Name 'VMware.VimAutomation.Core')){
Write-Warning "Could not find/load 'PowerCLI Module. Ensure that you are running this Script on Server with PowerCLI."
return
}
}
Write-Host "####################################" -ForegroundColor Yellow
$vCenter = Read-Host -prompt "Please enter the Name of your ESXi Host or vCenter"
Connect-VIServer $vCenter
$server = @(
# Enter Servernames here -> Equivalent to the Name of the VM-Target
"Hostname-Server1"
"Hostname-Server2"
"Hostname-Server3"
)
foreach ($server in $server){
try{
Restart-VM -VM $server -Confirm:$false
write-host "Reboot OK $server" -ForegroundColor Green
}catch{
write-host "Reboot NOT OK $server" -ForegroundColor yellow
}
}
Disconnect-VIServer -Server $vCenter -Confirm:$false
