MichAda
My feedback
-
64 votes
You are encouraged to vote on this ticket that was split out for a previous (closed ticket) that contained two different suggestions.
MichAda
supported this idea
·
-
49 votesMichAda
supported this idea
·
-
Label awareness: software is installed when placed into a label - uninstalls when removed from label
232 votesThis is a great idea. We will need to first blend the software and managed install functions into the software catalog in order to do this. This is something that will take a while to implement, but certainly has our interest.
MichAda
supported this idea
·
-
550 votesunder review · 13 comments · SMA (K1000) » Software Compliance · Flag idea as inappropriate… · Admin →MichAda
supported this idea
·
-
597 votes
Thank you for your input. Offering both 32 and 64 bit clients would double our Windows agent QA testing time and we are sensitive to the impact of extending test times as it impacts our ability to release full-featured updates at our desired pace. A surprisingly large amount of our customers still need 32bit support today. We are going to continue monitoring this closely to determine the best time to drop 32 bit support (of course older versions of the agent would still be available once we moved to 64 bit). In the meantime, it would be helpful to know specifically what difficulties a 32bit client is causing so we might consider work-arounds in parallel with the 64bit only decision.
MichAda
supported this idea
·
-
18 votesMichAda
commented
Because this is an automation appliance, it seems pretty clear that a simple password change should be modified on a single object that is referenced in 'X' locations. Manual updates to MULTIPLE locations over an account password change is not good and encourages poor security practices. Especially when you have Support Techs giving advice like "Use an account whose password does not ever change"....Ummm NO! I'll continue to manually change LDAP labels every 60 days until this obvious option added into the already existing 'Credentials Management'.
MichAda
supported this idea
·
-
27 votesMichAda
supported this idea
·
MichAda
commented
It would be nice if we could import AD groups to have them available as labels so we would not have to create each one manually. Especially since the appliance is already capable reading / pulling useful AD info in the appliance.
Similar post:
https://kace.uservoice.com/forums/82699-k1000/suggestions/1888433-import-user-groups-on-ldap-import -
10 votesMichAda
commented
It would be nice if we could import AD groups to have them available as labels so we would not have to create each one manually. Especially since the appliance is already capable reading / pulling useful AD info in the appliance.
Similar post:
https://kace.uservoice.com/forums/82699-k1000/suggestions/7243359-allow-for-the-import-of-active-directory-groups-asMichAda
supported this idea
·
-
272 votes
There are a couple of ways to approach this – I think the current thinking would be to add a “type” to each script and allow users to define them and then use the View By function. Thoughts?
MichAda
supported this idea
·
-
183 votes
The K1000 agentless inventory now supports most server class devices, including Windows, Linux, Debian, SUSE, RHEL, Ubuntu, Fedora, and FreeBSD. It would good to know if you think that a read-only agent is still necessary given the broader support agentless has.
MichAda
commented
We could really benefit from this on servers. No way agent will ever live on server due to potential misconfig. incorrect label, ect. Risk is way too high.
But to capture the other data would be super!
MichAda
supported this idea
·
-
36 votesMichAda
supported this idea
·
MichAda
commented
SUPER CONCUR...The ability to pick would be great! Anything is better than just duplicate. MAYBE even have the ability to pigeon hole ONLY the items that are at risk of duplication. Place them in some label, place, or state where the admin can go in and make the selection on at risk items. It would be much better to have to correct known problem systems than simply duplicate. Why would you ever opt to use the UID on of the client, the IP address...really? Or even the MAC address. If you replace a motherboard, the serial may change with some manufactures, but Dell lets you set that back to the service tag. PERFECT starting point. If you don't have a Dell, than you know to take additional steps to correct those rare instances. Integrating mac address, IP address, or anything other sort of non static data is shows weakness in design.
We have asset tags assigned to our machines and the name of the computer includes the last four characters of the asset tag. I would love to tell KACE to look at Serial number first, look at the machine name second, third check would see if this Serial and Name already had a UID. If so, It's the same system. If not, it goes into some kind of temporary association state and Admin gets alerted.MichAda
commented
No comments on this since 2013?
Either everyone just deals with system duplication, or there's a lot of censorship by the moderators.
Either way, glad to see this one out there!!!!
This would be soooo helpful and it should already be there just like with windows.