Jump to content
DeployCentral
tcarver

RMM Agent Install - Managing version changes

Recommended Posts

Hello - I use Kaseya as my RMM. The version of the agent changes from time to time, and I currently have a task to install the agent during deployment using the option, "Upon first boot as system". I have the agent install from the local drive, but I have to copy new agent versions to the reference machine, then recreate deployment packages. What I'd like to do is use the task as I have it now, but install the agent using a vbscript with the install file on the network. I could change out the file on the server without having to worry about my reference machine, images, deployment packages, etc.

I'm still a little confused about what needs to update when I modify my reference machine. I'm fairly certain that I should update, refresh, recreate (not sure what to call it here) when my reference machines change. Do I then need recreate my deployment packages too? Documentation isn't the best.

This confusion is why I'm looking to come up with a more static solution for 3rd party software that may change frequently. I don't want to have to recreate a bunch of stuff in SD every time something changes.

Thanks for considering responding, and I hope my question makes sense? I searched here in the forum and didn't see anything that fit my particular question. I may be the only one confused about such things.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×