Lost all Containers and DC Server 2008 R2 - URGENT - HELP!!!

[mrtechno77]

I am the administrator on a school network. At the end of each school year we have to delete the 8th grade OU and then rename all the other grades to move the students into the correct grade, We upgraded to Server 2008 last year. I tried to delete the old OU using the instructions in this link -

http://technet.microsoft.com/en-us/library/cc736842(v=ws.10).aspx

- but I still got an error. When I closed and reopened ADUC I found all my containers were gone and my server no longer the DC.
I stopped by the school and I was able to log on to a few different computers with different user accounts. I was also able to access network resources. Apparently all the information is still there but I need to get all of my folders etc back in ADUC because as it stands I can not add any new users (we have several new students and staff members to add) nor can I add any new computers. Please help in this matter.
Here is the result of DCDIAG

TEST: Authentication (Auth)
Authentication test: Successfully completed

TEST: Basic (Basc)
The OS
Microsoft Windows Server 2008 R2 Enterprise (Service Pack lev
el: 1.0)
is supported.
NETLOGON service is running
kdc service is running
DNSCACHE service is running
DNS service is running
DC is a DNS server
Network adapters information:
Adapter [00000007] Broadcom NetXtreme Gigabit Ethernet:
MAC address is 00:0F:20:F8:FD:69
IP Address is static
IP address: 192.168.0.3, fe80::a0ab:8067:40e:8411
DNS servers:
192.168.0.3 (win-p2fq0ms56nl.huntingtoncatholic.local.)
[Valid]
The A host record(s) for this DC was found
The SOA record for the Active Directory zone was found
The Active Directory zone on this DC/DNS server was found prim
ary
Root zone on this DC/DNS server was not found

TEST: Forwarders/Root hints (Forw)
Recursion is enabled
Forwarders are not configured on this DNS server
Root hint Information:
Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid
(unreachable)]
Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
Name: d.root-servers.net. IP: 128.8.10.90 [Valid]
Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unre
achable)]
Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unre
achable)]
Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid
(unreachable)]
Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreac
hable)]
Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (
unreachable)]
Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreach
able)]
Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unre
achable)]
Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreac
hable)]
Name: m.root-servers.net. IP: 202.12.27.33 [Valid]

TEST: Delegations (Del)
Delegation information for the zone: huntingtoncatholic.local.

Delegated domain name: _msdcs.huntingtoncatholic.local.
DNS server: win-p2fq0ms56nl.huntingtoncatholic.local. IP
:192.168.0.3 [Valid]

TEST: Dynamic update (Dyn)
Test record dcdiag-test-record added successfully in zone hunt
ingtoncatholic.local
Test record dcdiag-test-record deleted successfully in zone hu
ntingtoncatholic.local

TEST: Records registration (RReg)
Network Adapter
[00000007] Broadcom NetXtreme Gigabit Ethernet:
Matching CNAME record found at DNS server 192.168.0.3:
6dda1413-b937-4da3-a83d-e6c12207340c._msdcs.huntingtoncatho
lic.local

Matching A record found at DNS server 192.168.0.3:
hcsserver.huntingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_ldap._tcp.huntingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_ldap._tcp.365b977d-5362-45cf-8938-c6ddc399aa9a.domains._ms
dcs.huntingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_kerberos._tcp.dc._msdcs.huntingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_ldap._tcp.dc._msdcs.huntingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_kerberos._tcp.huntingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_kerberos._udp.huntingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_kpasswd._tcp.huntingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_ldap._tcp.Default-First-Site-Name._sites.huntingtoncatholi
c.local

Matching SRV record found at DNS server 192.168.0.3:
_kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.hun
tingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.hunting
toncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_kerberos._tcp.Default-First-Site-Name._sites.huntingtoncat
holic.local

Matching SRV record found at DNS server 192.168.0.3:
_ldap._tcp.gc._msdcs.huntingtoncatholic.local

Matching A record found at DNS server 192.168.0.3:
gc._msdcs.huntingtoncatholic.local

Matching SRV record found at DNS server 192.168.0.3:
_gc._tcp.Default-First-Site-Name._sites.huntingtoncatholic.
local

Matching SRV record found at DNS server 192.168.0.3:
_ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.hunting
toncatholic.local


Summary of test results for DNS servers used by the above domain
controllers:

DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:1::803f:235
[Error details: 1460 (Type: Win32 - Description: This operation ret
urned because the timeout period expired.)]

