Re: ADMT access denied error

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Frank,

Check out the post NT 4 Emulation in this same news group, dated 4/19/05 at
3:23 P.M.. This poster is having the same error 5 problem as you, Jason Tan
from MS is attempting to help him.

This may lead to a solution for you also.

good luck
hth
DDS W 2k MVP MCSE

"Frank Saxton" <Frank.Saxton@xxxxxxxxxxxxxxxxxx> wrote in message
news:d4689n01jgj@xxxxxxxxxxxxxxxxxxxxx
> Trying to migrate a Legacy NT4.0 environment over to the "latest and
> greatest".
>
> My current situation is that I have a w2k3 standard server running on new
> hardare that seems to more or less be working ok. When you log on from a
> PC, the user is presented with "this computer", the existing domain name
> and the new domain that belongs to w2k3 choices. Logging in to the new
> domain (provided there is an account there) works fine.
>
> If I can just get the existing domain user info over to the new w2k3
> machine, I should be good to go. Then, users would be able to log on to
> either the new domain or if there are problems, continue to log on to the
> old domain....
>
> I've read a lot of conflicting stuff about implementing the w2k3 server in
> an NT domain environment. I have no religious attachment to AD one way or
> another but it seems like this would be the better way to go. All of this
> depends on ADMT working which so far, it hasn't.
>
> What I need to know is what is the best way to get the current user info
> on the PDC over to the new w2k3 server? The answer seems to be to use
> ADMT but I am certainly open to other approaches. Right now, when I run
> ADMT I get an "access denied. error=5, domanin=PDC_domainname" error at
> the very last stage of the wizard. I'm doing this from the w2k3 box
> logged in as Administrator. Administrator is a member of Domain admin and
> Enterprise admin. There is a verified bi-directional trust relationship
> between the PDC and the w2k3 domains.
>
> I've seen several postings that address this same issue posted by others
> but have found the responses to be confusing and contradictory. For
> example, they talk about adding Administrator to the NT domain group
> which, as near as I can see, doesn't exist. And setting up moral user
> "test" accounts.
>
> Clearly, this is some type of a policies or permissions problem and is no
> doubt trivial to correct, if I can just get someone to tell me what needs
> to be done.
>
> Clear directions on how to satisfy this access denied complaint would be
> greatly appreciated!! Thanks very much in advance
>
>


.

Relevant Pages

  • Re: ADMT access denied error
    ... > Check out the post NT 4 Emulation in this same news group, ... >> and the new domain that belongs to w2k3 choices. ... >> What I need to know is what is the best way to get the current user info ... Administrator is a member of Domain admin ...
    (microsoft.public.windows.server.migration)
  • Re: (RD) expert advise needed
    ... Remote client from all different branch use XP RD to connect to main office server using W2k3. ... Al Jarvi (MS-MVP Windows Networking) ... Please post *ALL* questions and replies to the news group for the ...
    (microsoft.public.windowsxp.work_remotely)
  • Re: HKEY_LOCAL_MACHINE Registry Access
    ... from my W2K3 noSP box. ... > authenticate and what privileges are requested during logon. ... I connect to the remote registry with no problems. ...
    (microsoft.public.dotnet.languages.csharp)
  • Word documents with Zero File Size
    ... Having a bit of an issue with some W2K3 users and Word Documents: ... The issue is that some users are having Word Documents in their home folders ... The issue only affects users on the W2K3 server. ...
    (microsoft.public.windows.server.general)
  • Profilprobleme nach der Installation von W2K3
    ... wir haben 5 Lizenzen von W2K3 Standard Edition samt CAL's ... als Administrator und Ausführen der ersten Updates und ... Ich habe dann testweise die Maschinen wieder neu ... installiert, dieses Mal aber von W2K3 CD, der mit MSDN ...
    (microsoft.public.de.german.windows.server.general)