<div>
This is a complex topic I'm afraid. To be honest, every time I've done this I've ended up shifting to C#. PowerShell is not the best language for creating user interfaces. 
 
You might consider using ShowUI, it significantly simplifies the job of building the GUI: 
 
<a href="http://www.show-ui.com/" rel="ugc">http://www.show-ui.com/</a> 
 
If you do, you will also have to distribute the ShowUI to helpdesk staff.
</div>

<div>
i hope this below will help 
 
<a href="https://blogs.technet.microsoft.com/csps/2011/12/07/creating-your-own-gui-application/" rel="ugc">https://blogs.technet.microsoft.com/csps/2011/12/07/creating-your-own-gui-application/</a>
</div>

<div>
Fairly straight forward. You can also use Visual Studio to design GUI and just use it in Powershell with a couple of tweaks 
 

<pre><code class="code-10 nolinks" id="code-20-42076509-1">function Load-Form {
 $Form.Controls.Add($Button1)
 $Form.Controls.Add($Label)
 $Form.Add_Shown({$Form.Activate()})
	[void]$Form.ShowDialog()
}

Function ButtonWasClicked{

}

# Form
$Form = New-Object System.Windows.Forms.Form 
$Form.Size = New-Object System.Drawing.Size(900,450) 
$Form.MinimumSize = New-Object System.Drawing.Size(900,450)
$Form.MaximumSize = New-Object System.Drawing.Size(900,450)
$Form.SizeGripStyle = &quot;Hide&quot;
$Form.Icon = [System.Drawing.Icon]::ExtractAssociatedIcon($PSHome + &quot;\powershell.exe&quot;)
$Form.Text = &quot;Title&quot;
$Form.ControlBox = $true
$Form.TopMost = $true

#Draw buttons 
$Button1 = new-object System.Windows.Forms.Button
$Button1.Location = new-object System.Drawing.Size(60,370)
$Button1.Size = new-object System.Drawing.Size(90,25)
$Button1.Text = &quot;Click here...&quot;
$Button1.Add_Click({ButtonWasClicked})
$Button1.Visible = $True
$Button1.Enabled = $False
$Label = New-Object System.Windows.Forms.Label
$Label.Text = &quot;&quot;
$Label.AutoSize = $True
$Label.Location = new-object System.Drawing.Size(160,375)

# Load form
Load-Form
</code></pre>
</div>

<div>
Sapien makes a good GUI IDE for Powershell scripts.
</div>

<div>
I thought Sapien discontinued primal forms? Certainly not kicking around much any more. 
 
I think I should clarify this statement: 
 
&gt;&nbsp;This is a complex topic I'm afraid. 
 
Designing the initial front end with a few buttons is easy. Wiring up the back end, so you can execute things, get information back, properly handle errors and exceptions, present information, act on it, all of this takes a lot of time. This is especially true when you're dealing with longer running tasks that must trigger a change in a UI-thread when they're done (without completely locking up the GUI for the duration). 
 
I will hold fast to my opinion that PowerShell is not a good language for developing GUIs. You can... but outside of very, very simple utilities it becomes quite a drag. 
 
ShowUI goes a long way to mitigating this lack by providing a background jobs interface, my last project couldn't use that because it auto-builds itself on first import and every import was a first in the environment in question.
</div>

<div>
<a href="https://www.sapien.com/software/powershell_studio" rel="ugc">https://www.sapien.com/software/powershell_studio</a> 
 
still lists GUI Designer as a prominent feature.
</div>

<div>
I won't pay $389 for something I can do in Community VS/Notepad++ though
</div>

<div>
A decent example of a Powershell UI via forms in this solution to a prior problem, hope it's helpful. 
 
<a href="https://www.experts-exchange.com/questions/28982303/Help-to-convert-powershell-script-into-a-gui.html?anchorAnswerId=41884032#a41884032" rel="ugc">https://www.experts-exchange.com/questions/28982303/Help-to-convert-powershell-script-into-a-gui.html?anchorAnswerId=41884032#a41884032</a> 
 
~bp
</div>

<div>
PrimalForms was free way back when. It was all Forms though. Being able to &quot;draw&quot; most of the GUI in a XAML document is quite an advantage (over dynamically generating every single control) with WPF. 
 
As Shaun says, VS community is free and it has a forms designer. It could be used to build up the main GUI part. 
 
Beyond that I think you should break this problem down. If you must have a GUI, what should the minimum viable product include? 
 
If you take this part as an example: 
 
&gt;&nbsp;The GUI will grab information, example - &nbsp;mailbox sizes greater than 5 gb 
 
This means you need to execute some PowerShell, and you need to display the results. 
 
How should that be displayed? In a list? 
 
&gt;&nbsp;The GUI will have a button to migrate the mailbox 
 
This control will have to be dynamically generated. 
 
Where will the button appear? How will it be generated? What, exactly, will it do?
</div>

<div>
I am using wpf to build the gui, what are your thoughts? is there a better way??
</div>

<div>
<div class="content wysiwyg-content">
HI All, 
 
I need to produce GUI's for our helpdesk, what is the best way of doing this. The GUI will grab information, example - &nbsp;mailbox sizes greater than 5 gb and then the GUI will have a button to migrate the mailbox. &nbsp; 
 
thank you in advance, 
Kay
</div>
</div>

HI All, 

I need to produce GUI's for our helpdesk, what is the best way of doing this. The GUI will grab information, example -  mailbox sizes greater than 5 gb and then the GUI will have a button to migrate the mailbox.  

thank you in advance, 
Kay

Powershell GUI

Windows PowerShell is a task automation and configuration management framework from Microsoft, consisting of a command-line shell and associated scripting language built on the .NET Framework. PowerShell provides full access to the Component Object Model (COM) and Windows Management Instrumentation (WMI), enabling administrators to perform administrative tasks on both local and remote Windows systems as well as WS-Management and Common Information Model (CIM) enabling management of remote Linux systems and network devices.

Powershell

A scripting language is a programming language that supports scripts, programs written for a special run-time environment that automate the execution of tasks that could alternatively be executed one-by-one by a human operator. Scripting languages are often interpreted (rather than compiled). Primitives are usually the elementary tasks or API calls, and the language allows them to be combined into more complex programs. Environments that can be automated through scripting include software applications, web pages within a web browser, the shells of operating systems (OS), embedded systems, as well as numerous games. A scripting language can be viewed as a domain-specific language for a particular environment; in the case of scripting an application, this is also known as an extension language.