Enabling Desktop Hibernation
Desktop hibernation is an optional cost saving feature that enables desktops and standby instances to be automatically hibernated, or paused, when not in use.
During hibernation, the customer isn't billed for the standard time-based charges associated with the compute instances that host the desktops.
This feature can only be enabled when creating new desktop pools.
Creating a Desktop Pool with Hibernation Enabled
The desktop administrator enables hibernation for the desktop pool when Creating a Desktop Pool.
Use the Desktop management policy settings to define the Secure Desktops Action on inactivity and Action on disconnect. You can specify a grace period (in minutes) for certain actions to control when they occur.
To enable desktop hibernation, select the Stop value for the Action on disconnect setting and then specify a grace period for disconnect (in minutes).
- Once the desktop is created, you can't change these settings.
- You can't modify an existing desktop pool to enable or disable hibernation.
- When hibernation is enabled, you can't specify a regular schedule for the desktop pool. Scheduling options are disabled and the following message is displayed:
Desktop scheduling not available with the selected action.
- When hibernation is enabled, standby instances are automatically stopped (Inactive state in the administrator console).
- Hibernation requires additional storage. When a desktop pool is created with hibernation enabled, the boot volume size for the desktop instance is automatically increased. As a result, this boot volume size might not match the size originally defined in the operating system image.
Desktop Behavior with Hibernation Enabled
With hibernation enabled, when a desktop user exits their desktop client session, the desktop stops and enters hibernation after the specified grace period has elapsed. During hibernation, the complete desktop state is retained and all memory is written to disk.
- In the Secure Desktops administrator console, the desktop indicates an Inactive state.
- If desktop activity occurs during the specified grace period, hibernation doesn't occur.
The next time the desktop user accesses their desktop, the desktop exits hibernation and is automatically restored in its previous running state. All applications are open and running as they were when the desktop was hibernated. All data is preserved on disk or in memory.
- No action is required by the administrator to restore the desktop.
- In the Secure Desktops administrator console, the desktop indicates an Active state.
When a Windows update occurs on the client desktop, there might be a delay in the ability to access the desktop as it applies the update and reboots. This delay can vary depending on the size of the update and the compute shape of the desktop being updated. Also, you might need to restart applications after the reboot.
In Windows 11, The Windows Update page provides the estimated time to update and restart after the update is downloaded. Allow extra time for the client desktop to become accessible. If the delay persists, a Secure Desktops administrator can view status by monitoring the instance console for the desktop compute instance in Oracle Cloud Infrastructure.