jwood8,
Change type from 'Repairing this issue requires downloading a patch' to 'This issue can be repaired without downloading a patch' -- this setting is generally only used to download the patch content to your core server's patch folder, not actually to the client system for installation. Hence why it is labeled "Manufacturer's patch URL". For any self created patches, best practice is to use Additional Files. After that is set to 'This issue can be repaired without downloading a patch' [from a vendor], go under Additional Files and select the file you wish to download (e.g. your batch file) and generate the file hashes.
Then in your "Patch install commands" simply tell it to "Execute a program":
PATH = "%AdditionalFile0%"
This will then execute the file you told it to download - no need to move it to another location either because that variable will automatically detect it.
You could also instead of dealing with a batch file being hosted and downloaded - simply do this:
1. Change the "Execute a program" to "Run script"
2. Click "Insert example script" -> "Batch file"
e.g. you will get something like this:
EXTERNAL APPLICATION
exe=cmd.exe
args=/c %filename%
filename=repair.bat
echo off
echo Vulscan logs all standard output. It looks for the special strings 'succeeded', and 'message'.
echo If 'succeeded' is not found, then vulscan uses the return value to determine success (zero means succeeded).
echo the core name is %corename%
echo the local cache directory location: %sdmcache%
echo succeeded=true
echo message=batch file was repairing
3. Add the contents of your batch file to this script in place of where the red text is. Then you can manage the script from directly with-in the patch and compliance window rather than dealing with a file on a share.
Hope this helps - let me know if you need any assistance,
Peter