Thanks to the help I received from the previous post with the same title...I got brave and used the allvolumesattached.bat file.
It didn't work as anticipated.
Where would I find logs to troubleshoot if the batch file was called, did the execution fail, etc.
The batch file runs:
regedit.exe /s C:\F9V5\F9.reg
Normally the information is posted in the svservice.log file in the C:\Program Files (x86)\CloudVolumes\Agent\Logs.
You can actually see if the .bat file is being executed. I'm not quite sure if it actually shows an error if something in the file itself is misconfigured.
And just out of curiosity, you are executing a reg file, where is that located??
You could try and replace that with a regadd command and import the reg keys like that. The question is if the reg file actually is available at that time.
Thank you.
I will check those logs.
I added the .reg to a folder in the app stack.
I added the command to the allvolumesattached.bat, my assumption is that this gets called when all volumes are attached...including the one that the reg hack is located in.
Update - No update.
Putting out fires of a different nature, haven't had a chance to test suggestions.