To schedule a custom update script, click Browse to locate the script. The custom script will appear in the text window. Custom scripts should be tested by running the Schedule Software Updates feature.

Custom scripts must be written so that they return only after actions in the custom script have been completed. For example, if a script launches another process and returns immediately, the Schedule Software Updates feature will not detect the operation of the custom script process and may assume that the script has completed. This can result in partially updated files or failure of your custom script.

If a custom script update on a Windows SteadyState computer requires any resources during a scheduled update, such as a valid network connection, the resource must be available at the time of the update.

Write permissions for custom scripts are only available to the users in the Administrators group on the computer. Local Machine accounts and other user accounts do not have write permissions for custom scripts.

Custom script updates that are scheduled automatically in Windows SteadyState will run after Microsoft updates and antivirus updates have been performed.

Windows SteadyState supports custom scripts written in .exe, .vbs, .cmd, and .bat file formats.

Note IconImportant:
Custom scripts can only be used with the Schedule Software Updates feature if they do not require any interaction from you.

Caution IconCaution:
Any users logged onto the computer when scheduled updates begin will be immediately logged off. While scheduled updates are in progress, only the Administrator or users with administrative privileges can log on. We recommend that you not log on while updates are in progress; however, if you do so, you will not be able to modify any configurations made with Windows SteadyState until the update process is complete.

See Also