Hmm, it doesn't seem to include the contents of the second argument -- it is probably still too long when it tries to execute the shell command. Looks like I'll have to use arguments in a file or something.
↧
RE: Procedure variable max length?
↧
RE: Symantec Endpoint Protection
I'm using v2.5.1.14
↧
↧
RE: The Return of the RDP
Hi Mike Puglia. So, you're effectively saying there won't be a September release?
On the roadmap, it currently says "Over the past year Kaseya has completely converted to an Agile approach in engineering. We use an iterative planning approach, and priorities often change during the development process based on constant input from customers and the market. This creates a mismatch between expectations set in our roadmap and what we deliver."
Does this actually mean that the 3-yearly release cadence is dead now? Because although id doesn't say as much, it seems that this is now the case.
I know - wait for the webinar......
To Kaseya, I say, your releases are too slow. Delays, delays, delays. hurry up and fix things. For us, agent procedure signing wasn't a big issue, but I know it has been for others - and that's a great start - but keep it moving please. You took out RDP with a hotfix, you can put it back in just as easily.
↧
RE: The Return of the RDP
Is it real that RDP is going to be back?
I don't want to ask why it was taken off but urge Kaseya to but it back ASAP.
↧
RE: Agent versioning system
Agents should always be updated after a server upgrade. The version of software running on the server should always match the version running on the agent. Updates to the agent software can include security-related improvements, communication improvements, bug fixes, etc. Additionally, while the agent will generally continue to check into the KServer even when running an older version, some features may not work properly or at all when an agent is running a version older than the KServer. If an agent is "misbehaving," always check that it's running the latest version and, if not, update it. This is an older article by a Kaseya partner, but the information is still valid. It's worth the quick read: virtualadministrator.com/.../is-your-kaseya-agent-out-of-date
↧
↧
RE: Mac - Silent Agent Deploy / Install Script [Bash] [PKG Install]
Nice script had do add a user agent for Curl/Kaseya to serve Macversion of client.
#!/bin/bash
#
# Valiant Technology
# julio@valiant-ny.com
# 7/29/2014
#
# This script allows silent command based installation of the Kaseya Agent Packages on Macs
# Tested on OS X 10.6-10.9.4 & Kaseya 6.3 - 7.0
#
# Set your working environment and unique package download ID.
# Package ID is found by copying the download link and the string after 'id='
# Example: setupDownload("/mkDefault.asp?id=123456789")
# useragent needs to get Macversion of client
useragent="Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11) AppleWebKit/601.1.56 (KHTML, like Gecko) Version/9.0 Safari/601.1.56"
InstallDir="/var/tmp/InstallAgent"
vsaURL="https://kaseya.yourcompany.com"
agentID="123456789"
mkdir -p "$InstallDir"
cd "$InstallDir"
# this curl sends the command to the VSA server to generate a fresh package for download
# this step is important to ensuring you've downloaded the most up to date version of the package
curl -A "$useragent" "$vsaURL/mkDefault.asp?id=$agentID" -H "Connection: keep-alive" --compressed
# download the agent
curl -O "$vsaURL/install/VSA-default-$agentID/KcsSetup.zip"
unzip "KcsSetup.zip"
chmod 755 ./Agent/KcsSetup.app/Contents/MacOS/KcsSetup
./Agent/KcsSetup.app/Contents/MacOS/KcsSetup -s
rm -R -f "$InstallDir"
exit
↧
Mac - Silent Agent Deploy / Install Script [Bash] [PKG Install]
Although I've found no official support for this, I've come up with a tested method of deploying Mac Agents via bash script. I've tested this on OS X 10.6-10.9.4 as well as VSA servers 6.3 - 7.0. In addition, using a packaging tool, it is possible to include this script in a payload-free package to generate an always up-to-date .PKG based installer.
This became necessary for me since the official Agent installer was never designed for deployment; being that it includes files that, once unzipped, are consumed upon execution. These files are located within the hidden folder '~/Agent/.KcsSetup/' and contain the unique config files required to bind the agent to your VSA server, file the agent to in a specific Organization or Group, customize the Agent icon, and deploy the initial configuration settings.
My initial goals:
- Use a generic installer with switches to deploy and file the agent to specific Organizations or Groups without requiring a unique agent deployment package for each one
- Make on-boarding easier for environments that already used ARD (Apple Remote Desktop)
- Have a re-usable installer that is always up-to-date
After picking apart the installer for some time, I realized that wouldn't be completely possible.
First, my understanding of the Agent installation process:
- A Download link for a specific agent deployment package is clicked
- A request is sent to the server to compile a fresh agent install corresponding to the specified package ID (this happens on every download)
- After a brief pause, the fresh KcsSetup.zip corresponding to this package ID begins downloading
- The KcsSetup.zip archive is expanded resulting in the following hierarchy
- '~/Agent/KcsSetup.app/' - This directory contains the latest (relevant to your server) generic binary for Agent installations
- '~/Agent/.KcsSetup/' - This hidden directory contains the customizations relevant to that specific deployment package
- KcsSetup.app is executed - This executes the binary '~./Agent/KcsSetup.app/Contents/MacOS/KcsSetup' which does the following
- Expands the generic agent installer to '/var/tmp/KAgentSilent.mpkg'
- Moves the contents of '~/Agent/.KcsSetup/*' to '/var/tmp/*' (this is why a second execution of the installer does not work)
- Executes the '/var/tmp/KAgentSilent.mpkg' package install
- The package '/var/tmp/KAgentSilent.mpkg' is dependent on the files moved from '~/Agent/.KcsSetup/*' to '/var/tmp/' for a successful install with expected results
After understanding how the installer worked, I realized that the files needed for what I wanted to do with it contain too much information to be passed in as switches. The binary '~./Agent/KcsSetup.app/Contents/MacOS/KcsSetup' accepts switches(as noted several places in the forums and seen below) but does not accept the GROUP_OPTION or MACHINE_OPTION displayed in the dialogue. I suspect this is because a 'key' gets generated that binds an deployment package and group ID when created that is unique to that package. This key or config file is visible in the hidden directory('~/Agent/.KcsSetup/KaseyaDConf.ini')
All of that being said, here is the script I came up with to get me most of the way there.
#!/bin/bash
#
# Valiant Technology
# julio@valiant-ny.com
# 7/29/2014
#
# This script allows silent command based installation of the Kaseya Agent Packages on Macs
# Tested on OS X 10.6-10.9.4 & Kaseya 6.3 - 7.0
## Set your working environment and unique package download ID.
# Package ID is found by copying the download link and the string after 'id='
# Example: setupDownload("/mkDefault.asp?id=123456789")
InstallDir="/var/tmp/InstallAgent"
vsaURL="https://kaseya.yourcompany.com"
agentID="123456789"mkdir -p "$InstallDir"
cd "$InstallDir"
# this curl sends the command to the VSA server to generate a fresh package for download
# this step is important to ensuring you've downloaded the most up to date version of the package
curl "$vsaURL/mkDefault.asp?id=$agentID" -H "Connection: keep-alive" --compressed
# download the agent
curl -O "$vsaURL/install/VSA-default-$agentID/KcsSetup.zip"
unzip "KcsSetup.zip"
chmod 755 ./Agent/KcsSetup.app/Contents/MacOS/KcsSetup
./Agent/KcsSetup.app/Contents/MacOS/KcsSetup -s
rm -R -f "$InstallDir"
After coming up with this, I used a packaging tool to add it as a post-flight script to generate an empty 2KB .pkg installer that is always up-to-date and has the ability to be installed silently via 'installer -pkg ~/KaseyaInstaller.pkg -target /'.
http://s.sudre.free.fr/Software/Packages/about.html for a GUI based packaging tool
https://github.com/unixorn/luggage for a more automation friendly command-line packaging tool
↧
Anyone else having issues with Support?
I put in tickets, it takes days and sometimes weeks or months before they even get assigned to someone ... In fact the last 4 tickets I put in the solution became irrelevant as the machines with issues were replaced BEFORE Kaseya Support even looked at the issue ... Case in point I have 1 ticket in right now that has been a bug in the system for over a year, but yet still no fix from Kaseya ... yes you saw right a BUG, everyone has this problem, yet no fix for it has been put out, it's because it's in a module that no one uses very much and it doesn;t make them any money ... so why bother fixing it ...
Well, I can live with that one for now and even understand it ... but now there's a real issue and Support as usual, or should I say the one person who occasionally checks the queues and makes faux assignments to engineers that don;t really exist just to make it look like something is being done, has;t even checked the queue for about 2 weeks ... so I don;t even get the sense that something is being done because my ticket was assigned to someone, not even an acknowledgement that my ticket was submitted other than the auto-response.
Sorry, I know I am ranting, but i have been a customer for a LONG LONG time and watched promise after promise of support will get better, and have only seen it get worse ... I wish I could go elsewhere, but I am too heavily invested in Kaseya to do so (which maybe is their plan too?) not to mention the fact when it works there is nothing out there better than Kaseya, or does as much as Kaseya does for IT Support MSPs .... I just wish they would for once fix the support issues they keep saying they will fix ...
Now get off the forums and go find someone to fix my ticket!
↧
RE: Agent versioning system
I am on VSA version 9.1.0.9. When I install and agent, even with the force option checked, the version that gets installed is 9.1.0.1.
↧
↧
Agent versioning system
Newbie question:
Are agents versioned in lockstep with the server versions? I am reading about R9, R9.2 to come, and we have a variety of agent versions (6,7,8) in the field. I need to advise on the need to update them to the latest. Would the latest agents be version 9x and soon 9.2?
↧
RE: The Return of the RDP
To Mike Puglia:
And what about Hydra and all the features the current connect was to bring?
The current connection improvements have been delayed over a year and still no improvements...RDP has drawbacks too and will these be improved?
How many broken promises and deliveries with absurd time frames must we endure?
Does this mean there will be no further deliver of the promised remote connection improvements.
Kaseya old and new management are just full of broken promises and horrible time frames for halfhearted delivers.....What about a new reporting module?
What about fixing Network Monitoring to make it actually useful?
↧
Lack of Communication
I am reaching out to the community to see what experience anyone has had with Kaseya and the lack of response. I seem to continue to run into situations where my sales rep takes days to get back to me and tech support will take days to look at a ticket.
↧
RE: Lack of Communication
Thank you for taking the time to provide this feedback.
We have created a new thread to comment on multiple related topics.
↧
↧
RE: What standard of support do you get from Kaseya?
Thank you for taking the time to provide this feedback.
We have created a new thread to comment on multiple related topics.
↧
What standard of support do you get from Kaseya?
I'm fairly new with Kaseya, I've had a few support requests I've made to Kaseya, not due to me doing something dumb, bit things were the software is flaky or my portal is definitely not working as advertised.
I have to say the support from Kaseya has been utterly dismal. I have one serious business affecting request that has languished for almost a month now. Is this just me? What kind of responses do you get?
Currently I'm wishing I went with lab-tech. Their salesman warned me about this, and I think he was right. Are you satisfied with support from K?
Paul
↧
RE: Anyone else having issues with Support?
Thank you for taking the time to provide this feedback.
We have created a new thread to comment on multiple related topics.
↧
RE: KNM not recognizing Esxi CIM account credentials
Hi kakpindi
Out of curiosity, do you have both the CIM Credentials and VMWare credentials implemented on the object/asset?
You will require both in place to monitor fully ESXi functions.
If this is in place, can you clarify what build of KNM you are running and what version of ESXi you are trying to monitor?
You mentioned you have this in place on several ESXi boxes, but only 20% are affected, do these boxes have anything in common? (ESXi version?)
Additionally, have you created a support ticket on this issue? If yes, please let me know the ticket number.
↧
↧
RE: Problem Creating Agent Procedures
APs and Custom Fields don't play well when the title of the Custom Field contains a space. You can surround with quotes or enclose in brackets, depending on how you're using the Custom Field, but I would generally recommend removing the spaces or replacing them with an underscore. Here's an old post that talks through several recommendations with Custom Fields: community.kaseya.com/.../65930.aspx. You might find that the error being returned is resolved simply by removing the spaces.
For the second script, if you are On Premise, you can create a SQL query and use the SQLRead step to read info from the db. Info on doing this is available in the help file here: help.kaseya.com/.../index.asp. The AP can run the SQL statement to read the most recent checkin date from the database and then the populate that into the Custom Field.
↧
RE: Problem Creating Agent Procedures
So on line 1 I tried removing the spaces in Original Install Date and changing it to just Original (in cmd: systeminfo|find /i "Original") still shows the Windows Installation date, I also deleted the Custom field and created one with "_" in it and crated one just called OS. When I Run Now on selected machine to check if the procedure works i still get the same error Script Summary: Failed:Failed THEN in step 1 (Line1).
↧
RE: Monitor VMware on KNM 5.0
We monitor our Dell servers overall system health via SNMP against the DRAC IP. Just need to enable SNMP on the DRAC and then configure a SNMP monitor as follows
OID1 = .1.3.6.1.4.1.674.10892.2.2.1.0
Result translation = Other=1,Unknown=2,OK=3, Noncritical=4, Critical=5,NonREcoverable=6
Data Type = SNMP data
Counter mode = Absolute value
Value type = Integer
Compare operation = Pass if equal
Compare value = 3
IBM servers (at least the ones we monitor for clients) can be monitored in similar fashion (against the IMM) with
OID1 = .1.3.6.1.4.1.2.3.51.3.1.4.1.0
Return value must be 255 for the overall system health to be OK.
↧