KACE Agent Provisioning Failure- Network Related Failure
Hey Everybody!
So I seem to have an interesting issue with my KACE box and provisioning out the newest Agent, version 6.0.1079. I was able to grab all of my machines on the network except for two, and this is where the fun part starts. While trying to install via a managed provisioning run, the install fails. However, when I check on the targeted machines, I find AmpAgent.exe running in processes, Dell KACE Agent service started, and even Kacelookup and a few others. I looked through the Provisioning Log, and it lists that it was able to run the .bat file and install the Agent, but at Step 3 It ends the provisioning run and states it as 'Failed'. I have included the log at the bottom of the post for clarification. I have also enabled debugging and received a little more information on the issue. It seems that I receive an error after the Agent has been installed: error_on_pipe: NT_STATUS_PIPE_DISCONNECTED
Now the only difference that I can think of between these two machines and my others is that instead of updating Agents that were already in contact with the Kbox, these two laptops have nothing on them. I have tried reprovisioning right after, and I receive the usual 'Agent already installed, ending provisioning run'.
So, if you are feeling froggy, please take a look and see if you can tell what it is, and any help would be greatly appreciated!
V/r,
Jeff 'Spurpickle' B.
IT Padawan
"Names and IP Addresses have been changed to protect the innocent."
STEP 1: CONNECT TCP/SSH - SUCCESSFUL
[06/19/14 10:34:27 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
IN: pipe_open(\KBRemoteService, 7217006)
Sending commands
Commands: //192.168.168.185/client/agent_provisioning/windows_platform/agent_msi_provision.bat 192.168.168.185 client ampagent-6.0.1079-x86.msi helpdesk.abc_company.net
Sending login credentials
Login: DOMAIN\Administrator
[MSGCODE: 000] Begin agent_msi_provision.bat processing.
[MSGCODE: 064] Detected 64-bit platform.
[MSGCODE: 015] Executing MSI installer.
C:\Windows\TEMP>start /wait msiexec.exe /qn /l*v C:\Windows\TEMP\ampmsi.log /i \\192.168.168.185\client\agent_provisioning\windows_platform\ampagent-6.0.1079-x86.msi HOST=helpdesk.abc_company.net
C:\Windows\TEMP>echo off
MSI Info: [ERROR_SUCCESS] The action completed successfully.
[MSGCODE: 001] K1000 Agent is installed.
[MSGCODE: 091] AMP is connected.
[MSGCODE: 093] KUID value detected.
K1000 agent KUID: 4E8ACFF3-7338-4052-8E2F-E26661128851
[MSGCODE: 100] End agent_msi_provision.bat processing.
Removing service (Exit code: 0)
ERROR: on_pipe_error - NT_STATUS_PIPE_DISCONNECTED
OpenService - NT_STATUS_OK
StopService - NT_STATUS_OK
DeleteService - NT_STATUS_OK
CloseServiceHandle - NT_STATUS_OK
CloseSCMHandle - NT_STATUS_OK
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$
STEP 3: PUSH SCRIPT\PROVISIONING - FAILED
[06/19/14 10:34:27 AM] End of remote communications.
[06/19/14 10:34:27 AM] End provisioning run.
So I seem to have an interesting issue with my KACE box and provisioning out the newest Agent, version 6.0.1079. I was able to grab all of my machines on the network except for two, and this is where the fun part starts. While trying to install via a managed provisioning run, the install fails. However, when I check on the targeted machines, I find AmpAgent.exe running in processes, Dell KACE Agent service started, and even Kacelookup and a few others. I looked through the Provisioning Log, and it lists that it was able to run the .bat file and install the Agent, but at Step 3 It ends the provisioning run and states it as 'Failed'. I have included the log at the bottom of the post for clarification. I have also enabled debugging and received a little more information on the issue. It seems that I receive an error after the Agent has been installed: error_on_pipe: NT_STATUS_PIPE_DISCONNECTED
Now the only difference that I can think of between these two machines and my others is that instead of updating Agents that were already in contact with the Kbox, these two laptops have nothing on them. I have tried reprovisioning right after, and I receive the usual 'Agent already installed, ending provisioning run'.
So, if you are feeling froggy, please take a look and see if you can tell what it is, and any help would be greatly appreciated!
V/r,
Jeff 'Spurpickle' B.
IT Padawan
"Names and IP Addresses have been changed to protect the innocent."
STEP 1: CONNECT TCP/SSH - SUCCESSFUL
[06/19/14 10:34:27 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
IN: pipe_open(\KBRemoteService, 7217006)
Sending commands
Commands: //192.168.168.185/client/agent_provisioning/windows_platform/agent_msi_provision.bat 192.168.168.185 client ampagent-6.0.1079-x86.msi helpdesk.abc_company.net
Sending login credentials
Login: DOMAIN\Administrator
[MSGCODE: 000] Begin agent_msi_provision.bat processing.
[MSGCODE: 064] Detected 64-bit platform.
[MSGCODE: 015] Executing MSI installer.
C:\Windows\TEMP>start /wait msiexec.exe /qn /l*v C:\Windows\TEMP\ampmsi.log /i \\192.168.168.185\client\agent_provisioning\windows_platform\ampagent-6.0.1079-x86.msi HOST=helpdesk.abc_company.net
C:\Windows\TEMP>echo off
MSI Info: [ERROR_SUCCESS] The action completed successfully.
[MSGCODE: 001] K1000 Agent is installed.
[MSGCODE: 091] AMP is connected.
[MSGCODE: 093] KUID value detected.
K1000 agent KUID: 4E8ACFF3-7338-4052-8E2F-E26661128851
[MSGCODE: 100] End agent_msi_provision.bat processing.
Removing service (Exit code: 0)
ERROR: on_pipe_error - NT_STATUS_PIPE_DISCONNECTED
OpenService - NT_STATUS_OK
StopService - NT_STATUS_OK
DeleteService - NT_STATUS_OK
CloseServiceHandle - NT_STATUS_OK
CloseSCMHandle - NT_STATUS_OK
Connecting to ADMIN$
Deleting service file
Disconnecting ADMIN$
STEP 3: PUSH SCRIPT\PROVISIONING - FAILED
[06/19/14 10:34:27 AM] End of remote communications.
[06/19/14 10:34:27 AM] End provisioning run.
0 Comments
[ + ] Show comments
Answers (0)
Please log in to answer
Be the first to answer this question