Ben Schwartz

My feedback

  1. 821 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    17 comments  ·  SMA (K1000) » Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Schwartz supported this idea  · 
  2. 16 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SMA (K1000) » Managed Install  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Schwartz commented  · 

    @Troy V. Barkmeier - This is exactly what I'm talking about, it's terrible and is now becoming worse because of the way Windows 10 sub-releases is being inventoried in Kace. For example we had Windows 10 Pro X64 (10.0.14393) for the longest time until recently when it upped a version to (10.0.15063). I have ~30 managed installs for WIndows so now I have to spend a ton of tedious work on selecting this new version of Win 10. If this is going to continue I won't use Kace for software deployment anymore. I'm a very unsatisfied customer at this point as this has been a huge problem for me in the past and the last 3 years. Please, please add this as a next feature request.

    Ben Schwartz commented  · 

    I opened a ticket with Kace support for exactly this problem and they pointed me to UserVoice, I found this post. I totally agree that this needs to be done, now... I don't use Kace as much as Troy from what it sounds, but I have ~30 managed installs for Mac, with every new Mac OS X build number I need to go through every one of these software inventory items to select... 10.11.4. It should have a blanket choice for "Macintosh" like we do in scripting and patching.

    Ben Schwartz supported this idea  · 
  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.

    Ben Schwartz supported this idea  · 
    Ben Schwartz commented  · 

    For powershell scripts that check and edit the 64-bit registry you can add the following to the beginning of your PS1. For more info and background: http://www.itninja.com/question/kace-not-detecting-registry-values#answer-97733

    if ($PSHOME -like "*syswow64*") {
    Write-Output "Relaunching"
    & (Join-Path ($PSHOME -replace "syswow64", "sysnative") powershell.exe) `
    -File $Script:MyInvocation.MyCommand.Path `
    @args
    Exit
    }

  4. 5 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  SMA (K1000) » Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Schwartz commented  · 

    This feature request has more hits and should be addressed rather than this one.
    https://kace.uservoice.com/users/67367163

  5. 1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SMA (K1000) » Agent  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Schwartz shared this idea  · 
  6. 30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  SMA (K1000) » Appliance  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Schwartz commented  · 

    This already works. I can create a user label based on security group. I can create device labels based on computer OU. Device LDAP label test produces zero results, but does apply only on next computer inventory, try it out:

    Device LDAP label:
    Base DN: OU=Stage,OU=Workstations,OU=Company,DC=company,DC=com
    Search filter: (CN=KBOX_COMPUTER_NAME)

    User LDAP label:
    Removed mine but basically the same you just need to use a different variable.
    Page 14 - https://docs.google.com/file/d/0BxH6X8H1Q3CRYmZpNmZOZUFaOVU/edit?pli=1

  7. 660 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    19 comments  ·  SMA (K1000) » Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Schwartz supported this idea  · 
  8. 4 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  SMA (K1000) » Patch Management  ·  Flag idea as inappropriate…  ·  Admin →
    Ben Schwartz shared this idea  · 

Feedback and Knowledge Base