You can develop PowerShell scripts on your workstation and run and test them there too... But sometimes... That's not what you want. You could break your workstation with PowerShell code, and your workstation is not clean with all features installed, or settings enabled that your target systems don't. And that's where Visual Studio Code and its Remote SSH extension come into play. This blog post will show you how to combine that with a Windows Sandbox instance.
This week the annual Dutch Experts Live meeting was there again in Den Bosch, I was there together with some of my colleagues from NEXXT, and this is my impression of the event 🙂
Testing things is always essential, and Windows has a nice built-in Feature for that which is called Windows Sandbox. You can look at this as a throwaway Windows VM, you start and use it, and afterward, there's no trace of it anymore, making it ideal for testing! In this blog post, I will show you how to test PowerShell scripts and Intune packages in Windows Sandbox.
I use Windows Sandbox a lot for testing Endpoint Manager packages or software. Sometimes you want to start it with specific options (Connect a folder on your hard drive or start without a network connection). You must create a custom configuration file (.wsb) with those options. This blog post shows you how to start Windows Sandbox using PowerShell with parameters without creating multiple configuration files.