I find the pre-installed software packages extremely useful for deploying the latest product versions. Rolling out packages to clients is both quick and straightforward. Creating custom packages is also simple, as you can clone existing ones to use as a starting point. The option to run commands directly on client machines, whether through the command line or Powershell, is a feature that sets this solution apart from many other RMM tools. Deploying agents to devices is also very straightforward. The automated package deployment feature is truly a game changer. For example, with the recent wave of critical browser patches, we can automatically deploy updates to clients as soon as they are identified. Additionally, it's possible to stage these deployments to specific groups first for testing, if desired. Review collected by and hosted on G2.com.
Connect does provide the ability to remote connect to client desktops, but an additional agent needs to be installed on the client and a viewer installed on the admin's PC in order to use that feature. Most other RMMs that we have used has that capability built in. The Connect product has much of the same capabilities that their Deploy product has with one downside. If a package deployment fails, there is not ability in Connect to restart the deployment from the failed step. This requires going into the package and disable the initial steps that have already been completed and then run the package again. Not a show stopper, but coming from a D&I environment, it is definitely a function that admins would like to have. Review collected by and hosted on G2.com.
