While attempting to deploy the KACE Agent to a Windows 2008 R2 server, the installation failed. I tried it twice and got two different errors before fixing the issue.
Here is the first log:
| Provisioning Log |
||
| [04/26/13 11:03:06 AM] Begin provisioning... [04/26/13 11:03:06 AM] Executing Windows platform provisioning. [04/26/13 11:03:06 AM] Probing tcp ports for accessibility. [04/26/13 11:03:08 AM] Port 139 [netbios-ssn] not accessible [04/26/13 11:03:08 AM] Port 445 [microsoft-ds] open STEP 1: CONNECT TCP/SSH - FAILED [04/26/13 11:03:08 AM] End provisioning run. |
||
And the second one:
| Provisioning Log |
||
| [04/26/13 11:03:06 AM] Begin provisioning... [04/26/13 11:03:06 AM] Executing Windows platform provisioning. [04/26/13 11:03:06 AM] Probing tcp ports for accessibility. [04/26/13 11:03:06 AM] Port 139 [netbios-ssn] open [04/26/13 11:03:06 AM] Port 445 [microsoft-ds] open STEP 1: CONNECT TCP/SSH - SUCCESSFUL [04/26/13 11:03:15 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 Sending commands Sending login credentials This installation package could not be opened. Contact the application vendor to verify that this is a valid Windows Installer package. exit code: 1620Removing service Connecting to ADMIN$ Deleting service file Disconnecting ADMIN$ STEP 3: PUSH SCRIPT\PROVISIONING - FAILED End of remote communications. [04/26/13 11:03:15 AM] End provisioning run. |
||
A search on IT Ninja led me to this post: http://www.itninja.com/question/how-do-i-get-the-k1000-agent-to-install
Sometimes an error like the second is a UAC issue, but this was not the case in my scenario. One answer was to replace the Kbox FQDN with its IP. This worked for me. I don't totally understand what the problem was, but we've had some DNS issues on our network.
(P.S. Ignore those dates in the provisioning log. It happened today, trust me! :D)
It could also be a failure to logon and access the SAMBA share. - jdornan 10 years ago