This document details what troubleshooting steps to take if you receive the error "No Primer transport" when deploying agents.
It further discusses the ports necessary and shares and services that need be be active on the target machine.
When deploying agents via the Infrastructure Deployment Wizard, why is the resulting status of the job the following error "No Primer transport"?
Deploying agents starts with transferring the DMBoot.exe, DMKeydat.cer and DMSetup.exe (Primer + CAM) package to the target.
Once this is done, The primer install will be triggered to install via DMBoot.exe (CA BootStrap Service) along with CAM and used to facilitate the deployment of the actual CA IT Client Automation agent plugins onto the system. As soon as the trigger is processed, the temporary service will be removed. This usually happens very quickly and the temporary service may never been seen by the end user.
If the transfer of the primer fails with a "no primer transport" error, the following is a list of possible causes:
Make a NEW custom configuration policy and apply it to the Domain Manager directly or to a computer group containing this machine:
Go To Control Panel->Configuration->Configuration Policy-><Custom Policy Name>->DSM->Manager->Infrastructure Deployment
Set: AlwaysDeploy=1 AND AlwaysDeployPrimer=1"
For more details on meeting the prerequisites for deploying agents with the Client Automation Deployment Wizard please refer to the CA Client Automation Implementation guide at this link and look under "Implementing", then review the section "Infrastructure Deployment":