|MS SQL||Microsoft SQL Server||1433|
|CA ITCM||Software Delivery||TCP||4728|
#1 Machines need not be in Domain for agent deployment.
#2 you should be using local admin password for agents
BASIC INFRASTRUCTURE DEPLOYMENT TROUBLESHOOTING CHECKLIST
If you are having issue using Infrastructure Deployment, here is a good checklist to go thru before calling support,
then you can find out exactly where your issue is and if you can tell the tech which step you are stuck at, it should make it quicker and easier to resolve your issue.
Resuming, we need check communication roundtrip between workstation and server.
1. Local Machine Shared files
1.1. Can the remote admin$ (Or configured replacement) share be accessed?
TEC479626 Can the ADMIN$ share be disabled on the targets after deploying the agent?
1.2. Can this share be accessed as 'localsystem'?
2. Check DNS responses
2.1. Do a 'ping' of the target and then a 'ping -a' of the returned IP to verify it is online and resolves to the expected DNS name.
2.2. If correct, do the same from the agent to the DM (Note the SS is not yet involved at this point).
2.3 try to CAMPING the agent from the DM, this SHOULD succeed.
3. Check the target admin$ share for 'dmsetup.exe' and 'dmkeydat.pmr' (.cer)
4. If there, check for the existence of the path '..\program files\ca\dmprimer'
5. If not there then trigger port 135 TCP is likely being blocked from DM to agent.
NOTE: Note, even though there is an option to 'Deploy via SS', this part always comes from the DM.
6. If the folder exists, try to CAMPING the agent from the DM, this SHOULD succeed.
7. Even if this fails, which is potentially valid if you are deploying via SS and have restrictions?
It should NOT fail when you camping the agent from the SS.
8. Ping the SS from the agent, perform a reverse lookup and verify correct info. as in #2 above.
9. CAMPING the SS from the agent and ensure proper result.
10. Run 'CAMPING <SS name> -s 40000' to ensure camping works with larger packets of
the size used in a deployment.
11. Perform the same camping test from the SS to the agent.
12. Now try 'camping -a <SS name>' from the agent and make sure no error is shown in the output.
13. Try 'camping -a <agent name>' from the SS and make sure no error is shown in the output.
14. If that all works, check the '..\program files\ca\dmprimer' folder for <SS/DM name>.pmr (.cer in 12.5)
15. If not there, it's likely an authentication issue. Contact support.
16. If there, check the '..\program files\ca\dsm\dmprimer' folder for the
existence of a folder called \CAUnicenterDSM\.
17. If not there, check the same folder for a file called 'primer1.pack'.
18. If primer1.pack is there but no folder from #17, then the transfer confirmation was never received or responded to by the SS.
19. If the '..\ca\dsm\dmprimer\CAUnicenterDSM' folder exists then the agent DID receive the agent package
and acknowledge that, but the agent install failed.
20. From here the agent should be installed.
21. CAF should start automatically CAF STATUS
22. Check if all the CA agent processes are installed DSMVER
23. Check Firewall Firewall ports for ITCM Managed Service
If you still have issue open issue with CA support http://support.ca.com and report these response tests.
Summary CA Client Automation - ITCM
Background process for Agent Deployment on a Windows machine
How to specify a different share instead of the Admin$ share for deploying agents?
"An error occurred connecting to the deployment manager. Click help for more information (DPM225281)"