Exchange Server 2003 Running Mixed Mode and Outlook clients

  • Thread starter batfish
  • Start date Views 2,521
B

batfish

Hello all.

I am running Exchange 5.5 and Exchange 2003 in mixed mode.

The mailbox store is located on the Exchnge 2003 server.

The public folder store is duplicated and is on both the exchange 5.5 and

2003 servers.

I need to know if it is safe to run Outlook clients 2003 and 2007 without a

problem.

I know that historically you cannot run Outlook 2003 & 2007 clients against

an Exchange 5.5 Private/Public Information store without corruption.

So can I use Outlook 2003 & 2007 Clients since the mailbox store is now on

the 2003 Exchange server.

Thanks....
 
E

Ed Crowley [MVP]

I've never heard that Outlook 2003 or 2007 clients would cause corruption in

an Exchange 5.5 mailbox. Do you have a reference for that claim?

Likewise, I've never heard of problems running Outlook 2007 with an Exchange

2003 mailbox.

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"batfish" <batfish> wrote in message

news:B142C4BA-F602-4227-BC04-21DDEAF2D379@microsoft.com...
> Hello all.
> I am running Exchange 5.5 and Exchange 2003 in mixed mode.
> The mailbox store is located on the Exchnge 2003 server.
> The public folder store is duplicated and is on both the exchange 5.5 and
> 2003 servers.

> I need to know if it is safe to run Outlook clients 2003 and 2007 without
> a
> problem.

> I know that historically you cannot run Outlook 2003 & 2007 clients
> against
> an Exchange 5.5 Private/Public Information store without corruption.

> So can I use Outlook 2003 & 2007 Clients since the mailbox store is now on
> the 2003 Exchange server.

> Thanks....
 
L

Lanwench [MVP - Exchange]

Ed Crowley [MVP] <curspice@nospam.net> wrote:
> I've never heard that Outlook 2003 or 2007 clients would cause
> corruption in an Exchange 5.5 mailbox. Do you have a reference for
> that claim?
> Likewise, I've never heard of problems running Outlook 2007 with an
> Exchange 2003 mailbox.


Nor I. It works just fine.

> "batfish" <batfish> wrote in message
> news:B142C4BA-F602-4227-BC04-21DDEAF2D379@microsoft.com...
> > Hello all.
> > I am running Exchange 5.5 and Exchange 2003 in mixed mode.
> > The mailbox store is located on the Exchnge 2003 server.
> > The public folder store is duplicated and is on both the exchange
> > 5.5 and 2003 servers.
>

>> I need to know if it is safe to run Outlook clients 2003 and 2007
> > without a
> > problem.
>

>> I know that historically you cannot run Outlook 2003 & 2007 clients
> > against
> > an Exchange 5.5 Private/Public Information store without corruption.
>

>> So can I use Outlook 2003 & 2007 Clients since the mailbox store is
> > now on the 2003 Exchange server.
>

>> Thanks....
 
B

batfish

Hello Ed & LANWRENCH, See below. This is what I'm basing my question on.

1). Critical Update for Exchange Server 5.5 Required Before Installing

Outlook 2003

If your organization plans to use Microsoft® Exchange Server 5.5 with

Microsoft Office Outlook 2003, you should install a critical update for

Exchange Server before upgrading client computers to Outlook 2003.

Choosing to use Outlook 2003 with Exchange Server 5.5 without the update can

cause Exchange Server to encounter an error and stop responding. The problem

occurs in certain scenarios when a rule in a user's mailbox becomes

corrupted; when an e-mail message arrives and this rule is executed, Exchange

Server can fail.

To fix this problem, contact Microsoft Product Support Services to obtain an

update. The update requires Microsoft Exchange Server 5.5 Service Pack 4

(SP4). For a complete list of support phone numbers, click on Phone Numbers,

Support Options and Pricing on the Contact Microsoft - Overview page of the

