# Powershell

### Basics <a href="#basics" id="basics"></a>

So a command in PowerShell is called **cmdlet**. To get help on how to use a **cmdlet** while in PowerShell, the man-page, you do:

```
Get-Help    <cmdlet    name    |    topic    name>
```

Example

```
get-help echo
get-help get-command
```



### Variables <a href="#variables" id="variables"></a>

Variables are declared like this

```
$test = "something"
```

### Execute scripts <a href="#execute-scripts" id="execute-scripts"></a>

So for security reasons the default policy for executing scripts is **Restricted**. Here are the different script-policies.

**Restricted**: PowerShell won't run any scripts. This is PowerShell's default execution policy.

**AllSigned**: PowerShell will only run scripts that are signed with a digital signature. If you run a script signed by a publisher PowerShell hasn't seen before, PowerShell will ask whether you trust the script's publisher.

**RemoteSigned**: PowerShell won't run scripts downloaded from the Internet unless they have a digital signature, but scripts not downloaded from the Internet will run without prompting. If a script has a digital signature, PowerShell will prompt you before it runs a script from a publisher it hasn't seen before.

**Unrestricted**: PowerShell ignores digital signatures but will still prompt you before running a script downloaded from the Internet.

Source: [http://windowsitpro.com/powershell/running-powershell-scripts-easy-1-2-3](http://windowsitpro.com/powershell/running-powershell-scripts-easy-1-2-3)

So if we want to run script `myscript.ps1` we have to set the execution-policy. First let's check what execution-policy we currently have:

```
Get-ExecutionPolicy
```

Then we can set the execution policy like this

```
set-ExecutionPolicy unrestricted
```
