Virtual Apps and Desktops – VDAs will remain turned off after Restart Schedule

Mike,
One possible solution would be to create a function that perform those tasks. Then call the function passing, in my case, the Desktop Group name as parameter . I this way you can perform these operation against the Desktop Groups that you interested in monitoring. You should explore the various Get-BrokerDesktop options to see if you can gather a collection of VDAs that make sense to you, then put that collection on the foreach cycle.

Here I created the function
Function CheckingVDAPoweredOff ($DesktopGroupName)
{Write-Host “Checking VDAs DesktopGroupName $DesktopGroupName”
$VDAs = Get-BrokerDesktop -DesktopGroupName $DesktopGroupName -RegistrationState Unregistered -PowerState Off -InMaintenanceMode $false | Select HostedMachineName

if($VDAs -ne $null)
{
foreach($VDA in $VDAs)
{Write-Host “$($VDA.HostedMachineName) was powered off. Booting up the machine….”
try
{
New-BrokerHostingPowerAction -MachineName $VDA.HostedMachineName -Action TurnOn | Out-Null
$BrokenVDA++
}
catch
{
Write-Host “E” “Problem with turning on the VDA: $($VDA.HostedMachineName)”
Write-Host “I” “Exiting Script…..”
exit 1
}

Write-Host “Waiting for 15 seconds before starting the next VDA….”
Sleep 15
}
}

else {Write-Host “All VDAs are registered. Nothing to do…..”}
}

#here I am setting the desktop Group name that I want to check
$DesktopGroupName = “APPS01”

#Here I am calling the function passing the Desktop Group Name
CheckingVDAPoweredOff $DesktopGroupName

$DesktopGroupName = “APPS02”
CheckingVDAPoweredOff $DesktopGroupName