Hello, In enterprise world is something called Standard Operating Environment <https://en.wikipedia.org/wiki/Standard_Operating_Environment>
So basically what you have found is that Vagrant is not included in there in your company. I would suggest to open a ticket and let them to know the business requirement and ask them to review and approve the application. Vagrant and vagrant-installer are open source, and free of cost to use, so perhaps they can have a fast-track to add this application. good luck! Thanks Alvaro. On Wed, Mar 30, 2016 at 7:45 AM, Scott Johnson <[email protected]> wrote: > Thanks for the reply. I uninstalled the latest Microsoft Security updates > and it started to work again. Then the updates were automatically > restored. > So I gave up on my Windows use of Vagrant in my corporate environment. > > > On Monday, March 28, 2016 at 9:27:26 AM UTC-4, Scott Johnson wrote: >> >> I have been using my Windows 7 enterprise based Vagrant setup for two >> weeks now. It uses Vagrant 1.18, Git for Windows, and VirtualBox. I left >> it running and was happily using the service it provides. Then I tried to >> use "vagrant ssh" to connect and I got an error. I soon found that no >> vagrant commands work from Git Bash or CMD. Focusing on CMD I am baffled >> that I now get a stacktrace whenever I try to run a vagrant command. >> >> I posted the issue to StackOverflow. The callstack is listed there. >> >> http://stackoverflow.com/questions/36221690/vagrant-stopped-working-access-denied >> >> Can anyone read the Ruby(?) callstack and give me something to go on? My >> best theory is that my employer changed the configuration of the machine as >> part of a security update. If the error could just tell me which directory >> or which file it was trying to access then I'd at least have a lead. >> >> Thanks, >> Scott >> > -- > 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 [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/vagrant-up/82b74735-2ac4-4a02-bfde-84f7d044dbfa%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/82b74735-2ac4-4a02-bfde-84f7d044dbfa%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eyBPQNrVMcFNxZPm%3DUixgWW2xw6OW1gFVEsxEj1ba%2BCtg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
