| Author |
Message |
u4ic61
Guest
|
 Posted:
Tue Jan 04, 2005 10:29 am Post subject:
What about the client computers and member servers? |
|
|
Hi,
I am currently doing a test migration for a soon-to-happen production
migration of about 150 users from an NT4 domain, OLDDOMAIN , to a Windows
Server 2003 AD domain, NEWDOMAIN using a clean install (not in-place). The
upgrade will also include a migration from Exchange 5.5 to Exchange 2003. So
far the tests at the server-level are going great but I am trying to find
the best way to handle the client computers and member servers. Here are my
questions:
Short of going to each client computer, is there a way to do the following
things: Add the compters to the new domain, create a new user profile for
the new domain and copy the old user profile to the new user profile, and
set the Outlook Exchange profile properties to now look for the new server?
Should I be doing anything special with the member servers?
Is the ADMT "move computer" wizard supposed to do all of this for me?
Thank you for your help. |
|
| Back to top |
|
 |
Herb Martin
Guest
|
| Posted:
Tue Jan 04, 2005 11:09 am Post subject:
Re: What about the client computers and member servers? |
|
|
"u4ic61" <u4ic61@hotmail.com> wrote in message
news:eRmQvXh8EHA.3592@TK2MSFTNGP09.phx.gbl...
| Quote: | Hi,
I am currently doing a test migration for a soon-to-happen production
migration of about 150 users from an NT4 domain, OLDDOMAIN , to a Windows
Server 2003 AD domain, NEWDOMAIN using a clean install (not in-place). The
upgrade will also include a migration from Exchange 5.5 to Exchange 2003.
|
I always have to ask: Why not inplace?
(These systems are designed for upgrade.)
Name changes can be handled in NT before the upgrade if
that is the only serious issue.
| Quote: | So
far the tests at the server-level are going great but I am trying to find
the best way to handle the client computers and member servers. Here are
my
questions:
|
| Quote: | Short of going to each client computer, is there a way to do the following
things: Add the compters to the new domain, create a new user profile for
the new domain and copy the old user profile to the new user profile, and
set the Outlook Exchange profile properties to now look for the new
server? |
No -- well there might be ways to automate some of
this, scripts, utilities etc, but no way to make it really
seemless.
Upgrade.
| Quote: | Should I be doing anything special with the member servers?
|
Join the new domain or just UPGRADE.
| Quote: | Is the ADMT "move computer" wizard supposed to do all of this for me?
|
It will move the accounts but will not tell the computers
you did that.
Upgrade <grin>
--
Herb Martin |
|
| Back to top |
|
|
u4ic61
Guest
|
| Posted:
Tue Jan 04, 2005 11:53 am Post subject:
Re: What about the client computers and member servers? |
|
|
Unfortunately the client is set on doing it from scratch. Not my choice.
"Herb Martin" <news@LearnQuick.com> wrote in message
news:egNoD8h8EHA.3012@TK2MSFTNGP09.phx.gbl...
| Quote: | "u4ic61" <u4ic61@hotmail.com> wrote in message
news:eRmQvXh8EHA.3592@TK2MSFTNGP09.phx.gbl...
Hi,
I am currently doing a test migration for a soon-to-happen production
migration of about 150 users from an NT4 domain, OLDDOMAIN , to a Windows
Server 2003 AD domain, NEWDOMAIN using a clean install (not in-place).
The
upgrade will also include a migration from Exchange 5.5 to Exchange 2003.
I always have to ask: Why not inplace?
(These systems are designed for upgrade.)
Name changes can be handled in NT before the upgrade if
that is the only serious issue.
So
far the tests at the server-level are going great but I am trying to find
the best way to handle the client computers and member servers. Here are
my
questions:
Short of going to each client computer, is there a way to do the
following
things: Add the compters to the new domain, create a new user profile for
the new domain and copy the old user profile to the new user profile, and
set the Outlook Exchange profile properties to now look for the new
server?
No -- well there might be ways to automate some of
this, scripts, utilities etc, but no way to make it really
seemless.
Upgrade.
Should I be doing anything special with the member servers?
Join the new domain or just UPGRADE.
Is the ADMT "move computer" wizard supposed to do all of this for me?
It will move the accounts but will not tell the computers
you did that.
Upgrade <grin
--
Herb Martin
|
|
|
| Back to top |
|
|
Herb Martin
Guest
|
| Posted:
Tue Jan 04, 2005 12:00 pm Post subject:
Re: What about the client computers and member servers? |
|
|
"u4ic61" <u4ic61@hotmail.com> wrote in message
news:ekf4GHi8EHA.1392@tk2msftngp13.phx.gbl...
| Quote: | Unfortunately the client is set on doing it from scratch. Not my choice.
|
Sometimes you have to explain to the client that they
are shooting themselves in the foot OR you have to
understand what they really wish to achieve so you
can BOTH get them that (real) result and do it
efficiently (even if that means doing it the hard way
in the end.)
The client needs a reason -- you cannot (in general*)
pay me to waste someone's money or to screw up their
stuff.
*Ok, if you offer me millions and you understand the
objectsions I might take the money, but not just to get
a job.
If you do it correctly clients usually are impressed
when you talk them out of stupid ideas or eliminate
their misunderstandings and save them money. |
|
| Back to top |
|
|
Rebecca Chen [MSFT]
Guest
|
| Posted:
Tue Jan 04, 2005 3:48 pm Post subject:
Re: What about the client computers and member servers? |
|
|
Hello,
Yes, you need to use ADMT to migrate the user/computer/service account
instead of go to each machine to disjoin and rejoin into the new domain.
Please read the following article carefully:
Active Directory Migration Tool Overview
http://www.microsoft.com/windows2000/techinfo/planning/activedirectory/admt.
asp
You can download ADMT from the link below:
Windows 2000 Active Directory Migration Tool
http://www.microsoft.com/windows2000/downloads/tools/admt/default.asp
How To Set Up ADMT for Windows NT 4.0 to Windows 2000 Migration
http://support.microsoft.com/kb/260871/EN-US/
with regards to the user profile, ADMT has the ability to "translate"
account security information. The following link has addressed the details:
Remigrating User Accounts and Workstations in Batches
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deploy
guide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/de
ployguide/en-us/dssbi_reer_zgwe.asp
you can also use moveuser tool, which is in the Windows 2003 Server
Resource Kit. It will re-associate a profile with another user account.
It's specifically for this scenario where you need to move a profile from
local -> domain. One
thing to note is that this can't be done while the user is logged on. It
can however be done remotely so it could be scripted.
More details can be found in the following link:
Windows Server 2003 Resource Kit Tools
http://www.microsoft.com/downloads/details.aspx?FamilyID=9d467a69-57ff-4ae7-
96ee-b18c4790cffd&DisplayLang=en
Moveuser.exe: Move User
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techre
f/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techre
f/en-us/moveuser.asp
About the Exchange part, please post all Exchange related question to
microsoft.public.exchange.setup newsgroup to get more accurate information
from Exchange guy.
HTH!
Best regards,
Rebecca Chen
MCSE2000 MCDBA CCNA
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.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights. |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in