As simple as title says, how can I open VSA built-in procedures? We really need that for debugging purposes.
There was a Easter Egg ( Alt + Left Click in IE) that could allow this through KLC, but obviously the Live module has been re-designed and the shortcut is gone.
Any suggestions?
Thanks a lot Combo :)
just in case where someone else needs it, you have to fill in with the EXACT name or ID of the desired script (it's not a search box)
Gabriele
I've done All users MSI installs like this:
1. executeFile as SYSTEM and wait: %windir%\System32\msiexec.exe /jm file.msi /qn
2. executeFile as USER and wait: %windir%\System32\msiexec.exe /i file.msi /qn
Try adding ALLUSERS=1 to the end of your command:
msiexec.exe /i "c:\kworking\files\UC-One.msi" /quiet /norestart /log "c:\kworking\files\uc-onelog.log" ALLUSERS=1
That will hopefully tick the box for you during a silent installation.
AlanRQ We are seeing the same thing although we also have not found a way to reproduce it. The mouse being a half inch off is annoying but also potentially dangerous if it has not been noticed.
This appeared for us after installing patch 24 a couple of weeks ago.
Can you try the following and report back? From your machine, go to the directory:
%APPDATA%\Kaseya\KaseyaLiveConnect.ini
If the file doesn't already exist, create the file and edit it with the following:
[Renderer]
UseSWRenderer=true
Then reload Live Connect and see if the mouse cursor placement is accurate this time.
You can't add functions to Kaseya scripts in the way you are thinking. I'm looking for a redesign in a coming release, but as of now I've pretty much given up on using Kaseya Agent Procedures for anything other than pushing down a script (normally PowerShell), executing script, and getting the results. Not saying Agent Procedures are worthless, we use them extensively, just saying we normally put the bulk of the logic and functionality in a script that runs client side.
In the full Kaseya way, you would have to create an Agent Procedure called SendMessage. In this Procedure, you would read the Global Variables to get the message parameter and just know that Global Variable 1 must contain the message. Then from any other procedure you can write your message to Global Variable 1 and then call the SendMessage Procedure.
That said, I would recommend creating a Send-Message PowerShell script that accepts one parameter. Then from any Agent Procedure you can write the script, execute the script with the message, and delete the script.
Hi everybody,
I'm trying to learn Kaseya Scripting language, but I can't understand how to pass an argument to a custom procedure.
For instance, Kaseya's sendMessage is not working for my clients, so I started writing my own sendMessage procedure to use OS built-in commands to display a message (msg for Windows, osascript for Mac, maybe zenity for Linux).
now, I wanted to use my sendMessage procedure in another procedure, like it was a method: sendMessage(String message). is it possible to do this with Kaseya?
Thank you in advance!
Mark,
It looks like this procedure requires a custom audit field. Did you:
1. Create the "ConfigSyncDate" custom audit field by going to Audit > View Individual Data > Machine Summary and selecting New Custom Field
2. Edit line 15 and 20 where it says "Select the System info field to update", click the dropdown, and set it to the custom audit field "ConfigSyncDate"
Also line 19 is checking for the string "2015" in the variable #GLOBAL:ConfigSyncDate# so i'm unsure if that needs to be updated to "2017" or not.
Tried that fix here on an affected machine. No dice.
We are in the SaaS environment and are having trouble finding a good way of excluding small drives on our 300+ servers that we manage. Typically these are Witness disks or OEM recovery disks/partitions.
Did the Live Connect update coincide with a Windows update or video driver update? Is there anything specific on the machine that's different from yours? For example, is the machine running 4K resolution? Just wanted to confirm on that before we dig in further.
Hi Everyone,
Experiencing a strange issue when using Live Connect that I hope you can help with.
Since upgrading to the latest version of Live Connect - 9.4.6409.1304 a number of our users when they connect to machines via Live Connect the machine will be both missing the blue bar with Ctrl+Alt+Del on the top (you can see a few pixels of the bottom of it) It's like the whole live connect screen has been shifted up by 50 or so pixels. So when they click on the screen where the host mouse actually registers that click as being is off by a half an inch.
This means they have been accidentally clicking links because where they click on Live Connect screen doesn't match where the click happens on the machine they've connected to. As it is it's pretty unusable.
I can't seem to reproduce it on my own machine and i'm on the same Live Connect version as them. They have completely uninstalled Live Connect and installed it again. Rebooted machines and host machines. This happens on any machine they connect to. They are using Windows 10 and Chrome as a browser.
Any troubleshooting steps, ideas or help would be appreciated!
Thanks in advance.
Alan
I have created a ticket about this, but seeing that it's been a few days and no one has been assigned to it, I thought I'd bring it up here too.
So a few days ago, on one of the PCs in our office, we got an email alert notifying us about a active threat (which turned out to be a false positive in reality). So I did one of the first things that I thought would do that trick, that being creating an exclusion for it in Kaspersky. That, for whatever reason, still triggered the email alert. So then I went ahead and deleted the file itself, and that didn't work either!
For others out there that use Kaseya's email alerts for antivirus, have you encountered this extremely annoying issue? If so, let me know and guide me towards the solution to this. I don't want to have to keep removing our alert profile from these machines, because in moments where we need it most should there be an actual virus, these email alerts will come in very handy. Right now though, they are just nothing more than a mere annoyance because of them not working properly.
Create a custom field called "Excluded Drives"
Add the drive letters you want to exclude on a per machine basis
Then configure your Low Disk Monitoring to run a script when a low disk alert/alarm occurs.
You can pass into the script the drive letter as a variable that the alarm relates to
Then have the script compare this letter to the ones added to the custom field.
If there is a match then just exit the script
If there is no match i.e. you do want an alert/ticket , then use the "SendAlert" step in the script to create both
Paul
Post an export of your script ..e.g the one that doesn't work ..then we can look at it and see what needs fixing
I am also experiencing this. We submitted a ticket 17 July 2017 14:34 (196185) and have received this reply.
This issue has been identified to be a confirmed defect and has been progressed to our engineering team and is currently being worked on at a very high priority. I will update you of any progress made through this support ticket.
Thanks for sharing all. We are definitely planning on being able to use these as a KNM gateway, so the linux agent looks to be out the window. I'll review some of the models you all have recommended.
I'd like to know what others are doing for an instance where you need to place some type of system at a customer site for remote access or monitoring with KNM. We have some customers with no on premise servers or very few workstations period, so we'd like to come up with a cheap solution to pay for ourselves and place at the customer site.
I know we could do an old laptop with Linux, but has anyone come up with any other cheap SFF options, like a refurb'd ThinClient or mini-PC where we could also install Linux and send out to the site?
Any thoughts or ideas would be much appreciated? Thanks!
Brilliant Gabriel Medina that looks like the ticket - i saw that the custom field wasn't there but didn't quite understand the script, i assumed it'd create it - never really played much with AP's before.