Microsoft Product Support Services Web site.

For more detailed information about this problem, see the Knowledge Base

article XADM: Information Store Intermittently Stops Responding and an Access

Violation Occurs in EcDSDNFromSz.

2).Mixing Outlook 2003 and Exchange 5.5 can result in errors

by Jeremy "Smith MCSE, CNE, Network+" | Mar 25, 2004 8:00:00 AM

Tags: Microsoft Office, Groupware, E-mail servers, Jeremy Smith MCSE,

CNE..., Network+, Microsoft Outlook, Microsoft Exchange 5.5 Server, Microsoft

Outlook 2003, Microsoft Corp.

1 comment(s) Email Share Digg Yahoo! Buzz Twitter Facebook Google

del.icio.us StumbleUpon Reddit Newsvine Technorati Save Print Recommend 0

Takeaway: Look out for some problems when running Outlook 2003 with Exchange

5.5, and learn how to fix them.

This article has been reprinted from TechProGuild. If you find this article

helpful, subscribe to TechProGuild to get access to all our in-depth

technical articles. Sign up now for a FREE 30-day trial. All the articles on

our site that include a green $ icon are available only to TechProGuild

members.

In recent years, Microsoft's Exchange Server and Outlook client have emerged

as the leader in the messaging and collaboration platform marketplace.

However, it was not until version 5.5 that Exchange really gained a wide

acceptance among businesses. In fact, that version was so popular that there

are still many Exchange 5.5 installations running in businesses throughout

the globe.

However, while a lot of companies have not been able to justify the upgrade

to Exchange 2000 or 2003, many of them have upgraded to newer versions of

Outlook when upgrading installations of Microsoft Office. As a result, the

Exchange administrator is now faced with the dilemma of making a newer client

work with older messaging software. This can lead to a number of problems

when using Outlook 2003 to access a mailbox on an Exchange 5.5 server.

I'm going to outline some of the more common problems that Exchange

administrators might run into as they deal with a mixed environment of

Exchange 5.5 and Outlook 2003. We're going to look at:

What the problem is

What Microsoft recommends to do

Where to find any applicable patches

Problem 1

Perhaps the most common issue being reported by Exchange Administrators when

dealing with Outlook 2003 and Exchange 5.5 cohabitation is the issue

described in TechNet article 818709. One of the most useful and heavily used

features in the Exchange feature-set is Outlook Web Access (OWA), or the

ability to access an Exchange mailbox over a Web mail connection.

According to Microsoft, when you use OWA to access a mailbox on a server

running Exchange 5.5 and you are using a user account that was previously

accessed from a client computer running Outlook 2003, your OWA may stop

responding.

If you monitor your event logs, the event listed below will show up on the

Exchange system that the client was attempting to access:

Source: MSExchangeISPriv
 
L

Lanwench [MVP - Exchange]

batfish <batfish> wrote:
> Hello Ed & LANWRENCH, See below. This is what I'm basing my question
> on.
>


Honestly, I wouldn't worry about this - I use OL2003 and 2007 against E2007

and E2003 mailboxes. Hell, I use them against E2k mailboxes.

I would, however, get off the E5.5 server as soon as possible. That version

is ancient history and is no longer supported in any way.



> 1). Critical Update for Exchange Server 5.5 Required Before Installing
> Outlook 2003
> If your organization plans to use Microsoft® Exchange Server 5.5 with
> Microsoft Office Outlook 2003, you should install a critical update
> for Exchange Server before upgrading client computers to Outlook 2003.

> Choosing to use Outlook 2003 with Exchange Server 5.5 without the
> update can cause Exchange Server to encounter an error and stop
> responding. The problem occurs in certain scenarios when a rule in a
> user's mailbox becomes corrupted; when an e-mail message arrives and
> this rule is executed, Exchange Server can fail.

