Windows compatibility

[MassimoSporchia]

Expected Behavior

windows2008-ostest boots up, puppet gets installed and I can test out my puppet code.

Actual Behavior

windows2008-ostest boots up, vagrant command gets stuck on applying

Steps to Reproduce the Problem

1. cd into psick\vagrant\psick\vagrant\environments\ostest
2. vagrant up windows2008-ostest
3. get stuck

Specifications

For the forementioned reasons, I can't get add facter's output result.
Additional details (shame on me): I'm running vagrant from a Windows 10 machine.
The vagrant up log is the following:

==> windows2008-ostest: Matching MAC address for NAT networking...
==> windows2008-ostest: Setting the name of the VM: ostest_windows2008-ostest_1530083481921_1843
==> windows2008-ostest: Clearing any previously set network interfaces...
==> windows2008-ostest: Preparing network interfaces based on configuration...
    windows2008-ostest: Adapter 1: nat
    windows2008-ostest: Adapter 2: hostonly
==> windows2008-ostest: Forwarding ports...
    windows2008-ostest: 3389 (guest) => 33894 (host) (adapter 1)
    windows2008-ostest: 5985 (guest) => 55985 (host) (adapter 1)
    windows2008-ostest: 5986 (guest) => 55986 (host) (adapter 1)
    windows2008-ostest: 22 (guest) => 2222 (host) (adapter 1)
    windows2008-ostest: 5986 (guest) => 55986 (host) (adapter 1)
    windows2008-ostest: 22 (guest) => 2222 (host) (adapter 1)
==> windows2008-ostest: Running 'pre-boot' VM customizations...
==> windows2008-ostest: Booting VM...
==> windows2008-ostest: Waiting for machine to boot. This may take a few minutes...
    windows2008-ostest: WinRM address: 127.0.0.1:55985
    windows2008-ostest: WinRM username: vagrant
    windows2008-ostest: WinRM execution_time_limit: PT2H
    windows2008-ostest: WinRM transport: negotiate
==> windows2008-ostest: Machine booted and ready!
Sorry, don't know how to check guest version of Virtualbox Guest Additions on this platform. Stopping installation.
==> windows2008-ostest: Checking for guest additions in VM...
==> windows2008-ostest: Setting hostname...
==> windows2008-ostest: Configuring and enabling network interfaces...
==> windows2008-ostest: Mounting shared folders...
    windows2008-ostest: /vagrant => C:/Users/massimo.sporchia/workspace/vagrant/psick/vagrant/environments/ostest
    windows2008-ostest: /vagrant_puppet => C:/Users/massimo.sporchia/workspace/vagrant/psick
==> windows2008-ostest: Running provisioner: shell...
    windows2008-ostest: Running: ../../bin/vagrant-sethostname.sh as c:\tmp\vagrant-shell.sh

[alvagante]

Thanks for the report. We actually are aware that puppet doesn't run correctly on WIndows nodes when in apply mode.
If you want to test puppet on windows, you should try the lab vragrant environment, where you can have a puppet (enterprise) server serving the other nodes in the same environment where puppet runs in agent mode (and using the Puppet code and data in your Host (specify --environment=host to point to the control repo present on the host and mounted on the puppet vm).
Will leave the ticket open, as we would like to make puppet run smoothly on Windows also in apply mode.