Closed spuder closed 9 years ago
Please reproduce this without plugins, and we'll take a look! Sorry but we have to narrow the repro case down to get one.
I reproduced this again, it is caused by adding a machine to active directory. This causes the Vagrant user to loose administrative privileges. Without local administrative privileges, the vagrant user can not execute winRM.
I've sort of worked around the issue by running the following command to add vagrant back to the local administrators group.
config.vm.provision 'shell', inline: 'net localgroup administrators vagrant /add'
While attempting to provision a windows VM, it gave the following errors
If I run with debugging info, this is what it shows
Here is the full vagrant file
I'm not sure how to reproduce this, but I suspect it has something to do with the following things that I did.