Hello, Vagrant uses user and password for Winrm, so if after login the script gets a prompt like "you need to change the password" it may cause problems as its un-expected output.. I am thinking out loud here as I haven't test or checked the software code.
As for VMs in atlas, hashicorp provides the boxes under hashicorp/ user only. The rest are community based ones. If you are after a Windows 10 that can be activated, I am not sure the ones in atlas will work. My understanding is due licensing, most of the people have access to Win10 Evaluation only. If you have an specific ISO you would like to use, perhaps the best will be create your own vagrant box? The windows image I did suggest came from here: https://github.com/MattHodge/PackerTemplates There is a build ps1 script that have options to build a win10 too. Let me know how it goes. Those boxes are to be built using packer that is also a HashiCorp product. Thanks Alvaro. On Mon, Oct 10, 2016 at 3:46 AM, Megan Adams <lucid...@gmail.com> wrote: > Thanks for your reply. > > This problem went away and these are the circumstances: > > The first box I used was the only vmware workstation windows 10 box on > atlas hashicorp. It turned out that windows version was a pre build for > windows 10 and it was so old it was abandoned, it could not be activated. > (Side question: it shouldn't be on atlas hashicorp but I didn't see a spot > for comments or reviews, where can I provide this comment?) > Anyway that old version came up in vmware workstation okay but it > immediately told me I had an old password and had to change it. So I did. > Then I discovered this was a useless windows version and got another > version. > > HOWEVER the next windows 10 version box which I got ran into the winrm > authorization problem and I could not get it through 'vagrant up'. > > Then I tried getting to it via vmware and got into it (tho it wasn't > provisioned) and the password was not vagrant. Does the password setting > become part of some global vagrant state? After I changed the password to > vagrant the winrm authorization problem went away. > > lucidbee > > > > On Sunday, October 9, 2016 at 11:45:17 AM UTC-7, Alvaro Miranda Aguilera > wrote: >> >> Hello >> >> Can you try a different box? >> >> I just test this one and works fine witn WinRM: >> >> MattHodge/Windows2012R2-WMF5-NOCM >> <https://atlas.hashicorp.com/MattHodge/boxes/Windows2012R2-WMF5-NOCM> >> >> The messages you see on the DEBUG, are Vagrant logic, in the first part >> of the run, Vagrant goes to all the variables and move them to a separate >> context, basically to be able to load ruby plugins etc without getting >> confused with the OS ones. >> >> Thanks >> Alvaro. >> >> On Fri, Oct 7, 2016 at 2:19 AM, Megan Adams <luci...@gmail.com> wrote: >> >>> I have an ubuntu 16.04 host and I'm trying to bring up a windows 10 box, >>> vmware. >>> >>> vagrant 1.8.6 >>> vagrant-workstation plugin 4.0.13 >>> >>> No go. The provision fails and I cannot ssh into it but I can get into >>> the vm with vmware and it is a windows 10 system, unprovisioned. >>> >>> Any tips much appreciated. >>> >>> This box was made with packer, I did not make it. This trace excerpt >>> below is towards the end of the vagrant up --debug >>> >>> INFO host: Execute capability: nfs_prune [#<Vagrant::Environment: >>> /home/lucidbee/brain3/B>, #<Vagrant::UI::Prefixed:0x000000012e0670 >>> @logger=#<Log4r::Logger:0x000000012e0620 @fullname="vagrant::ui::interface", >>> @outputters=[], @additive=true, @name="interface", @path="vagrant::ui", >>> @parent=#<Log4r::Logger:0x00000001f3bde8 @fullname="vagrant", >>> @outputters=[#<Log4r::StderrOutputter:0x00000001f62c18 @mon_owner=nil, >>> @mon_count=0, @mon_mutex=#<Mutex:0x00000001f62ba0>, @name="stderr", >>> @level=0, @formatter=#<Log4r::DefaultFormatter:0x000000012151a0 >>> @depth=7>, @out=#<IO:<STDERR>>>], @additive=true, @name="vagrant", >>> @path="", @parent=#<Log4r::RootLogger:0x00000001f3bcd0 @level=0, >>> @outputters=[]>, @level=1, @trace=false>, @level=1, @trace=false>, >>> @opts={}, @stdin=#<IO:<STDIN>>, @stdout=#<IO:<STDOUT>>, >>> @stderr=#<IO:<STDERR>>, @prefix=:windev10, >>> @ui=#<Vagrant::UI::Basic:0x00000001f9b478 >>> @logger=#<Log4r::Logger:0x00000001f9b428 @fullname="vagrant::ui::interface", >>> @outputters=[], @additive=true, @name="interface", @path="vagrant::ui", >>> @parent=#<Log4r::Logger:0x00000001f3bde8 @fullname="vagrant", >>> @outputters=[#<Log4r::StderrOutputter:0x00000001f62c18 @mon_owner=nil, >>> @mon_count=0, @mon_mutex=#<Mutex:0x00000001f62ba0>, @name="stderr", >>> @level=0, @formatter=#<Log4r::DefaultFormatter:0x000000012151a0 >>> @depth=7>, @out=#<IO:<STDERR>>>], @additive=true, @name="vagrant", >>> @path="", @parent=#<Log4r::RootLogger:0x00000001f3bcd0 @level=0, >>> @outputters=[]>, @level=1, @trace=false>, @level=1, @trace=false>, >>> @opts={:color=>:default}, @stdin=#<IO:<STDIN>>, @stdout=#<IO:<STDOUT>>, >>> @stderr=#<IO:<STDERR>>, @lock=#<Mutex:0x00000001f6c808>>>, []] (linux)$ >>> INFO warden: Calling IN action: #<Vagrant::Action::Builtin::Sy >>> ncedFolderCleanup:0x00000002f85be0>$ >>> INFO synced_folder_cleanup: Invoking synced folder cleanup for: vmware$ >>> INFO warden: Calling IN action: #<Proc:0x00000002ef59f0@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling IN action: #<Proc:0x00000001ee8d78@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Proc:0x00000001ee8d78@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Proc:0x00000002ef59f0@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Sy >>> ncedFolderCleanup:0x00000002f85be0>$ >>> INFO warden: Calling OUT action: #<VagrantPlugins::SyncedFolder >>> NFS::ActionCleanup:0x00000002fd6720>$ >>> INFO warden: Calling OUT action: VMware Middleware: >>> PrepareSyncedFolderCleanup$ >>> INFO warden: Calling OUT action: VMware Middleware: PruneForwardedPorts$ >>> INFO warden: Calling OUT action: VMware Middleware: Destroy$ >>> INFO warden: Calling OUT action: #<Proc:0x00000002c61ef0@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Proc:0x000000029afab8@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Proc:0x00000001dbbc70@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: VMware Middleware: WaitForVMXHalt$ >>> INFO warden: Calling OUT action: VMware Middleware: Halt$ >>> INFO warden: Calling OUT action: VMware Middleware: >>> DiscardSuspendedState$ >>> INFO warden: Calling OUT action: #<Proc:0x00000001d14498@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Ca >>> ll:0x000000029afb58>$ >>> INFO warden: Calling OUT action: #<Proc:0x0000000296dbb8@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Ca >>> ll:0x00000002c61f68>$ >>> INFO warden: Calling OUT action: VMware Middleware: >>> DiscardSuspendedState$ >>> INFO warden: Calling OUT action: #<Proc:0x00000002c0f6c8@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Ca >>> ll:0x00000000f12520>$ >>> INFO warden: Calling OUT action: VMware Middleware: SudoHelperInstall$ >>> INFO warden: Calling OUT action: VMware Middleware: CheckVMware$ >>> INFO warden: Calling OUT action: VMware Middleware: FixOldMachineID$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Co >>> nfigValidate:0x000000014ff1b8>$ >>> INFO warden: Calling OUT action: VMware Middleware: Compatibility$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::En >>> vSet:0x000000014ff6e0>$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Pr >>> ovisionerCleanup:0x00000001586758>$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Co >>> nfigValidate:0x000000015867d0>$ >>> INFO warden: Calling OUT action: #<Proc:0x00000002ec6a10@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Ca >>> ll:0x00000001ee8eb8>$ >>> INFO warden: Calling OUT action: #<Proc:0x00000001e54830@/opt/v >>> agrant/embedded/gems/gems/vagrant-1.8.6/lib/vagrant/action/warden.rb:94 >>> (lambda)>$ >>> INFO warden: Calling OUT action: #<Vagrant::Action::Builtin::Ca >>> ll:0x000000029bbcf0>$ >>> INFO warden: Calling OUT action: VMware Middleware: SudoHelperInstall$ >>> INFO warden: Calling OUT action: VMware Middleware: FixOldMachineID$ >>> INFO warden: Calling OUT action: VMware Middleware: Compatibility$ >>> INFO warden: Recovery complete.$ >>> INFO warden: Beginning recovery process...$ >>> INFO warden: Recovery complete.$ >>> INFO warden: Beginning recovery process...$ >>> INFO warden: Recovery complete.$ >>> INFO warden: Beginning recovery process...$ >>> INFO warden: Recovery complete.$ >>> INFO warden: Beginning recovery process...$ >>> INFO warden: Recovery complete.$ >>> INFO warden: Beginning recovery process...$ >>> INFO warden: Recovery complete.$ >>> INFO warden: Beginning recovery process...$ >>> INFO warden: Recovery complete.$ >>> INFO warden: Beginning recovery process...$ >>> INFO warden: Recovery complete.$ >>> INFO warden: Beginning recovery process...$ >>> INFO warden: Recovery complete.$ >>> ERROR warden: Error occurred: WinRM::WinRMAuthorizationError$ >>> >>> and then there's a stack trace. >>> >>> I'm getting alot of 'command not in installer' messages in the trace: >>> >>> DEBUG subprocess: stderr: INFO subprocess: Starting process: >>> ["/etc/init.d/vmware", "status"] >>> DEBUG subprocess: stderr: INFO subprocess: Command not in installer, >>> restoring original environment... <====/etc/init.d/vmware DOES EXIST >>> DEBUG subprocess: stderr: DEBUG subprocess: Selecting on IO >>> DEBUG subprocess: stderr: DEBUG subprocess: stdout: Module vmmon >>> DEBUG subprocess: stderr: DEBUG subprocess: stdout: loaded >>> Module vmnet >>> DEBUG subprocess: stderr: DEBUG subprocess: stdout: loaded >>> DEBUG subprocess: stderr: DEBUG subprocess: Waiting for process to exit. >>> Remaining to timeout: 31997 >>> DEBUG subprocess: Exit status: 0 >>> DEBUG subprocess: stderr: INFO vmware_driver: Checking status of VMware >>> network services... >>> DEBUG subprocess: stderr: INFO subprocess: Starting process: >>> ["/usr/bin/vmware-networks", "--status"] >>> DEBUG subprocess: stderr: INFO subprocess: Command not in installer, >>> restoring original environment... <==== DOES EXIST >>> >>> -- >>> 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/6a046459-5ae0-4923-82d8-fe55042e68f4%40googlegroups.com >>> <https://groups.google.com/d/msgid/vagrant-up/6a046459-5ae0-4923-82d8-fe55042e68f4%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> 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/6c9c696e-a173-425b-bcf6-7928e2b0a127%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/6c9c696e-a173-425b-bcf6-7928e2b0a127%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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/CAHqq0exquTCvst_K9We5KF-5vkmQosHCWrAFY0EV1YNQE-AVWw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
