I have had a tab open to look at this for about 4 weeks 
I think you have a couple of typos. the command is:
iwr -useb https://christitus.com/win | iex
Sorry, I was going off of memory, not good when oneās wife calls him a geezer. The correct command according to his website, yours works too, is ```
irm christitus.com/win | iex. Instead of igm itās supposed to be irm.
One cool thing about this, that I found out, is after you choose the settings that you want, you can export them to a file. Then afterward programatically call the program with iex ā& { $(irm christitus.com/win) } -Config [path-to-your-config] -Runā
If that works in oneās environment, then appears we can put that into a script and apply automatically.
1 Like
the config option could make it quite useful
Iām not a fan of big monolithic scripts to do everything, so I have a bunch of small powershell scripts for my new computer onboarding and maintenance
For sure this is the way to do it. You can use a simple RMM Alert to trigger an Automated Remediation and control the order the individual scripts run in.
2 Likes
@daniel.hedges Iām confused where this is placed and how the event would trigger the script to run. Do you have the script calling those modules when an asset is assigned to a group that has a policy attached?
What event would trigger the imaging remediation?
Sorry if I am a little slow. Thanks.
you could have a script that you run against a newly deployed machine that creates a staging alert and then the AR would kick off against that alert.
Calling the syncro module locally you could probably do a PowerShell script that installs the syncro agent and then runs a script locally that creates the alert, so you do not need to kick it off from syncro itself.
We are still using FOG so do not need this too much but could use it for other things.
The āstart imaging processā is just a script creating a custom RMM Alert. From any RMM Alert, you can have Automated Remediation fire, with multiple scripts queued up in order. Iāll do a complete walk-through post early next week. A good setup might be to have an organization or a Policy folder for āstagingā and the Script that fires the RMM Alert is the only setup script that is assigned to the policy that is assigned to that Organization/Folder
1 Like
Adam, I would like a copy of your scripts. It is very appreciated. It would be nice to not have to reinvent the wheel.
Thank you.
Hey Adam, I would like a copy of your script, if available.
Thanks
thanks, perhaps consider placing these in the Community Scripts area
I sanitized my scripts and put them in a public Github repository. If you have any questions about them, let me know. Iām particularly proud of the printer install script.
6 Likes
thanks for this Adam.
Nice, would love to get a copy for our internal use.
you can download a copy from his github?
Whereās the fun in you sanitizing the scripts 
This helps a ton. Especially for someone like me. Hopefully I can share something soon.
Happy to share. I donāt have chip on my shoulder regarding those scripts, so if anyone has any criticisms, corrections, feature suggestions, whatever, definitely throw them my way.
Iāve started adding better Sycro alerts and logic to clear the alert if error state is fixed on the next script run, so Iām not drowning in invalid alerts.
I am not sure whatās happening but when I try accessing any of the items on the list, I get thisā¦
I just confirmed this error. Apologies! Iāll post back when I have this figured out.
So I havenāt had this error since the one time. Iāve checked it from multiple computers with different browsers.
confirm it appears to be accesible