macOS doesn't include python anymore. I am almost done with a shell script that replicates everything the python script does for macs. Is this something that would be possible to integrate as its own thing i.e. AutomateDiagnostics.sh? If so, I can submit a PR once I finish figuring out the lterrors piece.

Windows agents are reporting back: Server Check | ✗ Error | Server address not matched | Ping failure | Version check fail

Mac agents are reporting back: Server Check | ✓ https://labtech.server.com:443

Fresh install of the extension, only changed the LT server address in the configuration

The Last Updated timestamp at the top of the diags results pane can show a timestamp which has not occurred yet (is in the future).

Example

In this example all machines (guest, host, & server) are in the same timezone Europe/London (GMT +00:00) and that timezone is currently not observing DST. The Last Updates timestamp is 2022-01-31 18:28:56, but the current time is 2022-01-31 18:03 - so the Last Updated timestamp hasn't yet occurred. This logic cannot be correct.

I've not managed to trace the cause of this yet, but I'm opening this issue to track it.

Is it possible to create a session group for all broken Automate Agents?

When running the diagnostics in ConnectWise Control the following is output in the commands history:

`#!ps
#maxlength=100000
#timeout=600000
echo "DIAGNOSTIC-RESPONSE/1"
echo "DiagnosticType: Automate"
echo "ContentType: json"
echo ""
$WarningPreference='SilentlyContinue'; IF([Net.SecurityProtocolType]::Tls) {[Net.ServicePointManager]::SecurityProtocol=[Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls}; IF([Net.SecurityProtocolType]::Tls11) {[Net.ServicePointManager]::SecurityProtocol=[Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls11}; IF([Net.SecurityProtocolType]::Tls12) {[Net.ServicePointManager]::SecurityProtocol=[Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12}; [System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}; Try { (new-object Net.WebClient).DownloadString('https://raw.githubusercontent.com/johnduprey/CWCAutomateDiagnostics/master/AutomateDiagnostics.ps1') | iex; Start-AutomateDiagnostics -ltposh 'http://bit.ly/LTPoSh' -automate_server '' } Catch { $_.Exception.Message; Write-Output '!---BEGIN JSON---!'; Write-Output '{"version": "Error loading AutomateDiagnostics"}' }

DIAGNOSTIC-RESPONSE/1
DiagnosticType: Automate
ContentType: json

Get-LTServiceInfo : ERROR: Line 140: Unable to find information on LTSvc. Make sure the agent is installed.
At line:298 char:21

•         $info = Get-LTServiceInfo
  

•                 ~~~~~~~~~~~~~~~~~
  

  • CategoryInfo : NotSpecified: (:) [Write-Error], WriteErrorException
  • FullyQualifiedErrorId : Microsoft.PowerShell.Commands.WriteErrorException,Get-LTServiceInfo

Cannot bind parameter 'Date' to the target. Exception setting "Date": "Cannot convert null to type "System.DateTime"."
!---BEGIN JSON---!
{
"repair": "Reinstall",
"id": null,
"svc_ltsvcmon": {
"Status": "Not Detected",
"User": "",
"Start Mode": ""
},
"server_addr": null,
"version": "Agent error",
"ltsvc_path_exists": false,
"ltposh_loaded": true,
"clientid": null,
"locationid": null,
"svc_ltservice": {
"Status": "Not Detected",
"User": "",
"Start Mode": ""
}
}`

I then see "CWA Version: Agent error" appear under the agent name.

DIAGNOSTIC-RESPONSE/1
DiagnosticType: Automate
ContentType: json

The 'var' keyword is not supported in this version of the language.
!---BEGIN JSON---!
{"version": "Error loading AutomateDiagnostics"}

Upgraded from 20,2 to 20.3. Have had the module running for a year+ with no issues - excellent module.

Getting the error in the screenshot. As a test, uninstalled and reinstalled the module, error did not change.

Whenever we are enabling this plugin, it sends a lot of commands to the screenconnect server which is causing the server performance and our technicians are unable to connect to remote computers as it just shows the blank screen.

Please help to fix this issue.

In this part of the .sh file

