Issue with the ZAA

[theflyingcorpse]

Hey,

We've upgraded our server farm to ZCM 11, after having tested it throughtly in LAB. Some workstations are also running the newer agent and it works flawlessly as far as I can see.

However, deploying the agent, via imaging does not work properly.

Case:
- Upgraded agents from 10.3.1 properly use the location rules and finds the servers.
- Fresh 11.0 agents are stuck in "Default Location" with "Default Network...", and thus are unable to properly communicate. 8 out of 10 times, it talks to a server thats in a different firewall zone, a client of "that" type is not allowed to talk to, thus failing. The location rules are working and as I said before, the upgraded clients work 😉


The XML files in the client contains the proper servers, yet its unable to use the rules, for some unkown reason.

Other than that, great work with this .0.0 release, no issues with a MSSQL backend on a mixed server platform 😉

[Anonymous_User]

Theflyingcorpse,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

[steinbachl]

Granted this is many months after your original question... but I also am experiencing similar results using 11.1. Fresh installs of the zaa agent are stuck with 'Default Location' while existing agents are working properly.

Once a machine does work properly, it will never show 'Default Location' again, but rather ~unknown~ or the custom Location name we defined in ZCC.

This problem also only happens when you configure the ~unknown~ location to Exclude the Closest Server Default Rule which is important to us.
We do have a SR open on this case. I am wondering who else has run into this?

[kvallish]

Check if the ZES service is running. If not, start off the same and then refresh/restart the agent service.