Re: Migration of Windows server 2000 to Windows 2008

Hello Raul,

Also see:
http://technet.microsoft.com/en-us/l...53(WS.10).aspx

Windows server 2008 R2 functional level and Exchange 2003 Sp2 are not working
together according to the Exchange Server Supportability Matrix:
http://technet.microsoft.com/en-us/l...EXCHG.80).aspx

So you should think about upgrading Exchange at least to version 2007 or
better using Exchagne 2010 which should work with Windows server 2008 R2.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Great instruction Meinolf!
>
> I am going through the same process except I am installing 2008 R2
> server. Other that it was noted below, is there anything I should
> differently for R2?
>
>> - if the new machine is domain controller and DNS server run again
>> replmon, dcdiag on both domain controllers. For using netdiag.exe on
>> 2008, NOT 2008 R2, you have to download and install
>> (http://www.microsoft.com/downloads/d...id=96A35011-FD
>> 83-419D-939B->9A772EA2DF90&displaylang=en), ignore the compatibility
>> warning, or extract netdiag.exe only and copy it"
>>
> Currently I have one exchange server. How will the migration affect
> it? Is there anything else I need to do besides updating the RUS
> entries? please let me know. Thanks much!
>
> "Meinolf Weber [MVP-DS]" wrote in message
> news:. com...
>
>> Hello Mohammed,
>>
>> To migrate to Windows server 2008 i would start with the forest level
>> and then go to each child domain. I suggest to install the new 2008
>> DCs as additional domain controllers and then move the FSMOs.
>>
>> !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR
>> DATA/MACHINE!!!
>>
>> - For Exchange check the following articles:
>> http://msexchangeteam.com/archive/20...16/446709.aspx
>> http://msexchangeteam.com/archive/20...05/448338.aspx
>>
>> http://support.microsoft.com/?id=314649
>>
>> http://technet.microsoft.com/en-us/l...EXCHG.80).aspx
>>
>> http://theessentialexchange.com/blog...007/11/13/exch
>> ange-server-2003-and-domain-controllers-a-summary.aspx
>>
>> http://support.microsoft.com/kb/822931/
>>
>> - On the old server open DNS management console and check that you
>> are running Active directory integrated zone (easier for replication,
>> if you have more then one DNS server)
>>
>> - run replmon from the run line or repadmin /showreps(only if more
>> then one DC exist), dcdiag and netdiag from the command prompt on the
>> old machine to check for errors, if you have some post the complete
>> output from the command here or solve them first. For this tools you
>> have to install the support\tools\suptools.msi from the 2000
>> installation disk.
>>
>> - run adprep /forestprep and adprep /domainprep and adprep
>> /domainprep /gpprep and adprep /rodcprep from the 2008 installation
>> disk against the 2000 schema master(forestprep) / infrastructure
>> master(domainprep/rodcprep), with an account that is member of the
>> Schema/Enterprise/Domain admins, to upgrade the schema to the new
>> version (44) or 2008 R2 (47)
>>
>> - you can check the schema version with "schupgr" or "dsquery *
>> cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr
>> objectVersion" without the quotes in a command prompt
>> - Install the new machine as a member server in your existing domain
>> - configure a fixed ip and set the preferred DNS server to the old
>> DNS server only, think about disabling IPv6 if you are not using it,
>> some known problems exist with it. Follow
>> (http://blogs.dirteam.com/blogs/paulb...9/03/19/disabl
>> ing-ipv6-on-windows-2008.aspx) to disable it
>>
>> - run dcpromo and follow the wizard to add the 2008 server to an
>> existing domain, make it also Global catalog and DNS server.
>>
>> - for DNS give the server time for replication, at least 15 minutes.
>> Because you use Active directory integrated zones it will
>> automatically replicate the zones to the new server. Open DNS
>> management console to check that they appear
>>
>> - if the new machine is domain controller and DNS server run again
>> replmon, dcdiag on both domain controllers. For using netdiag.exe on
>> 2008, NOT 2008 R2, you have to download and install
>> (http://www.microsoft.com/downloads/d...id=96A35011-FD
>> 83-419D-939B-9A772EA2DF90&displaylang=en), ignore the compatibility
>> warning, or extract netdiag.exe only and copy it
>>
>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
>> (http://support.microsoft.com/kb/324801 applies also for
>> 2008/2008R2), FSMO should always be on the newest OS DC
>>
>> - after transfer of the PDCEmulator role, configure the NEW
>> PDCEmulator to an external timesource and reconfigure the old
>> PDCEmulator to use the domainhierarchie now. Therefore run on the NEW
>> "w32tm /config /manualpeerlist:PEERS /syncfromflags:manual
>> /reliable:yes /update" where PEERS will be filled with the ip address
>> or server(time.windows.com) and on the OLD one run "w32tm /config
>> /syncfromflags:domhier /reliable:no /update" and stop/start the time
>> service on the old one. All commands run in an elevated command
>> prompt without the quotes.
>>
>> - you can see in the event viewer (Directory service) that the roles
>> are transferred, also give it some time
>>
>> - reconfigure the DNS configuration on your NIC of the 2008 server,
>> preferred DNS itself, secondary the old one
>>
>> - if you use DHCP do not forget to reconfigure the scope settings to
>> point to the new installed DNS server
>>
>> Demoting the old DC(if needed)
>>
>> - reconfigure your clients/servers that they not longer point to the
>> old DC/DNS server on the NIC
>>
>> - to be sure that everything runs fine, disconnect the old DC from
>> the network and check with clients and servers the connectivity,
>> logon and also with one client a restart to see that everything is ok
>>
>> - then run dcpromo to demote the old DC, if it works fine the machine
>> will move from the DC's OU to the computers container, where you can
>> delete it by hand. Can be that you got an error during demoting at
>> the beginning, then uncheck the Global catalog on that DC and try
>> again
>>
>> - check the DNS management console, that all entries from the machine
>> are disappeared or delete them by hand if the machine is off the
>> network for ever
>>
>> - also you have to start AD sites and services and delete the old
>> servername under the site, this will not be done during demotion
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Dear Sir,
>>>
>>> We have a domain controller its very old harware Windows server2000.
>>> and its a large network, So we are planing to change hardware and
>>> migrate the users, Group Policies, etc etc... with Exchange server
>>> 2003. So sir please give me a suggestion regarding migration 2008
>>> server
>>>
>>> Regards,
>>> MRUA
>>> ----------------
>>> This post is a suggestion for Microsoft, and Microsoft responds to
>>> the
>>> suggestions with the most votes. To vote for this suggestion, click
>>> the "I
>>> Agree" button in the message pane. If you do not see the button,
>>> follow this
>>> link to open the suggestion in the Microsoft Web-based Newsreader
>>> and
>>> then
>>> click "I Agree" in the message pane.
>>> http://www.microsoft.com/communities...n-us/default.a
>>> sp
>>> x?mid=ad173f9c-9256-4d26-8062-d7e2630021c2&dg=microsoft.public.windo
>>> ws
>>> .server.migration

