However, when building a windows image in Rackspace the Administrator password is automatically generated by Rackspace, and is also the default password for the Administrator account for WinRM authentication (once WinRM is enabled). Shouldn't Vagrant automatically be setting windows.winrm.password to the password generated by Rackspace (and subsequently returned by Rackspace when initially creating the VM)?
Issue is that, in local development (VirtualBox) I can control the Administrator Username/Password that is baked into the image... but for VM's created by Rackspace the password is automatically generated. I guess I'm just not connecting the dots to how using ENV['VAGRANT_ADMIN_PASSWORD'] will work if Rackspace is generating the password?
derks
commented
8 years ago
In the README, the following is referenced in the example Vagrantfile regarding Windows configuration:
However, when building a windows image in Rackspace the Administrator password is automatically generated by Rackspace, and is also the default password for the Administrator account for WinRM authentication (once WinRM is enabled). Shouldn't Vagrant automatically be setting
windows.winrm.passwordto the password generated by Rackspace (and subsequently returned by Rackspace when initially creating the VM)?Issue is that, in local development (VirtualBox) I can control the Administrator Username/Password that is baked into the image... but for VM's created by Rackspace the password is automatically generated. I guess I'm just not connecting the dots to how using
ENV['VAGRANT_ADMIN_PASSWORD']will work if Rackspace is generating the password?Thanks... any help is appreciated.