In this post I will show you the new versin of my tool Windows Sandbox Editor (old nam Sandbox Configurattion Manager) that allows you to create and edit your Sandbox configuration files. You will be able to generate Sandbox to run different kind of files like PS1, VBS, EXE, msi.
In this post I will demonstrate how to enable the Windows Sandbox feature through SCCM and PowerShell and allow standard users to use it. What is Windows Sandbox ? Windows Sandbox is a new feature that allows you to run a virtualized environment from your Windows host computer. You will be able for instance to execute a specific application on an isolated environment. Windows Sandbox uses hardware virtualization to create this isolated environment. You won't need to install a VM to use it. Indeed it will use OS from your host computer. You will be able to run it from the Start menu or create a WSB shortcut to run a sandbox with a specific configuration. Enable execution for standard user In my last post I explained how to allow standard user to run Windows Sandbox. For that you will need to add the user to the Hype-V Admin group, below. See below how to add the current user in this group through SCCM: The PS1 script The below script will be used to do the below actions: - Check if Windows Sandbox is already installed or not - Enable the Sandbox feature is needed - Add the current user in the Hyper-V admin group See below the full script. It will be used in the SCCM application, copy it to you SCCM server for later. Create the application 1 / In your SCCM console, go to Software Library then Applications 2 / Click on Create Application 3 / Select Manually specify the application information
4 / Type a name and choose what you want
5 / Choose what you want, like an icon
6 / Click on the Add button
7 / Choose Script installer
8 / Type a name
9 / In the content location, browse to the folder path that contains the PS1
10 / In the Installation program, select the PS1 file
11 / Click on Add clause
12 / In the direction Rule choose File
13 / In the path field type %Windir%\System32\ 14 / In the file or folder type WindowsSandbox.exe
15 / The direction rule will be as below
16 / Choose how you want to run the application
17 / In the Requirements part click on Next
18 / In the Software dependencies part, click on Next
19 / Click on Next 20 / Click on Close 21 / Click on Next 22 / Click on Next 23 / Click on Close
Create the collection 1 / In your SCCM console, go to Assets and Compliance 2 / Do a right click on Device collections then Create device collection 3 / Type a collection name and choose a limit collection
4 / Click on Add Rule
5 / Select Direct Rule 6 / Click on Next 7 / In the Resources class use System Resource 8 / In the Attribute name choose Operating System Build 9 / In the Value part type the build version of the 1903, %18362%
10 / Click on Select All
11 / Click on Next then Close 12 / Click on Next 13 / Click on Next then Close Deploy the Sandbox feature 1 / Go to Software Libray 2 / Do a right-click on the application 2 / Click on Deploy 3 / In the Collection part, browse to the Sandbox collection
4 / Click on Next 5 / Click on Add and select your DP
6 / Choose what you want and click on Next
7 / Click on Next
8 / Click on Next
9 / Click on Next 10 / Click on Close
Install through Software Center 1 / Open the Software Center 2 / The application appears in the Software Center
3 / Click on Install
Check installation 1 / Go to C:\Windows\Debug 2 / Open the file Install_Sandbox_Feature.log
3 / Check in the Hyper-V admin group 4 / Restart the computer 5 / Run Windows Sandbox Add requirements In this part we will add some requirements to the application. 1 / For that do a right-click on your application 2 / Click on Properties 3 / Go to Deployment Types 4 / Click on the appli and Edit
5 / Click on Requirements then Add
Computer should have at least 4GB of RAM 6 / Select Total physical memory 7 / Type the RAM to set and then OK
Operating System should be at least 1903 8 / Click on Add 9 / Select Custom then click on Create
10 / Create the custom rule as below then click on OK
11 / Select the new custom rule 12 / Type the 1903 version in the Value part: 18362
In this post I will share with you a solution, called Run in Sandbox, I developed that allows you to run directly a PS1, VBS, msi or EXE from a context menu, after doing a right-click on the file.
In this post I will show you how to change the main theme and accent from a PowerShell and WPF application with MahApps directly from a button in the GUI.
In this post, I will show you a short sample to create easily your prerequisites part in a GUI. Sometimes it could be useful to have a prerequisites part to check some parameters before clicking on a button and starting a process.
