NS7 - Agent is shutting down

[Migration User]

I have built a New NS7 test lab for office and testing NS7.0 SP5. We also have NS 6.5 running.

We have around 500+ client machines so according built a test lab NS7, we do not have Site server (Not sure if this is required for package push)

Presetntly we have created a new Test OU and added clients to it and deployed agent to the Test OU.

Problem is after the agent is installed on the test machine, in Task status showing Shutting down.Not sure whats wrong. We goggled and found

Turn on the NSAgent config policy that is associated with a filter for XP machines, and then refresh that filter:

1. Go to Settings > Agents/Plug-ins > Targeted Agent Settings
2. Find the policy that matches your OS type (in this case, "All Desktop Computers (excluding 'Site Servers')"
3. Turn the policy ON.
4. Go to the agent machine and click on Update in the Agent Settings.

Even this is not working

[Thomas K]

This is the forum for Connect site issues, I am moving your thread to the Altiris forum.

 

Thomas

[Migration User]

For 500 clients you don't necessarily need a stand alone site server, but if you can have one, it takes some pressure off the NS. Regardless, as long as the NS has the client task server installed and configured on it, it should be able to start registering clients.

Settings -> Notification Server - Site Server Settings.

One gotcha in the past has been proxy servers in the environment, let us know if you are using proxies for web access.

[Migration User]

We have setup a test environment for NS7 and we have discovered that we cannot push out any jobs to our test clients. When checking the agent task status it says 'shutting down'. We have uninstalled the agent on one of the machines and as soon as it calls into the server for the 1st time the status automatically changes to shutting down.

We dont have any proxies setup. Please advise how do we resolve this.

[Alex Bizjajev]

Please check if service "Altiris Object Host Service" is up and running on the NS machine. Try to restart it and check if it will help.

Also, go to Console -> Settings -> NS -> Site Server Settings. Select "Site Service" -> "NS_NAME" -> Services node. Expand "Task Service" section. Review the status of the task service and global settings for the task service, including the ports that need to be open.

Thank you,

Alex.

[Migration User]

Altiris Object Host service is up and running on the NS Machine,restarted the service. Also checked the "Task Service" Global setting for Ports. Checked all the setting and Not sure whats wrong but still see 'shutting down' on the client machine Task status.

 

Thank you,

Pradeep

[Migration User]

Can you restart these three services?

Altiris Client Task Data Loader
Altiris Object Host Service
Altiris Support Service

A different user had a similar issue and this resolved the problem.

If you force a particular agent to Update configuration and check for tasks, does this change the status from Shutting down to Waiting for tasks?

[Migration User]

As told restarted the 3 services and checked but still the same. When clicked on Reset Agent on the client machine, the status changes to "Received request to stop running tasks"

[Migration User]

Try registering "Client Task Agent.dll."  I've seen issues with the agent before where this not being registered would cause issues, though typically that message is "Agent not initialized," not "Agent shutting down."

In either case, the file is found at C:\Program Files\Altiris\Altiris Agent\Agents\Client Task Agent\Client Task Agent.dll (or pretty close).  From a command prompt, runu the command regsvr32 "Client Task Agent.dll"

[Migration User]

I ran into this exact issue with the client indicating "shutting down" and when we selected "Reset Agent" it then indicated "Received request to stop running tasks".

In our case this was due to the credentials for the Service Account (Log on as) being changed/updated. This was preventing the services from properly starting. Reset the credentials for the services and everything was good to go and our agents began responding with "Waiting for Tasks". :)