I have an OES/Netware 6.5 sp7 server running iManager 2.7 for managing DHCP. In the past we have been able to manage DHCP without specifying the location of the locator object and the administrative scope.

Over the past few days we have started getting Java exceptions when we attempt to view or modify DHCP objects. This occurs when the list of objects is being created and before the object is selected. However, if we specifiy the location of the locator object and the administrative scope the errors do not occur.

Now I understand the short answer is to start specifying the location of the locator object and administrative scope. However, I'm wondering if the is a known issue? Our tree is large with about 100,000 objects including 45,000 users in 86 locations with multiple subnets in many locations.

Is there a way to specify a default for the locator object and administrative scope?