DNS server: 2001:500:2d::d (d.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2d::d
[Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]

DNS server: 2001:500:2f::f (f.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:2f::f
[Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]

DNS server: 2001:500:3::42 (l.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:500:3::42
[Error details: 1460 (Type: Win32 - Description: This operation returned
because the timeout period expired.)]

DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:ba3e::2:30
[Error details: 1460 (Type: Win32 - Description: This operation retu
rned because the timeout period expired.)]

DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:503:c27::2:30
[Error details: 1460 (Type: Win32 - Description: This operation retur
ned because the timeout period expired.)]

DNS server: 2001:7fd::1 (k.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fd::1
[Error details: 1460 (Type: Win32 - Description: This operation returned bec
ause the timeout period expired.)]

DNS server: 2001:7fe::53 (i.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:7fe::53
[Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]

DNS server: 2001:dc3::35 (m.root-servers.net.)
1 test failure on this DNS server
PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.
0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed on the DNS server 2001:dc3::35
[Error details: 1460 (Type: Win32 - Description: This operation returned be
cause the timeout period expired.)]

DNS server: 128.63.2.53 (h.root-servers.net.)
All tests passed on this DNS server

DNS server: 128.8.10.90 (d.root-servers.net.)
All tests passed on this DNS server

DNS server: 192.112.36.4 (g.root-servers.net.)
All tests passed on this DNS server

DNS server: 192.168.0.3 (win-p2fq0ms56nl.huntingtoncatholic.local.)
All tests passed on this DNS server
Name resolution is functional._ldap._tcp SRV record for the fores
t root domain is registered
DNS delegation for the domain _msdcs.huntingtoncatholic.local. i
s operational on IP 192.168.0.3


DNS server: 192.203.230.10 (e.root-servers.net.)
All tests passed on this DNS server

DNS server: 192.228.79.201 (b.root-servers.net.)
All tests passed on this DNS server

DNS server: 192.33.4.12 (c.root-servers.net.)
All tests passed on this DNS server

DNS server: 192.36.148.17 (i.root-servers.net.)
All tests passed on this DNS server

DNS server: 192.5.5.241 (f.root-servers.net.)
All tests passed on this DNS server

DNS server: 192.58.128.30 (j.root-servers.net.)
All tests passed on this DNS server

DNS server: 193.0.14.129 (k.root-servers.net.)
All tests passed on this DNS server

DNS server: 198.41.0.4 (a.root-servers.net.)
All tests passed on this DNS server

DNS server: 199.7.83.42 (l.root-servers.net.)
All tests passed on this DNS server

DNS server: 199.7.91.13 (d.root-servers.net.)
All tests passed on this DNS server

DNS server: 202.12.27.33 (m.root-servers.net.)
All tests passed on this DNS server

Summary of DNS test results:

Auth Basc Forw Del Dyn RReg Ext
_________________________________________________________________
Domain: huntingtoncatholic.local
hcsserver PASS PASS PASS PASS PASS PASS n/a

......................... huntingtoncatholic.local passed test DNS
Starting test: LocatorCheck
GC Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
Warning: Couldn't verify this server as a PDC using DsListRoles()
PDC Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
Time Server Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
Preferred Time Server Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
KDC Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
......................... huntingtoncatholic.local passed test
LocatorCheck
Starting test: FsmoCheck
GC Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
Warning: Couldn't verify this server as a PDC using DsListRoles()
PDC Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
Time Server Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
Preferred Time Server Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
KDC Name: \\hcsserver.huntingtoncatholic.local
Locator Flags: 0xe00033fd
......................... huntingtoncatholic.local passed test
FsmoCheck
Starting test: Intersite
Skipping site Default-First-Site-Name, this site is outside the scope
provided by the command line arguments provided.
......................... huntingtoncatholic.local passed test
Intersite

C:\Users\Administrator>

netdom query

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Administrator>netdom query fsmo
Schema master hcsserver.huntingtoncatholic.local
Domain naming master hcsserver.huntingtoncatholic.local
PDC *** Warning: role owner is undefined.
RID pool manager *** Warning: role owner is undefined.
Infrastructure master *** Warning: role owner is undefined.
The command completed successfully.


C:\Users\Administrator>

I am attaching links to all the screen shots I sent to experts Exchange. They have been unsuccessful in helping with this issue and I hope someone on this forum can help. I will be at the school Saturday most of the day to hopefully work on this and resolve this problem.

We do not have a backup DC but we still have to old server with Server 2003 that has been offline for about a year.

Thank you!

Robert

 

[technome]

Not had this fun experience, go slow so you do not compound the issue...

Manually undeleting objects

http://www.petri.co.il/manually-undeleting-objects-windows-active-directory-ad.htm

Try the Minasi forum, if your not successful here, few guys there who eat AD issues as a staple diet...

http://www.minasi.com/forum/forum.asp?FORUM_ID=5

........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

"Computers in the future may weigh no more than 1.5 tons."
Popular Mechanics, 1949

 

[mrtechno77]

I followed the instructions to undelete objects but all that was found were some user accounts that have been deleted. There were no OUs or containers found. I suspect that they are all there somewhere but just hidden somehow because users can logon using their network credentials, we can map drives and other network resources but I can't add any users or computers because the containers are not visible. Does anyone have any other thoughts on this?

 

[technome]

I see you did not post to the Minasi forum, that is you best bet, do it!!!!!.
If you get an answer from Mark Minasi or Wsasdo, either one has great knowledge of AD issues, if they recommend something, do it. An AD restore my be possible, but again do not do anything unless your sure of the results of you actions; 90% of impulsive actions only cause greater problems/stress.

When you post to the Minasi site, have the following info on hand.....
Do you have a second DC? You should run DcDiag with the /v switch as DcDiag /v

If you have a second DC, the second DC should be referenced towards the beginning of a DcDiag /v output.
If a second Dc exists, run DcDiag /v on that and keep the info handy by outputting to a text file.

http://technet.microsoft.com/en-us/library/cc776854(v=ws.10).aspx

If you have a second Dc, replication hopefully stopped, the second one, holding much of the domain info you might be able to retrieve.

Can't hurt to run Netdiag /v, likely not needed but handy to have the output info on hand

Do you have a full backup, including the system state, before this issue occurred?



........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

"Computers in the future may weigh no more than 1.5 tons."
Popular Mechanics, 1949