Client not registered with task server

[Migration User]

Hi

We just updated ITMS 7.1 SP1 to ITMS 7.1 SP2 and also created new database as well.

We having one NS as task server and 6 remote site server who is task server as well.

We observer that suddenly on local and remote user not registered with task server and if we restart symantec management agent server then also it will not registered with task server but suddenly Full inventory task run on client system. Our inventory task for client is only once in week on monday.

I am not change our site server and task server configuration it is same which we updated prior ITMS 7.1 SP2

after that also why clinet not registered with task server? some time it registered and sometime not?

 

[Migration User]

We had a nightmare with a bunch of our site servers a while ago. they were working for a while then stopped.

We found that it was related to the dotnet client for the task server.

"2008 Task Servers:  Though already mentioned above, there are some items of note fir 2008 R2 severs that run IIS7 by default.  The main thing we see is that, by default in version 7.0 and 7.1 sp1, Task Servers often don't work "out of the box".  This is almost always a very quick "fix" involving going into IIS and modifying the default app pool to operate in Classic instead of Integrated mode.

1. On a server with shared roles, this may not be possible, so you can modify the ClientTaskServer application instead to use the classic-mode app pool.  It has the same net effect, and is what we do on the NS.

2. To find where to change this, go to Server Manager\Roles\Web Server and highlight "Internet Information Server".  Then, in the next pane to the right, expand your server name and highlight Application Pools.  Here you can change the Default App Pool (highlight it) and at the right, select Basic Settings.  This shows you the integrated option and you can change it to Classic.  Alternatively, if you continue browsing in the 2nd pane to Sites\Default Web Site\Altiris, right-click ClientTaskServer, select Manage Application\Advanced Settings and you can switch from using the Default App Pool to the Classic Mode App Pool."

http://www.symantec.com/business/support/index?page=content&id=HOWTO32603

The below help or howto articles were also referenced while trying to remove the problem and may help.

http://www.symantec.com/business/support/index?page=content&id=HOWTO63116&actp=search&viewlocale=en_US&searchid=1333526021757

http://www.symantec.com/business/support/index?page=content&id=HOWTO47803

http://www.symantec.com/business/support/index?page=content&id=TECH47470

http://www.symantec.com/business/support/index?page=content&id=TECH169086

Check your event logs and those on the clients that can't connect to the server and see if anything stands out but the logs are the first place to go after you check the servers are configured correctly.

[Migration User]

You say you created a new database with SP2, which suggests a new install, but then you say nothing has changed since prior to the upgrade, which suggests an existing database and an upgrade.  Is this brand new or an upgrade from an existing database, even if you cloned the existing database?

You'll want to make sure you correctly set all the pre-requisites for task server prior to deploying task server to those systems:
http://www.symantec.com/docs/TECH46601

 

[Migration User]

Hi

Can i get sql query report which gives me  computers not registered with task server

[Migration User]

If you dont have the CRT Reports install download and add these reports in to your reports console: https://www-secure.symantec.com/connect/downloads/crt-reports-symantec-management-platform

In there is a report called 'Computers not requesting configuration in Last 'N' days'

If it can't talk to the task server theres a good chance its either retired off the network or not able to communicate.  The reason i noticed the devices weren't responding to task servers was because of the altiris logs on my NS Server. The devices were failing to pickup and execute policies and sending NS logs stating such.

I ran Remote Altiris Agent Diagnostics (RAAD) at the machines. This can be found by searching for it or theres a link in here with a list of other useful tools for troubleshooting: http://www.symantec.com/business/support/index?page=content&id=HOWTO77027

Once i fixed the server issue. I reset the agent's and restart the services on the agents and they start communicating as you would expect.

[Migration User]

Hi Mclemson

We were using ITMS 7.1 SP1 but because of some reason we created new database name Symantec_CMDB_1 and also upgraded from SP1 to SP1 at the same time.

Now in every location we reinstall all the task server by doing uninstall and install and after that we now seen that many are registered with task server but many are not for local as well remote location.

We restarted there altiris agent services but still not registered with task server.

[Migration User]

You're getting there.  Now that most, but not all agents, have checked in, check the agent log of one of the computers having trouble.  I assume that you're describing a situation now where some agents at a site check in and some do not.  Agent logs should shed light.