dev-setup

Scripts and utilities for setting up a dev machine running Windows.

Setup

Pre-requisites

The only thing you need is the contents of this repo down to your local machine.

If you already have git installed then you can just clone the repo:

git clone https://github.com/swellaby/dev-setup-windows.git

If not, then you can download a zip of the repo contents from the default main branch at: https://github.com/swellaby/dev-setup-windows/archive/main.zip

(note you can also use the GitHub UI if you prefer by going to https://github.com/swellaby/dev-setup-windows/ and then clicking the Code button and then Download ZIP).

Be sure to extract the archive if you downloaded the zip file.

Prepare

Using a PowerShell terminal with admin/elevated permissions, navigate to the root directory containing the repository contents.

PowerShell Execution Policy

Ensure that the Windows PowerShell execution policy is configured to allow for scripts to be executed (the default values on Windows client OS prevent running any scripts). Setting the policy to RemoteSigned should suffice.

Set-ExecutionPolicy RemoteSigned

Unblock Entry Script File

Since the script file was downloaded, make sure it is unblocked so that Windows will allow it to be executed:

Unblock-File -Path .\SetupWindows.ps1

Firewall/Proxy

If you are on a machine behind a firewall or corporate proxy, make sure you configure the relevant proxy environment variables from the same PowerShell session before running the script.

You may want to utilize both setx and set due to the nature of how the script executes

setx no_proxy ...
setx http_proxy ...
setx https_proxy ...
set no_proxy=...
set http_proxy=...
set https_proxy=...

Usage

Be sure to use an admin/elevated session to run the script

With all default parameters:

.\SetupWindows.ps1

Parameters

The script supports many parameters to allow you to control what is, and what is not, installed and configured on your system. To run the script with a non-default value, just include it in your script execution.

For example if you wanted to install legacy Python 2.x install and wanted the Enterprise edition of Visual Studio instead of Community:

.\SetupWindows.ps1 -IncludePython2x $True -InstallVSEnterpriseVersion $True