Seems the MSIAfterburneragent is not auto-started by AwesomeMiner in 3.2.6 version. I believe this used to work (not sure now) in past version. My Awesome miner remote agent starting up fine on all 3 of my miners but all 3 now no longer auto start the MSI afterburner agent. I have confirmed under Options the command line to executable. Once I manually start up MSI afterburner agent on each node, my Awesomeminer can manage the MSI afterburner settings through the console.
Is this known problem with 3.2.6 beta release?
There are no changes to Afterburner autostart in any of the development versions. Can you clear the settings in the Options dialog, MSI Afterburner section, for:
Auto start path
Username
Password
Then click OK. Then you go back and fill in those 3 fields again. Are the settings applied?
Did not fix the issue. I now have 4 miners all running AwesomeMiner agent but this Afterburner Remote Agent is not auto starting on any of the 4 miners. Again i have confirmed the command line points to the correct .exe and directory, the security key is correct and port is correct. I can confirm that manually making changes in Awesome Miner console to GPU settings does work--they do update to each remote miner so the communications are working, just not the autostart of the MSIafterburnerremoteagent itself. I tried adding MSIafterburner remote agent to my shell:startup in Windows but for some reason this doesn't actually run/start the remote agent (other items in my shell:startup directory start up automatically).
The complexity here, which is also the reason why it fails when you manually try this from Windows startup, is that the MSI Afterburner Remote Server (and their UI app) must be running as Administrator. This is fully possible to do with some configuration using Task Scheduler, and that's what Awesome Miner is trying to setup. A stanard Startup-folder solution is not working. It would be great if the Afterburner software had built-in support for auto-starting properly, but that isn't available.
The username you specified in the Options dialog of Awesome Miner must be the same username you are logged on to on the remote computer where you run your mining and Awesome Miner Remote Agent. It shouldn't be some other account like the Administrator. You probably checked this already, but I just want to confirm. I've also updated the guide on the web site about these settings in the Options dialog:
http://www.awesomeminer.com/help/gpuclocking.aspxWhat you can look at on the remote computer is the log file for Awesome Miner Remote Agent, that can be accessed if you right-click on the icon and select Log File. Look for "Setting MSI Remote Server path" and then it should say Register Task successful or failed.