Hi Nick,

I recently wrote an article about this on my blog (although mine was based 
on Windows 2008, but should be the same process)

http://dennypc.wordpress.com/

I ran into a similar issues as you and ran a few additional configuration 
for winrm on the guest.  I also used Chef's knife windows plugin to verify 
that winrm was working fine.  Detailed steps are covered on my blog.  Also 
packer-windows templates are based on SSH at the moment, so if you're 
trying to use WinRM you might have to roll your own box any ways.

On Wednesday, June 11, 2014 9:28:50 AM UTC-4, Nick Anderson wrote:
>
> On Wednesday, June 11, 2014 8:09:50 AM UTC-5, Shawn Neal wrote:
>>
>> Did you fully configure winrm as per 
>> https://github.com/winrb/vagrant-windows#winrm-configuration?
>>
>
> I did try those at one point. I am not sure I have done that on this 
> attempt. It's not clear if any of those instructions are relevant if I am 
> using Vagrant 1.6+. The top of the page says "This plugin is deprecated, 
> please use Vagrant 1.6+ <http://www.vagrantup.com/downloads.html> which 
> natively supports Windows guests over WinRM." and the only info in the 
> vagrant documentation I could find was the reference to 
> config.vm.communicator 
> = "winrm".
>  
>
>> Setting the network to private, not sure about that one. Usually work is 
>> used.
>>
>
> It was something I found from other threads. The only options are "Not 
> configured", "Private", and "Public". I also saw something about having to 
> have network discovery enabled ( I tried that as well)
>  
>
>> Firewall?
>>
>
> It's enabled. RDP and Windows Remote Management are allowed.
>
>
> IMO the easiest way to create a Vagrant base box is to use Packer with 
>> packer-windows (https://github.com/joefitzgerald/packer-windows)
>>
>
> Thanks, I will take a look at that. 
>
>  
>
>> On Tuesday, June 10, 2014 12:46:18 PM UTC-7, Nick Anderson wrote:
>>>
>>> I am trying to build a Windows Server 2012 vm that I can use with 
>>> Vagrant and Virtualbox.
>>>
>>> It's not clear to me what I need to do. Here are the things I have done 
>>> on the Windows vm that I am preparing as a basebox.
>>>
>>> Disable password complexity requirements
>>> Set minimum password age to 0
>>> Set Administrator password to 'vagrant'
>>> Create vagrant user
>>> Set vagrant users password to 'vagrant'
>>> Enable remote desktop
>>> Add the vagrant user to the allowed list of remote desktop users
>>> Allow all connections from computers running any version of RDP (or my 
>>> linux client cant rdp successfully)
>>> Install ruby 1.9.3 from rubyinstall.org
>>> Install winrm with geminstall -rwinrm
>>> Configure winrm with winrm quickconfig
>>> Disable UAC
>>> Disable Server Manager on login
>>> Disable Shutdown Tracker
>>> Ensure that network is set to "Private"
>>> Install Virtualbox guest tools
>>>
>>> I export the vm as a box, import it to vagrant 
>>> I think generate a vagrant config using vagrant init <name of windows 
>>> box>
>>> And then I added config.cm.communicator = "winrm"
>>> Finally I vagrant up my env.
>>>
>>> The VM comes up without issue, but Vagrant just sits waiting for the 
>>> machine to boot until it times out.
>>> vagrant rdp does nothing
>>>
>>> I am able to manually log in with rdesktop if I specifically forward a 
>>> port
>>> config.vm.network "forwarded_port", guest: 3389, host: 53389
>>>
>>> Then rdesktop localhost:53389 will give me the windows login screen.
>>>
>>> I have tried with and without the vagrant-windows plugin.
>>>
>>> I am running vagrant 1.6.3 on Ubuntu.
>>>
>>> It seems like I am missing some basic thing. Have I missed some 
>>> documentation somewhere?
>>>
>>

-- 
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 [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to