Brandon Padgett (Gerane)

My feedback

  1. 165 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SMA (K1000) » Backups  ·  Flag idea as inappropriate…  ·  Admin →
    Brandon Padgett (Gerane) supported this idea  · 
  2. 57 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    7 comments  ·  SMA (K1000) » UX  ·  Flag idea as inappropriate…  ·  Admin →

    We are investigating some changes to the UI that will ensure a more consistent experience across the K1 for each of these areas.

    Considering there are three different areas listed in this idea, we may look to implement these separately to focus on the most urgent needs. Based on the comments, the biggest issue here appears to be related to the OS selection for software inventory not allowing the ability to select all OS versions for Mac or Windows.

    These are all valid ideas that would improve consistency so these have all been added to the backlog but they are not currently planned for our next release. Please continue to vote if you’d like to see this prioritized for a future release.

    Brandon Padgett (Gerane) supported this idea  · 
    Brandon Padgett (Gerane) commented  · 

    It has been 3 years, any updates on this? I have a very, large number of Custom Inventory Objects among other things. It is a major time investment to go and correct these constantly.

  3. 630 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    45 comments  ·  SMA (K1000) » Agent  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Ken Galvin responded

    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.

    Brandon Padgett (Gerane) commented  · 

    I cannot express how displeased I am that this was created 4 years ago and they still have not done anything about this.

    If I had known about the 64 bit limitations when purchasing Kace, I would have steered my company to a different product. The bigger issue is the lack of understanding of why the 64 Bit client is needed. Kace is stuck in the past and is incapable of even understanding the real issue here. When I am asked if I recommend Kace, I have to say no. This is such a glaring issue and one that many might not even realize is impacting them.

    To further point out the issue here, if you use the built in Configuration Policy/Security Policy Utilities inside of Kace they are broken on 64 Bit machines. They create Policies that will not work on a 64 Bit Host due to the redirection. The Policies are applied to the 32 bit location and do not actually work.

    Honestly, the headaches caused by 32/64 issues have me fed up with this product. It has cost me months of my time and I am still neck deep in solving all of the issues it has caused. I have to go through every single Managed Install, Script, Policy, Custom Inventory Object, Label... pretty much everything inside of Kace and try to weed out every single place there might have been an issue. To top this off, it doubles your work load. You have to do everything twice. Once for 32 bit and again for 64 bit. This, for an environment the size of mine, has caused very, very noticeable impact on my Server's performance.

    To make matters worse, there are some items in Kace in my environment that having multiple instances for different architectures simply is not viable. If someone has developed a solid method to handle this please feel free to contact me.

    Thomas Turner mentioned, "True, it isn't a bad thing to know how that all works. In fact, I assume many of us already conjured up our kludgery, even while we were voting up this issue and complaining in the comments. It isn't that we *can't* get things to work, but just that the worst enemy of IT pros is wasted time."

    The problem with this, is that it is incredibly easy to overlook something and have something critical missed. I mean, just look at the Configuration Policies and Security Policy utilities inside of Kace. These are incredibly important settings and even they missed this and have deployed it broken to their customers. To me this points out the lack of understanding of the issue. Many of these types of issues are not going to be pointed out or alerted to you. The settings get applied, they just do not actually do anything. If you do not have something going back behind you and checking, you may not ever know. Heh, just don't use Kace to do the checking, since it will find the wrong path and return true.

    Brandon Padgett (Gerane) supported this idea  · 

Feedback and Knowledge Base