ITCM agent upgrade using batch file

[Amosu Babatunde]

Hello all,

Good day and trust this enquiry meet you all well.

We just installed a fresh Domain Manager ver14 in our environment and have upgraded our Scalability Servers to 14 as well.

Now we are in the process of upgrading the agent on end user's systems to 14 from 12.5 but we discovered so many flaws while running this from the Infrastructure Deployment Wizard so we decided to build a batch file to manually do this on user's machine.

We picked a single system and executed the batch file and we could see the "deploywrapper" running on the task manager but this stays there forever. We monitored this for hours but the "deploywrapper" didn't disappear and agent didn't install on the machine.

We then decided to completely uninstall the older agent on the system and run the batch file again but the case remain the same.

We therefore request the help of every individual who has ever faced this kind of issue before or who have ideas on how best this could be resolved as soon as humanly possible.

Thanks all as I awaits swift responses.

 

Warm Regards,

Amosu

[Steve Parker]

You need to check the logs in the %TEMP% directory to see what its doing.

[mccst05]

Don’t use infrastructure deployment to upgrade existing agents, use the software delivery packages provided for that purpose.

 

Steve McCormick, ITIL

CA Technologies

Principal Services Consultant

[e-mail]

<mailto:[e-mail]>

[Brian_Fontana]

Building on the replies here, as there's two angles here...

 

What does the %temp%\TRC_DeployWrapper_ITRM.log say?  If it's hanging for hours, we need to understand what it's hanging on.  Is this happening for all PCs you are attempting to upgrade?

 

Second angle is what Steve says.  Infrastructure Deployment is typically used for deploying NEW agents.  Once you have an existing agent, you should upgrade via software delivery.  Though software delivery will also be using Deploywrapper, though with a different entrypoint than command line usage.

 

Since some degree of troubleshooting is involved here, I would also recommend opening a support case...

 

-Brian

[Amosu Babatunde]

Hello Brian,

Unfortunately the logfile is so large and could not be attached here.

We would have also used the Software delivery package but the deployment port 445 is blocked on our network due to some critical security reasons.

Is there any other method this process could be achieved?

Awaits usual swift responses.

Warm Regards,

Amosu

[mccst05]

Using the Software Delivery package does not require port 445, it requires only the standard ITCM ports UDP 4104 and TCP 4728

 

Steve McCormick, ITIL

CA Technologies

Principal Services Consultant

[e-mail]

<mailto:[e-mail]>

[Amosu Babatunde]

Thanks Stephen,

We will try this and update the community.

 

Warm Regards,

Amosu