Same issue here on W2012 r1, was fine before last update (now at 8.10.1.30).
I notice there is a new menu option under Server, Session Opening preferences. Is there something we need to do in there?
Craig
Search found 5 matches
- Mon Feb 09, 2015 4:27 am
- Forum: Troubleshooting and Problems
- Topic: Long delay before desktop appears at login
- Replies: 4
- Views: 10655
- Thu Oct 16, 2014 12:43 am
- Forum: Troubleshooting and Problems
- Topic: KB2984972 kills RDP
- Replies: 7
- Views: 22107
KB2984972 kills RDP
Please note that a recent security update from MS (Oct 2014) KB2984972 will kill concurrent RDP sessions.
Fix is to remove KB2984972 and reboot.
And remember to turn off automatic updates.
Regards
Fix is to remove KB2984972 and reboot.
And remember to turn off automatic updates.
Regards
- Thu Jan 09, 2014 10:47 pm
- Forum: Troubleshooting and Problems
- Topic: Windows 2012 flickering screen
- Replies: 21
- Views: 51044
Re: Windows 2012 flickering screen
Good news indeed. Can confirm that testing on W2012R2, Tsplus 6.80.12.15 & the Flickerscreen patch. No flickering was detected. The display is rock solid. Very very nice. Thanks guys, this is really good. I'll upload to our 'problem' site tonight & report back when I have some real user feedback. Cr...
- Sat Jan 04, 2014 10:03 pm
- Forum: Troubleshooting and Problems
- Topic: Windows 2012 flickering screen
- Replies: 21
- Views: 51044
Re: Windows 2012 flickering screen
On our sites we use a variety of thick & thin clients, running both standard MS RDP client as well as TSplus clients. We even has some older Linux based thin clients running rdesktop. All flicker to some extent. The heavy users tend to have the TSplus client as they like to run dual monitors & the T...
- Fri Jan 03, 2014 11:48 pm
- Forum: Troubleshooting and Problems
- Topic: Windows 2012 flickering screen
- Replies: 21
- Views: 51044
Re: Windows 2012 flickering screen
Also have this problem with Windows 2012, on more than one site. At one site we had to downgrade to 2008r2 (which you can do with the 2012 license) as the issue was so bad. Since then the problem never re-occurred, but we almost lost the client over it, not to mention a stack of time we couldn't bil...