1. Sign out and close the Workplace app. 2. After you attempt to fix the issue, restart your computer.
3. Sign in to Workplace and wait for the compliance checks to finish processing. 3. If you are still having an issue after following the directions below, contact your IT department.
The Screensaver failed compliance checks indicate the user account on the device used to access Frontline does not have a screensaver enabled, the wait time for the screensaver is not acceptable or the screensaver does not require a password on resume. This compliance check is to ensure that if someone physically gains access to your computer they cannot get into your account when you are away from your device.
To resolve this issue, ensure the user account has a screensaver enabled, adjust the wait time to an acceptable value and require a password when resuming work.
Windows
Windows 10
Follow the steps below to access the screen saver settings or click here.
- Click on the Start menu.
- Click Settings.
- Click Personalization.
- Click Lock screen.
- Scroll down and click Screen saver settings.
- Select a screen saver.
- Set the Wait time according to your firm's compliance policy.
- Check the option On resume, display logon screen.
Windows 8.1
Follow the steps below to access the screen saver settings or click here.
- Right-click on the desktop and click Personalize.
- Click Screen saver.
- Select a screen saver.
- Set the Wait time according to your firm's compliance policy.
- Check the option On resume, display logon screen.
macOS
- Click the Apple menu.
- Click System Preferences or click here.
- Click Desktop & Screen Saver.
- Click on the Screen Saver tab.
- Select a Screen Saver.
- Verify Start after is set according to your firm's compliance policy.
- Click the back button to return to System Preferences.
- Click Security and Privacy or click here.
- Check the option Require Password after sleep or screensaver begins.
You may be required to enter an administrative password.
- Select immediately from the dropdown.
- Select immediately from the dropdown.
Other setting configurations
If there are settings configured, other than screensaver, that prevent access to a device via password such as Power & Sleep settings, the Screensaver check will continue to fail until the screensaver is configured. If a user sets their device to automatically Sleep and/or Hibernate, or if they wish to have the screen automatically turn off via Power settings, and they want to pass the screensaver check, they must configure a screensaver to start within a timeframe established by the set policy.