Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Update for script version 2.1

...

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

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

...

opa0 mode preparation

If the combination of username/password is used there is no need for configuration.If or an encrypted file is used to store the password (.clixml) then as specific has to be defined for the "SYSTEM" (service account) user.

Execute the same operations as described in chapter "Using opa0" or "Using expect" to create theĀ file containing the encrypted password.

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:

...

C:\WINDOWS\system32>whoami

nt authority\system

(warning) Give a different name to the clixml file than the one used for tests and setup the "clixmlsys" parameter, there is no need for configuration.

rsh mode preparation

Warning

A proxy has to be defined at OpenVMS level hence the local "system" user must be specified. This user name is translated depending on the language of the Windows distribution.

It is then highly recommended to install an English version of Windows to avoid issues with accents and non standard characters when creating this proxy.

...