RE: strange access denied in ADMT v3

Thanks for your response Vincent.
Well I am using an account of old domain that is :
-member of the administrators group of old domain
-member of the domain admins group of old domain
-member of the administrators group of new domain.
But he cannot be part of the domain admins of the new domain( scope is
global ).
The only specific thing is that the domain admins group of old domain has
been renamed.

When I am using an account of new domain, I don't have the access denied on
admt. But I will have problems when I want to run the agent to migrate the
PCs since this account will not be part of the local admins. ( since it
cannot be part of the domain admins group of old domain ) .

How can I proceed ?
Thanks .


"Vincent Xu [MSFT]" wrote:

> Hi,
>
> Please make sure:
>
> The user account you logged on to run ADMT is added into:
>
> 1) Local Administrators group.
> 2) Target Domain Admin group
> 3) Source Domain Admin group.
>
> Hope it helps.
>
>
> Best regards,
>
> Vincent Xu
> 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.
>
>
> --------------------
> >>Thread-Topic: strange access denied in ADMT v3
> >>thread-index: AcX2Z39GtKTb5NycSfKcHXW5TATKIA==
> >>X-WBNR-Posting-Host: 217.167.147.251
> >>From: "=?Utf-8?B?Sm9lIFBhc3M=?=" <JoePass@xxxxxxxxxxxxxxxxxxxxxxxxx>
> >>Subject: strange access denied in ADMT v3
> >>Date: Thu, 1 Dec 2005 03:08:02 -0800
> >>Lines: 36
> >>Message-ID: <79FDA5EF-0205-4759-AB33-E884C4786126@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!TK2MSFTNGP08.phx.gbl!TK2MSFTNGXA03.phx.gbl
> >>Xref: TK2MSFTNGXA02.phx.gbl
> microsoft.public.windows.server.migration:21537
> >>X-Tomcat-NG: microsoft.public.windows.server.migration
> >>
> >>I have been using ADMT v2 for a while with other migration projects.
> >>I have a strange access rights issue with v3:
> >>Running it on the DC of the new domain with an account of old domain that
> is :
> >>-part of the administrators group of the new domain
> >>-and part of the domain admins group of the old domain
> >>
> >>I have following error:
> >>
> >>Source Domain
> >> Name: SOURCE
> >> DC: PDC
> >> OS: Windows NT 4.0
> >>Target Domain
> >> Name: dest.local (DEST)
> >> DC: dcdest.dest.local (DCDEST)
> >> OS: Windows Server 2003 5.2 (3790) Service Pack 1
> >> OU: LDAP://dest.local/OU=Migration,DC=dest,DC=local
> >>Intra-Forest: No
> >>Translate Option: Add
> >>Translate Files: Yes
> >>Translate Local Groups: Yes
> >>Translate Printers: Yes
> >>Translate Registry: Yes
> >>Translate Rights: Yes
> >>Translate Shares: Yes
> >>Translate User Profiles: Yes
> >>Conflict Option: Ignore
> >>Perform Pre-check Only: No
> >>
> >>[Object Migration Section]
> >>2005-11-25 17:50:15 Starting Account Replicator.
> >>2005-11-25 17:50:18 ERR3:7585 The account replicator is unable to
> continue.
> >> Access is denied.
> >>2005-11-25 17:50:18 Operation completed.
> >>
> >>Any ideas ? I'm stuck.
> >>
>
>
.

Relevant Pages

  • RE: Access Denied when using ADMT to migrage Computer Accounts
    ... the Domain Admins group will be added ... to the local Administrators group if the customer joins in the domain. ... Please add the user account to the local ...
    (microsoft.public.windows.server.migration)
  • RE: Best practice to migrate computer accounts - Query
    ... Add Win2k3Dom Domain admins group to NT Domain admins group and built-in ... Assume the account TEST is the NT domain account, ... Use user1 to logon to NT domain, you will find the profile is located to ... Logon to the win2k3dom DC and run ADMT to migrate user account user1. ...
    (microsoft.public.windows.server.migration)
  • Re: NT 4.0/Exchange 5.5 to Windows/Exchange 2003
    ... this kind of issues is caused by permission. ... migration does not require any special domain configuration. ... The account you use to run ADMT must have enough permissions to complete ... Add NT Domain Admin to Win2k3Dom Domain admins group and Win2k3Dom ...
    (microsoft.public.windows.server.migration)
  • Re: Failure Audit on Event Log
    ... Primary User Name: CAPACO-MCY$ ... Client Domain: CAPACOMCY ... But I include the account on Domain Admins group, ...
    (microsoft.public.windowsxp.general)
  • RE: Migration for WinNt 4 to Windows Server 2003
    ... Add Win2k3Dom Domain admins group to NT Domain admins group and built-in ... Assume the account TEST is the NT domain account, ... Use TEST to logon to the Win2k3Dom DC to perform ADMT migration. ... Use user1 to logon to NT domain, you will find the profile is located to ...
    (microsoft.public.windows.server.migration)