Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
Exchange
2000.active.directory
2000.admin
2000.announcements
2000.app.conversion
2000.applications
2000.clients
2000.clustering
2000.connectivity
2000.development
2000.documentation
2000.general
2000.information.store
2000.interop
2000.kms
2000.misc
2000.protocols
2000.realtime.collabo.
2000.setup
2000.transport
2000.win2000
admin
application.conversion
applications
clients
clustering
connectivity
design
development
misc
mobility
setup
tools
  
 
date: Thu, 17 Jan 2008 22:07:27 -0500,    group: microsoft.public.exchange.design        back       


Operating in a mixed Ex2003 and Ex2007 environment   
(I had previously posted these questions as part of another thread, "Re: 
Questions about migrating from Ex2003 to Ex2007 and coexistence. - more 
questions", but I think they got lost in the other information)

We're in the process of planning a migration from Exchange 2003 to Exchange 
2007.  For a period of time we'll be operating with both environments in 
place.

I have a couple of questions related to operating in a mixed Exchange 2003 
and Exchange 2007 environment.

I know for Exchange 2007 user mailbox settings you have to use the Exchange 
07 tools, you don't use the A/D users and computers snap in, but during the 
"coexistence" phase, I assume I still use the A/D snap in for the Exchange 
2003 users, correct?  If we need to create a new user, or mailbox enable 
someone on the Exchange 2003 system, do we just use the regular tools?

Also, regarding OWA.  I realize that the Exchange 2007 CAS provides for the 
backward compatibility 2003 "/exchange" OWA site, but due to our licensing 
issues I don't want to run the 2003 users through the 2007 web system.  Is 
there any problem with leaving our 2003 Outlook Web server active and as we 
migrate users and at that time have them go to the 2007 CAS server (and use 
the "/OWA")?    What would happen if a user with a mailbox on the 2007 
server would try to access the 2003 OWA server?

Mike O.
date: Thu, 17 Jan 2008 22:07:27 -0500   author:   Mike O

RE: Operating in a mixed Ex2003 and Ex2007 environment   
Mike, yes continue to use the "regular" tools for managing/creating Exchange 
2003 users.

Also for Exchange 07 users access an OWA 2003 server..this will not work. 
OWA 2003 does not have the capability to render pages for Exchange 07 
mailboxes.

Thanks,
Jason

"Mike O" wrote:

> (I had previously posted these questions as part of another thread, "Re: 
> Questions about migrating from Ex2003 to Ex2007 and coexistence. - more 
> questions", but I think they got lost in the other information)
> 
> We're in the process of planning a migration from Exchange 2003 to Exchange 
> 2007.  For a period of time we'll be operating with both environments in 
> place.
> 
> I have a couple of questions related to operating in a mixed Exchange 2003 
> and Exchange 2007 environment.
> 
> I know for Exchange 2007 user mailbox settings you have to use the Exchange 
> 07 tools, you don't use the A/D users and computers snap in, but during the 
> "coexistence" phase, I assume I still use the A/D snap in for the Exchange 
> 2003 users, correct?  If we need to create a new user, or mailbox enable 
> someone on the Exchange 2003 system, do we just use the regular tools?
> 
> Also, regarding OWA.  I realize that the Exchange 2007 CAS provides for the 
> backward compatibility 2003 "/exchange" OWA site, but due to our licensing 
> issues I don't want to run the 2003 users through the 2007 web system.  Is 
> there any problem with leaving our 2003 Outlook Web server active and as we 
> migrate users and at that time have them go to the 2007 CAS server (and use 
> the "/OWA")?    What would happen if a user with a mailbox on the 2007 
> server would try to access the 2003 OWA server?
> 
> Mike O.
> 
>
date: Thu, 17 Jan 2008 21:41:00 -0800   author:   JSilva

Re: Operating in a mixed Ex2003 and Ex2007 environment   
Thanks.  Both answers are pretty much what I figured, I just wanted to 
confirm.   We don't use OWA extensively, mostly management or staff who what 
to check their email from home, or occasionally from out of town.  However, 
when we start telling people to use "/OWA" instead of "/Exchange", I KNOW 
there's going to be ones who use /exchange then wonder why it doesn't work. 
I was hoping there would be some process where the Exchange 2003 would 
recognize that the mailbox is on a different server and redirect their 
access to the new one.





"JSilva"  wrote in message 
news:EA7DB26A-1CCB-4E16-9851-4F440038A184@microsoft.com...
> Mike, yes continue to use the "regular" tools for managing/creating 
> Exchange
> 2003 users.
>
> Also for Exchange 07 users access an OWA 2003 server..this will not work.
> OWA 2003 does not have the capability to render pages for Exchange 07
> mailboxes.
>
> Thanks,
> Jason
>
> "Mike O" wrote:
>
>> (I had previously posted these questions as part of another thread, "Re:
>> Questions about migrating from Ex2003 to Ex2007 and coexistence. - more
>> questions", but I think they got lost in the other information)
>>
>> We're in the process of planning a migration from Exchange 2003 to 
>> Exchange
>> 2007.  For a period of time we'll be operating with both environments in
>> place.
>>
>> I have a couple of questions related to operating in a mixed Exchange 
>> 2003
>> and Exchange 2007 environment.
>>
>> I know for Exchange 2007 user mailbox settings you have to use the 
>> Exchange
>> 07 tools, you don't use the A/D users and computers snap in, but during 
>> the
>> "coexistence" phase, I assume I still use the A/D snap in for the 
>> Exchange
>> 2003 users, correct?  If we need to create a new user, or mailbox enable
>> someone on the Exchange 2003 system, do we just use the regular tools?
>>
>> Also, regarding OWA.  I realize that the Exchange 2007 CAS provides for 
>> the
>> backward compatibility 2003 "/exchange" OWA site, but due to our 
>> licensing
>> issues I don't want to run the 2003 users through the 2007 web system. 
>> Is
>> there any problem with leaving our 2003 Outlook Web server active and as 
>> we
>> migrate users and at that time have them go to the 2007 CAS server (and 
>> use
>> the "/OWA")?    What would happen if a user with a mailbox on the 2007
>> server would try to access the 2003 OWA server?
>>
>> Mike O.
>>
>>
date: Sun, 20 Jan 2008 16:12:59 -0500   author:   Mike O

Re: Operating in a mixed Ex2003 and Ex2007 environment   
Hi,
It is best practice to phase out all Exchange 2003 Front Ends, so you only 
have Exchange 2007 CAS and HT Servers.

From here you can then have Exchange 2007 and your legacy Exchange 2003 
backend mailbox servers.

The Exchange 2007 Client Access Servers will support 2003 users, allowing 
OWA (using legacy /exchange virtual directory) and RPC over HTTPs (Outlook 
Anywhere) access.

From here you then move the 2003 mailboxes to 2007 backends in your own 
time.

Oliver


> Thanks.  Both answers are pretty much what I figured, I just wanted to 
> confirm.   We don't use OWA extensively, mostly management or staff who 
> what to check their email from home, or occasionally from out of town. 
> However, when we start telling people to use "/OWA" instead of 
> "/Exchange", I KNOW there's going to be ones who use /exchange then wonder 
> why it doesn't work. I was hoping there would be some process where the 
> Exchange 2003 would recognize that the mailbox is on a different server 
> and redirect their access to the new one.
date: Tue, 22 Jan 2008 16:48:10 -0000   author:   Oliver Moazzezi [MVP]

Re: Operating in a mixed Ex2003 and Ex2007 environment   
I know the Exchange 2007 can handle both "flavors" of OWA, and the intent is 
to migrate everyone to the Exchange 2007 eventually, but due to budget 
issues, we can't migrate everyone yet.  I don't want to send (potentially) 
all 4500 Exchange 2003 users through an Exchange 2007 system with only 160 
Ex07 client access licenses.


"Oliver Moazzezi [MVP]"  wrote in message 
news:uzGoTaRXIHA.3940@TK2MSFTNGP05.phx.gbl...
> Hi,
> It is best practice to phase out all Exchange 2003 Front Ends, so you only 
> have Exchange 2007 CAS and HT Servers.
>
> From here you can then have Exchange 2007 and your legacy Exchange 2003 
> backend mailbox servers.
>
> The Exchange 2007 Client Access Servers will support 2003 users, allowing 
> OWA (using legacy /exchange virtual directory) and RPC over HTTPs (Outlook 
> Anywhere) access.
>
> From here you then move the 2003 mailboxes to 2007 backends in your own 
> time.
>
> Oliver
>
>
>> Thanks.  Both answers are pretty much what I figured, I just wanted to 
>> confirm.   We don't use OWA extensively, mostly management or staff who 
>> what to check their email from home, or occasionally from out of town. 
>> However, when we start telling people to use "/OWA" instead of 
>> "/Exchange", I KNOW there's going to be ones who use /exchange then 
>> wonder why it doesn't work. I was hoping there would be some process 
>> where the Exchange 2003 would recognize that the mailbox is on a 
>> different server and redirect their access to the new one.
>
>
date: Tue, 22 Jan 2008 22:46:49 -0500   author:   Mike O

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us