If I log into the server they are on and kill their Outlook process their session starts to respond. Have them log back in but now I have narrowed it down to the OUTLOOK.EXE process. ![]() All the user gets is usually only a partial display or just the desktop backgroup and the session doesn't respond. To their session or after a period of inactivity their session will lock them out and then they log in. When a user moves from one desk to another and they log into the terminal server and reconnect There are two scenarios that this happens. ![]() ![]() The issue I am running into is users’ terminal sessions will freeze up when they reconnect to their existing session. Just a little background info, I have a terminal server farm running Windows 2003 R2 Enterprise behind a hardware load balancer and I am utilizing the session directory service.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |