ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

In deployment jobs sometime the boot to production runs for many hours until time out

book

Article ID: 239616

calendar_today

Updated On:

Products

Client Management Suite

Issue/Introduction

After Windows images with Symantec Management Agent deploy, they cannot register with the task server and don't receive the task for the next steps. 

 

Cause

In this particular case, Notification Server's DNS name was different from the FQDN.

Also, based on the logs the Agent was using http instead of https to register with the NS and task server.

Environment

Release: 8.x

Resolution

In the Console go to Targeted Agent Settings> Agent/ Plug-ins> Targeted Agent Settings>Initial Settings> Advanced tab, changed the server URL to HTTPS. 

Also, In NS console> Settings> Agent/Plug-ins> Symantec Management Agent> Symantec management agent communication profile> NS Communication profile, make sure the resolvable name comes first.