SMA (K1000)

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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. 120 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  Replication  ·  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.

  2. Show TO DO in Replication Shares

    On the K1000 on 5.5 the To Do row was removed which - when you have over 100 replication shares means we cannot see if we have any issues with the replication shares. This option was around in 5.4 please can you bring it back urgently!

    75 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    11 comments  ·  Replication  ·  Flag idea as inappropriate…  ·  Admin →
    under review  ·  Dean Wade responded

    We are looking into this. The reason it was eliminated was that it was trying to retrieve the information in real-time and the page never rendered where there many replication policies. Stay tuned – hoping to have an answer in the coming month as to where this falls in our priority list.

  3. Force replication to specific share regardless of schedule.

    Add an option to force replication to the selected replication share(s) ignoring the schedule. This would be useful for dependencies of scripts that need to be run asap but are not replicated yet.

    37 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Replication  ·  Flag idea as inappropriate…  ·  Admin →
  4. Decouple agent requirement from replication setup

    Right now in order to setup a replication share there needs to be a computer with an agent installed on it and that computer must remain on. It would be nice to replicate to an inexpensive NAS device that could be placed at remote facilities.

    30 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    3 comments  ·  Replication  ·  Flag idea as inappropriate…  ·  Admin →
  5. Traffic Shaping for Replication

    The replication between the appliance and the remote shares e.g. for patches uses for a while, the time to transfer the bytes configured in the bandwidth limitation, 100% of the WAN bandwidth. This causes in some errors when applications try to use the WAN to the same time. A good solution for this would be to use traffic shaping on the appliance to control the bandwidth to each remote share separately. Therefore, it is possible to use a constant bandwidth without interrupting other applications on the WAN Link.
    Solution for a Linuxsystem see attached File

    18 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Replication  ·  Flag idea as inappropriate…  ·  Admin →
  6. Replication Share Global

    Global Replication Share to be used by all machines from all ORG's, this will be usefull for Corporation with high transit of employs between the sites/Orgs. eg. Replication Share Global on headquarter or main brandoffices.

    15 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Replication  ·  Flag idea as inappropriate…  ·  Admin →
  7. Add ability to control what items are replicated. Everything isn't always needed on every repository

    We have several different types of repositories for software distribution, but there seems to be no way to control what distributed software packages are sent to what repositories. It seems to be an all or nothing. This is an issue with remotes sites with limited bandwidth (primary reason for repository)

    7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Replication  ·  Flag idea as inappropriate…  ·  Admin →
  8. replication

    Currently when you enable replication to remote sites, you have wait untill all data is synced. All this data can be huge in total size. 40GB+. We have slow links to these site and it's going to take forver for all the patches to replicate. Would be nice if you could copy the replication folder to a removable drive, drive it to the other location and copy it into a folder and have it sync.

    2 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    2 comments  ·  Replication  ·  Flag idea as inappropriate…  ·  Admin →
  9. Improve Replication Share Status

    First, please change the colors or the ICONs in the rep share. Replicating high/low is nearly the same color as Window Closed, and window open high/low. Come on. Please change these colors. Second, when you force inventory during inventory closed, it just snaps back to the same "Window Closed" icon. Force inventory should force the schedule to update the share. Because we have to change the schedule to force the replication to finish. Or at least add a force update option.

    1 vote
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    0 comments  ·  Replication  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

Feedback and Knowledge Base