Closed StefanScherer closed 9 years ago
But there is still some work to do. A vagrant up
waits for WinRM. And Edge does not want to launch if UAC is turned off.
Ready to :ship: @StefanScherer?
At the moment the download URL responds with 404. Seems that Microsoft is cleanup up its insider program for the final release. If this is not just a temporary error I prefer to wait until an official trial ISO is available.
@joefitzgerald I have updated the ISO link to the final eval version.
The Packer build runs fine, I've tested it with VirtualBox 5.0.0. But the Vagrant box still does not have an open WinRM port 5985, so Vagrant times out:
$ vagrant up --provider virtualbox
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'windows_10'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: win10_default_1438207192498_68333
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 3389 => 3389 (adapter 1)
default: 22 => 2222 (adapter 1)
default: 5985 => 5985 (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:5985
default: WinRM username: vagrant
default: WinRM transport: plaintext
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.
If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
This are the open ports after a vagrant up
:
C:\Windows\system32>netstat -ano
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:22 0.0.0.0:0 LISTENING 2120
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 680
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 864
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49408 0.0.0.0:0 LISTENING 428
TCP 0.0.0.0:49409 0.0.0.0:0 LISTENING 884
TCP 0.0.0.0:49410 0.0.0.0:0 LISTENING 1340
TCP 0.0.0.0:49411 0.0.0.0:0 LISTENING 820
TCP 0.0.0.0:49414 0.0.0.0:0 LISTENING 544
TCP 0.0.0.0:49430 0.0.0.0:0 LISTENING 552
TCP 10.0.2.15:139 0.0.0.0:0 LISTENING 4
TCP 10.0.2.15:49450 207.46.7.252:80 ESTABLISHED 4556
TCP 10.0.2.15:49451 204.79.197.200:443 ESTABLISHED 3292
TCP 10.0.2.15:49452 204.79.197.200:443 ESTABLISHED 3292
TCP [::]:22 [::]:0 LISTENING 2120
TCP [::]:135 [::]:0 LISTENING 680
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:3389 [::]:0 LISTENING 864
TCP [::]:47001 [::]:0 LISTENING 4
TCP [::]:49408 [::]:0 LISTENING 428
TCP [::]:49409 [::]:0 LISTENING 884
TCP [::]:49410 [::]:0 LISTENING 1340
TCP [::]:49411 [::]:0 LISTENING 820
TCP [::]:49414 [::]:0 LISTENING 544
TCP [::]:49430 [::]:0 LISTENING 552
UDP 0.0.0.0:3389 *:* 864
UDP 0.0.0.0:3544 *:* 820
UDP 0.0.0.0:5353 *:* 864
UDP 0.0.0.0:5355 *:* 864
UDP 10.0.2.15:137 *:* 4
UDP 10.0.2.15:138 *:* 4
UDP 10.0.2.15:1900 *:* 912
UDP 10.0.2.15:51551 *:* 820
UDP 10.0.2.15:64112 *:* 912
UDP 127.0.0.1:1900 *:* 912
UDP 127.0.0.1:64113 *:* 912
UDP [::]:3389 *:* 864
UDP [::]:5353 *:* 864
UDP [::]:5355 *:* 864
UDP [::1]:1900 *:* 912
UDP [::1]:64111 *:* 912
UDP [fe80::4478:fb2a:e825:91f5%5]:1900 *:* 912
UDP [fe80::4478:fb2a:e825:91f5%5]:64110 *:* 912
If this PR is helpful for others we can merge it now and have a look at the problem enabling WinRM later. Perhaps someone else sees what's wrong with it.
I think the problem has something to do with the public network. There is a fix over there at boxcutter/windows ;-) https://github.com/boxcutter/windows/blob/master/floppy/install-winrm.cmd#L24-34
I've updated the windows_10.json template to build Windows 10 technical preview build 10162. Now also shell provisioning seems to work again, so I have added some of them. Tested with packer 0.8.1 with Fusion 7 on OSX 10.10.3 (packer is still compacting the disk...).
Nice new wallpaper :+1: