Re: ADMT migration of computers

From: Keith Wada (kwada_at_sheppardmullin.com)
Date: 03/03/04


Date: Wed, 3 Mar 2004 10:33:48 -0800

Sorry for the delay in replying.

The problem has been happening with all desktops places in this "test" lab.

We migrated all of the Users/Groups prior to the desktops. The delay between
the users and desktop migration test phases ranged from 1 hour to 48

hours. We verified to make sure that all of the replication traffic

between the root and child (2003) domains were successful and timely. During
the testing we chose the 1min and 5min reboot time, both did not work. There
were no errors in the migration.log file that I could see.

I was able to get the desktops to reboot once I logged into the desktop as a

(source) domain admin user. Any other user logged in (target/source) or if

no one was logged into the desktop, the desktop would not reboot
automatically.

Keith

"Bob Qin [MSFT]" <bobqin@online.microsoft.com> wrote in message
news:EpZoxER$DHA.2452@cpmsftngxa06.phx.gbl...
> Hi Keith,
>
> Thanks for your posting here.
>
> I would like to know the following information.
>
> Does the problem occur on all the clients or just this certain one?
> Did you migrate user account before computer migration?
> How long did you put the client there after migration?
> Please choose 1min reboot in ADMT and only migrate computer account and
> groups. What is the result?
> Did you get any error in the migration.log?
>
> Thank you!
>
> Regards,
> Bob Qin
> Product Support Services
> Microsoft Corporation
>
> 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.
>



Relevant Pages

  • Re: Migration of user accounts from NT4 to 2003 AD
    ... also tried to remove the Registry key on the source NT DC and began ... it then asked to reboot the DC. ... I did a migration of that domain and it went through fine. ... The RestrictAnonymous value on the target domain controller should be ...
    (microsoft.public.windows.server.migration)
  • RE: Domain List could not point to new domain automatically
    ... I tried to use another computer to reboot the ... >installation of ADMT. ... The migration ... >|>agent will help to change the logon domain. ...
    (microsoft.public.windows.server.migration)
  • Re: ADMT v3 and computer accounts
    ... All you should have to do is request the reboot and it should belong to the ... be sure that this account has local admin rights other wise this piece will ... > I'm testing ADMTv3 and the Computer Migration Wizard. ... > Can anyone tell me whether or not the migrated computer will automatically ...
    (microsoft.public.windows.server.active_directory)
  • Re: migrating 4.3.3 to 5.3 on P series F80
    ... > migration. ... use alt_disk_install utility to clone one of your ... LATEST stuff *then* break rootvg mirroring -- unmirrorvg rootvg hdisk1. ... Reboot at convenience. ...
    (comp.unix.aix)
  • RE: Moving a file server to new domain
    ... Can a member server that is running web services or SQL server be moved with ... > Yes, to keep the original permissions, we have to use Computer Migration ... > Microsoft Online Partner Support ...
    (microsoft.public.windows.server.migration)