79 results found

1. Progress bar on patch deployment + Summary of patching

   This idea is already published. It is marked as 'Completed', but there is still no progress bar, so I decided to create a new idea, because I don't know another way to respond to the status, so it will be recognized by Kace.

   I would like to see a progress bar on the client while patching for the current patching job.

   I think it would be enough for example if there are 10 patches to deploy, 6 are already finished, the progress bar would show 60% finished.

   Maybe it is also a good idea to see a short summary which patches were successful, which not.

   This idea is already published. It is marked as 'Completed', but there is still no progress bar, so I decided to create a new idea, because I don't know another way to respond to the status, so it will be recognized by Kace.

   I would like to see a progress bar on the client while patching for the current patching job.

   I think it would be enough for example if there are 10 patches to deploy, 6 are already finished, the progress bar would show 60% finished.

   Maybe it is also a good idea to see a short summary which… more

   564 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  14 comments  ·  Agent  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

2. Have agent update K1000 when IP changes

   I have a problem where employees with laptops cannot get software from the User Console Library because the IP address from their last inventory (up to 4 hours ago) does not match the IP the K1000 web interface is seeing.

   For example I have about 50 scripts in the library to automate the installation of printers in Boston, New York, LA, and Dallas. I have smart labels configured so that if you check in on the Boston, NY, LA, or Dallas subnets you get that site label. I then limit all the scripts for the printers in each site to the appropriate site label so employees will only see the printers they care about.

   My biggest problem is the laptops. If they are docked at their desk in Boston and they get inventoried so their IP address is 192.168.100.1 then they undock and go to the other side of the building and login to get a printer they cannot see the scripts because their IP address in the User Console Library sees them as 192.168.200.2.

   If I force and Inventory update on them and they logout and in they can now see the scripts for Boston, etc.

   This problem would go away if the agent could detect an IP configuration change and either run an inventory (runkbot 4 0) on its own or at least just send the updated IP address to the K1000 so they are always in sync.

   I have a problem where employees with laptops cannot get software from the User Console Library because the IP address from their last inventory (up to 4 hours ago) does not match the IP the K1000 web interface is seeing.

   For example I have about 50 scripts in the library to automate the installation of printers in Boston, New York, LA, and Dallas. I have smart labels configured so that if you check in on the Boston, NY, LA, or Dallas subnets you get that site label. I then limit all the scripts for the printers in each site to… more

   202 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   8 comments  ·  Agent  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   under review  ·  Ken Galvin responded

   Thank you for your very thorough desciption of the issue. We will consider this as a feature request in the future. We prioritize based on feedback like yours – so we encourage others to vote for this feature request.

3. Provide BIOS settings inventory

   It would be nice to have the ability to inventory (and enforce) BIOS settings right from the KBox Appliance. Dell provides the CCTK utility to manage these features on supported systems. Having this utility integrated into the agent would give the ability to centralize management of BIOS setttings, provide compliance reports on BIOS settings and push out BIOS profiles. This would be wonderful.

   93 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   1 comment  ·  Agent  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   under review  ·  Ken Galvin responded

   We are investigating using OMCI to support this functionality

4. Bypass UAC while running scripts

   This is a follow up ticket to continue tracking an add on thread to a ticket which is now completed:
   http://kace.uservoice.com/forums/82699-k1000/suggestions/1637531-uac-compatibility

   Bypass UAC while running scripts:
   Running scripts as System does not involve UAC. If running scripts as a User, UAC applies. That case is still under consideration for a future release.

   79 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   2 comments  ·  Agent  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   under review  ·  Ken Galvin responded

   You are encouraged to vote on this ticket that was split out for a previous (closed ticket) that contained two different suggestions.

5. Allow turning off software discovery on chosen machines

   There are situations when certain machine should have agent installed but software dscovery is causing problems when it comes to license compliance, like file servers. Ability to turn off software discovery or at least exclude drives/folders from it would be usefull.

   62 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   3 comments  ·  Agent  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   under review  ·  Ken Galvin responded

   We’re engouraging votes from those who feel strongly that this is a valuable feature

