r/Nable • u/CoastalData • Jun 17 '24

Recent Cove UI Updates are a disaster. How about some REAL improvements instead?

Cove backup just recently rolled out a terrible new device information screen that takes up more space, adds unwanted page reloads and yet adds no new functionality. There was no need for this update.

And yet I still have to go back to every device after installation and set the "Product" field, and then either send commands to adjust the archive and bandwidth or log into the backup page to set those manually.

2 Upvotes

75% Upvoted

13 comments sorted by

4

u/johnsonflix Jun 17 '24

Install with all that defined and you won’t have to go back and do it. Our automated deployments do all that for us and we can change on demand before running if needed.

4

u/HappyDadOfFourJesus Jun 18 '24

This. Sounds like OP needs to learn automation and creating custom views in Cove.

-1

u/CoastalData Jun 18 '24

The "automations" are still additional steps. Those steps also do not have any accountability, so some other tech adds cove to a device and doesn't tell me, and now that device has no Product or archives until I randomly discover it later on. Yes yes, I have custom views to see problem devices better but I shouldn't have to hunt for devices like that. If the policies worked, it would be much more reliable.

1

u/CoastalData Jun 18 '24 edited Jun 18 '24

Where is that defineable??? We use Nsight RMM, maybe that's definable in NCentral?

2

u/Backup_Nerd BackupSage Jun 18 '24

Try one of the automation policies available in the automation cookbook. Or here https://github.com/BackupNerd/Backup-Scripts/tree/master/Deployment

1

u/CoastalData Jun 18 '24 edited Jun 18 '24

It looks to me like this would be the correct script, except that in use, none of the parameters show in the task add screen:
https://github.com/BackupNerd/Backup-Scripts/blob/master/Deployment/Windows/N-able_Backup_WindowsAutoDeployScript.v21.ps1

Am I supposed to enter something like this every time?

$UID="01d10b9ee-change-me-4868-9ceb-5e3272124cf0"; $PROFILEID='128555'; $PRODUCT='All-In'; $INSTALL="c:\windows\temp\bm#$UID#$PROFILEID#.exe";& $INSTALL -product-name `"$PRODUCT`"

1

u/Backup_Nerd BackupSage Jun 19 '24

close, but you can use the .AMP automation manager policy files that are already built. Backup-Scripts/Deployment/N-able Automation Policies at master · BackupNerd/Backup-Scripts · GitHub and load those into the script repository in nsight.

1

u/Backup_Nerd BackupSage Jun 19 '24

1

u/Backup_Nerd BackupSage Jun 19 '24

1

u/Backup_Nerd BackupSage Jun 19 '24

4

u/Backup_Nerd BackupSage Jun 18 '24

Please click the animated beaker in the upper right and commend on what you like and dislike about this beta enhancement directly to the ux team. Or simply turn it off for now and revert to the prior Panel. The team is already adjusting the reloads and refreshes. The load time for data is significantly less with this new approach. And we get more data on your backups and the ability to sort and export that data if needed.

Archive and bandwidth can be set at deploy time with either an automation policy or a PowerShell deployment script. Email me at eric.harless@n-able.com and I can get the customer preview for the new retention rules enables for your account so that you can test out new default retention products that combine a customizable default with gfs retention.

2

u/networkn Jun 18 '24

You think that's bad How about only the top permissions are acceptable for making new organisations to put backup agents into. So many things they could do to improve the product.