On new computer setups, there's often a long list of settings to apply and apps to be installed. Sometimes this work requires reboots in-between the different steps. 

This example shows the most reliable way to do this using Syncro's scripting and automation features. You get complete control over the steps and can easily create variations without needing a ton of policies.

The high level steps are as follows:

1. Create a script that triggers an RMM Alert. (Ours is called “Imaging.”)
2. Create a policy that at minimum, uses the script from Step 1 and enables remote access. (Ours is called “Staging Policy.”)
3. Assign the Policy from Step 2 to a Policy Folder for an Organization. (Ours is called “Staging.”)
4. Install the Syncro Agent on the new machines using the Policy Folder from Step 3.
5. Gather a list of scripts that apply settings, install apps, and/or run the jobs you want as part of your imaging process. 
   Tip: As much as possible, it's best to have individual scripts for each.
6. Build an Automated Remediation to control the order your scripts from Step 4 will run when the RMM Alert from the script in Step 1 triggers.

Step 1: Create the Imaging Script

1. Navigate to the Scripts tab.
2. Click +New Script.
3. Name this script “Imaging.” 
4. In the Script body, enter the following two lines:
   

   Import-Module $env:SyncroModule
   Rmm-Alert -Category ‘Imaging’ -Body ‘Imaging’

   Note: The values for -Category and -Body you provide for the RMM alert in line 2 can be anything you like. This example uses ‘Imaging’ for both.
5. Click Create Script.

Step 2: Create the Staging Policy

1. Navigate to the Policies tab.
2. Click +New Policy.
3. Name the policy “Staging Policy.”
4. Select the Scripting policy category from the left side.
5. From the “Add a Scripting Option” dropdown menu, select Setup Scripts.
6. Click +Add Entry. 
   1. In the first dropdown, select your Imaging Script from Step 1. 
   2. In the second dropdown, choose “If Never Run:” 
      
7. Select the Enable Access policy category from the left side, and check the “Enable And Deploy Splashtop For Assets On This Policy” box.
8. Make any other additions, then click Save Policy.

Step 3: Assign the Policy to an Organization

1. Navigate to the Organizations tab.
2. Select an existing Organization (or create a new one) to display its Details Page.
3. Select the Assets & Policies subtab.
4. Click the top-level folder (named after the Organization), then click Add Folder. 
   1. Name the new policy sub-folder “Staging.”
   2. Click Add Folder.
5. Click Assign Policy.
   1. Select the Policy you created in Step 2: Create the Staging Policy.
   2. Click Assign Policy.
6. Click Save Changes:

Step 4: Create an RMM Agent Installer

1. While still on the Organization's Details Page, click +New > RMM Agent Installer.
2. In the Policy Folder dropdown menu, select the “Staging” sub-folder you created in Step 3: Assign the Policy to an Organization.
3. Use the installer to install the Syncro Agent on the machines: 
   

See also: Install and Deploy the Syncro RMM Agent.

Step 5: Gather Imaging Scripts

Next, gather a list of scripts you want to run to onboard the new machine. You'll use these in the next step as Actions for the Automated Remediation. 

Here are some scripts from the Community Library that might be of Interest:

• Install Chocolatey
• App Install - One-Time Install from a Choco Package
• Install Available Windows Updates
• Force Restart Windows
• Get Bitlocker Keys
• Disable hard disk sleep in power settings
• Add Local Admin Account
• Debloat Windows Apps
• Don’t display last logged in user and show Other User
• Dell Command update all

Step 6: Build an Automated Remediation

1. Navigate to the Assets & RMM tab.
2. From the View button menu in the upper right, select Automated Remediation.
3. Click +New Automated Remediation.
4. Name the Automated Remediation “Image Machine.”
5. Optionally, check the Run Once box.
6. Add a Condition with the following settings:
   • Trigger Category
   • Is
   • “Custom Script: Imaging” (This the value for -Category you specified in your RMM Alert from Step 1: Create the Imaging Script).
7. For each of the scripts in your list from Step 5: Gather Imaging Scripts, add Actions to “Run Script” and set the Delay as desired:
   
   IMPORTANT: When the RMM Alert fires and this Automated Remediation triggers, all Actions you define here will immediately happen on the Assets for the Organization simultaneously. Therefore, what you specify in the Delay fields for each Action/script is what controls their order. It also allows you to take into account any reboot time. In the screenshot above, the listed delays (60, 65, 70, 75, 80 minutes) are all calculated from the initial trigger time, not sequentially from the completion of the previous step. Each step's delay is an aggregate from the original first step's trigger. For example, if the process starts at 12:00 PM:
   • The 60-minute delay script runs at 1:00 PM.
   • The 65-minute delay script runs at 1:05 PM.
   • The 70-minute delay script runs at 1:10 PM.
8. Click Save.

Now, whenever the RMM Alert is fired via the Imaging script from Step 1: Create the Imaging Script, all the "Run Script" actions will queue up in order on Assets for that Organization:

Advanced Tips & Tricks

Step 3: Assign the Policy to an Organization shows the recommended way to do this. However, you could instead create a new, temporary Organization to keep the machines completely separate. After they've been imaged, you can then multi-select the Assets associated with your temporary, staging Organization from the Assets & RMM tab, and use the “Change Customer” option in the Bulk Actions menu to associate them with the actual Organization(s). You could also add a Condition to your Automated Remediation for “Customer” “Is | ”Is Not" and specify specific Customer Organizations to include or exclude in the process.

As your business and service offerings grow, you could daisy-chain several Automated Remediations together. As shown in Step 1: Create the Imaging Script, you could set it up so that the last thing a script does is fire an RMM Alert to move onto the next Automated Remediation. For example, all Organizations might get Stage 1 imaging, but only those who paid for an upgraded imaging stack also gets Stage 2.