6. Allow access to agent share after SMB Signature Required is enabled in AD

   Once SMB Signature Required is enabled in Active Directory then the agent share is unable to be access. It would nice to be able to download the new agent without having to block smb signature and then have to enable smb signature again.

   51 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   12 comments  ·  Agent  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. There needs to be an actual Agent for vmWare Host Servers.

   Having go manually run scripts on over 50 host machines is cumbersome. It would be far less cumbersom to be ablel to push an agent to the vmWare Host Server and then never have to worry about inventories again.

   47 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   under review  ·  3 comments  ·  Agent  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

8. Manual agent check in from client

   I would love to be able to use a command switch to force a check-in from a client machine. Something like %INSTALLDIR%\AMPAgent.exe /checkin. This would be very handy for new machines trying to get updates and patches ASAP before being deployed to a new hire, for example.

   40 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   4 comments  ·  Agent  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   under review  ·  Ken Galvin responded

   Thank you for your input. We are investigating this and encourage others to vote for this feature/functionality if they think it would be useful

9. View Application & Windows Patch State on the Client

   It would be a great idea to show the enduser the current state of the Patching Process.

   The Enduser should be able to see which Application and which patch is currently beeing installed.

   I have found some other ideas about this already but they all have been closed as "completed" but there is nothing like this in the current Version of K1000 8.1.

   27 votes

   Vote Vote Vote

   Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   1 vote 2 votes 3 votes Remove votes

   You have left! (?) (thinking…)
   0 comments  ·  Agent  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

10. variable

    Ability to use environment variables with custom inventory rules

    27 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    under review  ·  4 comments  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

11. Agent Install arguments to provision into specific org

    It would be useful for complicated Org setup and unreliable filters (currently an issue with the LDAP/AD query in the public release) to be able to specify the destination Org during the install with an argument. This would allow for overriding the filters when needed, and offer much more control to ensure devices get to the intended destination.

    24 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

12. Create x64 agent so the correct version of PowerShell is run

    In order to run PowerShell correctly on x64 Windows OS I have to remember to use c:\windows\sysnative\windowspowershell\v1.0\powershell.exe. This should be transparent to me, and will probably fix a large number of issues through the userbase for people who are running PowerShell scripts on x64 and x32 machines. It'll work for the x32 machines, but not for the x64 machines. It can't be THAT hard...

    22 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    3 comments  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

13. Fix Amp.conf File So It Doesn't Reconfigure

    Our K1000 is not available when you are not connected to our network. So when laptops leave our network to do work at home the agent continues to try to check in. Over time, because the agent can't connect to the server, the amp.conf deletes out all the configuration data, and the machines stop checking in. We have over 200 machines that have this problem. We then have to track these all down and reinstall the agent. But since this continues to happen we are never able to really make much progress.

    15 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

14. Customization of Agent Alerts

    I'd like to be able to customize the colors and other aspects of Agent Alerts shown to users when Managed Software or updates are installed.

    Currently we have our logo on the Agent Alerts, but the orange gradient kinda clashes and doesn't look that good. Having some options to customize this from a branding perspective would be neat.

    •  

    14 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

15. KACE Agent Tray Icon popup when On-Demand Patches are ready to install

    How about adding a popup on the KACE Agent Tray Icon when On-Demand Patches are ready to install?

    14 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

