Follow these steps to deploy a corporate screensaver created with Ultra Screen Saver Maker or Live Screensaver Creator to the computers in your organization with Group Policy, Configuration Manager (SCCM) or Intune.
1. Create the .scr file
- Click “Create” button.
- In “Save as type” drop-down box select “Screen Saver (*.scr)”.
- Choose folder and enter a file name of up to 8 characters without spaces, e.g. “mysaver”, then click “Save”.
- Click “Open Folder”.
- Double-click the screen saver file to check that it works.
2. Copy the file to every computer
With Group Policy
- Put mysaver.scr in a shared folder, e.g.
\\server\share\mysaver.scr, and give the computer accounts read access to it, e.g. the Domain Computers group. - In Group Policy Management edit a Group Policy Object that is linked to the organizational unit with the computers.
- Go to Computer Configuration > Preferences > Windows Settings > Files, right-click Files and select New > File.
- Set Action to “Update”, Source file(s) to
\\server\share\mysaver.scrand Destination File toC:\Windows\SysWOW64\mysaver.scr, then click OK.
Computers copy the file the next time they apply Group Policy, e.g. after a restart.
With Configuration Manager (SCCM) or Intune
Create a folder, e.g. C:\ScreenSaver, with mysaver.scr and two script files.
install.cmd:
@echo off copy /Y "%~dp0mysaver.scr" "%SystemRoot%\SysWOW64\mysaver.scr" exit /b %errorlevel%
uninstall.cmd:
@echo off del /F /Q "%SystemRoot%\SysWOW64\mysaver.scr" exit /b 0
In Configuration Manager:
- Put the folder on a network share that the site server can read.
- In the Configuration Manager console go to Software Library > Application Management > Applications, click Create Application and select “Manually specify the application information”.
- Add a deployment type of type “Script Installer”. Content location is the folder, Installation program is
install.cmdand Uninstall program isuninstall.cmd. - Detection method: click Add Clause and set Setting type to “File System”, Type to “File”, Path to
C:\Windows\SysWOW64and File or folder name tomysaver.scr. - User experience: set Installation behavior to “Install for system”, Logon requirement to “Whether or not a user is logged on” and Installation program visibility to “Hidden”.
- Deploy the application as Required to a device collection.
In Intune:
- Download the Microsoft Win32 Content Prep Tool, keep it outside the folder and run:
IntuneWinAppUtil.exe -c C:\ScreenSaver -s C:\ScreenSaver\install.cmd -o C:\Output
It creates a file with the .intunewin extension inC:\Output. - In the Microsoft Intune admin center go to Apps > All Apps > Create, select “Windows app (Win32)” and upload the .intunewin file.
- Program: Install command
install.cmd, Uninstall commanduninstall.cmd, Install behavior “System”. - Requirements: Operating system architecture x64.
- Detection rules: select “Manually configure detection rules” and add a rule of type File with Path
C:\Windows\SysWOW64, File or foldermysaver.scrand Detection method “File or folder exists”. - Assignments: Required, to the device groups that should get the screen saver.
3. Turn on the screen saver
With Group Policy and Configuration Manager
Edit a Group Policy Object that is linked to the organizational unit with the user accounts and go to User Configuration > Policies > Administrative Templates > Control Panel > Personalization:
- Enable screen saver: Enabled.
- Force specific screen saver: Enabled, with “Screen saver executable name” set to the full path
C:\Windows\SysWOW64\mysaver.scr. - Screen saver timeout: Enabled, with the number of seconds to wait, e.g. 900 for 15 minutes.
- Password protect the screen saver: Enabled, if users should sign in again when the screen saver ends.
To apply these settings to everyone who signs in on certain computers, link the Group Policy Object to the organizational unit with the computers instead and enable “Configure user Group Policy loopback processing mode” under Computer Configuration > Policies > Administrative Templates > System > Group Policy.
With Intune
- Go to Devices > Manage devices > Configuration > Create > New policy, select Platform “Windows 10 and later” and Profile type “Settings catalog”.
- Click Add settings, search for “screen saver” and select these settings under Administrative Templates > Control Panel > Personalization: Enable screen saver (User), Force specific screen saver (User) and Screen saver timeout (User). Add Password protect the screen saver (User) if users should sign in again when the screen saver ends.
- Enable the settings, enter the full path
C:\Windows\SysWOW64\mysaver.scras the screen saver executable name and set the number of seconds, e.g. 900 for 15 minutes. - Assign the policy to user groups, or to device groups to apply it to everyone who signs in on those devices.
Digitally signed .scr file
If security software in your organization blocks or warns about unsigned programs, select “Digitally Signed Screen Saver (*.scr) with Separate Data (*.dat)” in step 2 of section “Create the .scr file”. It creates two files with the same name, e.g. mysaver.scr and mysaver.dat, and both have to be copied to the same folder:
- Group Policy: add a second file item for mysaver.dat.
- Configuration Manager and Intune: add a second copy line for mysaver.dat to install.cmd and a second del line to uninstall.cmd, both before the exit line.
See screen saver types.
Installation package instead of .scr file
You can deploy “Screen Saver Installation Package (*.exe)” instead of the .scr file. For a screen saver with large videos it is the better choice, because a .scr file unpacks each video to the temporary folder before it plays it.
The package puts the screen saver in C:\Windows\SysWOW64 and its other files in a folder in C:\Program Files (x86). Live Screensaver Creator names both after the package, so mysaver.exe installs mysaver.scr. Ultra Screen Saver Maker names them after “Screen Saver Name”, so keep that name to 8 characters without spaces too.
- Install the package on one computer first and check the names of the installed .scr file and folder. The silent installation command is:
mysaver.exe /verysilent /suppressmsgboxes /norestart
The silent uninstallation command is:
"C:\Program Files (x86)\mysaver\unins000.exe" /verysilent /suppressmsgboxes /norestart
- In Configuration Manager or Intune use these two commands as the installation and uninstall commands, and the installed .scr file in the detection rule.
- Continue with section “Turn on the screen saver”.
Updating the screen saver
To change the screen saver later, create it again under a new name, e.g. mysave2.scr, deploy the new file the same way and change the path in the policy settings. Intune and Configuration Manager do not copy a file again while their detection rule still finds the old one, and the Group Policy “Update” action does not overwrite an existing file.
Troubleshooting
- Double-click
C:\Windows\SysWOW64\mysaver.scron that computer. If it runs, the file is fine and the cause is in the policy settings. - If the computer locks or the screen goes black at the timeout instead of showing the screen saver, check that “Screen saver executable name” holds the full path of a file that exists on that computer.
- On 32-bit Windows use
C:\Windows\System32instead ofC:\Windows\SysWOW64in all steps. - A security warning before the screen saver starts usually means that it runs from a network share. Copy the file to the computer as described in section “Copy the file to every computer”.
- Check that the settings from section “Turn on the screen saver” reach the user. With Group Policy, the Group Policy Object has to be linked to the organizational unit with the user accounts.
- Windows can show (None) as the screen saver even when the policy works. What counts is whether the screen saver starts after the timeout.
- An error about a missing .dat file means that the screen saver was created as the digitally signed type and the .dat file has to be copied next to the .scr file.
- If the screen saver shows the “Unregistered version” message, it was created during the trial. Create it again after you register the program and deploy it as described in section “Updating the screen saver”.
- A screen saver that shows Web pages needs access to those pages from that computer, and it works best with Microsoft Edge WebView2 Runtime, see What browser does Live Screensaver Creator use?
When no one is signed in
The settings above work when a user is signed in. To show the screen saver when no one is signed in, see How to run screen saver when no one is logged in?