Automatic Provisioning failures... Agent already installed
Can anyone help me understand why these are failing if the agent is already installed? Shouldn't it stop trying to deploy to these machines (we're getting this on 50+ systems in various offices of ours).
Provisioning Log |
||
[05/09/13 10:08:18 AM] Begin provisioning... [05/09/13 10:08:18 AM] Executing Windows platform provisioning. [05/09/13 10:08:18 AM] Probing tcp ports for accessibility. [05/09/13 10:08:18 AM] Port 139 [netbios-ssn] open [05/09/13 10:08:18 AM] Port 445 [microsoft-ds] open STEP 1: CONNECT TCP/SSH - SUCCESSFUL [05/09/13 10:08:46 AM] Executing remote communications: Initializing RPC Connecting to ADMIN$ Copying service file Disconnecting ADMIN$ Connecting to IPC$ STEP 2: AUTHENTICATION - SUCCESSFUL Opening pipe to service Sending commands Sending login credentials Begin agent_msi_provision.bat processing. Detected 64-bit platform. K1000 Agent is already installed. End agent_msi_provision.bat processing. Removing service (Exit code: 0) Connecting to ADMIN$ Deleting service file Disconnecting ADMIN$ STEP 3: PUSH SCRIPT\PROVISIONING - FAILED [05/09/13 10:08:46 AM] End of remote communications. [05/09/13 10:08:46 AM] End provisioning run. |
Answers (4)
Use the agent updates and do it that way
Comments:
-
Yeah, we've got that enabled already. - j.hough_FNP 11 years ago
The automatic provisioning just attempts to install on everything. It doesn't care if it tried and succeeded last week, it just keeps trying. So these 50+ are machines that it actually installed the agent on during a previous run (or maybe you did it manually), but it tries again anyway. It doesn't really hurt anything, and in my experience can basically be ignored. Does that answer your question?
Comments:
-
Sorta, yes... lol. We're just on our initial deployment of the agents and the kace appliance. Just trying to make sure that all the agents have been to deployed to all the machines we have and that these aren't failing for other reasons. - j.hough_FNP 11 years ago