SMA (K1000)

Please tell us how you’d like to see the Systems Management Appliance product improved!

How can we improve the SMA (K1000)?

You've used all your votes and won't be able to post a new idea, but you can still search and comment on existing ideas.

There are two ways to get more votes:

  • When an admin closes an idea you've voted on, you'll get your votes back from that idea.
  • You can remove your votes from an open idea you support.
  • To see ideas you have already voted on, select the "My feedback" filter and select "My open ideas".
(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow ability to enable authentication for client shares

    Now that Microsoft is no longer allowing guest access to SMB shares by default, beginning with Windows 10 v1709 (Fall Creators Update), the appliance client share(s) are no longer of any use without changing the default behavior in Windows to be less secure.

    See https://support.microsoft.com/en-us/help/4046019/guest-access-smb2-disabled-by-default-in-windows-10-server-2016

    The appliance should allow the admin to enable authentication to the \\k1000\client share(s) so that they are usable without compromising Windows security.

    Ideally, existing accounts created or imported into the appliance (In Organizations, on Org enabled appliances) would be able to use this share, but a local account with a password we set would be…

    62 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add TELNET testing to list of DIagnostic Tools

    WHen provisioning to a client, most of the time my clients get SUCCESS on 90 percent of the deployment but then fail with one error or another. Your support site says “Test connectivity to ports 139 and 445 on TARGETPC from the K1000 Appliance. On Windows devices, ports 139 and 445, File and Print Sharing, and Administrator credentials are required only during Agent installation. “
    SYSTEM>SETTINGS>SUPPORT>Diagnostic Utilities> TEST:
    But there is no TELNET option available to use to TEST!!! TELNET needs to be added for PHYSICAL APPLIANCES as the instructions are written for KACE VM’s I believe.

    From: support@software.dell.com […

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  3. Change the way how i can make manual Provisioning by Hostname

    We have 100 Users an also 100 PC, and then any of this user has 1 or 2 VMs on his PC. I would make the Provisioning by the Hostname with a Placeholder. On example
    Physical PC beginns with: CLVDxxxxxxxx
    Virtual PCs beginns with: VCLVDxxxxxx
    I would now enroll the agent only to the Physical PCs. But in the Target Hostnames its not possible to write CLVD* or something like that.

    12 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Ken Galvin responded

    Thank you for your suggestion. We encourage others to vote as we use this input for adding and prioritizing features for future release plans.

  4. Need an option to push the new agent by login into System page (example : Ping, RDP)

    It will be more helpful If the team create a new option to provision the agent for single device by opening the device page.

    I have attached the sample screenshot for the same...

    6 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  5. Ability to add MSIEXEC switches during agent provisioning

    Hello.

    For differents reasons, we install the K1000 agent with some switches, namely "NOHOOKS=1" or "/qb! /i". But when we use agent provisioning feature (either "Provisioning Schedule Detail" page or "Update Agent Settings" page), we're unable to add these switches, so the installer don't have the behavior we expect.
    It could be interesting to have an "Additionnal Parameters" field like in "Managed Installation Detail" page.

    Regards.

    5 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Ken Galvin responded

    Thank you for your suggestion. This has been added to the feature request list. We encourage others to vote as we use this input for prioritizing our release plans.

  6. More accurate agent provisioning errors

    It would be great if the error messages were more accurate so if I run a agent installation against a subnet the failed error message said "agent already installed" or "no agent found" and that sort of thing. This will allow me to focus on actual problem devices.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  7. External Provisioning

    The ability to provision a machine, for example, by going "Kace_Server"/provision instead of having to create a simple provisioning schedule. You could have the page you landed on ask you for your kace credentials and then only allow specific users in Kace to initiate this process.

    This would be much faster for getting new machines or recently rebuilt machines provisioned instead of waiting for Kace to scan your entire DHCP range for new machines or look-up each machines IP so that you could setup a simple provisioning schedule.

    4 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  8. option to deploy all software which is installed on another machine

    an option to select a list of software which is installed on another machine and to deploy this to a new machine

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  9. Chrome Device Discovery Filtering

    Google Admin Portal does not allow devices to be deleted after it has been associated with an account. The only option is to "Deprovision" a device, which un-assigns a license from that device, but still remain in the account.

    Currently, when the SMA performs a discovery, there is not a way to filter these "deprovisioned" devices that are discovered. All devices are discovered regardless of status. (Google API provides a method of filtering the devices being discovered.) Devices now have to be discovered and manually added. This is a VERY tedious task, as working for a school district, we will…

    3 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  10. Free Professional Services to script alternate file shares until SMB vulnerability is addressed

    The latest version of the SMA fails to address SMB vulnerabilities by continuing to utilize SMB v1 to share out the client folder and Agent installers it contains. Quest KB articles suggest workarounds of re-enabling this knowingly vulnerable protocol to avoid losing access to the file shares; shares that are necessary to provision agents to new Windows 10 1709 PCs (and other wise OSs which have disabled SMB).

    I would suggest that, rather than asking clients to either 1. Create and troubleshoot their own custom scripts to work around the vulnerabilities you failed to address in the latest update or…

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  11. 1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  12. Ability to assign preferred networks for agent installation

    This could be done by a simple weight rating for preferred subnets. The idea is to give a way to tell the KACE to try to use LAN connection before wireless connections.

    1 vote
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    under review  ·  0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  13. Exclude ip addresses or devices via label or smart label in KACE

    Our servers are managed by WSUS and need KACE to not install an agent or patch the servers.
    We need a way to exclude the servers from KACE.
    Exclude ip addresses or devices via label or smart label in KACE

    0 votes
    Vote
    Sign in
    (thinking…)
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Provisioning  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base