...

Principle

TO BE COMPLETED

expect mode preparation

→ noneUsing 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 if the chosen mode is "rsh" or "ssh".

There is no specific operation to perform if "expect" mode is selected.

rsh mode preparation

→ add "SYSTEM" user in proxy/VMS or .rhosts/Tru64    "SYSTEM" not "system"

...

Warning
A proxy has to be defined at OpenVMS level hence the local "system" user must be specified. This user is translated depending on the language of the Windows distribution. It is then highly recommended to install a English version of Windows to avoid issues with accents and non standard characters when creating this proxy.

Execute the same operations as described in chapter "Using rsh" for Tru64 or VMS but 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:

C:\WINDOWS\system32>C:\Charon\psexec.exe -i -s cmd.exe

...

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

C:\WINDOWS\system32>whoami nt authority\system

The run the Powershell script in check mode:

C:\WINDOWS\system32>powershell -file c:\charon\charon_cleanshutdown.ps1 -config c:\charon\myds20vms.ini -check

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

Note
It is recommended to move the psexec.exe program file to a secured folder or to remove it when it is no more needed (check completed)

ssh mode preparation

→ use "psexec.exe -i -s cmd.exe" to run as local "system" account to create the ssh trust (keys)

...