Hi all!
I know we had a support case on this at one point, but figured I’d just ask: We have some use cases where we’d like a script to run ‘at startup’, and not ‘at logon’, which is the closest analogue. We could do some voodoo to catch am Event Log, and I think the suggestion was to use a Scheduled Task; that’s… well, clunky. You have this beautiful UI with drop downs and such; why not a drop down for “Startup”?
Just to clarify too, I am not looking to strictly recreate “startup scripts”, ala GPO, where it runs like “before Explorer.exe launchs” sort of thing, but rather just “as soon as your service fires up” sort of thing. That might be the initial ‘hesitancy’ to recreate this, as you’re not acting like GPO ‘strictly’, but rather your own SYSTEM level process…
These are also all SYSTEM level processes I’d want to run, nothing in user context, etc. We have, quite honestly, like a dozen or so Configuration Items in ConfigMgr I’m trying to port over, and a lot of them are simply “check this thing, do this thing”, but ideally I’d like them to work ‘without a trigger, but not at every policy’ sort of thing.