Re: Event-ID 2103 on all two domain controllers

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



Use Method 1 to solve the prblem, make sure that you also manually remove
the other server from the Active directory Sites and services, and that you
have at least one GC. In the end don't forguet to Enable inbound and
outbound replication again.

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"HeinzET" <HeinzET-web@xxxxxx> wrote in message
news:1154940237.313775.134990@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Jorge Silva wrote:
Drive imaging and rolling back of disks is not a supported Active
Directory
recovery.
How to detect and recover from a USN rollback in Windows Server 2003
http://support.microsoft.com/kb/875495/

--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"HeinzET" <HeinzET-web@xxxxxx> wrote in message
news:1154781160.907317.203980@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hallo I am new here, may be someone can help me. Tanks!

Every time when one of the two Domain controllers (windows 2000 SP4) is
started on this DC the logon service is paused. In the eventlog you can
find the ID 2103 (The active directory database has been restored using
an unsupported restoration procedure...). According to Microsoft
articel 885875 I demoted one of dc's, but on the surviving dc I still
get the ID 2103 and the logon service is paused. What can I do?


Hallo Jorge,

TankYou for your message and your help! I know the artikel 875495 its
the german translation of artikel 885875. My Problem is if there is
only one DC left (because I demoted the otherone) I still get the
Event-ID 2103. How can I solve this Problem?
Dcdiag shows the following Error
Starting test: frssysvol
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... BOSS passed test frssysvol
An Error Event occured. EventID: 0x00000010
Time Generated: 08/04/2006 18:18:34
(Event String could not be retrieved)
......................... BOSS failed test systemlog
Best regards
Heinz



.



Relevant Pages

  • Re: 2003 Migration
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: i got 6 server in company which contains NT4 , windows 2000 , windowser 2003
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: Urgent Advise - [WildPacket]
    ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to W2K3 Migration
    ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)