Install .NET framework via powershell through shell provider not working about vagrant-windows HOT 13 CLOSED

You need to use a scheduled task to elevate to true admin privileges. The Chef provisioners in vagrant-windows do this automatically for you, the others do not.

from vagrant-windows.

@sneal I've gone over this with @ferventcoder and it actually appears to work on some baseboxes but not others... (same exact powershell script and Vagrantfile) so it appears to possibly be more of locking down the exact steps for configuring a winrm basebox properly. @ferventcoder's basebox includes ssh so the thought is maybe the script is working on his because its using ssh vs winrm? Trying to properly diagnose this for consistent basebox builds.
chocolatey/puppet-chocolatey-handsonlab#5
So you think using scheduled task is still the answer here?
Any idea when the other provisioners will support elevated privs? Documentation appears that elevated is default.

from vagrant-windows.

Using SSH is going to behave completely differently than WinRM - security, environment, and limitations. For non-trivial software installs SSH is even more problematic than WinRM.

If you want installers to behave like they do when running locally on the box the most reliable and consistent way is to use a scheduled task - regardless of transport.

from vagrant-windows.

ok but since it works on some base boxes and doesn't on others there has to
be a difference being met in the vagrant-windows requirements that's
unclear. anyone able to pull down that repo and help me understand the
underlying issue with the basebox? (base_setup.ps1 as you see handles all
the requirements so there must be something missing)

from vagrant-windows.

I use Packer to build my base boxes. The Autounattend.xml here does something very similar to what your base_setup.ps1 script does.

I haven't seen a consistent way to install all Windows software over SSH or WinRM without the scheduled task trickery. If you figure out a better way that would be awesome.

from vagrant-windows.

I also shut off UAC. Perhaps that's the difference?

from vagrant-windows.

It appears you are installing .net framework 4.0. The next version of choco will install it automatically. It should be out soon. Be aware that it will assert privileges if UAC is turned on. So it's likely to fail in an automated fashion unless you have UAC turned off.

_sigh_ - UAC was built to be secure but there is no sudo, so it's somewhat useless for those who would script installation.

from vagrant-windows.

@ferventcoder the base_setup.ps1 disables UAC along with complex passwords and a bunch of other things https://github.com/cdenneen/vagrant-windows-build/blob/master/base_setup.ps1

from vagrant-windows.

Dumb question from me, is there a reboot after UAC is disabled?

from vagrant-windows.

bottom of the ps1 it restarts the computer... then i create basebox...

from vagrant-windows.

@cdenneen I just starred that. I need some of those items to packerize my boxes :)

from vagrant-windows.

@ferventcoder well maybe looking at that you can see something I missed to make my basebox like yours (that works with .NET ps1 install?)... I do a base install of windows, run that script (actually going to modify that to do the administrator -> vagrant user rename and password) and create box.

from vagrant-windows.

I don't yet see what could cause it unfortunately.

from vagrant-windows.