Pushing the Agent to new inventory (error message)
I'm having trouble adding new Dell Latitude E6320s to my inventory. I've added my machines to DHCP and DNS, but when I try to provision the agent I'm getting an error. It occurs in step 3. It connects to the laptop and authenticates, then it says that the push script\provisioning failed, end of remote communications. This seems like it might be a fairly common occurence. Wish there was more information. I'm sure someone has run in to this before. I'd appreciate any assistance on this while I go back and review the tutorial videos. Thanks!
Answers (5)
Have you enabled debug on the provision?
can you vailidate that the E6320 can get to the client folder on your kbox by trying to UNC into it?
have you tried to add a entry in the host file for the KBOX?
Did you turn off UAC on the Win7 box since it is out of the box?
Comments:
-
I did turn off the UAC. I have not tried to access the Hosts file on the KBOX. I cannot UNC into the KBOX. I did enable the debug provision. Everything looks good until it gets to "This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows installer." Then there is an exit code 1620ERROR.
I'll see what I can find out about that. Thanks again. - AndrewQ 12 years ago
Is your firewall enabled?
Comments:
-
The firewall is disabled. I've also uninstalled McAfee. I read that there may be a conflict there. It's a Windows 7 machine right out of the box. - AndrewQ 12 years ago
-
What version of kbox are you running? - SMal.tmcc 12 years ago
-
I'm running 5.3.53177. - AndrewQ 12 years ago
-
It was suggested that maybe the Agent itself had become corrupted. I got a new copy from KACE Support but I'm still getting the same error. I've attached a copy of the error log to this thread. Also, I was able to manually add the Agent and it is checking with the KBox. That makes me think the laptop is Ok. I then went and added a latitude D630 and a Precision T7400 the same way. I've got over 200 more to go so I'd like to get this provisioning figured out. Thanks for the help. - AndrewQ 12 years ago
I don't have a real answer, but I have had this happen before. My solution has been to push the agent out again. This has fixed it almost every time for me.
i had exactly the same problem.. my issue was a registry key that only allowed the workstation to connect to windows shares.. Since the KACE appliance is not native windows it runs a samba share.
So whenever the workstation tried to connect to the samba share, to run the agent installation, it would come back and say it was not authorized. You would not see this in the agent deployment because it is a silent install. But if you tried to go to the samba share directly from the workstation (\\kbox\client) you would get the access denied message.
I changed this registry key around Server Message Blocking..
The workstation needs a rebook for the change to take effect.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\lanmanworkstation\parameters
requiresecuritysignature = 0x0 (disabled)
When this key is enabled (0x1) the workstation can only connect to windows shares.
Now everything works just fine.
I hope this helps somebody as it was a real frustrating issue to resolve.
Comments:
-
Thanks Mark. I tried that and I did get a little further this time. These are the results that I got.
Provisioning Log
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
[10/12/12 09:29:50 AM] Begin provisioning...
[10/12/12 09:29:50 AM] Executing Windows platform provisioning.
[10/12/12 09:29:50 AM] Probing tcp ports for accessibility.
[10/12/12 09:29:50 AM] Port 139 [netbios-ssn] open
[10/12/12 09:29:50 AM] Port 445 [microsoft-ds] open
STEP 1: CONNECT TCP/SSH - SUCCESSFUL
[10/12/12 09:30:28 AM] Executing remote communications:
Initializing RPC
Connecting to ADMIN$
Copying service file
Disconnecting ADMIN$
Connecting to IPC$
STEP 2: AUTHENTICATION - SUCCESSFUL
Creating service
Opening pipe to service
IN: pipe_open(\pipe\KBRemoteService, 2)
Sending commands
Commands: msiexec /qn /i \\searde-k1100\client\agent_provisioning\windows_platform\ampagent-5.3.53177-x86.msi HOST=searde-k1100
Sending login credentials
Login: EGLIN.HPC.MIL\searde_admin
This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package.
exit code: 1620ERROR: smb_raw_read_recv - NT_STATUS_PIPE_DISCONNECTED
ERROR: on_pipe_error - NT_STATUS_PIPE_DISCONNECTED
Removing service
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 - AndrewQ 12 years ago -
So close. I'm almost there. - AndrewQ 12 years ago
-
The issue might have something to do with your DNS server. Try using the KBOX IP address in the 'K1000 Server Name' field and see if you are able to provision or continue to have the same results. Are you able to access the samba share by both KBOX name and KBOX IP from any of these clients? ( \\KBOX\client ) or does it give you an error? - brian_klocek 12 years ago
