Remote Desktop issue

[chris11256]

Hi All,

 

Hoping someone knowledgeable in remote desktop can help. We have a remote desktop host which provide a virtual desktop which staff can access remotely via a gateway.

 

However within the past day or so it's stopped logging people in properly. From windows machine they gets stuck at 'Configuring remote session'. From MacOS it sticks at preparing windows, both do the same thing, just displayed differently.

 

It's not a resource issue or a licence as far as i'm aware, both servers have been beefed up given the current situation.

 

Thanks,

 

Chris

[E_G_R2]

I had an issue where users were getting black screens. One finally said it came up with a disc full message. Had to go in the back end of the server and delete old UVHD hard disk image files using a tool called Sidder.

 

Of course this may not be your problem

[chris11256]

Sadly it's not a disk usage problem. Both the host & broker have over 20GB of free space currently.

[Davit2005]

User Profiles?

 

Can you create a test user and see what the experience is?

Edited March 26, 2020 by Davit2005

[chris11256]

User profiles are local profiles on the host server with all folders redirected to the users H drive.

[Davit2005]

User profiles are local profiles on the host server with all folders redirected to the users H drive.

 

As well as testing with a fresh user is there anything showing in event logs on the server?

 

I have seen profiles in excess of 20Gb before now.

Edited March 26, 2020 by Davit2005

[chris11256]

As well as testing with a fresh user is there anything showing in event logs on the server?

 

I have seen profiles in excess of 20Gb before now.

 

 

I've just made a new test account and the same thing happened.Only error I can find on the Broker is 'Error in the WMI interface to localhost. Check that the machine is running and connected to the network. If the problem persists, reboot the machine. Error Code: 0x8004100A'

 

 

 

Found some UseURCP errors on the host server. I've found a suggested registry edit to make and have scheduled the server to reboot tonight. Will report back in the morning with any progress.