So I have a Windows (Windows Server 2019 Datacenter Version 1809) (US East) set up on MS Azure, work's perfectly, & has great latency for what I need & I have no technical faults with the product.
To save costs, I have Runbook which is connected to a schedule which shuts down my VM overnight - again, all works perfectly.
The issue I have, however, is when the VM is started up by my Runbook, the third-party application I have running on said VM doesn't start unless I physically log into the VM first thing in the morning, surely the idea of a VM is that it should be relatively "hands off" and that any application or function (which I do have included in my "Startup Apps" window) should just run without the need for the user needing to login?
I do know that clicking the "X" at the top of the screen keeps the VM running & that's not the issue, it's just the initial logging in, after the VM has started back up after the night before, that is needed to be achieved in order for the application to actually function.
So my question to you is: is there a way to not need to physically login to my VM every morning for the Application to actually start?
The Error Logs I'm getting are the following:
*The attempt to connect to the RPCSS service was denied access for the COM Server application C:\windows\system32\logman.exe to the user Unavailable\Unavailable SID (S-1-5-18) running in the application container Unavailable SID (Unavailable). The most likely cause is that the machine wide Access Limits do not grant the user or application local access permissions. The Access Limits can be modified using the Component Services administrative tool.
The WinRM service is not listening for WS-Management requests.
*User Action
If you did not intentionally stop the service, use the following command to see the WinRM configuration:
winrm enumerate winrm/config/listener
Crash dump initialization failed!**
