Contents

Principle

Using the "Local Group Policy Editor", it is possible to add the execution of a Powershell script at Windows shutdown. As this operation is performed with the "system" account, some operations have to be performed depending on the method chosen (opa0, rsh or ssh).

opa0 mode preparation

If the combination of username/password is used, there is no need for configuration change.

If an encrypted file is used to store the password using the "cryptedpsys" parameter, it must be created on a session as "system" account.

To do so, open a cmd.exe window as Administrator and run the following command:

A new window will popup. To check you're connected as "system", run:

Run the following command to create the encrypted file:

Example:

Run the Powershell script in check mode:

then check the "OPA0 was successful" message is displayed followed by "Command successfully completed."

rsh mode preparation

Execute the same operations as described in chapter "Using rsh" for Tru64 or VMS to enable remote connection for the "SYSTEM" user.

This is case sensitive so for Tru64, specify "SYSTEM" and not "system" in the .rhosts file

It is highly recommended to test the execution of the script in check mode while connected as "system" account. To do so, use the psexec.exe program file provided in the kit or download it from the Microsoft Sysinternals page.

Open a cmd.exe window as Administrator and run the following command:

A new window will popup. To check you're connected as "system", run:

Run the Powershell script in check mode:

then check the "RSH was successful" message is displayed followed by "Command successfully completed."

ssh mode preparation

Execute the same operations as described in chapter "Using ssh" for Tru64 or VMS to create a key pair with "SYSTEM" user with a different identity file.

To do so, use the psexec.exe program file provided in the kit or download it from the Microsoft Sysinternals page.

Open a cmd.exe window as Administrator and run the following command:

A new window will popup. To check you're connected as "system", run:

Create a new ssh trust as described in the "Using ssh" chapter.

Run the Powershell script in check mode:

then check the "SSH was successful" message is displayed followed by "Command successfully completed."

Windows settings - Local group policy

Adding the script to the shutdown Powershell scripts

Open the "Local Group Policy Editor" (run gpedit.msc) and go to the Shutdown script setup:

Select the "Powershell Scripts" tab, click on the "Add..." button, specify the path to the charon_cleanshutdown.ps1 script and its parameters:

Display instructions in shutdown scripts as they run

It is recommended to enable the display instructions during shutdown to check the Charon Legacy OS shutdown is correctly performed.

Open the "Local Group Policy Editor" (run gpedit.msc) and go to the "Computer Configuration" → "Administrative Templates" → "System" → "Scripts" setup:

Enable this functionality and optionally leave a comment:

Specify maximum wait time for Group Policy scripts

By default the script executed at Windows shutdown have a default timeout of 10 minutes (600 seconds). It is possible to change this value in case the shutdown takes more time.

Open the "Local Group Policy Editor" (run gpedit.msc) and go to the "Computer Configuration" → "Administrative Templates" → "System" → "Scripts" setup:

Enable this functionality, define the new timeout and optionally leave a comment:

Windows shutdown example

This example is given for a Windows 10 Professional version running Charon-AXP V4.10 B202-03. The emulated Alphaserver is a DS20 running OpenVMS 8.4:

The PowerShell window is displayed during Windows shutdown thanks to the enabled "Display instructions in shutdown scripts as they run" feature and the putty / OPA0 window is opened thanks to the "openconsolecmd" and "openconsolearg" parameters in the .ini file.