My client is running terminal server in application mode. The windows os is server 2003 standard edition sp1. One of the applications on the terminal server is Outlook 2003 SP2 with all post sp2 updates installed.
There is a problem with one user. She is an executive assistant and has been delegated access to her bosses mailbox, as well as editor permissions on several user's calendars.
When she uses Outlook via the terminal server everything is fine until she does the following:
- create a meeting request on behalf of her boss
- she receives the response emails from the required attendees
- she'll open one of these response meeting request emails and when she closes it, Outlook will freeze
Windows is still functioning fine, but Outlook needs to be closed through task manager.
She's also reported issues of random blank appointments appearing in her calendar. Sometimes multiple blank appointments appearing side by side (i.e. 3 12:00PM blank calendar items appearing on the same day)
Has anyone else seen or heard of similar issues when running Outlook 2003 on a windows 2003 sp1 terminal server? The weird thing is that none of these issues present themselves when she runs Outlook 2003 directly from her desktop - only via terminal server.
Any help would be appreciated.
There is a problem with one user. She is an executive assistant and has been delegated access to her bosses mailbox, as well as editor permissions on several user's calendars.
When she uses Outlook via the terminal server everything is fine until she does the following:
- create a meeting request on behalf of her boss
- she receives the response emails from the required attendees
- she'll open one of these response meeting request emails and when she closes it, Outlook will freeze
Windows is still functioning fine, but Outlook needs to be closed through task manager.
She's also reported issues of random blank appointments appearing in her calendar. Sometimes multiple blank appointments appearing side by side (i.e. 3 12:00PM blank calendar items appearing on the same day)
Has anyone else seen or heard of similar issues when running Outlook 2003 on a windows 2003 sp1 terminal server? The weird thing is that none of these issues present themselves when she runs Outlook 2003 directly from her desktop - only via terminal server.
Any help would be appreciated.