Microsoft Provisioning portion logs into Applications and Services Logs > Microsoft > Windows > Provisioning-Diagnostics-Provider > Admin
Any errors during the provisioning portion up to and including CleanPC option should log as event since all that happens before Toolshed EZDService actually starts deploying agents, running scripts or kicking off Windows Update (including Feature Updates)The EZDService will generate log files at c:\EZDeploy\logging folder on the machine being deployed.
EzdServiceDownloaderInfo.log
Connectivity to Google is tested for up to 5 min to verify internet connectivity. If successful then should try and download the Ezdservice.zip to the target computer and log creation of the folders, EzdService creation and the cleanup.
You may have EzdServiceDownloaderError.log if download fails.EzdService-YYYYMMDD.txt will log the order of deployment once the Microsoft Provisioning portion has completed. If using Automate the agent deployment first, then Configuration Profile items processed and finishes with Windows Updates if enabled on OneTouch Deployment package.
The c:\EZDeploy\logging\InstallLogs folder will store logs for
Agent_Installer.log if integrated with ConnectWise Automate
Logs for Chocolately and Native Toolshed Scripts
Automate RMM Scripts will have their own script logs available within Automate Control Center client.
If Toolshed is able to schedule and the script runs but fails - you would need to check the RMM Script logging to troubleshoot. If Toolshed not able to run any RMM scripts from Automate - you likely have a permissions issue - see ConnectWise Automate - Permission Requirements .
Additionally Automate scripts can also have permissions set directly on a script that can potentially block Toolshed User/Service Account from scheduling script if the User Class is not present on the individual script with Execute Permission. Reference Add Permissions to Scripts