Hello everyone,
we recently lost a dc and replaced it...had to do the whole seize the fsmo
roles and everything...Anyway we recently discovered that all the servers are
looking for the gpt.ini file on the dead server....Does anyone know how to
point it to another live server? 
I'm also curious to know if the existing servers are even using the
GPO...Kind of like a ghost policy with no real enforcement.

Any insight to this would be greatly appreciated.

Thanks
Rick

Hello Rick,
The GPT.ini files are policy versions stored in your sysvol. If your
environment had proper replication, then all DCs in your domain should have
identical gpt.ini files. So it seems like all your policies where in the
lost DC and cuurent servers can't find policies etc in current sysvol. These
posts might be of help
http://support.microsoft.com/default.aspx?scid=kb;en-us;314494
http://support.microsoft.com/kb/290647/en-us
http://support.microsoft.com/kb/842804

Show quoteHide quote

Rick,

Rick Holland wrote:
Have you changed all server/client configuration regarding DNS so that
other machines don't refer to the dead server as the DNS server (either
primary or secondary)? How many DCs are left there?

Cheers,
Florian

Hello Rick,

The clients should not use the old server on the NIC as DNS server if it
is not available any longer.

Did you cleanup AD database from the old DC according to this one?
http://support.microsoft.com/kb/555846/en-us

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


Show quoteHide quote

Once you have followed the others suggestions, I would also like to add for
you to run diagnostics against your domain to verify that things are working
correctly.

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
-> dnslint /ad /s "ip address of your dc"

**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.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests without
having to learn all the switch options. The details will be output in
notepad text files that pop up automagically.

The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.

Description and download for dnslint
http://support.microsoft.com/kb/321045


Show quoteHide quote

What am I doing wrong? (Want to use Server 2003 R2 for Domain Cont
offline KB 810859
Home directory
Win2k3R2 Domain Preparing for Win2k8 Member & Domain Controllers
Domain renaming
User dis-join from domain, how to re-join again
Roamin Profiles
Quick question about two-way trust.
Unexplained time changes
duplicate SPN's