Re: Adding a 2003 DC to an existing 2000 AD

Tech-Archive recommends: Fix windows errors by optimizing your registry

Thanks for the info. I ran the diagnostics you suggested and I have numerous
errors on both systems. However, I have found something extremely troubling.
I went to run the DNS manager on our secondary DC and noted that DNS manager
was not available. I also noted the Active Directory Manager for Users and
Computers was not available. Is this normal?

"Paul Bergson [MVP-DS]" wrote:

I agree, resolve the dns issues.

Run diagnostics against your Active Directory domain.

If you don't have the support tools installed, install them from your server
install disk.
d:\support\tools\setup.exe

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt

**Note: Using the /E switch in dcdiag will run diagnostics against ALL dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take
into account slow links to dc's will also add to the testing time.

When complete search for fail, error and warning messages.


--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.

"Danny Sanders" <DSanders@xxxxxxxxxxxxxxx> wrote in message
news:uxi$x7luHHA.4412@xxxxxxxxxxxxxxxxxxxxxxx
I'm not to concerned about the DNS warnings.
However, I'm a little reluctant in running the the ADPREP while there are
errors concerning group policy. What do you think?

Solve those DNS warnings. AD is TOTALLY tied to DNS. Solve those DNS
errors and the group policy errors may go away.

hth
DDS


"Ted W" <TedW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:59064529-661F-446B-829F-F164D7B50504@xxxxxxxxxxxxxxxx
Thanks for the info. I also noted on our servers event viewer that we
have
some error conditions pertaining to group policy in the Application Log
and
warnings in the DNS Server Log. I'm not to concerned about the DNS
warnings.
However, I'm a little reluctant in running the the ADPREP while there are
errors concerning group policy. What do you think?


"Paul Bergson [MVP-DS]" wrote:

Microsoft recommends (It should be requires but it isn't) that all dc's
are
at sp4. If not then you need to make sure all the Windows 2000 domain
controllers must have an Ntdsa.dll file whose date stamp and version is
later than June 4th, 2001 and 5.0.2195.3673. If you can apply sp4 I
would
do it.

For more info see the link below, specifically step 2:
http://support.microsoft.com/kb/325379

--
Paul Bergson
MVP - Directory Services
MCT, MCSE, MCSA, Security+, BS CSci
2003, 2000 (Early Achiever), NT

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no
rights.

"Ted W" <TedW@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:DAFC96D8-FB7B-432C-A5BE-63B5894F3CFD@xxxxxxxxxxxxxxxx
We currently have a domain with 2 W2K DCs, one primary and a member.
The
primary has been upgraded to SP4. I noted one article in the
Knowledgebase
concerning hotfixes and service packs but they stop at SP3. With my
current
configuration should I expect any problems running adprep and what
things
should I be looking out for?

Thanks,

Ted









.

Relevant Pages

  • Re: GPO doesnt take effect on the clients
    ... That is set in the network properties to pick up the DNS ... So 192.168.150.101 is your Active Directory Domain Controller, ... Microsoft MVP - Windows Server - Group Policy. ...
    (microsoft.public.windows.group_policy)
  • Re: Windows firewall spontaneously changes profiles
    ... If you want to get your Active Directory and Group Policy to work correctly ... to have your domain controllers be dns servers for your Active Directory ...
    (microsoft.public.windows.server.security)
  • Re: Adding a 2003 DC to an existing 2000 AD
    ... I agree, resolve the dns issues. ... If you don't have the support tools installed, ... Solve those DNS warnings. ... errors and the group policy errors may go away. ...
    (microsoft.public.win2000.active_directory)
  • Re: Configuring DNS settings
    ... and DNS settings.Now I need to change the DNS settings for all clent machines.Individually going and doing on all PC's will be tediuos. ... You need to script that as there is no native Group Policy for it. ... Be aware that pointing all clients to a wrong DNS server might break your entire Directory Server (Active Directory) with Group Policy. ... I recommend you really test the script in a test environment. ...
    (microsoft.public.windows.group_policy)
  • Re: Group Policy on a Win2K domain wont apply to an XP Pro workstation.
    ... Active Directory ... then check that the Tcp/Ip settings for DNS on the XP ... client is identical to that on the working W2k. ... >>Group policy application onto XP clients works. ...
    (microsoft.public.windowsxp.security_admin)