2014-03-14 18:23:07 +00:00
|
|
|
en:
|
2014-06-10 05:46:03 +00:00
|
|
|
vagrant_windows:
|
2014-03-14 18:23:07 +00:00
|
|
|
errors:
|
|
|
|
cant_read_mac_addresses: |-
|
|
|
|
The provider being used to start Windows ('%{provider}')
|
|
|
|
doesn't support the "nic_mac_addresses" capability which is required
|
|
|
|
for advanced networking to work with Windows guests. Please inform
|
|
|
|
the author of the provider to add this feature.
|
|
|
|
|
|
|
|
Until then, you must remove any networking configurations other
|
|
|
|
than forwarded ports from your Vagrantfile for Vagrant to continue.
|
2014-05-07 02:00:58 +00:00
|
|
|
network_winrm_required: |-
|
|
|
|
Configuring networks on Windows requires the communicator to be
|
|
|
|
set to WinRM. To do this, add the following to your Vagrantfile:
|
|
|
|
|
|
|
|
config.vm.communicator = "winrm"
|
|
|
|
|
|
|
|
Note that the Windows guest must be configured to accept insecure
|
|
|
|
WinRM connections, and the WinRM port must be forwarded properly from
|
|
|
|
the guest machine. This is not always done by default.
|
2014-06-10 05:46:03 +00:00
|
|
|
rename_computer_failed: |-
|
|
|
|
Renaming the Windows guest failed. Most often this is because you've
|
|
|
|
specified a FQDN instead of just a host name.
|
|
|
|
|
|
|
|
Ensure the new guest name is properly formatted. Standard names may
|
|
|
|
contain letters (a-z, A-Z), numbers (0-9), and hypens (-), but no
|
|
|
|
spaces or periods (.). The name may not consist entirely of digits.
|