Power Management and Session State

Overview

This test case validates the power management features of the zTC, which are crucial for enterprise energy savings and security compliance. It confirms that devices can correctly enter and resume from a low-power suspend state, be woken remotely by an administrator, and adhere to scheduled power policies.

The test also verifies security-related features like the inactivity screen lock. A successful outcome demonstrates that a fleet of zTC devices can be managed efficiently to reduce power costs and ensure that unattended terminals remain secure.

zTC/zMAN Configuration

All power management policies and schedules are configured centrally through the zMAN Director.

1. Create a Power Management Policy:
   • Log into the zMAN Director UI.
   • Navigate to Device Settings -> Settings.
   • Click ADD SETTINGS and create a new configuration named Standard-Power-Policy.
   • In the configuration window, select the Power Management section.
   • Tick the checkboxes to.
2. Create an End-of-Day Power Schedule:
   • Navigate to Device Settings -> Power Schedule.
   • Click ADD POWER SCHEDULE.
   • Give the schedule a name, such as End-of-Day Suspend.
   • Set the power option like Shutdown/ Suspend/ Reboot and submit it.

Operation to Suspend.

1. • Set the schedule

Type to Run Recursive, select the desired days (e.g., Monday-Friday), and set a time (e.g., 7:00 PM)³.

1. • Save the power schedule.
2. Apply Policies to the zTC:
   • Select the settings and select the device/devices/groups.
   • Apply Power schedule to selected devices.

3rd Party Setup

• Wake-on-LAN (WoL) Utility: You will need a separate computer on the same network as the zTC with a WoL tool installed. This tool will send the “magic packet” required to wake the device.
• VDI Session: Have a standard VDI session active during the tests to ensure session state is preserved correctly through suspend and resume cycles.

Execution

1. Test Manual Suspend/Resume:
   • With an active VDI session running on the zTC, go to the local

Start menu -> Power -> Suspend⁴.

1. • Wait for the device’s LED indicator to show it is in a low-power (sleep) state.
   • Wake the device by pressing a key on the keyboard or tapping the power button.
2. Test Scheduled Suspend:
   • Set the End-of-Day Suspend schedule in zMAN to a time a few minutes in the future.
   • Leave the zTC powered on with an active session and observe it at the scheduled time.
3. Test Wake-on-LAN:
   • Put the device into a suspended state (either manually or by using an “Immediate” suspend command from zMAN)⁵⁵⁵⁵.
   • Go to your other computer on the same network.
   • Use the WoL utility to send a magic packet to the zTC’s MAC address.
4. Test Inactivity Screen Lock:
   • Log in to the zTC and leave it idle at the SnapOS desktop.
   • Do not touch the mouse or keyboard.
   • Wait for the configured timeout period (15 minutes in this test case) to pass.

Verification

• Suspend and Resume (Pass/Fail):
  • PASS: The device correctly enters the low-power suspend state. Upon waking, the SnapOS desktop and the VDI session are restored exactly as they were, fully responsive and without errors.
  • FAIL: The device fails to enter suspend mode, freezes during the process, or crashes upon waking. The VDI session is disconnected or the entire OS requires a reboot.
• Scheduled Suspend (Pass/Fail):
  • PASS: At the time specified in the zMAN Power Schedule, the zTC device automatically and cleanly enters the suspend state.
  • FAIL: The device does not enter the suspend state at the scheduled time and remains fully powered on.
• Wake-on-LAN (Pass/Fail):
  • PASS: Within a few seconds of the magic packet being sent, the suspended zTC device powers on and boots the OS without any physical interaction.
  • FAIL: The device does not respond to the magic packet and remains in its suspended state.
• Inactivity Screen Lock (Pass/Fail):
  • PASS: After 15 minutes of inactivity, the SnapOS screen automatically locks, requiring user credentials to regain access.
  • FAIL: The screen remains unlocked indefinitely, posing a security risk for unattended terminals.