Go Back   TechArena Community > Technical Support > Computer Help > Windows Server > Active Directory
showing deleted active directory site showing deleted active directory site
Become a Member!
Forgot your username/password?
Register Tags Active Topics RSS Search Mark Forums Read SiteMap

Tags: , , ,

Sponsored Links



showing deleted active directory site

Active Directory


Reply
 
Thread Tools Search this Thread
  #1  
Old 18-02-2009
Fachlul
 
Posts: n/a
showing deleted active directory site
We are running active Directory on Windows 2003 SP 2

We have created a site on active directory sites and service and then delete
the site from that console. The deleted site is still displayed when we
execute right mouse click move server. (shown as "SITENAME\0ADEL:#GUID#)

Here come the problem, one of our team accidentally move our server to the
deleted site and we don't have a back up of our AD

Could somebody tell me how to deisplay the deleted site or recover the
deleted site so that we can move back our server to default first site name
site?

Really appriciate any help.

Fachlul
Reply With Quote
  #2  
Old 18-02-2009
Paul Bergson [MVP-DS]
 
Posts: n/a
Re: showing deleted active directory site
First think I would do is check the "Lost and Found" container for your
missing DC
Bring up Active Directory Users and Computers
Make sure the advanced features are turned on via View / Advanced
Features

The DC isn't going to just go away so lets hope it is in that container


--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.


"Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
news:27BEB016-9547-4523-91F8-BFBB346C6C84@microsoft.com...
> We are running active Directory on Windows 2003 SP 2
>
> We have created a site on active directory sites and service and then
> delete
> the site from that console. The deleted site is still displayed when we
> execute right mouse click move server. (shown as "SITENAME\0ADEL:#GUID#)
>
> Here come the problem, one of our team accidentally move our server to the
> deleted site and we don't have a back up of our AD
>
> Could somebody tell me how to deisplay the deleted site or recover the
> deleted site so that we can move back our server to default first site
> name
> site?
>
> Really appriciate any help.
>
> Fachlul

Reply With Quote
  #3  
Old 18-02-2009
Fachlul
 
Posts: n/a
Re: showing deleted active directory site
nope... i've check there.. its empty...

i even have gone thru the with adrestore.exe and ldp.exe but i can't find
the deleted site

what i think could help me right now is how to get the deleted site object
back to my active directory sites and services console so that i can move my
server manually from the console. :((

"Paul Bergson [MVP-DS]" wrote:

> First think I would do is check the "Lost and Found" container for your
> missing DC
> Bring up Active Directory Users and Computers
> Make sure the advanced features are turned on via View / Advanced
> Features
>
> The DC isn't going to just go away so lets hope it is in that container
>
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
> news:27BEB016-9547-4523-91F8-BFBB346C6C84@microsoft.com...
> > We are running active Directory on Windows 2003 SP 2
> >
> > We have created a site on active directory sites and service and then
> > delete
> > the site from that console. The deleted site is still displayed when we
> > execute right mouse click move server. (shown as "SITENAME\0ADEL:#GUID#)
> >
> > Here come the problem, one of our team accidentally move our server to the
> > deleted site and we don't have a back up of our AD
> >
> > Could somebody tell me how to deisplay the deleted site or recover the
> > deleted site so that we can move back our server to default first site
> > name
> > site?
> >
> > Really appriciate any help.
> >
> > Fachlul
>
Reply With Quote
  #4  
Old 18-02-2009
Paul Bergson [MVP-DS]
 
Posts: n/a
Re: showing deleted active directory site
The only way you are going to be able to do that is through authoritative
restore.

Config partition
CN=Sites,CN=Configuration,DC=domainname,DC=domainname



--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.


"Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
news:A5DBE095-FAFB-49C6-993D-0B2E58DA4561@microsoft.com...
> nope... i've check there.. its empty...
>
> i even have gone thru the with adrestore.exe and ldp.exe but i can't find
> the deleted site
>
> what i think could help me right now is how to get the deleted site object
> back to my active directory sites and services console so that i can move
> my
> server manually from the console. :((
>
> "Paul Bergson [MVP-DS]" wrote:
>
>> First think I would do is check the "Lost and Found" container for your
>> missing DC
>> Bring up Active Directory Users and Computers
>> Make sure the advanced features are turned on via View / Advanced
>> Features
>>
>> The DC isn't going to just go away so lets hope it is in that container
>>
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> 2008, 2003, 2000 (Early Achiever), NT4
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup This
>> posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>
>> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
>> news:27BEB016-9547-4523-91F8-BFBB346C6C84@microsoft.com...
>> > We are running active Directory on Windows 2003 SP 2
>> >
>> > We have created a site on active directory sites and service and then
>> > delete
>> > the site from that console. The deleted site is still displayed when
>> > we
>> > execute right mouse click move server. (shown as
>> > "SITENAME\0ADEL:#GUID#)
>> >
>> > Here come the problem, one of our team accidentally move our server to
>> > the
>> > deleted site and we don't have a back up of our AD
>> >
>> > Could somebody tell me how to deisplay the deleted site or recover the
>> > deleted site so that we can move back our server to default first site
>> > name
>> > site?
>> >
>> > Really appriciate any help.
>> >
>> > Fachlul
>>

Reply With Quote
  #5  
Old 18-02-2009
Fachlul
 
Posts: n/a
Re: showing deleted active directory site
do i need my back up file to do this since we never back up our active
directory server.....

"Paul Bergson [MVP-DS]" wrote:

> The only way you are going to be able to do that is through authoritative
> restore.
>
> Config partition
> CN=Sites,CN=Configuration,DC=domainname,DC=domainname
>
>
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
> news:A5DBE095-FAFB-49C6-993D-0B2E58DA4561@microsoft.com...
> > nope... i've check there.. its empty...
> >
> > i even have gone thru the with adrestore.exe and ldp.exe but i can't find
> > the deleted site
> >
> > what i think could help me right now is how to get the deleted site object
> > back to my active directory sites and services console so that i can move
> > my
> > server manually from the console. :((
> >
> > "Paul Bergson [MVP-DS]" wrote:
> >
> >> First think I would do is check the "Lost and Found" container for your
> >> missing DC
> >> Bring up Active Directory Users and Computers
> >> Make sure the advanced features are turned on via View / Advanced
> >> Features
> >>
> >> The DC isn't going to just go away so lets hope it is in that container
> >>
> >>
> >> --
> >> Paul Bergson
> >> MVP - Directory Services
> >> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> >> 2008, 2003, 2000 (Early Achiever), NT4
> >>
> >> http://www.pbbergs.com
> >>
> >> Please no e-mails, any questions should be posted in the NewsGroup This
> >> posting is provided "AS IS" with no warranties, and confers no rights.
> >>
> >>
> >> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
> >> news:27BEB016-9547-4523-91F8-BFBB346C6C84@microsoft.com...
> >> > We are running active Directory on Windows 2003 SP 2
> >> >
> >> > We have created a site on active directory sites and service and then
> >> > delete
> >> > the site from that console. The deleted site is still displayed when
> >> > we
> >> > execute right mouse click move server. (shown as
> >> > "SITENAME\0ADEL:#GUID#)
> >> >
> >> > Here come the problem, one of our team accidentally move our server to
> >> > the
> >> > deleted site and we don't have a back up of our AD
> >> >
> >> > Could somebody tell me how to deisplay the deleted site or recover the
> >> > deleted site so that we can move back our server to default first site
> >> > name
> >> > site?
> >> >
> >> > Really appriciate any help.
> >> >
> >> > Fachlul
> >>
>
Reply With Quote
  #6  
Old 18-02-2009
Paul Bergson [MVP-DS]
 
Posts: n/a
Re: showing deleted active directory site
Yes you would.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.


"Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
news:5AECC3E6-E8C6-4820-A35C-42C1A477016E@microsoft.com...
> do i need my back up file to do this since we never back up our active
> directory server.....
>
> "Paul Bergson [MVP-DS]" wrote:
>
>> The only way you are going to be able to do that is through authoritative
>> restore.
>>
>> Config partition
>> CN=Sites,CN=Configuration,DC=domainname,DC=domainname
>>
>>
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> 2008, 2003, 2000 (Early Achiever), NT4
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup This
>> posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>
>> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
>> news:A5DBE095-FAFB-49C6-993D-0B2E58DA4561@microsoft.com...
>> > nope... i've check there.. its empty...
>> >
>> > i even have gone thru the with adrestore.exe and ldp.exe but i can't
>> > find
>> > the deleted site
>> >
>> > what i think could help me right now is how to get the deleted site
>> > object
>> > back to my active directory sites and services console so that i can
>> > move
>> > my
>> > server manually from the console. :((
>> >
>> > "Paul Bergson [MVP-DS]" wrote:
>> >
>> >> First think I would do is check the "Lost and Found" container for
>> >> your
>> >> missing DC
>> >> Bring up Active Directory Users and Computers
>> >> Make sure the advanced features are turned on via View / Advanced
>> >> Features
>> >>
>> >> The DC isn't going to just go away so lets hope it is in that
>> >> container
>> >>
>> >>
>> >> --
>> >> Paul Bergson
>> >> MVP - Directory Services
>> >> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> >> 2008, 2003, 2000 (Early Achiever), NT4
>> >>
>> >> http://www.pbbergs.com
>> >>
>> >> Please no e-mails, any questions should be posted in the NewsGroup
>> >> This
>> >> posting is provided "AS IS" with no warranties, and confers no rights.
>> >>
>> >>
>> >> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
>> >> news:27BEB016-9547-4523-91F8-BFBB346C6C84@microsoft.com...
>> >> > We are running active Directory on Windows 2003 SP 2
>> >> >
>> >> > We have created a site on active directory sites and service and
>> >> > then
>> >> > delete
>> >> > the site from that console. The deleted site is still displayed
>> >> > when
>> >> > we
>> >> > execute right mouse click move server. (shown as
>> >> > "SITENAME\0ADEL:#GUID#)
>> >> >
>> >> > Here come the problem, one of our team accidentally move our server
>> >> > to
>> >> > the
>> >> > deleted site and we don't have a back up of our AD
>> >> >
>> >> > Could somebody tell me how to deisplay the deleted site or recover
>> >> > the
>> >> > deleted site so that we can move back our server to default first
>> >> > site
>> >> > name
>> >> > site?
>> >> >
>> >> > Really appriciate any help.
>> >> >
>> >> > Fachlul
>> >>
>>

Reply With Quote
  #7  
Old 18-02-2009
Paul Bergson [MVP-DS]
 
Posts: n/a
Re: showing deleted active directory site
I clicked send to quick

You should still be able to view deleted objects via ldp
http://support.microsoft.com/kb/258310

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.


"Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
news:5AECC3E6-E8C6-4820-A35C-42C1A477016E@microsoft.com...
> do i need my back up file to do this since we never back up our active
> directory server.....
>
> "Paul Bergson [MVP-DS]" wrote:
>
>> The only way you are going to be able to do that is through authoritative
>> restore.
>>
>> Config partition
>> CN=Sites,CN=Configuration,DC=domainname,DC=domainname
>>
>>
>>
>> --
>> Paul Bergson
>> MVP - Directory Services
>> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> 2008, 2003, 2000 (Early Achiever), NT4
>>
>> http://www.pbbergs.com
>>
>> Please no e-mails, any questions should be posted in the NewsGroup This
>> posting is provided "AS IS" with no warranties, and confers no rights.
>>
>>
>> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
>> news:A5DBE095-FAFB-49C6-993D-0B2E58DA4561@microsoft.com...
>> > nope... i've check there.. its empty...
>> >
>> > i even have gone thru the with adrestore.exe and ldp.exe but i can't
>> > find
>> > the deleted site
>> >
>> > what i think could help me right now is how to get the deleted site
>> > object
>> > back to my active directory sites and services console so that i can
>> > move
>> > my
>> > server manually from the console. :((
>> >
>> > "Paul Bergson [MVP-DS]" wrote:
>> >
>> >> First think I would do is check the "Lost and Found" container for
>> >> your
>> >> missing DC
>> >> Bring up Active Directory Users and Computers
>> >> Make sure the advanced features are turned on via View / Advanced
>> >> Features
>> >>
>> >> The DC isn't going to just go away so lets hope it is in that
>> >> container
>> >>
>> >>
>> >> --
>> >> Paul Bergson
>> >> MVP - Directory Services
>> >> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
>> >> 2008, 2003, 2000 (Early Achiever), NT4
>> >>
>> >> http://www.pbbergs.com
>> >>
>> >> Please no e-mails, any questions should be posted in the NewsGroup
>> >> This
>> >> posting is provided "AS IS" with no warranties, and confers no rights.
>> >>
>> >>
>> >> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
>> >> news:27BEB016-9547-4523-91F8-BFBB346C6C84@microsoft.com...
>> >> > We are running active Directory on Windows 2003 SP 2
>> >> >
>> >> > We have created a site on active directory sites and service and
>> >> > then
>> >> > delete
>> >> > the site from that console. The deleted site is still displayed
>> >> > when
>> >> > we
>> >> > execute right mouse click move server. (shown as
>> >> > "SITENAME\0ADEL:#GUID#)
>> >> >
>> >> > Here come the problem, one of our team accidentally move our server
>> >> > to
>> >> > the
>> >> > deleted site and we don't have a back up of our AD
>> >> >
>> >> > Could somebody tell me how to deisplay the deleted site or recover
>> >> > the
>> >> > deleted site so that we can move back our server to default first
>> >> > site
>> >> > name
>> >> > site?
>> >> >
>> >> > Really appriciate any help.
>> >> >
>> >> > Fachlul
>> >>
>>

Reply With Quote
  #8  
Old 18-02-2009
Fachlul
 
Posts: n/a
Re: showing deleted active directory site
Thank's I can see the object on active directory setting but still don't
know how to change the things back to normal.... :(

where can i see my domain setting?

here is my domain detail

Expanding base 'dc=kei,dc=kangean-energy,dc=com'...
Result <0>: (null)
Matched DNs:
Getting 1 entries:
>> Dn: dc=kei,dc=kangean-energy,dc=com
3> objectClass: top; domain; domainDNS;
1> distinguishedName: DC=kei,DC=kangean-energy,DC=com;
1> instanceType: 0x5 = ( DS_INSTANCETYPE_IS_NC_HEAD | IT_WRITE );
1> whenCreated: 9/3/2007 23:26:29 SE Asia Standard Time SE Asia Standard
Time;
1> whenChanged: 2/18/2009 21:24:14 SE Asia Standard Time SE Asia Standard
Time;
3> subRefs: DC=ForestDnsZones,DC=kei,DC=kangean-energy,DC=com;
DC=DomainDnsZones,DC=kei,DC=kangean-energy,DC=com;
CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> uSNCreated: 4098;
1> dSASignature: <ldp: Binary blob>;
3> repsTo: dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0
V1.timeLastSuccess: 12879449944 V1.timeLastAttempt: 12879449944
V1.ulResultLastAttempt: 0x0 V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71
V1.ulReplicaFlags: 0x10 V1.rtSchedule: <ldp:skipped>
V1.usnvec.usnHighObjUpdate: 0 V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
4bdde1ed-5a4e-4a70-81a4-15a8f790a3df V1.uuidInvocId:
00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
4bdde1ed-5a4e-4a70-81a4-15a8f790a3df._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
12879449887 V1.timeLastAttempt: 12879449887 V1.ulResultLastAttempt: 0x0
V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x10
V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 0
V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
420ffd3f-1b7b-437e-961e-ab49b12a1806 V1.uuidInvocId:
00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
420ffd3f-1b7b-437e-961e-ab49b12a1806._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
12879449611 V1.timeLastAttempt: 12879449611 V1.ulResultLastAttempt: 0x0
V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x10
V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 0
V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
c50f4d07-2b7b-4d53-93cd-774fa63f61ed V1.uuidInvocId:
00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
c50f4d07-2b7b-4d53-93cd-774fa63f61ed._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
3> repsFrom: dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0
V1.timeLastSuccess: 12879450190 V1.timeLastAttempt: 12879450190
V1.ulResultLastAttempt: 0x0 V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71
V1.ulReplicaFlags: 0x70 V1.rtSchedule: <ldp:skipped>
V1.usnvec.usnHighObjUpdate: 9227169 V1.usnvec.usnHighPropUpdate: 9227169
V1.uuidDsaObj: c50f4d07-2b7b-4d53-93cd-774fa63f61ed V1.uuidInvocId:
8054edfa-4d1c-4b3a-83d6-3bae4dcae0b4 V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
c50f4d07-2b7b-4d53-93cd-774fa63f61ed._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
12879450187 V1.timeLastAttempt: 12879450187 V1.ulResultLastAttempt: 0x0
V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x70
V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 9081728
V1.usnvec.usnHighPropUpdate: 9081728 V1.uuidDsaObj:
420ffd3f-1b7b-437e-961e-ab49b12a1806 V1.uuidInvocId:
2876ea87-f023-4217-b075-257c9df8342f V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
420ffd3f-1b7b-437e-961e-ab49b12a1806._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
12879450111 V1.timeLastAttempt: 12879450111 V1.ulResultLastAttempt: 0x0
V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x70
V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 7402879
V1.usnvec.usnHighPropUpdate: 7402879 V1.uuidDsaObj:
4bdde1ed-5a4e-4a70-81a4-15a8f790a3df V1.uuidInvocId:
7271d9ab-28f0-43da-a9db-2ded7daab9fd V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
4bdde1ed-5a4e-4a70-81a4-15a8f790a3df._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
1> uSNChanged: 15054668;
1> name: kei;
1> objectGUID: dfae445b-dc9d-405d-ae1e-3b77ed3f69f2;
1> replUpToDateVector: <ldp error: cannot process UPDATE_VECTOR v.2>;
1> creationTime: <ldp error <0x0>: cannot format time field;
1> forceLogoff: -9223372036854775808 (none);
1> lockoutDuration: 1800;
1> lockOutObservationWindow: 1800;
1> lockoutThreshold: 5;
1> maxPwdAge: 7776000;
1> minPwdAge: 0 (none);
1> minPwdLength: 5;
1> modifiedCountAtLastProm: 0;
1> nextRid: 1003;
1> pwdProperties: 0;
1> pwdHistoryLength: 1;
1> objectSid: S-1-5-21-3132921636-2566841788-1541036888;
1> serverState: 1;
1> uASCompat: 1;
1> modifiedCount: 83;
1> auditingPolicy: <ldp: Binary blob>;
1> nTMixedDomain: 0;
1> rIDManagerReference: CN=RID
Manager$,CN=System,DC=kei,DC=kangean-energy,DC=com;
1> fSMORoleOwner: CN=NTDS
Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> systemFlags: 0x8C000000 = ( FLAG_DISALLOW_DELETE |
FLAG_DOMAIN_DISALLOW_RENAME | FLAG_DOMAIN_DISALLOW_MOVE );
11> wellKnownObjects: B:32:6227F0AF1FC2410D8E3BB10615BB5B0F:CN=NTDS
Quotas,DC=kei,DC=kangean-energy,DC=com;
B:32:F4BE92A4C777485E878E9421D53087DB:CN=Microsoft,CN=Program
Data,DC=kei,DC=kangean-energy,DC=com;
B:32:09460C08AE1E4A4EA0F64AEE7DAA1E5A:CN=Program
Data,DC=kei,DC=kangean-energy,DC=com;
B:32:22B70C67D56E4EFB91E9300FCA3DC1AA:CN=ForeignSecurityPrincipals,DC=kei,DC=kangean-energy,DC=com;
B:32:18E2EA80684F11D2B9AA00C04F79F805:CN=Deleted
Objects,DC=kei,DC=kangean-energy,DC=com;
B:32:2FBAC1870ADE11D297C400C04FD8D5CD:CN=Infrastructure,DC=kei,DC=kangean-energy,DC=com;
B:32:AB8153B7768811D1ADED00C04FD8D5CD:CN=LostAndFound,DC=kei,DC=kangean-energy,DC=com;
B:32:AB1D30F3768811D1ADED00C04FD8D5CD:CN=System,DC=kei,DC=kangean-energy,DC=com;
B:32:A361B2FFFFD211D1AA4B00C04FD7D83A:OU=Domain
Controllers,DC=kei,DC=kangean-energy,DC=com;
B:32:AA312825768811D1ADED00C04FD8D5CD:CN=Computers,DC=kei,DC=kangean-energy,DC=com;
B:32:A9D1CA15768811D1ADED00C04FD8D5CD:CN=Users,DC=kei,DC=kangean-energy,DC=com;
1> objectCategory:
CN=Domain-DNS,CN=Schema,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> isCriticalSystemObject: TRUE;
1> gPLink:
[LDAP://CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=kei,DC=kangean-energy,DC=com;0];
4> masteredBy: CN=NTDS
Settings,CN=KEISBYDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEISPJDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEIPAGDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> ms-DS-MachineAccountQuota: 10;
1> msDS-Behavior-Version: 0 = ( DS_BEHAVIOR_WIN2000 );
1> msDS-PerUserTrustQuota: 1;
1> msDS-AllUsersTrustQuota: 1000;
1> msDS-PerUserTrustTombstonesQuota: 10;
4> msDs-masteredBy: CN=NTDS
Settings,CN=KEISBYDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEISPJDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEIPAGDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> dc: kei;
-----------

how do i move this server:

Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;


back to CN=default first site name instead of pagerungan\0adel:GUID

"Paul Bergson [MVP-DS]" wrote:

> I clicked send to quick
>
> You should still be able to view deleted objects via ldp
> http://support.microsoft.com/kb/258310
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
> news:5AECC3E6-E8C6-4820-A35C-42C1A477016E@microsoft.com...
> > do i need my back up file to do this since we never back up our active
> > directory server.....
> >
> > "Paul Bergson [MVP-DS]" wrote:
> >
> >> The only way you are going to be able to do that is through authoritative
> >> restore.
> >>
> >> Config partition
> >> CN=Sites,CN=Configuration,DC=domainname,DC=domainname
> >>
> >>
> >>
> >> --
> >> Paul Bergson
> >> MVP - Directory Services
> >> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> >> 2008, 2003, 2000 (Early Achiever), NT4
> >>
> >> http://www.pbbergs.com
> >>
> >> Please no e-mails, any questions should be posted in the NewsGroup This
> >> posting is provided "AS IS" with no warranties, and confers no rights.
> >>
> >>
> >> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
> >> news:A5DBE095-FAFB-49C6-993D-0B2E58DA4561@microsoft.com...
> >> > nope... i've check there.. its empty...
> >> >
> >> > i even have gone thru the with adrestore.exe and ldp.exe but i can't
> >> > find
> >> > the deleted site
> >> >
> >> > what i think could help me right now is how to get the deleted site
> >> > object
> >> > back to my active directory sites and services console so that i can
> >> > move
> >> > my
> >> > server manually from the console. :((
> >> >
> >> > "Paul Bergson [MVP-DS]" wrote:
> >> >
> >> >> First think I would do is check the "Lost and Found" container for
> >> >> your
> >> >> missing DC
> >> >> Bring up Active Directory Users and Computers
> >> >> Make sure the advanced features are turned on via View / Advanced
> >> >> Features
> >> >>
> >> >> The DC isn't going to just go away so lets hope it is in that
> >> >> container
> >> >>
> >> >>
> >> >> --
> >> >> Paul Bergson
> >> >> MVP - Directory Services
> >> >> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> >> >> 2008, 2003, 2000 (Early Achiever), NT4
> >> >>
> >> >> http://www.pbbergs.com
> >> >>
> >> >> Please no e-mails, any questions should be posted in the NewsGroup
> >> >> This
> >> >> posting is provided "AS IS" with no warranties, and confers no rights.
> >> >>
> >> >>
> >> >> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
> >> >> news:27BEB016-9547-4523-91F8-BFBB346C6C84@microsoft.com...
> >> >> > We are running active Directory on Windows 2003 SP 2
> >> >> >
> >> >> > We have created a site on active directory sites and service and
> >> >> > then
> >> >> > delete
> >> >> > the site from that console. The deleted site is still displayed
> >> >> > when
> >> >> > we
> >> >> > execute right mouse click move server. (shown as
> >> >> > "SITENAME\0ADEL:#GUID#)
> >> >> >
> >> >> > Here come the problem, one of our team accidentally move our server
> >> >> > to
> >> >> > the
> >> >> > deleted site and we don't have a back up of our AD
> >> >> >
> >> >> > Could somebody tell me how to deisplay the deleted site or recover
> >> >> > the
> >> >> > deleted site so that we can move back our server to default first
> >> >> > site
> >> >> > name
> >> >> > site?
> >> >> >
> >> >> > Really appriciate any help.
> >> >> >
> >> >> > Fachlul
> >> >>
> >>
>
Reply With Quote
  #9  
Old 18-02-2009
Fachlul
 
Posts: n/a
Re: showing deleted active directory site
Thank's I can see the object on active directory setting but still don't
know how to change the things back to normal.... :(

where can i see my domain setting?

here is my domain detail

Expanding base 'dc=kei,dc=kangean-energy,dc=com'...
Result <0>: (null)
Matched DNs:
Getting 1 entries:
>> Dn: dc=kei,dc=kangean-energy,dc=com
3> objectClass: top; domain; domainDNS;
1> distinguishedName: DC=kei,DC=kangean-energy,DC=com;
1> instanceType: 0x5 = ( DS_INSTANCETYPE_IS_NC_HEAD | IT_WRITE );
1> whenCreated: 9/3/2007 23:26:29 SE Asia Standard Time SE Asia Standard
Time;
1> whenChanged: 2/18/2009 21:24:14 SE Asia Standard Time SE Asia Standard
Time;
3> subRefs: DC=ForestDnsZones,DC=kei,DC=kangean-energy,DC=com;
DC=DomainDnsZones,DC=kei,DC=kangean-energy,DC=com;
CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> uSNCreated: 4098;
1> dSASignature: <ldp: Binary blob>;
3> repsTo: dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0
V1.timeLastSuccess: 12879449944 V1.timeLastAttempt: 12879449944
V1.ulResultLastAttempt: 0x0 V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71
V1.ulReplicaFlags: 0x10 V1.rtSchedule: <ldp:skipped>
V1.usnvec.usnHighObjUpdate: 0 V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
4bdde1ed-5a4e-4a70-81a4-15a8f790a3df V1.uuidInvocId:
00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
4bdde1ed-5a4e-4a70-81a4-15a8f790a3df._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
12879449887 V1.timeLastAttempt: 12879449887 V1.ulResultLastAttempt: 0x0
V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x10
V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 0
V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
420ffd3f-1b7b-437e-961e-ab49b12a1806 V1.uuidInvocId:
00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
420ffd3f-1b7b-437e-961e-ab49b12a1806._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
12879449611 V1.timeLastAttempt: 12879449611 V1.ulResultLastAttempt: 0x0
V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x10
V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 0
V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
c50f4d07-2b7b-4d53-93cd-774fa63f61ed V1.uuidInvocId:
00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
c50f4d07-2b7b-4d53-93cd-774fa63f61ed._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
3> repsFrom: dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0
V1.timeLastSuccess: 12879450190 V1.timeLastAttempt: 12879450190
V1.ulResultLastAttempt: 0x0 V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71
V1.ulReplicaFlags: 0x70 V1.rtSchedule: <ldp:skipped>
V1.usnvec.usnHighObjUpdate: 9227169 V1.usnvec.usnHighPropUpdate: 9227169
V1.uuidDsaObj: c50f4d07-2b7b-4d53-93cd-774fa63f61ed V1.uuidInvocId:
8054edfa-4d1c-4b3a-83d6-3bae4dcae0b4 V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
c50f4d07-2b7b-4d53-93cd-774fa63f61ed._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
12879450187 V1.timeLastAttempt: 12879450187 V1.ulResultLastAttempt: 0x0
V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x70
V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 9081728
V1.usnvec.usnHighPropUpdate: 9081728 V1.uuidDsaObj:
420ffd3f-1b7b-437e-961e-ab49b12a1806 V1.uuidInvocId:
2876ea87-f023-4217-b075-257c9df8342f V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
420ffd3f-1b7b-437e-961e-ab49b12a1806._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
12879450111 V1.timeLastAttempt: 12879450111 V1.ulResultLastAttempt: 0x0
V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x70
V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 7402879
V1.usnvec.usnHighPropUpdate: 7402879 V1.uuidDsaObj:
4bdde1ed-5a4e-4a70-81a4-15a8f790a3df V1.uuidInvocId:
7271d9ab-28f0-43da-a9db-2ded7daab9fd V1.uuidTransportObj:
00000000-0000-0000-0000-000000000000 V1~mtx_address:
4bdde1ed-5a4e-4a70-81a4-15a8f790a3df._msdcs.kei.kangean-energy.com
V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
1> uSNChanged: 15054668;
1> name: kei;
1> objectGUID: dfae445b-dc9d-405d-ae1e-3b77ed3f69f2;
1> replUpToDateVector: <ldp error: cannot process UPDATE_VECTOR v.2>;
1> creationTime: <ldp error <0x0>: cannot format time field;
1> forceLogoff: -9223372036854775808 (none);
1> lockoutDuration: 1800;
1> lockOutObservationWindow: 1800;
1> lockoutThreshold: 5;
1> maxPwdAge: 7776000;
1> minPwdAge: 0 (none);
1> minPwdLength: 5;
1> modifiedCountAtLastProm: 0;
1> nextRid: 1003;
1> pwdProperties: 0;
1> pwdHistoryLength: 1;
1> objectSid: S-1-5-21-3132921636-2566841788-1541036888;
1> serverState: 1;
1> uASCompat: 1;
1> modifiedCount: 83;
1> auditingPolicy: <ldp: Binary blob>;
1> nTMixedDomain: 0;
1> rIDManagerReference: CN=RID
Manager$,CN=System,DC=kei,DC=kangean-energy,DC=com;
1> fSMORoleOwner: CN=NTDS
Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> systemFlags: 0x8C000000 = ( FLAG_DISALLOW_DELETE |
FLAG_DOMAIN_DISALLOW_RENAME | FLAG_DOMAIN_DISALLOW_MOVE );
11> wellKnownObjects: B:32:6227F0AF1FC2410D8E3BB10615BB5B0F:CN=NTDS
Quotas,DC=kei,DC=kangean-energy,DC=com;
B:32:F4BE92A4C777485E878E9421D53087DB:CN=Microsoft,CN=Program
Data,DC=kei,DC=kangean-energy,DC=com;
B:32:09460C08AE1E4A4EA0F64AEE7DAA1E5A:CN=Program
Data,DC=kei,DC=kangean-energy,DC=com;
B:32:22B70C67D56E4EFB91E9300FCA3DC1AA:CN=ForeignSecurityPrincipals,DC=kei,DC=kangean-energy,DC=com;
B:32:18E2EA80684F11D2B9AA00C04F79F805:CN=Deleted
Objects,DC=kei,DC=kangean-energy,DC=com;
B:32:2FBAC1870ADE11D297C400C04FD8D5CD:CN=Infrastructure,DC=kei,DC=kangean-energy,DC=com;
B:32:AB8153B7768811D1ADED00C04FD8D5CD:CN=LostAndFound,DC=kei,DC=kangean-energy,DC=com;
B:32:AB1D30F3768811D1ADED00C04FD8D5CD:CN=System,DC=kei,DC=kangean-energy,DC=com;
B:32:A361B2FFFFD211D1AA4B00C04FD7D83A:OU=Domain
Controllers,DC=kei,DC=kangean-energy,DC=com;
B:32:AA312825768811D1ADED00C04FD8D5CD:CN=Computers,DC=kei,DC=kangean-energy,DC=com;
B:32:A9D1CA15768811D1ADED00C04FD8D5CD:CN=Users,DC=kei,DC=kangean-energy,DC=com;
1> objectCategory:
CN=Domain-DNS,CN=Schema,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> isCriticalSystemObject: TRUE;
1> gPLink:
[LDAP://CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=kei,DC=kangean-energy,DC=com;0];
4> masteredBy: CN=NTDS
Settings,CN=KEISBYDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEISPJDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEIPAGDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> ms-DS-MachineAccountQuota: 10;
1> msDS-Behavior-Version: 0 = ( DS_BEHAVIOR_WIN2000 );
1> msDS-PerUserTrustQuota: 1;
1> msDS-AllUsersTrustQuota: 1000;
1> msDS-PerUserTrustTombstonesQuota: 10;
4> msDs-masteredBy: CN=NTDS
Settings,CN=KEISBYDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEISPJDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEIPAGDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
CN=NTDS
Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
1> dc: kei;
-----------

I want to move my server from CN=NTDS
Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
to
CN=NTDS
Settings,CN=KEIJKTDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;

I canat see the site name
CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694 on my adsi editor


Reply With Quote
  #10  
Old 18-02-2009
Paul Bergson [MVP-DS]
 
Posts: n/a
Re: showing deleted active directory site
I am attempting to find out some info, but from what I know you will have to
flatten the dc, clean out the metadata and reinstall. I am not sure so I am
waiting to see if there is any other info. Someone may just pop in on this
thread or provide feedback to me. But you will have to wait.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.


"Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
news:654EF17B-FCB9-42BA-AF64-1057666D9587@microsoft.com...
> Thank's I can see the object on active directory setting but still don't
> know how to change the things back to normal.... :(
>
> where can i see my domain setting?
>
> here is my domain detail
>
> Expanding base 'dc=kei,dc=kangean-energy,dc=com'...
> Result <0>: (null)
> Matched DNs:
> Getting 1 entries:
>>> Dn: dc=kei,dc=kangean-energy,dc=com
> 3> objectClass: top; domain; domainDNS;
> 1> distinguishedName: DC=kei,DC=kangean-energy,DC=com;
> 1> instanceType: 0x5 = ( DS_INSTANCETYPE_IS_NC_HEAD | IT_WRITE );
> 1> whenCreated: 9/3/2007 23:26:29 SE Asia Standard Time SE Asia Standard
> Time;
> 1> whenChanged: 2/18/2009 21:24:14 SE Asia Standard Time SE Asia Standard
> Time;
> 3> subRefs: DC=ForestDnsZones,DC=kei,DC=kangean-energy,DC=com;
> DC=DomainDnsZones,DC=kei,DC=kangean-energy,DC=com;
> CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> 1> uSNCreated: 4098;
> 1> dSASignature: <ldp: Binary blob>;
> 3> repsTo: dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0
> V1.timeLastSuccess: 12879449944 V1.timeLastAttempt: 12879449944
> V1.ulResultLastAttempt: 0x0 V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71
> V1.ulReplicaFlags: 0x10 V1.rtSchedule: <ldp:skipped>
> V1.usnvec.usnHighObjUpdate: 0 V1.usnvec.usnHighPropUpdate: 0
> V1.uuidDsaObj:
> 4bdde1ed-5a4e-4a70-81a4-15a8f790a3df V1.uuidInvocId:
> 00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
> 4bdde1ed-5a4e-4a70-81a4-15a8f790a3df._msdcs.kei.kangean-energy.com
> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
> dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
> 12879449887 V1.timeLastAttempt: 12879449887 V1.ulResultLastAttempt: 0x0
> V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x10
> V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 0
> V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
> 420ffd3f-1b7b-437e-961e-ab49b12a1806 V1.uuidInvocId:
> 00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
> 420ffd3f-1b7b-437e-961e-ab49b12a1806._msdcs.kei.kangean-energy.com
> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
> dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
> 12879449611 V1.timeLastAttempt: 12879449611 V1.ulResultLastAttempt: 0x0
> V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x10
> V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 0
> V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
> c50f4d07-2b7b-4d53-93cd-774fa63f61ed V1.uuidInvocId:
> 00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
> c50f4d07-2b7b-4d53-93cd-774fa63f61ed._msdcs.kei.kangean-energy.com
> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
> 3> repsFrom: dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0
> V1.timeLastSuccess: 12879450190 V1.timeLastAttempt: 12879450190
> V1.ulResultLastAttempt: 0x0 V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71
> V1.ulReplicaFlags: 0x70 V1.rtSchedule: <ldp:skipped>
> V1.usnvec.usnHighObjUpdate: 9227169 V1.usnvec.usnHighPropUpdate: 9227169
> V1.uuidDsaObj: c50f4d07-2b7b-4d53-93cd-774fa63f61ed V1.uuidInvocId:
> 8054edfa-4d1c-4b3a-83d6-3bae4dcae0b4 V1.uuidTransportObj:
> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
> c50f4d07-2b7b-4d53-93cd-774fa63f61ed._msdcs.kei.kangean-energy.com
> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
> dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
> 12879450187 V1.timeLastAttempt: 12879450187 V1.ulResultLastAttempt: 0x0
> V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x70
> V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 9081728
> V1.usnvec.usnHighPropUpdate: 9081728 V1.uuidDsaObj:
> 420ffd3f-1b7b-437e-961e-ab49b12a1806 V1.uuidInvocId:
> 2876ea87-f023-4217-b075-257c9df8342f V1.uuidTransportObj:
> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
> 420ffd3f-1b7b-437e-961e-ab49b12a1806._msdcs.kei.kangean-energy.com
> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
> dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
> 12879450111 V1.timeLastAttempt: 12879450111 V1.ulResultLastAttempt: 0x0
> V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x70
> V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 7402879
> V1.usnvec.usnHighPropUpdate: 7402879 V1.uuidDsaObj:
> 4bdde1ed-5a4e-4a70-81a4-15a8f790a3df V1.uuidInvocId:
> 7271d9ab-28f0-43da-a9db-2ded7daab9fd V1.uuidTransportObj:
> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
> 4bdde1ed-5a4e-4a70-81a4-15a8f790a3df._msdcs.kei.kangean-energy.com
> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
> 1> uSNChanged: 15054668;
> 1> name: kei;
> 1> objectGUID: dfae445b-dc9d-405d-ae1e-3b77ed3f69f2;
> 1> replUpToDateVector: <ldp error: cannot process UPDATE_VECTOR v.2>;
> 1> creationTime: <ldp error <0x0>: cannot format time field;
> 1> forceLogoff: -9223372036854775808 (none);
> 1> lockoutDuration: 1800;
> 1> lockOutObservationWindow: 1800;
> 1> lockoutThreshold: 5;
> 1> maxPwdAge: 7776000;
> 1> minPwdAge: 0 (none);
> 1> minPwdLength: 5;
> 1> modifiedCountAtLastProm: 0;
> 1> nextRid: 1003;
> 1> pwdProperties: 0;
> 1> pwdHistoryLength: 1;
> 1> objectSid: S-1-5-21-3132921636-2566841788-1541036888;
> 1> serverState: 1;
> 1> uASCompat: 1;
> 1> modifiedCount: 83;
> 1> auditingPolicy: <ldp: Binary blob>;
> 1> nTMixedDomain: 0;
> 1> rIDManagerReference: CN=RID
> Manager$,CN=System,DC=kei,DC=kangean-energy,DC=com;
> 1> fSMORoleOwner: CN=NTDS
> Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> 1> systemFlags: 0x8C000000 = ( FLAG_DISALLOW_DELETE |
> FLAG_DOMAIN_DISALLOW_RENAME | FLAG_DOMAIN_DISALLOW_MOVE );
> 11> wellKnownObjects: B:32:6227F0AF1FC2410D8E3BB10615BB5B0F:CN=NTDS
> Quotas,DC=kei,DC=kangean-energy,DC=com;
> B:32:F4BE92A4C777485E878E9421D53087DB:CN=Microsoft,CN=Program
> Data,DC=kei,DC=kangean-energy,DC=com;
> B:32:09460C08AE1E4A4EA0F64AEE7DAA1E5A:CN=Program
> Data,DC=kei,DC=kangean-energy,DC=com;
> B:32:22B70C67D56E4EFB91E9300FCA3DC1AA:CN=ForeignSecurityPrincipals,DC=kei,DC=kangean-energy,DC=com;
> B:32:18E2EA80684F11D2B9AA00C04F79F805:CN=Deleted
> Objects,DC=kei,DC=kangean-energy,DC=com;
> B:32:2FBAC1870ADE11D297C400C04FD8D5CD:CN=Infrastructure,DC=kei,DC=kangean-energy,DC=com;
> B:32:AB8153B7768811D1ADED00C04FD8D5CD:CN=LostAndFound,DC=kei,DC=kangean-energy,DC=com;
> B:32:AB1D30F3768811D1ADED00C04FD8D5CD:CN=System,DC=kei,DC=kangean-energy,DC=com;
> B:32:A361B2FFFFD211D1AA4B00C04FD7D83A:OU=Domain
> Controllers,DC=kei,DC=kangean-energy,DC=com;
> B:32:AA312825768811D1ADED00C04FD8D5CD:CN=Computers,DC=kei,DC=kangean-energy,DC=com;
> B:32:A9D1CA15768811D1ADED00C04FD8D5CD:CN=Users,DC=kei,DC=kangean-energy,DC=com;
> 1> objectCategory:
> CN=Domain-DNS,CN=Schema,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> 1> isCriticalSystemObject: TRUE;
> 1> gPLink:
> [LDAP://CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=kei,DC=kangean-energy,DC=com;0];
> 4> masteredBy: CN=NTDS
> Settings,CN=KEISBYDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> CN=NTDS
> Settings,CN=KEISPJDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> CN=NTDS
> Settings,CN=KEIPAGDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> CN=NTDS
> Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> 1> ms-DS-MachineAccountQuota: 10;
> 1> msDS-Behavior-Version: 0 = ( DS_BEHAVIOR_WIN2000 );
> 1> msDS-PerUserTrustQuota: 1;
> 1> msDS-AllUsersTrustQuota: 1000;
> 1> msDS-PerUserTrustTombstonesQuota: 10;
> 4> msDs-masteredBy: CN=NTDS
> Settings,CN=KEISBYDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> CN=NTDS
> Settings,CN=KEISPJDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> CN=NTDS
> Settings,CN=KEIPAGDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> CN=NTDS
> Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> 1> dc: kei;
> -----------
>
> I want to move my server from CN=NTDS
> Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
> to
> CN=NTDS
> Settings,CN=KEIJKTDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>
> I canat see the site name
> CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694 on my adsi editor
>
>

Reply With Quote
  #11  
Old 19-02-2009
Paul Bergson [MVP-DS]
 
Posts: n/a
Re: showing deleted active directory site
There is nothing you will be able to do. So here are the steps you will
wanto to take.

Read an article I have on decommissioning a DC to keep things well known up
front on possible issues
http://www.pbbergs.com/windows/articles.htm

On the lost dc run the following from a command prompt
dcpromo /forceremoval
http://support.microsoft.com/kb/332199

Clean up metadata
http://support.microsoft.com/?id=216498

Build you new site if you need to, make sure to define all subnets that
should be defined for it
http://technet.microsoft.com/en-us/l.../cc755768.aspx

Repromote the DC



--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.


"Paul Bergson [MVP-DS]" <pbbergs@nopspam_msn.com> wrote in message
news:uE652FfkJHA.1928@TK2MSFTNGP03.phx.gbl...
>I am attempting to find out some info, but from what I know you will have
>to flatten the dc, clean out the metadata and reinstall. I am not sure so
>I am waiting to see if there is any other info. Someone may just pop in on
>this thread or provide feedback to me. But you will have to wait.
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Fachlul" <Fachlul@discussions.microsoft.com> wrote in message
> news:654EF17B-FCB9-42BA-AF64-1057666D9587@microsoft.com...
>> Thank's I can see the object on active directory setting but still don't
>> know how to change the things back to normal.... :(
>>
>> where can i see my domain setting?
>>
>> here is my domain detail
>>
>> Expanding base 'dc=kei,dc=kangean-energy,dc=com'...
>> Result <0>: (null)
>> Matched DNs:
>> Getting 1 entries:
>>>> Dn: dc=kei,dc=kangean-energy,dc=com
>> 3> objectClass: top; domain; domainDNS;
>> 1> distinguishedName: DC=kei,DC=kangean-energy,DC=com;
>> 1> instanceType: 0x5 = ( DS_INSTANCETYPE_IS_NC_HEAD | IT_WRITE );
>> 1> whenCreated: 9/3/2007 23:26:29 SE Asia Standard Time SE Asia Standard
>> Time;
>> 1> whenChanged: 2/18/2009 21:24:14 SE Asia Standard Time SE Asia Standard
>> Time;
>> 3> subRefs: DC=ForestDnsZones,DC=kei,DC=kangean-energy,DC=com;
>> DC=DomainDnsZones,DC=kei,DC=kangean-energy,DC=com;
>> CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> 1> uSNCreated: 4098;
>> 1> dSASignature: <ldp: Binary blob>;
>> 3> repsTo: dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0
>> V1.timeLastSuccess: 12879449944 V1.timeLastAttempt: 12879449944
>> V1.ulResultLastAttempt: 0x0 V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71
>> V1.ulReplicaFlags: 0x10 V1.rtSchedule: <ldp:skipped>
>> V1.usnvec.usnHighObjUpdate: 0 V1.usnvec.usnHighPropUpdate: 0
>> V1.uuidDsaObj:
>> 4bdde1ed-5a4e-4a70-81a4-15a8f790a3df V1.uuidInvocId:
>> 00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
>> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
>> 4bdde1ed-5a4e-4a70-81a4-15a8f790a3df._msdcs.kei.kangean-energy.com
>> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
>> dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
>> 12879449887 V1.timeLastAttempt: 12879449887 V1.ulResultLastAttempt: 0x0
>> V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x10
>> V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 0
>> V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
>> 420ffd3f-1b7b-437e-961e-ab49b12a1806 V1.uuidInvocId:
>> 00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
>> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
>> 420ffd3f-1b7b-437e-961e-ab49b12a1806._msdcs.kei.kangean-energy.com
>> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
>> dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
>> 12879449611 V1.timeLastAttempt: 12879449611 V1.ulResultLastAttempt: 0x0
>> V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x10
>> V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 0
>> V1.usnvec.usnHighPropUpdate: 0 V1.uuidDsaObj:
>> c50f4d07-2b7b-4d53-93cd-774fa63f61ed V1.uuidInvocId:
>> 00000000-0000-0000-0000-000000000000 V1.uuidTransportObj:
>> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
>> c50f4d07-2b7b-4d53-93cd-774fa63f61ed._msdcs.kei.kangean-energy.com
>> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
>> 3> repsFrom: dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0
>> V1.timeLastSuccess: 12879450190 V1.timeLastAttempt: 12879450190
>> V1.ulResultLastAttempt: 0x0 V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71
>> V1.ulReplicaFlags: 0x70 V1.rtSchedule: <ldp:skipped>
>> V1.usnvec.usnHighObjUpdate: 9227169 V1.usnvec.usnHighPropUpdate: 9227169
>> V1.uuidDsaObj: c50f4d07-2b7b-4d53-93cd-774fa63f61ed V1.uuidInvocId:
>> 8054edfa-4d1c-4b3a-83d6-3bae4dcae0b4 V1.uuidTransportObj:
>> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
>> c50f4d07-2b7b-4d53-93cd-774fa63f61ed._msdcs.kei.kangean-energy.com
>> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
>> dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
>> 12879450187 V1.timeLastAttempt: 12879450187 V1.ulResultLastAttempt: 0x0
>> V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x70
>> V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 9081728
>> V1.usnvec.usnHighPropUpdate: 9081728 V1.uuidDsaObj:
>> 420ffd3f-1b7b-437e-961e-ab49b12a1806 V1.uuidInvocId:
>> 2876ea87-f023-4217-b075-257c9df8342f V1.uuidTransportObj:
>> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
>> 420ffd3f-1b7b-437e-961e-ab49b12a1806._msdcs.kei.kangean-energy.com
>> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
>> dwVersion = 1, V1.cb: 287, V1.cConsecutiveFailures: 0 V1.timeLastSuccess:
>> 12879450111 V1.timeLastAttempt: 12879450111 V1.ulResultLastAttempt: 0x0
>> V1.cbOtherDraOffset: 216 V1.cbOtherDra: 71 V1.ulReplicaFlags: 0x70
>> V1.rtSchedule: <ldp:skipped> V1.usnvec.usnHighObjUpdate: 7402879
>> V1.usnvec.usnHighPropUpdate: 7402879 V1.uuidDsaObj:
>> 4bdde1ed-5a4e-4a70-81a4-15a8f790a3df V1.uuidInvocId:
>> 7271d9ab-28f0-43da-a9db-2ded7daab9fd V1.uuidTransportObj:
>> 00000000-0000-0000-0000-000000000000 V1~mtx_address:
>> 4bdde1ed-5a4e-4a70-81a4-15a8f790a3df._msdcs.kei.kangean-energy.com
>> V1.cbPASDataOffset: 0 V1~PasData: version = -1, size = -1, flag = -1 ;
>> 1> uSNChanged: 15054668;
>> 1> name: kei;
>> 1> objectGUID: dfae445b-dc9d-405d-ae1e-3b77ed3f69f2;
>> 1> replUpToDateVector: <ldp error: cannot process UPDATE_VECTOR v.2>;
>> 1> creationTime: <ldp error <0x0>: cannot format time field;
>> 1> forceLogoff: -9223372036854775808 (none);
>> 1> lockoutDuration: 1800;
>> 1> lockOutObservationWindow: 1800;
>> 1> lockoutThreshold: 5;
>> 1> maxPwdAge: 7776000;
>> 1> minPwdAge: 0 (none);
>> 1> minPwdLength: 5;
>> 1> modifiedCountAtLastProm: 0;
>> 1> nextRid: 1003;
>> 1> pwdProperties: 0;
>> 1> pwdHistoryLength: 1;
>> 1> objectSid: S-1-5-21-3132921636-2566841788-1541036888;
>> 1> serverState: 1;
>> 1> uASCompat: 1;
>> 1> modifiedCount: 83;
>> 1> auditingPolicy: <ldp: Binary blob>;
>> 1> nTMixedDomain: 0;
>> 1> rIDManagerReference: CN=RID
>> Manager$,CN=System,DC=kei,DC=kangean-energy,DC=com;
>> 1> fSMORoleOwner: CN=NTDS
>> Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> 1> systemFlags: 0x8C000000 = ( FLAG_DISALLOW_DELETE |
>> FLAG_DOMAIN_DISALLOW_RENAME | FLAG_DOMAIN_DISALLOW_MOVE );
>> 11> wellKnownObjects: B:32:6227F0AF1FC2410D8E3BB10615BB5B0F:CN=NTDS
>> Quotas,DC=kei,DC=kangean-energy,DC=com;
>> B:32:F4BE92A4C777485E878E9421D53087DB:CN=Microsoft,CN=Program
>> Data,DC=kei,DC=kangean-energy,DC=com;
>> B:32:09460C08AE1E4A4EA0F64AEE7DAA1E5A:CN=Program
>> Data,DC=kei,DC=kangean-energy,DC=com;
>> B:32:22B70C67D56E4EFB91E9300FCA3DC1AA:CN=ForeignSecurityPrincipals,DC=kei,DC=kangean-energy,DC=com;
>> B:32:18E2EA80684F11D2B9AA00C04F79F805:CN=Deleted
>> Objects,DC=kei,DC=kangean-energy,DC=com;
>> B:32:2FBAC1870ADE11D297C400C04FD8D5CD:CN=Infrastructure,DC=kei,DC=kangean-energy,DC=com;
>> B:32:AB8153B7768811D1ADED00C04FD8D5CD:CN=LostAndFound,DC=kei,DC=kangean-energy,DC=com;
>> B:32:AB1D30F3768811D1ADED00C04FD8D5CD:CN=System,DC=kei,DC=kangean-energy,DC=com;
>> B:32:A361B2FFFFD211D1AA4B00C04FD7D83A:OU=Domain
>> Controllers,DC=kei,DC=kangean-energy,DC=com;
>> B:32:AA312825768811D1ADED00C04FD8D5CD:CN=Computers,DC=kei,DC=kangean-energy,DC=com;
>> B:32:A9D1CA15768811D1ADED00C04FD8D5CD:CN=Users,DC=kei,DC=kangean-energy,DC=com;
>> 1> objectCategory:
>> CN=Domain-DNS,CN=Schema,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> 1> isCriticalSystemObject: TRUE;
>> 1> gPLink:
>> [LDAP://CN={31B2F340-016D-11D2-945F-00C04FB984F9},CN=Policies,CN=System,DC=kei,DC=kangean-energy,DC=com;0];
>> 4> masteredBy: CN=NTDS
>> Settings,CN=KEISBYDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> CN=NTDS
>> Settings,CN=KEISPJDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> CN=NTDS
>> Settings,CN=KEIPAGDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> CN=NTDS
>> Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> 1> ms-DS-MachineAccountQuota: 10;
>> 1> msDS-Behavior-Version: 0 = ( DS_BEHAVIOR_WIN2000 );
>> 1> msDS-PerUserTrustQuota: 1;
>> 1> msDS-AllUsersTrustQuota: 1000;
>> 1> msDS-PerUserTrustTombstonesQuota: 10;
>> 4> msDs-masteredBy: CN=NTDS
>> Settings,CN=KEISBYDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> CN=NTDS
>> Settings,CN=KEISPJDC01,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> CN=NTDS
>> Settings,CN=KEIPAGDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> CN=NTDS
>> Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> 1> dc: kei;
>> -----------
>>
>> I want to move my server from CN=NTDS
>> Settings,CN=KEIJKTDC1,CN=Servers,CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>> to
>> CN=NTDS
>> Settings,CN=KEIJKTDC1,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=kei,DC=kangean-energy,DC=com;
>>
>> I canat see the site name
>> CN=Pagerungan\0ADEL:36a60937-0734-425a-982a-ee0ba1090694 on my adsi
>> editor
>>
>>
>

Reply With Quote
  #12  
Old 19-02-2009
Meinolf Weber [MVP-DS]
 
Posts: n/a
Re: showing deleted active directory site
Hello Fachlul,

As far as i know the only option is as described from Paul with demoting/cleanup/promoting
of the "lost" DC.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> We are running active Directory on Windows 2003 SP 2
>
> We have created a site on active directory sites and service and then
> delete the site from that console. The deleted site is still
> displayed when we execute right mouse click move server. (shown as
> "SITENAME\0ADEL:#GUID#)
>
> Here come the problem, one of our team accidentally move our server to
> the deleted site and we don't have a back up of our AD
>
> Could somebody tell me how to deisplay the deleted site or recover the
> deleted site so that we can move back our server to default first site
> name site?
>
> Really appriciate any help.
>
> Fachlul
>


Reply With Quote
Reply

  TechArena Community > Technical Support > Computer Help > Windows Server > Active Directory

« AD Inter- Forest Restructure    Moving user account to different AD (w2k -> w2k8) »

Thread Tools Search this Thread
Search this Thread:

Advanced Search


Similar Threads for: "showing deleted active directory site"
Thread Thread Starter Forum Replies Last Post
Creating a site in Active Directory 2003 Xiomar Active Directory 2 14-12-2010 05:26 AM
New Active Directory not showing up as DC! Davidstar Active Directory 1 13-04-2010 02:11 AM
2008 R2 - Active Directory Site Rename Rene Heinze Active Directory 5 05-02-2010 10:09 PM
site active directory brandwidth slardy Active Directory 2 10-06-2009 07:11 PM
question on upgrading from active directory 2000 to active directory 2003 Gary M Window 2000 Help 2 17-03-2007 02:27 AM


All times are GMT +5.5. The time now is 09:05 PM.

Contact Us - TechArena - Privacy Statement -