RE: Migration from 4.5 to 2003

From: Ray Fong [MSFT] (rayfong_at_online.microsoft.com)
Date: 08/03/04 

Date: Tue, 03 Aug 2004 13:19:10 GMT

1. Depends on how far you are in the migration. Anytime before moving the
computer accounts you can back off. Once you use ADMT to move the computer
accounts, they will belongs to the new domain. Anything goes wrong you can
unjoin/rejoin the machines back to the domain, or use ADMT to move it back.

2. Yes, in order for ADMT to migrate the profile, all machines needs to be
turn on, but logoff.

3. If you want to move them into the domain without manually unjoin/rejoin,
they need to be on the LAN.

Check out the paper and the last few pages on the advanced troubleshooting.
Make sure third party firewall is turn off. Verify File and Printer sharing
and client for MS networks are enabled at the server and clients. Verify
DNS name resolution across each SBS is working. I would remove all the ISP
DNSs and setup forwarders to point to each other. To be sure, run NSlookup
against each other and see if you can query anything at all. Finally,
backup, backup, backup.

Ray Fong
Microsoft SBS Product Support

This posting is provided "AS IS" with no warranties, and confers no rights.

>
>This weekend I will be migrating from 4.5 to a new server runing SBS2003
>
>I have read the migration document ( and some other posts on this board )
>
>I still have a few questions.
>
>1. Will my existing sbs server be left intact (including user, computer
and Email Accounts)? In other words if it goes wrong can I simply power off
the new server and continue using the old one?
>
>2. To enable the user desktop profiles to be migrated do the PCs need to
be switched on?
>
>3. What happens to laptops that are offsite?
>
>Are there any othe "Gotchas" to watch out for
>
>Thanks in advance
>
>Jon
>
>
>

Relevant Pages

  • Re: AD merge with exchange 2007 srv, can ADMT do it?
    ... > ADMT will do user and computer account migration. ... > "Exchange cross forest migration" and you will find some documentations. ... I usually do put together step by step docs such as this, to help folks in the newsgroups, but I haven't yet with this procedure because besides being scattered and the procedure having many facets, my notes are customer specific with domain names, user accounts, passwords, etc, that it will take me some time to go through to compile it into one doc, and I do apologize I am short on time to do anything with this at this point. ...
    (microsoft.public.windows.server.active_directory)
  • Re: ADMT Queries
    ... Are there any known issues by doing this during the migration, ... Backup - Perform daily/weekly/fortnight backup of the local ADMT ... 2.When DB is on a central SQL Server ...
    (microsoft.public.windows.server.migration)
  • Re: Win2k3 and E2k3 migration to SBS 2003
    ... Most users here have given up on ADMT ... and switched to Swing Migration. ... > Migration Wizard (MigWiz). ... >>>accounts and then using Exchange Migration Wizard ...
    (microsoft.public.windows.server.sbs)
  • Re: Win2k3 and E2k3 migration to SBS 2003
    ... Migration Wizard (MigWiz). ... property is populated on those ADMT migrated accounts. ... and tested process as a basis for this migration. ...
    (microsoft.public.windows.server.sbs)
  • RE: Exchange 5.5 to 2003 co-exist question
    ... Use ADMT with SID history for the migration. ... after the ADMT you should get no additional accounts in AD ... Move the Exchange 5.5 Mailboxes fast to 2003. ...
    (microsoft.public.exchange.admin)