Success with the primary admin account, although upon creating new admin accounts and attempting to provision new machines I am met with the result below.  Any input on why new admin accounts wouldn't be able to provision new agent installs?

  [09/10/14 04:40:29 PM] Executing Windows platform provisioning.

  [09/10/14 04:40:29 PM] Probing tcp ports for accessibility.

  [09/10/14 04:40:29 PM] Port 139 [netbios-ssn] open

  [09/10/14 04:40:29 PM] Port 445 [microsoft-ds] open


  STEP 1: CONNECT TCP/SSH - SUCCESSFUL


  [09/10/14 04:42:39 PM] 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.

      Executing MSI installer.

      

      C:\Windows\TEMP>start /wait msiexec.exe /qn /l*v C:\Windows\TEMP\ampmsi.log /i \\kbox16\client\agent_provisioning\windows_platform\ampagent-6.0.1079-x86.msi HOST=kbox16

      ......

      C:\Windows\TEMP>echo off

      MSI Info: [ERROR_INSTALL_FAILURE] A fatal error occurred during installation.

      Access is denied.

      K1000 Agent is not installed.

      AMP is not connected.

      ERROR: The system was unable to find the specified registry key or value.

      KUID value not written by MSI installer.

      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


  [09/10/14 04:42:39 PM] End of remote communications.

  [09/10/14 04:42:39 PM] End provisioning run.
5 Comments   [ + ] Show Comments

Comments

  • Bump
  • Have you verified that the new account is an admin on the target machine and can also access the kace share?
  • Thanks for the feedback. I made that adjustment on the target machine and it was successful. Ran it on a separate machine to check for consistency without making myself admin locally and it still provisioned. It would appear KACE has a mind of it's own at times.
  • Are you using a local admin account on the machine to do this? If so, is it possible to create a provisioning schedule with a range of IP's, and instruct it to use local admin?

    I don't see how as you have to specify the domain, and if you fill in the domain and type admin for the user name it will use domain admin instead of local admin. If I want to do it local do I need to make a single provisioning schedule for each machine?
  • I just tested this. If you leave the domain field populated it fails. If you delete the domain field, and are lucky enough to have an environment where all of your machines that need an agent have the same local admin name and password like me, you can create a provisioning schedule for a range of IP's. Just use administrator for the username, the local administrator password for password, and leave the domain field blank.

    I'm able to uninstall/reinstall agents at will doing this, with UAC enabled. The only thing wrong is the status of the machines I do this with in KACE shows as "Unable to reach this agent managed-device". I assume this is because I left the domain field blank, but I'm not sure. I don't know if this is a solution or not yet.
Please log in to comment

There are no answers at this time

Answers

Answer this question or Comment on this question for clarity