Hi there!
We are slowly testing/deploying Immy. Our CEO wants to have the functionality to lower the amount of on-site visits or being able to deploy Immy straight to remote clients. We want to launch Immy straight from startup (same way we do with USB) but having trouble figuring out best way to do this? Looking to see if this is possible or if there is a good workaround?
I am looking into the same request from our CEO. We are looking into an imaging service offered by our vendor to install an updated/debloated OS image with an Immy .ppkg pre-applied. This only allows us to deploy a generic onboarding immy instance though, no auto onboarding or pre-set user.
I only have our internal imaging go to an onboarding tenant first (with no onboarding).
Then I am using a series of Rewst automations to review our PSAβs project ticketing/configurations to determine what Immy Tenant to move it to and start onboarding.
If you have a tool like that, it could fit in well in your process.
Here is my Documentation of this process. This uses the new computer in onboarding state Immybot trigger in Rewst - This requires that we make a base config in Connectwise PSA with the serial # (which you should be scanning when you receive products, yes?). Then then Immybot Win11 pkg I have puts it into a default onboarding tenant that has 0 deployments.
Overview
This workflow automates the onboarding process for new PCs by integrating ConnectWise PSA and ImmyBot. It retrieves configuration information from ConnectWise PSA, matches the device to the appropriate ImmyBot tenant, and initiates the ImmyBot onboarding process. The workflow also handles asset tagging and creates project ticket notes to document the onboarding.
Integrations Used
Integration
Purpose
ConnectWise PSA
Retrieve configuration/asset information and create project ticket notes
ImmyBot
List tenants, change tenant assignment, add tags, and trigger onboarding
Workflows (Subworkflow)
Locate project ticket information
Input Parameters
Parameter
Description
id
The ImmyBot Computer ID of the device to onboard
serialNumber
The serial number of the PC to onboard
Workflow Process Flow
Phase 1: Initialization
Task
Action
Description
START
Core: noop
Initializes workflow and publishes serial_number and immy_computer_ID from input parameters
Phase 2: Configuration Lookup
Task
Action
Description
Get_Configuration
ConnectWise PSA: List Configurations
Queries ConnectWise PSA for configuration matching the serial number. Publishes:
cwm_company_name
cwm_company_id
cwm_config_id
cwm_tag_number
Phase 3: ImmyBot Tenant Matching
Task
Action
Description
immy_bot_list_tenants
ImmyBot: List Tenants
Retrieves all ImmyBot tenants and uses sophisticated Jinja logic to match the correct tenant based on company and site name from ConnectWise configuration. Publishes immy_tenant_ID
Change_Immy_Tenant
ImmyBot: API Request
Moves the computer to the matched ImmyBot tenant via POST to /computers/change-tenant
Phase 4: Asset Tag Check & Conditional Branching
Task
Action
Description
Check_if_asset_tag_exists
Core: noop
Decision point that checks if CTX.cwm_tag_number exists. Routes to different onboarding paths based on result.
Branch A: Asset Tag EXISTS
Task
Action
Description
Tag_for_Tagged
ImmyBot: API Request
Adds tag ID 138 to the computer in ImmyBot via POST to /computers/add-tags
Start_Immy_Onboarding_with_Tag
ImmyBot: API Request
Initiates ImmyBot onboarding with the asset tag value included in maintenance task parameters via POST to /run-immy-service
Branch B: No Asset Tag
Task
Action
Description
Start_Immy_Onboarding
ImmyBot: API Request
Initiates standard ImmyBot onboarding without asset tag via POST to /run-immy-service
I setup a golden image with each of our vendors, and they apply that before the computers ship to users. have them turn it on and connect to wifi and itβll run onboarding, and go into a special tenant. it did take me an embarrassingly long time to figure it out, and each vendor has their own tool to capture the image, but itβs saved tons of time.