World of EUC

Asking this question here because I'm getting a ton of different responses and want to see what people's assumptions are. 
For a Non Persistent Win 11 pooled random delivery group, if the power state is unknown, would you expect to be able to connect to it if it is registered? 

Yes, because power state of unknown means your DDC or CC can't communicate with the hypervisor, but registered means the VDA on the win 11 machine is reporting in to the DDC, and it must be booted for that to happen.  Solution.... Fix your hosting connection.   You can run Get-ProvVmInUnknownPowerState to determine the root cause.

So you would expect to be brokered to it?

I’m not looking for solutions just what you think happens in that scenario, you get brokered or not 

same, I'd expect connections as long as they're registered

I was always under the impression that power state unknown would prevent sessions from being brokered to the VDA but seen it in real world recently with power state unknown and sessions can be brokered to them

I have a customer where they aren't brokered at all when power state is unknown and I always assumed that was normal and related to shut down after use, but I've had so many people tell me recently that connections should still broker to them I wanted to hear what other people thought 

Dated article... but

<https://support.citrix.com/external/article/CTX318027/brokering-to-power-state-unknown-vdas.html|Brokering to Power State Unknown VDAs>

&gt; Virtual Apps and Desktop Servers (VDAs) with Power State Unknown are considered by the broker for session brokering, albeit at a lower priority than VDAs with known power states. In a deployment with VDAs in both known and unknown power states – the Broker will prefer VDAs in the following order: 
&gt; 1.  VDAs in power state ON 
&gt; 2.  VDAs in power state OFF 
&gt; 3.  VDAs in unknown power state

And server OS doesn't have shutdown after use 

We are doing this for a years, W10-W11 no connection with Hypervisor due to restrictions in our fully automated vmware solution where we are unable to get proper rights. PowerState Unknown, we set daily reboots, all is working fine eiter with pooled or personal VDI's.

Ok so it sounds like something is definitely not working correctly for this customer then, thanks everyone 

I just labbed it out in 2507 and to my surprise it connected me just fine with an unknown power state. 

defo NO - if power is unknown, you can't broker to it, very silly but that's the way it has been for me on-prems with XenServer.

I wonder if it changed because it was always my assumption that it would not broker 