Remote Deploy: configuration not applied when changing user
I was just testing remote deployment of configurations and rules, and I stumbled onto a bug, I think.
I have a new configuration, and a new rule that applied to a single company. In the client on my test desktop, I had already logged in as another user in another company. I switched users in the client, but the rule was never triggered (I've waited a whole day to make sure).
I know that a user changing company is a rare occurence, but I think this should work nonetheless.
We'll look into this and report back here. Thanks.
Sorry, that's on me.
I created a new configuration, but for Windows instead of MacOS/Linux. When I changed it to MacOS/Linux and opened the client again, the new configuration was pushed.
The old backup plan was still present and active. It's probably a good idea to keep it there, but something to keep in mind when managing the service.
Thanks for the update. I was just testing this myself.
Sign in or register to add a comment.
Add a Comment
Welcome to MSP360 Forum!
MSP360 Managed Products
Managed Backup - General
Managed Backup Windows
Managed Backup Mac
Managed Backup Linux
Managed Backup SQL Server
Managed Backup Exchange
Managed Backup Microsoft 365
Managed Backup G Workspace
Connect (Remote Desktop)
Backup for Linux
Backup SQL Server
Connect Free/Pro (Remote Desktop)
Remote Deploy: removing a Backup plan from a configuration doesn't remove it from the client
Remote Deploy: Configuration file format documentation
Remote Assistant/Remote Desktop 2.4 release notes?/Name Change
Backups are failing with "connection was forcibly closed by the remote host" error
Terms of Service
Useful Hints and Tips
Created with PlushForums
© 2022 MSP360 Forum