Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Task Server

Updated: 21 May 2010 | 7 comments
Tim_Scott's picture
0 0 Votes
Login to vote

I had recently set up a power policy for shut down 4 computers in my network. This worked fine for a while but now it has started to spread to other computers that I do not want shut down. I have gone into the NS and deleted the power management job but the computers are still shutting down.

as a test I went and removed the Altiris Agent from the computers and this seemed to resolve the problem but the Agent has tobe on those computers for inventory and patch management. So I put the agent back on. The power is shutting off again even though no job exists. What can I do to resolve this problem.

Comments

jharings's picture
13
Nov
2009
0 Votes 0
Login to vote

Did you disable the policy before deleting?

Since you don't list your filter\target here, I'm not entirely sure how it could spread to other systems (could be a bad filter or even a bug).

That being said, deleting the policy before disabling it doesn't necesarily remove it from your systems, but it does make it very difficult to troubleshoot. In all honesty, I would contact support for resolution.

It's possible, if you can find the guid of the power management task to try and remove it from the policy .xml's on the clients, but I haven't attempted that.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Tim_Scott's picture
13
Nov
2009
0 Votes 0
Login to vote

I do not think I disabled the

I do not think I disabled the policy. We have a case open with Symantec but they are extreamly slow at responses regardless of this being a critical ticket. When we spoke to the technician he stated he did not really know what was causing the issue. Unfortunaly this is in a municipality and affecting out 911 dispatch computers shutting them down when they must always remain up and running.

jharings's picture
13
Nov
2009
0 Votes 0
Login to vote

See if you can find the client .xml policies

Copy a whole agent directory and sort out the .xml and log files. Sanitize it if you can and post it here (zip it up).

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Tim_Scott's picture
13
Nov
2009
0 Votes 0
Login to vote

I have attached it to the

I have attached it to the first post

jharings's picture
13
Nov
2009
0 Votes 0
Login to vote

Do you remember the schedule it was set to run at?

Just trying to sort through it.

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.

Tim_Scott's picture
13
Nov
2009
0 Votes 0
Login to vote

It was set to run every week

It was set to run every week day starting at 8:30 PM

jharings's picture
13
Nov
2009
0 Votes 0
Login to vote

I don't see any policy referenced

with that description or that time\date stamp. If you uninstall and reinstall an agent (although that would be a bummer) does the issue go away?

Jim Harings
HP Enterprise Services
1st Rule of Connect Club: Mark the post that helped you the most as a 'solution'. 2nd Rule of Connect Club:You must talk about Connect club.