The AD database has been restored using an unsupported restoration procedure.

I have an SBS 2K server and a peer domain controller on my network.  We imaged the SBS computer to a new computer successfully.  However, when it was brought on to the network it did not sync up properly with the peer domain controller.  As a result, replication has been halted between the two domain controllers.  When the first domain controller is restarted, the netlogon service pauses.  The exchange information store and MTA stacks services do not start and have to be started manually.  Attempts to force replication manually failed.  I would like to remove the peer domain controller and clean up the Active Dir Db on the first domain controller.  Attempts to run Dcpromo on the peer failed.  Any ideas?

Event Type:       Error
Event Source:    NTDS General
Event Category: Service Control
Event ID:           2103
Date:                4/19/2006
Time:                9:19:26 PM
User:                Everyone

Computer:         SERVER1

The Active Directory database has been restored using an unsupported restoration procedure.
Active Directory will be unable to log on users while this condition persists. As a result, the Net Logon service has paused.
User Action

Event Type:       Warning
Event Source:    NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID:           1265
Date:                4/19/2006
Time:                10:09:26 PM
User:                N/A
Computer:         SERVER1

The attempt to establish a replication link with parameters
 Partition: CN=Schema,CN=Configuration,DC=Ism,DC=local
 Source DSA DN: CN=NTDS Settings,CN=CNC-SERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=Ism,DC=local
 Source DSA Address: c0af2b69-03a1-4a12-bc30-b3aaec7426ca._msdcs.Ism.local
Inter-site Transport (if any):

 failed with the following status:
 The destination server is currently rejecting replication requests.
 The record data is the status code.  This operation will be retried.

Data:0000: 09 21 00 00  

Event Type:       Warning
Event Source:    NtFrs
Event Category: None
Event ID:           13508
Date:                4/19/2006
Time:                9:21:32 PM
User:                N/A

Computer:         SERVER1
The File Replication Service is having trouble enabling replication from CNC-SERVER to SERVER1 for c:\winnt\sysvol\domain using the DNS name Cnc-Server.Ism.local. FRS will keep retrying.
 Following are some of the reasons you would see this warning.
 [1] FRS can not correctly resolve the DNS name Cnc-Server.Ism.local from this computer.
 [2] FRS is not running on Cnc-Server.Ism.local.
 [3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.

 This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
Data: 0000: 0d 00 00 00
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

First thing to note, that imaging domain controllers (especially on-line snapshot backup) is not a supported method of backup up a domain controller. Always use VSS or Active Directory-aware backup solutions for backing up domain controllers.

I think the best way to recover from this, is to restore a System State backup on the Small Business Server.

The problem "Active Directory database has been restored using an unsupported restoration procedure" is caused by resetting the database to a previous version without notifying replication partners of the restored database (like restoring an image). This is discussed in

The article is about Windows Server 2003 but should apply to Windows 2000 as well.

You can force removal of a domain controller by following instructions in

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Just out of curiosity, have you been able to restore the AD properly without the above error messages? There are some other questions about this topic and it'd be nice to know if this is a solution.

jeadams99Author Commented:
Yes.  We imaged and restored an entire computer to a totally different machine.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows 2000

From novice to tech pro — start learning today.