- HOW TO INSTALL KASEYA AGENT IN THE HE ENDPOINTS HOW TO
- HOW TO INSTALL KASEYA AGENT IN THE HE ENDPOINTS UPDATE
- HOW TO INSTALL KASEYA AGENT IN THE HE ENDPOINTS FULL
- HOW TO INSTALL KASEYA AGENT IN THE HE ENDPOINTS CODE
Also if we would have moved last year we would have saved 140K in Kaseya licenses alone (we acquired another MSP about 2k agents) so also don't forget about price. Due to this, I was dispositioned to not even give other products a chance. I was very closed minded figured we would never move to a Different RMM due to how much we built in Kaseya and how much time it would take to forklift it to another platform. We literally were trying to give them 40K for traverse and couldn't get a quote. While at connect last year I had to basically jump Bruno S and ask for a new Sales rep due to a lack of communication from our current rep. It's safe to say internally they are struggling to stay organized. This is distracting them from working on the VSA which is in need of some love.
The last year has been weird for Kaseya, they are acquiring all these tech companies trying to build Kaseya ONE. We get native STDout and STDerr which makes it a treat troubleshooting when errors arise.
Don't need to write file, Don't need to mess with execute command and worrying about 32 or 64-bit shells.
HOW TO INSTALL KASEYA AGENT IN THE HE ENDPOINTS CODE
Datto Supports Powershell Natively you can simply past your code and it will run it. We have found our selves automating almost everything and leveraging PowerShell very heavily. It took 3 years, and a 7 month Proof of concept. The decision was not an easy one as I used to bleed Kaseya blue. We had 12K agents which we moved to Datto RMM. Using a TEMP\working_folder minimizes the risk because it's present only for the duration of the installation process, then everything is removed.Īctually today I just finished our migration. This is difficult to clean up, and this leaves behind potential vulnerabilities. We find too many MSPs use the KWorking folder as a temporary repository. ExecutePowerShell (or executeCommandLine, which sometimes works better), then GetFile to get the log and DeleteFolder with the recursive option. Then we either use WriteDirectory to write several files or WriteFile to write individual files to that folder. The only difference from what Ages4020 is suggesting is reading the registry first to find the TEMP location.
Once the procedure is complete, we use GetFile to upload the log, then recursively delete the folder we created, leaving nothing behind. It's easy to find the TEMP environment var in the registry - we create a subfolder there, push all our scripts, install files, etc there.
HOW TO INSTALL KASEYA AGENT IN THE HE ENDPOINTS HOW TO
I have no idea how to fix this issue.We provide our customers with hundreds of Agent Procedures plus scripts, and never, ever write these to the KWorking folder. I deleted the tasks and manually activated the clients thinking it was a issue with the sync.īut when i logged in the next day i saw tons of activation tasks again in ERA.Įvery minute it will generate 20 tasks.
HOW TO INSTALL KASEYA AGENT IN THE HE ENDPOINTS FULL
When i logged into ERA i saw that our whole activation task tab was full with activation tasks and then nver run (see the attached picture)
HOW TO INSTALL KASEYA AGENT IN THE HE ENDPOINTS UPDATE
You can make a task in the ESET plugin that will install the ERA agent, ESET endpoint antivirus and will activate it.Īfter the update to 6.2 we run into a problem the package installs the ERA agent and ESET enpoint antivirus without a issue and it says that the task was executed without a issue but when i log in to the client i see that ESET is'nt activated. In our company we use the Kaseya ESET plugin to enroll ESET to our clients.Īfter we upgraded to ERA 6.3 we have a issue with deploying installation packages to our clients
0 kommentar(er)
