I wanted to add the SSH client as an optional feature on my Win10 now when it was available but I got an error when using the command “Add–WindowsCapability–Online–Name OpenSSH.Client~~~~0.0.1.0″
after a little bit of digging i could find out that my dear IT department had set a GPO which was not letting me get the bits:
So after I had changed the value to 0 and done a reboot, I was able to install the SSH client optional feature
Great success and using ssh from the cmd prompt gives me the following :
I created a new Windows 10 client in my Mac that I have in an assignment and that on VirtualBox. I made it to small of course and when trying to add some stuff with onedrive sync I could not succeed …
So to be able to expand the underlying disk in virtualbox I had to go into terminal mode as this is not part of the gui which of course is okay, so find your vdi file and possible if you are afraid, do a copy of the file before and of course the VM have to be stopped during the expansion.
Using command VBoxManage modifymedium disk xxxx.vdi –resizebytes 85899345920
and checking the properties on the virtual disk file I can see that it has been expanded
after that you boot the VM and go into windows disk settings and expand the partition and you are ready to add files 🙂
I wanted to install the different browsers and also ChefDK on an new Windows 10 client and that with PowerShell. There is of course a way to just run Chocolatey command line but I wanted to use the PackageManagement so I had to add that provider and source so I could just use the Install-Package cmdlet.
I have a Windows 10 1511 with latest patches and I run the following commands to enable the chocolatey repository:
As you can see, when I enter Find-PackageProvider I find the Chocolatey provider and just run the Install-PackageProvider -Name Chocolatey
Then I need to open a new PowerShell window and can see that the PackageProvider and PackageSource have the Chocolatey records and thus I can now add software from this,
First I add Firefox and as you can see my PackageSource is not trusted and I get an warning, that can be configured with the Set-PackageSource -Name chocolatey -Trusted
I have upgraded my windows 10 to the latest build 10041 and activated Hyper-V.
In this build I can see that there are now 211 cmdlets in the hyper-v PowerShell module:
And comparing it to the PowerShell module that was released in Windows 8.1/2012 R2 you can see the following new cmdlets, although the Windows 10 is in preview and things can change before it is released!
I will dig into the new preview release and maybe there will be a followup post on my findings!