The Remote Agent seems to install perfectly, but the ConnectWiseControl portion does not. There appears to be a bug here.How can I troubleshoot the error that caused the installation to fail? Interestingly. Contact the software manufacturer for assistance.) When checking the Jamf logs, it says the script is in a "Completed" status, but I see the following error: Script result: installer: Package name is installer: Installing at base path /installer: The install failed (The Installer encountered an error that caused the installation to fail. Sudo installer -pkg "/tmp/LT/LTvc.mpkg" -target / I use a Jamf policy to place the Agent installer in /tmp/ and then run a script afterwards that does: #!/bin/sh Identifier: Ĭode requirement: identifier "" and anchor apple generic and certificate 1 / exists / and certificate leaf / exists / and certificate leaf = K8M3XDZV9Y Identifier: /usr/local/ltechagent/ltechagentĬode requirement: identifier ""īundleID / identifier "" and anchor appleīundleID / identifier "" and anchor apple I have the following related PPPC Config Policies (Created used the latest PPPC Utility) in place:Ĭode requirement: identifier "" and anchor appleīundleID / identifier "" and anchor apple When logged into the CWA Console, I am able to download the MacOS Agent installer that is setup to put the device into our instance of CWA. What I currently have and what I'm currently seeing: Looking for advice on how to roll forward with a silent installation of both of these pieces of ConnectWise Automate (CWA), so that they appear and work with our console correctly. I'm having trouble doing a clean and silent install for both the Remote Agent and the ConnectWiseControl piece. We hope that you experience great success when doing so.Does anyone else here use ConnectWise Automate (ie - not the standalone Screenconnect product)? When done, remove your publicly hosted installer file or set the URL to private.īy following this process, you’ll save your team quite a bit of time while also eliminating the need to interrupt your end users. Based on your MAC signup settings, the newly installed agent should bind to the computer’s existing ID in ConnectWise Automate and maintain its existing location. Installs the agent in the default install location.Downloads your generic ConnectWise Automate installer and transfers it to /tmp.If the agent is not currently installed, this command will fail. The four commands above are performing the following actions: Be sure to remove the asterisks when doing so.Ĭurl -0 **Insert agent download URL** -o /tmp/agent.zip Insert your own download URL where specified. Upload the installer to a location that will be publicly accessible via URL.Log into your ConnectWise Automate Web Control Center to download a Mac agent installer.Review your Automate server’s MAC signup settings and adjust to obtain your desired behavior.Use the following steps to reinstall your ConnectWise Automate Mac agent using background CLI via ConnectWise Control or another background command line service: By proceeding, you are doing so at your own risk. Diligex is not responsible for any issues that you may experience. Well if you also utilize ConnectWise Control as part of your suite or any other ancillary tool that can perform command line functions in the background, you can use it to your advantage to reinstall your ConnectWise Automate agent without needing to get the end user involved.ĭISCLAIMER: Diligex provides no guarantee for the process listed below. Ideally, you’d handle the matter without having to get the end user involved. The last thing you want to do when dealing with a situation like this is have to interrupt your end users to connect into their computer to repair or reinstall your agent. Whether it be due to a macOS update or a system issue, the ConnectWise Automate Mac agent has experienced occasional problems that have been discussed among many partners. If you utilize the ConnectWise suite of products to manage workstations that include Macs, you may have occasionally run into a need to reinstall your ConnectWise Automate agent due to lost communication or to troubleshoot a reporting issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |