![How to install kaseya agent](https://kumkoniak.com/111.png)
![how to install kaseya agent how to install kaseya agent](https://cdn.soft112.com/kaseya-agent/00/00/0F/O7/00000FO7MN/pad_screenshot_240x180.jpg)
For the name of the hive software, enter BROKENSOFTWARE. The new registry hive is displayed under the HKEY_LOCAL_MACHINE key.īrowse to the \windows\system32\config\SOFTWARE folder on the OS disk that you attached. For the name of the hive, enter BROKENSYSTEM. On the menu, select File > Load Hive:īrowse to the \windows\system32\config\SYSTEM folder on the OS disk that you attached. Copy all of the files in this folder as a backup, in case a rollback is required. In the troubleshooter VM, browse to the OS disk that you attached, open the \windows\system32\config folder. Make a remote desktop connection to the troubleshooter VM. Step 2: Modify the OS disk to install the Azure VM Agent Confirm that the OS disk is online and that drive letters are assigned to the disk partitions. Open Computer management > Disk management. For the classic VM, delete the VM and keep the OS disk, and then attach the OS disk to the troubleshoot VM.Ĭonnect to the troubleshooter VM. For more information, see Troubleshoot a Windows VM by attaching the OS disk to a recovery VM using the Azure portal. Take a snapshot for the OS disk of the affected VM, create a disk from the snapshot, and then attach the disk to a troubleshoot VM.
![how to install kaseya agent how to install kaseya agent](https://addigy.zendesk.com/hc/article_attachments/4403549691795/ZaJE2aAvi74tfCDrkUpqN3XK25OwolhPqg.png)
Step 1: Attach the OS disk of the VM to another VM as a data disk Use the following steps to install the VM Agent in offline mode. How to install the VM Agent in offline mode
- You forgot the administrator password for the VM or you can't access the VM.
- The deployed Azure VM doesn't have the VM Agent installed or the agent isn't working.
-
Install the VM Agent in offline mode in the following scenarios: This article shows you how to install the VM Agent for an offline Windows virtual machine (VM). Communication will resume when XXX is available and communication from this computer is allowed.The Azure Virtual Machine Agent (VM Agent) provides useful features, such as local administrator password reset and script pushing. Event ID: 21016 OpsMgr was unable to set up a communications channel to XXX and there are no failover hosts. Check the event log on the server for the presence of 20000 events, indicating that agents which are not approved are attempting to connect. The most likely cause of this error is that the agent is not authorized to communicate with the server, or the server has not received configuration. Event ID: 20070 The OpsMgr Connector connected to XXX, but the connection was closed immediately after authentication occurred. Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination. The error code is 10061L(No connection could be made because the target machine actively refused it.). There are mostly three types of errors: Event ID: 21006 The OpsMgr Connector could not connect to XXX.