|
|
|
date: Sun, 13 Jan 2008 16:40:51 -0500,
group: microsoft.public.exchange.design
back
Questions about migrating from Ex2003 to Ex2007 and coexistance.
I'm looking for some information regarding a migration from Exchange 2003 to
Exchange 2007 within the same organization.
Our A/D environment is a single forest/single domain/single site with about
4,500 users. We currently have a stable Exchange 2003 configuration since
early 2004 (before that we had multiple 5.5 orgs). We have two
(non-clustered) mailbox servers and a front end/OWA server. The front end
server is also the "bridgehead" to a McAfee SCM email gateway/antispam
device for internet mail.
We had planned on migrating all users to Exchange 2007 early this year.
However, due to a series of problems in our fiscal department, we were
unable to purchase the required 4,500 client access licenses at this time.
We were able to purchase the hardware, the Exchange server software, and 160
CAL's, though.
I've gone through the Microsoft class "Updating your skills from Ex2003 to
Ex2007", as well as doing a lot of research and reading. What I'm planning
to do is set up the Exchange 2007 system and migrate a group of users to it.
Then when the funding gets straightened out, migrate the remaining users.
I've already set up two x64 Windows 2003 R2 Enterprise servers in a MNS
cluster with the file share witness for the mailbox server, (each with 20GB
of RAM). I have another server for the Hub Transport and Client Access
functions. Eventually, we'll set up another hub/CAS server. The "edge
transport" functions will be handled by the McAfee appliance, and we're not
using the Unified Messaging functions.
I'm at the point to install the Exchange 2007 software on the first system
and I have a few questions. I know Exchange 2007 and Exchange 2003 can
coexist. However I want to make sure that as I install the Exchange 2007 on
the new servers that I don't do anything that will "break" the Exchange 2003
users. Upper management frowns on that..
When I install the first Exchange 2003 server (the hub/CAS), I know it will
modify the Active Directory schema. Will there be any interruptions for
existing 2003 users? Is this something that can be done during normal
operating hours, or should it be done during a maintenance time?
Currently our email flow to and from the internet goes through the Exchange
2003 front end server to the McAfee appliance "smart host". In most of the
migration scenarios I've seen, the idea is to install the Exchange 2007 hub
and let it take on the internet email flow for both the old 2003 servers and
the new Exchange 2007 system. However, since we don't have sufficient
license for all the users to be on Exchange 2007, I don't want to run all
the users email through the new server (at least until I know when the rest
of the CAL's will be purchased). What I'd like to do is have the 2007 hub
server used for mail just to and from the users on the Exchange 2007 system,
and send internet mail to through the "routing group" that it sets up with
the Exchange 2003 system, and letting that system send to the smart host
appliance. Of course, incoming internet mail to the Exchange server will
need to be properly forwarded to the users on the Exchange 2007 system when
it's received on the Exchange 2003 server from the appliance. When I
install the Exchange 2007 hub, will it affect the forwarding of internet
mail through the existing 2003 server? Will internet mail from the 2007
system automatically go through the 2003 system? If not, how do I need to
configure it to?
Sorry about the length of this post. Any suggestions, comments, or opinions
would be appreciated.
Mike O.
date: Sun, 13 Jan 2008 16:40:51 -0500
author: Mike O
Re: Questions about migrating from Ex2003 to Ex2007 and coexistance.
These articles discuss a move from Ex2003 to a coexistence setup:
http://www.exchangeinbox.com/article.aspx?i=85&t=5
http://www.exchangeinbox.com/article.aspx?i=86&t=5
--
Alexander Zammit
WinDeveloper Software
IMF Tune - Unleash the Full Intelligent Message Filter Power
http://www.windeveloper.com/imftune/
"Mike O" wrote in message
news:eQNO6ziVIHA.3400@TK2MSFTNGP03.phx.gbl...
> I'm looking for some information regarding a migration from Exchange 2003
> to Exchange 2007 within the same organization.
>
> Our A/D environment is a single forest/single domain/single site with
> about 4,500 users. We currently have a stable Exchange 2003 configuration
> since early 2004 (before that we had multiple 5.5 orgs). We have two
> (non-clustered) mailbox servers and a front end/OWA server. The front end
> server is also the "bridgehead" to a McAfee SCM email gateway/antispam
> device for internet mail.
>
> We had planned on migrating all users to Exchange 2007 early this year.
> However, due to a series of problems in our fiscal department, we were
> unable to purchase the required 4,500 client access licenses at this time.
> We were able to purchase the hardware, the Exchange server software, and
> 160 CAL's, though.
>
> I've gone through the Microsoft class "Updating your skills from Ex2003 to
> Ex2007", as well as doing a lot of research and reading. What I'm
> planning to do is set up the Exchange 2007 system and migrate a group of
> users to it. Then when the funding gets straightened out, migrate the
> remaining users.
>
> I've already set up two x64 Windows 2003 R2 Enterprise servers in a MNS
> cluster with the file share witness for the mailbox server, (each with
> 20GB of RAM). I have another server for the Hub Transport and Client
> Access functions. Eventually, we'll set up another hub/CAS server. The
> "edge transport" functions will be handled by the McAfee appliance, and
> we're not using the Unified Messaging functions.
>
> I'm at the point to install the Exchange 2007 software on the first system
> and I have a few questions. I know Exchange 2007 and Exchange 2003 can
> coexist. However I want to make sure that as I install the Exchange 2007
> on the new servers that I don't do anything that will "break" the Exchange
> 2003 users. Upper management frowns on that..
>
> When I install the first Exchange 2003 server (the hub/CAS), I know it
> will modify the Active Directory schema. Will there be any interruptions
> for existing 2003 users? Is this something that can be done during
> normal operating hours, or should it be done during a maintenance time?
>
> Currently our email flow to and from the internet goes through the
> Exchange 2003 front end server to the McAfee appliance "smart host". In
> most of the migration scenarios I've seen, the idea is to install the
> Exchange 2007 hub and let it take on the internet email flow for both the
> old 2003 servers and the new Exchange 2007 system. However, since we
> don't have sufficient license for all the users to be on Exchange 2007, I
> don't want to run all the users email through the new server (at least
> until I know when the rest of the CAL's will be purchased). What I'd like
> to do is have the 2007 hub server used for mail just to and from the users
> on the Exchange 2007 system, and send internet mail to through the
> "routing group" that it sets up with the Exchange 2003 system, and letting
> that system send to the smart host appliance. Of course, incoming
> internet mail to the Exchange server will need to be properly forwarded to
> the users on the Exchange 2007 system when it's received on the Exchange
> 2003 server from the appliance. When I install the Exchange 2007 hub,
> will it affect the forwarding of internet mail through the existing 2003
> server? Will internet mail from the 2007 system automatically go through
> the 2003 system? If not, how do I need to configure it to?
>
>
> Sorry about the length of this post. Any suggestions, comments, or
> opinions would be appreciated.
>
> Mike O.
>
>
date: Mon, 14 Jan 2008 09:21:44 +0100
author: Alexander Zammit [MVP] alex@respond_to_group
Re: Questions about migrating from Ex2003 to Ex2007 and coexistance.
Thank you for the information, those articles look to be exactly what I'm
looking for.
The scenario they're talking about is the same as ours; wanting internet
mail to flow through the Exchange 2003 system. We already have an Exchange
2003 connector set up for our internet mail, so it sounds like the Exchange
2007 system will pick it up automatically.
Mike O.
"Alexander Zammit [MVP]" <alex@respond_to_group> wrote in message
news:%2396ojZoVIHA.484@TK2MSFTNGP06.phx.gbl...
> These articles discuss a move from Ex2003 to a coexistence setup:
> http://www.exchangeinbox.com/article.aspx?i=85&t=5
> http://www.exchangeinbox.com/article.aspx?i=86&t=5
>
>
> --
> Alexander Zammit
> WinDeveloper Software
> IMF Tune - Unleash the Full Intelligent Message Filter Power
> http://www.windeveloper.com/imftune/
>
>
> "Mike O" wrote in message
> news:eQNO6ziVIHA.3400@TK2MSFTNGP03.phx.gbl...
>> I'm looking for some information regarding a migration from Exchange 2003
>> to Exchange 2007 within the same organization.
>>
>> Our A/D environment is a single forest/single domain/single site with
>> about 4,500 users. We currently have a stable Exchange 2003
>> configuration since early 2004 (before that we had multiple 5.5 orgs).
>> We have two (non-clustered) mailbox servers and a front end/OWA server.
>> The front end server is also the "bridgehead" to a McAfee SCM email
>> gateway/antispam device for internet mail.
>>
>> We had planned on migrating all users to Exchange 2007 early this year.
>> However, due to a series of problems in our fiscal department, we were
>> unable to purchase the required 4,500 client access licenses at this
>> time. We were able to purchase the hardware, the Exchange server
>> software, and 160 CAL's, though.
>>
>> I've gone through the Microsoft class "Updating your skills from Ex2003
>> to Ex2007", as well as doing a lot of research and reading. What I'm
>> planning to do is set up the Exchange 2007 system and migrate a group of
>> users to it. Then when the funding gets straightened out, migrate the
>> remaining users.
>>
>> I've already set up two x64 Windows 2003 R2 Enterprise servers in a MNS
>> cluster with the file share witness for the mailbox server, (each with
>> 20GB of RAM). I have another server for the Hub Transport and Client
>> Access functions. Eventually, we'll set up another hub/CAS server. The
>> "edge transport" functions will be handled by the McAfee appliance, and
>> we're not using the Unified Messaging functions.
>>
>> I'm at the point to install the Exchange 2007 software on the first
>> system and I have a few questions. I know Exchange 2007 and Exchange
>> 2003 can coexist. However I want to make sure that as I install the
>> Exchange 2007 on the new servers that I don't do anything that will
>> "break" the Exchange 2003 users. Upper management frowns on that..
>>
>> When I install the first Exchange 2003 server (the hub/CAS), I know it
>> will modify the Active Directory schema. Will there be any interruptions
>> for existing 2003 users? Is this something that can be done during
>> normal operating hours, or should it be done during a maintenance time?
>>
>> Currently our email flow to and from the internet goes through the
>> Exchange 2003 front end server to the McAfee appliance "smart host". In
>> most of the migration scenarios I've seen, the idea is to install the
>> Exchange 2007 hub and let it take on the internet email flow for both the
>> old 2003 servers and the new Exchange 2007 system. However, since we
>> don't have sufficient license for all the users to be on Exchange 2007, I
>> don't want to run all the users email through the new server (at least
>> until I know when the rest of the CAL's will be purchased). What I'd
>> like to do is have the 2007 hub server used for mail just to and from the
>> users on the Exchange 2007 system, and send internet mail to through the
>> "routing group" that it sets up with the Exchange 2003 system, and
>> letting that system send to the smart host appliance. Of course,
>> incoming internet mail to the Exchange server will need to be properly
>> forwarded to the users on the Exchange 2007 system when it's received on
>> the Exchange 2003 server from the appliance. When I install the Exchange
>> 2007 hub, will it affect the forwarding of internet mail through the
>> existing 2003 server? Will internet mail from the 2007 system
>> automatically go through the 2003 system? If not, how do I need to
>> configure it to?
>>
>>
>> Sorry about the length of this post. Any suggestions, comments, or
>> opinions would be appreciated.
>>
>> Mike O.
>>
>>
>
>
date: Mon, 14 Jan 2008 12:53:13 -0500
author: Mike O
Re: Questions about migrating from Ex2003 to Ex2007 and coexistance.
That is exactly the case. No need to do anything in your scenario.
--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner
"Mike O" wrote in message
news:%23PMcXZtVIHA.4696@TK2MSFTNGP05.phx.gbl...
> Thank you for the information, those articles look to be exactly what I'm
> looking for.
>
> The scenario they're talking about is the same as ours; wanting internet
> mail to flow through the Exchange 2003 system. We already have an
> Exchange 2003 connector set up for our internet mail, so it sounds like
> the Exchange 2007 system will pick it up automatically.
>
> Mike O.
>
> "Alexander Zammit [MVP]" <alex@respond_to_group> wrote in message
> news:%2396ojZoVIHA.484@TK2MSFTNGP06.phx.gbl...
>> These articles discuss a move from Ex2003 to a coexistence setup:
>> http://www.exchangeinbox.com/article.aspx?i=85&t=5
>> http://www.exchangeinbox.com/article.aspx?i=86&t=5
>>
>>
>> --
>> Alexander Zammit
>> WinDeveloper Software
>> IMF Tune - Unleash the Full Intelligent Message Filter Power
>> http://www.windeveloper.com/imftune/
>>
>>
>> "Mike O" wrote in message
>> news:eQNO6ziVIHA.3400@TK2MSFTNGP03.phx.gbl...
>>> I'm looking for some information regarding a migration from Exchange
>>> 2003 to Exchange 2007 within the same organization.
>>>
>>> Our A/D environment is a single forest/single domain/single site with
>>> about 4,500 users. We currently have a stable Exchange 2003
>>> configuration since early 2004 (before that we had multiple 5.5 orgs).
>>> We have two (non-clustered) mailbox servers and a front end/OWA server.
>>> The front end server is also the "bridgehead" to a McAfee SCM email
>>> gateway/antispam device for internet mail.
>>>
>>> We had planned on migrating all users to Exchange 2007 early this year.
>>> However, due to a series of problems in our fiscal department, we were
>>> unable to purchase the required 4,500 client access licenses at this
>>> time. We were able to purchase the hardware, the Exchange server
>>> software, and 160 CAL's, though.
>>>
>>> I've gone through the Microsoft class "Updating your skills from Ex2003
>>> to Ex2007", as well as doing a lot of research and reading. What I'm
>>> planning to do is set up the Exchange 2007 system and migrate a group of
>>> users to it. Then when the funding gets straightened out, migrate the
>>> remaining users.
>>>
>>> I've already set up two x64 Windows 2003 R2 Enterprise servers in a MNS
>>> cluster with the file share witness for the mailbox server, (each with
>>> 20GB of RAM). I have another server for the Hub Transport and Client
>>> Access functions. Eventually, we'll set up another hub/CAS server.
>>> The "edge transport" functions will be handled by the McAfee appliance,
>>> and we're not using the Unified Messaging functions.
>>>
>>> I'm at the point to install the Exchange 2007 software on the first
>>> system and I have a few questions. I know Exchange 2007 and Exchange
>>> 2003 can coexist. However I want to make sure that as I install the
>>> Exchange 2007 on the new servers that I don't do anything that will
>>> "break" the Exchange 2003 users. Upper management frowns on that..
>>>
>>> When I install the first Exchange 2003 server (the hub/CAS), I know it
>>> will modify the Active Directory schema. Will there be any
>>> interruptions for existing 2003 users? Is this something that can be
>>> done during normal operating hours, or should it be done during a
>>> maintenance time?
>>>
>>> Currently our email flow to and from the internet goes through the
>>> Exchange 2003 front end server to the McAfee appliance "smart host". In
>>> most of the migration scenarios I've seen, the idea is to install the
>>> Exchange 2007 hub and let it take on the internet email flow for both
>>> the old 2003 servers and the new Exchange 2007 system. However, since
>>> we don't have sufficient license for all the users to be on Exchange
>>> 2007, I don't want to run all the users email through the new server (at
>>> least until I know when the rest of the CAL's will be purchased). What
>>> I'd like to do is have the 2007 hub server used for mail just to and
>>> from the users on the Exchange 2007 system, and send internet mail to
>>> through the "routing group" that it sets up with the Exchange 2003
>>> system, and letting that system send to the smart host appliance. Of
>>> course, incoming internet mail to the Exchange server will need to be
>>> properly forwarded to the users on the Exchange 2007 system when it's
>>> received on the Exchange 2003 server from the appliance. When I install
>>> the Exchange 2007 hub, will it affect the forwarding of internet mail
>>> through the existing 2003 server? Will internet mail from the 2007
>>> system automatically go through the 2003 system? If not, how do I need
>>> to configure it to?
>>>
>>>
>>> Sorry about the length of this post. Any suggestions, comments, or
>>> opinions would be appreciated.
>>>
>>> Mike O.
>>>
>>>
>>
>>
>
date: Mon, 14 Jan 2008 18:49:54 -0500
author: John Oliver, Jr. [MVP]
Re: Questions about migrating from Ex2003 to Ex2007 and coexistance.
Thanks. So the fact that there is an existing connector to the outside
world will enable the Exchange 2007 to use it? So once I move some
mailboxes to the Exchange 2007 system, any outgoing internet mail use the
site connector to the 2003 system (that Exchange 07 setup creates), then go
out through the connector to our smart host appliance, correct?
Regarding the other question (about the schema changes), should any of the
changes cause any interruption or other effect on the existing 2003 users?
Should I want for a maintenance window when I do this? All of our DC's are
connected with 1Gb etherernet, and we have a single forest/domain/site, so
there should be minimal DC/GC replication issues.
I would think it wouldn't be an issue to do it during normal operating
hours, but I just want to make sure I'm not missing anything.
Mike O.
"John Oliver, Jr. [MVP]" wrote in message
news:OnNIrgwVIHA.3400@TK2MSFTNGP03.phx.gbl...
> That is exactly the case. No need to do anything in your scenario.
>
> --
> John Oliver, Jr
> MCSE, MCT, CCNA
> Exchange MVP 2008
> Microsoft Certified Partner
>
>
> "Mike O" wrote in message
> news:%23PMcXZtVIHA.4696@TK2MSFTNGP05.phx.gbl...
>> Thank you for the information, those articles look to be exactly what I'm
>> looking for.
>>
>> The scenario they're talking about is the same as ours; wanting internet
>> mail to flow through the Exchange 2003 system. We already have an
>> Exchange 2003 connector set up for our internet mail, so it sounds like
>> the Exchange 2007 system will pick it up automatically.
>>
>> Mike O.
>>
>> "Alexander Zammit [MVP]" <alex@respond_to_group> wrote in message
>> news:%2396ojZoVIHA.484@TK2MSFTNGP06.phx.gbl...
>>> These articles discuss a move from Ex2003 to a coexistence setup:
>>> http://www.exchangeinbox.com/article.aspx?i=85&t=5
>>> http://www.exchangeinbox.com/article.aspx?i=86&t=5
>>>
>>>
>>> --
>>> Alexander Zammit
>>> WinDeveloper Software
>>> IMF Tune - Unleash the Full Intelligent Message Filter Power
>>> http://www.windeveloper.com/imftune/
>>>
>>>
>>> "Mike O" wrote in message
>>> news:eQNO6ziVIHA.3400@TK2MSFTNGP03.phx.gbl...
>>>> I'm looking for some information regarding a migration from Exchange
>>>> 2003 to Exchange 2007 within the same organization.
>>>>
>>>> Our A/D environment is a single forest/single domain/single site with
>>>> about 4,500 users. We currently have a stable Exchange 2003
>>>> configuration since early 2004 (before that we had multiple 5.5 orgs).
>>>> We have two (non-clustered) mailbox servers and a front end/OWA server.
>>>> The front end server is also the "bridgehead" to a McAfee SCM email
>>>> gateway/antispam device for internet mail.
>>>>
>>>> We had planned on migrating all users to Exchange 2007 early this year.
>>>> However, due to a series of problems in our fiscal department, we were
>>>> unable to purchase the required 4,500 client access licenses at this
>>>> time. We were able to purchase the hardware, the Exchange server
>>>> software, and 160 CAL's, though.
>>>>
>>>> I've gone through the Microsoft class "Updating your skills from Ex2003
>>>> to Ex2007", as well as doing a lot of research and reading. What I'm
>>>> planning to do is set up the Exchange 2007 system and migrate a group
>>>> of users to it. Then when the funding gets straightened out, migrate
>>>> the remaining users.
>>>>
>>>> I've already set up two x64 Windows 2003 R2 Enterprise servers in a MNS
>>>> cluster with the file share witness for the mailbox server, (each with
>>>> 20GB of RAM). I have another server for the Hub Transport and Client
>>>> Access functions. Eventually, we'll set up another hub/CAS server.
>>>> The "edge transport" functions will be handled by the McAfee appliance,
>>>> and we're not using the Unified Messaging functions.
>>>>
>>>> I'm at the point to install the Exchange 2007 software on the first
>>>> system and I have a few questions. I know Exchange 2007 and Exchange
>>>> 2003 can coexist. However I want to make sure that as I install the
>>>> Exchange 2007 on the new servers that I don't do anything that will
>>>> "break" the Exchange 2003 users. Upper management frowns on that..
>>>>
>>>> When I install the first Exchange 2003 server (the hub/CAS), I know it
>>>> will modify the Active Directory schema. Will there be any
>>>> interruptions for existing 2003 users? Is this something that can be
>>>> done during normal operating hours, or should it be done during a
>>>> maintenance time?
>>>>
>>>> Currently our email flow to and from the internet goes through the
>>>> Exchange 2003 front end server to the McAfee appliance "smart host".
>>>> In most of the migration scenarios I've seen, the idea is to install
>>>> the Exchange 2007 hub and let it take on the internet email flow for
>>>> both the old 2003 servers and the new Exchange 2007 system. However,
>>>> since we don't have sufficient license for all the users to be on
>>>> Exchange 2007, I don't want to run all the users email through the new
>>>> server (at least until I know when the rest of the CAL's will be
>>>> purchased). What I'd like to do is have the 2007 hub server used for
>>>> mail just to and from the users on the Exchange 2007 system, and send
>>>> internet mail to through the "routing group" that it sets up with the
>>>> Exchange 2003 system, and letting that system send to the smart host
>>>> appliance. Of course, incoming internet mail to the Exchange server
>>>> will need to be properly forwarded to the users on the Exchange 2007
>>>> system when it's received on the Exchange 2003 server from the
>>>> appliance. When I install the Exchange 2007 hub, will it affect the
>>>> forwarding of internet mail through the existing 2003 server? Will
>>>> internet mail from the 2007 system automatically go through the 2003
>>>> system? If not, how do I need to configure it to?
>>>>
>>>>
>>>> Sorry about the length of this post. Any suggestions, comments, or
>>>> opinions would be appreciated.
>>>>
>>>> Mike O.
>>>>
>>>>
>>>
>>>
>>
>
>
date: Mon, 14 Jan 2008 22:19:19 -0500
author: Mike O
Re: Questions about migrating from Ex2003 to Ex2007 and coexistance.
Yes for your first question. Schema changes in your environment should not
have a great impact. I prefer to run the setup after hours and after a good
system state backup.
--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner
"Mike O" wrote in message
news:%23O5$rVyVIHA.5980@TK2MSFTNGP04.phx.gbl...
> Thanks. So the fact that there is an existing connector to the outside
> world will enable the Exchange 2007 to use it? So once I move some
> mailboxes to the Exchange 2007 system, any outgoing internet mail use the
> site connector to the 2003 system (that Exchange 07 setup creates), then
> go out through the connector to our smart host appliance, correct?
>
> Regarding the other question (about the schema changes), should any of the
> changes cause any interruption or other effect on the existing 2003 users?
> Should I want for a maintenance window when I do this? All of our DC's
> are connected with 1Gb etherernet, and we have a single
> forest/domain/site, so there should be minimal DC/GC replication issues.
>
> I would think it wouldn't be an issue to do it during normal operating
> hours, but I just want to make sure I'm not missing anything.
>
> Mike O.
>
>
> "John Oliver, Jr. [MVP]" wrote in message
> news:OnNIrgwVIHA.3400@TK2MSFTNGP03.phx.gbl...
>> That is exactly the case. No need to do anything in your scenario.
>>
>> --
>> John Oliver, Jr
>> MCSE, MCT, CCNA
>> Exchange MVP 2008
>> Microsoft Certified Partner
>>
>>
>> "Mike O" wrote in message
>> news:%23PMcXZtVIHA.4696@TK2MSFTNGP05.phx.gbl...
>>> Thank you for the information, those articles look to be exactly what
>>> I'm looking for.
>>>
>>> The scenario they're talking about is the same as ours; wanting internet
>>> mail to flow through the Exchange 2003 system. We already have an
>>> Exchange 2003 connector set up for our internet mail, so it sounds like
>>> the Exchange 2007 system will pick it up automatically.
>>>
>>> Mike O.
>>>
>>> "Alexander Zammit [MVP]" <alex@respond_to_group> wrote in message
>>> news:%2396ojZoVIHA.484@TK2MSFTNGP06.phx.gbl...
>>>> These articles discuss a move from Ex2003 to a coexistence setup:
>>>> http://www.exchangeinbox.com/article.aspx?i=85&t=5
>>>> http://www.exchangeinbox.com/article.aspx?i=86&t=5
>>>>
>>>>
>>>> --
>>>> Alexander Zammit
>>>> WinDeveloper Software
>>>> IMF Tune - Unleash the Full Intelligent Message Filter Power
>>>> http://www.windeveloper.com/imftune/
>>>>
>>>>
>>>> "Mike O" wrote in message
>>>> news:eQNO6ziVIHA.3400@TK2MSFTNGP03.phx.gbl...
>>>>> I'm looking for some information regarding a migration from Exchange
>>>>> 2003 to Exchange 2007 within the same organization.
>>>>>
>>>>> Our A/D environment is a single forest/single domain/single site with
>>>>> about 4,500 users. We currently have a stable Exchange 2003
>>>>> configuration since early 2004 (before that we had multiple 5.5 orgs).
>>>>> We have two (non-clustered) mailbox servers and a front end/OWA
>>>>> server. The front end server is also the "bridgehead" to a McAfee SCM
>>>>> email gateway/antispam device for internet mail.
>>>>>
>>>>> We had planned on migrating all users to Exchange 2007 early this
>>>>> year. However, due to a series of problems in our fiscal department,
>>>>> we were unable to purchase the required 4,500 client access licenses
>>>>> at this time. We were able to purchase the hardware, the Exchange
>>>>> server software, and 160 CAL's, though.
>>>>>
>>>>> I've gone through the Microsoft class "Updating your skills from
>>>>> Ex2003 to Ex2007", as well as doing a lot of research and reading.
>>>>> What I'm planning to do is set up the Exchange 2007 system and migrate
>>>>> a group of users to it. Then when the funding gets straightened out,
>>>>> migrate the remaining users.
>>>>>
>>>>> I've already set up two x64 Windows 2003 R2 Enterprise servers in a
>>>>> MNS cluster with the file share witness for the mailbox server, (each
>>>>> with 20GB of RAM). I have another server for the Hub Transport and
>>>>> Client Access functions. Eventually, we'll set up another hub/CAS
>>>>> server. The "edge transport" functions will be handled by the McAfee
>>>>> appliance, and we're not using the Unified Messaging functions.
>>>>>
>>>>> I'm at the point to install the Exchange 2007 software on the first
>>>>> system and I have a few questions. I know Exchange 2007 and Exchange
>>>>> 2003 can coexist. However I want to make sure that as I install the
>>>>> Exchange 2007 on the new servers that I don't do anything that will
>>>>> "break" the Exchange 2003 users. Upper management frowns on that..
>>>>>
>>>>> When I install the first Exchange 2003 server (the hub/CAS), I know it
>>>>> will modify the Active Directory schema. Will there be any
>>>>> interruptions for existing 2003 users? Is this something that can be
>>>>> done during normal operating hours, or should it be done during a
>>>>> maintenance time?
>>>>>
>>>>> Currently our email flow to and from the internet goes through the
>>>>> Exchange 2003 front end server to the McAfee appliance "smart host".
>>>>> In most of the migration scenarios I've seen, the idea is to install
>>>>> the Exchange 2007 hub and let it take on the internet email flow for
>>>>> both the old 2003 servers and the new Exchange 2007 system. However,
>>>>> since we don't have sufficient license for all the users to be on
>>>>> Exchange 2007, I don't want to run all the users email through the new
>>>>> server (at least until I know when the rest of the CAL's will be
>>>>> purchased). What I'd like to do is have the 2007 hub server used for
>>>>> mail just to and from the users on the Exchange 2007 system, and send
>>>>> internet mail to through the "routing group" that it sets up with the
>>>>> Exchange 2003 system, and letting that system send to the smart host
>>>>> appliance. Of course, incoming internet mail to the Exchange server
>>>>> will need to be properly forwarded to the users on the Exchange 2007
>>>>> system when it's received on the Exchange 2003 server from the
>>>>> appliance. When I install the Exchange 2007 hub, will it affect the
>>>>> forwarding of internet mail through the existing 2003 server? Will
>>>>> internet mail from the 2007 system automatically go through the 2003
>>>>> system? If not, how do I need to configure it to?
>>>>>
>>>>>
>>>>> Sorry about the length of this post. Any suggestions, comments, or
>>>>> opinions would be appreciated.
>>>>>
>>>>> Mike O.
>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
date: Mon, 14 Jan 2008 22:58:27 -0500
author: John Oliver, Jr. [MVP]
Re: Questions about migrating from Ex2003 to Ex2007 and coexistance. - more questions
Now I have a couple of related questions.
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 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.
"John Oliver, Jr. [MVP]" wrote in message
news:%23YnojryVIHA.484@TK2MSFTNGP06.phx.gbl...
> Yes for your first question. Schema changes in your environment should
> not have a great impact. I prefer to run the setup after hours and after
> a good system state backup.
>
> --
> John Oliver, Jr
> MCSE, MCT, CCNA
> Exchange MVP 2008
> Microsoft Certified Partner
>
>
> "Mike O" wrote in message
> news:%23O5$rVyVIHA.5980@TK2MSFTNGP04.phx.gbl...
>> Thanks. So the fact that there is an existing connector to the outside
>> world will enable the Exchange 2007 to use it? So once I move some
>> mailboxes to the Exchange 2007 system, any outgoing internet mail use the
>> site connector to the 2003 system (that Exchange 07 setup creates), then
>> go out through the connector to our smart host appliance, correct?
>>
>> Regarding the other question (about the schema changes), should any of
>> the changes cause any interruption or other effect on the existing 2003
>> users? Should I want for a maintenance window when I do this? All of our
>> DC's are connected with 1Gb etherernet, and we have a single
>> forest/domain/site, so there should be minimal DC/GC replication issues.
>>
>> I would think it wouldn't be an issue to do it during normal operating
>> hours, but I just want to make sure I'm not missing anything.
>>
>> Mike O.
>>
>>
>> "John Oliver, Jr. [MVP]" wrote in message
>> news:OnNIrgwVIHA.3400@TK2MSFTNGP03.phx.gbl...
>>> That is exactly the case. No need to do anything in your scenario.
>>>
>>> --
>>> John Oliver, Jr
>>> MCSE, MCT, CCNA
>>> Exchange MVP 2008
>>> Microsoft Certified Partner
>>>
>>>
>>> "Mike O" wrote in message
>>> news:%23PMcXZtVIHA.4696@TK2MSFTNGP05.phx.gbl...
>>>> Thank you for the information, those articles look to be exactly what
>>>> I'm looking for.
>>>>
>>>> The scenario they're talking about is the same as ours; wanting
>>>> internet mail to flow through the Exchange 2003 system. We already
>>>> have an Exchange 2003 connector set up for our internet mail, so it
>>>> sounds like the Exchange 2007 system will pick it up automatically.
>>>>
>>>> Mike O.
>>>>
>>>> "Alexander Zammit [MVP]" <alex@respond_to_group> wrote in message
>>>> news:%2396ojZoVIHA.484@TK2MSFTNGP06.phx.gbl...
>>>>> These articles discuss a move from Ex2003 to a coexistence setup:
>>>>> http://www.exchangeinbox.com/article.aspx?i=85&t=5
>>>>> http://www.exchangeinbox.com/article.aspx?i=86&t=5
>>>>>
>>>>>
>>>>> --
>>>>> Alexander Zammit
>>>>> WinDeveloper Software
>>>>> IMF Tune - Unleash the Full Intelligent Message Filter Power
>>>>> http://www.windeveloper.com/imftune/
>>>>>
>>>>>
>>>>> "Mike O" wrote in message
>>>>> news:eQNO6ziVIHA.3400@TK2MSFTNGP03.phx.gbl...
>>>>>> I'm looking for some information regarding a migration from Exchange
>>>>>> 2003 to Exchange 2007 within the same organization.
>>>>>>
>>>>>> Our A/D environment is a single forest/single domain/single site with
>>>>>> about 4,500 users. We currently have a stable Exchange 2003
>>>>>> configuration since early 2004 (before that we had multiple 5.5
>>>>>> orgs). We have two (non-clustered) mailbox servers and a front
>>>>>> end/OWA server. The front end server is also the "bridgehead" to a
>>>>>> McAfee SCM email gateway/antispam device for internet mail.
>>>>>>
>>>>>> We had planned on migrating all users to Exchange 2007 early this
>>>>>> year. However, due to a series of problems in our fiscal department,
>>>>>> we were unable to purchase the required 4,500 client access licenses
>>>>>> at this time. We were able to purchase the hardware, the Exchange
>>>>>> server software, and 160 CAL's, though.
>>>>>>
>>>>>> I've gone through the Microsoft class "Updating your skills from
>>>>>> Ex2003 to Ex2007", as well as doing a lot of research and reading.
>>>>>> What I'm planning to do is set up the Exchange 2007 system and
>>>>>> migrate a group of users to it. Then when the funding gets
>>>>>> straightened out, migrate the remaining users.
>>>>>>
>>>>>> I've already set up two x64 Windows 2003 R2 Enterprise servers in a
>>>>>> MNS cluster with the file share witness for the mailbox server, (each
>>>>>> with 20GB of RAM). I have another server for the Hub Transport and
>>>>>> Client Access functions. Eventually, we'll set up another hub/CAS
>>>>>> server. The "edge transport" functions will be handled by the McAfee
>>>>>> appliance, and we're not using the Unified Messaging functions.
>>>>>>
>>>>>> I'm at the point to install the Exchange 2007 software on the first
>>>>>> system and I have a few questions. I know Exchange 2007 and Exchange
>>>>>> 2003 can coexist. However I want to make sure that as I install the
>>>>>> Exchange 2007 on the new servers that I don't do anything that will
>>>>>> "break" the Exchange 2003 users. Upper management frowns on that..
>>>>>>
>>>>>> When I install the first Exchange 2003 server (the hub/CAS), I know
>>>>>> it will modify the Active Directory schema. Will there be any
>>>>>> interruptions for existing 2003 users? Is this something that can
>>>>>> be done during normal operating hours, or should it be done during a
>>>>>> maintenance time?
>>>>>>
>>>>>> Currently our email flow to and from the internet goes through the
>>>>>> Exchange 2003 front end server to the McAfee appliance "smart host".
>>>>>> In most of the migration scenarios I've seen, the idea is to install
>>>>>> the Exchange 2007 hub and let it take on the internet email flow for
>>>>>> both the old 2003 servers and the new Exchange 2007 system. However,
>>>>>> since we don't have sufficient license for all the users to be on
>>>>>> Exchange 2007, I don't want to run all the users email through the
>>>>>> new server (at least until I know when the rest of the CAL's will be
>>>>>> purchased). What I'd like to do is have the 2007 hub server used for
>>>>>> mail just to and from the users on the Exchange 2007 system, and send
>>>>>> internet mail to through the "routing group" that it sets up with the
>>>>>> Exchange 2003 system, and letting that system send to the smart host
>>>>>> appliance. Of course, incoming internet mail to the Exchange server
>>>>>> will need to be properly forwarded to the users on the Exchange 2007
>>>>>> system when it's received on the Exchange 2003 server from the
>>>>>> appliance. When I install the Exchange 2007 hub, will it affect the
>>>>>> forwarding of internet mail through the existing 2003 server? Will
>>>>>> internet mail from the 2007 system automatically go through the 2003
>>>>>> system? If not, how do I need to configure it to?
>>>>>>
>>>>>>
>>>>>> Sorry about the length of this post. Any suggestions, comments, or
>>>>>> opinions would be appreciated.
>>>>>>
>>>>>> Mike O.
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>
>
date: Tue, 15 Jan 2008 18:23:55 -0500
author: Mike O
Re: Questions about migrating from Ex2003 to Ex2007 and coexistance. - more questions
Inline:
--
John Oliver, Jr
MCSE, MCT, CCNA
Exchange MVP 2008
Microsoft Certified Partner
"Mike O" wrote in message
news:eKu3028VIHA.4896@TK2MSFTNGP06.phx.gbl...
> Now I have a couple of related questions.
>
> 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?
Yes, for a complete explaination see
http://msexchangeteam.com/archive/2006/10/09/429135.aspx
>
> 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 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?
The user will access his/her mailbox through OWA depending on what server
his/her mailbox resides on.
>
> Mike O.
>
>
> "John Oliver, Jr. [MVP]" wrote in message
> news:%23YnojryVIHA.484@TK2MSFTNGP06.phx.gbl...
>> Yes for your first question. Schema changes in your environment should
>> not have a great impact. I prefer to run the setup after hours and after
>> a good system state backup.
>>
>> --
>> John Oliver, Jr
>> MCSE, MCT, CCNA
>> Exchange MVP 2008
>> Microsoft Certified Partner
>>
>>
>> "Mike O" wrote in message
>> news:%23O5$rVyVIHA.5980@TK2MSFTNGP04.phx.gbl...
>>> Thanks. So the fact that there is an existing connector to the outside
>>> world will enable the Exchange 2007 to use it? So once I move some
>>> mailboxes to the Exchange 2007 system, any outgoing internet mail use
>>> the site connector to the 2003 system (that Exchange 07 setup creates),
>>> then go out through the connector to our smart host appliance, correct?
>>>
>>> Regarding the other question (about the schema changes), should any of
>>> the changes cause any interruption or other effect on the existing 2003
>>> users? Should I want for a maintenance window when I do this? All of
>>> our DC's are connected with 1Gb etherernet, and we have a single
>>> forest/domain/site, so there should be minimal DC/GC replication issues.
>>>
>>> I would think it wouldn't be an issue to do it during normal operating
>>> hours, but I just want to make sure I'm not missing anything.
>>>
>>> Mike O.
>>>
>>>
>>> "John Oliver, Jr. [MVP]" wrote in message
>>> news:OnNIrgwVIHA.3400@TK2MSFTNGP03.phx.gbl...
>>>> That is exactly the case. No need to do anything in your scenario.
>>>>
>>>> --
>>>> John Oliver, Jr
>>>> MCSE, MCT, CCNA
>>>> Exchange MVP 2008
>>>> Microsoft Certified Partner
>>>>
>>>>
>>>> "Mike O" wrote in message
>>>> news:%23PMcXZtVIHA.4696@TK2MSFTNGP05.phx.gbl...
>>>>> Thank you for the information, those articles look to be exactly what
>>>>> I'm looking for.
>>>>>
>>>>> The scenario they're talking about is the same as ours; wanting
>>>>> internet mail to flow through the Exchange 2003 system. We already
>>>>> have an Exchange 2003 connector set up for our internet mail, so it
>>>>> sounds like the Exchange 2007 system will pick it up automatically.
>>>>>
>>>>> Mike O.
>>>>>
>>>>> "Alexander Zammit [MVP]" <alex@respond_to_group> wrote in message
>>>>> news:%2396ojZoVIHA.484@TK2MSFTNGP06.phx.gbl...
>>>>>> These articles discuss a move from Ex2003 to a coexistence setup:
>>>>>> http://www.exchangeinbox.com/article.aspx?i=85&t=5
>>>>>> http://www.exchangeinbox.com/article.aspx?i=86&t=5
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Alexander Zammit
>>>>>> WinDeveloper Software
>>>>>> IMF Tune - Unleash the Full Intelligent Message Filter Power
>>>>>> http://www.windeveloper.com/imftune/
>>>>>>
>>>>>>
>>>>>> "Mike O" wrote in message
>>>>>> news:eQNO6ziVIHA.3400@TK2MSFTNGP03.phx.gbl...
>>>>>>> I'm looking for some information regarding a migration from Exchange
>>>>>>> 2003 to Exchange 2007 within the same organization.
>>>>>>>
>>>>>>> Our A/D environment is a single forest/single domain/single site
>>>>>>> with about 4,500 users. We currently have a stable Exchange 2003
>>>>>>> configuration since early 2004 (before that we had multiple 5.5
>>>>>>> orgs). We have two (non-clustered) mailbox servers and a front
>>>>>>> end/OWA server. The front end server is also the "bridgehead" to a
>>>>>>> McAfee SCM email gateway/antispam device for internet mail.
>>>>>>>
>>>>>>> We had planned on migrating all users to Exchange 2007 early this
>>>>>>> year. However, due to a series of problems in our fiscal department,
>>>>>>> we were unable to purchase the required 4,500 client access licenses
>>>>>>> at this time. We were able to purchase the hardware, the Exchange
>>>>>>> server software, and 160 CAL's, though.
>>>>>>>
>>>>>>> I've gone through the Microsoft class "Updating your skills from
>>>>>>> Ex2003 to Ex2007", as well as doing a lot of research and reading.
>>>>>>> What I'm planning to do is set up the Exchange 2007 system and
>>>>>>> migrate a group of users to it. Then when the funding gets
>>>>>>> straightened out, migrate the remaining users.
>>>>>>>
>>>>>>> I've already set up two x64 Windows 2003 R2 Enterprise servers in a
>>>>>>> MNS cluster with the file share witness for the mailbox server,
>>>>>>> (each with 20GB of RAM). I have another server for the Hub
>>>>>>> Transport and Client Access functions. Eventually, we'll set up
>>>>>>> another hub/CAS server. The "edge transport" functions will be
>>>>>>> handled by the McAfee appliance, and we're not using the Unified
>>>>>>> Messaging functions.
>>>>>>>
>>>>>>> I'm at the point to install the Exchange 2007 software on the first
>>>>>>> system and I have a few questions. I know Exchange 2007 and
>>>>>>> Exchange 2003 can coexist. However I want to make sure that as I
>>>>>>> install the Exchange 2007 on the new servers that I don't do
>>>>>>> anything that will "break" the Exchange 2003 users. Upper
>>>>>>> management frowns on that..
>>>>>>>
>>>>>>> When I install the first Exchange 2003 server (the hub/CAS), I know
>>>>>>> it will modify the Active Directory schema. Will there be any
>>>>>>> interruptions for existing 2003 users? Is this something that can
>>>>>>> be done during normal operating hours, or should it be done during a
>>>>>>> maintenance time?
>>>>>>>
>>>>>>> Currently our email flow to and from the internet goes through the
>>>>>>> Exchange 2003 front end server to the McAfee appliance "smart host".
>>>>>>> In most of the migration scenarios I've seen, the idea is to install
>>>>>>> the Exchange 2007 hub and let it take on the internet email flow for
>>>>>>> both the old 2003 servers and the new Exchange 2007 system.
>>>>>>> However, since we don't have sufficient license for all the users to
>>>>>>> be on Exchange 2007, I don't want to run all the users email through
>>>>>>> the new server (at least until I know when the rest of the CAL's
>>>>>>> will be purchased). What I'd like to do is have the 2007 hub server
>>>>>>> used for mail just to and from the users on the Exchange 2007
>>>>>>> system, and send internet mail to through the "routing group" that
>>>>>>> it sets up with the Exchange 2003 system, and letting that system
>>>>>>> send to the smart host appliance. Of course, incoming internet mail
>>>>>>> to the Exchange server will need to be properly forwarded to the
>>>>>>> users on the Exchange 2007 system when it's received on the Exchange
>>>>>>> 2003 server from the appliance. When I install the Exchange 2007
>>>>>>> hub, will it affect the forwarding of internet mail through the
>>>>>>> existing 2003 server? Will internet mail from the 2007 system
>>>>>>> automatically go through the 2003 system? If not, how do I need to
>>>>>>> configure it to?
>>>>>>>
>>>>>>>
>>>>>>> Sorry about the length of this post. Any suggestions, comments, or
>>>>>>> opinions would be appreciated.
>>>>>>>
>>>>>>> Mike O.
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>
date: Tue, 22 Jan 2008 20:46:00 -0500
author: John Oliver, Jr. [MVP]
|
|
