This Vagrantfile helps to setup and provision the Virtual Machine "Windows 10 with Legacy Microsoft Edge and Internet Explorer 11" provided by Microsoft for usage with Vagrant.

Only VirtualBox and Vagrant are required. On macOS, these dependencies can be installed using Homebrew:

$ brew install --cask virtualbox
$ brew install --cask vagrant

For managing your Vagrant virtual machines, I can recommend the use of Vagrant-Manager, a small utility app for the menu bar.

$ brew install --cask vagrant-manager

The Vagrant Box from Microsoft, which provides "Windows 10 with Legacy Microsoft Edge and Internet Explorer 11", has to be downloaded and added into your local Vagrant installation under the name MSEdge. This process can be automated with the script prepare.sh:

$ # in case jq isn't installed yet:
$ brew install jq
$ ./prepare.sh

Some parts of the provisioning process can be configured. To make this possible a file config.ps1 is expected. If it doesn't exist, prepare.sh will create one based on config.dist.ps1.

To build the virtual machine based on the above Vagrant Box and your configuration, you only need to execute

$ vagrant up

This will create the virtual machine, updates the VirtualBox guest tools and applies the provisioning. This can take some time, please wait until the command is finished before using the VM. When the VM is ready, it has been rebooted and the user IEUser is logged on automatically.

The VM uses an account with username IEUser and password Passw0rd!. To access the VM, a remote desktop connection can be used as well:

$ vagrant rdp

The host (the computer running Vagrant) from the perspective of VM can be reached via the IP address 10.0.2.2 or the hostname vagrant-host (if not changed in config.ps1).

So if your local running web application is listening on *:8443, you can access it via https://10.0.2.2:8443 or https://vagrant-host:8443. If it is listening on localhost:8443, you first have to set up a reverse ssh tunnel, so you can access it via https://localhost:8443 from within the VM as well:

$ vagrant ssh -- -R8443:localhost:8443

If your application expects to be accessed via a custom host name, modifiy $hostsFile in config.ps1 accordingly.

The VM can be unusable for a significant amount of time due to the search and installation for updates. Therefore, the automatic update feature of Windows Update can be disabled in the configuration of the provisioning.

If you do so, I strongly recommend to manually initiate the installation of the updates when you do not need the VM but as soon as possible.

If you need another Windows display language than the preinstalled "English (United States)", you have to install the corresponding language pack by your own via the Settings app.