Site Lists are not picking closest server if site OUs contain site OUs

When site OUs exist underneath other site OUs in the tree, Site List processing is not choosing the correct application and users could end up going across WAN links to access NAL application source files.

Steps to Duplicate:

Have an eDirectory structure similar to this:

apps.provo.utah.novell

apps.utah.novell

Ensure that the closest server is in the utah OU.

> create app1 in each apps container

> have the provo app launch calc and the utah app launch notepad

> link the two apps together in a site list

> associate the utah app to your user

> launch the associated app repeatedly

Sometimes the calc app runs (provo app), sometimes the notepad app runs (utah app).  Since the closest server is in utah, the utah app should always be chosen.

The reason why this is happening is because NAL does a context compare between the site list apps and the closest server:

app1.apps.provo.utah.novell
app1.apps.utah.novell

closestSRVR.utah.novell

Since utah.novell is all that can be matched up, both apps are tied in the context compare. When apps are tied, NAL randomly chooses the one to use.