No. Most functions executed in Live Connect are not visible to end users, unless the command is set to echo or be displayed.
Just select the procedure again and click on the cancel button. Be mindful that you can only cancel a scheduled action before it is sent to the endpoint.
Yes it can by using the Agent Procedure tool to uninstall specific patches.
You can do a silent remote and the end user will not be notified at all. However, if you start moving the mouse on the end user’s screen, the end user will be disrupted.
Kaseya Policy Management is not an AD policy management tool. It only manages Kaseya options which is the purpose of the Kaseya Policy Management.
Kaseya does not manage the Windows GPO. You can however, use the Agent Procedure module to do that for machines that are not enrolled to an AD.
You do not need to restart the machine. It works just like a net user reset password command.
Every agent that is installed will have an audit of all the system information. This information can be accessed from the agent screen. You can also generate a report and have it scheduled.
Yes, you can with Kaseya Network Monitor module which is already included in your VSA subscription.
By using Kaseya VSA together with IT Glue (an IT documentation tool), we can support a function called 1-Click Access. During a remote session, an engineer can click that button, and the password will be injected directly into the remote computer.
Yes, you can. You can do that via the Remote Control module. You can set user role policies or machine policies.
Most MSI installed software have an uninstalled GUID string which can be utilised by agent procedures. At the same time, there are EXE softwares, which have their own uninstall parameters, that we can set agent procedures to utilise. For example, C:\program files\7zip -uninstall /Quiet.
Go to Screen Recordings, then select the machine you want.
For the cloud version, screen recordings are recorded on the Kaseya server. The limit is 1GB.
If you are using the on-premise version, it will be stored locally.
To access recordings, go to Manage Agent > Screen Recordings then select the machine you want.
The so-called roll back can be done by uninstalling the patches via Agent Procedure. Most patches are MSI, so they will have an uninstalled GUID String which can be used in Agent Procedure.
Yes. If you want to reset password for the domain admin, be sure to run the reset function on the Active Directory server.
When you enrol 2FA into one device/one app, you can’t enrol it on another app. If you lose access to the app, another admin in Kaseya VSA can go to System > Server Management > Logon Policy and un-enrol your user from 2FA. Then you can re-enrol with another app.
Yes, under the Software Management module.
Pre-recorded video messages can be played using scripting.
Please refer to the network requirements here:
Kaseya R95 System Requirements
We have a training and certification course called the Kaseya Administrator Training for VSA. For more information, email us at [email protected]
Bandwidth requirements can vary widely, depending on the functions used. Remote desktop and file transfers can potentially consume large amounts of bandwidth, depending on screen resolution, complexity and file size.
Live Connect in an non-intrusive remote from the back end while Remote Control is a screen-sharing remote.
VSA supports both MSI and EXE installation file for application installation.
Kaseya VSA does not supports MDM at the moment.
Agent communication uses AES-256 and Remote session is encrypted using TLS (Transport Layer Security).
To have a better understanding, you may refer here: Kaseya VSA Security & Compliance Overview.
With the Kaseya Network Monitoring module, it will utilise a gateway machine to monitor device bandwidth based on Windows WMI, RPC and for Linux and other device, via SNMP.
You have the option to specify a silent switch in the agent procedure to uninstall programs silently in the background.
Kaseya Remote allows seamless machine user-switching, you can switch between Windows users and still maintain control of the remote session.
Kaseya VSA has two hosting options: Cloud SAAS (which is hosted in Kaseya Cloud) and On-Premise (for SAAS). You will be given an account to login upon purchasing.
After setup for On-Premise, you can define the username to login.
If an agent is idle, it typically uses very little bandwidth as low as a few kilobytes or bytes to send a keep alive package. Hence, bandwidth requirements are dependent on what instructions you want the agents to execute. If bandwidth is of a concern, VSA allows you to set a distribution window to spread the load of agent instructions for execution.
Agent installation works like how other software installation works, it will require admin access. If all machines are authenticated via Active Directory, VSA will be able to remote deploy via Active directory server. If all machines are workgroup based, you can use Kaseya Network Discovery, with the requirement of a centralised machine with full access to the network range and credentials of the remote computer you intend to install VSA Agent on.
Kaseya VSA is available for both on-premise and on the cloud. Kaseya VSA get machine vulnerability from Microsoft standards, it will scan the patches required that are applicable for that machine.
VSA Installer works like how other software installation works, if you are able to deploy via GPO to the endpoint that does not have admin rights, you can then put the VSA in to GPO and script it to deploy to all the endpoints.
If machines are under a Domain environment, you can deploy the agents via Active Directory to the endpoint silently and do not require the user to key in administrative credentials.
The difference between VSA and VSA Lite is the functionality of the admin console, not the agent itself. In the full VSA Suite, you can define module permissions to other admin, for instance, a Junior IT Admin will only have remote access feature to all the machines, while a Senior IT Admin will have more module access such as patching and scripting to all the machines or selected group of machines. Minimum OS supported can be found here: Kaseya R95 System Requirements.
Alerts are “near real-time” as when the triggers hit based on sample interval, it will take some time for mail servers both sending and receiving ends to process the email turning it into an alert.
Linux agent only supports Intel-based machines. SuSE Linux Enterprise (10 & 11), Red Hat Enterprise Linux (5 & 6), Ubuntu (10.04 LTS, 12.04 LTS, and the two most recent non-Long Term Support versions), OpenSuSE 12, and CentOS (5 & 6) are fully supported.