When ever you want to automate some mundane work or setup steps on your Windows computer the word PowerShell seems to be starting to pop up. But before the fun even can begin one will hit a wall pretty quickly.


Get scripting enabled

So how do we get scripts enabled? On the Technet site you will find a long list of possible options on what levels can be set to:

  • Restricted: Default execution policy, does not run scripts, interactive commands only. This is what the default setup is on Windows 8.1, Windows 8 and even good old Windows 7.
  • All Signed: Runs scripts; all scripts and configuration files must be signed by a publisher that you trust; opens you to the risk of running signed (but malicious) scripts, after confirming that you trust the publisher.
  • Remote Signed: Local scripts run without signature. Any downloaded scripts need a digital signature, even an UNC path.
  • Unrestricted: Runs scripts; all scripts and configuration files downloaded from communication applications such as Microsoft Outlook, Internet Explorer, Outlook Express and Windows Messenger run after confirming that you understand the file originated from the Internet; no digital signature is required; opens you to the risk of running unsigned, malicious scripts downloaded from these applications

This list was originally taken from HowTo-Geek on 31. December 2014.

For now I'll go with the Remote Signed level. As I'm not planning on downloading any scripts from the web or using scripts from a network share. If you do intend to use any scripts from the web or any network share that are not signed you might want to use the Unrestricted level. So enough talk lets change the level, open a PowerShell with administrative rights and run the command:

Set-ExecutionPolicy RemoteSigned


Now you should be able to start writing the little helpers for your system with the help of PowerShell.




These 14 steps show in great detail how you can add a printer that is connected to your Airport Extreme Router and print via your Network or even wirelessly if you happen to use WiFi from you Windows Device.

  1. Push the Windows-Key and W to enter Devices and Printers and push enter to open
  2. Select Add a Printer
  3. Don’t bother waiting until the scan has finished and just select next
  4. Select the Add a local printer option – lets not get into a discussion about bad naming.. Let’s just get the printer setup and working
  5. Click Create a new port, then select Standard TCP/IP Port from the drop-down list and finally click Next
  6. Fill in the Hostname or IP address with the address of your Airport Extreme router.
    1. By default it should be
    2. If default fails push Windows-Key and S, enter cmd, as soon as the command line has opened enter ipconfig. The IP next to the Default Gateway will be your Routers IP.
  7. Leave Port name at whatever it fills in, uncheck Query the printer and automatically select the driver to use, and click Next.
  8. The wizard will say it’s Detecting the TCP/IP port. It should find the device. If not, you probably entered the wrong IP address. Check it and try again. If it still fails to detect it, don’t worry about it and continue anyway.
  9. Select your printer manufacturer in the dropdown e.g. Samsung Printer. Click Next.
  10. Select your printer’s Manufacturer from the list, then select your specific printer from the Printers list, then click Next. If your printer isn’t there, you’ll have to download a driver and use the Have Disk… option.
  11. Leave the option Use the driver that is currently installed (recommended) and just click Next.
  12. Fill in a Printer name, or leave the name it fills in for you alone. Click Next.
  13. Decide whether to share the printer or not. Since other devices on your network can print directly to the Airport Extreme, why bother to share it? I selected Do not share this printer and clicked Next.
  14. Decide whether to Set as the default printer, and try to Print a test page, then click Finish.

This worked on all my Windows 8.x machines even RT. This blog post leans very heavily on the Blogpost from Charles Engelke, whom originally wrote the insturctions for Windows 7.