> To fix this problem, contact Microsoft Product Support Services to
> obtain an update. The update requires Microsoft Exchange Server 5.5
> Service Pack 4 (SP4). For a complete list of support phone numbers,
> click on Phone Numbers, Support Options and Pricing on the Contact
> Microsoft - Overview page of the Microsoft Product Support Services
> Web site.

> For more detailed information about this problem, see the Knowledge
> Base article XADM: Information Store Intermittently Stops Responding
> and an Access Violation Occurs in EcDSDNFromSz.

> 2).Mixing Outlook 2003 and Exchange 5.5 can result in errors
> by Jeremy "Smith MCSE, CNE, Network+" | Mar 25, 2004 8:00:00 AM

> Tags: Microsoft Office, Groupware, E-mail servers, Jeremy Smith MCSE,
> CNE..., Network+, Microsoft Outlook, Microsoft Exchange 5.5 Server,
> Microsoft Outlook 2003, Microsoft Corp.

> 1 comment(s) Email Share Digg Yahoo! Buzz Twitter Facebook Google
> del.icio.us StumbleUpon Reddit Newsvine Technorati Save Print
> Recommend 0 Takeaway: Look out for some problems when running Outlook
> 2003 with Exchange
> 5.5, and learn how to fix them.

> This article has been reprinted from TechProGuild. If you find this
> article helpful, subscribe to TechProGuild to get access to all our
> in-depth technical articles. Sign up now for a FREE 30-day trial. All
> the articles on our site that include a green $ icon are available
> only to TechProGuild members.

> In recent years, Microsoft's Exchange Server and Outlook client have
> emerged as the leader in the messaging and collaboration platform
> marketplace. However, it was not until version 5.5 that Exchange
> really gained a wide acceptance among businesses. In fact, that
> version was so popular that there are still many Exchange 5.5
> installations running in businesses throughout the globe.

> However, while a lot of companies have not been able to justify the
> upgrade to Exchange 2000 or 2003, many of them have upgraded to newer
> versions of Outlook when upgrading installations of Microsoft Office.
> As a result, the Exchange administrator is now faced with the dilemma
> of making a newer client work with older messaging software. This can
> lead to a number of problems when using Outlook 2003 to access a
> mailbox on an Exchange 5.5 server.

> I'm going to outline some of the more common problems that Exchange
> administrators might run into as they deal with a mixed environment of
> Exchange 5.5 and Outlook 2003. We're going to look at:

> What the problem is
> What Microsoft recommends to do
> Where to find any applicable patches

> Problem 1
> Perhaps the most common issue being reported by Exchange
> Administrators when dealing with Outlook 2003 and Exchange 5.5
> cohabitation is the issue described in TechNet article 818709. One of
> the most useful and heavily used features in the Exchange feature-set
> is Outlook Web Access (OWA), or the ability to access an Exchange
> mailbox over a Web mail connection.

> According to Microsoft, when you use OWA to access a mailbox on a
> server running Exchange 5.5 and you are using a user account that was
> previously accessed from a client computer running Outlook 2003, your
> OWA may stop responding.

> If you monitor your event logs, the event listed below will show up
> on the Exchange system that the client was attempting to access:

> Source: MSExchangeISPriv
 
B

batfish

Cool Beans.

Yes Exch 5.5 is on the way out as we speak.

I just need to make sure I have all my ducks in a row.

I'll post if I need help.

But in the mean time I can upgrade my users without fear to Outlook 2003 and

or 2007.

"Lanwench [MVP - Exchange]" wrote:


> batfish <batfish> wrote:
> > Hello Ed & LANWRENCH, See below. This is what I'm basing my question
> > on.
> >


> Honestly, I wouldn't worry about this - I use OL2003 and 2007 against E2007
> and E2003 mailboxes. Hell, I use them against E2k mailboxes.

> I would, however, get off the E5.5 server as soon as possible. That version
> is ancient history and is no longer supported in any way.
 
L

Lanwench [MVP - Exchange]

