anchor.diff:  === 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.
   
  -**UPDATE:** the issue has been resolved in VirtualBox 5.1.18.  The `/vagrant` folder is now mounted as usual.
  +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.
  
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: Sometimes networks fail or mirror sites go down. If you experience a failure, you can attempt to resume the construction by issuing `vagrant provision` at the command line.  Vagrant will attempt to start over, but will skip any provisions that have already taken place.
  
  === Cannot Acquire Repository Lock
  TIP: we've altered some of the installation logic to perform the retry logic described below automatically so you probably don't have to worry about this scenario any longer.
  
  One of the first steps is to update the APT repositories via `apt-get update` which every once in a while can fail. What appears to happen in those cases is that the Ubuntu GUI has already acquired the lock and is running the update on its own.  The solution is to wait a bit and then reset the environment so that provisioning can continue.  This issue will manifest in "Ansible is not installed" errors.
  
  