RE: Transfer roles
- From: v-amanwa@xxxxxxxxxxxxxxxxxxxx (Amanda Wang [MSFT])
- Date: Mon, 09 May 2005 10:10:52 GMT
Hello,
Thanks for your update.
1) You want to know if it is possible to setup the two new servers with
fresh copies of windows 03 and exchange on one of them. Then create a
trust between the NT and the new Win 03 domain, Copy over any data stored
on the NT servers, setup exchange to accept smtp.
>From your description, it looks like you want to migrate NT to 2k3. You
can use ADMT to migrate from NT to 2K3. However, I know your network is
not very large and we recommend you use upgrade to instead of migration
because migration is more complex. Meanwhile, we don't recommend you setup
exchange server on DC because it will cause some problems as following:
The only valid business cases for installing Exchange Server on a DC that I
have ever encountered are (1) budget limitations in an environment too
large to use Microsoft Small Business Server, and (2) when deploying
Exchange servers in locations where reliable WAN links are difficult or
impossible to purchase and implement. Exchange 2003 on a domain controller
is supported by Microsoft as a valid configuration, provided you adhere to
the following restrictions and limitations:
?¡è Exchange and Active Directory are both resource-intensive applications.
There are serious performance implications that result from running them
both on the same system.
?¡è The domain controller must also be a global catalog server.
?¡è Several directory-related components of Exchange 2003, namely DSAccess,
DSProxy and the message categorizer will not load-balance or failover to
any other domain controller or global catalog server.
?¡è You should not take advantage of the /3GB switch in Windows, as it
could cause Exchange to consume all available memory, effectively choking
out Active Directory.
?¡è System shutdown will take longer due to the order in which components
are automatically shutdown. This problem can be overcome by shutting down
Exchange prior to shutting down the operating system.
?¡è This configuration is less secure because Exchange administrators will
have local administrative access to Active Directory, enabling them to
elevate their privileges. In addition, any security vulnerability found in
Exchange or Active Directory exposes the other to attack and compromise.
?¡è Once Exchange has been installed on a computer, its role (e.g., domain
controller or member server) cannot be changed. Do not demote or promote
an Exchange 2003 computer. Doing so will break several components,
including Outlook Mobile Access, and Microsoft Product Support Services
does not support this.
?¡è Running clustered Exchange servers on cluster nodes that are also
domain controllers is not supported by Microsoft and should never be done
under any circumstances.
For more questions about Exchange, you'd best address in
Microsoft.public.exchange or exchange2000 to get the most efficient and
professional support.
2) Since their will be two domains, if i setup dhcp, dns etc on the new
machines will this cause problem with users logging on. Once my data has
been copied over and i have created user account on the new servers then
simply switch off the NTdomain and point the client pcs to the new domain.
After migration, it will not effect dhcp,dns etc on the new machines.
However, if two domains are in the same subnet, we cannot setup two DHCP
servers, that will cause the confusion. If eventually you will remove NT
domain, you can move DHCP database to win2k3 domain and then use win2k3
dhcp to assign the ip address for all clients. Please refer to the
following article about how to move DHCP:
How to move a DHCP database from a computer that is running Windows NT
Server 4.0, Windows 2000, or Windows Server 2003 to a computer that is
running Windows Server 2003
http://support.microsoft.com/default.aspx?scid=kb;en-us;325473
And after migration, you needn't create user account on the new servers
because there is a user account migration wizard during migration.
3) I would give you some references about migration from Win NT to Win 2k3:
First, I would like let you know the Recommended Migration Order and it is
listed below for your reference:
1. Trust migration (UI Only)
2. Service account migration
3. Domain Global Group
4. Domain Local Group
5. User migration
6. Computer migration
7. Security translation
8. Report
Second, for more reference about migraton:
Migrating from Windows NT Server 4.0 to Windows Server 2003
http://www.microsoft.com/downloads/details.aspx?FamilyID=e92cf6a0-76f0-4e25-
8de0-19544062a6e6&DisplayLang=en
You can download ADMT from the link below:
Windows 2000 Active Directory Migration Tool
http://www.microsoft.com/windows2000/downloads/tools/admt/default.asp
Active Directory Migration Tool Overview
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
asp
HTH!
Thanks & Regards
Amanda Wang [MSFT]
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================================
--------------------
>Thread-Topic: Transfer roles
>thread-index: AcVRhw6LDux52LlqQ7mO6S5fDms2Mw==
>X-WBNR-Posting-Host: 82.68.91.165
>From: =?Utf-8?B?bWFobWFk?= <mahmad@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <92BAA03F-1B7B-4AFB-8539-09B65DE9B899@xxxxxxxxxxxxx>
<K9gTNLUUFHA.3052@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: Transfer roles
>Date: Thu, 5 May 2005 08:28:15 -0700
>Lines: 185
>Message-ID: <6131CBA0-8398-4952-A0CB-D32A2E13FE8E@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.migration
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.migration:10030
>X-Tomcat-NG: microsoft.public.windows.server.migration
>
>Hi Amands,
>
>Thanks for your reply and its very helpful. I have another question,
since
>we only have 30 users at both of our offices and we currently dont host
our
>own exchange server, would it be possible to setup the two new servers
with
>fresh copies of windows 03 and exchange on one of them. Then create a
trust
>between the NT and the new Win 03 domain, Copy over any data stored on the
NT
>servers, setup exchange to accept smtp.
>
>Since their will be two domains, if i setup dhcp, dns etc on the new
>machines will this cause problem with users logging on. Once my data has
>been copied over and i have created user account on the new servers then
>simply switch off the NTdomain and point the client pcs to the new domain.
>
>Thanks for your help
>
>Mo
>
>"Amanda Wang [MSFT]" wrote:
>
>> Hello,
>>
>> Thanks for your post.
>>
>> I understand that you want to upgrade your network from Windows NT to
>> Windows 2k3 DC. If I have misunderstood, please feel free to let me
know.
>>
>> Based on my experience, I would reply to your main questions as
following:
>>
>> Q1: So what I want to know is can I now install Win 03 and exchange on
my
>> new server which will copy all user data from my test win 03 machine and
>> then I simply add my new server to the current NT domain to run in a
mixed
>> mode.
>>
>> We cannot do so because the test environment and production environment
are
>> separate and there is no communication between them. After you add this
>> new 2k3 DC into original NT domain, it cannot be recognized.
>>
>> Q2: I have bought two Dell 2800 servers. If I go the way of installing
NT
>> on the new servers I am only given the option to install Win 03 and Win
>> 2000 in Dell's Open manager. So my next question is how would I go
about
>> installing NT4 and bypass this and then create the partition etc.
>>
>> It should be related to Dell 2800 servers and about this question I
suggest
>> you'd better consult Dell engineer to get the most efficient and
suitable
>> reply.
>>
>> Meanwhile, I would give you another workaround about how to Upgrade to
>> Windows 2003 with hardware that does not support Windows NT 4.0.
>>
>> If you buy new hardware and find your new hardware will not support
Windows
>> NT 4.0. What do you do?
>>
>> First you will need to get a transition machine that can support both
>> Windows NT 4.0 and Windows 2003. This can be a workstation class
machine.
>> It will only be used as a transition server.
>>
>> Install Windows NT 4.0 on the transition machine. Install SP 6 also.
>> Make this machine a BDC to the existing Windows NT 4.0 domain.
>> Formulate your back out plan. (create a good back up, or take a domain
>> controller off line. )
>> Make sure replication has taken place.
>> Promote it to the Primary Domain Controller.
>> Plan your DNS. Will it be on the new DC or another machine.
>> Upgrade it to Windows 2003. AD is now installed.
>> Build a new Windows 2003 server on the new hardware.
>> Run dcpromo and make it a domain controller for the existing domain.
>> Move all FSMO rolls to the new domain controller. See FSMO What? Pull it
>> together and "How to view and transfer FSMO roles in Windows Server
2003".
>>
>> To Transfer FSMO rolls. To use the GUI, follow these steps: For the
domain
>> wide roles, Open Active Directory Users and Computers, right-click
Active
>> Directory Users and Computers, and then click "Connect" to Domain
>> Controller, In "Enter the name of another domain controller", type the
name
>> of the domain controller you want to hold the role or browse to it, then
>> right-click Active Directory Users and Computers, point to All Tasks.
Then
>> click Operations Masters, select the role you wish to change and click,
>> "change".
>>
>> It is a similar process for the Domain Naming Master, except you will be
>> using the Active Directory Domains and Trusts mmc console. For the
Schema
>> Master, Open the Active Directory Schema snap-in, right-click Active
>> Directory Schema and then click Change Domain Controller, Click Specify
>> Name and type the name of the domain controller that you want to hold
the
>> Schema Master role, right-click Active Directory Schema, and then click
>> Operations Master, simply click Change.
>>
>> I suggest you check the following KB articles to migrate to Win2k3 from
NT4:
>>
>> For more details, please refer to the following articles:
>>
>> How To Upgrade a Windows NT 4.0-Based PDC to a Windows Server 2003-Based
>> Domain Controller
>> http://support.microsoft.com/default.aspx?kbid=326209&product=winsvr2003
>>
>> Using Ntdsutil.exe to transfer or seize FSMO roles to a domain controller
>> http://support.microsoft.com/kb/255504
>>
>> Migrating Windows NT Server 4.0 Domains to Windows Server 2003 Active
>> Directory
>>
<http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4dom
>> toad.mspx>
>>
>> Upgrading from Windows NT Server 4.0 to Windows Server 2003
>>
http://www.microsoft.com/windowsserver2003/evaluation/whyupgrade/nt4/nt4tows
>> 03-2.mspx
>>
>> HTH!
>>
>> Thanks & Regards
>>
>> Amanda Wang [MSFT]
>>
>> Microsoft Online Partner Support
>>
>> Get Secure! - www.microsoft.com/security
>>
>> ====================================================================
>>
>> When responding to posts, please "Reply to Group" via your newsreader so
>> that others may learn and benefit from your issue.
>>
>> =====================================================================
>>
>> --------------------
>> >Thread-Topic: Transfer roles
>> >thread-index: AcVQoM/E8ILJR49BQp+Zg6LY4nUubg==
>> >X-WBNR-Posting-Host: 82.68.91.165
>> >From: =?Utf-8?B?bWFobWFk?= <mahmad@xxxxxxxxxxxxxxxxxxxxxxxxx>
>> >Subject: Transfer roles
>> >Date: Wed, 4 May 2005 05:00:06 -0700
>> >Lines: 31
>> >Message-ID: <92BAA03F-1B7B-4AFB-8539-09B65DE9B899@xxxxxxxxxxxxx>
>> >MIME-Version: 1.0
>> >Content-Type: text/plain;
>> > charset="Utf-8"
>> >Content-Transfer-Encoding: 7bit
>> >X-Newsreader: Microsoft CDO for Windows 2000
>> >Content-Class: urn:content-classes:message
>> >Importance: normal
>> >Priority: normal
>> >X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>> >Newsgroups: microsoft.public.windows.server.migration
>> >NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>> >Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>> >Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:10002
>> >X-Tomcat-NG: microsoft.public.windows.server.migration
>> >
>> >Hi,
>> >
>> >We currently have two sites both running NT4.
>> >
>> >Site one
>> >PDC and member server
>> >
>> >Site two
>> >BDC
>> >
>> >I have already carried out a test of a inplace upgrade as follows:
>> >
>> >Load NT4, join to current domain as BDC, remove from network and
>> >Promote to PDC
>> >Upgrade to Windows 03 with Exchange and AD
>> >
>> >
>> >So what i want to know is can i now install Win 03 and exchange on my
new
>> >server which will copy all user data from my test win 03 machine and
then
>> i
>> >simply add my new server to the current NT domain to run in a mixed
mode.
>> >
>> >Or is there a better way to go about this, I have bought two Dell 2800
>> >servers. If i go the way of installing NT on the new servers i am only
>> given
>> >the option to install Win 03 and Win 2000 in Dell's Openmanager. So my
>> next
>> >question is how would i go about installing NT4 and bypass this and
then
>> >create the partition etc.
>> >
>> >Thank for all your help
>> >
>> >MO
>> >
>> >
>>
>>
>
.
- References:
- Transfer roles
- From: mahmad
- RE: Transfer roles
- From: Amanda Wang [MSFT]
- RE: Transfer roles
- From: mahmad
- Transfer roles
- Prev by Date: RE: Netware -> MS2003 migration --- MSDSS / FMU log file manipulation
- Next by Date: ADMT v2 questions
- Previous by thread: RE: Transfer roles
- Next by thread: NT4->2003 Computer Account Migration Problem
- Index(es):
Relevant Pages
|
Loading