Thanks again Meinolf!


I am adding a new exchange 2010 server to the organization.

The procedure I am following will be:

1. Add one win 2008 R2 domain controller to parent and child domains.
2. follow procedure below to migrate server roles to win 2008 R2 servers.
3. Introduce an exchange 2010 server to organization.
4. Move mailboxes from exchange 2003 to exchange 2010
5. remove exchange 2003 server from organization.
6. remove AD from win 2000 sp4 domain controllers be demoting them to member
servers.

Does this sound like a good plan? Thanks.





"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
news:. com...
> Hello Raul,
>
> Also see:
> http://technet.microsoft.com/en-us/l...53(WS.10).aspx
>
> Windows server 2008 R2 functional level and Exchange 2003 Sp2 are not
> working together according to the Exchange Server Supportability Matrix:
> http://technet.microsoft.com/en-us/l...EXCHG.80).aspx
>
> So you should think about upgrading Exchange at least to version 2007 or
> better using Exchagne 2010 which should work with Windows server 2008 R2.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> Great instruction Meinolf!
>>
>> I am going through the same process except I am installing 2008 R2
>> server. Other that it was noted below, is there anything I should
>> differently for R2?
>>
>>> - if the new machine is domain controller and DNS server run again
>>> replmon, dcdiag on both domain controllers. For using netdiag.exe on
>>> 2008, NOT 2008 R2, you have to download and install
>>> (http://www.microsoft.com/downloads/d...id=96A35011-FD
>>> 83-419D-939B->9A772EA2DF90&displaylang=en), ignore the compatibility
>>> warning, or extract netdiag.exe only and copy it"
>>>
>> Currently I have one exchange server. How will the migration affect
>> it? Is there anything else I need to do besides updating the RUS
>> entries? please let me know. Thanks much!
>>
>> "Meinolf Weber [MVP-DS]" wrote in message
>> news:. com...
>>
>>> Hello Mohammed,
>>>
>>> To migrate to Windows server 2008 i would start with the forest level
>>> and then go to each child domain. I suggest to install the new 2008
>>> DCs as additional domain controllers and then move the FSMOs.
>>>
>>> !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR
>>> DATA/MACHINE!!!
>>>
>>> - For Exchange check the following articles:
>>> http://msexchangeteam.com/archive/20...16/446709.aspx
>>> http://msexchangeteam.com/archive/20...05/448338.aspx
>>>
>>> http://support.microsoft.com/?id=314649
>>>
>>> http://technet.microsoft.com/en-us/l...EXCHG.80).aspx
>>>
>>> http://theessentialexchange.com/blog...007/11/13/exch
>>> ange-server-2003-and-domain-controllers-a-summary.aspx
>>>
>>> http://support.microsoft.com/kb/822931/
>>>
>>> - On the old server open DNS management console and check that you
>>> are running Active directory integrated zone (easier for replication,
>>> if you have more then one DNS server)
>>>
>>> - run replmon from the run line or repadmin /showreps(only if more
>>> then one DC exist), dcdiag and netdiag from the command prompt on the
>>> old machine to check for errors, if you have some post the complete
>>> output from the command here or solve them first. For this tools you
>>> have to install the support\tools\suptools.msi from the 2000
>>> installation disk.
>>>
>>> - run adprep /forestprep and adprep /domainprep and adprep
>>> /domainprep /gpprep and adprep /rodcprep from the 2008 installation
>>> disk against the 2000 schema master(forestprep) / infrastructure
>>> master(domainprep/rodcprep), with an account that is member of the
>>> Schema/Enterprise/Domain admins, to upgrade the schema to the new
>>> version (44) or 2008 R2 (47)
>>>
>>> - you can check the schema version with "schupgr" or "dsquery *
>>> cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr
>>> objectVersion" without the quotes in a command prompt
>>> - Install the new machine as a member server in your existing domain
>>> - configure a fixed ip and set the preferred DNS server to the old
>>> DNS server only, think about disabling IPv6 if you are not using it,
>>> some known problems exist with it. Follow
>>> (http://blogs.dirteam.com/blogs/paulb...9/03/19/disabl
>>> ing-ipv6-on-windows-2008.aspx) to disable it
>>>
>>> - run dcpromo and follow the wizard to add the 2008 server to an
>>> existing domain, make it also Global catalog and DNS server.
>>>
>>> - for DNS give the server time for replication, at least 15 minutes.
>>> Because you use Active directory integrated zones it will
>>> automatically replicate the zones to the new server. Open DNS
>>> management console to check that they appear
>>>
>>> - if the new machine is domain controller and DNS server run again
>>> replmon, dcdiag on both domain controllers. For using netdiag.exe on
>>> 2008, NOT 2008 R2, you have to download and install
>>> (http://www.microsoft.com/downloads/d...id=96A35011-FD
>>> 83-419D-939B-9A772EA2DF90&displaylang=en), ignore the compatibility
>>> warning, or extract netdiag.exe only and copy it
>>>
>>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
>>> (http://support.microsoft.com/kb/324801 applies also for
>>> 2008/2008R2), FSMO should always be on the newest OS DC
>>>
>>> - after transfer of the PDCEmulator role, configure the NEW
>>> PDCEmulator to an external timesource and reconfigure the old
>>> PDCEmulator to use the domainhierarchie now. Therefore run on the NEW
>>> "w32tm /config /manualpeerlist:PEERS /syncfromflags:manual
>>> /reliable:yes /update" where PEERS will be filled with the ip address
>>> or server(time.windows.com) and on the OLD one run "w32tm /config
>>> /syncfromflags:domhier /reliable:no /update" and stop/start the time
>>> service on the old one. All commands run in an elevated command
>>> prompt without the quotes.
>>>
>>> - you can see in the event viewer (Directory service) that the roles
>>> are transferred, also give it some time
>>>
>>> - reconfigure the DNS configuration on your NIC of the 2008 server,
>>> preferred DNS itself, secondary the old one
>>>
>>> - if you use DHCP do not forget to reconfigure the scope settings to
>>> point to the new installed DNS server
>>>
>>> Demoting the old DC(if needed)
>>>
>>> - reconfigure your clients/servers that they not longer point to the
>>> old DC/DNS server on the NIC
>>>
>>> - to be sure that everything runs fine, disconnect the old DC from
>>> the network and check with clients and servers the connectivity,
>>> logon and also with one client a restart to see that everything is ok
>>>
>>> - then run dcpromo to demote the old DC, if it works fine the machine
>>> will move from the DC's OU to the computers container, where you can
>>> delete it by hand. Can be that you got an error during demoting at
>>> the beginning, then uncheck the Global catalog on that DC and try
>>> again
>>>
>>> - check the DNS management console, that all entries from the machine
>>> are disappeared or delete them by hand if the machine is off the
>>> network for ever
>>>
>>> - also you have to start AD sites and services and delete the old
>>> servername under the site, this will not be done during demotion
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> Dear Sir,
>>>>
>>>> We have a domain controller its very old harware Windows server2000.
>>>> and its a large network, So we are planing to change hardware and
>>>> migrate the users, Group Policies, etc etc... with Exchange server
>>>> 2003. So sir please give me a suggestion regarding migration 2008
>>>> server
>>>>
>>>> Regards,
>>>> MRUA
>>>> ----------------
>>>> This post is a suggestion for Microsoft, and Microsoft responds to
>>>> the
>>>> suggestions with the most votes. To vote for this suggestion, click
>>>> the "I
>>>> Agree" button in the message pane. If you do not see the button,
>>>> follow this
>>>> link to open the suggestion in the Microsoft Web-based Newsreader
>>>> and
>>>> then
>>>> click "I Agree" in the message pane.
>>>> http://www.microsoft.com/communities...n-us/default.a
>>>> sp
>>>> x?mid=ad173f9c-9256-4d26-8062-d7e2630021c2&dg=microsoft.public.windo
>>>> ws
>>>> .server.migration
>
>

