PROTECTED]]
Sent: Tuesday, February 11, 2003 7:17 PM
To: Exchange Discussions
Subject: Re: WARNING! OWA 5.5 E2K
It's not the MS Exchange legacy DN? Call PSS back and tell them to find
the
attribute(s) in question, they can and if they won't ask them who they'd
like to escalate the call to. You'll
on the test plan.
-Original Message-
From: Charles Marriott [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 9:35 AM
To: Exchange Discussions
Subject: RE: WARNING! OWA 5.5 E2K
Since Exchange 2k native means no 5.5 isn't this what one would expect?
-Original Message
Cornetet
Sent: Wednesday, February 12, 2003 7:43 AM
To: Exchange Discussions
Subject: RE: WARNING! OWA 5.5 E2K
OWA 5.5 isn't exchange, it's just a big vbscript asp program that uses
some COM objects and MAPI to access mail. It worked just fine in our
test lab. Unfortunately, our testing didn't include
Our AD domain is still mixed.
-Original Message-
From: Charles Marriott [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, February 12, 2003 9:55 AM
To: Exchange Discussions
Subject: RE: WARNING! OWA 5.5 E2K
I agree in spirit. But, don't you install it from the Exchange 5.5 CD?
Could
A word of warning! If you plan on using Exchange 5.5 OWA to access E2K
mailboxes, DO NOT GO NATIVE E2K! Any new users created after going
native will not be able to access their mailbox via OWA 5.5.
We opened a PSS call on this and Microsoft confirmed that this will not
work because legacy
It's not the MS Exchange legacy DN? Call PSS back and tell them to find the
attribute(s) in question, they can and if they won't ask them who they'd
like to escalate the call to. You'll likely be able to set those attributes
programmatically.
On 2/11/03 16:02, Ken Cornetet [EMAIL PROTECTED]
6 matches
Mail list logo
