Hi folks,
New here, and I have a question about a product that does not quite fit in other forums, this one seemed appropriate enough.
It seems that someone before me at my site had made an attempt at a DirXML implementation to sync a barely functional AD (the DNS was not functioning because it was trying to do dynamic record updates against named.nlm on Netware, not good) to a eDir tree.
I know very little about DirXML other than it was the precursor to IDM. I am not sure what NLMs would be running where or what software would be running on the Windows server. All I know is that I have a DirXML OU in my tree with related objects inside it. The DirXML OU is living on its' own partition, of which there is only one replica.
I am trying to work out a strategy to cleanly remove all traces of this product from my environment.
Do I need to find and unload NLMs that would be running, or software on the Windows box? Do I need to administer the objects in eDir to disable it? Then delete objects and then the OU and then remove the only replica of the partition containing the DirXML OU?
Do I need to think about modifications to the eDir schema that this product could have made?
The server that would have had a potential involvement with this is currently running NW65sp8, eDir 8.7xx. I have other NW and
OES SLES servers in my tree but the
OES SLES boxes have been commissioned much later after the fact.
Any thoughts or pointers appreciated.
TIA.
DirXML Removal
Threaded Mode
