Page Comparison

...

1.  Create a batch file and test to make sure it produces the desired result (i.e., it launches AGRIS and runs a report stream). For the purposes of this article, let's say that command line has already been created successfully.

   1. Example file name:  AGRIS-RS-004.BAT

   2. Example file contents:  C:\Apps\AGRIS\bin\SysMenu.exe /D001 /Uusr /Ppassword /L200 /R04

2. Modify the file extension (or make a copy of the batch file with a new file extension) so that the file is a .TXT instead of a .BAT

   1. Example AGRIS-RS-004.BAT --> AGRIS-RS-004.TXT

3. To convert the plain text commands to an encrypted string, open PowerShell and execute these 4 commands:

   1. NOTE:  Replace "C:\Apps\AGRIS-RS-004.TXT" with the path and filename of the TXT containing the AGRIS command line info.

   2. NOTE:  Replace "C:\apps\AGRIS-RS-004-Encrypted.TXT" with the path and filename where the encrypted info will be stored. 

$Code = Get-Content C:\Apps\AGRIS-RS-004.TXT

...

4. Next, create a PS1 script that will execute the encrypted commands:

   1. BEST PRACTICE:  Add a remark statement to the script that indicates what the script does since it won't be clear otherwise. 

      1. To add a remark, put a # symbol at the start of a line and anything that follows on that same line will be identified as a remark.

      2. Recommendation would be is to add the original plain text command as a remark and then remove the password value. 

      3. It is helpful to leave the User ID in place to know what account the script will use to sign into AGRIS. 

   2. BEST PRACTICE: Incorporate identifiers into the name of the script to help differentiate various scripts.

      1. Example:  AGRIS-RS-004.PS1

...

6. Save the updated PS1 script. 

7. Execute PS1 and verify that it produces the desired outcome.  If it does, then automate this script as desired. 

8. Once the PS1 script has been validated and is running as expected, the original batch file and output file generated in Step #3 can be deleted, modified, archived, etc.  The only file needed moving forward is the one created in Steps #3 - 6.

Credit to Brien Posey:

https://www.itprotoday.com/powershell/secure-sensitive-information-powershell-scripts-encryption

...