Re: Restoring Active Directory

From: Joe Richards [MVP] (humorexpress_at_hotmail.com)
Date: 09/23/04 

Date: Thu, 23 Sep 2004 12:27:29 -0400

Make part of your process to delete the objects (or attributes on other objects)
prior to defuncting. That way the data gets cleared out of AD.

You always want to be careful with companies wanting to extend your schema, most
of them don't seem to understand what they are doing. There have been many
examples of companies screwing this up including Cisco even.

  joe 

--
Joe Richards Microsoft MVP Windows Server Directory Services
www.joeware.net
Jeff Gamet wrote:
> I have just upgraded my test network DC to 2k3 and am just in the process of 
> verifying that all is well before I attempt to defunct these objects.  I have 
> my fingers crossed as this has been going on for over 3 weeks now.  As far as 
> backing it up I will do so, however the new version of the software that 
> started all of this doesn't used these schema changes any more so I guess you 
> could say they are just orphaned.  As far as the vendor they don't have a 
> clue is my take.  They have know about this for over a year, but of course 
> never bothered to warn their installers of this danger and they have given me 
> their Microsoft case number, but I haven't heard from them in a couple of 
> days.  I'm disgusted with them!
> 
> But you live and learn right!!!  I've learned alot of stuff regarding the AD 
> and Schema and the like that'll benefit me in the future so all is not lost.  
> I appreciate the help and I'll let you know how this turns out.
> 
> "Joe Richards [MVP]" wrote:
> 
> 
>>If you upgrade to 2K3, you will be able to defunct the old bad attribs. This 
>>should allow you to apply your Exchange schema mods (test in a test lab forest 
>>prior to doing it in production so you know the whole process and what the 
>>catches are). Note you should export any info in the directory that the bad 
>>attribs/objects have so you don't lose it all.
>>
>>What exactly is the vendor saying?
>>
>>
>>--
>>Joe Richards Microsoft MVP Windows Server Directory Services
>>www.joeware.net
>>
>>
>>
>>Jeff Gamet wrote:
>>
>>>I will keep that in mind next time..  
>>>
>>>Yea and I have been able to move forward to the point where I am now.  I 
>>>either figure out how to modify the attributes for the other vendor (if it's 
>>>possible) or reinstall my forest, which is very undesireable.  Unfortunately 
>>>the vendor is of no help and I'm extremely frusterated at the moment.  My 
>>>last hope appears to be to upgrade my dcs to W2003 in hopes that it will 
>>>allow me to modify the attribute as W2000 doesn't.
>>>
>>>"Joe Richards [MVP]" wrote:
>>>
>>>
>>>
>>>>I would say put on the original question the details of why the response didn't 
>>>>work for you.
>>>>
>>>>I recall answering several of your threads as well but that is a couple among 
>>>>thousands of responses, I don't recall the specifics other than some moron 
>>>>vendor screwed you in the *** because they didn't know what they were doing 
>>>>with AD and used a schema prefix and linkids that they didn't have properly 
>>>>registered.
>>>>
>>>>--
>>>>Joe Richards Microsoft MVP Windows Server Directory Services
>>>>www.joeware.net
>>>>
>>>>
>>>>
>>>>Jeff Gamet wrote:
>>>>
>>>>
>>>>>Well I am just looking for answers, so I'm sorry if I wasn't aware of these 
>>>>>supposed "manners" that you speak of.  This question that I asked about 
>>>>>restoring to the System State is not the same question that I had previously 
>>>>>asked, but a different question that grew out of answers from the first one.  
>>>>>Where am I supposed to put this question??  On the original question?
>>>>>
>>>>>"Cary Shultz [A.D. MVP]" wrote:
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>Okay,
>>>>>>
>>>>>>It is often confusing for all of us when someone has a post and receives
>>>>>>some answers ( maybe solves the issue or not ) and then posts the same thing
>>>>>>a few days later.  This is usually considered 'bad manners'.  But, I am not
>>>>>>your mother so there will be no hand-slapping from me!  Just trying to let
>>>>>>you know ( and everyone else ) so that it does not happen too often! ;-)
>>>>>>
>>>>>>A better idea might have been to let all of us know - in the original post -
>>>>>>that Chriss' solution did not resolve the issue and that you are open to
>>>>>>more suggestions.
>>>>>>
>>>>>>Cary
>>>>>>
>>>>>>"Jeff Gamet" <JeffGamet@discussions.microsoft.com> wrote in message
>>>>>>news:53A826C8-40D3-4EEF-9677-2AE8698F7FDE@microsoft.com...
>>>>>>
>>>>>>
>>>>>>
>>>>>>>Yes, but it is still not resolved as to how I remedy this situation so I'm
>>>>>>>exploring all my options.
>>>>>>>
>>>>>>>"Cary Shultz [A.D. MVP]" wrote:
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>Jeff,
>>>>>>>>
>>>>>>>>I thought that Chriss answered this question already for you.  I want to
>>>>>>
>>>>>>say
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>that I remember reading this.  Was it in this NG or in the Widows Server
>>>>>>
>>>>>>NG?
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>Cary
>>>>>>>>
>>>>>>>>"Jeff Gamet" <JeffGamet@discussions.microsoft.com> wrote in message
>>>>>>>>news:F835B437-D17A-4D7D-B58E-4C917424F6C7@microsoft.com...
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>A third party app that extended the schema is using LinkIDs that
>>>>>>
>>>>>>Exchange
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>is
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>trying to use during setup
>>>>>>>>>
>>>>>>>>>"Simon Geary" wrote:
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>>Nope, I'm afraid not. You can't do an authoritative restore of the
>>>>>>>>
>>>>>>>>schema
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>NC. What is the conflict, perhaps there are other ways around it?
>>>>>>>>>>
>>>>>>>>>>"Jeff Gamet" <JeffGamet@discussions.microsoft.com> wrote in message
>>>>>>>>>>news:95D1E025-F6E3-46EB-9F78-8A19BD24CF28@microsoft.com...
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>>If I restore AD from my system state backup will it restore the
>>>>>>
>>>>>>schema
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>to
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>>the
>>>>>>>>>>>state it was at prior to the backup?  Long story, but I have an
>>>>>>
>>>>>>3rd
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>party
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>>app
>>>>>>>>>>>that has extended the schema and it is now interfering with a MS
>>>>>>
>>>>>>app
>>>>>>
>>>>>>
>>>>>>
>>>>>>>>that
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>>>is
>>>>>>>>>>>trying to extend the schema.
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
Loading