RE: ADMT local user profile migration



ADMT V2 did not let me transfer local profile. That is the why I downloaded
V3. I am opening new post with subject line: ADMTV3 Questions

Yes, with version 3, I was able to migrate user, computer, local profile.
--
Dipti


"Vincent Xu [MSFT]" wrote:

> Hi Dipti,
>
> Let's make the situation more clearly before we go anyfurther.
>
> From your post, I noticed that you are using ADMT V3 now.How about the ADMT
> V2?Did you use it successfully? As you said reran user migration once again
> on the same users and enable these account in target domain and after
> migration you found these account still disabled. Am I right? After you
> changed the password, the user account can be logged in, am I right?
>
> Regarding your second question, I think you need to migrate member server
> after the user profile migration is done.
>
> Let me know the question as above. Thanks.
>
> Best regards,
>
> Vincent Xu
> Microsoft Online Partner Support
>
> Get Secure! - www.microsoft.com/security
>
>
> --------------------
> >>Thread-Topic: ADMT local user profile migration
> >>thread-index: AcXJ8vpcJACDzRs6TSeDBkmLmZp56Q==
> >>X-WBNR-Posting-Host: 65.213.142.100
> >>From: "=?Utf-8?B?RGlwdGk=?=" <Dipti@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >>References: <828D60D1-72D2-4A79-9E5D-5EF2CB1BF9FF@xxxxxxxxxxxxx>
> <Rk5Q2QIpFHA.2700@xxxxxxxxxxxxxxxxxxxxx>
> <D0377CB3-D0BE-4222-94DB-B5D0808B233F@xxxxxxxxxxxxx>
> <9aKSA6UqFHA.1208@xxxxxxxxxxxxxxxxxxxxx>
> <7A7B2B7F-849C-4961-87A9-307F4406DFE4@xxxxxxxxxxxxx>
> <CzFBg8gqFHA.2152@xxxxxxxxxxxxxxxxxxxxx>
> <EBF5C5A2-49C3-4467-B6EF-7779649AD0AD@xxxxxxxxxxxxx>
> <nDxlePRtFHA.780@xxxxxxxxxxxxxxxxxxxxx>
> >>Subject: RE: ADMT local user profile migration
> >>Date: Wed, 5 Oct 2005 14:23:06 -0700
> >>Lines: 357
> >>Message-ID: <508928CC-FADC-4078-8548-840769C83B82@xxxxxxxxxxxxx>
> >>MIME-Version: 1.0
> >>Content-Type: text/plain;
> >> charset="Utf-8"
> >>Content-Transfer-Encoding: 8bit
> >>X-Newsreader: Microsoft CDO for Windows 2000
> >>Content-Class: urn:content-classes:message
> >>Importance: normal
> >>Priority: normal
> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >>Newsgroups: microsoft.public.windows.server.migration
> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>Xref: TK2MSFTNGXA01.phx.gbl
> microsoft.public.windows.server.migration:12249
> >>X-Tomcat-NG: microsoft.public.windows.server.migration
> >>
> >>Sorry, it took me so long to get back to you. After a long try with ADMT
> 2, I
> >>finally downloaded the ADMT V3. I have few observation which I want to
> share
> >>with you and get some feed back.
> >>
> >>here is the details.:
> >>
> >>
> >>
> >>Question s regarding ADMT V3.
> >>
> >>When migrating user accounts from source to target domain using “user
> >>migration wizard�, I initially chose to keep the migrated accounts
> disabled
> >>in target domain, and kept it enabled in source domain.
> >>
> >>I also tried to “migrate password�, but kept getting the error
> message
> >>“could not connect to PES server� even though I can ping the PES
> server in
> >>source domain from Target domain DC where I am running ADMT. I chose to
> >>select “create complex password�
> >>
> >>
> >>I migrated the local and global groups, migrated computer, user profile
> etc.
> >>using the group migration wizard, computer migration wizard
> >>
> >>I reran user migration once again on the same users, this time asking to
> >>enable accounts to target domain and disable after 30 days in source
> domain.
> >>
> >>
> >>Here are my problems:
> >>
> >>When I look at the AD user and computer, I see accounts are still
> disabled.
> >>I manually enable the accounts. When I try to log on to the target domain
> >>with the password generated by ADMT , I get the error message “access
> >>denied� I have to reset password manually. ( this is Ok in test domain
> but
> >>for production domain it is a big inconvenience).
> >>
> >>After migration, I checked the local profile (we do not use roaming
> >>profile). I see profiles are copied but drive mapping are not there. Also
> >>outlook profile did not transfer. I compared the username.newdomain
> folder
> >>with the username.olddomain folder. Seems OK.
> >>
> >>
> >>Now here is my test domain situation:
> >>
> >>I have two way trusts between domains in two forests. My file server and
> >>exchange servers are still in the source domain and preferably will be in
> >>this state for a while until I am able to migrate all users.. Given the
> >>situation, my question is do I need to migrate the file server and
> exchange
> >>server to the target domain for everything to work ?
> >>
> >>Thanks for any feed back you can provide me.
> >>
> >>--
> >>Dipti
> >>
> >>
> >>"Vincent Xu [MSFT]" wrote:
> >>
> >>> Hi,
> >>>
> >>> On the Source domain DC :
> >>>
> >>> 1. Make sure the DHCP server service is disabled.
> >>> 2. In DNS make sure the only forwarder listed is the internal IP
> address
> >>> of the Target Domain DC. To check this follow these steps:
> >>>
> >>> a. Go to Start, Programs, Administrative Tools, DNS.
> >>> b. Right click on the servername and choose Properties.
> >>> c. Click on the forwarders tab. The only IP listed should be the
> internal
> >>> IP of the Target Domain DC.
> >>>
> >>> 3. Make sure the Remote Procedure Call (RPC service) is running. The
> >>> default settings for RPC and RPC locator services are: Automatic and
> >>> Started.
> >>>
> >>>
> >>> On the Target domain DC:
> >>>
> >>> 1. Make sure the DHCP server service is running.
> >>> 2. Make sure the Remote Procedure Call (RPC) service is set to
> Automatic
> >>> and running. The RPC Locator service should be set to Manual and not
> >>> running.
> >>> 3. In DNS make sure the only IP listed in the Forwarders is the
> Internal
> >>> IP address of the source domain side.
> >>> 4. Check to see if the client machines have A (host) records in DNS.
> If
> >>> not, manually create host records and check the box to create the
> >>> associated PTR record. If the host records are there check for a PTR
> >>> record. If it is missing create it manually.
> >>>
> >>> On the Clients:
> >>>
> >>> 1. Make sure the Remote Procedure Call (RPC) service is running.
> >>> 2. Make sure that File and Print Sharing is checked on the properties
> of
> >>> the Local Area Connection.
> >>> 3. Make sure there is an IPC$ and Admin$ share.
> >>> 4. At a command prompt run IPConfig /release then IPConfig /renew.
> >>> Verify that the IP address is in the same range as the Target domain
> DC.
> >>>
> >>> Hope it helps.
> >>>
> >>> Best regards,
> >>>
> >>> Vincent Xu
> >>> Microsoft Online Partner Support
> >>>
> >>> Get Secure! - www.microsoft.com/security
> >>>
> >>>
> >>> --------------------
> >>> >>Thread-Topic: ADMT local user profile migration
> >>> >>thread-index: AcW0uNmBxIg1Sz8dTYSB54ohTovM8A==
> >>> >>X-WBNR-Posting-Host: 65.213.142.100
> >>> >>From: "=?Utf-8?B?RGlwdGk=?=" <Dipti@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >>> >>References: <828D60D1-72D2-4A79-9E5D-5EF2CB1BF9FF@xxxxxxxxxxxxx>
> >>> <Rk5Q2QIpFHA.2700@xxxxxxxxxxxxxxxxxxxxx>
> >>> <D0377CB3-D0BE-4222-94DB-B5D0808B233F@xxxxxxxxxxxxx>
> >>> <9aKSA6UqFHA.1208@xxxxxxxxxxxxxxxxxxxxx>
> >>> <7A7B2B7F-849C-4961-87A9-307F4406DFE4@xxxxxxxxxxxxx>
> >>> <CzFBg8gqFHA.2152@xxxxxxxxxxxxxxxxxxxxx>
> >>> >>Subject: RE: ADMT local user profile migration
> >>> >>Date: Thu, 8 Sep 2005 14:04:06 -0700
> >>> >>Lines: 301
> >>> >>Message-ID: <EBF5C5A2-49C3-4467-B6EF-7779649AD0AD@xxxxxxxxxxxxx>
> >>> >>MIME-Version: 1.0
> >>> >>Content-Type: text/plain;
> >>> >> charset="Utf-8"
> >>> >>Content-Transfer-Encoding: 7bit
> >>> >>X-Newsreader: Microsoft CDO for Windows 2000
> >>> >>Content-Class: urn:content-classes:message
> >>> >>Importance: normal
> >>> >>Priority: normal
> >>> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >>> >>Newsgroups: microsoft.public.windows.server.migration
> >>> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >>> >>Path: TK2MSFTNGXA02.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>> >>Xref: TK2MSFTNGXA02.phx.gbl
> >>> microsoft.public.windows.server.migration:20568
> >>> >>X-Tomcat-NG: microsoft.public.windows.server.migration
> >>> >>
> >>> >>I applied SP1 on 2003 server. Tried to migrate user local profile
> again,
> >>> I am
> >>> >>still getting the "RPC server unavailable" message. What is next?
> Account
> >>> I
> >>> >>am using for migration has domain admin rights.
> >>> >>--
> >>> >>Dipti
> >>> >>
> >>> >>
> >>> >>"Vincent Xu [MSFT]" wrote:
> >>> >>
> >>> >>> Hi,
> >>> >>>
> >>> >>> I think you mean the hotfix in KB823735,am I right? This hotfix is
> >>> >>> included in Windows 2003 SP1.
> >>> >>>
> >>> >>> To obtain Service Pack 1, please visit following link:
> >>> >>>
> >>> >>>
> >>>
> <http://www.microsoft.com/windowsserver2003/downloads/servicepacks/sp1/defau
> >>> >>> lt.mspx>
> >>> >>>
> >>> >>> Thanks.
> >>> >>>
> >>> >>> Best regards,
> >>> >>>
> >>> >>> Vincent Xu
> >>> >>> Microsoft Online Partner Support
> >>> >>>
> >>> >>> Get Secure! - www.microsoft.com/security
> >>> >>>
> >>> >>>
> >>> >>> --------------------
> >>> >>> >>Thread-Topic: ADMT local user profile migration
> >>> >>> >>thread-index: AcWpglZq+Lpjb8ojRaimsbxXkQxVxA==
> >>> >>> >>X-WBNR-Posting-Host: 65.213.142.100
> >>> >>> >>From: "=?Utf-8?B?RGlwdGk=?=" <Dipti@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >>> >>> >>References: <828D60D1-72D2-4A79-9E5D-5EF2CB1BF9FF@xxxxxxxxxxxxx>
> >>> >>> <Rk5Q2QIpFHA.2700@xxxxxxxxxxxxxxxxxxxxx>
> >>> >>> <D0377CB3-D0BE-4222-94DB-B5D0808B233F@xxxxxxxxxxxxx>
> >>> >>> <9aKSA6UqFHA.1208@xxxxxxxxxxxxxxxxxxxxx>
> >>> >>> >>Subject: RE: ADMT local user profile migration
> >>> >>> >>Date: Thu, 25 Aug 2005 07:36:11 -0700
> >>> >>> >>Lines: 219
> >>> >>> >>Message-ID: <7A7B2B7F-849C-4961-87A9-307F4406DFE4@xxxxxxxxxxxxx>
> >>> >>> >>MIME-Version: 1.0
> >>> >>> >>Content-Type: text/plain;
> >>> >>> >> charset="Utf-8"
> >>> >>> >>Content-Transfer-Encoding: 7bit
> >>> >>> >>X-Newsreader: Microsoft CDO for Windows 2000
> >>> >>> >>Content-Class: urn:content-classes:message
> >>> >>> >>Importance: normal
> >>> >>> >>Priority: normal
> >>> >>> >>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
> >>> >>> >>Newsgroups: microsoft.public.windows.server.migration
> >>> >>> >>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
> >>> >>> >>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>> >>> >>Xref: TK2MSFTNGXA01.phx.gbl
> >>> >>> microsoft.public.windows.server.migration:11784
> >>> >>> >>X-Tomcat-NG: microsoft.public.windows.server.migration
> >>> >>> >>
> >>> >>> >>Thanks for your reply. Now I know we do need to get that Hotfix
> >>> described
> >>> >>> in
> >>> >>> >>837366.
> >>> >>> >>--
> >>> >>> >>Dipti
> >>> >>> >>
> >>> >>> >>
> >>> >>> >>"Vincent Xu [MSFT]" wrote:
> >>> >>> >>
> >>> >>> >>> Hi Dipti,
> >>> >>> >>>
> >>> >>> >>> Regarding the error message, I'd like to provide some articles
> as
> >>> below:
> >>> >>> >>>
> >>> >>> >>> 837366 The Active Directory Migration Tool displays a "RPC
> server is
> >>> >>> >>> http://support.microsoft.com/?id=837366
> >>> >>> >>>
> >>> >>> >>> 823735 Active Directory Migration Tool Version 2 Uses the DNS
> Name
> >>> to
> >>> >>> >>> Resolve
.



