T
tektotket
Guest
Since updating a desktop from win10 version 1809 to 1903 build 18362.145 remote desktop session behavior to that desktop has been abnormal. The client for the sessions to the 1903 desktop is still on 1809.
Upon reconnecting to a disconnected 1903 session with many items open, the taskbar now becomes blank for a period of time and eventually all the open items repopulate. Sometimes the blank taskbar initially appears floating in the middle of the screen instead of bottom during the reconnection while it goes through the blanking/repopulating. Problem persists across reboots.
Additionally, an imap account in outlook 2016 mso 16.0.4849.1000 32bit that is kept open in a disconnected remote desktop session no longer syncs mail until that session is reconnected. This results in inbound mail piling up in the inbox on the server and Outlook rules having nothing to process. Once the remote desktop session is reconnected, the taskbar goes through the blanking/repopulating and Outlook immediately begins syncing mail. Problem persists across reboots. I don't know if this behavior changed as a result of an Office update but it began sometime after the 1903 update.
Suggestions are appreciated.
More...
Upon reconnecting to a disconnected 1903 session with many items open, the taskbar now becomes blank for a period of time and eventually all the open items repopulate. Sometimes the blank taskbar initially appears floating in the middle of the screen instead of bottom during the reconnection while it goes through the blanking/repopulating. Problem persists across reboots.
Additionally, an imap account in outlook 2016 mso 16.0.4849.1000 32bit that is kept open in a disconnected remote desktop session no longer syncs mail until that session is reconnected. This results in inbound mail piling up in the inbox on the server and Outlook rules having nothing to process. Once the remote desktop session is reconnected, the taskbar goes through the blanking/repopulating and Outlook immediately begins syncing mail. Problem persists across reboots. I don't know if this behavior changed as a result of an Office update but it began sometime after the 1903 update.
Suggestions are appreciated.
More...