New
#2621
If you are able to run them under XPE With Core Only it will Add around 300 mo to your build, That would be nearly Tolerable for me...
But Honestly don't take my advice for granted Many are using themes and such... And are adding anything they need to reach their Goal, etc... I only Build plain XPE relying only on VC++ And The "Main Application required to achieve Goal". ...Yes I have A SUPER Loaded XPE Version But It's Loaded With Software And Drivers.
In a corporate Environment Where PowerShell Core Is Mandatary, the Payload is acceptable, But for Every days common task It's unlikely to Serve as a primary Platform.
That Said... I dont Know what theses scripts are capable of... But If You are Working in an Environment that Requires them. I'm ready to try to help you as much as I Can. On the other hand it Would be a waste of time Porting These Scripts To An XPE Plugin if they Already have tested working solutions With PESE, XPE, GENA projects.
BUT... If you are trying to port these scrips to XPE "Just to learn how to do it." You can ask anything you want... (If Worty) ---I'll do my best. And I'm not the only one listening here.
...First, Verify the minimal Version of powerShell You need. Add only that to you build. If it's "Core", Core is not added to PATH Environment at Build you will have to use fully qualified commands for your tests or install your scripts to PowerShell-Core directory.
Then Confirm what scripts are usable under PE... Make a package of all these scripts (.zip/.7z) After that create an XPE Packed Application out of it... Type anything in exe box... It won't create shortcut anyway. It will Give you a Base Plugin to install ALL your Scripts to your XPE...
In your booted XPE. Go to your Scripts installation directory Run a PowerShell Prompt and You will be able to test everything you need to use.
If The Results seems worthy of "Uses" You can escalate your plugin to complete integration. Ex: "BSOD Team Scrips Start Menu Item" That opens a PS Prompts in your scrips folder, Another link that Opens a Quick Start help, Add PowerShell Core to Path Env if needed. Etc...
It's quite Addictive once you get a hold of it :)