MikeDGallagher
asked on
Outlook 2003 - Problems with "do not deliver before" feature
Hi,
We have recently upgraded from Windows 2000 with MS Office 97 to Windows XP SP2 with MS Office 2003. They are currently on an Exchange 5.5 Server back end.
Previously within Outlook, users could create emails and schedule them for delivery at a time of their choosing, normally when they are not in the office. Since upgrading to MS Office 2003, the email only sends if the user is logged in and has MS Outlook 2003 open at the time the email is scheduled to be sent. This clearly defeats the object of the function and is impractical in our environment.
I've looked reasonably extensively on the web and the best info I have is that this feature is "buggy" with Outlook 2003 due to a change in the way the message is transported from Outlook 97.
Does anyone have a definite answer as to whether there is a tried and tested solution to fixing this, or whether I have to accept the current situation and potentially look at a 3rd party solution or roll back to Outlook 97.
Many thanks.
We have recently upgraded from Windows 2000 with MS Office 97 to Windows XP SP2 with MS Office 2003. They are currently on an Exchange 5.5 Server back end.
Previously within Outlook, users could create emails and schedule them for delivery at a time of their choosing, normally when they are not in the office. Since upgrading to MS Office 2003, the email only sends if the user is logged in and has MS Outlook 2003 open at the time the email is scheduled to be sent. This clearly defeats the object of the function and is impractical in our environment.
I've looked reasonably extensively on the web and the best info I have is that this feature is "buggy" with Outlook 2003 due to a change in the way the message is transported from Outlook 97.
Does anyone have a definite answer as to whether there is a tried and tested solution to fixing this, or whether I have to accept the current situation and potentially look at a 3rd party solution or roll back to Outlook 97.
Many thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Actually you did mention that, but it I don't believe it makes any difference. Cached mode works with 5.5 too, or at least according to what I've read (e.g. http://office.microsoft.com/en-us/assistance/HA011402591033.aspx)
ASKER
Thanks,
I'm now looking in the area of, although we are not using Cached Exchanged Mode, whether it is still using OST files and disabling these. If you think of anything else, feel free to let me know.
Thanks a lot.
I'm now looking in the area of, although we are not using Cached Exchanged Mode, whether it is still using OST files and disabling these. If you think of anything else, feel free to let me know.
Thanks a lot.
ASKER
I should have mentioned on the first post, as we are still on an Exchange 5.5 back end, the users are not in cached exchange mode but are still experiencing the problem. It is a bit intermittent, but fails far far more than it succeeds.
Any other ideas?
Many thanks again.