Automation job fails to run after modifying Agent Registration Policy - Allow
Last Updated October 13, 2017
You've configured the 'Agent Registration Policy - Allow' within the NS console to prevent specific machines from registering with the NS console. You've removed the Host name = * value and added any other rule option. Now your automation jobs fail to start once the client machine has loaded into automation.
ITMS/DS 7.5 or newer through 8.1 RU3 currently
You will not receive an error message within the console after scheduling the job on the client machine. It will simply say the job is running. Once the client machine loads into automation you will also not see any errors. Your client machine will simply sit in automation and do nothing. If you review the pectagent.log or the smp.log you will see errors however. Here are a few examples of what you might see.
The reason why this is happening is because of the modified agent registration policy. By removing the Host name = * value from this policy you have effectively broken the ability for the PectAgent to register with the NS.
At this time, the Agent Registration Policy - Allow only applies to the production Symantec Management Agent. Removing the default Host name = * or adding additional rules to this policy breaks the automation PectAgent. Removing any additional rules and having just the Host name = * is currently the only way to allow automation jobs to run.
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe