14.1 Technical requirements, downloading, etc.
14.1.1 Minimum PowerShell Version Required
The GDPRSCAN requires (on Windows) at least PowerShell Version 3.0 on the machine from which it will be executed. PowerShell 5.x or greater is preferred. For Linux and MacOS, you should install the latest version of PowerShell Core, which at this writing is 7.1.2.
14.1.2 PowerShell Execution Policy (Windows)
Note that the Microsoft Windows version of PowerShell has a default execution policy of “Restricted”, that is, PowerShell accepts only interactive commands and will not run scripts. Typically this results in an error something like the following:
PS E:\listserv\main> .\gdprscan.ps1
.\gdprscan.ps1 : File E:\listserv\main\gdprscan.ps1 cannot be loaded because running
scripts is disabled on this system. For more information, see about_Execution_Policies
At line:1 char:1
+ CategoryInfo : SecurityError: (:) , PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess
In order to run the GDPRSCAN script, you must do one of two things:
- If you are running PowerShell from a standard Windows “run as administrator” command prompt, you can bypass the default execution policy by adding “-ExecutionPolicy Bypass” to the command, like this:
E:\LISTSERV\MAIN>PowerShell -ExecutionPolicy Bypass -File .\gdprscan.ps1
- If you are running GDPRSCAN in a PowerShell console, you will need to elevate the execution policy level for the CurrentUser scope to at least “RemoteSigned”. This can be done as follows:
PS E:\listserv\main> Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
You will be prompted to ensure that this is really what you want to do.
14.1.3 Downloading the script and associated files
The script is available for download from http://download.lsoft.com/downloads/gdprscan/gdprscan.zip and comes bundled with copies of LCMD.EXE, LCMDX.EXE, and the source code for LCMDX (lcmdx.c) for users' convenience. (We don't provide an executable copy of lcmdx for Linux/MacOS, because it's usually best to compile and link the code locally against your existing libraries. We'll provide instructions for doing that below.)
- LISTSERV change-logging is NOT enabled by default. Change-logging MUST be enabled in LISTSERV in order to provide changelog reports. For information on how to set up the system-level changelog, see this link. For information on how to set up list-level changelogs, see this link.
- For Windows, a reasonably-recent version of PowerShell (5.x or later is preferred). For Linux or MacOS users, the latest version of PowerShell Core should be used.
- LISTSERV 16.5 or later, with a build date of 9 Apr 2018 or later, is required in order to run changelog reports. Earlier builds will produce a message in the XML stating that changelog reports cannot be run because the installed LISTSERV version does not support them.
- LISTSERV POSTMASTER-level access is required to run the comprehensive, server-level reports.
- List owners may use the script to run reports against lists they own. However, such a report may not fully meet the GDPR criteria if the target address is subscribed to lists on the server which are not owned by the script invoker.
Customers with paid-up LISTSERV maintenance may obtain help and report problems with the script by emailing firstname.lastname@example.org.