RE: Domain List could not point to new domain automatically

anonymous_at_discussions.microsoft.com
Date: 08/22/04

  • Next message: JerryT: "RE: Win2K3 PDC not acting as time server"
    Date: Sun, 22 Aug 2004 12:03:05 -0700
    
    

    However, I tried to use another computer to reboot the
    migrated computer to finish the process, the problem
    appereed same as before.

    >-----Original Message-----
    >Hi Stephen,
    >
    >Personally, I do not think it is caused by the reboot
    after the
    >installation of ADMT. However, I am concerning if you
    have followed the
    >exact steps as described in KB articles.
    >
    >Have a nice day!
    >
    >Thanks & Regards,
    >
    >Feng Mao [MSFT], MCSE
    >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.
    >
    >
    >
    >--------------------
    >| Content-Class: urn:content-classes:message
    >| From: <anonymous@discussions.microsoft.com>
    >| Sender: <anonymous@discussions.microsoft.com>
    >| References: <7c0501c484b2$e7a5e2b0$a501280a@phx.gbl>
    ><9ugnU5QhEHA.3452@cpmsftngxa06.phx.gbl>
    ><8a1c01c48543$e5ea3110$a601280a@phx.gbl>
    ><$VT5RnZhEHA.584@cpmsftngxa10.phx.gbl>
    >| Subject: RE: Domain List could not point to new domain
    automatically
    >| Date: Thu, 19 Aug 2004 06:52:38 -0700
    >| Lines: 153
    >| Message-ID: <909901c485f3$ca01f6d0$a401280a@phx.gbl>
    >| MIME-Version: 1.0
    >| Content-Type: text/plain;
    >| charset="iso-8859-1"
    >| Content-Transfer-Encoding: 7bit
    >| X-Newsreader: Microsoft CDO for Windows 2000
    >| Thread-Index: AcSF88oBh4Fbe8D8RiCVZ3Hh4VTtcg==
    >| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
    >| Newsgroups: microsoft.public.windows.server.migration
    >| Path: cpmsftngxa10.phx.gbl
    >| Xref: cpmsftngxa10.phx.gbl
    microsoft.public.windows.server.migration:13088
    >| NNTP-Posting-Host: tk2msftngxa12.phx.gbl 10.40.1.164
    >| X-Tomcat-NG: microsoft.public.windows.server.migration
    >|
    >|
    >| I have a question: I install ADMT to the migrated
    computer
    >| and restart itself, is that the main point caused the
    >| logon domain cannot change to target domain
    automatically?
    >|
    >| >-----Original Message-----
    >| >Hi Stephen,
    >| >
    >| >Generally, when you use ADMT to migrate Computer
    account
    >| from one domain to
    >| >another, it will dispatch a migration agent to the
    >| computers. The migration
    >| >agent will help to change the logon domain. However,
    if
    >| the client cannot
    >| >get the agent, or the agent failed to be lauched. The
    >| user must change the
    >| >logon domain manually.
    >| >
    >| >Have a good day!
    >| >
    >| >Thanks & Regards,
    >| >
    >| >Feng Mao [MSFT], MCSE
    >| >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.
    >| >
    >| >
    >| >
    >| >--------------------
    >| >| Content-Class: urn:content-classes:message
    >| >| From: <anonymous@discussions.microsoft.com>
    >| >| Sender: <anonymous@discussions.microsoft.com>
    >| >| References: <7c0501c484b2$e7a5e2b0$a501280a@phx.gbl>
    >| ><9ugnU5QhEHA.3452@cpmsftngxa06.phx.gbl>
    >| >| Subject: RE: Domain List could not point to new
    domain
    >| automatically
    >| >| Date: Wed, 18 Aug 2004 09:53:33 -0700
    >| >| Lines: 84
    >| >| Message-ID: <8a1c01c48543$e5ea3110$a601280a@phx.gbl>
    >| >| MIME-Version: 1.0
    >| >| Content-Type: text/plain;
    >| >| charset="iso-8859-1"
    >| >| Content-Transfer-Encoding: 7bit
    >| >| X-Newsreader: Microsoft CDO for Windows 2000
    >| >| Thread-Index: AcSFQ+XqXZkFQNRKRtuFt2b+jdC/yA==
    >| >| X-MimeOLE: Produced By Microsoft MimeOLE
    V5.50.4910.0300
    >| >| Newsgroups: microsoft.public.windows.server.migration
    >| >| Path: cpmsftngxa06.phx.gbl
    >| >| Xref: cpmsftngxa06.phx.gbl
    >| microsoft.public.windows.server.migration:13181
    >| >| NNTP-Posting-Host: tk2msftngxa14.phx.gbl 10.40.1.166
    >| >| X-Tomcat-NG:
    microsoft.public.windows.server.migration
    >| >|
    >| >| Yes, this is the new domain
    >| >|
    >| >| However, after I using ADMT to migrate computer,
    >| >| then reboot the computer, the domain logon list
    >| >| pointed to old domain or local computer, not the
    >| >| new domain.
    >| >|
    >| >| After I changed to use new domain logon, all of
    >| >| them are normal. But we worry the user cannot
    >| >| know the concept of domain changed.
    >| >|
    >| >| I hope ADMT can change the domain list to be
    >| >| new domain that user can logon successfully without
    >| >| need to change the domain, do you have any idea?
    >| >|
    >| >| >-----Original Message-----
    >| >| >Hi Stephen,
    >| >| >
    >| >| >Thank you for posting!
    >| >| >
    >| >| >Could you please take a look to see if the computer
    >| >| account is in the new
    >| >| >domain?
    >| >| >
    >| >| >1. Right click My Computer
    >| >| >2. Choose Properties from context menu
    >| >| >3. In Computer Name tab, click Change button
    >| >| >4. Verify if your computer is in the new domain.
    >| >| >
    >| >| >Have a nice day!
    >| >| >
    >| >| >Thanks & Regards,
    >| >| >
    >| >| >Feng Mao [MSFT], MCSE
    >| >| >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.
    >| >| >
    >| >| >
    >| >| >
    >| >| >--------------------
    >| >| >| Content-Class: urn:content-classes:message
    >| >| >| From: "Stephen Fong" <stephen.fong@ceithk.com>
    >| >| >| Sender: "Stephen Fong" <stephen.fong@ceithk.com>
    >| >| >| Subject: Domain List could not point to new
    domain
    >| >| automatically
    >| >| >| Date: Tue, 17 Aug 2004 16:35:39 -0700
    >| >| >| Lines: 7
    >| >| >| Message-ID: <7c0501c484b2$e7a5e2b0
    $a501280a@phx.gbl>
    >| >| >| MIME-Version: 1.0
    >| >| >| Content-Type: text/plain;
    >| >| >| charset="iso-8859-1"
    >| >| >| Content-Transfer-Encoding: 7bit
    >| >| >| X-Newsreader: Microsoft CDO for Windows 2000
    >| >| >| X-MimeOLE: Produced By Microsoft MimeOLE
    >| V5.50.4910.0300
    >| >| >| Thread-Index: AcSEsuelT5zhw0RuSFqLIrK7uh0+TA==
    >| >| >| Newsgroups:
    microsoft.public.windows.server.migration
    >| >| >| Path: cpmsftngxa06.phx.gbl
    >| >| >| Xref: cpmsftngxa06.phx.gbl
    >| >| microsoft.public.windows.server.migration:13146
    >| >| >| NNTP-Posting-Host: tk2msftngxa13.phx.gbl
    10.40.1.165
    >| >| >| X-Tomcat-NG:
    >| microsoft.public.windows.server.migration
    >| >| >|
    >| >| >| I also have a testing with ADMT to migrate
    computer
    >| >| >| account and change it to another domain
    >| >| >|
    >| >| >| However, after I changed the account, why the
    domain
    >| >| list
    >| >| >| from logon screen cannot point to new domain
    >| >| automatically?
    >| >| >|
    >| >| >| Do you have any solutions?
    >| >| >|
    >| >| >
    >| >| >.
    >| >| >
    >| >|
    >| >
    >| >.
    >| >
    >|
    >
    >.
    >


  • Next message: JerryT: "RE: Win2K3 PDC not acting as time server"