Create a Metro design MDT Progress Bar Part 2

In this post I will show you a Progress Bar with Windows 10 design that I have done to replace the existing MDT progress bar. This progress bar looks like to this one from Windows 10, for updates or upgrade.
In my previous post I shared a first metro design progress bar., see here. Both of them use MDT variables mentioned in my article here.

Create a Metro design MDT Progress Bar Part 1

In this post I will show you a Metro design Progress Bar I have done to replace the existing MDT progress bar. I will show you two kinds of Progress Bar.
In a previous post I explained how to use native MDT variables, to control the progress bar current step name and number, and also the total step number.

Run a Post Configuration Task Sequence once MDT deployment is completed

In this post, I will show you a way to add a Post Configuration Task Sequence once your deployment is completed successfully. It will allow you for instance, to configure the computer name, create a user, choose applications to install from your deployment Share after the deployment.

PowerShell WPF & GUI Facebook group

Few days ago I decided to create the PowerShell GUI & WPF Facebook Group. 
Link, here.

Why this group ?
If you read my posts, I often publish something about PowerShell GUI, or tools with GUI.
Many people asked me, for instance, how to proceed to create Metro design GUI or how to use it with PowerShell.
That's why I decided to create a Group about this subject.  

Who can access to this group ?
This group is for everyone, who want to talk, learn or share something about PowerShell WPF GUI.

Who can publish on this Group ?
Everyone of course !!!
If you have a question ask it on the group and community will try to help you.
If you work on a project and need help, ask for it.
If you have done a cool project and you want to share it with others, you are welcome.
If you have some cool tips & tricks don't hesitate to share with others. 

Fake Windows 10 in PowerShell, WPF and MahApps

In this post, I will share a WPF GUI I have done.
Goal is to show you how powerfull is the combo: WPF + MahApps + PowerShell.
This GUI is not a real Windows 10 computer but a GUI I have done entirely with WPF and WPF.

PS1 To Exe Generator - New version

In this post, I will show you the new version of my tool PS1 To EXE generator that allows you to generate an EXE file from a PowerShell project, choose the main ps1 and inlude other files and folders.
Link to the first version: Here

In this new versions, there is some new features:
- New design
- Possibility to require or not admin rights for your EXE
- Possibility to set a password 
- Possibility to add paramaters to your PS1 script
- Check WinRAR informations

How to get the tool?

What's new ?

New design
New design
The tool is now composed of two parts.
The first one, is the same than in the first version.
The second part is new. This part called WinRAR infos allows you to check if WinRAR is installed and which version is used (x86 or x64).

WinRAR test

If WinRAR is installed, you will get the below WinRAR infos:
WinRAR is installed
If WinRAR isn't installed, you will get the below WinRAR infos and this part will be first opened.
WinRAR isn't installed
Admin rights

In the EXE configuration part, the Requires admin rights CheckBox allows you to ask or not admin rights after running the EXE. 
Admin rights CheckBox
If the Requires admin rights has been checked the EXE file will be as below:
Requires admin rights 
If not, it will be as below
Not requires admin rights 

Set a Password 

This function allows you to ask for a password after running the EXE.
Click on the button below
This will open the Flyout below
More options Flyout
Check the Set a password CheckBox to enable the password part as below
Password field
Type your password and close the Flyout.

Now when you run your EXE, you will have to type your password as below
Ask for password
If a bad password is typed, you will get the below message
Bad password

Add parameters

Click on the More options button
In the Add parameters to your PS1 TextBox, type the parameters to add. Don't forget to type with "-"
Add parameters option

How to use it ?

The first step is to selected your PowerShell project. This project should be a folder that contain your PS1 file and all associated files and folder.
For instance, in the following example, my project is the folder below, that contains all these items.
My Project folder
Click on the Browse button from the Content sources part, and select the folder containing your project, in my case it's the folder MyApplication.
Content sources part
Browse project
In the EXE name part, type the name of the EXE you will create.
In the PS1 name, choose the main PS file that will be run after running the EXE file. 
In my case it will be the PS1 MyAppli.ps1
EXE infos part
As mentioned above, check the Requires admin rights CheckBox, to ask for admin rights after running the EXE file.

The icon part allows you to add an icon to your EXE file. Click on the Browse button and select you .ico file.
Choose an icon
To finish, click on the Build the EXE button to create your EXE.
Once it's done the below message appears and your EXE file will be created in your Desktop.
Success message

How to use the Customsettings.ini file like an installation profile ?

In this I will show you, how to use the Customsettings.ini like a profile for your master installation. 

Why a profile ?

This way you can create multiple INI file with different names, for insta,nce one with domain integration, one with workgroup integration, one with DHCP, one for a specific branch of your company...
Once, before starting the deployment, you just have to select the profile you want and all parameters will be set automatically.

How it works ?

Create your profiles

The first step is to create INI file. You can find a tool I created, MDT Profile Generator, that allows you to generate INI profile.

In my following example, I will create one INI profile with below configuration:
- Name: French and Domain
- Domain integration
- DHCP mode
- Language: French
- Computer name: TEST1

My second INI profile will have the configuration below:
- Name: French-StaticIP-Workgroup
- Workgroup integration
- Static IP configuration
- Language: French
- Computer name: TEST2

The third will have the configuration below:
- Name: German and Domain
- Domain integration
- DHCP mode
- Language: Spanish
- Computer name: TEST3

The latest one:
- Name: German and Workgroup
- Workgroup integration
- DHCP mode
- Language: Spanish
- Computer name: TEST4

So, now I have four Customsettings.ini with different names.
The next step is to allow MDT to let your choose which Customsettings.ini to apply.
Indeed, by default MDT will use only INI file with name Customsettings.ini, and you can't use multiple.

Create your wizard

To do that I have created a really simple MDT wizard that allows you to choose an external INI profile, see here my post about it.
The first step is to copy all your INI files in a folder INI_Profiles that should be located in the Deploy folder.
Then integrate the new wizard in your MDT deployment.
Selection profile wizard

Select your profile

The last step, is to run a deployment and select your profile :-).
The below example shows you my selection wizard that displays all my INI profile files mentioned previously.
Selection profile Wizard
Once you choose one of them, all configuration is automatically setted.