NT4 with Exchange 5.5 to SBS2003 R2 using ADMT

Hi,
I have a customer who wants me to do their migration from NT4 to SBS2003 R2.
Since I've never done it and I've lived on an NT4 domain for the last nine
years (don't fix what aint broke), I took the opportunity to use my own
domain as the guinea pig for a test migration. I found the ADMT help lacking
but, I was successful migrating the domain.
I actually spent several months sort of pregnant but duplicating the users
and key group, syncronizing the new sbs file server with the old file server
and then mapping user on the old dome to shares on the new domain. The only
snag with that was security which I was able to address.
Anyway, my question is about Exchange 5.5 and migrating to the new server;
when I do the ADMT migration will the message stores transfer as well?

Russ
Thu Mar 27 01:44:31 PDT 2008

Any NT4 Domains I don't bother.
Most of them are so messed up.

I just make sure I get everything Export mail, Copy Files and treat it as
they were in a workgroup.
(Of course I have to take the PC's out of the Domain before adding them
back.)

That is what I do, however others may have different opinions.

Russ

--

SBITS.Biz
Microsoft Gold Certified Partner
Microsoft Certified Small Business Specialist.
MCP, MCPS, MCNPS, (MCP-SBS)
North America Remote SBS2003 Support - http://www.SBITS.Biz
Information on Small Business Server 2008 - http://www.sbs2008.com
Information on Essentials Business Server - http://www.ebs2008.com



-

"VorDesigns" <VorDesigns@discussions.microsoft.com> wrote in message
news:9D1F3E75-4A01-4117-BC6C-37841DD5FA4A@microsoft.com...
> Hi,
> I have a customer who wants me to do their migration from NT4 to SBS2003
> R2.
> Since I've never done it and I've lived on an NT4 domain for the last nine
> years (don't fix what aint broke), I took the opportunity to use my own
> domain as the guinea pig for a test migration. I found the ADMT help
> lacking
> but, I was successful migrating the domain.
> I actually spent several months sort of pregnant but duplicating the users
> and key group, syncronizing the new sbs file server with the old file
> server
> and then mapping user on the old dome to shares on the new domain. The
> only
> snag with that was security which I was able to address.
> Anyway, my question is about Exchange 5.5 and migrating to the new server;
> when I do the ADMT migration will the message stores transfer as well?

Jim
Thu Mar 27 05:07:45 PDT 2008

I sat through an ADMT class 5 years ago with the scenario of doing
virtual servers to move from Exchange 5.5 to 2003. Long time ago and I
never actual did what we talked about in class outside of class. Study
guide is on the shelf and about an inch thick..
http://support.microsoft.com/kb/328871 That article does not seem to
have the gory stuff my hands on lab book has.

msexchange.com is probably where you need to be to do some research.
http://www.msexchange.org/tutorials/Exchange-55-Directory-Migration-Exchange-2003.html

Looking at the study guide you may need to migrate to Server 2003 and
Exchange 2003 before you migrate to SBS. There is talk about two way
trusts whcih SBS is not keen on. But I could be totally wrong on that.
On Wed, 26 Mar 2008 23:37:00 -0700, VorDesigns
<VorDesigns@discussions.microsoft.com> wrote:

>Hi,
>I have a customer who wants me to do their migration from NT4 to SBS2003 R2.
> Since I've never done it and I've lived on an NT4 domain for the last nine
>years (don't fix what aint broke), I took the opportunity to use my own
>domain as the guinea pig for a test migration. I found the ADMT help lacking
>but, I was successful migrating the domain.
>I actually spent several months sort of pregnant but duplicating the users
>and key group, syncronizing the new sbs file server with the old file server
>and then mapping user on the old dome to shares on the new domain. The only
>snag with that was security which I was able to address.
>Anyway, my question is about Exchange 5.5 and migrating to the new server;
>when I do the ADMT migration will the message stores transfer as well?
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx

Cris
Thu Mar 27 05:52:40 PDT 2008

This is a multi-part message in MIME format.

------=_NextPart_000_001D_01C88FD7.26740F20
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable

Actually, NT4 has been "broke" for sometime if you understand that no =
updates, etc. have been done for NT4 for a long time.
You would have been much better off (and taken a lot less time) to =
consider using the Swing Migration Kit at sbsmigration.com

As far as the Exchange...I'd consider running Exmerge to get the =
mailboxes out and then import them into Exchange 2003

--=20
Cris Hanna [SBS - MVP]
-----------------------------------------------------------
MVPs Do Not Work for Microsoft
Please do not contact me directly regarding issues
"VorDesigns" <VorDesigns@discussions.microsoft.com> wrote in message =
news:9D1F3E75-4A01-4117-BC6C-37841DD5FA4A@microsoft.com...
Hi,
I have a customer who wants me to do their migration from NT4 to =
SBS2003 R2.=20
Since I've never done it and I've lived on an NT4 domain for the last =
nine=20
years (don't fix what aint broke), I took the opportunity to use my =
own=20
domain as the guinea pig for a test migration. I found the ADMT help =
lacking=20
but, I was successful migrating the domain.
I actually spent several months sort of pregnant but duplicating the =
users=20
and key group, syncronizing the new sbs file server with the old file =
server=20
and then mapping user on the old dome to shares on the new domain. =
The only=20
snag with that was security which I was able to address.
Anyway, my question is about Exchange 5.5 and migrating to the new =
server;=20
when I do the ADMT migration will the message stores transfer as well?
------=_NextPart_000_001D_01C88FD7.26740F20
Content-Type: text/html;
charset="Utf-8"
Content-Transfer-Encoding: quoted-printable

=EF=BB=BF<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dutf-8">
<META content=3D"MSHTML 6.00.5730.13" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Actually, NT4 has been "broke" for =
sometime if you=20
understand that no updates, etc. have been done for NT4 for a long=20
time.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>You would have been much better off =
(and taken a=20
lot less time) to consider using the Swing Migration Kit at=20
sbsmigration.com</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>As far as the Exchange...I'd consider =
running=20
Exmerge to get the mailboxes out and then import them into Exchange=20
2003</FONT></DIV>
<DIV><BR>-- <BR>Cris Hanna [SBS -=20
MVP]<BR>-----------------------------------------------------------<BR>MV=
Ps Do=20
Not Work for Microsoft<BR>Please do not contact me directly regarding=20
issues</DIV>
<BLOCKQUOTE=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV>"VorDesigns" &lt;<A=20
=
href=3D"mailto:VorDesigns@discussions.microsoft.com">VorDesigns@discussio=
ns.microsoft.com</A>&gt;=20
wrote in message <A=20
=
href=3D"news:9D1F3E75-4A01-4117-BC6C-37841DD5FA4A@microsoft.com">news:9D1=
F3E75-4A01-4117-BC6C-37841DD5FA4A@microsoft.com</A>...</DIV>Hi,<BR>I=20
have a customer who wants me to do their migration from NT4 to SBS2003 =
R2.=20
<BR>&nbsp;Since I've never done it and I've lived on an NT4 domain for =
the=20
last nine <BR>years (don't fix what aint broke), I took the =
opportunity to use=20
my own <BR>domain as the guinea pig for a test migration.&nbsp; I =
found the=20
ADMT help lacking <BR>but, I was successful migrating the domain.<BR>I =

actually spent several months sort of pregnant but duplicating the =
users=20
<BR>and key group, syncronizing the new sbs file server with the old =
file=20
server <BR>and then mapping user on the old dome to shares on the new=20
domain.&nbsp; The only <BR>snag with that was security which I was =
able to=20
address.<BR>Anyway, my question is about Exchange 5.5 and migrating to =
the new=20
server; <BR>when I do the ADMT migration will the message stores =
transfer as=20
well?</BLOCKQUOTE></BODY></HTML>

------=_NextPart_000_001D_01C88FD7.26740F20--

Lanwench
Thu Mar 27 06:27:03 PDT 2008

VorDesigns <VorDesigns@discussions.microsoft.com> wrote:
> Hi,
> I have a customer who wants me to do their migration from NT4 to
> SBS2003 R2. Since I've never done it and I've lived on an NT4 domain
> for the last nine years (don't fix what aint broke), I took the
> opportunity to use my own domain as the guinea pig for a test
> migration. I found the ADMT help lacking but, I was successful
> migrating the domain.
> I actually spent several months sort of pregnant but duplicating the
> users and key group, syncronizing the new sbs file server with the
> old file server and then mapping user on the old dome to shares on
> the new domain. The only snag with that was security which I was
> able to address.
> Anyway, my question is about Exchange 5.5 and migrating to the new
> server; when I do the ADMT migration will the message stores transfer
> as well?

IMO, you're a lot better off doing a clean setup of SBS and copy the data
over manually. Use exmerge or manually export the mailboxes to PST. Then
exmerge them back in, or select/copy/paste the items from PST to mailbox in
outlook (don't import!).

I want to know what "sort of pregnant" means!

VorDesigns
Thu Mar 27 17:01:00 PDT 2008

Once I filter out the FUD line; thank you for the Exmerge suggestion.

I can agree, that as a consequence of the last critical patch I applied per
an MS tech bulletin, NT4 was broken by the patch; RRAS died. None the less,
domain authentication, share security enforcement and user rights, the core
functions and services all continue to work just fine.

From an intrusion standpoint, anyone running anything except maybe a
hardened *Nix Internet appliance on the WAN should have their fingers broken
and have their bathroom privileges takeen away. Dedicated use type firewalls
are a fact of Internet life and subsidiary on LAN aggregation of the same
type of devices for departments isn't a bad idea either. But that isn't what
this post is about. This is about refinishing a fine wood floor, not about
covering over the floor with Pergo because you don't know how to find a
craftsman.

"Cris Hanna [SBS-MVP]" wrote:
> Actually, NT4 has been "broke" for sometime if you understand that no updates, etc. have been done for NT4 for a long time.
> You would have been much better off (and taken a lot less time) to consider using the Swing Migration Kit at sbsmigration.com
>
> As far as the Exchange...I'd consider running Exmerge to get the mailboxes out and then import them into Exchange 2003
>
> --
> Cris Hanna [SBS - MVP]
> -----------------------------------------------------------
> MVPs Do Not Work for Microsoft
> Please do not contact me directly regarding issues
> "VorDesigns" <VorDesigns@discussions.microsoft.com> wrote in message news:9D1F3E75-4A01-4117-BC6C-37841DD5FA4A@microsoft.com...
> Hi,
> I have a customer who wants me to do their migration from NT4 to SBS2003 R2.
> Since I've never done it and I've lived on an NT4 domain for the last nine
> years (don't fix what aint broke), I took the opportunity to use my own
> domain as the guinea pig for a test migration. I found the ADMT help lacking
> but, I was successful migrating the domain.
> I actually spent several months sort of pregnant but duplicating the users
> and key group, syncronizing the new sbs file server with the old file server
> and then mapping user on the old dome to shares on the new domain. The only
> snag with that was security which I was able to address.
> Anyway, my question is about Exchange 5.5 and migrating to the new server;
> when I do the ADMT migration will the message stores transfer as well?

VorDesigns
Thu Mar 27 17:21:01 PDT 2008

Thank you, four EXMerge suggestions (I've asked others through different
channels) means that is the avenue to focus on.
I am intrigued that not one of you suggested I even think about using the
ADMT Exchange component.

Sort of pregnant defined: Scenario, NT4 domain (legacy domain for the
FUDrakers) and a brand spanking new SBS2003R2 server preloaded from DELL (I'm
busy and didn't want to build one from scratch). I was too busy to implement
the change over immediately on the test domain, basically my domain built
back in the late nineties.
My file server lost a drive in the mirror set so I was motivated to get the
file server portion of the new server running. To that end, I mapped the
shares for the file server onto the new server and robocopied the data onto
the new server. I created new users on the SBS domain (with errors which I'm
not going to go into, that is for my Wouldn't it make sense to you rant on a
different site). These user have the same name and password as the old
domain users.
I created new shares on the new sbs server, added new groups, allocated the
users to their respective groups, set security on the files and directories
at the server level, created shares and security.
Since the legacy domain and the brand spanking new SBS2003 domain shared the
same primary name with different classifiers (.net for the legacy, .local for
the new) and NETBIOS which really still uses WINS to handle where and who is
what on the LAN, mapping drives to the new shares was a simple modification
of the legacy domain logon scripts.
There you have sort of pregnant or the pre 1960's pull out method.
My users are still on the legacy domain but their files are on the new
domain and neither is the worse for wear.
I could have just left everything like that and continued on without a care
(the legacy DC uses an obselete Promise DriveDefender which has saved me
through five drive failures in nine years) but, I wanted to cut down the
amount of equipment running to green up a bit more.
At some point I'll pull the DELL noisemake out and put in an Antec unit to
make the unit whisper quiet.
"Lanwench [MVP - Exchange]" wrote:

>
> IMO, you're a lot better off doing a clean setup of SBS and copy the data
> over manually. Use exmerge or manually export the mailboxes to PST. Then
> exmerge them back in, or select/copy/paste the items from PST to mailbox in
> outlook (don't import!).
>
> I want to know what "sort of pregnant" means!
>
>
>