Video Screencast Help

configure as task server client going offline in Altiris 7.5

Created: 24 Mar 2014 | 10 comments
Sachin Sawant's picture

Hi Support,

After configure as task server client going offline in Altiris 7.5.

Operating Systems:

Comments 10 CommentsJump to latest comment

Alex Bizjajev's picture

Hi Sachin,

May you provide slightly more details of your scenario? Was it clean install of 7.5 or upgrade? Exact OS on task-server computer? "Off-line" means client cannot connect to network anymore of cannot see NS server or cannot register on Task Server?

And if it is possible to attach logs from the problematic task server it will be really helpful for investigations (..\Altiris\Altiris Agent\Logs).

Thank you,

Alex.

Sachin Sawant's picture

Hi Alex,

Thanx for reply I am new install the agent on server.

Please find attachment of logs

AttachmentSize
logs.zip 26.58 KB
Alex Bizjajev's picture

Hi Sachin,

Thank you for the logs. At the first sight seems like user under which SMA agent is running don't have access to the Altiris Agent directory. Please check under that user Symantec Management Agent service is running -  and verify this account have enough rights on a local computer to access Altiris Agent folder.

Also, please check the state of the Notification Server to be sure the activities of NS are not paused: NS Console -> Settings - All Settings. Expand Notification Server folder in the left pane and select "Notification Server Settings" item. Verify "Server Processing" is On.

Thanks,

Alex.

Sachin Sawant's picture

Hi Alex,

I am checking Altiris agent (on site server) communicate with NS server, Server processing is On.

The site server is communicate properly with NS but is not taken task server. Please find the scree short for your understanding.

This issues is coming only two site server and my other site server is working fine.

AttachmentSize
site Server.docx 44.69 KB
Igor Perevozchikov's picture

Please send logs from your Site Server, where CTA unable to register with TS ⇒ C:\ProgramData\Symantec\Symantec Agent\Logs

  • Click on "Reset Agent" button to try to register CTA and collect logs.

Because previously attached logs, contain only information about failure to create shared package path for downloaded packages on your Package Server and there is no information about why CTA unable to register with Task Server.

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
Alex Bizjajev's picture

Hi Sachin,

If client cannot communicate with the task server then in most cases investigations should contain the next steps:

1. On NS: check Task Service status in Site Servers - it should be "Green".

2. On site server side: check status of "Altiris Object Host Service" and "Altiris Client Task Data Loader" - both should be started

3. On site server side: open IIS Manager and check ClientTaskServer web-directory exists under Default Web Site\Altiris. Expand it - there should not be errors.

4. On client side: clean SMA logs, and restart SMA agent service. After restart logs should contain information about attempts to select Task Server for registration from "Client Task Agent" module. Try to ping TS by exactly the same name as in logs - ping should work.

If you may perform step_4 and before service restart you could modify registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris Agent\Event Logging\LogFile 

by setting "Severity" value to 255 then additional traces will be gathered. Such log could say much more about the problem (log that you have attached previously contains similar 5 records for 3 seconds period and it's hard to understand the reason of the problem). I will be reasonable to change the “Max files” value to bigger value, as there will be a LOT of traces in log with such severity.

Thank you,

Alex.

Igor Perevozchikov's picture

I see that now CTA on your Site Server has been registered to Task Server, which is running on apkricnlbutil02.dc.hk.publicisgroupe.net

"3/26/2014 5:27:50 AM","Connecting ..., host: [apkricnlbutil02.dc.hk.publicisgroupe.net:50124] resource: [b425caca-246f-4357-978f-493fc676ca53]","Client Task Agent","Client Task Agent.dll","3644","Informational"

"3/26/2014 5:27:50 AM","Connection is established successfully","Client Task Agent","Client Task Agent.dll","3644","Informational"

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread
Sachin Sawant's picture

Yes,but site server is register after remove the task services.

Igor Perevozchikov's picture

You've removed "Task Service" for this same machine, where CTA wasn't able to register with Task Server?

Now it's hard to determine what was a root cause of problem with registering CTA, since this Task Service is already removed.

  1. Don't forget that, first you can find an answer for your question in Knowledge base
  2. If answer solves your question, then please mark as solution to close a thread