Remove tp5

README.md

@@ -21,8 +21,8 @@ Some of my enhancements are:
 The following Windows versions are known to work (built with VMware Fusion Pro 8.1.1):
 
  * Windows 10
- * Windows Server 2016 TP5
- * Windows Server 2016 TP5 with Hyper-V and Docker -> see [docker-windows-box](https://github.com/StefanScherer/docker-windows-box) for an use case
+ * Windows Server 2016
+ * Windows Server 2016 with Hyper-V and Docker -> see [docker-windows-box](https://github.com/StefanScherer/docker-windows-box) for an use case
 
 You may find other packer template files, but older versions of Windows doesn't work so nice with a Retina display.
 
@@ -45,7 +45,7 @@ If you have already downloaded the ISOs or would like to override them, set thes
 - iso_checksum - md5sum of existing ISO (if different)
 
 ```
-packer build -var 'iso_url=./server2016tp5.iso' .\windows_2016.json
+packer build -var 'iso_url=./server2016.iso' .\windows_2016.json
 ```
 
 ### Windows Updates
@@ -103,7 +103,7 @@ Be sure to set hyperv_switchname to an external Hyper-V switch.
 
 I have the ISO already downloaded to save time, and only have Hyper-V installed on my laptop, so I run:
 ```
-packer build --only hyperv-iso -var 'hyperv_switchname=Ethernet' -var 'iso_url=./server2016tp5.iso' .\windows_2016_docker.json
+packer build --only hyperv-iso -var 'hyperv_switchname=Ethernet' -var 'iso_url=./server2016.iso' .\windows_2016_docker.json
 ```
 
 You then can use this box with Vagrant to spin up a Hyper-V VM. Vagrant currently
@@ -119,13 +119,13 @@ WinRM to communicate with the box.
 Vagrant 1.8.4 does need some workarounds though:
 - There is a bug in get_vm_status.ps1
 - winrm-fs needs an update as well
-See: https://github.com/PatrickLang/packer-windows/issues/1#issuecomment-230151622 
+See: https://github.com/PatrickLang/packer-windows/issues/1#issuecomment-230151622
 These are fixed in 1.8.5, so upgrading is easiest.
 
 Example Steps for Hyper-V:
 ```
-vagrant box add windows_2016_tp5_docker windows_2016_docker_hyperv.box
-vagrant init windows_2016_tp5_docker
+vagrant box add windows_2016_docker windows_2016_docker_hyperv.box
+vagrant init windows_2016_docker
 vagrant up --provider hyperv
 ```
 

hyperv/README.md

@@ -25,7 +25,7 @@ vagrant up --provider vmware_fusion
 ```
 
 ## In the Windows 10 VM
-### Build the Windows Server 2016 TP5 Hyper-V base box
+### Build the Windows Server 2016 Hyper-V base box
 
 Now inside the Windows 10 VM create a Hyper-V external switch and then run
 packer with this command
@@ -41,7 +41,7 @@ on a shared folder of the host.
 ### Run the Hyper-V VM in Windows 10
 
 ```powershell
-vagrant box add windows_2016_tp5_docker windows_2016_docker_hyperv.box
+vagrant box add windows_2016_docker windows_2016_docker_hyperv.box
 cd C:\Users\vagrant
 git clone https://github.com/StefanScherer/docker-windows-box
 cd docker-windows-box

windows_2016.json

 {
   "builders": [
     {
-      "vm_name":"WindowsServer2016TP5",
+      "vm_name":"WindowsServer2016",
       "type": "hyperv-iso",
       "disk_size": 41440,
       "boot_wait": "0s",

windows_2016_core.json

 {
   "builders": [
     {
-      "vm_name":"WindowsServer2016TP5Core",
+      "vm_name":"WindowsServer2016Core",
       "type": "hyperv-iso",
       "disk_size": 41440,
       "boot_wait": "0s",

windows_2016_docker.json

 {
   "builders": [
     {
-      "vm_name":"WindowsServer2016TP5Docker",
+      "vm_name":"WindowsServer2016Docker",
       "type": "hyperv-iso",
       "disk_size": 41440,
       "boot_wait": "0s",
@@ -31,7 +31,7 @@
       "enable_virtualization_extensions":true
     },
     {
-      "vm_name":"WindowsServer2016TP5Docker",
+      "vm_name":"WindowsServer2016Docker",
       "type": "vmware-iso",
       "communicator": "winrm",
       "iso_url": "{{user `iso_url`}}",
@@ -67,7 +67,7 @@
       }
     },
     {
-      "vm_name":"WindowsServer2016TP5Docker",
+      "vm_name":"WindowsServer2016Docker",
       "type": "virtualbox-iso",
       "communicator": "winrm",
       "iso_url": "{{user `iso_url`}}",