Windows 10: Remote Desktop Services - Timeout issue with no available logs

Hi,


We have a RDS environment set up which up until last week was able to create collections successfully, both pooled and personal, now unfortunately each collection creation seems to fail after hanging on the installation part for a very long time. The machines get created on the virtual host hyper-v along with their necessary files and whilst you can access the virtual machine through there it is not accessible through the gateway.


We have tried to enable DeploymentUILog files but they are not appearing so i am not sure if this has changed for the 2019 environement. The error that appears is "Failed: The VMHostAgent service times out while waiting for the newly provisioned virtual desktop to start"


I know there are some previous mentions regarding stale DHCP entries but i am unable to locate these so if someone could guide me in the right direction that would be most helpful.


Thanks

:)

 

Remote Desktop

Okay guys need some help here before going crazy...
I am trying to setup a remote desktop connection and see exactly what the logged on user is looking at with out going through Windows Remote Desktop.

Since its local network I don't have any password or want to setup a password.

Any suggestions are appreciated

 

Remote Desktop Timeout

Hello,

I'm facing an issue with one of my Remote Desktop machines. I have 2 running in my environment in which I thought were identically configured. I have noticed that with one server if a user is idle for 10 minutes the session will lock and present and screen
saver. ( expected behavior). On my other machine, it takes a few hours of idle time before it presents the user with a locked screen. I logged into both machines and let them sit to simulate idle time. I then logged into another machine and ran quser /server:
</servername>. I noticed that the timer for the working server started to calculate the idle time while the other did not. Has anyone experienced this behavior before?

Things I have tried.

• Reboot (a time tested troubleshooting step)
• Patching
• sfc /scannow.
• Verify group policy settings
• Compared local registry settings with the working RDS server.

I'm running Server 2016 Datacenter.

 

remote desktop

Hello,



Thank you for writing to Microsoft Community Forums.



Please help me with the below details to understand your issue in a better way:

1. Are you using the Microsoft remote desktop app?
   

If you are using the Microsoft remote desktop app downloaded from
Microsoft store then, I suggest you to follow the steps to
fix problems with apps from Microsoft Store.



If the issue still persists with the Microsoft remote desktop app, then you can contact the support team by going to the

link and scrolling down to the bottom and clicking on
Microsoft remote desktop support under the Publisher info.



However, if you are using the Remote desktop connection, which comes pre-installed with Windows 10, then I suggest you to please post your question in the
TechNet forum.



Hope it helps.



Prakhar Khare

Microsoft Community - Moderator