batfish <batfish> wrote:
> Cool Beans.
> Yes Exch 5.5 is on the way out as we speak.
> I just need to make sure I have all my ducks in a row.
> I'll post if I need help.

> But in the mean time I can upgrade my users without fear to Outlook
> 2003 and or 2007.


Yep. Go to town. I would suggest keeping everyone on the same version, tho -

makes support easier.

> "Lanwench [MVP - Exchange]" wrote:
>
> > batfish <batfish> wrote:
> >> Hello Ed & LANWRENCH, See below. This is what I'm basing my question
> >> on.
> >>

>

>> Honestly, I wouldn't worry about this - I use OL2003 and 2007
> > against E2007 and E2003 mailboxes. Hell, I use them against E2k
> > mailboxes.
>

>> I would, however, get off the E5.5 server as soon as possible. That
> > version is ancient history and is no longer supported in any way.
 
B

batfish

Thanks. Your help is greatly appreciated.

See you down the Road or in the next Forum.

BATFISH.

"Lanwench [MVP - Exchange]" wrote:


> Yep. Go to town. I would suggest keeping everyone on the same version, tho -
> makes support easier.
> > "Lanwench [MVP - Exchange]" wrote:
> >
> >> batfish <batfish> wrote:
> >>> Hello Ed & LANWRENCH, See below. This is what I'm basing my question
> >>> on.
> >>
> >
> >> Honestly, I wouldn't worry about this - I use OL2003 and 2007
> >> against E2007 and E2003 mailboxes. Hell, I use them against E2k
> >> mailboxes.
> >
> >> I would, however, get off the E5.5 server as soon as possible. That
> >> version is ancient history and is no longer supported in any way.


>
 
L

Lanwench [MVP - Exchange]

batfish <batfish> wrote:
> Thanks. Your help is greatly appreciated.
> See you down the Road or in the next Forum.
> BATFISH.


You're welcome ...have fun storming the castle!

> "Lanwench [MVP - Exchange]" wrote:
>
> > Yep. Go to town. I would suggest keeping everyone on the same
> > version, tho - makes support easier.
> >
>>
>>> "Lanwench [MVP - Exchange]" wrote:
> >
>>>> batfish <batfish> wrote:
> >>>> Hello Ed & LANWRENCH, See below. This is what I'm basing my
> >>>> question on.
> >>>
>>>
>>>> Honestly, I wouldn't worry about this - I use OL2003 and 2007
> >>> against E2007 and E2003 mailboxes. Hell, I use them against E2k
> >>> mailboxes.
> >>
>>>> I would, however, get off the E5.5 server as soon as possible. That
> >>> version is ancient history and is no longer supported in any way.
 
E

Ed Crowley [MVP]

Okay, so you apply a patch. What's the big deal?

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"batfish" <batfish> wrote in message

news:707CD795-FFD2-4837-8E28-86A364221EB9@microsoft.com...
> Hello Ed & LANWRENCH, See below. This is what I'm basing my question on.

> 1). Critical Update for Exchange Server 5.5 Required Before Installing
> Outlook 2003
> If your organization plans to use Microsoft® Exchange Server 5.5 with
> Microsoft Office Outlook 2003, you should install a critical update for
> Exchange Server before upgrading client computers to Outlook 2003.

> Choosing to use Outlook 2003 with Exchange Server 5.5 without the update
> can
> cause Exchange Server to encounter an error and stop responding. The
> problem
> occurs in certain scenarios when a rule in a user's mailbox becomes
> corrupted; when an e-mail message arrives and this rule is executed,
> Exchange
> Server can fail.

> To fix this problem, contact Microsoft Product Support Services to obtain
> an
> update. The update requires Microsoft Exchange Server 5.5 Service Pack 4
> (SP4). For a complete list of support phone numbers, click on Phone
> Numbers,
> Support Options and Pricing on the Contact Microsoft - Overview page of
> the
> Microsoft Product Support Services Web site.

