Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Logging Information

  1. 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

...

  1. ezdeploy EZDService actually starts deploying agents, running scripts or kicking off Windows Update (including Feature Updates)

  2. The EZDService will generate log files at c:\EZDeploy\logging folder on the machine being deployed.

    1. 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. Note that the URL for the EzdService.zip file expires after 15 min - so if you are troubleshooting outside that 15 min window - you won’t be able to test the download URL in browser etc…

    2. 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.

  3. The c:\EZDeploy\logging\InstallLogs folder will store logs for

    1. Agent_Installer.log if integrated with ConnectWise Automate

    2. Logs for Chocolately

...

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 .

...

    1. , ezdeploy Scripts, Custom Installers and Powershell Scripts.

  1. RMM Scripts in Automate will have script log information on both the agent Scripts tab and on the script itself using the Script Logs button when editing script.

Order of Deployment

OneTouch

WebStart

  1. Windows Provisioning

  2. Create local admin account

  3. Connect to SSID (if enabled)

  4. CleanPC (if enabled)

  5. Install EZDService

  6. Reboot

  7. Disable hibernate, disk timeout, monitor timeout and standby timeout

  8. Set Build Notification registry values

  9. Computer Rename and Reboot (if enabled)

  10. RMM Agent Install (if enabled/Automate integration in place)

  11. Script items in order

  12. Windows Build and Updates (if enabled)

  13. Apply final Power Settings

  14. Power Off when finished if flag set

  15. Reset Build Notification registry values

  16. Remove EZD Service and files (logging files left in place)

  17. Remove Chocolatey agent if flag not set

  1. Install EZDService

  2. Disable hibernate, disk timeout, monitor timeout and standby timeout

  3. Set Build Notification registry values

  4. Computer Rename and Reboot (if enabled)

  5. RMM Agent Install (if enabled/Automate integration in place)

  6. Script items in order

  7. Windows Build and Updates (if enabled)

  8. Apply final Power Settings

  9. Power Off when finished if flag set

  10. Reset Build Notification registry values

  11. Remove EZD Service and files (logging files left in place)

  12. Remove Chocolatey agent if flag not set