We are having strange problem that end-users not able to connect disconnected session after 30 min short break and while connecting back to the desired desktop getting error message " cannot start desktop <desktop name >" and this only happen to specific user with CWA version 22.5.0.18 & 22.3.1.41 ( tested as of now )
Please refer the below screenshot from not working user Protocol : changed from HDX to console and client IP address changed : loopback IP address .
Platform info :
MCS workload are hosted on Azure platform
Installed VDA Version: 2203.0.0.33220
Operating System: Windows 10
Policy
Session ideal :60 min
Session disconnect : 2 hours
Not working screenshot
Working user screenshot taken before connecting disconnected session
Question
nishanthpro.five
We are having strange problem that end-users not able to connect disconnected session after 30 min short break and while connecting back to the desired desktop getting error message " cannot start desktop <desktop name >" and this only happen to specific user with CWA version 22.5.0.18 & 22.3.1.41 ( tested as of now )
Please refer the below screenshot from not working user Protocol : changed from HDX to console and client IP address changed : loopback IP address .
Platform info :
MCS workload are hosted on Azure platform
Installed VDA Version: 2203.0.0.33220
Operating System: Windows 10
Policy
Session ideal :60 min
Session disconnect : 2 hours
Not working screenshot
Working user screenshot taken before connecting disconnected session
Link to comment
2 answers to this question
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now