PowerShell PackageManagement (OneGet) - Install Apps from Command Line

Kari · 05 Jan 2017

For the first, the video you are referring to and packages (programs) I install in it are only meant to be an example. You can of course install whatever you want to, you don't have to install exactly the same packages as me in the example.

At the moment there seem to issues with several Chocolatey packages. Chrome, Firefox, various Office365 packages, VLC and several other packages do not install correctly. Any software not installing correctly must be installed directly from software maker's site, Chrome from Google, Firefox from Mozilla and so on.

List of packages available at Chocolatey: Chocolatey Gallery | Packages (but, as I mentioned, at the moment there are a few packages listed there which do not actually work).

You could also try to install Chocolatey and use it directly instead of PowerShell PackageManagement, instructions here: Installation. I'm not sure if those missing packages install any better using Chocolatey directly but it might be worth a try.

Kari

etbonney · 06 Jan 2017

Kari,

Thank you for the reply. I will look at the Power Shell guides and become more familiar with the packages once I get the basics of creating VM reference images and proper deployment techniques with the Windows 10 ADK. I am coming from much older imaging techniques (most notably Ghost) so I'm still learning the basics.

Ron

mta3006 · 02 Jan 2019

@Kari,

I searched the forum for 'local package repository' but got no pertinent results. Having read most of this tut, it seems to me that if one were mistrustful of the idea of web-based repositories, one could still benefit from creating a 'local repository' of software packages, starting from installation files collected from trusted application vendor sites. Is this possible, and what sort of modifications would be needed to the vendor-provided install files?

Many thanks for all your contributions to this forum!

Kari · 02 Jan 2019

mta3006 said:

[MENTION=1291]... it seems to me that if one were mistrustful of the idea of web-based repositories, one could still benefit from creating a 'local repository' of software packages, starting from installation files collected from trusted application vendor sites. Is this possible, and what sort of modifications would be needed to the vendor-provided install files?

See this post on PowerShell Team Blog: Setting up an Internal PowerShellGet Repository | PowerShell Team Blog

Kari

Wynona · 03 Jan 2019

Kari said:

See this post on PowerShell Team Blog: Setting up an Internal PowerShellGet Repository | PowerShell Team Blog

Kari

Good morning, Kari.

This is from 2014; will it still be viable?

Kari · 03 Jan 2019

Wynona said:

Good morning, Kari.

This is from 2014; will it still be viable?

PS Packet management has lost some features lately. Today, I prefer Chocolatey as the packet manager on my machines. See the tutorial on our sister site EightForums.com: Chocolatey - Install Apps from Command Line Tutorial | Windows 8 Help Forums

Kari