DSM Explorer goes to Not Responding state while performing Agent deployments
search cancel

DSM Explorer goes to Not Responding state while performing Agent deployments

book

Article ID: 115811

calendar_today

Updated On:

Products

CA Client Automation - Asset Management CA Client Automation - IT Client Manager CA Client Automation CA Client Automation - Remote Control CA Client Automation - Asset Intelligence CA Client Automation - Desktop Migration Manager CA Client Automation - Patch Manager

Issue/Introduction

While performing an Agent deployment to a group of target machines, at certain point DSM Explorer enters into a "Not Responding" state, causing that the ongoing deployments are lost (regardless if they are in OK or Failure state):



User-added image

Environment

ITCM 14.0, 14.0 SP1 and 14.0 SP2

Resolution

When a deployment is made to large group of target machines, in some cases may be a lack of validation of what those IPs correspond to.

This problem may occur when one or more IPs on the target group belongs to a non-computer machine, like a Printer or Scanner, causing this problem to happen.

Based on network configuration, is possible to isolate the issue trying to send the Agent package only to that Pinter/Scanner machine and checking what the Deployment Wizard's scanner shows:



User-added image

Removing the non-computer device from the target group will solve the problem.