NDSLookupForDB fails on deleted OU.

Just a little background to this long-running problem: We're running
ZENworks for Desktops 4.0.1 Inventory across several dozen servers
throughout our organization, all setup to roll-up to regional Intermediate
servers and from there to a single Root database. Most of these servers
were originally 3.2, were upgraded to 4.0.1 and now run with either ir5,
ir6, or ir7. After the upgrade, we had many straggler 3.2 workstations in
the inventory that just wouldn't remove themselves over time. I'm now
trying to come up with a good way to clean-up our inventory state-wide.

I've tried using the NDSLookupforDB service, but on the ir5 servers it
always fails when encountering an OU which doesn't exist. For example:
searching for workstations in the Win9x.Workstations.Davis... OU (Which was
deleted long ago) the following returns in the log file.

ZENInv - DB NDS Lookup: search DirContext:[Root]
ZENInv - DB NDS Lookup: NDAPAuthUtilities: search: Base DN =
WIN9X.WORKSTATIONS.DAVIS...[Etc...], filter = (Object Class=Workstation)
ZENInv - DB NDS Lookup: NamingException
javax.naming.NamingException. Root exception is
com.novell.service.jncp.NDSException: ccode = -601 (0xfffffda7)
at
com.novell.service.jncp.NSIExceptionBuilder.build( NSIExceptionBuilder.java:82)
at
com.novell.service.jncpv2.net.BasicNetService.sear ch(BasicNetService.java:1260)
....
Etc...

It seems to retry this process about 5 times before giving up and at that
point simply fails and stops the NDSLookupForDB service. The
DeleteWSList.txt of course comes back as a 0 KB file. This never shows up
as a problem on the ir7 servers, but we only have a few of them in the tree
right now, and I'd rather not ask all of the admins to run around upgrading
them all if this will work fine on ir5.

Sorry for the long-winded post, I value any and all input on this matter as
I have tried all I know to try myself.

---
John Sheats