{"action":"created","issue":{"url":"https://api.github.com/repos/ferventcoder/vagrant-windows-puppet/issues/6","labels_url":"https://api.github.com/repos/ferventcoder/vagrant-windows-puppet/issues/6/labels{/name}","comments_url":"https://api.github.com/repos/ferventcoder/vagrant-windows-puppet/issues/6/comments","events_url":"https://api.github.com/repos/ferventcoder/vagrant-windows-puppet/issues/6/events","html_url":"https://github.com/ferventcoder/vagrant-windows-puppet/issues/6","id":88492547,"number":6,"title":"Puppet set PATH not working and fail puppet calls later","user":{"login":"iDVB","id":189506,"avatar_url":"https://avatars.githubusercontent.com/u/189506?v=3","gravatar_id":"","url":"https://api.github.com/users/iDVB","html_url":"https://github.com/iDVB","followers_url":"https://api.github.com/users/iDVB/followers","following_url":"https://api.github.com/users/iDVB/following{/other_user}","gists_url":"https://api.github.com/users/iDVB/gists{/gist_id}","starred_url":"https://api.github.com/users/iDVB/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/iDVB/subscriptions","organizations_url":"https://api.github.com/users/iDVB/orgs","repos_url":"https://api.github.com/users/iDVB/repos","events_url":"https://api.github.com/users/iDVB/events{/privacy}","received_events_url":"https://api.github.com/users/iDVB/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":24,"created_at":"2015-06-15T17:40:54Z","updated_at":"2015-06-16T02:50:51Z","closed_at":null,"body":"When running `vagrant up` for `win7x64pro-vagrant` it seems to run almost flawlessly until it trys to make puppet calls.\r\n\r\nIt's failing because the PATH vars are not being set. Which errors with ... \"The term 'puppet' is not recognized as the name of a cmdlet\"\r\n![Puppet PATH not set](http://goo.gl/F6Jx4Z)\r\n\r\nWhen Manually setting the path in the VM and then manually calling `puppet` I can then see that the path is correctly set.\r\n\r\nIs there a chance these scripts could be broken somewhere, or am I doing something wrong?\r\n\r\n```\r\nVirtualbox: 4.3.26\r\nVagrant: 1.7.2\r\nHost: OSX 10.10.3\r\n```\r\n\r\nUPDATE - Only other thing I can think of is that maybe the windows licensing prompt is crapping out the scripts? I intend to license only IF I can actually get this to work.\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/ferventcoder/vagrant-windows-puppet/issues/comments/112265766","html_url":"https://github.com/ferventcoder/vagrant-windows-puppet/issues/6#issuecomment-112265766","issue_url":"https://api.github.com/repos/ferventcoder/vagrant-windows-puppet/issues/6","id":112265766,"user":{"login":"ferventcoder","id":63502,"avatar_url":"https://avatars.githubusercontent.com/u/63502?v=3","gravatar_id":"","url":"https://api.github.com/users/ferventcoder","html_url":"https://github.com/ferventcoder","followers_url":"https://api.github.com/users/ferventcoder/followers","following_url":"https://api.github.com/users/ferventcoder/following{/other_user}","gists_url":"https://api.github.com/users/ferventcoder/gists{/gist_id}","starred_url":"https://api.github.com/users/ferventcoder/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/ferventcoder/subscriptions","organizations_url":"https://api.github.com/users/ferventcoder/orgs","repos_url":"https://api.github.com/users/ferventcoder/repos","events_url":"https://api.github.com/users/ferventcoder/events{/privacy}","received_events_url":"https://api.github.com/users/ferventcoder/received_events","type":"User","site_admin":false},"created_at":"2015-06-16T02:50:51Z","updated_at":"2015-06-16T02:50:51Z","body":"> Also, not sure if its normal, but I noticed all of these end up running the VM GUI where as I'll my personal tested prior to this ran things headless. Also the Docs talk about that being the default as well?\r\n\r\nThis is set up to be the default in https://github.com/ferventcoder/vagrant-windows-puppet/blob/master/boxes/VagrantWindows.rb#L8"}}