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!
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.
Randir Ramkissoon commented
Replication of all application patches to remote locations when only a few are needed is a major waste of bandwidth.
Alois Baumgartner commented
Yes please bring it back! We have around 100 replication shares and its a lot of work to check each share!
Donna Botelhol commented
For folks w/a bunch of remote locations, the 'To Do' column is a feature that is routinely used for monitoring replication. The 'To Do' column gives you a birds-eye view of all shares & where you can begin to start deploying patches. Ever deploy patches when a share is replicating? Doesn't work well. Need to monitor the shares, wait for replication to finish, then push the patches. It's annoying to have to check each share individually when previously you could get that information at a glance w/the 'To Do' column.
Removing the To Do row is tantamount to Microsoft removing the famous "Start" from Windows. Please bring it back.
Vinnie Mescall commented
This feature absolutely needs to be brought back. Requiring administrators to dig into each share in order to verify/check remaining replication is absolute nonsense and borders on being a deal break when using this appliance.
Kley Abel commented
I concur. This was nice to see in a summary how much, if any were waiting to be replicated.... Please bring back! Waste of my valuable time having to drill into each patch schedule...
Chyanne Krause commented
I agree I used this feature every day and liked not having to drill into each of the replication shares to see what still needed to be replicated.
Ch. Böhnisch commented
yes, its important
Dave Guyton commented
Your not alone. We agree. Please bring it back!
sangeeta ganguly commented
This is extremely important in order to start detecting and deploying patches to remote locations. I solely depend on the status of TO DO column to schedule my remote patching jobs.
Please bring it back immediately.
Wonder what made you decide to remove one most crucial piece of information column altogether in the new version?
Nick Hidalgo commented
Agreed, this was very helpful, please bring it back.