> For more detailed information about this problem, see the Knowledge Base
> article XADM: Information Store Intermittently Stops Responding and an
> Access
> Violation Occurs in EcDSDNFromSz.

> 2).Mixing Outlook 2003 and Exchange 5.5 can result in errors
> by Jeremy "Smith MCSE, CNE, Network+" | Mar 25, 2004 8:00:00 AM

> Tags: Microsoft Office, Groupware, E-mail servers, Jeremy Smith MCSE,
> CNE..., Network+, Microsoft Outlook, Microsoft Exchange 5.5 Server,
> Microsoft
> Outlook 2003, Microsoft Corp.

> 1 comment(s) Email Share Digg Yahoo! Buzz Twitter Facebook Google
> del.icio.us StumbleUpon Reddit Newsvine Technorati Save Print Recommend 0
> Takeaway: Look out for some problems when running Outlook 2003 with
> Exchange
> 5.5, and learn how to fix them.

> This article has been reprinted from TechProGuild. If you find this
> article
> helpful, subscribe to TechProGuild to get access to all our in-depth
> technical articles. Sign up now for a FREE 30-day trial. All the articles
> on
> our site that include a green $ icon are available only to TechProGuild
> members.

> In recent years, Microsoft's Exchange Server and Outlook client have
> emerged
> as the leader in the messaging and collaboration platform marketplace.
> However, it was not until version 5.5 that Exchange really gained a wide
> acceptance among businesses. In fact, that version was so popular that
> there
> are still many Exchange 5.5 installations running in businesses throughout
> the globe.

> However, while a lot of companies have not been able to justify the
> upgrade
> to Exchange 2000 or 2003, many of them have upgraded to newer versions of
> Outlook when upgrading installations of Microsoft Office. As a result, the
> Exchange administrator is now faced with the dilemma of making a newer
> client
> work with older messaging software. This can lead to a number of problems
> when using Outlook 2003 to access a mailbox on an Exchange 5.5 server.

> I'm going to outline some of the more common problems that Exchange
> administrators might run into as they deal with a mixed environment of
> Exchange 5.5 and Outlook 2003. We're going to look at:

> What the problem is
> What Microsoft recommends to do
> Where to find any applicable patches

> Problem 1
> Perhaps the most common issue being reported by Exchange Administrators
> when
> dealing with Outlook 2003 and Exchange 5.5 cohabitation is the issue
> described in TechNet article 818709. One of the most useful and heavily
> used
> features in the Exchange feature-set is Outlook Web Access (OWA), or the
> ability to access an Exchange mailbox over a Web mail connection.

> According to Microsoft, when you use OWA to access a mailbox on a server
> running Exchange 5.5 and you are using a user account that was previously
> accessed from a client computer running Outlook 2003, your OWA may stop
> responding.

> If you monitor your event logs, the event listed below will show up on the
> Exchange system that the client was attempting to access:

> Source: MSExchangeISPriv

>
 
E

Ed Crowley [MVP]

So now you're Mrs. Goodwrench?

Ed Crowley MVP

"There are seldom good technological solutions to behavioral problems."

> .

"Lanwench [MVP - Exchange]"

<lanwench@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote in message

news:%23NC3D7n%23JHA.1248@TK2MSFTNGP04.phx.gbl...
> batfish <batfish> wrote:
> > Hello Ed & LANWRENCH, See below. This is what I'm basing my question
> > on.
> >


> Honestly, I wouldn't worry about this - I use OL2003 and 2007 against
> E2007 and E2003 mailboxes. Hell, I use them against E2k mailboxes.

> I would, however, get off the E5.5 server as soon as possible. That
> version is ancient history and is no longer supported in any way.

>
>

>> 1). Critical Update for Exchange Server 5.5 Required Before Installing
> > Outlook 2003
> > If your organization plans to use Microsoft® Exchange Server 5.5 with
> > Microsoft Office Outlook 2003, you should install a critical update
> > for Exchange Server before upgrading client computers to Outlook 2003.
>

