anchor.diff:  * https://www.vagrantup.com/[Vagrant] installed and working
   * https://www.virtualbox.org/[VirtualBox] installed and working
   * https://www.virtualbox.org/wiki/Downloads[VirtualBox Extension Pack] installed into VirtualBox
  -* **https://en.wikipedia.org/wiki/X86_virtualization[Virtualization support] enabled in your BIOS**
  +* https://en.wikipedia.org/wiki/X86_virtualization[Virtualization support] enabled in your BIOS
   * a working internet connection
   * Your corporate VPN running (if you want to apply some work-specific plays)
   
   IMPORTANT: if you don't enable virtualization support in your BIOS, VirtualBox will not run correctly.
  +IMPORTANT: if you don't install the extension pack, the virtual machine won't come up, complaining about USB errors.
   
   == Building
  -All the components of the environment live in repositories on the internet so there is nothing to build. **UPDATE:** some people have experienced issues when rebuilding a box due to flaky networks, online assets moving to different locations or installation processes changing.  When you need your box, you need your box and you don't have the time to troubleshoot an installation issue.  To combat this problem, we've decided to change the build model and bake in much of the software into the base image.  The trade-off we've made to ensure quick and stable rebuilds is a larger initial download.  All boxes are currently housed in https://app.vagrantup.com/kurron[HashiCorp's Vagrant Cloud] repository.
  +All the components of the environment live in repositories on the internet so there is nothing to build.
  +
  +TIP: some people have experienced issues when rebuilding a box due to flaky networks, online assets moving to different locations or installation processes changing.  When you need your box, you need your box and you don't have the time to troubleshoot an installation issue.  To combat this problem, we've decided to change the build model and bake in much of the software into the base image.  The trade-off we've made to ensure quick and stable rebuilds is a larger initial download.  All boxes are currently housed in https://app.vagrantup.com/kurron[HashiCorp's Vagrant Cloud] repository.
   
   == Installation
   Use Git to clone this project, go into the project folder and type `vagrant up` and go get a cup of coffee.  The construction time of the box greatly depends on your internet speeds.
  
positive.code: 1. `vagrant provision` should resume the provisioning of the box
  
  === My Git settings are all wrong!
  You need to specify a custom Git configuration file.  The best way to do that is to create and apply your own customizations. See the *Applying Your Own Customizations* section above on how to do that.  You can use https://github.com/kurron/ansible-pull-desktop-tweaks[kurron/ansible-pull-desktop-tweaks.git] as inspiration. **Do not blindly copy the customizations as they are specific to a particular person.**
  
  === I lost power and now VPN isn't working!
  >I guess this is just an FYI to anybody who might have also had this problem, but if you are using the VPN on the guest boxes, it will edit your `resolv.conf` file to only use TLs nameservers.  If you lose power, these will remain in this state and you will lose DNS the next time you start the machine (seeing that you no longer have a VPN session).  I found just starting and stopping the scripts in `~/VPN` would restore the `resolv.conf` back to normal.
  
  === I'm running Windows 7 and Vagrant hangs!
  You need to install a current version of [Windows Management Framework](https://www.microsoft.com/en-us/download/details.aspx?id=40855) and then reboot your machine.  Apparently, there is a compatibility issue older PowerShell and newer Vagrant versions.
  
  == Change History
  
  
negative.code: === Where did `/vagrant` go?
  There is http://stackoverflow.com/questions/42074246/vagrant-error-unable-to-mount-virtualbox-shared-folders-guest-additions-vboxs[an issue with Windows 10 and VirtualBox 5.1.16] that prevents Vagrant from starting properly.  As a workaround, we've disabled sharing of folders.  Non-Windows users can edit the `vagrantfile` and re-enable the mount if desired.
  
  TIP: the issue has been resolved in VirtualBox 5.1.18.  The `/vagrant` folder is now mounted as usual.
  
  === Vagrant Asks Me Which Network Interface To Bind To
  By default, the box is configured to join the local network as a fully accessible machine. The `desktop.vm.network "public_network"` in the `vagrantfile` is the key to this.  If you have multiple networks available on your machine, running a VPN for example, Vagrant needs to know which network you want to put your Vagrant box onto and will wait until you give it guidance.
  