Re: Win2k3 -> Win2k3

Hi Jason,

Thank you for your reply. When you say temp domain, do you mean different
domain or the same domain? I've tried to create a scenario with virtual
machines, where I use the temp server as a DC that replicate the AD objects.
I'm able to seize the FSMO to the temp server, rebuilt the original server,
and do the same thing (i.e. promote as DC and transfer the FSMO). Problem is:
everything is copied.

As with ADMT, I need to create a new domain (I just learned that 2 days
ago). Thus, the problem using ADMT is that every PC has to be rejoined.
Please correct me if I miss your point. Thank you.

--
Lito Kusnadi
Technical Consultant
React Solutions AU


"Jason Tan" wrote:

Hello,

Thanks for posting!

Based on my experience, you may migrate users and computers accounts from
Windows 2003 domain to Windows 2003 domain using ADMT. However I think the
method could be somewhat time-consuming. The new Windows 2003 domain should
have different domain name from the original Windows 2003 domain.
Additionally the client workstations will rejoin the the new domain
automatically. You may refer to the following example.

1. Create temp domain TEMP as a temporary domain on the temporary box.
2. Migrate users and computers from domain A (original domain) to TEMP
domain.
3. Verify everything is Ok and retire domain A on the powerful server and
rebuild domain A. Migrate users and computers from TEMP back to domain A.

You may refer to the following information.

Active Directory Migration Tool v.2.0
<http://www.microsoft.com/downloads/details.aspx?FamilyID=788975b1-5849-4707-9817-8c9773c25c6c&DisplayLang=en>

326480 How to use Active Directory Migration Tool version 2 to migrate from
Windows 2000 to Windows Server 2003
<http://support.microsoft.com/default.aspx?scid=kb;EN-US;326480>

Hope the information helps. If there is anything that is unclear, please
feel free to let me know.

Best Regards,

Jason Tan

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.


"Lito Kusnadi" <LitoKusnadi@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C5444077-4B34-464B-8941-7858F658103F@xxxxxxxxxxxxxxxx
Hi,

This may be the simplest form of migration ever. I am a beginner in
windows
migration, so your advise is very valuable to me.
I have a server running Windows 2003 with AD mode on a powerful machine.
The
previous admin hasn't maintained the server in the past (i.e. instead of
using group policy, permission security hack and all sort of strange thing
is
configured on the server).
When the admin left, no one has any idea of what has happened in the
server.
The management told me to reload the server using the same machine. I am
looking of a way to migrate the user, group, and computer object from the
AD
so that I don't have to run around configuring every workstation one by
one.
I don't mind loosing the group policy, I just want to move user, group,
and
computer as I know rejoining the PC to the domain takes a lot of time.
I've heard the term swing migration and I understand that it is for SBS.
But
with ADMT, would I be able to move particular AD object so that I don't
need
to rejoin the workstation to the domain and so that there's no invalid
SSID?
Do you know what objects I need to move?
Could anyone point me to the right direction please (i.e. documentation of
how to do the migration)?
I am thinking of using a temporary server (running win 2003) to capture
only
the user, group, and computer from the AD; then after I reload a brand new
win 2003 on the real server, I can put the objects back. Is this possible?
Thank you in advance.
--
Lito Kusnadi
Technical Consultant
React Solutions AU



.

Relevant Pages

  • Re: SwingIt Pain and Suffering
    ... BTW - I did purchase the Advanced Windows Small Business Server 2003 Best Practices book and consumed large parts of it before starting this project. ... That being said, I do feel like his documentation could greatly benefit by having some more detailed check points for verifying the health of AD at various steps along the way, and what steps to take or resources to consult if the replication doesn't seem to be going according to plan. ... BTW, even after discovering this constraint and disabling the firewalls on my destination server as part of the base OS install, replication still initially failed and I was dumb founded to find the firewall reenabled. ... I did complete the AD replication from the migration computer to the destination computer as planned. ...
    (microsoft.public.windows.server.sbs)
  • Re: NT4 to 2003 with Dell2650
    ... PDC for good; ie Will the accounts stay on the PDC to allow me a testing ... The Recommended Migration Order is listed below for your reference: ... Yes, after completion of ADMT, you may logon to the new Windows Server 2003 ...
    (microsoft.public.windows.server.migration)
  • RE: migrating users and other from win2k to win2003
    ... You may migrate the users, NTFS permissions, IIS and DNS to the new Windows ... Server 2003 system by using the Active Directory Migration Tool. ... This article assumes that the source domain is a Windows 2000-based ...
    (microsoft.public.windows.server.migration)
  • RE: SMTP IIS6.0 -problem to send out external email
    ... Windows 2003 server. ... > on IIS service after migrating from Win2k to Win2k3. ... > migration, how do you migrate the application, does the application have ...
    (microsoft.public.windows.server.migration)
  • RE: Forwarding External IP Address to Internal Web Server Resource
    ... As I know, if the web site is a customer web site, the migration for SBS ... 2003 is similar with windows server 2003. ... Linux to Windows Migration Migrating Linux-Apache-MySQL-PHP to Windows 2000 ...
    (microsoft.public.windows.server.sbs)