status=$(launchctl list | grep com.labtechsoftware.LTSvc)
if [ -z "$status" ]; then
launchctl stop com.labtechsoftware.LTSvc
launchctl start com.labtechsoftware.LTSvc
status=$(launchctl list | grep com.labtechsoftware.LTSvc)
if [ -z "$status" ]; then
statusName="Stopped"
else
statusName="Running"
fi
else
statusName="Running"
fi

It appears that the service gets restarted.

problem is on all the macs I have I have to run the restart of the service manually before it will even notice the service has been upgrade.

Both versions of the Initializer.js file (master / dev) are currently failing to parse session events correctly, so nothing loads on the Automate tab in the browser except for the Run Automate Diagnostics link.

The function "getLatestDiagnosticEvent" is looking for data that doesn't exist, likely due to a change with the more recent versions on Control. The function as currently written:

function getLatestDiagnosticEvent(sessionDetails, diagnosticEventType) {
return sessionDetails.Connections
.map(function(c) { return c.Events; })
.reduce(function(outputArray, events) { Array.prototype.push.apply(outputArray, events); return outputArray; }, [])
.filter(function(e) {
return e.EventType === SC.types.SessionEventType.RanCommand &&
isDiagnosticContent(e.Data) &&
parseDataHeaders(e.Data).DiagnosticType.trim() == diagnosticEventType;
})
.sort(function (x, y) { return x.Time - y.Time; })
[0];
}

sessionDetails.Connections has no event information in it, because events are now a separate part of the sessionDetails object. I changed the function to the following, which resolves the errors, and the tab now loads the data correctly:

function getLatestDiagnosticEvent(sessionDetails, diagnosticEventType) {
return sessionDetails.Events
.filter(function(e) {
return e.EventType === SC.types.SessionEventType.RanCommand &&
isDiagnosticContent(e.Data) &&
parseDataHeaders(e.Data).DiagnosticType.trim() == diagnosticEventType;
})
.sort(function (x, y) { return x.Time - y.Time; })
[0];
}

No Location ID is in the data in the JSON from the agent because there's no Location ID in the /usr/local/ltechagent/state file.
Also worth noting that the Client ID which is in the file and returned JSON can be wrong, thankfully the GUI ignores it anyway.

Another one for my list when I get time. I assume this affects Linux too as diag_result in AutomateDiagnostics.py doesn't contain a Location ID field.

I've just installed and setup this plugin for CW Control and I'm noticing the following behavior. I know that Automate Diagnostics runs when a guest connects. However, this seems to be preventing control of the computer until the Automate Diagnostics finishes it's execution. For example, when I reboot a computer, I use to be able to access it as soon as the guest connected. Now after a reboot, the screen is grey and I cannot do anything with that computer until the Automate Diagnostics finishes. Once it finishes, I can see the remote screen and control the inputs.

My CW Control server is version 19.4.25542.7214 and I have configured Automate Diagnostics to pull the files needed from my Control server and not from GitHub.

Is there something that can be done about this delayed 'access' to the computer after reboots?

Getting these:

DIAGNOSTIC-RESPONSE/1
DiagnosticType: Automate
ContentType: json

Exception calling "DownloadString" with "1" argument(s): "The operation has timed out"
!---BEGIN JSON---!
{"version": "Error loading AutomateDiagnostics"}

Or something to the effect of:

The request was aborted: Could not create SSL/TLS secure channel

Wondering if instead of all this:

IF([Net.SecurityProtocolType]::Tls) {[Net.ServicePointManager]::SecurityProtocol=[Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls}; IF([Net.SecurityProtocolType]::Tls11) {[Net.ServicePointManager]::SecurityProtocol=[Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls11}; IF([Net.SecurityProtocolType]::Tls12) {[Net.ServicePointManager]::SecurityProtocol=[Net.ServicePointManager]::SecurityProtocol -bor [Net.SecurityProtocolType]::Tls12};

Could be instead of or include somehow this:

[System.Net.ServicePointManager]::ServerCertificateValidationCallback = {$true}

Thanks!

We recently upgraded Control to 22.9.10446.8359, but after upgrading Control would not respond after 10-20 minutes of uptime. We narrowed the issue down to this plugin, and since disabling we have functioned normally.