>> Choosing to use Outlook 2003 with Exchange Server 5.5 without the
> > update can cause Exchange Server to encounter an error and stop
> > responding. The problem occurs in certain scenarios when a rule in a
> > user's mailbox becomes corrupted; when an e-mail message arrives and
> > this rule is executed, Exchange Server can fail.
>

>> To fix this problem, contact Microsoft Product Support Services to
> > obtain an update. The update requires Microsoft Exchange Server 5.5
> > Service Pack 4 (SP4). For a complete list of support phone numbers,
> > click on Phone Numbers, Support Options and Pricing on the Contact
> > Microsoft - Overview page of the Microsoft Product Support Services
> > Web site.
>

>> For more detailed information about this problem, see the Knowledge
> > Base article XADM: Information Store Intermittently Stops Responding
> > and an Access Violation Occurs in EcDSDNFromSz.
>

>> 2).Mixing Outlook 2003 and Exchange 5.5 can result in errors
> > by Jeremy "Smith MCSE, CNE, Network+" | Mar 25, 2004 8:00:00 AM
>

>> Tags: Microsoft Office, Groupware, E-mail servers, Jeremy Smith MCSE,
> > CNE..., Network+, Microsoft Outlook, Microsoft Exchange 5.5 Server,
> > Microsoft Outlook 2003, Microsoft Corp.
>

>> 1 comment(s) Email Share Digg Yahoo! Buzz Twitter Facebook Google
> > del.icio.us StumbleUpon Reddit Newsvine Technorati Save Print
> > Recommend 0 Takeaway: Look out for some problems when running Outlook
> > 2003 with Exchange
> > 5.5, and learn how to fix them.
>

>
>> This article has been reprinted from TechProGuild. If you find this
> > article helpful, subscribe to TechProGuild to get access to all our
> > in-depth technical articles. Sign up now for a FREE 30-day trial. All
> > the articles on our site that include a green $ icon are available
> > only to TechProGuild members.
>

>> In recent years, Microsoft's Exchange Server and Outlook client have
> > emerged as the leader in the messaging and collaboration platform
> > marketplace. However, it was not until version 5.5 that Exchange
> > really gained a wide acceptance among businesses. In fact, that
> > version was so popular that there are still many Exchange 5.5
> > installations running in businesses throughout the globe.
>

>> However, while a lot of companies have not been able to justify the
> > upgrade to Exchange 2000 or 2003, many of them have upgraded to newer
> > versions of Outlook when upgrading installations of Microsoft Office.
> > As a result, the Exchange administrator is now faced with the dilemma
> > of making a newer client work with older messaging software. This can
> > lead to a number of problems when using Outlook 2003 to access a
> > mailbox on an Exchange 5.5 server.
>

>> I'm going to outline some of the more common problems that Exchange
> > administrators might run into as they deal with a mixed environment of
> > Exchange 5.5 and Outlook 2003. We're going to look at:
>

>> What the problem is
> > What Microsoft recommends to do
> > Where to find any applicable patches
>

>> Problem 1
> > Perhaps the most common issue being reported by Exchange
> > Administrators when dealing with Outlook 2003 and Exchange 5.5
> > cohabitation is the issue described in TechNet article 818709. One of
> > the most useful and heavily used features in the Exchange feature-set
> > is Outlook Web Access (OWA), or the ability to access an Exchange
> > mailbox over a Web mail connection.
>

>> According to Microsoft, when you use OWA to access a mailbox on a
> > server running Exchange 5.5 and you are using a user account that was
> > previously accessed from a client computer running Outlook 2003, your
> > OWA may stop responding.
>

>> If you monitor your event logs, the event listed below will show up
> > on the Exchange system that the client was attempting to access:
>

>> Source: MSExchangeISPriv


>
 

Top