KNOWN ISSUE: Client Task Agent selects task servers based on how many clients are connected to them, not how many free slots are available.

Article:TECH127375  |  Created: 2010-04-20  |  Updated: 2010-04-20  |  Article URL http://www.symantec.com/docs/TECH127375
NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.
Article Type
Technical Solution


Issue



Client Task Agent selects Task Servers based on the count of how many clients are connected to them, this means that if a Task Server has a smaller limit than another in the same site then the one with the least registered clients will always be selected first even though it would be full.
Example, the Task Server on the NS has a limit of 100 clients and they have another task server on their designated site server which has a limit of over 1000 clients, because when the Client Task Agent does a client count check on both servers, since the NS task server has less clients connected, all agents will try and connect to it first even though it has reached its limit.

Priority: 4
Date: 4/19/2010 7:55:24 PM
Tick Count: 147042234
Host Name: Client1D
Process: aexnsagent.exe (368)
Thread ID: 2244
Module: client task agent.dll
Source: Client Task Agent
Description: CTaskServerNetCommsConnection::GetCurrentClientCountFromServerFinal(): http://taskserver.domain.com/Altiris/ClientTaskServer/GetComputerCount.aspx

******************

Priority: 4
Date: 4/19/2010 7:55:25 PM
Tick Count: 147043343
Host Name: ClientD
Process: aexnsagent.exe (368)
Thread ID: 2244
Module: client task agent.dll
Source: Client Task Agent
Description: CTaskServerNetCommsConnection::GetCurrentClientCountFromServerFinal(): Got 878 for server http://taskserver.domain.com/Altiris/ClientTaskServer/GetComputerCount.aspx

******************

Priority: 4
Date: 4/19/2010 7:55:24 PM
Tick Count: 147042234
Host Name: Client1D
Process: aexnsagent.exe (368)
Thread ID: 2244
Module: client task agent.dll
Source: Client Task Agent
Description: CTaskServerNetCommsConnection::GetCurrentClientCountFromServerFinal(): http://mainNS.domain.com/Altiris/ClientTaskServer/GetComputerCount.aspx

******************

Priority: 4
Date: 4/19/2010 7:55:25 PM
Tick Count: 147043343
Host Name: Client1D
Process: aexnsagent.exe (368)
Thread ID: 2244
Module: client task agent.dll
Source: Client Task Agent
Description: CTaskServerNetCommsConnection::GetCurrentClientCountFromServerFinal(): Got 106 for server http://mainNS.domain.com/Altiris/ClientTaskServer/GetComputerCount.aspx

******************

Priority: 4
Date: 4/19/2010 7:55:25 PM
Tick Count: 147043437
Host Name: CVGAPP67D
Process: aexnsagent.exe (368)
Thread ID: 2244
Module: client task agent.dll
Source: Client Task Agent
Description: CTaskServerNetCommsConnection::RegisterWithServerList(): Register order: mainNS.domain.com, taskserver.domain.com


Environment



Symantec Management Platform 7.0 SP3, SP4

Cause



Working as designed. Our code will check for how many client task agents are registered rather than checking how many more clients are still available to register as well.

Solution



This issue has been reported to our Symantec Development team. This issue is been reviewed to see how could be the best possible way to implement the desired change in a future release.

Supplemental Materials

SourceDEFECT
ValueETK 2025055
DescriptionLogged in Etrack (Symantec) database

Legacy ID



52490


Article URL http://www.symantec.com/docs/TECH127375


Terms of use for this information are found in Legal Notices