macOS, Vagrant, VirtualBox, shell provider powershell bug?

classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

macOS, Vagrant, VirtualBox, shell provider powershell bug?

Bob Tanner
Not sure if this is a bug or a personal problem, posting here before opening a bug report.

macOS 10.12.6
Vagrant 2.0.0
VirtualBox 5.1.30 r118389
Windows Server 2016 Standard Edition

Unfortunately I upgraded Vagrant and VirtualBox at the same time so I don't know which one is causing the problem.

Using the Vagrant configuration from the https://github.com/chocolatey/chocolatey-test-environment project

$ vagrant  up
==> default: Checking if box 'BasicTheProgram/windows_2016' is up to date...
==> default: Running provisioner: shell...
    default: Running: shell/PrepareWindows.ps1 as c:\tmp\vagrant-shell.ps1
==> default: (10,8):UserId:
==> default: At line:72 char:1
==> default: + $folder.RegisterTaskDefinition($task_name, $task, 6, $username, $pass ...
==> default: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> default:     + CategoryInfo          : OperationStopped: (:) [], ArgumentException
==> default:     + FullyQualifiedErrorId : System.ArgumentException
==> default: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
==> default: At line:74 char:1
==> default: + $registered_task = $folder.GetTask("\$task_name")
==> default: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> default:     + CategoryInfo          : OperationStopped: (:) [], FileNotFoundException
==> default:     + FullyQualifiedErrorId : System.IO.FileNotFoundException
==> default: You cannot call a method on a null-valued expression.
==> default: At line:75 char:1
==> default: + $registered_task.Run($null) | Out-Null
==> default: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> default:     + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
==> default:     + FullyQualifiedErrorId : InvokeMethodOnNull

The shell/PrepareWindows.ps1 works when executed from an interactive powershell prompt inside the VM

# Adapted from http://stackoverflow.com/a/29571064/18475
$AdminKey = "HKLM:\SOFTWARE\Microsoft\Active Setup\Installed Components\{A509B1A7-37EF-4b3f-8CFC-4F3A74704073}"
$UserKey = "HKLM:\SOFTWARE\Microsoft\Active Setup\Installed Components\{A509B1A8-37EF-4b3f-8CFC-4F3A74704073}"
New-ItemProperty -Path $AdminKey -Name "IsInstalled" -Value 0 -Force | Out-Null
New-ItemProperty -Path $UserKey -Name "IsInstalled" -Value 0 -Force | Out-Null
Stop-Process -Name Explorer -Force
Write-Output "IE Enhanced Security Configuration (ESC) has been disabled."

# http://techrena.net/disable-ie-set-up-first-run-welcome-screen/
New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Internet Explorer\Main" -Name "DisableFirstRunCustomize" -Value 1 -PropertyType "DWord" -Force | Out-Null
Write-Output "IE first run welcome screen has been disabled."

Write-Output 'Setting Windows Update service to Manual startup type.'
Set-Service -Name wuauserv -StartupType Manual

#Set-ExecutionPolicy Unrestricted

Vagrantfile attached

# Vagrant File (Vagrantfile)
# http://docs.vagrantup.com/v2/vagrantfile/index.html

# Windows guests can't even be used with Vagrant versions less than 1.3.5.
Vagrant.require_version ">= 1.3.5"
if Vagrant::VERSION < '1.6.0'
  # Vagrant versions less than 1.6.x do not have a built-in way to
  # communicate with Windows guest images.For versions less than 1.6.x
  # the vagrant-windows plugin is required.
  Vagrant.require_plugin "vagrant-windows"
end

# http://docs.vagrantup.com/v2/vagrantfile/machine_settings.html
Vagrant.configure("2") do |config|
  # This setting will download the atlas box at
  # https://atlas.hashicorp.com/ferventcoder/boxes/win2012r2-x64-nocm
  config.vm.box = "BasicTheProgram/windows_2016"

  # http://docs.vagrantup.com/v2/providers/configuration.html
  # http://docs.vagrantup.com/v2/virtualbox/configuration.html
  config.vm.provider :virtualbox do |v, override|
    # Show the GUI
    v.gui = true
    # 4GB RAM
    v.customize ["modifyvm", :id, "--memory", "4096"]
    # 2 CPUs
    v.customize ["modifyvm", :id, "--cpus", "2"]
    # Video RAM is 32 MB
    v.customize ["modifyvm", :id, "--vram", 32]
    # For better DNS resolution
    v.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
    # No audio
    v.customize ["modifyvm", :id, "--audio", "none"]
    # Clipboard enabled
    v.customize ["modifyvm", :id, "--clipboard", "bidirectional"]
    v.customize ["modifyvm", :id, "--draganddrop", "hosttoguest"]
    # For performance
    v.customize ["modifyvm", :id, "--usb", "off"]
    # Huge performance gain here
    v.linked_clone = true if Vagrant::VERSION >= '1.8.0'
  end

  # https://www.vagrantup.com/docs/hyperv/configuration.html
  # https://technet.microsoft.com/en-us/library/dn798297(v=ws.11).aspx
  config.vm.provider :hyperv do |v, override|
    # 4GB RAM
    v.memory = 4096
    # 2 CPUs
    v.cpus = 2
    # The time in seconds to wait for the virtual machine to report an IP address
    v.ip_address_timeout = 130
    # Use differencing disk instead of cloning whole VHD
    v.differencing_disk = true
    v.vm_integration_services = {
      guest_service_interface: true,
      heartbeat: true,
      key_value_pair_exchange: true,
      shutdown: true,
      time_synchronization: true,
      vss: true
  }
  end

  # timeout of waiting for image to stop running - may be a deprecated setting
  config.windows.halt_timeout = 20
  # username/password for accessing the image
  config.winrm.username = "vagrant"
  config.winrm.password = "vagrant"
  # explicitly tell Vagrant the guest is Windows
  config.vm.guest = :windows

  if Vagrant::VERSION >= '1.6.0'
    # If we are on greater than v1.6.x, we are using the built-in version
    # of communicating with Windows. For versions less than 1.6 the
    # `vagrant-windows` plugin would need to be installed and uses monkey
    # patching to override the communicator.
    config.vm.communicator = "winrm"
  end

  # Synced folders - http://docs.vagrantup.com/v2/synced-folders/
  # A synced folder is a fancy term for shared folders - it takes a folder on
  # the host and shares it with the guest (vagrant) image. The entire folder
  # where the Vagrantfile is located is always shared as `c:\vagrant` (the
  # naming of this directory being `vagrant` is just a coincedence).
  # Share `packages` directory as `C:\packages`
  config.vm.synced_folder "packages", "/packages"
  config.vm.synced_folder "/Users/tanner/projects/", "/projects"

  #config.vm.synced_folder "temp", "/Users/vagrant/AppData/Local/Temp/chocolatey"
  # not recommended for sharing, it may have issues with `vagrant sandbox rollback`
  #config.vm.synced_folder "chocolatey", "/ProgramData/chocolatey"

  # Port forward WinRM / RDP
  # Vagrant 1.9.3 - if you run into Errno::EADDRNOTAVAIL (https://github.com/mitchellh/vagrant/issues/8395),
  #  add host_ip: "127.0.0.1" for it to work
  config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct: true #, host_ip: "127.0.0.1"
  config.vm.network :forwarded_port, guest: 3389, host: 3389, id: "rdp", auto_correct: true #, host_ip: "127.0.0.1"
  # Port forward SSH (ssh is forwarded by default in most versions of Vagrant,
  # but be sure). This is not necessary if you are not using SSH, but it doesn't
  # hurt anything to have it
  config.vm.network :forwarded_port, guest: 22, host: 2222, id: "ssh", auto_correct: true #, host_ip: "127.0.0.1"

  # Provisioners - http://docs.vagrantup.com/v2/provisioning/
  # In this specific vagrant usage, we are using the shell provisioner
  # http://docs.vagrantup.com/v2/provisioning/shell.html
  if Vagrant::VERSION < '1.8.0'
    config.vm.provision :shell, :path => "shell/PrepareWindows.ps1"
    config.vm.provision :shell, :path => "shell/InstallNet4.ps1"
    config.vm.provision :shell, :path => "shell/InstallChocolatey.ps1"
    config.vm.provision :shell, :path => "shell/NotifyGuiAppsOfEnvironmentChanges.ps1"
  else
    config.vm.provision :shell, :path => "shell/PrepareWindows.ps1", :powershell_elevated_interactive => true
    config.vm.provision :shell, :path => "shell/InstallNet4.ps1", :powershell_elevated_interactive => true
    config.vm.provision :shell, :path => "shell/InstallChocolatey.ps1", :powershell_elevated_interactive => true
    config.vm.provision :shell, :path => "shell/NotifyGuiAppsOfEnvironmentChanges.ps1", :powershell_elevated_interactive => true
    config.vm.provision :shell, :path => "shell/InstallToolchain.ps1", :powershell_elevated_interactive => true
  end

$packageTestScript = <<SCRIPT
setx.exe trigger 1  # run arbitrary win32 application so LASTEXITCODE is 0
$ErrorActionPreference = "Stop"
$env:PATH +=";$($env:SystemDrive)\\ProgramData\\chocolatey\\bin"
# https://github.com/chocolatey/choco/issues/512
$validExitCodes = @(0, 1605, 1614, 1641, 3010)

Write-Output "Testing package if a line is uncommented."
# THIS IS WHAT YOU CHANGE
# - uncomment one of the two and edit it appropriately
# - See the README for details
#choco.exe install -fdvy INSERT_NAME --version INSERT_VERSION  --allow-downgrade
#choco.exe install -fdvy INSERT_NAME  --allow-downgrade --source "'c:\\packages;http://chocolatey.org/api/v2/'"

$exitCode = $LASTEXITCODE

Write-Host "Exit code was $exitCode"
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode
SCRIPT

  if Vagrant::VERSION < '1.8.0'
    config.vm.provision :shell, :inline => $packageTestScript
  else
    config.vm.provision :shell, :inline => $packageTestScript, :powershell_elevated_interactive => true
  end
end

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/9a3d2149-7d04-4bae-9aa7-06515040c129%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: macOS, Vagrant, VirtualBox, shell provider powershell bug?

Alvaro Miranda Aguilera
Windows 10
Vagrant 2.0.0
Virtualbox 5.1.30

vagrant up worked fine

==> default: Running provisioner: shell...
    default: Running: shell/NotifyGuiAppsOfEnvironmentChanges.ps1 as c:\tmp\vagrant-shell.ps1
==> default: 1
==> default: SUCCESS: Specified value was saved.
==> default: Running provisioner: shell...
    default: Running: inline PowerShell script
==> default: SUCCESS: Specified value was saved.
==> default: Testing package if a line is uncommented.
==> default: Exit code was 0

kikitux@alvaro MINGW64 ~/Downloads/chocolatey-test-environment (master)
$

On Fri, Nov 3, 2017 at 12:53 AM, Bob Tanner <[hidden email]> wrote:
Not sure if this is a bug or a personal problem, posting here before opening a bug report.

macOS 10.12.6
Vagrant 2.0.0
VirtualBox 5.1.30 r118389
Windows Server 2016 Standard Edition

Unfortunately I upgraded Vagrant and VirtualBox at the same time so I don't know which one is causing the problem.

Using the Vagrant configuration from the https://github.com/chocolatey/chocolatey-test-environment project

$ vagrant  up
==> default: Checking if box 'BasicTheProgram/windows_2016' is up to date...
==> default: Running provisioner: shell...
    default: Running: shell/PrepareWindows.ps1 as c:\tmp\vagrant-shell.ps1
==> default: (10,8):UserId:
==> default: At line:72 char:1
==> default: + $folder.RegisterTaskDefinition($task_name, $task, 6, $username, $pass ...
==> default: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> default:     + CategoryInfo          : OperationStopped: (:) [], ArgumentException
==> default:     + FullyQualifiedErrorId : System.ArgumentException
==> default: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
==> default: At line:74 char:1
==> default: + $registered_task = $folder.GetTask("\$task_name")
==> default: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> default:     + CategoryInfo          : OperationStopped: (:) [], FileNotFoundException
==> default:     + FullyQualifiedErrorId : System.IO.FileNotFoundException
==> default: You cannot call a method on a null-valued expression.
==> default: At line:75 char:1
==> default: + $registered_task.Run($null) | Out-Null
==> default: + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
==> default:     + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
==> default:     + FullyQualifiedErrorId : InvokeMethodOnNull

The shell/PrepareWindows.ps1 works when executed from an interactive powershell prompt inside the VM

$AdminKey = "HKLM:\SOFTWARE\Microsoft\Active Setup\Installed Components\{A509B1A7-37EF-4b3f-8CFC-4F3A74704073}"
$UserKey = "HKLM:\SOFTWARE\Microsoft\Active Setup\Installed Components\{A509B1A8-37EF-4b3f-8CFC-4F3A74704073}"
New-ItemProperty -Path $AdminKey -Name "IsInstalled" -Value 0 -Force | Out-Null
New-ItemProperty -Path $UserKey -Name "IsInstalled" -Value 0 -Force | Out-Null
Stop-Process -Name Explorer -Force
Write-Output "IE Enhanced Security Configuration (ESC) has been disabled."

New-ItemProperty -Path "HKLM:\SOFTWARE\Microsoft\Internet Explorer\Main" -Name "DisableFirstRunCustomize" -Value 1 -PropertyType "DWord" -Force | Out-Null
Write-Output "IE first run welcome screen has been disabled."

Write-Output 'Setting Windows Update service to Manual startup type.'
Set-Service -Name wuauserv -StartupType Manual

#Set-ExecutionPolicy Unrestricted

Vagrantfile attached

# Vagrant File (Vagrantfile)

# Windows guests can't even be used with Vagrant versions less than 1.3.5.
Vagrant.require_version ">= 1.3.5"
if Vagrant::VERSION < '1.6.0'
  # Vagrant versions less than 1.6.x do not have a built-in way to
  # communicate with Windows guest images.For versions less than 1.6.x
  # the vagrant-windows plugin is required.
  Vagrant.require_plugin "vagrant-windows"
end

Vagrant.configure("2") do |config|
  # This setting will download the atlas box at
  config.vm.box = "BasicTheProgram/windows_2016"

  config.vm.provider :virtualbox do |v, override|
    # Show the GUI
    v.gui = true
    # 4GB RAM
    v.customize ["modifyvm", :id, "--memory", "4096"]
    # 2 CPUs
    v.customize ["modifyvm", :id, "--cpus", "2"]
    # Video RAM is 32 MB
    v.customize ["modifyvm", :id, "--vram", 32]
    # For better DNS resolution
    v.customize ["modifyvm", :id, "--natdnshostresolver1", "on"]
    # No audio
    v.customize ["modifyvm", :id, "--audio", "none"]
    # Clipboard enabled
    v.customize ["modifyvm", :id, "--clipboard", "bidirectional"]
    v.customize ["modifyvm", :id, "--draganddrop", "hosttoguest"]
    # For performance
    v.customize ["modifyvm", :id, "--usb", "off"]
    # Huge performance gain here
    v.linked_clone = true if Vagrant::VERSION >= '1.8.0'
  end

  config.vm.provider :hyperv do |v, override|
    # 4GB RAM
    v.memory = 4096
    # 2 CPUs
    v.cpus = 2
    # The time in seconds to wait for the virtual machine to report an IP address
    v.ip_address_timeout = 130
    # Use differencing disk instead of cloning whole VHD
    v.differencing_disk = true
    v.vm_integration_services = {
      guest_service_interface: true,
      heartbeat: true,
      key_value_pair_exchange: true,
      shutdown: true,
      time_synchronization: true,
      vss: true
  }
  end

  # timeout of waiting for image to stop running - may be a deprecated setting
  config.windows.halt_timeout = 20
  # username/password for accessing the image
  config.winrm.username = "vagrant"
  config.winrm.password = "vagrant"
  # explicitly tell Vagrant the guest is Windows
  config.vm.guest = :windows

  if Vagrant::VERSION >= '1.6.0'
    # If we are on greater than v1.6.x, we are using the built-in version
    # of communicating with Windows. For versions less than 1.6 the
    # `vagrant-windows` plugin would need to be installed and uses monkey
    # patching to override the communicator.
    config.vm.communicator = "winrm"
  end

  # A synced folder is a fancy term for shared folders - it takes a folder on
  # the host and shares it with the guest (vagrant) image. The entire folder
  # where the Vagrantfile is located is always shared as `c:\vagrant` (the
  # naming of this directory being `vagrant` is just a coincedence).
  # Share `packages` directory as `C:\packages`
  config.vm.synced_folder "packages", "/packages"
  config.vm.synced_folder "/Users/tanner/projects/", "/projects"

  #config.vm.synced_folder "temp", "/Users/vagrant/AppData/Local/Temp/chocolatey"
  # not recommended for sharing, it may have issues with `vagrant sandbox rollback`
  #config.vm.synced_folder "chocolatey", "/ProgramData/chocolatey"

  # Port forward WinRM / RDP
  # Vagrant 1.9.3 - if you run into Errno::EADDRNOTAVAIL (https://github.com/mitchellh/vagrant/issues/8395),
  #  add host_ip: "127.0.0.1" for it to work
  config.vm.network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct: true #, host_ip: "127.0.0.1"
  config.vm.network :forwarded_port, guest: 3389, host: 3389, id: "rdp", auto_correct: true #, host_ip: "127.0.0.1"
  # Port forward SSH (ssh is forwarded by default in most versions of Vagrant,
  # but be sure). This is not necessary if you are not using SSH, but it doesn't
  # hurt anything to have it
  config.vm.network :forwarded_port, guest: 22, host: 2222, id: "ssh", auto_correct: true #, host_ip: "127.0.0.1"

  # In this specific vagrant usage, we are using the shell provisioner
  if Vagrant::VERSION < '1.8.0'
    config.vm.provision :shell, :path => "shell/PrepareWindows.ps1"
    config.vm.provision :shell, :path => "shell/InstallNet4.ps1"
    config.vm.provision :shell, :path => "shell/InstallChocolatey.ps1"
    config.vm.provision :shell, :path => "shell/NotifyGuiAppsOfEnvironmentChanges.ps1"
  else
    config.vm.provision :shell, :path => "shell/PrepareWindows.ps1", :powershell_elevated_interactive => true
    config.vm.provision :shell, :path => "shell/InstallNet4.ps1", :powershell_elevated_interactive => true
    config.vm.provision :shell, :path => "shell/InstallChocolatey.ps1", :powershell_elevated_interactive => true
    config.vm.provision :shell, :path => "shell/NotifyGuiAppsOfEnvironmentChanges.ps1", :powershell_elevated_interactive => true
    config.vm.provision :shell, :path => "shell/InstallToolchain.ps1", :powershell_elevated_interactive => true
  end

$packageTestScript = <<SCRIPT
setx.exe trigger 1  # run arbitrary win32 application so LASTEXITCODE is 0
$ErrorActionPreference = "Stop"
$env:PATH +=";$($env:SystemDrive)\\ProgramData\\chocolatey\\bin"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)

Write-Output "Testing package if a line is uncommented."
# THIS IS WHAT YOU CHANGE
# - uncomment one of the two and edit it appropriately
# - See the README for details
#choco.exe install -fdvy INSERT_NAME --version INSERT_VERSION  --allow-downgrade
#choco.exe install -fdvy INSERT_NAME  --allow-downgrade --source "'c:\\packages;http://chocolatey.org/api/v2/'"

$exitCode = $LASTEXITCODE

Write-Host "Exit code was $exitCode"
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode
SCRIPT

  if Vagrant::VERSION < '1.8.0'
    config.vm.provision :shell, :inline => $packageTestScript
  else
    config.vm.provision :shell, :inline => $packageTestScript, :powershell_elevated_interactive => true
  end
end

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/9a3d2149-7d04-4bae-9aa7-06515040c129%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyStiKr%3DMra4XmUmcUQWvPBYaU2GSg-qMAF3%3Dv%2BTLe-Lg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: macOS, Vagrant, VirtualBox, shell provider powershell bug?

Bob Tanner
Thanks for that info.

I tried 

    Windows 10: worked
    Windows Server 2012 R2: worked. 
    Windows Server 2016: failed

It's a problem with Windows Server 2016.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/de27058a-cb1e-41e5-9894-90329ac91d9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: macOS, Vagrant, VirtualBox, shell provider powershell bug?

Stefan Scherer
I tried 

Windows 7 on Host
Vagrant 2.0.0
VirtualBox 5.1.30
works fine with StefanScherer/windows_2016_docker basebox

C:\Users\stefan.scherer\GitHub\chocolatey-test-environment [master +0 ~1 -0 !]> git diff
diff
--git a/Vagrantfile b/Vagrantfile
index e1d5c6d
..9c6eb09 100644
--- a/Vagrantfile
+++ b/Vagrantfile
@@ -14,7 +14,7 @@ end
 
Vagrant.configure("2") do |config|
   
# This setting will download the atlas box at
   
# https://atlas.hashicorp.com/ferventcoder/boxes/win2012r2-x64-nocm
-  config.vm.box = "ferventcoder/win2012r2-x64-nocm"
+  config.vm.box = "StefanScherer/windows_2016_docker"


   
# http://docs.vagrantup.com/v2/providers/configuration.html
   
# http://docs.vagrantup.com/v2/virtualbox/configuration.html
C
:\Users\stefan.scherer\GitHub\chocolatey-test-environment [master +0 ~1 -0 !]>




C
:\Users\stefan.scherer\GitHub\chocolatey-test-environment [master ≡]> vagrant up --provider virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Box 'StefanScherer/windows_2016_docker' could not be found. Attempting to find and install...
   
default: Box Provider: virtualbox
   
default: Box Version: >= 0
==> default: Loading metadata for box 'StefanScherer/windows_2016_docker'
   
default: URL: https://vagrantcloud.com/StefanScherer/windows_2016_docker
==> default: Adding box 'StefanScherer/windows_2016_docker' (v17.06.0) for provider: virtualbox
   
default: Downloading: https://vagrantcloud.com/StefanScherer/boxes/windows_2016_docker/versions/17.06.0/providers/virtualbox.box
   
default: Progress: 100% (Rate: 9202k/s, Estimated time remaining: --:--:--)
==> default: Successfully added box 'StefanScherer/windows_2016_docker' (v17.06.0) for 'virtualbox'!
==> default: Preparing master VM for linked clones...
   
default: This is a one time operation. Once the master VM is prepared,
   
default: it will be used as a base for linked clones, making the creation
   
default: of new VMs take milliseconds on a modern system.
==> default: Importing base box 'StefanScherer/windows_2016_docker'...
==> default: Cloning VM...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'StefanScherer/windows_2016_docker' is up to date...
==> default: Setting the name of the VM: chocolatey-test-environment_default_1510128934328_78090
==> default: Fixed port collision for 3389 => 3389. Now on port 2200.
==> default: Fixed port collision for 5985 => 5985. Now on port 2201.
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
   
default: Adapter 1: nat
==> default: Forwarding ports...
   
default: 3389 (guest) => 2200 (host) (adapter 1)
   
default: 22 (guest) => 2222 (host) (adapter 1)
   
default: 5985 (guest) => 2201 (host) (adapter 1)
   
default: 5986 (guest) => 55986 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
   
default: WinRM address: 127.0.0.1:2201
   
default: WinRM username: vagrant
   
default: WinRM execution_time_limit: PT2H
   
default: WinRM transport: negotiate
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
==> default: Mounting shared folders...
   
default: /vagrant => C:/Users/stefan.scherer/GitHub/chocolatey-test-environment
   
default: /packages => C:/Users/stefan.scherer/GitHub/chocolatey-test-environment/packages
==> default: Running provisioner: shell...
   
default: Running: shell/PrepareWindows.ps1 as c:\tmp\vagrant-shell.ps1
==> default: IE Enhanced Security Configuration (ESC) has been disabled.
==> default: IE first run welcome screen has been disabled.
==> default: Setting Windows Update service to Manual startup type.
==> default: Running provisioner: shell...
   
default: Running: shell/InstallNet4.ps1 as c:\tmp\vagrant-shell.ps1
==> default: Running provisioner: shell...
   
default: Running: shell/InstallChocolatey.ps1 as c:\tmp\vagrant-shell.ps1
==> default: Mode                LastWriteTime         Length Name
==> default: ----                -------------         ------ ----
==> default: d-----        11/8/2017  12:16 AM                chocInstall
==> default: Downloading https://chocolatey.org/api/v2/package/chocolatey/0.10.8 to C:\Users\vagrant\AppData\Local\Temp\chocolatey\chocInstall\chocolatey.zip
==> default: Download 7Zip commandline tool
==> default: Downloading https://chocolatey.org/7za.exe to C:\Users\vagrant\AppData\Local\Temp\chocolatey\chocInstall\7za.exe
==> default: Extracting C:\Users\vagrant\AppData\Local\Temp\chocolatey\chocInstall\chocolatey.zip to C:\Users\vagrant\AppData\Local\Temp\chocolatey\chocInstall.
..
==> default: 7-Zip (A) 9.20  Copyright (c) 1999-2010 Igor Pavlov  2010-11-18
==> default: Processing archive: C:\Users\vagrant\AppData\Local\Temp\chocolatey\chocInstall\chocolatey.zip
==> default: Extracting  _rels\.rels
==> default: Extracting  chocolatey.nuspec
==> default: Extracting  tools\chocolateyInstall.ps1
==> default: Extracting  tools\chocolateysetup.psm1
==> default: Extracting  tools\init.ps1
==> default: Extracting  tools\chocolateyInstall\choco.exe
==> default: Extracting  tools\chocolateyInstall\choco.exe.ignore
==> default: Extracting  tools\chocolateyInstall\choco.exe.manifest
==> default: Extracting  tools\chocolateyInstall\CREDITS.txt
==> default: Extracting  tools\chocolateyInstall\LICENSE.txt
==> default: Extracting  tools\chocolateyInstall\helpers\chocolateyInstaller.psm1
==> default: Extracting  tools\chocolateyInstall\helpers\chocolateyProfile.psm1
==> default: Extracting  tools\chocolateyInstall\helpers\chocolateyScriptRunner.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\ChocolateyTabExpansion.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Format-FileSize.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-CheckSumValid.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-ChocolateyUnzip.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-ChocolateyWebFile.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-EnvironmentVariable.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-EnvironmentVariableNames.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-FtpFile.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-OSArchitectureWidth.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-PackageParameters.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-ToolsLocation.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-UACEnabled.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-UninstallRegistryKey.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-VirusCheckValid.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-WebFile.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-WebFileName.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Get-WebHeaders.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-BinFile.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyDesktopLink.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyEnvironmentVariable.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyExplorerMenuItem.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyFileAssociation.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyInstallPackage.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyPackage.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyPath.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyPinnedTaskBarItem.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyPowershellCommand.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyShortcut.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyVsixPackage.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-ChocolateyZipPackage.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Install-Vsix.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Set-EnvironmentVariable.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Set-PowerShellExitCode.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Start-ChocolateyProcessAsAdmin.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Test-ProcessAdminRights.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Uninstall-BinFile.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Uninstall-ChocolateyEnvironmentVariable.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Uninstall-ChocolateyPackage.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\UnInstall-ChocolateyZipPackage.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Update-SessionEnvironment.ps1
==> default: Extracting  tools\chocolat
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Write-ChocolateySuccess.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Write-FileUpdateLog.ps1
==> default: Extracting  tools\chocolateyInstall\helpers\functions\Write-FunctionCallLogMessage.ps1
==> default: Extracting  tools\chocolateyInstall\redirects\choco.exe
==> default: Extracting  tools\chocolateyInstall\redirects\choco.exe.ignore
==> default: Extracting  tools\chocolateyInstall\redirects\chocolatey.exe
==> default: Extracting  tools\chocolateyInstall\redirects\chocolatey.exe.ignore
==> default: Extracting  tools\chocolateyInstall\redirects\cinst.exe
==> default: Extracting  tools\chocolateyInstall\redirects\cinst.exe.ignore
==> default: Extracting  tools\chocolateyInstall\redirects\clist.exe
==> default: Extracting  tools\chocolateyInstall\redirects\clist.exe.ignore
==> default: Extracting  tools\chocolateyInstall\redirects\cpack.exe
==> default: Extracting  tools\chocolateyInstall\redirects\cpack.exe.ignore
==> default: Extracting  tools\chocolateyInstall\redirects\cpush.exe
==> default: Extracting  tools\chocolateyInstall\redirects\cpush.exe.ignore
==> default: Extracting  tools\chocolateyInstall\redirects\cuninst.exe
==> default: Extracting  tools\chocolateyInstall\redirects\cuninst.exe.ignore
==> default: Extracting  tools\chocolateyInstall\redirects\cup.exe
==> default: Extracting  tools\chocolateyInstall\redirects\cup.exe.ignore
==> default: Extracting  tools\chocolateyInstall\redirects\cver.exe
==> default: Extracting  tools\chocolateyInstall\redirects\cver.exe.ignore
==> default: Extracting  tools\chocolateyInstall\redirects\RefreshEnv.cmd
==> default: Extracting  tools\chocolateyInstall\tools\7z.dll
==> default: Extracting  tools\chocolateyInstall\tools\7z.dll.manifest
==> default: Extracting  tools\chocolateyInstall\tools\7z.exe
==> default: Extracting  tools\chocolateyInstall\tools\7z.exe.ignore
==> default: Extracting  tools\chocolateyInstall\tools\7z.exe.manifest
==> default: Extracting  tools\chocolateyInstall\tools\7zip.license.txt
==> default: Extracting  tools\chocolateyInstall\tools\checksum.exe
==> default: Extracting  tools\chocolateyInstall\tools\checksum.exe.config
==> default: Extracting  tools\chocolateyInstall\tools\checksum.exe.ignore
==> default: Extracting  tools\chocolateyInstall\tools\checksum.license.txt
==> default: Extracting  tools\chocolateyInstall\tools\shimgen.exe
==> default: Extracting  tools\chocolateyInstall\tools\shimgen.exe.ignore
==> default: Extracting  tools\chocolateyInstall\tools\shimgen.license.txt
==> default: Extracting  package\services\metadata\core-properties\572306d3793d450399abed41e7cd6692.psmdcp
==> default: Extracting  [Content_Types].xml
==> default: Everything is Ok
==> default: Files: 91
==> default: Size:       10724638
==> default: Compressed: 5372647
==> default: Installing chocolatey on this machine
==> default: DEBUG: Initialize-Chocolatey
==> default: DEBUG: Host version is 5.1.14393.1532, PowerShell Version is '5.1.14393.1532' and CLR Version
==> default: is '4.0.30319.42000'.
==> default: DEBUG: Get-ChocolateyInstallFolder
==> default: DEBUG: Set-ChocolateyInstallFolder
==> default: DEBUG: Running Install-ChocolateyEnvironmentVariable -variableName 'ChocolateyInstall'
==> default: -variableValue '' -variableType 'User'
==> default: DEBUG: Running Set-EnvironmentVariable -Name 'ChocolateyInstall' -Value '' -Scope 'User'
==> default: DEBUG: Test-ProcessAdminRights: returning True
==> default: DEBUG: Administrator installing so using Machine environment variable target instead of User.
==> default: DEBUG: Running Install-ChocolateyEnvironmentVariable -variableName 'ChocolateyInstall'
==> default: -variableValue '' -variableType 'Machine'
==> default: DEBUG: Test-ProcessAdminRights: returning True
==> default: DEBUG: Running Set-EnvironmentVariable -Name 'ChocolateyInstall' -Value '' -Scope 'Machine'
==> default: Creating ChocolateyInstall as an environment variable (targeting 'Machine')
==> default:   Setting ChocolateyInstall to 'C:\ProgramData\chocolatey'
==> default: WARNING: It's very likely you will need to close and reopen your shell
==> default:   before you can use choco.
==> default: DEBUG: Running Install-ChocolateyEnvironmentVariable -variableName '
ChocolateyInstall'
==> default: -variableValue '
C:\ProgramData\chocolatey' -variableType 'Machine'
==> default: DEBUG: Test-ProcessAdminRights: returning True
==> default: DEBUG: Running Set-EnvironmentVariable -Name '
ChocolateyInstall' -Value
==> default: '
C:\ProgramData\chocolatey' -Scope 'Machine'
==> default: DEBUG: Registry type for ChocolateyInstall is/will be String
==> default: DEBUG:
==> default: using System;
==> default: using System.Runtime.InteropServices;
==> default: namespace Win32
==> default: {
==> default:     public class NativeMethods
==> default:     {
==> default:     [DllImport("user32.dll", SetLastError = true, CharSet = CharSet.Auto)]
==> default: public static extern IntPtr SendMessageTimeout(
==> default:     IntPtr hWnd, uint Msg, UIntPtr wParam, string lParam,
==> default:     uint fuFlags, uint uTimeout, out UIntPtr lpdwResult);
==> default:     }
==> default: }
==> default: DEBUG: Running Update-SessionEnvironment
==> default: DEBUG: Create-DirectoryIfNotExists
==> default: DEBUG: Ensure-Permissions
==> default: DEBUG: Test-ProcessAdminRights: returning True
==> default: DEBUG: Removing existing permissions.
==> default: Restricting write permissions to Administrators
==> default: DEBUG: Current user no longer set due to possible escalation of privileges - set
==> default: $env:ChocolateyInstallAllowCurrentUser="true" if you require this.
==> default: DEBUG: Set Owner to Administrators
==> default: DEBUG: Default Installation folder - removing inheritance with no copy
==> default: DEBUG: Allow users to append to log files.
==> default: DEBUG: Create-DirectoryIfNotExists
==> default: We are setting up the Chocolatey package repository.
==> default: The packages themselves go to '
C:\ProgramData\chocolatey\lib'
==> default:   (i.e. C:\ProgramData\chocolatey\lib\yourPackageName).
==> default: A shim file for the command line goes to '
C:\ProgramData\chocolatey\bin'
==> default:   and points to an executable in '
C:\ProgramData\chocolatey\lib\yourPackageName'.
==> default: Creating Chocolatey folders if they do not already exist.
==> default: WARNING: You can safely ignore errors related to missing log files when
==> default:   upgrading from a version of Chocolatey less than 0.9.9.
==> default:   '
Batch file could not be found' is also safe to ignore.
==> default:   '
The system cannot find the file specified' - also safe.
==> default: DEBUG: Create-DirectoryIfNotExists
==> default: DEBUG: Create-DirectoryIfNotExists
==> default: DEBUG: Install-ChocolateyFiles
==> default: DEBUG: Removing install files in chocolateyInstall, helpers, redirects, and tools
==> default: DEBUG: Attempting to move choco.exe to choco.exe.old so we can place the new version here.
==> default: DEBUG: Unpacking files required for Chocolatey.
==> default: DEBUG: Copying the contents of
==> default: '
C:\Users\vagrant\AppData\Local\Temp\chocolatey\chocInstall\tools\chocolateyInstall' to
==> default: '
C:\ProgramData\chocolatey'.
==> default: DEBUG: Ensure-ChocolateyLibFiles
==> default: DEBUG: Create-DirectoryIfNotExists
==> default: chocolatey.nupkg file not installed in lib.
==> default:  Attempting to locate it from bootstrapper.
==> default: DEBUG: First the zip file at
==> default: '
C:\Users\vagrant\AppData\Local\Temp\chocolatey\chocInstall\chocolatey.zip'.
==> default: DEBUG: Then from a neighboring chocolatey.*nupkg file
==> default: '
C:\Users\vagrant\AppData\Local\Temp\chocolatey\chocInstall\tools/../../'.
==> default: DEBUG: Copying '
C:\Users\vagrant\AppData\Local\Temp\chocolatey\chocInstall\chocolatey.zip' to
==> default: '
C:\ProgramData\chocolatey\lib\chocolatey\chocolatey.nupkg'.
==> default: DEBUG: Install-ChocolateyBinFiles
==> default: DEBUG: Installing the bin file redirects
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\choco.exe to
==> default: C:\ProgramData\chocolatey\bin\choco.exe
==> default: DEBUG: Added command choco
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\chocolatey.exe to
==> default: C:\ProgramData\chocolatey\bin\chocolatey.exe
==> default: DEBUG: Added command chocolatey
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\cinst.exe to
==> default: C:\ProgramData\chocolatey\bin\cinst.exe
==> default: DEBUG: Added command cinst
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\clist.exe to
==> default: C:\ProgramData\chocolatey\bin\clist.exe
==> default: DEBUG: Added command clist
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\cpack.exe to
==> default: C:\ProgramData\chocolatey\bin\cpack.exe
==> default: DEBUG: Added command cpack
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\cpush.exe to
==> default: C:\ProgramData\chocolatey\bin\cpush.exe
==> default: DEBUG: Added command cpush
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\cuninst.exe to
==> default: C:\ProgramData\chocolatey\bin\cuninst.exe
==> default: DEBUG: Added command cuninst
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\cup.exe to
==> default: C:\ProgramData\chocolatey\bin\cup.exe
==> default: DEBUG: Added command cup
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\cver.exe to
==> default: C:\ProgramData\chocolatey\bin\cver.exe
==> default: DEBUG: Added command cver
==> default: DEBUG: Attempting to copy C:\ProgramData\chocolatey\redirects\RefreshEnv.cmd to
==> default: C:\ProgramData\chocolatey\bin\RefreshEnv.cmd
==> default: DEBUG: Added command RefreshEnv
==> default: DEBUG: Initialize-ChocolateyPath
==> default: DEBUG: Initializing Chocolatey Path if required
==> default: DEBUG: Test-ProcessAdminRights: returning True
==> default: DEBUG: Administrator installing so using Machine environment variable target instead of User.
==> default: DEBUG: Running Install-ChocolateyPath -pathToInstall '
C:\ProgramData\chocolatey\bin' -pathType
==> default:  '
Machine'
==> default: DEBUG: Running Update-SessionEnvironment
==> default: PATH environment variable does not have C:\ProgramData\chocolatey\bin in it. Adding...
==> default: DEBUG: Test-ProcessAdminRights: returning True
==> default: DEBUG: Running Set-EnvironmentVariable -Name '
Path' -Value
==> default: '
C:\Windows\system32;C:\Windows;C:\Windows\System32\Wbem;C:\Windows\System32\WindowsPowerShell
==> default: \v1.0\;C:\Program Files\Docker;C:\ProgramData\chocolatey\bin;' -Scope 'Machine'
==> default: DEBUG: Registry type for Path is/will be ExpandString
==> default: DEBUG: Running Update-SessionEnvironment
==> default: DEBUG: Process-ChocolateyBinFiles
==> default: DEBUG: Host version is 5.1.14393.1532, PowerShell Version is '
5.1.14393.1532' and CLR Version
==> default: is '
4.0.30319.42000'.
==> default: DEBUG: Add-ChocolateyProfile
==> default: WARNING: Not setting tab completion: Profile file does not exist at
==> default: '
C:\Users\vagrant\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1'.
==> default: DEBUG: Install-DotNet4IfMissing called with $forceFxInstall=False
==> default: Chocolatey (choco.exe) is now ready.
==> default: You can call choco from anywhere, command line or powershell by typing choco.
==> default: Run choco /? for a list of functions.
==> default: You may need to shut down and restart powershell and/or consoles
==> default:  first prior to using choco.
==> default: DEBUG: Remove-OldChocolateyInstall
==> default: Ensuring chocolatey commands are on the path
==> default: Ensuring chocolatey.nupkg is in the lib folder
==> default: Chocolatey v0.10.8
==> default: autoUninstaller was enabled by default. Explicitly setting value.
==> default: Enabled autoUninstaller
==> default: Chocolatey v0.10.8
==> default: Enabled allowGlobalConfirmation
==> default: Chocolatey v0.10.8
==> default: Enabled logEnvironmentValues
==> default: Running provisioner: shell...
    default: Running: shell/NotifyGuiAppsOfEnvironmentChanges.ps1 as c:\tmp\vagrant-shell.ps1
==> default: 1
==> default: SUCCESS: Specified value was saved.
==> default: Running provisioner: shell...
    default: Running: inline PowerShell script
==> default: SUCCESS: Specified value was saved.
==> default: Testing package if a line is uncommented.
==> default: Exit code was 0
C:\Users\stefan.scherer\GitHub\chocolatey-test-environment [master ≡ +0 ~1 -0 !]>



--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/7f3f57f8-6b31-41aa-8ee3-d42cf854dd7c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: macOS, Vagrant, VirtualBox, shell provider powershell bug?

bob-2
In reply to this post by Alvaro Miranda Aguilera
Can you try Windows Server 2016?

I found evidence Windows Server 2016 does not allow non-Administrator accounts to manage scheduled tasks.

Details in github at https://github.com/hashicorp/vagrant/issues/9138


On Friday, November 3, 2017 at 7:41:06 AM UTC-5, Alvaro Miranda Aguilera wrote:
Windows 10
Vagrant 2.0.0
Virtualbox 5.1.30

vagrant up worked fine

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/c46fec24-3300-4ec6-8217-04a56384817a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: macOS, Vagrant, VirtualBox, shell provider powershell bug?

bob-2
In reply to this post by Stefan Scherer
Hmm, macOS on host or the WinRM code Vagrant uses on macOS?

On Wednesday, November 8, 2017 at 2:24:23 AM UTC-6, Stefan Scherer wrote:
I tried 

Windows 7 on Host
Vagrant 2.0.0
VirtualBox 5.1.30
works fine with StefanScherer/windows_2016_docker basebox

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6b56419c-14e7-431d-8bf2-3fe13e3a8ea1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.