Still fresh in mind after delivering a great FMA Internals Power management session @ E2EVC in Berlin (thanks for having us Justin, a.k.a. Alex Juschin!!) with my good friend and FMA Internals Co-op co-founder Bas van Kam, I’m going to take a quick look at one of the topics we covered on the day: the Extended Disconnect Power Policy settings hidden DEEP within the XenDesktop/FMA SDK.
OK, so maybe that’s a tad dramatic, but you get the picture (no ominous music here or anything like that).
Note: you’ll need the SDK and a smidgen of PoSH experience to follow on.
For those of you that didn’t get the chance to see me and Bas (The FMA Internals Co-op) present live and experience, in living color, the pure awesomeness that is E2EVC, fear not! All is not lost. You can join in the revelry and catch up by heading over to http://www.basvankaam.com/ right now. It’ll be almost like being there. Yes, really.
Per usual, Bas did a great job with his post, sharing the slides and his thoughts on the topic itself as well as our little announcement.
The FMA Internal Co-op:
“A co-operation between a seasoned Citrix veteran and an established community blogger and Citrix enthusiast. Which is sort of a unique combination as far as we know.” – Bas van Kam
Extended Disconnect Power Policy settings
Designed (wait–inhale deeply–this is a bit of a mouthful, so you might have to read this through a couple of times) to control the actions to be performed after a second extended and configurable period of a user session disconnecting in peak and off-peak hours, extended disconnect power policy settings along with the standard disconnect policy settings, to allow administrators to apply multistage power policy rules such as initially suspending a machine shortly after a session disconnect occurs, and then later power off the machine if the session has not been reconnected.
For the purpose of this blog, I’m going to keep it very simple (my previous passage notwithstanding) and run through a quick step-by-step process of how to configure these super-funky power policy settings.
Training Win8 (Pooled Static) Delivery Group
Step 1: Configure a standard disconnect policy setting through Citrix Studio against the Training Win8 Delivery Group
During Peak Hours
When disconnected: 5 mins
Step 2: Configure an extended disconnect policy setting through PoSH against the same Training Win8 Delivery Group
Set-BrokerDesktopGroup –Name “Training Win8” –PeakExtendedDisconnectAction Shutdown –PeakExtendedDisconnectTimeout 10
Observations Within XenCenter:
After being disconnected for 5 mins: The Win8VM will suspend
After being disconnected for a further 5 mins: The Win8VM will shutdown
Note: The extended disconnect setting timer starts from the initial disconnect and not after the initial disconnect action has taken place. For this reason. The Win8VM shutsdown 10 mins after the session has been disconnected and NOT 15 mins.
There you have it. Short and to the point. Who knew digging deeper and unearthing some advanced Power mgmt would be such fun!
Until next time, Keep it FMA!!!
Mick Glover (aka XD Tipster “Rocking XenDesktop since 2008”)
Senior Readiness Specialist,
Worldwide Support Readiness [EMEA]
Citrix Systems, Inc