Reasons that agents are not eligible for auto-configuration

If a "needs to be configured" message appears for an agent on the Computers page, the agent is not eligible for auto-configuration. This can occur if:

• The agent is not a Windows agent, or is a Windows agent version that is not supported for auto-configuration. Agent auto-configuration is supported with Windows Agent version 8.90a or later.

• An encryption password was not specified when the agent was installed. See Install the Windows Agent and plug-ins.

• An Image job template is selected for the child site, but the Image Plug-in is not installed with the agent.

• The agent has more than one vault registration (vault setting), or has a vault registration that does not match the vault profile selected for agent auto-configuration in the site.

• The agent has one or more backup jobs. This could occur if a backup job was manually configured before the Agent Configuration task ran in Portal.

• The agent is registered to a site where agent auto-configuration is not fully set up (e.g., a job template is not selected). See Set up agent auto-configuration.

  IMPORTANT: Auto-configuration must be enabled in the child site when the agent first registers to Portal. An agent will not be automatically configured if you enable auto-configuration after the agent is registered to Portal.