I would certainly use a recovered Workstation machine simply as a precaution. No matter what happens the first time the single DC goes down u are more than likely to be blamed so even as CYA exercise it's worth doing!!
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger Sent: 27 December 2004 20:16 To: [email protected] Subject: RE: [ActiveDir] JRNL_WRAP_ERROR with Single DC So, it looks like I want to do a Global non-authoritative (D2) restore first. If that does not work, I may need to do an authoritative (D4). I say this because under a D2 "the FRS database is rebuilt," which sounds like what I want. Also, MSKB 290762 says the D4 should be used only as a last resort. What is the impact of this problem? This client hired me to install a new server and build a new domain. They specifically do not want to upgrade or move directory data from the existing domain. This will all be done in the next 30 days. Can the existing system limp along until then? A separate question (extract can-o-worms opener from pocket): in very small environments, how does one address the "crime" of a single DC? In an office of 10-25 users, it is highly unlikely that management will pop for a server-class machine as a second DC. So should one use a repurposed workstation, for example, or do what most small offices do -- just stick with a single box. Thanks. -- nme -----Original Message----- From: David Adner [mailto:[EMAIL PROTECTED] Sent: Monday, December 27, 2004 8:35 AM To: [email protected] Subject: RE: [ActiveDir] JRNL_WRAP_ERROR with Single DC You may want to perform a D4 instead of a D2. A D4 will make that DC the "new" master source. In this case, you have no others DC's, so that would be the end of the process, but at least this way when you do deploy a second DC, they'll be able to replicate SYSVOL between each other successfully. I say "when you deploy a second DC" since it's criminal to have just a single DC unless you have absolutely 100% no regard for the Domain being wiped out due to a single server failure. As for the cause of a journal wrap, there are a few possibilities. Someone could have stopped the FRS service for an extended period of time, the FRS database could have become corrupt, etc. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Noah Eiger > Sent: Monday, December 27, 2004 00:55 > To: [email protected] > Subject: [ActiveDir] JRNL_WRAP_ERROR with Single DC > > Hi - > > Merry merry, happy happy everyone. > > I have inherited a single DC network (W2k SP4) that is > spitting out NTFRS errors (ID 13568) every time the server > (or service) restarts. Several online sources give > instructions for, what appears to be, forcing > synchronization. However, in this case, there is nothing with > which to synchronize. > > My questions are: with a single DC, how could I be getting > this error? And, is there anything I need to do about this > error? Does it really indicate corruption in the SYSVOL? > > Thanks. > > -- nme > List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/mail_list.htm List FAQ : http://www.activedir.org/list_faq.htm List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