Hello Raul,

For the AD part it sounds ok, keep in mind to have at least 2 DC/DNS/GC per
domain for failover and redundancy.

For exchange migration to 2010 i have no experience, so i strongly suggest
to use the exchnage newsgroups/forums BEFORE starting, to get best information
about it.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Thanks again Meinolf!
>
> I am adding a new exchange 2010 server to the organization.
>
> The procedure I am following will be:
>
> 1. Add one win 2008 R2 domain controller to parent and child domains.
> 2. follow procedure below to migrate server roles to win 2008 R2
> servers.
> 3. Introduce an exchange 2010 server to organization.
> 4. Move mailboxes from exchange 2003 to exchange 2010
> 5. remove exchange 2003 server from organization.
> 6. remove AD from win 2000 sp4 domain controllers be demoting them to
> member
> servers.
> Does this sound like a good plan? Thanks.
>
> "Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de> wrote in message
> news:. com...
>
>> Hello Raul,
>>
>> Also see:
>> http://technet.microsoft.com/en-us/l...53(WS.10).aspx
>> Windows server 2008 R2 functional level and Exchange 2003 Sp2 are not
>> working together according to the Exchange Server Supportability
>> Matrix:
>> http://technet.microsoft.com/en-us/l...EXCHG.80).aspx
>>
>> So you should think about upgrading Exchange at least to version 2007
>> or better using Exchagne 2010 which should work with Windows server
>> 2008 R2.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>> Great instruction Meinolf!
>>>
>>> I am going through the same process except I am installing 2008 R2
>>> server. Other that it was noted below, is there anything I should
>>> differently for R2?
>>>
>>>> - if the new machine is domain controller and DNS server run again
>>>> replmon, dcdiag on both domain controllers. For using netdiag.exe
>>>> on 2008, NOT 2008 R2, you have to download and install
>>>> (http://www.microsoft.com/downloads/d...lyid=96A35011-
>>>> FD 83-419D-939B->9A772EA2DF90&displaylang=en), ignore the
>>>> compatibility warning, or extract netdiag.exe only and copy it"
>>>>
>>> Currently I have one exchange server. How will the migration affect
>>> it? Is there anything else I need to do besides updating the RUS
>>> entries? please let me know. Thanks much!
>>>
>>> "Meinolf Weber [MVP-DS]" wrote in message
>>> news:. com...
>>>> Hello Mohammed,
>>>>
>>>> To migrate to Windows server 2008 i would start with the forest
>>>> level and then go to each child domain. I suggest to install the
>>>> new 2008 DCs as additional domain controllers and then move the
>>>> FSMOs.
>>>>
>>>> !!!NEVER START BEFORE HAVING CREATED AND TESTED A BACKUP OF YOUR
>>>> DATA/MACHINE!!!
>>>>
>>>> - For Exchange check the following articles:
>>>> http://msexchangeteam.com/archive/20...16/446709.aspx
>>>> http://msexchangeteam.com/archive/20...05/448338.aspx
>>>>
>>>> http://support.microsoft.com/?id=314649
>>>>
>>>> http://technet.microsoft.com/en-us/l...EXCHG.80).aspx
>>>>
>>>> http://theessentialexchange.com/blog.../2007/11/13/ex
>>>> ch ange-server-2003-and-domain-controllers-a-summary.aspx
>>>>
>>>> http://support.microsoft.com/kb/822931/
>>>>
>>>> - On the old server open DNS management console and check that you
>>>> are running Active directory integrated zone (easier for
>>>> replication, if you have more then one DNS server)
>>>>
>>>> - run replmon from the run line or repadmin /showreps(only if more
>>>> then one DC exist), dcdiag and netdiag from the command prompt on
>>>> the old machine to check for errors, if you have some post the
>>>> complete output from the command here or solve them first. For this
>>>> tools you have to install the support\tools\suptools.msi from the
>>>> 2000 installation disk.
>>>>
>>>> - run adprep /forestprep and adprep /domainprep and adprep
>>>> /domainprep /gpprep and adprep /rodcprep from the 2008 installation
>>>> disk against the 2000 schema master(forestprep) / infrastructure
>>>> master(domainprep/rodcprep), with an account that is member of the
>>>> Schema/Enterprise/Domain admins, to upgrade the schema to the new
>>>> version (44) or 2008 R2 (47)
>>>>
>>>> - you can check the schema version with "schupgr" or "dsquery *
>>>> cn=schema,cn=configuration,dc=domainname,dc=local -scope base -attr
>>>> objectVersion" without the quotes in a command prompt
>>>> - Install the new machine as a member server in your existing
>>>> domain
>>>> - configure a fixed ip and set the preferred DNS server to the old
>>>> DNS server only, think about disabling IPv6 if you are not using
>>>> it,
>>>> some known problems exist with it. Follow
>>>> (http://blogs.dirteam.com/blogs/paulb...009/03/19/disa
>>>> bl
>>>> ing-ipv6-on-windows-2008.aspx) to disable it
>>>> - run dcpromo and follow the wizard to add the 2008 server to an
>>>> existing domain, make it also Global catalog and DNS server.
>>>>
>>>> - for DNS give the server time for replication, at least 15
>>>> minutes. Because you use Active directory integrated zones it will
>>>> automatically replicate the zones to the new server. Open DNS
>>>> management console to check that they appear
>>>>
>>>> - if the new machine is domain controller and DNS server run again
>>>> replmon, dcdiag on both domain controllers. For using netdiag.exe
>>>> on 2008, NOT 2008 R2, you have to download and install
>>>> (http://www.microsoft.com/downloads/d...lyid=96A35011-
>>>> FD 83-419D-939B-9A772EA2DF90&displaylang=en), ignore the
>>>> compatibility warning, or extract netdiag.exe only and copy it
>>>>
>>>> - Transfer, NOT seize the 5 FSMO roles to the new Domain controller
>>>> (http://support.microsoft.com/kb/324801 applies also for
>>>> 2008/2008R2), FSMO should always be on the newest OS DC
>>>>
>>>> - after transfer of the PDCEmulator role, configure the NEW
>>>> PDCEmulator to an external timesource and reconfigure the old
>>>> PDCEmulator to use the domainhierarchie now. Therefore run on the
>>>> NEW "w32tm /config /manualpeerlist:PEERS /syncfromflags:manual
>>>> /reliable:yes /update" where PEERS will be filled with the ip
>>>> address or server(time.windows.com) and on the OLD one run "w32tm
>>>> /config /syncfromflags:domhier /reliable:no /update" and stop/start
>>>> the time service on the old one. All commands run in an elevated
>>>> command prompt without the quotes.
>>>>
>>>> - you can see in the event viewer (Directory service) that the
>>>> roles are transferred, also give it some time
>>>>
>>>> - reconfigure the DNS configuration on your NIC of the 2008 server,
>>>> preferred DNS itself, secondary the old one
>>>>
>>>> - if you use DHCP do not forget to reconfigure the scope settings
>>>> to point to the new installed DNS server
>>>>
>>>> Demoting the old DC(if needed)
>>>>
>>>> - reconfigure your clients/servers that they not longer point to
>>>> the old DC/DNS server on the NIC
>>>>
>>>> - to be sure that everything runs fine, disconnect the old DC from
>>>> the network and check with clients and servers the connectivity,
>>>> logon and also with one client a restart to see that everything is
>>>> ok
>>>>
>>>> - then run dcpromo to demote the old DC, if it works fine the
>>>> machine will move from the DC's OU to the computers container,
>>>> where you can delete it by hand. Can be that you got an error
>>>> during demoting at the beginning, then uncheck the Global catalog
>>>> on that DC and try again
>>>>
>>>> - check the DNS management console, that all entries from the
>>>> machine are disappeared or delete them by hand if the machine is
>>>> off the network for ever
>>>>
>>>> - also you have to start AD sites and services and delete the old
>>>> servername under the site, this will not be done during demotion
>>>>
>>>> Best regards
>>>>
>>>> Meinolf Weber
>>>> Disclaimer: This posting is provided "AS IS" with no warranties,
>>>> and
>>>> confers no rights.
>>>> ** Please do NOT email, only reply to Newsgroups
>>>> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>>>>> Dear Sir,
>>>>>
>>>>> We have a domain controller its very old harware Windows
>>>>> server2000. and its a large network, So we are planing to change
>>>>> hardware and migrate the users, Group Policies, etc etc... with
>>>>> Exchange server 2003. So sir please give me a suggestion
>>>>> regarding migration 2008 server
>>>>>
>>>>> Regards,
>>>>> MRUA
>>>>> ----------------
>>>>> This post is a suggestion for Microsoft, and Microsoft responds to
>>>>> the
>>>>> suggestions with the most votes. To vote for this suggestion,
>>>>> click
>>>>> the "I
>>>>> Agree" button in the message pane. If you do not see the button,
>>>>> follow this
>>>>> link to open the suggestion in the Microsoft Web-based Newsreader
>>>>> and
>>>>> then
>>>>> click "I Agree" in the message pane.
>>>>> http://www.microsoft.com/communities.../en-us/default
>>>>> .a
>>>>> sp
>>>>> x?mid=ad173f9c-9256-4d26-8062-d7e2630021c2&dg=microsoft.public.win
>>>>> do
>>>>> ws
>>>>> .server.migration