I am starting to have a sporadic and random issue where a user reboots their VDI (agent 5.3.2), and is then unable to access it because the Windows Firewall Service is not starting Automatically like it is set to do. I have the service set to Started and Automatic in the template. In order to start the service so that the user can access their VDI, I have to go in through the console. Sometimes I even have to restart the Guest through Console to gain access. After restarting the Guest and accessing the machine through the Console, the Windows Firewall Service will sometimes be started.
As an update, I can "Reset Desktop" from the View Client and about 50% of the time, the VDI will come up successfully. The other 50% will be connection timeout errors where the Firewall didn't start.
Attached are two Event errors that I am receiving and seeing that in my mind are associated with this issue.
Edit: Was unable to fix the problem via Service changing in the template or following some Event Logs about Superfetch, etc etc. But I did add the Firewall Service to Start in GPO and have now rebooted the VDI 10 times with successful Firewall starts. Not sure if it is a bug or some sort of weird Template configuration, but either way, I found a work around solution.