Relevant Pages

  • RE: ADMT local user profile migration
    ... After a long try with ADMT 2, ... in target domain, and kept it enabled in source domain. ... using the group migration wizard, ... My file server and ...
    (microsoft.public.windows.server.migration)
  • RE: SidHistory and password migration with ADMT
    ... on the target domain. ... |Subject: RE: SidHistory and password migration with ADMT ... I let ADMT create it. ... |In target domain there are deafult user rights in registry ...
    (microsoft.public.windows.server.migration)
  • Re: Profile not following migrated user when using ADMT
    ... Thanks for your help....The profile is translated correctly when run from ... > How many objects did you migrated using the Remote site's ADMT? ... > delete as it may contain migration information). ... > |original ADMT DC so profiles will translate properly? ...
    (microsoft.public.windows.server.migration)
  • Re: Profile not following migrated user when using ADMT
    ... You can rename the profile folders for that newly created profiles ... |copying the protar.mdb file to DC in remote office and running the security ... |> How many objects did you migrated using the Remote site's ADMT? ... |> delete as it may contain migration information). ...
    (microsoft.public.windows.server.migration)
  • Re: Profile not following migrated user when using ADMT
    ... How many objects did you migrated using the Remote site's ADMT? ... We do not need to un-do the previous migration jobs. ... |Subject: Re: Profile not following migrated user when using ADMT ...
    (microsoft.public.windows.server.migration)

Loading