Re: Replication failure after restore

Thanks a lot.
Now I am removing the dfs targets that are hosted by the demoted DC (hostname of this server is Sgintfs02). I have 3 dfs namespaces:
I am able to display both the DfsDpt and DFSRIS in dfs mmc console but not the DFSRPT. It said "the specified domain either does not exist or could not be contacted".
That's the first problem.
 
When I want to remove the root target \\SGINTFS02\DfsDpt, it gave a warning followed by an error. I clicked 'Yes' to forcibly remove the root target, it gave the "The system cannot find the file specified" error. It seems that the root target is already removed but in the dfs mmc, it is still displayed there. How can I remove it from the display?
 
 
Good. Done those steps today but not yet repromote the server. I will have to go back to the office tomorrow to troubleshoot again to see why I cannot remotely connect the Remote Access server and the Exchange server. As the demoted server was a DHCP and DNS server, could it be the cause?
* take that DC off the network (while it is up, remove the cable)
 
* SEIZE the FSMO roles held by that bad DC to another live DC
 
* Cleanup the metadata of the bad DC (Make sure ALL the metadata is cleaned/removed from AD and replicated to other DCs)
 
* Forcebly demote the bad DC: DCPROMO /FORCEREMOVAL (end result is a stand alone server!!!)
 
* If needed REPROMOTE the stand alone server to an additional DC of an existing domain, make it a GC, transfer the FSMO roles back, reconfigure additional services like DNS/WINS accordingly if needed

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto #
BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
-----------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
-----------------------------------------------------------------------------
 

-----------------------------------------------------------------------------
So far the resolution stated in KBQ885875 is to demote the DC. As the DC host the major FSMO roles and it can't transfer the role to other DC at this state. How to best demote it?
Yes, use a normal backup to restore a DC!!! NEVER EVER USE AN IMAGE TO RESTORE A DC!!!
 
IMAGES/SNAPSHOTS are not AD aware when restoring. So I guess you have been having troubles because of a USN rollback
 
you can find more info at:
MS-KBQ885875_How to detect and recover from a USN rollback in Windows 2000 Server
MS-KBQ875495_How to detect and recover from a USN rollback in Windows Server 2003

--

Cheers,
(HOPEFULLY THIS INFORMATION HELPS YOU!)
# Jorge de Almeida Pinto #
BLOG --> http://blogs.dirteam.com/blogs/jorge/default.aspx
-----------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
-----------------------------------------------------------------------------
 

-----------------------------------------------------------------------------
I restored a Windows 2000 DC from a most recent ghost image, but it cannot replicate to and from other DCs. The DC within the same site gives the "target principal name is incorrect" when trying to replicate to this restore DC. The DC on the other site of the WAN link gives "Access is denied" when trying to replicate this DC.
 
Just less than a week ago I did forestprep and domainprep to my Windows 2000 domain so as to allow a Windows 2003 server to be promoted to DC into this domain. Unluckily today the Windows 2000 DC that host the PDC, RID, Infrastructure master could not completely startup (directory service database corrupted). The ghost image does not contains the changes to the AD of forestprep and domainprep.
 
Is there a way to resolve this replication problem?

Relevant Pages

  • Re: Disaster Recovery with NTBackup
    ... Windows Update may ... Win2K3 SP1 only (if not integrated into your SBS CD) ... Restore the backup using the document from the link I mentioned ... size equal to greater than the original server). ...
    (microsoft.public.windows.server.sbs)
  • Re: Disaster Recovery with NTBackup
    ... Windows Update may ... Win2K3 SP1 only (if not integrated into your SBS CD) ... Restore the backup using the document from the link I mentioned ... size equal to greater than the original server). ...
    (microsoft.public.windows.server.sbs)
  • Re: Disaster Recovery with NTBackup
    ... during the stage where it ask How to restore I ... The partitions are on the production and test server plus array ... required or not on an SBS 2003 ... Disaster test - Windows Product Activation problem ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 Std Restore
    ... weekend I will try to restore my server and I will get back later on with the ... server was at RTM or SP1/SP2 prior to the backup and then upgrade the ... reinstalled Windows base OS to that level before the restore. ... this doesn't tell us if Windows 2003 SP2 has been installed. ...
    (microsoft.public.windows.server.sbs)
  • RE: Upgrading W2K DC to W2003
    ... Windows Server 2003 DC and keep other Windows 2000 DCs untouched. ... Upgrading W2K DC to W2003 ...
    (microsoft.public.windows.server.migration)