KACE


Recommended Quest Virtual Appliance specifications (K1000)

The K1000 Virtual Appliance is configured, by default, to utilize 2 vCPUs and 4 GB of memory (this is also the minimum system requirement for the K1000). However, this minimum specification is only designed for the average customer up to 1000 managed devices. For larger implementations, more resources are required.

This chart below lists the recommended vCPU, RAM and NIC specifications based on managed device count (i.e. client systems with a K1000 agent installed). This is only a general guideline, as the results can vary widely based on how the K1000 is configured. It’s possible to have less then 1000 managed devices, for example, and require more than 4 GB of memory. Details about the K1000’s performance are available in Settings > Logs, then click System Performance in the drop-down menu.

Managed Device CountRecommended VM ResourcesNetwork interface
0 - 10002 vCPU & 4 GB RAM1 Gigabit
1000 - 20004 vCPU & 8 GB RAM1 Gigabit
2000 - 40008 vCPU & 16 GB RAM1 Gigabit
4000 - 800016 vCPU & 32 GB RAM1 Gigabit
8000 - 1600024 vCPU & 64 GB RAM10 Gigabit

How to export & import images between KACE2000 <> Remote Site Appliance

This article describes the necessary steps to move System Images from the Remote Site Appliance to the KACE 2000 server. When the System Image is stored on the K2000 server it’s possible to create a bootable USB flash drive containing the image.

The image I wish to export is a captures K-image file currently stored on the RSA.

export_rsa_1

As you can see it’s not possible to create the Flash drive:

export_rsa_3

There is no option to create a flash drive, like this example below:

export_rsa_2

Alright, let’s start exporting the image. First step browse to the IP address of the RSA. Use the SAMBA account to browse the shares :

export_rsa_4

In this example the RSA uses the IP address 10.70.28.2. Notice the restore folder. The restore is empty before the export:

export_rsa_5

No files and folders currently present in the restore folder, check 🙂

Now go to settings/Package Management/Export SDA Packages :

export_rsa_6

Select the specific image you wish to export and choose “Export Selected”:

export_rsa_7

Notice that KACE starts exporting the file:

export_rsa_8

After some time the export job is completed. Notice the green version mark (you currently have the latest version exported)

export_rsa_9

Notice the exported image in the restore folder :

export_rsa_10

Copy both files to the restore folder of the KACE 2000 folder. Now choose Import SDA Packages on the K2000 server (web interface):

export_rsa_11

Now select the specific image and choose “Import Selected”

export_rsa_12

After the import job succesfully ends you now have the specific image on your K2000 server. Notice the create flash drive option:

export_rsa_13

 


Troubleshooting KACE 1000 client issues

I recently ran into some issues with installing the KACE 1000 client. KACE 1000 is the KACE Systems Management Appliance from Quest software.

In this example I want to push the agent to a specific client and that fails.

Check the logging

First step is to check the logging. Go to settings, Provisioning, Provisioning results. There you find the logging of the deployment tasks.

k1000_provisionerror

When you want more information you can easily click the specific task and see more details :

k1000_provisioninglog

Try installing the agent manually

You can save youreself a lot of time troubleshooting the issue when you try to install the agent manually. This way you can quickly troubleshoot the problem and often (when you have multiple clients with problems) the solution you’re going to find is also the answer for your other clients.

Go to the machine you want to install the client on. Open File Explorer and browse to the following directory:

kace1000_clientlocation.png

In my example I want to install the client on a Windows device. (There are also Linux and Mac clients)

Use the agent_msi_provision script to manually install the K1000 client. The script automatically tries to detect the K1000 server. Sometimes (due to DNS problems for example) it fails to determine the K1000 server. You can use the command line option %1 for specifying the K1000 server. So use the following command agent_msi_provision 192.168.1.41 In my example the IP address of the K1000 in the demo environment has the .41 IP Address

Wait a minute and check in the Devices windows of the K1000 for the specific client.

Check network connectivity

When that doesn’t work (the first step often doesn’t :-)) check the network connectivity. Can you ping the client <> K1000? Are the right firewall rules in place? You can decide to temporary disable the firewall (and after adding it to K1000 use the K1000 options to enable the firewall again). I don’t encourage disabling firewalls, so use this tip only for troubleshooting.

net stop wuauserv
sc config wuauserv start=disabled (to keep it disabled after a reboot)

Turn on Network discovery and turn on file and printer sharing.

k1000_networkdetection

Check sharing and security settings

The installer uses the default ADMIN$ share to connect to the client to install the software. Go to the client and browse to the \\clientname\ADMIN$ share. Can you see the files using the account you specified in the K1000 provisioning task? No? Check if the shares are available.

k1000_adminshares

User account control (UAC) must be configured in one of two ways: Turn UAC off or set user account control: run all administrators in admin approval mode to enabled.

Ofcourse the specified user in the provisioning job has to exist and has local administrator rights.

Install the client using winrm method

I found installing using the winrm service to be a quick fix for me. You can easily enable that on the provisioning task :

k1000_enablewinrm

For this to work, the winrm service has to be enabled and running :

k1000_winrmservice

Wrap up

So in a nutshell :

  1. Check the logging
  2. Try troubleshooting installing the K1000 using manually install
  3. Appropiate account? (UAC disabled?)
  4. Check network connectivity (DNS/Firewall/same domain?)
  5. Fall back to WinRm method