Forum Discussion
No Heartbeat on Session Host after shutdown
I have same issues on Application Pool and Desktop Pool. Agent is running perfectly until first connection and First reboot, after that Agent is in NoHeartBeat Status on WVD
I found this Warning in EventViewer on my Virtual Machine wvd-dev-30
Microsoft.RDInfra.Monitoring.AgentMonitoringService.AgentMonitoringServiceWorker
Fail to set default dimensions Invalid Operation: Fail to set default dimensions, error code is 2147942487.. Error code is 80070057
Do you have any case on this error ? do you need more information ?
Matthieu
MicrosoftMrossi : Thanks for bringing this up! At the moment, I'm unaware of similar cases. Can you file a support ticket for Windows Virtual Desktop through the Azure Portal? This will help us better triage and dive into this.
Christian_Montoya : Perhaps I found issue did you have any network requirement ? Like URL ?
My customer use Proxy and I think I need to white list some Windows Virtual Desktop URL.
I did not found any URL list for this service in documentation.
Matthieu
- Christian_Montoya
Mrossi : Yes, we have our service URLs listed under here that you would need to whitelist: https://docs.microsoft.com/azure/virtual-desktop/overview#requirements . Hope that helps!
I found something in WVD Agent.
When Agent start it read this Key in reg :
DefaultConnectionSettings REG_BINARY
in : Computer\HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Internet Settings\Connections\
In my customer environment this key is overload by ZScaler Proxy configuration but Agent don't care about new configuration and still continue to use old configuration.
If I delete this setting and restart Agent, status change to Available value.
Do you know if if possible to set Agent proxy setting at this installation or use system proxy configuration ?
for information ZScaler Agent inject loopback proxy configuration in Windows 10 settings but this configuration is not use by Agent
Best Regards,
Matth
Thx Christian, Will open case on Azure Portal just for information I have 2 environments:
- One Lab without any GPO Sandbox
- One Test With my customer GPO
This can be a starting root cause 🙂
Matthieu