Re: Microsoft from W2003 domain to SBS2003

Kieran,

It sounds as though a fresh install is better for you. Use exmerge to get
the Exchange data exported to PST and imported into the new store.

Gregg Hill


"Kieran F" <KieranF@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CEAD0577-958D-47C2-BACB-25B2C36BBFF0@xxxxxxxxxxxxxxxx
ADMT does require trusts - i dont care about migrating over accounts - the
only reason to preserve them is to that they match up with Exchange
accounts.
Will i need matching accounts in the new AD to migrate the Exchange
accounts
across?

There are no workstations in the domain - long story - dont go there.

Cheers for the advice on the .local - we use macs so this will help.

The reason i want to migrate to a new AD is that i'd like to leave the
current system as is. Its unreliable and i simply dont have the time to
troubleshoot the current problems. I'd rather leave it as is and then
migrate
services across.

"Gregg Hill" wrote:

A swing is great IF you want to keep your internal domain name, server
name,
and IP address. It sounds as though this is NOT what you want. BTW, do
not
use the .local domain suffix; it can conflict with Macs. Use .lan or
something like that.

You can rename the domain BEFORE you install SBS, but from what I hear,
it
is not easy, in spite of the MS domain rename tool.

You can exmerge the Exchange data. I'm not sure about ADMT. Doesn't it
require a trust?

When you say the current servers are unreliable from a software
standpoint,
what do you mean by that? Is AD intact and error-free (install the
support
tools to check it with dcdiag and netdiag)?

Gregg Hill



"Kieran F" <KieranF@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:679C6D79-6D47-4D6A-9360-72164249E589@xxxxxxxxxxxxxxxx
Fair point, but can you advise on any of the questions raised below in
regards to doing the work without the product. I'd get it if required,
but
i
just want to know if what i'm asking is possible.

From other reading, i notice that domain renaming isn't possible in SBS
2003.

My question is - If i chose not to use the swing migration method - can
i
just setup
my SBS 2003 system, migrate users over (from the 2003 domain) with ADMT
v3
and then do an Exchange pst merge to get the Exchange data across?

"Kevin Weilbacher [SBS-MVP]" wrote:

Kieran, as far as addressing the questions you have as to what
SBSMigration
tool can or cannot do for you, it would be best to communicate with
Jeff
Middleton (the author of SBS Migration) directly:
http://www.sbsmigration.com/contact.php

--
Kevin Weilbacher [SBS-MVP]
"The days pass by so quickly now, the nights are seldom long"


"Kieran F" <KieranF@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C5B5242A-F832-4760-BD5B-2500B8C281AA@xxxxxxxxxxxxxxxx
Hi All,

Started working at a company several months ago and they're
currently
running their 2003 domain in an unsupportable state. The primary
issues
are
servers are unreliable (both at the hardware and software level),
Exchange
is
currently unreliable, internal DNS is the same as the external which
is
causing resolution problems and everyone changes the system at their
whim.

I'd like to swap over to a SBS 2003 system, lock it down and get
back
to
my
actual role. I've done AD architecture before - i just never used
SBS

I've noticed that sbsmigration seems to be a good resource that is
consistenly recommended, i just have the following questions:
- We've got a MS action pack that allows us SBS2003 + 2003 R2 - can
a
R2
server join a domain and then yet AD Promo'd as an alternate
DC/DNS/DHCP?
- If we use the swing migration, we'd go over to a server with the
same
name and IP as domain name correct?
- If so for the above, i'd ideally like to change all 3 of the above
(name,
IP and domain name) from company.com to company.local - can this be
done
- If i chose not to use the swing migration method - can i just
setup
another SBS 2003 system, migrate users over with ADMT v3 and then do
an
Exchange pst merge to get data across? I can't afford to lose any
email
in
the process!

Thanks in advance,

Kieran








.

Relevant Pages

  • Re: Exchange/Outlook 2003 - group policy & local PST files
    ... Exchange 2003 SP2 is applicable to SBS 2003! ... It won't move existing PST files. ... so I already have found the settings I want to modify ...
    (microsoft.public.windows.server.sbs)
  • Re: Exchange/Outlook 2003 - group policy & local PST files
    ... We're running the SBS 2003 version of Exchange - to my knowledge, ... Otherwise, if an ANSI PST exists anywhere in the user's profile, it'll create an ANSI PST, which will have a 2 GB size limit. ... consistent AutoArchive settings as well as a common location for the ...
    (microsoft.public.windows.server.sbs)
  • Re: new installation questions..
    ... > installation with 2 NICs and a router (DHCP handled by SBS). ... How do I get my existing emails out of outlook and into exchange? ... > save the pst, reconfigure outlook for Exchange, then somehow load the pst ...
    (microsoft.public.backoffice.smallbiz)
  • Re: Help - Cannot Open *Some* Messages with Outlook...?
    ... used the ExMerge tool to import the PST to the SBS ... Outlook 2000 was configured as ... >> Exchange server, all is OK. ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 4.0 - SBS 2003
    ... Since it is Exchange 5.0, That was my thinking about the PST. ... So your recommendation is to the leave Outlook with PST afterwards? ... > Have you looked at the migration documents found on the SBS Website ... but I would then import back to the Exchange server and start ...
    (microsoft.public.backoffice.smallbiz)