Re: [vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

2017-11-17 Thread Alvaro Miranda Aguilera
Hello

Chris has been working hard on getting all the issues related to windows
solved.

We were able to replicate some of them on win10/win2016 domain, but some
others weren't possible to replicate at all.

so maybe are still some that we are working hard to catch up.

alvaro



On Thu, Nov 16, 2017 at 10:08 PM, Eric Beach  wrote:

> So, I don't know what changed with 5.0.4, but this seems to have fixed the
> issue.  I was able to successfully install the plugin and it appears to be
> functioning normally.
>
> Thanks again!
>
> On Wednesday, November 15, 2017 at 2:53:26 PM UTC-5, Eric Beach wrote:
>>
>> Hey Alvaro,
>>
>> Thanks for getting back.
>>
>> I was re-running the command to provide a new debug for you and it
>> appears that 5.0.4 has released as well. It took a long time (with no
>> verbose output), but it appears the plugin finally installed with 5.0.4.
>>
>> I'll do some testing and see what happens.
>>
>> Thanks!
>>
>> On Wednesday, November 15, 2017 at 3:52:28 AM UTC-5, Alvaro Miranda
>> Aguilera wrote:
>>>
>>> Hello
>>>
>>> We haven't been able to reproduce this particular error.
>>>
>>> We did release 5.0.3 that includes the fix for the machine on the
>>> domain, but I am able to install and run VMs with either local user or
>>> domain user.
>>>
>>> Does the error happens at install time of the plugin or after the
>>> install on the vagrant commands?
>>>
>>> Can you share a verbose error? (just add --debug to the command)
>>>
>>> Also, some information.
>>>
>>> I am testing with win10 pro, english lang. windows 2016 AD domain.
>>>
>>> Thanks
>>> Alvaro
>>>
>>> On Tue, Nov 14, 2017 at 4:01 PM, Eric Beach  wrote:
>>>
 Unfortunately, no, not yet.   I was able to install with a local
 account, but not with a domain account logged in.

 --
 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 vagrant-up+...@googlegroups.com.
 To view this discussion on the web visit https://groups.google.com/d/ms
 gid/vagrant-up/7e71859f-e16c-41c0-84dd-482be9571082%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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/e7897e15-306c-49c9-b922-2a525a39ba3a%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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eza9SzehOAG38ApALuOoVBe6tG7z%2B4UTxb54x6Y8QYc%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

2017-11-16 Thread Eric Beach
So, I don't know what changed with 5.0.4, but this seems to have fixed the 
issue.  I was able to successfully install the plugin and it appears to be 
functioning normally.  

Thanks again!

On Wednesday, November 15, 2017 at 2:53:26 PM UTC-5, Eric Beach wrote:
>
> Hey Alvaro,
>
> Thanks for getting back. 
>
> I was re-running the command to provide a new debug for you and it appears 
> that 5.0.4 has released as well. It took a long time (with no verbose 
> output), but it appears the plugin finally installed with 5.0.4.  
>
> I'll do some testing and see what happens.  
>
> Thanks!
>
> On Wednesday, November 15, 2017 at 3:52:28 AM UTC-5, Alvaro Miranda 
> Aguilera wrote:
>>
>> Hello
>>
>> We haven't been able to reproduce this particular error.
>>
>> We did release 5.0.3 that includes the fix for the machine on the domain, 
>> but I am able to install and run VMs with either local user or domain user.
>>
>> Does the error happens at install time of the plugin or after the install 
>> on the vagrant commands?
>>
>> Can you share a verbose error? (just add --debug to the command)
>>
>> Also, some information.
>>
>> I am testing with win10 pro, english lang. windows 2016 AD domain.
>>
>> Thanks
>> Alvaro
>>
>> On Tue, Nov 14, 2017 at 4:01 PM, Eric Beach  wrote:
>>
>>> Unfortunately, no, not yet.   I was able to install with a local 
>>> account, but not with a domain account logged in.
>>>
>>> --
>>> 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 vagrant-up+...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/vagrant-up/7e71859f-e16c-41c0-84dd-482be9571082%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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/e7897e15-306c-49c9-b922-2a525a39ba3a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

2017-11-15 Thread Eric Beach
Hey Alvaro,

Thanks for getting back. 

I was re-running the command to provide a new debug for you and it appears 
that 5.0.4 has released as well. It took a long time (with no verbose 
output), but it appears the plugin finally installed with 5.0.4.  

I'll do some testing and see what happens.  

Thanks!

On Wednesday, November 15, 2017 at 3:52:28 AM UTC-5, Alvaro Miranda 
Aguilera wrote:
>
> Hello
>
> We haven't been able to reproduce this particular error.
>
> We did release 5.0.3 that includes the fix for the machine on the domain, 
> but I am able to install and run VMs with either local user or domain user.
>
> Does the error happens at install time of the plugin or after the install 
> on the vagrant commands?
>
> Can you share a verbose error? (just add --debug to the command)
>
> Also, some information.
>
> I am testing with win10 pro, english lang. windows 2016 AD domain.
>
> Thanks
> Alvaro
>
> On Tue, Nov 14, 2017 at 4:01 PM, Eric Beach  > wrote:
>
>> Unfortunately, no, not yet.   I was able to install with a local account, 
>> but not with a domain account logged in.
>>
>> --
>> 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 vagrant-up+...@googlegroups.com .
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/vagrant-up/7e71859f-e16c-41c0-84dd-482be9571082%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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/3bcaff39-9ddb-4b5e-b81b-73690e93bc09%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

2017-11-15 Thread Alvaro Miranda Aguilera
Hello

We haven't been able to reproduce this particular error.

We did release 5.0.3 that includes the fix for the machine on the domain,
but I am able to install and run VMs with either local user or domain user.

Does the error happens at install time of the plugin or after the install
on the vagrant commands?

Can you share a verbose error? (just add --debug to the command)

Also, some information.

I am testing with win10 pro, english lang. windows 2016 AD domain.

Thanks
Alvaro

On Tue, Nov 14, 2017 at 4:01 PM, Eric Beach  wrote:

> Unfortunately, no, not yet.   I was able to install with a local account,
> but not with a domain account logged in.
>
> --
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/7e71859f-e16c-41c0-84dd-482be9571082%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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyFn4bnehF5VzH%2Bn4JgOiyW8z%2Bpkxjbm7mZpjr8Q8PR%2BA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

2017-11-15 Thread Alvaro Miranda Aguilera
can you email supp...@hashicorp.com with a description on your setup?

Thanks
Alvaro

On Tue, Nov 14, 2017 at 8:07 AM, Arvind Prabhakar 
wrote:

> Did you get any solution to this issue? I'm having similar issue.
>
>
> On Friday, November 10, 2017 at 12:11:44 AM UTC+5:30, Eric Beach wrote:
>>
>> Attempting to install the plugin on a domain-joined computer with a
>> domain account fails.  I was able to install to the same computer running a
>> local account.
>>
>> PS C:\> vagrant plugin install vagrant-vmware-workstation
>> Installing the 'vagrant-vmware-workstation' plugin. This can take a few
>> minutes...
>> Fetching: vagrant-share-1.1.9.gem (100%)
>> Fetching: vagrant-vmware-workstation-5.0.3.gem (100%)
>> Building native extensions.  This could take a while...
>> Administator failed to take ownership of install directory
>> Bundler, the underlying system Vagrant uses to install plugins,
>> reported an error. The error is shown below. These errors are usually
>> caused by misconfigured plugin installations or transient network
>> issues. The error from Bundler is:
>>
>> ERROR: Failed to build gem native extension.
>>
>> current directory: C:/Users//.vagrant.d/gems/
>> 2.4.2/gems/vagrant-vmware-workstation-5.0.3/ext/vagrant-vmware-desktop
>> C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -r
>> ./siteconf20171109-5712-114qzcn.rb extconf.rb
>>
>> Folder: \
>> TaskName Next Run Time  Status
>>  ==
>> ===
>> vagrant-vmware-desktop--N/AReady
>> A subdirectory or file C:\ProgramData\HashiCorp\VagrantVMware\-\bin
>> already exists.
>> A subdirectory or file 
>> C:\ProgramData\HashiCorp\VagrantVMware\-\UserData
>> already exists.
>> 1 file(s) copied.
>> 1 file(s) moved.
>> processed file: C:\ProgramData\HashiCorp\VagrantVMware\-\UserData
>> Successfully processed 1 files; Failed processing 0 files
>> No mapping between account names and security IDs was done.
>> Successfully processed 0 files; Failed processing 0 files
>> 'Administrator"' is not recognized as an internal or external command,
>> operable program or batch file.
>> *** extconf.rb failed ***
>> Could not create Makefile due to some reason, probably lack of necessary
>> libraries and/or headers.  Check the mkmf.log file for more details.  You
>> may
>> need configuration options.
>>
>> Provided configuration options:
>> --with-opt-dir
>> --without-opt-dir
>> --with-opt-include
>> --without-opt-include=${opt-dir}/include
>> --with-opt-lib
>> --without-opt-lib=${opt-dir}/lib
>> --with-make-prog
>> --without-make-prog
>> --srcdir=.
>> --curdir
>> --ruby=C:/HashiCorp/Vagrant/embedded/mingw64/bin/$(RUBY_BASE
>> _NAME)
>>
>> extconf failed, exit code 1
>>
>> Gem files will remain installed in C:/Users//.vagrant.d/gems/
>> 2.4.2/gems/vagrant-vmware-workstation-5.0.3 for inspection.
>> Results logged to C:/Users//.vagrant.d/gems/
>> 2.4.2/extensions/x64-mingw32/2.4.0/vagrant-vmware-workstatio
>> n-5.0.3/gem_make.out
>>
> --
> 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 vagrant-up+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/vagrant-up/fe0ce4db-b45c-448a-912f-1167559987bd%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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/CAHqq0exUmXochaVw4quudbd9ypoq7RefZP2AKm2g25pG9fUBeg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

2017-11-14 Thread Eric Beach
Unfortunately, no, not yet.   I was able to install with a local account, but 
not with a domain account logged in.   

-- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/7e71859f-e16c-41c0-84dd-482be9571082%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[vagrant-up] Re: Can't install vagrant-vmware-workstation 5.0.3

2017-11-13 Thread Arvind Prabhakar
Did you get any solution to this issue? I'm having similar issue.

On Friday, November 10, 2017 at 12:11:44 AM UTC+5:30, Eric Beach wrote:
>
> Attempting to install the plugin on a domain-joined computer with a domain 
> account fails.  I was able to install to the same computer running a local 
> account.  
>
> PS C:\> vagrant plugin install vagrant-vmware-workstation
> Installing the 'vagrant-vmware-workstation' plugin. This can take a few 
> minutes...
> Fetching: vagrant-share-1.1.9.gem (100%)
> Fetching: vagrant-vmware-workstation-5.0.3.gem (100%)
> Building native extensions.  This could take a while...
> Administator failed to take ownership of install directory
> Bundler, the underlying system Vagrant uses to install plugins,
> reported an error. The error is shown below. These errors are usually
> caused by misconfigured plugin installations or transient network
> issues. The error from Bundler is:
>
> ERROR: Failed to build gem native extension.
>
> current directory: 
> C:/Users//.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.3/ext/vagrant-vmware-desktop
> C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -r 
> ./siteconf20171109-5712-114qzcn.rb extconf.rb
>
> Folder: \
> TaskName Next Run Time  Status
>  == 
> ===
> vagrant-vmware-desktop--N/AReady
> A subdirectory or file 
> C:\ProgramData\HashiCorp\VagrantVMware\-\bin already exists.
> A subdirectory or file 
> C:\ProgramData\HashiCorp\VagrantVMware\-\UserData already exists.
> 1 file(s) copied.
> 1 file(s) moved.
> processed file: C:\ProgramData\HashiCorp\VagrantVMware\-\UserData
> Successfully processed 1 files; Failed processing 0 files
> No mapping between account names and security IDs was done.
> Successfully processed 0 files; Failed processing 0 files
> 'Administrator"' is not recognized as an internal or external command,
> operable program or batch file.
> *** extconf.rb failed ***
> Could not create Makefile due to some reason, probably lack of necessary
> libraries and/or headers.  Check the mkmf.log file for more details.  You 
> may
> need configuration options.
>
> Provided configuration options:
> --with-opt-dir
> --without-opt-dir
> --with-opt-include
> --without-opt-include=${opt-dir}/include
> --with-opt-lib
> --without-opt-lib=${opt-dir}/lib
> --with-make-prog
> --without-make-prog
> --srcdir=.
> --curdir
> --ruby=C:/HashiCorp/Vagrant/embedded/mingw64/bin/$(RUBY_BASE_NAME)
>
> extconf failed, exit code 1
>
> Gem files will remain installed in 
> C:/Users//.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.3 
> for inspection.
> Results logged to 
> C:/Users//.vagrant.d/gems/2.4.2/extensions/x64-mingw32/2.4.0/vagrant-vmware-workstation-5.0.3/gem_make.out
>

-- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/fe0ce4db-b45c-448a-912f-1167559987bd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.