16. Non-persistent VDI agent

    Please incorporate agent support for VDI environments with workstations and servers that auto-scale / provision and collapse on demand. Other apps utilize VDI agent flags that are installed on the cloned workstation(s) that enables those systems to detect and classify cloned workstations as being VDI stations. When the agents become unresponsive or are no longer detected, they're automatically removed from the inventory / licensing.

    While we could choose to ignore installing agents on VDI devices, it's still important to be able to assist users in a evolving VDI landscape, and using KACE as our primary control pane gives us our first look and insight into the workstations as we troubleshoot.

    The issue we're encountering is that even with token based installations, once the agents become stale they have to be manually deleted or wait for an MIA period to elapse before the agents are removed from inventory which has an impact on licensing.

    Two ideas come to mind

    1. Incorporate a VDI agent flag during install that ties all VDI agents to the root/master device record. While VDI agents are detected, they consume a license, but will automatically delete if they go MIA for specified period of time.

    2. Utilize the token system and expand the functionality of the MIA settings to support MIA profiles based on the token used to install the agent. This way we could build tokens specifically for VDI environments, and then set their MIA settings to delete (not archive) the agent records when they're no longer detected. Allow MIA to be expanded to support deleting device agents no longer detected based on hours and days.

    Please incorporate agent support for VDI environments with workstations and servers that auto-scale / provision and collapse on demand. Other apps utilize VDI agent flags that are installed on the cloned workstation(s) that enables those systems to detect and classify cloned workstations as being VDI stations. When the agents become unresponsive or are no longer detected, they're automatically removed from the inventory / licensing.

    While we could choose to ignore installing agents on VDI devices, it's still important to be able to assist users in a evolving VDI landscape, and using KACE as our primary control pane gives us our… more

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

17. Add Pre-Install and Post-Install Message to the Software Library Installs

    Add Custom Pre-Install and Post-Install Message options for Software Library Installs. This is present for Managed installs. Why not in the Software Library?

    13 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    under review  ·  1 comment  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

18. Include the minor build number as an OS inventory field

    Include the minor build number as an OS inventory field, so we can report based on the latest Cumulative Update that has been installed on a device

    •  

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    1 comment  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

19. Better Mac OS X documentation for Kace Agent

    I've found sadly very little documentation about using the Kace Agent on a Mac. I did find a list of all the runkbot commands for Windows and for a while presumed that this would be the same on a Mac. But I started to realize that this is not the case. Now, I've finally located support articles that show that runkbot 2 0 on a Mac runs inventory where the same command in windows is runkbot 4 0. But then what does 4 0 do on a Mac? And what about the rest of the commands such as 6 0? Please give us Mac admins more to go on when using your product. Thanks.

    I've found sadly very little documentation about using the Kace Agent on a Mac. I did find a list of all the runkbot commands for Windows and for a while presumed that this would be the same on a Mac. But I started to realize that this is not the case. Now, I've finally located support articles that show that runkbot 2 0 on a Mac runs inventory where the same command in windows is runkbot 4 0. But then what does 4 0 do on a Mac? And what about the rest of the commands such as 6 0?… more

    12 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    5 comments  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

20. configure Kace not to use the root of the C drive as a working area

    Is it possible to configure Kace not to use the root of the C drive as a working area? It keeps adding and removing cab files there when it’s working, which is a pain when you have Explorer configured to expand the directory tree. It keeps appearing and disappearing from the tree. The name of the cab file causes it to appear at the top of the entries under the C drive, causing the entire tree to flicker and shuffle. This is both distracting and causes directories I’m trying to click to move around underneath the mouse. The path to use is passed on the command line to cabarc.exe, which is a subprocess of kpatch.exe.

    Can the system be used to use something under (e.g.) “C:\ProgramData\Dell\KACE” or “C:\Windows\Temp” ?

    Is it possible to configure Kace not to use the root of the C drive as a working area? It keeps adding and removing cab files there when it’s working, which is a pain when you have Explorer configured to expand the directory tree. It keeps appearing and disappearing from the tree. The name of the cab file causes it to appear at the top of the entries under the C drive, causing the entire tree to flicker and shuffle. This is both distracting and causes directories I’m trying to click to move around underneath the mouse. The path to… more

    11 votes

    Vote Vote Vote

    Vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close

    1 vote 2 votes 3 votes Remove votes

    You have left! (?) (thinking…)
    0 comments  ·  Agent  ·  Delete…  ·  Admin →
    How important is this to you?

    Not at all You must login first! Important You must login first! Critical You must login first!

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    Close

    Close