Environment
Novell ZENworks Desktop Management 7 - ZDM7 Application
Launcher (NAL)
Situation
When you have site OUs underneath other site OUs in your tree, Site
List processing may not choose the correct application and users
end up going across WAN links to access NAL application source
files.
For example, if your eDirectory structure is similar to this:
APPS.PROVO.UTAH.NOVELL
APPS.UTAH.NOVELL
and you have your closest server in the UTAH OU, i.e. ClosestSRVR.UTAH.NOVELL, then you create app1 in each APPS OU, have the provo app launch calc, and the utah app launch notepad, and you link them together in a site list.
Associate the utah app to your user, and launch the app repeatedly.
Sometimes calc runs (Provo app), sometimes notepad runs (Utah app), but it should always run the Utah app because thats where your closest server is.
For example, if your eDirectory structure is similar to this:
APPS.PROVO.UTAH.NOVELL
APPS.UTAH.NOVELL
and you have your closest server in the UTAH OU, i.e. ClosestSRVR.UTAH.NOVELL, then you create app1 in each APPS OU, have the provo app launch calc, and the utah app launch notepad, and you link them together in a site list.
Associate the utah app to your user, and launch the app repeatedly.
Sometimes calc runs (Provo app), sometimes notepad runs (Utah app), but it should always run the Utah app because thats where your closest server is.
Resolution
Fixed in ZENworks 7 with SP1 Desktop Management, available athttps://download.novell.com
Additional Information
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 picks one - causing this problem.
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 picks one - causing this problem.