Jump to content

Search the Community

Showing results for tags 'automate'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • MSPGeek
    • The Geek Cast
    • Code of Conduct
  • ConnectWise Automate / Labtech
    • ConnectWise Automate / LabTech
    • ConnectWise Automate / LabTech - Development

Categories

  • ConnectWise Automate
    • Scripts
    • Plugins
    • SQL Snippets
    • Role Definitions
    • Automate PowerShell Code
    • Reports
    • Internal Monitors
    • Remote Monitors
  • ConnectWise Manage
    • API Interacting Code

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


About Me


Location


Agent Count


INTERESTS


OCCUPATION


ICQ


WEBSITE


WLM


YAHOO


AOL


FACEBOOK


GOOGLEPLUS


SKYPE


TWITTER


YOUTUBE

Found 58 results

  1. Hello, I created a script to deploy Sentinel One AV and in the script i have to call the site token so that it verifies the product. I set it in the Client Info and added the site token. I also set the Global Parameter in the script it self as: @SentinelOne_Site_Token@ with the value blank. Ran it and got a error. Added the value as the actual site token that i got from the Sentinel One website just to test it. The first line in my script reads: GET: @SentinelOne_Site_Token@ = [EXTRAFIELD SentinelOne_Site_Token] Further down in the script where the script actually executes it states: EXECUTE as Admin: %windir%\system32\msiexec.exe /i %tempdir%\SentinelInstaller-@soarchitecture@-@soversion@.msi /SITE_TOKEN=@SentinelOne_Site_Token@ /SILENT /l*v C:\windows\temp\sosinstall.log When i click on that line it is set up like so: Function: Process Execute as Admin File: %windir%\system32\msiexec.exe Arguments: /i %tempdir%\SentinelInstaller-@soarchitecture@-@soversion@.msi /SITE_TOKEN=@SentinelOne_Site_Token@ /SILENT /l*v C:\windows\temp\sosinstall.log And it is set to "Wait for Process" The exact error i get when i run it is: Script: S6366 - Starting at Server Time: Wednesday, April 22, 2020 10:03:34 AM IF F62 AppName (P1): Sentinel 4.0.2.42 Jump (P2): 0 T: 0.9057142 L1 F139 Note (P1): Check that all global variables have been set T: 0.9107007 L2 F103 EdfId (P1): 542 TargetId (P2): 2529 Variable (P3): SentinelOne_Site_Token T: 0.9117026 L3 F70 Value (P1): soversion Comparer (P2): 2 To (P3): ChangeMe Jump (P4): :Update_Global T: 0.9136999 L4 F70 Value (P1): sosarchitecture Comparer (P2): 2 To (P3): ChangeMe Jump (P4): :Update_Global T: 0.9136999 L5 F200 Local (P1): Software/SentinelOne/SentinelOne.msi Destination (P2): C:\WINDOWS\Temp\SentinelInstaller-x64-4.0.2.42.msi T: 0.9136999 L6 F114 File (P1): 'C:\WINDOWS\Temp\SentinelInstal...' Check (P2): 1 Jump (P3): :Download_Failed T: 40.9213775 L7 F125 File (P1): %windir%\system32\msiexec.exe Wait (P3): 0 T: 66.9247203 L8 F29 Message (P1): @shellresult@ T: 681.0338181 L9 F29 Message (P1): Checking SO Agent install T: 681.0358104 L10 F139 Note (P1): :Check_Install T: 681.0358104 L11 F54 T: 681.0358104 L12 F120 App (P1): SentinelOne 4.0.2.42 Jump (P2): :Successful_Install T: 697.0415205 L13 F29 Message (P1): SentinelAgent 4.0.2.42 Agent install failed. Please check logs T: 697.0455042 L14 F215 T: 697.0475083 Please Help!!
  2. Using Automate, I am trying to locate/create a report that will show me the OS build number of my endpoints. As build 2004 is being released I want to see who is on what. I looked in the canned reports and also under DataViews and am not able to locate this information. Am I missing it? Any advice is greatly appreciated.
  3. Hi all, I have been working with Automate Scripts for quite some time now and I have one issue which support cannot seem to understand. Everytime I use a Shell Function (Shell as Admin, Shell, Shell Enhanced), the variable %shellresult% always return OK, whether I am running an actual shell command (Like ping google.com) or if I am executing a powershell script. Do you have any idea on what could cause the issue. See one script result and content in attachement.
  4. So, you're here because tomorrow 1 months time on 1st September you're going to lose a bunch of Automate agents due to TLS 1.2 compatibility. https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Supportability_Statements/Supportability_Statement%3A_TLS_1.0_and_1.1_Protocols_Unsupported So there's some measures that while not foolproof, I whipped up in a couple of hours yesterday to at least get a good head start on sorting these devices out. 1) 2 Searches, one that identifies Vista and below that will be gone no matter what you do, and one that identifies your Windows 7, Server 2008 and Server 2008 R2 machines that you can at least try to save 2) 2 remote monitors. One that looks for if the TLS 1.2 Patch is even applied to the machine, and one that checks if the DisabledByDefault registry key is set to 0 3) 2 scripts that can be used as an Autofix action to install the patch and set the registry key if necessary So, 1). Attached are the two searches. 2) You will want two remote monitors assigned to a group that you have limited to the 7-2008-2008R2 search. The first is an EXE monitor with this as the EXE. You want to monitor for the condition of "Exists". "%windir%\System32\WindowsPowerShell\v1.0\powershell.exe" -noprofile -command "(get-hotfix -Id KB3140245,KB4019276 -ErrorAction silentlycontinue).hotfixid" This is your monitor for if the patch is installed or not. Second monitor is to check if the registry key is set correctly. For this you can use a Registry key remote monitor to look at the following key. You want to monitor for a condition of "0". SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\Protocols\TLS 1.2\Client\DisabledByDefault 3) The Autofix scripts. First is "Enable TLS 1.2". You will need Darren White's Email Technician function script, otherwise just remove lines 8,9,10,13,14,15. You can then set this script as an Autofix action for your remote monitor checking for the registry key Second is "Deploy TLS1.2 Patch". You will need to enter the URL's to the patches here which you can download from the MS website. I wasn't sure if these were static URL's or not so I downloaded them and uploaded them to our web server which is why I've stripped the URL's out. You can get the downloads from the links provided in ConnectWise's KB article at the top of this post. Again you can then set this as an Autofix action against your monitor to check if the patch is installed. This patch will also set the registry keys as well as installing the patch. NOTE! It does not do anything but download the file on servers by default. You can edit lines 22 and 25 to GOTO :Install Patch instead if you want to allow it to automatically make changes to servers as well. It will not reboot machines as the WUSA command has the /norestart switch. You can drop that if you want to force reboots. I will throw one disclaimer out there. The Deploy TLS 1.2 script has had limited testing. We found that out of the machines that we tested that failed to have the patch installed, there was an underlying issue with patching in general. EDIT: So it would appear that there is another registry key potentially required. And that is HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp and KKLM\SOFTWARE\Wow6432node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp for 64 bit machines. The value required is "DefaultSecureProtocols" and it needs to be set to 0x00000800 Again you can just fire up remote monitors for these, and then have an autofix script to set these appropriately. All I did for mine was copy the Enable TLS 1.2 script and swap out lines 6 and 7 appropriately like below (Note the OS Versions it runs on were changed for line 7 from Windows Server to Windows 64 bit) EDIT EDIT: So at least 1 ConnectWise support rep has also advised that .NET Framework 4.5 or higher has to be installed on the endpoint. You can quickly setup a remote monitor for this with the below configuration, and then script the install if it fails. Deploy TLS 1.2 Patch Script.xml Enable TLS 1.2 Script.xml XP-2003-Vista Search.xml 7-2008-2008R2 Search.xml
  5. We use Automate version 12 and Control. Over the past few months, we have seen a growing number of Automate agents becoming corrupted and going offline. At the same time, we are finding those same agents are in fact online and their Control (Screen Connect) session is active. With that said, is there a way to setup something in Automate that would alert us if an agent is offline in Automate but is still online in Control? That way we would know that we need to repair the Automate agent on those computers.
  6. New agents are getting this error, Automate support is useless and I got in the schedule for Sunday.......can anyone advise what the issue is and how to fix? We've uninstalled/reinstalled, even going into Revo, both MSI and EXE versions, etc. LTService v120.451 - 12/4/2018 8:02:20 PM - Error: The inventoryrepository's InitializeInventoryDB method has thrown an exception.::: LTService v120.451 - 12/4/2018 8:02:20 PM - Registered LTService for remoting on 42000.::: LTService v120.451 - 12/4/2018 8:02:20 PM - REMOTING PORT IS:42000::: LTService v120.451 - 12/4/2018 8:02:20 PM - INIT CLR:4.0.30319.42000::: LTService v120.451 - 12/4/2018 8:02:20 PM - Platform\OS: Win32NT\10 0::: LTService v120.451 - 12/4/2018 8:02:20 PM - Settings loaded.::: LTService v120.451 - 12/4/2018 8:02:35 PM - Post Upgrade Actions. Ex: Version string portion was too short or too long. ::: LTService v120.451 - 12/4/2018 8:02:35 PM - 64BIT: True::: LTService v120.451 - 12/4/2018 8:02:35 PM - Setting SSL Policy::: LTService v120.451 - 12/4/2018 8:02:50 PM - Download Dep File Success 1 C:\windows\LTSvc\setcad.exe::: LTService v120.451 - 12/4/2018 8:02:50 PM - Failed to check Dependancy: 1 C:\windows\LTSvc\setcad.exe::: LTService v120.451 - 12/4/2018 8:02:51 PM - Download Dep File Success 3 C:\windows\LTSvc\cpuidsdk.dll::: LTService v120.451 - 12/4/2018 8:02:51 PM - Failed to check Dependancy: 3 C:\windows\LTSvc\cpuidsdk.dll::: LTService v120.451 - 12/4/2018 8:02:52 PM - Download Dep File Success 4 C:\windows\LTSvc\ICSharpCode.SharpZipLib.dll::: LTService v120.451 - 12/4/2018 8:02:52 PM - Failed to check Dependancy: 4 C:\windows\LTSvc\ICSharpCode.SharpZipLib.dll::: LTService v120.451 - 12/4/2018 8:02:52 PM - Download Dep File Success 5 C:\windows\LTSvc\Interop.wodVPN.dll::: LTService v120.451 - 12/4/2018 8:02:52 PM - Failed to check Dependancy: 5 C:\windows\LTSvc\Interop.wodVPN.dll::: LTService v120.451 - 12/4/2018 8:02:52 PM - Download Dep File Success 6 C:\windows\LTSvc\Interop.WUApiLib.dll::: LTService v120.451 - 12/4/2018 8:02:52 PM - Failed to check Dependancy: 6 C:\windows\LTSvc\Interop.WUApiLib.dll::: LTService v120.451 - 12/4/2018 8:02:52 PM - Download Dep File Success 9 C:\windows\LTSvc\LSR.exe::: LTService v120.451 - 12/4/2018 8:02:52 PM - Failed to check Dependancy: 9 C:\windows\LTSvc\LSR.exe::: LTService v120.451 - 12/4/2018 8:02:53 PM - Download Dep File Success 10 C:\windows\LTSvc\nsoftware.IPWorks.dll::: LTService v120.451 - 12/4/2018 8:02:53 PM - Failed to check Dependancy: 10 C:\windows\LTSvc\nsoftware.IPWorks.dll::: LTService v120.451 - 12/4/2018 8:02:54 PM - Download Dep File Success 11 C:\windows\LTSvc\nsoftware.IPWorksSSH.dll::: LTService v120.451 - 12/4/2018 8:02:54 PM - Failed to check Dependancy: 11 C:\windows\LTSvc\nsoftware.IPWorksSSH.dll::: LTService v120.451 - 12/4/2018 8:02:54 PM - Download Dep File Success 12 C:\windows\LTSvc\nsoftware.IPWorksSSNMP.dll::: LTService v120.451 - 12/4/2018 8:02:54 PM - Failed to check Dependancy: 12 C:\windows\LTSvc\nsoftware.IPWorksSSNMP.dll::: LTService v120.451 - 12/4/2018 8:02:55 PM - Download Dep File Success 14 C:\windows\LTSvc\PS.exe::: LTService v120.451 - 12/4/2018 8:02:55 PM - Failed to check Dependancy: 14 C:\windows\LTSvc\PS.exe::: LTService v120.451 - 12/4/2018 8:02:55 PM - Download Dep File Success 17 C:\windows\LTSvc\SCHook.dll::: LTService v120.451 - 12/4/2018 8:02:55 PM - Failed to check Dependancy: 17 C:\windows\LTSvc\SCHook.dll::: LTService v120.451 - 12/4/2018 8:02:55 PM - Download Dep File Success 18 C:\windows\LTSvc\screenhooks.dll::: LTService v120.451 - 12/4/2018 8:02:55 PM - Failed to check Dependancy: 18 C:\windows\LTSvc\screenhooks.dll::: LTService v120.451 - 12/4/2018 8:02:55 PM - Download Dep File Success 19 C:\windows\LTSvc\screenhooks32.dll::: LTService v120.451 - 12/4/2018 8:02:55 PM - Failed to check Dependancy: 19 C:\windows\LTSvc\screenhooks32.dll::: LTService v120.451 - 12/4/2018 8:03:00 PM - Download Dep File Success 20 C:\windows\LTSvc\tvnserver.exe::: LTService v120.451 - 12/4/2018 8:03:00 PM - Failed to check Dependancy: 20 C:\windows\LTSvc\tvnserver.exe::: LTService v120.451 - 12/4/2018 8:03:01 PM - Download Dep File Success 23 C:\windows\LTSvc\wodVPN.dll::: LTService v120.451 - 12/4/2018 8:03:01 PM - Failed to check Dependancy: 23 C:\windows\LTSvc\wodVPN.dll::: LTService v120.451 - 12/4/2018 8:03:02 PM - Download Dep File Success 93 C:\windows\LTSvc\System.Data.SQLite.dll::: LTService v120.451 - 12/4/2018 8:03:02 PM - Failed to check Dependancy: 93 C:\windows\LTSvc\System.Data.SQLite.dll::: LTService v120.451 - 12/4/2018 8:03:02 PM - Download Dep File Success 95 C:\windows\LTSvc\SQLite.Interop.dll::: LTService v120.451 - 12/4/2018 8:03:02 PM - Failed to check Dependancy: 95 C:\windows\LTSvc\SQLite.Interop.dll::: LTService v120.451 - 12/4/2018 8:03:06 PM - Download Dep File Success 100 C:\windows\LTSvc\labvnc.exe::: LTService v120.451 - 12/4/2018 8:03:06 PM - Failed to check Dependancy: 100 C:\windows\LTSvc\labvnc.exe::: LTService v120.451 - 12/4/2018 8:03:07 PM - Download Dep File Success 101 C:\windows\LTSvc\vnchooks.dll::: LTService v120.451 - 12/4/2018 8:03:07 PM - Failed to check Dependancy: 101 C:\windows\LTSvc\vnchooks.dll::: LTService v120.451 - 12/4/2018 8:03:08 PM - Download Dep File Success 105 C:\windows\LTSvc\devP2P.dll::: LTService v120.451 - 12/4/2018 8:03:08 PM - Failed to check Dependancy: 105 C:\windows\LTSvc\devP2P.dll::: LTService v120.451 - 12/4/2018 8:03:08 PM - Download Dep File Success 106 C:\windows\LTSvc\LabTechCommon.dll::: LTService v120.451 - 12/4/2018 8:03:08 PM - Failed to check Dependancy: 106 C:\windows\LTSvc\LabTechCommon.dll::: LTService v120.451 - 12/4/2018 8:03:08 PM - Download Dep File Success 107 C:\windows\LTSvc\wbem-sharp.dll::: LTService v120.451 - 12/4/2018 8:03:08 PM - Failed to check Dependancy: 107 C:\windows\LTSvc\wbem-sharp.dll::: LTService v120.451 - 12/4/2018 8:03:09 PM - Download Dep File Success 108 C:\windows\LTSvc\nsoftware.IPWorks.System.dll::: LTService v120.451 - 12/4/2018 8:03:09 PM - Failed to check Dependancy: 108 C:\windows\LTSvc\nsoftware.IPWorks.System.dll::: LTService v120.451 - 12/4/2018 8:03:09 PM - Download Dep File Success 109 C:\windows\LTSvc\nsoftware.IPWorksSSH.System.dll::: LTService v120.451 - 12/4/2018 8:03:09 PM - Failed to check Dependancy: 109 C:\windows\LTSvc\nsoftware.IPWorksSSH.System.dll::: LTService v120.451 - 12/4/2018 8:03:09 PM - Download Dep File Success 110 C:\windows\LTSvc\nsoftware.IPWorksSSNMP.System.dll::: LTService v120.451 - 12/4/2018 8:03:09 PM - Failed to check Dependancy: 110 C:\windows\LTSvc\nsoftware.IPWorksSSNMP.System.dll::: LTService v120.451 - 12/4/2018 8:03:10 PM - Download Dep File Success -10 C:\windows\LTSvc\plugins\Backup.Acronis.dll::: LTService v120.451 - 12/4/2018 8:03:10 PM - Failed to check Dependancy: -10 C:\windows\LTSvc\plugins\Backup.Acronis.dll::: LTService v120.451 - 12/4/2018 8:03:11 PM - Download Dep File Success -495 C:\windows\LTSvc\plugins\Intronis.dll::: LTService v120.451 - 12/4/2018 8:03:11 PM - Failed to check Dependancy: -495 C:\windows\LTSvc\plugins\Intronis.dll::: LTService v120.451 - 12/4/2018 8:03:11 PM - Cleaning up Supporting Files and Logs:::: LTService v120.451 - 12/4/2018 8:03:12 PM - Initializing Tunnels...::: LTService v120.451 - 12/4/2018 8:03:12 PM - Observed unhandled exception: Site:TestTunnels Error:System.BadImageFormatException: Could not load file or assembly 'Interop.wodVPN, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The module was expected to contain an assembly manifest. File name: 'Interop.wodVPN, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' at LTSVC.modTunnels.TestTunnels(Boolean& VPNAvail) at LTSVC.modTunnels.InitTunnels() at LTSVC.LTService.Startup() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. ::: LTService v120.451 - 12/4/2018 8:03:12 PM - Error: The inventoryrepository's InitializeInventoryDB method has thrown an exception.::: LTService v120.451 - 12/4/2018 8:03:12 PM - Registered LTService for remoting on 42000.::: LTService v120.451 - 12/4/2018 8:03:12 PM - REMOTING PORT IS:42000::: LTService v120.451 - 12/4/2018 8:03:12 PM - INIT CLR:4.0.30319.42000::: LTService v120.451 - 12/4/2018 8:03:12 PM - Platform\OS: Win32NT\10 0::: LTService v120.451 - 12/4/2018 8:03:12 PM - Settings loaded.::: LTService v120.451 - 12/4/2018 8:03:27 PM - Post Upgrade Actions. Ex: Version string portion was too short or too long. ::: LTService v120.451 - 12/4/2018 8:03:27 PM - 64BIT: True::: LTService v120.451 - 12/4/2018 8:03:27 PM - Setting SSL Policy::: LTService v120.451 - 12/4/2018 8:03:43 PM - Download Dep File Success 1 C:\windows\LTSvc\setcad.exe::: LTService v120.451 - 12/4/2018 8:03:43 PM - Failed to check Dependancy: 1 C:\windows\LTSvc\setcad.exe::: LTService v120.451 - 12/4/2018 8:03:44 PM - Download Dep File Success 3 C:\windows\LTSvc\cpuidsdk.dll::: LTService v120.451 - 12/4/2018 8:03:44 PM - Failed to check Dependancy: 3 C:\windows\LTSvc\cpuidsdk.dll::: LTService v120.451 - 12/4/2018 8:03:45 PM - Download Dep File Success 4 C:\windows\LTSvc\ICSharpCode.SharpZipLib.dll::: LTService v120.451 - 12/4/2018 8:03:45 PM - Failed to check Dependancy: 4 C:\windows\LTSvc\ICSharpCode.SharpZipLib.dll::: LTService v120.451 - 12/4/2018 8:03:45 PM - Download Dep File Success 5 C:\windows\LTSvc\Interop.wodVPN.dll::: LTService v120.451 - 12/4/2018 8:03:45 PM - Failed to check Dependancy: 5 C:\windows\LTSvc\Interop.wodVPN.dll::: LTService v120.451 - 12/4/2018 8:03:45 PM - Download Dep File Success 6 C:\windows\LTSvc\Interop.WUApiLib.dll::: LTService v120.451 - 12/4/2018 8:03:45 PM - Failed to check Dependancy: 6 C:\windows\LTSvc\Interop.WUApiLib.dll::: LTService v120.451 - 12/4/2018 8:03:45 PM - Download Dep File Success 9 C:\windows\LTSvc\LSR.exe::: LTService v120.451 - 12/4/2018 8:03:45 PM - Failed to check Dependancy: 9 C:\windows\LTSvc\LSR.exe::: LTService v120.451 - 12/4/2018 8:03:46 PM - Download Dep File Success 10 C:\windows\LTSvc\nsoftware.IPWorks.dll::: LTService v120.451 - 12/4/2018 8:03:46 PM - Failed to check Dependancy: 10 C:\windows\LTSvc\nsoftware.IPWorks.dll::: LTService v120.451 - 12/4/2018 8:03:47 PM - Download Dep File Success 11 C:\windows\LTSvc\nsoftware.IPWorksSSH.dll::: LTService v120.451 - 12/4/2018 8:03:47 PM - Failed to check Dependancy: 11 C:\windows\LTSvc\nsoftware.IPWorksSSH.dll::: LTService v120.451 - 12/4/2018 8:03:47 PM - Download Dep File Success 12 C:\windows\LTSvc\nsoftware.IPWorksSSNMP.dll::: LTService v120.451 - 12/4/2018 8:03:48 PM - Failed to check Dependancy: 12 C:\windows\LTSvc\nsoftware.IPWorksSSNMP.dll::: LTService v120.451 - 12/4/2018 8:03:48 PM - Download Dep File Success 14 C:\windows\LTSvc\PS.exe::: LTService v120.451 - 12/4/2018 8:03:48 PM - Failed to check Dependancy: 14 C:\windows\LTSvc\PS.exe::: LTService v120.451 - 12/4/2018 8:03:48 PM - Download Dep File Success 17 C:\windows\LTSvc\SCHook.dll::: LTService v120.451 - 12/4/2018 8:03:48 PM - Failed to check Dependancy: 17 C:\windows\LTSvc\SCHook.dll::: LTService v120.451 - 12/4/2018 8:03:48 PM - Download Dep File Success 18 C:\windows\LTSvc\screenhooks.dll::: LTService v120.451 - 12/4/2018 8:03:48 PM - Failed to check Dependancy: 18 C:\windows\LTSvc\screenhooks.dll::: LTService v120.451 - 12/4/2018 8:03:48 PM - Download Dep File Success 19 C:\windows\LTSvc\screenhooks32.dll::: LTService v120.451 - 12/4/2018 8:03:48 PM - Failed to check Dependancy: 19 C:\windows\LTSvc\screenhooks32.dll::: LTService v120.451 - 12/4/2018 8:03:53 PM - Download Dep File Success 20 C:\windows\LTSvc\tvnserver.exe::: LTService v120.451 - 12/4/2018 8:03:53 PM - Failed to check Dependancy: 20 C:\windows\LTSvc\tvnserver.exe::: LTService v120.451 - 12/4/2018 8:03:54 PM - Download Dep File Success 23 C:\windows\LTSvc\wodVPN.dll::: LTService v120.451 - 12/4/2018 8:03:54 PM - Failed to check Dependancy: 23 C:\windows\LTSvc\wodVPN.dll::: LTService v120.451 - 12/4/2018 8:03:54 PM - Download Dep File Success 93 C:\windows\LTSvc\System.Data.SQLite.dll::: LTService v120.451 - 12/4/2018 8:03:54 PM - Failed to check Dependancy: 93 C:\windows\LTSvc\System.Data.SQLite.dll::: LTService v120.451 - 12/4/2018 8:03:55 PM - Download Dep File Success 95 C:\windows\LTSvc\SQLite.Interop.dll::: LTService v120.451 - 12/4/2018 8:03:55 PM - Failed to check Dependancy: 95 C:\windows\LTSvc\SQLite.Interop.dll::: LTService v120.451 - 12/4/2018 8:04:00 PM - Download Dep File Success 100 C:\windows\LTSvc\labvnc.exe::: LTService v120.451 - 12/4/2018 8:04:00 PM - Failed to check Dependancy: 100 C:\windows\LTSvc\labvnc.exe::: LTService v120.451 - 12/4/2018 8:04:01 PM - Download Dep File Success 101 C:\windows\LTSvc\vnchooks.dll::: LTService v120.451 - 12/4/2018 8:04:01 PM - Failed to check Dependancy: 101 C:\windows\LTSvc\vnchooks.dll::: LTService v120.451 - 12/4/2018 8:04:01 PM - Download Dep File Success 105 C:\windows\LTSvc\devP2P.dll::: LTService v120.451 - 12/4/2018 8:04:01 PM - Failed to check Dependancy: 105 C:\windows\LTSvc\devP2P.dll::: LTService v120.451 - 12/4/2018 8:04:02 PM - Download Dep File Success 106 C:\windows\LTSvc\LabTechCommon.dll::: LTService v120.451 - 12/4/2018 8:04:02 PM - Failed to check Dependancy: 106 C:\windows\LTSvc\LabTechCommon.dll::: LTService v120.451 - 12/4/2018 8:04:02 PM - Download Dep File Success 107 C:\windows\LTSvc\wbem-sharp.dll::: LTService v120.451 - 12/4/2018 8:04:02 PM - Failed to check Dependancy: 107 C:\windows\LTSvc\wbem-sharp.dll::: LTService v120.451 - 12/4/2018 8:04:02 PM - Download Dep File Success 108 C:\windows\LTSvc\nsoftware.IPWorks.System.dll::: LTService v120.451 - 12/4/2018 8:04:02 PM - Failed to check Dependancy: 108 C:\windows\LTSvc\nsoftware.IPWorks.System.dll::: LTService v120.451 - 12/4/2018 8:04:03 PM - Download Dep File Success 109 C:\windows\LTSvc\nsoftware.IPWorksSSH.System.dll::: LTService v120.451 - 12/4/2018 8:04:03 PM - Failed to check Dependancy: 109 C:\windows\LTSvc\nsoftware.IPWorksSSH.System.dll::: LTService v120.451 - 12/4/2018 8:04:03 PM - Download Dep File Success 110 C:\windows\LTSvc\nsoftware.IPWorksSSNMP.System.dll::: LTService v120.451 - 12/4/2018 8:04:03 PM - Failed to check Dependancy: 110 C:\windows\LTSvc\nsoftware.IPWorksSSNMP.System.dll::: LTService v120.451 - 12/4/2018 8:04:04 PM - Download Dep File Success -10 C:\windows\LTSvc\plugins\Backup.Acronis.dll::: LTService v120.451 - 12/4/2018 8:04:04 PM - Failed to check Dependancy: -10 C:\windows\LTSvc\plugins\Backup.Acronis.dll::: LTService v120.451 - 12/4/2018 8:04:05 PM - Download Dep File Success -495 C:\windows\LTSvc\plugins\Intronis.dll::: LTService v120.451 - 12/4/2018 8:04:05 PM - Failed to check Dependancy: -495 C:\windows\LTSvc\plugins\Intronis.dll::: LTService v120.451 - 12/4/2018 8:04:05 PM - Cleaning up Supporting Files and Logs:::: LTService v120.451 - 12/4/2018 8:04:05 PM - Initializing Tunnels...::: LTService v120.451 - 12/4/2018 8:04:06 PM - Observed unhandled exception: Site:TestTunnels Error:System.BadImageFormatException: Could not load file or assembly 'Interop.wodVPN, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The module was expected to contain an assembly manifest. File name: 'Interop.wodVPN, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' at LTSVC.modTunnels.TestTunnels(Boolean& VPNAvail) at LTSVC.modTunnels.InitTunnels() at LTSVC.LTService.Startup() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Threading.ThreadHelper.ThreadStart() WRN: Assembly binding logging is turned OFF. To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1. Note: There is some performance penalty associated with assembly bind failure logging. To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog]. :::
  7. so I wrote powershell and got it displaying fine but when I add that powershell code into the "execute script" line in automate and then have the results of that sent in an email, the email is formatted weird and I thought it would be exactly like the powershell output. has anyone ran into this issue? Im not sure how to go about this
  8. GM- I am new here and this is my first post. I am internal IT setting up Automate in my environment. I would like Automate to create new tickets from emails going to helpdesk@contso.com, and we use Azure / O365. I went in and created an App Registration as per the directions: https://docs.connectwise.com/ConnectWise_Automate/ConnectWise_Automate_Documentation/060/120/045 What happened was nothing - no tickets came in from the emails that I sent to helpdesk@contso.com. I then talked to Chat at Automate. They suggested switching the information on Inbox Folder to just say Inbox. This created tickets from my personal email. That was fun. Questions: Should I add helpdesk@contso.com to have Azure permissions to be able to create the App Registration in that user name? Or Could I just add helpdesk@contso.com to the Username field instead of my email address? The directions from CW state to use that the Username field needs to be the email address of the person that created the App Registration. Screen shot of what I thought would work but failed: Like Comment
  9. Bud

    LT share

    I have only been using Automate for 6-8 months now so i admit that I am still green. I am starting to dive in to all the amazing things it can do. In regards to the ltshare, is it possible to use it as a file repository to send several files to many workstations all at once? I find the command-->file--> download from lt share to be super helpful but I want to be able to send several files possibly even a directory to all machines at a location at once. Any help is appreciated.
  10. Hi All, 1st post on here. We are new to Automate as of January this year and there has been a lot to learn. I have a couple of scenarios which I require help with to create appropriate monitors. These monitors were possible on Solarwinds but we cant find a way to set them up on Automate. 1) We require a monitor that checks a file, and if that files time stamp is greater than an hour, then it raises an alert. This monitor is to check that a DVR is working correctly and recording data, if the file its monitoring doesnt get written to in over an hour then there is an issue we need to look at. 2) We require a monitor that checks the content of a file and looks for the words "Alert" or "Error". Again, this was available in Solarwinds but I cant find anything but to check that a file or directory exists. 3) We require a monitor that checks a website for the word "Disconnect". Solarwinds used to check a website and if that website loads with a message saying Disconnect then a ticket was raised. I have checked the create a monitor via wizard but none of those seem to fit. I believe this may be a new monitor from scratch but again could not find the options that would fit the above scenarios. I believe the system is very powerful and will be capable of the above, I just need a little help to get more familiar with the system. Appreciate any help.
  11. View File Windows 7,8,10 Upgrade Script This script will upgrade copies of Windows to whatever Windows 10 ISO you give it. You will need to upload the Windows 10 ISO to your LTShare/Transfer/ folder(by default in the /ISO/ sub folder). For Windows 7 installs, you must put a copy of 7z.dll and 7z.exe in your LTShare/Transfer/ folder(by default in the \Software\7ZipCLI\ sub folder). This is because it extracts the ISO since Windows 7 can't mount it. I recommend a 32bit copy because they work for both 32 and 64bit. You can download the 7-Zip installer and open it with 7-Zip like a zip file to extract just those files without bothering to install it. You can now also use an EDF to specify a UNC path to get the ISO from instead of downloading from the CWA server. The EDF is located under the TNE - Setup tab called TNE - Windows 10 ISO Location under the location screen. Double click on a location to find it. This should be in the format of \\server\iso, no trailing slash. If you put domain computer permissions on the share and the folder the CWA agent shouldn't have a problem copying it. Also just added, the script will now check to see if the ISO is in place before running, so you can create a script to preload the ISO. Now supports Windows 10, 8, and 7. Sorry, no Windows 9 support at this time. Thanks to @Slartibartfast, @johnduprey, and the rest of the community for contributions and bug reports. More details and discussion can be found on the forum post: If you are downloading the ISO directly from your CWA server, I might recommend the below to rate limit it. It is a script that will rate limit how many computers are running it at once. Of course, that will slow deploy, so you have to be careful not to accidentally run it on to many and cause it to run outside of maintenance hours. Submitter danialbulloch Submitted 11/20/19 Category Scripts  
  12. I would like to customize one of the basic inventory reports to include the machine's BIOS date. For the life of me I can't find the data source that includes this field. It is definitely captured by the Automate agent, on the hardware tile it is located here: Does anyone know how I can get that field on a report? Thanks! [First Post]
  13. Hey all, Attached are two scripts. "EXAMPLE - IT Glue Credentials" - This could easily be a scriptlet as well, but you could pretend this would be any other script where you would want to have credentials from IT Glue to do something with them. This script then calls... "FUNCTION - Retrieve IT Glue Credentials" - This is the script that does the work to go off and pull the credentials from IT Glue Assumptions You're syncing Automate and IT Glue, or at least have the names of your clients in IT Glue exactly match those in Automate. You have an Enterprise IT Glue plan Things you need to do before using Step 4 in "EXAMPLE - IT Glue Credentials" - This variable needs to be set to the exact name of the password you want to pull from IT Glue. Limitation here is that you need consistency in your password naming - we use a PowerShell script to pre-populate various password records for ones we'd want to pull into Automate Step 4 in "FUNCTION - Retreive ITGlue Credentials" - This query needs to be updated with a 'centralised' Server that you want to run the PowerShell from that goes off to do the IT Glue query. This was so I knew PowerShell versions wouldn't get in the way of the script and that my IT Glue API key wasn't being exposed to hundreds of servers. Step 6 in "FUNCTION - Retreive ITGlue Credentials" - This PowerShell script needs to be updated with your IT Glue URI and your API Key. This API Key obviously needs the Password Access box ticked... What you should then have at the end of it are two variables, @username@ and @password@ - You can then use these in your Automate script. There is some basic error checking built in - one for if it simply can't find the credentials, and one for if the PowerShell command fails for some reason. These are then tied to Script GoTo's in the EXAMPLE script that you can then log off of if you wish. FUNCTION - Retreive ITGlue Credentials.xml EXAMPLE - IT Glue Credentials.xml
  14. Hello all, Im trying to write an automate script that will run the following power-shell script md c:\\HWID Set-Location c:\\HWID Set-ExecutionPolicy -Scope Process -ExecutionPolicy Unrestricted Install-Script -Name Get-WindowsAutoPilotInfo Get-WindowsAutoPilotInfo.ps1 -OutputFile AutoPilotHWID.csv I was wondering what the best way of going about having the Prompts that appear when going through to have [y] or [a] scripted to be input to continue the power shell process This would be running as admin on multiple machines, will i need to be adding something like /a or -Force to my scripts in Automate. Any help would be appreciated as im fairly new to power shell 🙂
  15. Version 2.5.0

    454 downloads

    This script will upgrade copies of Windows to whatever Windows 10 ISO you give it. You will need to upload the Windows 10 ISO to your LTShare/Transfer/ folder(by default in the /ISO/ sub folder). For Windows 7 installs, you must put a copy of 7z.dll and 7z.exe in your LTShare/Transfer/ folder(by default in the \Software\7ZipCLI\ sub folder). This is because it extracts the ISO since Windows 7 can't mount it. I recommend a 32bit copy because they work for both 32 and 64bit. You can download the 7-Zip installer and open it with 7-Zip like a zip file to extract just those files without bothering to install it. You can now also use an EDF to specify a UNC path to get the ISO from instead of downloading from the CWA server. The EDF is located under the TNE - Setup tab called TNE - Windows 10 ISO Location under the location screen. Double click on a location to find it. This should be in the format of \\server\iso, no trailing slash. If you put domain computer permissions on the share and the folder the CWA agent shouldn't have a problem copying it. Also just added, the script will now check to see if the ISO is in place before running, so you can create a script to preload the ISO. Now supports Windows 10, 8, and 7. Sorry, no Windows 9 support at this time. Thanks to @Slartibartfast, @johnduprey, and the rest of the community for contributions and bug reports. More details and discussion can be found on the forum post: If you are downloading the ISO directly from your CWA server, I might recommend the below to rate limit it. It is a script that will rate limit how many computers are running it at once. Of course, that will slow deploy, so you have to be careful not to accidentally run it on to many and cause it to run outside of maintenance hours.
  16. We're looking for a way to modify an alert - Or any other method, really - that will generate a ticket whenever a machine is added in to Automate. We get tickets with the default monitor for when they're added in to the 'New devices' pool, for machines that need to be assigned to the proper client.. But that doesn't cover situations in which a custom agent installation is used, or if a machine was retired and recently started checking back in. Any help is appreciated, thank you!
  17. So, I have a really cool and useful script I found posted here and it works fantastically for a majority of sites. Unfortunately it doesn't yet work at all sites because at some places there is more than one domain controller. At those sites, only one of the multi-DC's has the AD Domain Naming Master role, but also only one has the NTDS role - so I am confused as to why the script cannot correctly identity this and select just 1 DC from 2 or 3 when c.RoleName = "AD Domain Naming Master" Is there an easier way to single out systems based on roles installed? OG post for more info
  18. I am looking to make a script that would allow me to create a user profile without having to log into the machine. Does anyone have experience with the power-shell command that would do this?
  19. Hi All, Wanted to see what everyone has setup for Standards and Health in CW Automate. I am in the process of setting up a Standards for a specific client location and it baffles me that the Standards and Health does not allow you to edit globally created standard at the location or group level. Is this a bug? I have been in touch with CW support who advised, the Standards and Health plugin is working as it should. I am slo struggling to apply newly created standards to a specific location. I can apply the new standard to other locations just this specific location. Any help welcome!
  20. Hi All, Wanted to see what everyone has setup for Standards and Health in CW Automate. I am in the process of setting up a Standards for a specific client location and it baffles me that the Standards and Health does not allow you to edit globally created standard at the location or group level. Is this a bug? I have been in touch with CW support who advised, the Standards and Health plugin is working as it should. I am slo struggling to apply newly created standards to a specific location. I can apply the new standard to other locations just this specific location. Any help welcome!
  21. So I have been combing through the forum here for a while looking for examples of how people have scripted local admin account setups. I have built out a script to do all of those tasks but wanted to customize the @Password@ variable in some way so that the script could reference a client-specific local admin password. This way ALL the PCs I manage don't have the same local admin pw. Is there an intuitive way to do this with EDF's etc? I can't even find where I would put in a Client EDF and which script function to use for this. I feel like they are right in front of my eyes. What am I missing? Anyone else have a different setup for creating different local admin passwords via scripts? I don't want a different script for each client unless there is no other choice, but I feel like fetching an edf value that has that pw would be perfect, just not clear on the details. Any help would be awesome.
  22. Just wanted to see if anyone would have any experience to offer or opinions on this. We are working to setup a new on-prem server to be our new Automate Server. We currently have an on-prem Automate server but just working to move it to a more robust and better server than where it currently sits. We were thinking to have a split server setup where we would set the application server in the DMZ and then have the database server in our main production network in hopes to increase the security by placing the publicly accessible items in a DMZ and to keep the database more protected. As we had a call with Automate support, they suggested that this setup would most likely cause some performance issues and may not really increase the security much since we would need to open up certain ports from our main production network to the DMZ for our agents to check in and for the Control Center to operate properly. They also said that having a split server for our agent count was overkill for right now and that having a single server would be better. With that said, has anyone had our proposed setup before, and if so, have you had any performance issues with it? Also, due to our agent count, we are open to having a single server but also thought to vlan off the server so that it's on its own network so we can keep our production environment more protected. Again, if we went this way, has anyone had any issues with having an Automate server in its own VLAN and separate from the rest of the network? I am assuming not since it should work just fine but just wanted to get some feedback on this. Thanks!
  23. Hi all Just coming to create some manual reports in connectwise automate for the first time. Looking to extract a report showing the cores and logical processors of devices i have agents on. Spoke to connectwise and they said heres our standard ( of which i can't find this info ) and they mentioned, if its not in "inventory" come here and check forums :) Only thing i can find in automate is the type of processor, had a quick look at the fields in custom reports but could spot anything there. Any know of such a report / how to generate this in automate or other scripts that would extract this information? Thanks
  24. Hi Folks, I was in the middle of setting up SSO for Connectwise thinking this is great all users can log in to all the applications using their Office 365 account Then I learnt that in true Connectwise style they are not enabling SSO for the thick client in Automate - sure everything is moving to the web (yeah right) So now I am left with a dilemma - I enable SSO for Manage / Sell / Control and then setup a different 2FA for Automate which is bloody tedious. What have others done here just out of curiosity. This whole move to the web client is dumb the web client is nowhere near the fat client. Thanks
  25. Hi All, First post so apologies if I'm in the wrong location on the forum. We are about 6 months into the roll out and already its becoming clear that disconnected agents where the devices has been retired or replaced need to be dealt with cleverly so stop a bulk building up. We have spoken to a number of clients and they are all of the opinion anything disconnected for more that 60 days can just be deleted. A:) What are your thoughts on this, how are you handling diconnected agents B:) Is there a way to make Automate automate this process. ie Agent last connect >60 days = Retire asset C:) If a retired asset comes back online after its been retired, how does Automate handle this. Does it move it back to live, does it warn you or does it continue to ignore it. Thank you in advance for any thoughts or assistance. Regards Patrick
×
×
  • Create New...