Hello dear community, somebody can help me?
When I try to deploy an agent to some machines, I'm getting this error
after that a few seconds
I do this process
Client Automation - Deployment Wizard - Unexpected - CA Knowledge
And it didn't work either... Can somebody help me PLEASE!??
Test if the admin$ share is accessible from DM to target:
From the domain manager, Start --> Run --> \\192.168.92.182\admin$
- Ensure the Windows administrative shares are enabled (e.g. admin$).
- Ensure the Windows File Share ports are open on the firewall.
- Ensure the required basic ITCM ports are open on the firewall, bi-directionally: UDP/4104, TCP/4728,7163
Here's the basics of how deployment works to a Windows endpoint:
1- The target machine is resolved to an IP address and the deployment manager tries to access the ‘ADMIN$’ share on the target machine (usually c:\windows). Note: This is a configurable share if ‘ADMIN$’ is not desired.2- DMBoot.ex get copied via file share to admin$ and temporarily installed as a Windows service called ‘CA Deployment Bootstrap Service’.3- That service is triggered over port 135 TCP (Remote Procedure Call (RPC) service port) and reaches out to the Domain Manager (by default) or a remote Scalability Server if specified to ask for the rest of the deployment ‘base files’.4- Dmkeydat.cer, DMsetup.exe and msvcr71.dll are copied into the target admin$ share.5- The Service then triggers the DMSetup.exe and uninstalls itself.6- DMSetup.exe installs both CAM (CAM install location can always be found at ‘%cai_msq%’) and DMPrimer. Note1: If CAM is already installed, no matter what version it is, no CAM install will be run when DMSetup.exe executes. CAM will be upgraded if needed when the agent MSI executes however.Note2: DMSetup.exe leaves its MSI install log-- C:\dmmsi.log.7- DMPrimer reaches out to the pre-set location (DM by default or SS if specified) and tries to communicate via CAM.8- Dmkeydat.cer is copied into the DMPrimer root folder (typically ..\ca\dsm\dmprimer\ ) and certificate authentication between the two points take place.9- Upon successful authentication ‘dmkeydat.cer’ is renamed to ‘<DM FQDN name.cer>’ (or ‘<SS FQDN name.cer>’ if pointing to an SS) Ex. MyTestServer.mycompany.com.cer.10- DMPrimer now starts the download of the compressed agent package from the DM (or SS) as ‘Primer1.Pack’.Note1: If for some reason ‘Primer1.Pack’ is not deleted and the copy needs to retry, the new file will download as ‘Primer2.Pack’ etc…Note2: The ‘Primer1.pack’ file is the same compressed file stored in ‘%sdroot%\..\packages\private\CAUnicenterDSM’ on the domain manager.11- When complete, the final compressed file is validated and receipt of the file is confirmed to the DM (or SS) by DMPrimer, via CAM.12-Once validation completes successfully, (via CAM) the file is unpacked into a folder called ‘CAUnicenterDSM’ in the root of the ..\ca\dsm\dmprimer\ folder.13- The agent install is now invoked as LocalSystem rather than any user specified in DSM Explorer for the initial file copy to ADMIN$.14- When the install completes a client registration will automatically occur and SD and AM job checks will execute.
Thanks for the help Brian! I have a question, I have the CA Client Automation 14.0.2000.255 version. and the .ddl the deploy copied is this: msvcr100.dll that's correct? And when I check if the CA folder was created... it didn't, but the machine has Dmkeydat.cer, DMsetup.exe and msvcr100.dll.
MSI (s) (10:BC) [15:17:47:278]: Note: 1: 1708MSI (s) (10:BC) [15:17:47:279]: Transforming table Error.
MSI (s) (10:BC) [15:17:47:281]: Transforming table Error.
MSI (s) (10:BC) [15:17:47:282]: Producto: CA DSM DMPrimer -- Fallo en la operación de instalación.
MSI (s) (10:BC) [15:17:47:283]: Windows Installer instaló el producto. Nombre del producto: CA DSM DMPrimer. Versión del producto: 14.0.2000.255. Idioma del producto: 1034. Fabricante: CA, Inc.. Resultado de la instalación: 1603.
MSI (s) (10:BC) [15:17:47:284]: Attempting to delete file C:\Windows\Installer\526bd6d7.mstMSI (s) (10:BC) [15:17:47:293]: Deferring clean up of packages/files, if any existMSI (s) (10:BC) [15:17:47:293]: Attempting to delete file C:\Windows\Installer\526bd6d7.mstMSI (s) (10:BC) [15:17:47:294]: Unable to delete the file outside of the engine. LastError = 2MSI (s) (10:BC) [15:17:47:294]: MainEngineThread is returning 1603MSI (s) (10:B4) [15:17:47:300]: RESTART MANAGER: Session closed.MSI (s) (10:B4) [15:17:47:300]: No System Restore sequence number for this installation.=== Registro detenido: 21-12-2018 15:17:47 ===MSI (s) (10:B4) [15:17:47:315]: User policy value 'DisableRollback' is 0MSI (s) (10:B4) [15:17:47:315]: Machine policy value 'DisableRollback' is 0MSI (s) (10:B4) [15:17:47:315]: Incrementing counter to disable shutdown. Counter after increment: 0MSI (s) (10:B4) [15:17:47:315]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2MSI (s) (10:B4) [15:17:47:316]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2MSI (s) (10:B4) [15:17:47:317]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1MSI (s) (10:B4) [15:17:47:318]: Destroying RemoteAPI object.MSI (s) (10:18) [15:17:47:318]: Custom Action Manager thread ending.MSI (c) (AC:B0) [15:17:47:333]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1MSI (c) (AC:B0) [15:17:47:334]: MainEngineThread is returning 1603
=== Verbose logging stopped: 21-12-2018 15:17:47 ===
What can I do?
This shows the DMPrimer installation failed with 1603, which is a generic MSI failure code. The DMPrimer is responsible for installing CAM, and enabling the communications with the DM, in order to xfer the agent installation package.
I would recommend running the removal tool from WinOffline on this computer:
Latest WinOffline -- 2018.10.23
From the GUI:
WinOffline Explorer --> Removal Tool --> Remove ITCM button.
From the command line:
Then retry the deployment from the start.
If that does not work, then please open a case, and upload the C:\dmmsi.log, so we can better understand the 1603 error. I'm thinking likely the removal tool cleaning of the system may resolve whatever is causing the 1603, hence it is simplest to try that first!