Symantec Management Platform (Notification Server)

For whatever reason our Inventory Agent package was set to "delete if unused for 0 days" (ie: delete immediately)  We have fixed this issue by setting the agent to "Never Delete", so now, new machines should be getting the package and running the inventory tasks appropriately. Since we have an unknown number of machines 'out there' that have the Inventory Agent Package "DISABLED", what is the best way to get that package re-enabled on those workstations - the folder {01B54EB5-3679-4C73-9E10-E169D5A5EC59} is sitting on the workstations in question there without any package files (ie: no CACHE folder).  Should I create a job that looks for the CACHE folder and if it is not found, delete the entire folder so the agent will reinstall?  I don't want to reinstall the agent if it is functional.  Any suggestions how to get Inventory Agent Package functional on these machines again?

If so, make sure the computers in question are in the targeted collections, and that the schedule is set appropriate (weekly scans for example).

Hi all,

were you actually able to resolve this?

We've got a similar issue, and are stuck in a loop because the AexInvSoln.exe is not available on the PC, so Inventory is not running, and the Inventory Package remains disabled (as the target machine is showing in NS as having the package installed)

I've even uninstalled agents/client and re-installed, still no go.

Any help would be appreciated,
Justin

I can't say I've seen this myself before, but instead of uninstalling the agent, you may want to try to do an AeXAgentUtil.exe /resetguid and delete the machine's record on the NS so the NS thinks it's a new machine.  That should cause it to get a new set of policies.  Not a real great long term solution, but definitely good for troubleshooting.

Hi dfrancis,

I actually found that if i run a normal inventory task (rather than a Job from Task Server), the AexInvSoln gets re-enabled and pushed back out to the clients. I then stop/start the Agent, and the Task Server job seems to work aok.

No idea why the Inventory task is different to the inventory action step in Task Server, but the above has worked on 10+ clients so far.

Ahh, completely missed the part that you were using Task Server.  Glad everything is working out now!