{"id":2357,"date":"2015-02-26T01:04:05","date_gmt":"2015-02-25T21:04:05","guid":{"rendered":"https:\/\/rakhesh.com\/?p=2357"},"modified":"2015-02-26T01:04:05","modified_gmt":"2015-02-25T21:04:05","slug":"notes-of-powershell-dsc-course-oneget-chocolatey","status":"publish","type":"post","link":"https:\/\/rakhesh.com\/windows\/notes-of-powershell-dsc-course-oneget-chocolatey\/","title":{"rendered":"Notes of PowerShell DSC course, OneGet &#038; Chocolatey"},"content":{"rendered":"<p>Spent the past hour and half attending this course &#8211;\u00a0<a href=\"http:\/\/www.microsoftvirtualacademy.com\/liveevents\/getting-started-with-powershell-desired-state-configuration-dsc\" target=\"_blank\">Getting started with PowerShell Desired State Configuration (DSC) Jump Start<\/a>, by Jeffrey Snover (inventor of PowerShell) and Jason Helmick. Had to give up coz my connection quality is so poor it kept freezing every now and then. Better to wait 2-3 weeks for the recorded version to be released so I can download and view. It&#8217;s a pity I couldn&#8217;t watch this though. I was looking forward to this course very much (and also its sequel\u00a0<a href=\"http:\/\/www.microsoftvirtualacademy.com\/liveevents\/advanced-powershell-desired-state-configuration-dsc-and-custom-resources\" target=\"_blank\">Advanced PowerShell Desired State Configuration (DSC) and Custom Resources<\/a> same time tomm which I will now have to skip).<\/p>\n<p>From the little bit that I did attend, here are some notes.<\/p>\n<h2>Desired State Configuration (DSC)<\/h2>\n<ul>\n<li>Desired State Configuration (DSC) is meant to be a platform. You have tools that can manage configuration changes. And you have the actual items which you configure. Usually the tools are written specifically for the item you wish to configure. So, a certain tool might be good at managing certain aspects of your environment but not that great at managing other aspects. What Microsoft&#8217;s goal here is to offer a platform for configuration tools. Jeffrey likens it to Word Processors and printers in the past. Whereas once upon a time Word Processors were tied to printers in that certain Word Processors only worked with certain printers, once Windows OS came along and it had the concept of print drivers, all that was required was for printer manufacturers to provide drivers for their model and Word Processors to target this driver model and soon all Word Processors could print to all printers. DSC has a similar aim.\u00a0<\/li>\n<li>DSC tends to get compared to GPOs a lot because they do similar things. But, (1) GPOs require domain joined machines &#8211; which DSC does not require &#8211; and (2) with a GPO you don&#8217;t have a way of knowing whether the policy applied successfully and\/ or what failed, while with DSC you have insight into that. Other differences are that GPOs are tied to Windows whereas DSC is standards based so works with Linux and *nix (and even <a href=\"http:\/\/blogs.technet.com\/b\/windowsserver\/archive\/2014\/04\/03\/windows-management-framework-v5-preview.aspx\" target=\"_blank\">network switches<\/a>!).\u00a0<\/li>\n<li>DSC is Distributed &amp; Heterogeneous. Meaning it&#8217;s meant to scale across a large number of devices or various types.\u00a0<\/li>\n<li>Local Configuration Manager (LCM) is a WMI agent that&#8217;s built into PowerShell 4 and above. <a href=\"http:\/\/blogs.msdn.com\/b\/powershell\/archive\/2013\/12\/09\/understanding-meta-configuration-in-windows-powershell-desired-state-configuration.aspx\" target=\"_blank\">It is the engine behind DSC<\/a>? (The presenters were starting to explain LCM in Module 2 which is when I finally gave up coz of the jerkiness).<\/li>\n<li>Windows Management Infrastructure (WMI) has an open source counterpart (created by Microsoft?) called <a href=\"http:\/\/blogs.technet.com\/b\/windowsserver\/archive\/2012\/06\/28\/open-management-infrastructure.aspx\" target=\"_blank\">Open Management Infrastructure<\/a> (OMI) for Linux and *nix machines. This is based on DMTF standards and protocols. Since LCM is based on WMI whose open source counterpart is OMI, LCM can work with Linux and *nix machines too.\u00a0<\/li>\n<li>DevOps model is the future. Release a minimal viable product (i.e. release a product that works with the minimum requirements and then quickly keep releasing improvements to it). Respect reality (i.e. release what you have in mind, collect customer feedback (reality), improve the product). Jeffrey Snover recommends <a href=\"http:\/\/smile.amazon.com\/Phoenix-Project-DevOps-Helping-Business-ebook\/dp\/B00AZRBLHO\/ref=tmm_kin_swatch_0?_encoding=UTF8&amp;sr=&amp;qid=\" target=\"_blank\">The Phoenix Project<\/a>, a novel on the DevOps style.\u00a0\n<ul>\n<li>Windows Management Framework (WMF) &#8211; which contains PowerShell, WMI, etc &#8211; now follows a DevOps style. New releases happen every few months in order to get feedback.\u00a0<\/li>\n<\/ul>\n<\/li>\n<\/ul>\n<h2>OneGet and friends<\/h2>\n<ul>\n<li><a href=\"https:\/\/www.nuget.org\/\" target=\"_blank\">NuGet<\/a> is a package manager for Visual Studio (and other Windows development platforms?). Developers use it to pull in development libraries. It is similar to the package managers for Perl, Ruby, Python, etc. I think.<\/li>\n<li><a style=\"line-height: 1.5;\" href=\"https:\/\/chocolatey.org\/\" target=\"_blank\">Chocolatey<\/a><span style=\"line-height: 1.5;\"> is a binary package manager, built on NuGet infrastructure, but for Windows. It is similar to <\/span><code style=\"line-height: 1.5;\">apt-get<\/code><span style=\"line-height: 1.5;\">, <\/span><code style=\"line-height: 1.5;\">yum<\/code><span style=\"line-height: 1.5;\">, etc. Chocolatey is what you would use as an end-user to install Chrome, for instance. <\/span><\/li>\n<li><a style=\"line-height: 1.5;\" href=\"https:\/\/github.com\/OneGet\/oneget\/wiki\/Q-and-A\" target=\"_blank\">OneGet<\/a><span style=\"line-height: 1.5;\"> is a package manager&#8217;s manager. It exposes APIs for package managers (such as Chocolatey) to tap into, as well as APIs for packages to utilize. OneGet is available in Windows 10 Technical Preview as well as in the <\/span><a style=\"line-height: 1.5;\" href=\"http:\/\/www.microsoft.com\/en-us\/download\/details.aspx?id=42316\" target=\"_blank\">WMF 5.0 Preview<\/a><span style=\"line-height: 1.5;\">. <\/span><a style=\"line-height: 1.5;\" href=\"http:\/\/blogs.msdn.com\/b\/garretts\/archive\/2014\/04\/01\/my-little-secret-windows-powershell-oneget.aspx\" target=\"_blank\">Here&#8217;s the blog post<\/a><span style=\"line-height: 1.5;\"> introducing OneGet. Basically, you can use a set of common cmdlets to install\/ uninstall packages, add\/ remove\/ query package repositories regardless of the installation technology. <\/span><\/li>\n<\/ul>\n<p><span style=\"line-height: 1.5;\">To my mind, an analogy would be that OneGet is something that can work with <\/span><code style=\"line-height: 1.5;\">deb<\/code><span style=\"line-height: 1.5;\"> and <\/span><code style=\"line-height: 1.5;\">rpm<\/code><span style=\"line-height: 1.5;\"> repositories (as well as repositories maintained by multiple entities such as say Ubuntu <code>deb<\/code> repositories, Debian <code>deb<\/code> repositories) and\u00a0as long as these repositories have a hook into OneGet. You, the end user, can then add repositories containing such packages and use a common set of cmdlets to manage it. <em>This is my understanding, I could be way off track here &#8230;\u00a0<\/em><\/span><\/p>\n<p>Installing WMF 5.0 preview on my Windows 8.1 machine, for instance, gets me a new module called <code>OneGet<\/code>. Here are the commands available to it:<\/p>\n<pre class=\"lang:ps decode:true\">PS&gt; Get-Command -Module OneGet\r\n\r\nCommandType     Name                                               Version    Source                                                                         \r\n-----------     ----                                               -------    ------                                                                         \r\nCmdlet          Find-Package                                       1.0.0.0    OneGet                                                                         \r\nCmdlet          Get-Package                                        1.0.0.0    OneGet                                                                         \r\nCmdlet          Get-PackageProvider                                1.0.0.0    OneGet                                                                         \r\nCmdlet          Get-PackageSource                                  1.0.0.0    OneGet                                                                         \r\nCmdlet          Install-Package                                    1.0.0.0    OneGet                                                                         \r\nCmdlet          Register-PackageSource                             1.0.0.0    OneGet                                                                         \r\nCmdlet          Save-Package                                       1.0.0.0    OneGet                                                                         \r\nCmdlet          Set-PackageSource                                  1.0.0.0    OneGet                                                                         \r\nCmdlet          Uninstall-Package                                  1.0.0.0    OneGet                                                                         \r\nCmdlet          Unregister-PackageSource                           1.0.0.0    OneGet                                                                         <\/pre>\n<p>As part of the course Jeffrey mentioned the <a href=\"https:\/\/www.powershellgallery.com\/\" target=\"_blank\">PowerShell Gallery<\/a>\u00a0which is a repository of PowerShell and DSC stuff. He mentioned two modules &#8211; <code>MVA_DSC_2015_DAY1<\/code> and <code>MVA_DSC_2015_DAY2<\/code>\u00a0&#8211; which would be worth installing to practice what is taught during the course.\u00a0The PowerShell Gallery has its own package manager called <code>PowerShellGet<\/code>\u00a0which has its own set of cmdlets.\u00a0<\/p>\n<pre class=\"lang:ps decode:true \">PS&gt; Get-Command -Module PowerShellGet\r\n\r\nCommandType     Name                                               Version    Source                                                                         \r\n-----------     ----                                               -------    ------                                                                         \r\nFunction        Find-Module                                        0.5        PowerShellGet                                                                  \r\nFunction        Get-PSRepository                                   0.5        PowerShellGet                                                                  \r\nFunction        Install-Module                                     0.5        PowerShellGet                                                                  \r\nFunction        Publish-Module                                     0.5        PowerShellGet                                                                  \r\nFunction        Register-PSRepository                              0.5        PowerShellGet                                                                  \r\nFunction        Set-PSRepository                                   0.5        PowerShellGet                                                                  \r\nFunction        Unregister-PSRepository                            0.5        PowerShellGet                                                                  \r\nFunction        Update-Module                                      0.5        PowerShellGet        <\/pre>\n<p>Notice there are cmdlets to find modules, install modules, and even publish modules to the repository. One way of installing modules from PowerShell Gallery would be to use the <code>PowerShellGet<\/code> cmdlets.\u00a0<\/p>\n<pre class=\"lang:ps decode:true\">PS&gt; Find-Module mva*\r\n\r\nNuGet-anycpu.exe is required to continue.\r\nPowerShellGet requires NuGet-anycpu.exe to interact with NuGet based galleries. NuGet-anycpu.exe must be available in\r\n'C:\\Program Files\\OneGet\\ProviderAssemblies' or 'C:\\Users\\Rakhesh\\AppData\\Local\\OneGet\\ProviderAssemblies'. For more\r\ninformation about NuGet provider, see http:\/\/oneget.org\/NuGet.html. Do you want PowerShellGet to download\r\nNuGet-anycpu.exe now?\r\n[Y] Yes  [N] No  [S] Suspend  [?] Help (default is \"Y\"):\r\n\r\nVersion    Name                                Repository           Description\r\n-------    ----                                ----------           -----------\r\n0.0.0.2    MVA_DSC_2015_DAY1                   PSGallery            This contains the presentations and modules asso...\r\n0.0.0.2    MVA_DSC_2015_DAY2                   PSGallery            This contains the presentations and modules asso...<\/pre>\n<p>Notice that it depends on NuGet to proceed. My guess is that NuGet is where the actual dependency resolution and other logic happens.\u00a0I can install the modules using another cmdlet from <code>PowerShellGet<\/code>:<\/p>\n<pre class=\"lang:ps decode:true\">PS&gt; Find-Module mva* | Install-Module\r\n\r\nYou are installing the module 'MVA_DSC_2015_DAY1' from an untrusted repository. If you trust this repository, change\r\nits InstallationPolicy value by running the Set-PSRepository cmdlet.\r\nAre you sure you want to install software from 'https:\/\/www.powershellgallery.com\/api\/v2\/'?\r\n[Y] Yes  [N] No  [S] Suspend  [?] Help (default is \"Y\"): y\r\n\r\nYou are installing the module 'MVA_DSC_2015_DAY2' from an untrusted repository. If you trust this repository, change\r\nits InstallationPolicy value by running the Set-PSRepository cmdlet.\r\nAre you sure you want to install software from 'https:\/\/www.powershellgallery.com\/api\/v2\/'?\r\n[Y] Yes  [N] No  [S] Suspend  [?] Help (default is \"Y\"):<\/pre>\n<p>Now, the interesting thing is that you can do these operations via <code>OneGet<\/code> too. Because remember, <code>OneGet<\/code> provides a common set of cmdlets for all these operations. You use the <code>OneGet<\/code> provided cmdlets and behind the scenes it will get the actual providers (like <code>PowerShellGet<\/code>) to do the work. (<strong><a href=\"http:\/\/www.powershellgallery.com\/pages\/GettingStarted\" target=\"_blank\">Update<\/a><\/strong>: Turns out it&#8217;s actually the reverse. Sort of. <code>Install-Module<\/code> from <code>PowerShellGet<\/code> actually invokes <code>Install-Package -Provider PSModule<\/code> from <code>OneGet<\/code>. This works because <code>PowerShellGet<\/code> hooks into <code>OneGet<\/code> with so <code>OneGet<\/code> knows how to use the <code>PowerShellGet<\/code> repository).\u00a0<\/p>\n<pre class=\"lang:ps decode:true\">PS&gt; Find-Module *fire*\r\n\r\nVersion    Name                                Repository           Description\r\n-------    ----                                ----------           -----------\r\n1.0.0      xFirefox                            PSGallery            Firefox Main module\r\n\r\n\r\nPS&gt; Find-Package *fire*\r\n\r\nName                          Version      Status       ProviderName     Source           Summary\r\n----                          -------      ------       ------------     ------           -------\r\nxFirefox                      1.0.0        Available    PSModule         https:\/\/www.p...\r\n\r\n\r\nPS&gt; Find-Package *fire* | Install-Package\r\n\r\nThe package 'xFirefox' comes from a package source that is not marked as trusted.\r\nAre you sure you want to install software from 'https:\/\/www.powershellgallery.com\/api\/v2\/'?\r\n[Y] Yes  [N] No  [S] Suspend  [?] Help (default is \"Y\"):\r\n\r\nName                          Version      Status       ProviderName     Source           Summary\r\n----                          -------      ------       ------------     ------           -------\r\nxFirefox                      1.0.0        Installed    PSModule         https:\/\/www.p...\r\n<\/pre>\n<p>Remember, the <code>find-*<\/code> cmdlets are for searching the remote repository. The <code>get-*<\/code> cmdlets are for searching the installed packages. <code>PowerShellGet<\/code> is about modules, hence these cmdlets have the noun as <code>module<\/code>. <code>OneGet<\/code> is about packages (generic), so the noun has <code>package<\/code>.\u00a0<\/p>\n<p>Very oddly, there seems to be no way to uninstall the modules installed from the PowerShell Gallery. As you can see below <code>Uninstall-Module<\/code> does nothing. That&#8217;s because there&#8217;s no uninstall cmdlet from <code>PowerShellGet<\/code>.\u00a0<\/p>\n<pre class=\"lang:ps decode:true\">PS&gt; get-package *fire* | Uninstall-Package\r\nPS&gt; get-package *fire*\r\n\r\nName                          Version      Status       ProviderName     Source           Summary\r\n----                          -------      ------       ------------     ------           -------\r\nxFirefox                      1.0.0        Installed    PSModule         https:\/\/www.p... Firefox Main module\r\n\r\n\r\nPS&gt; Get-Command -Module PowerShellGet\r\n\r\nCommandType     Name                                               Version    Source\r\n-----------     ----                                               -------    ------\r\nFunction        Find-Module                                        0.5        PowerShellGet\r\nFunction        Get-PSRepository                                   0.5        PowerShellGet\r\nFunction        Install-Module                                     0.5        PowerShellGet\r\nFunction        Publish-Module                                     0.5        PowerShellGet\r\nFunction        Register-PSRepository                              0.5        PowerShellGet\r\nFunction        Set-PSRepository                                   0.5        PowerShellGet\r\nFunction        Unregister-PSRepository                            0.5        PowerShellGet\r\nFunction        Update-Module                                      0.5        PowerShellGet<\/pre>\n<p>I installed the <code>xFirefox<\/code> module above. Again, from the course I learnt that &#8220;x&#8221; stands for experimental. To know more about this module one can <a href=\"http:\/\/www.powershellgallery.com\/packages\/xFirefox\/\" target=\"_blank\">visit the page<\/a> on PowerShell Gallery and from there go to the actual <a href=\"http:\/\/www.powershellgallery.com\/packages\/xFirefox\/\" target=\"_blank\">module DSC resource page<\/a>. (I have no idea what I can do with this module. From the module page I understand it should now appear as a DSC resource, but when I do a <code>Get-DSCResource<\/code> it does not appear. Tried this for the <code>xChrome<\/code> module too &#8211; same result. Other modules, e.g. <code>xComputer<\/code>, appear fine so it seems to be an issue with the <code>xFirefox<\/code> and <code>xChrome<\/code> modules.)<\/p>\n<p>Notice I have two repositories\/ sources on my system now: Chocolatey, which came by default, and PowerShell Gallery. I can search for packages available in either repository.\u00a0<\/p>\n<pre class=\"lang:ps decode:true \">PS&gt; Get-PackageSource\r\n\r\nName                             ProviderName     IsTrusted  IsRegistered IsValidated  Location\r\n----                             ------------     ---------  ------------ -----------  --------\r\nchocolatey                       Chocolatey       False      True         False        http:\/\/chocolatey.org\/api\/v2\/\r\nPSGallery                        PSModule         False      True         False        https:\/\/www.powershellgallery...\r\n\r\nPS&gt; Find-Package -ProviderName Chocolatey\r\n\r\nName                          Version      Status       ProviderName     Source           Summary\r\n----                          -------      ------       ------------     ------           -------\r\nfoxe.install                  2.4.2.2      Available    Chocolatey       chocolatey\r\nsuricata                      2.0.2.201... Available    Chocolatey       chocolatey       Free open-source IDS\/IPS\/N...\r\nxmlstarlet                    1.6.1        Available    Chocolatey       chocolatey\r\nfoxe                          2.4.2.2      Available    Chocolatey       chocolatey\r\nprocesshacker.portable        2.33.0       Available    Chocolatey       chocolatey\r\nprocesshacker                 2.33.0       Available    Chocolatey       chocolatey\r\nfoxe.portable                 2.4.2.2      Available    Chocolatey       chocolatey\r\nflashdevelop                  4.7.1        Available    Chocolatey       chocolatey       Open source code editor fo...\r\nffdshow-x86_32                1.3.4531     Available    Chocolatey       chocolatey       The all-in-one codec solution<\/pre>\n<p><code>OneGet<\/code> is working with Chocolatey developers to <a href=\"https:\/\/groups.google.com\/forum\/#!topic\/chocolatey\/a8WdEoF-M58\" target=\"_blank\">make this happen<\/a>. Currently <code>OneGet<\/code> ships with a prototype plugin for Chocolatey, which work with packages from the Chocolatey repository (note: this plugin <a href=\"https:\/\/github.com\/OneGet\/oneget\/wiki\/Q-and-A#why-didnt-you-just-use-the-current-version-of-chocolatey\" target=\"_blank\">is a rewrite<\/a>, not a wrapper around the original Chocolatey). For instance, here&#8217;s how I install Firefox from Chocolatey:<\/p>\n<pre class=\"lang:ps decode:true\">PS&gt; Find-Package -Name *firefox*\r\n\r\nName                          Version      Status       ProviderName     Source           Summary\r\n----                          -------      ------       ------------     ------           -------\r\nadblockplusfirefox            0.0.0.1      Available    Chocolatey       chocolatey\r\nFirefox                       35.0.1       Available    Chocolatey       chocolatey       Bringing together all kind...\r\nFirefoxESR                    31.2.0       Available    Chocolatey       chocolatey       This package installs Fire...\r\nxFirefox                      1.0.0        Available    PSModule         https:\/\/www.p...\r\n\r\n\r\nPS&gt; Install-Package -Name Firefox -ProviderName Chocolatey\r\n\r\nThe package 'Firefox' comes from a package source that is not marked as trusted.\r\nAre you sure you want to install software from 'chocolatey'?\r\n[Y] Yes  [N] No  [S] Suspend  [?] Help (default is \"Y\"): y\r\n\r\nName                          Version      Status       ProviderName     Source           Summary\r\n----                          -------      ------       ------------     ------           -------\r\nFirefox                       35.0.1       Installed    Chocolatey       chocolatey       Bringing together all kind...<\/pre>\n<h3>OneGet &amp; Chocolatey &#8211; still WIP<\/h3>\n<p>Even though Firefox <em>appeared<\/em> as installed above, it did not actually install. This is because Chocolatey support was removed in the latest WMF 5.0 preview I had installed. To get it back I had to <a href=\"http:\/\/oneget.org\/oneget.zip\" target=\"_blank\">install the experimental version<\/a> of <code>OneGet<\/code>. Here&#8217;s me installing PeaZip:<\/p>\n<pre class=\"lang:ps decode:true \">PS&gt; Install-Package -Name peazip -Verbose\r\nVERBOSE: Skipping package provider provider 'NuGet'-- missing required option\r\n'Microsoft.OneGet.Utility.Collections.ReEnumerable`1[System.String]'\r\nVERBOSE: The -Repository parameter was not specified.  PowerShellGet will use all of the registered repositories.\r\nVERBOSE: Getting the provider object for the OneGet Provider 'NuGet'.\r\nVERBOSE: The specified Location is 'https:\/\/www.powershellgallery.com\/api\/v2\/' and OneGetProvider is 'NuGet'.\r\nVERBOSE: Performing the operation \"Install Package\" on target \"Package 'peazip' v'5.5.0.20141130' from 'chocolatey'\".\r\n\r\nThe package 'peazip' comes from a package source that is not marked as trusted.\r\nAre you sure you want to install software from 'chocolatey'?\r\n[Y] Yes  [N] No  [S] Suspend  [?] Help (default is \"Y\"):\r\nVERBOSE: NuGet: Installing 'peazip 5.5.0.20141130'.\r\nVERBOSE: NuGet: Successfully installed 'peazip 5.5.0.20141130'.\r\nVERBOSE: CreateFolder Success C:\\Users\\Rakhesh\\AppData\\Local\\Temp\\chocolatey\\peazip\r\nVERBOSE: GetChocolateyWebFile peazip =&gt; http:\/\/www.peazip.org\/downloads\/peazip-5.5.0.WIN64.exe\r\nVERBOSE: Launching Process-EXE :'C:\\Users\\Rakhesh\\AppData\\Local\\Temp\\chocolatey\\peazip\\peazipinstall.EXE'\r\nVERBOSE: Process Exited Successfully. \u00ab{0}\u00bb \u00abC:\\Users\\Rakhesh\\AppData\\Local\\Temp\\chocolatey\\peazip\\peazipinstall.EXE\u00bb\r\nVERBOSE: Package Successfully Installed peazip\r\nVERBOSE: Installation Successful \u00abpeazip\u00bb\r\nVERBOSE: True\r\nVERBOSE: False\r\n\r\nName                          Version      Status       ProviderName     Source           Summary\r\n----                          -------      ------       ------------     ------           -------\r\npeazip                        5.5.0.201... Installed    Chocolatey       chocolatey       A cross-platform file arch...<\/pre>\n<p>For comparison here&#8217;s the same output with the non-experimental version of <code>OneGet<\/code>:<\/p>\n<pre class=\"lang:ps decode:true \">PS C:\\Windows\\system32&gt; Install-Package -Name peazip -Verbose\r\nVERBOSE: Skipping package provider provider 'NuGet'-- missing required option\r\n'Microsoft.OneGet.Utility.Collections.ReEnumerable`1[System.String]'\r\nVERBOSE: The -Repository parameter was not specified.  PowerShellGet will use all of the registered repositories.\r\nVERBOSE: Getting the provider object for the OneGet Provider 'NuGet'.\r\nVERBOSE: The specified Location is 'https:\/\/www.powershellgallery.com\/api\/v2\/' and OneGetProvider is 'NuGet'.\r\nVERBOSE: Performing the operation \"Install Package\" on target \"Package 'peazip' v'5.5.0.20141130' from 'chocolatey'\".\r\n\r\nThe package 'peazip' comes from a package source that is not marked as trusted.\r\nAre you sure you want to install software from 'chocolatey'?\r\n[Y] Yes  [N] No  [S] Suspend  [?] Help (default is \"Y\"):\r\nVERBOSE: NuGet: GET http:\/\/chocolatey.org\/api\/v2\/Packages(Id='peazip',Version='5.5.0.20141130')\r\nVERBOSE: NuGet: GET http:\/\/chocolatey.org\/api\/v2\/package\/peazip\/5.5.0.20141130\r\nVERBOSE: NuGet: Installing 'peazip 5.5.0.20141130'.\r\nVERBOSE: NuGet: Successfully installed 'peazip 5.5.0.20141130'.\r\n\r\nName                          Version      Status       ProviderName     Source           Summary\r\n----                          -------      ------       ------------     ------           -------\r\npeazip                        5.5.0.201... Installed    Chocolatey       chocolatey       A cross-platform file arch...<\/pre>\n<p>As you can see it doesn&#8217;t really download anything &#8230;<\/p>\n<p>Here&#8217;s a list of providers <code>OneGet<\/code> is aware of:<\/p>\n<pre class=\"lang:ps decode:true \">PS&gt; Get-PackageProvider\r\n\r\nName                     Version          DynamicOptions\r\n----                     -------          --------------\r\nmsu                      10.0.9800.0      {}\r\nARP                      10.0.9800.0      {IncludeWindowsInstaller}\r\nmsi                      10.0.9800.0      {AdditionalArguments}\r\nChocolatey               2.8.4.30         {SkipDependencies, ContinueOnFailure, ExcludeVersion, ForceX86...}\r\nNuGet                    2.8.4.30         {Destination, SkipDependencies, ContinueOnFailure, ExcludeVersion...}\r\nPSModule                 10.0.9800.0      {OneGetProvider, Location, InstallUpdate, InstallationPolicy...}\r\n<\/pre>\n<p>ARP stands for Add\/ Remove Programs. With the experimental version one can list the programs in Add\/ Remove programs:<\/p>\n<pre class=\"lang:ps decode:true\">PS&gt; Get-Package -ProviderName ARP\r\n\r\nName                          Version      Status       ProviderName     Source           Summary\r\n----                          -------      ------       ------------     ------           -------\r\nCDisplayEx 1.10.18                         Installed    ARP\r\nMicrosoft Azure Compute Em... 2.5.6496.10  Installed    ARP\r\nMicrosoft Visual Studio 20... 10.0.50903   Installed    ARP\r\nMicrosoft Office Professio... 15.0.4569... Installed    ARP\r\nMicrosoft Visio Profession... 15.0.4569... Installed    ARP\r\nTeraCopy 2.3                               Installed    ARP\r\nPeaZip 5.5.0 (WIN64)                       Installed    ARP<\/pre>\n<p>The MSI and MSU providers are what you think they are (for installing MSI, MSP (patch) and MSU (update) packages). You can install &amp; uninstall MSI packages via <code>OneGet<\/code>. (But can you specify additional parameters while installing MSI? <a href=\"https:\/\/github.com\/OneGet\/oneget\/issues\/95\" target=\"_blank\">Not yet<\/a>, I think &#8230;)<\/p>\n<p>That&#8217;s it then!\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Spent the past hour and half attending this course &#8211;\u00a0Getting started with PowerShell Desired State Configuration (DSC) Jump Start, by Jeffrey Snover (inventor of PowerShell) and Jason Helmick. Had to give up coz my connection quality is so poor it kept freezing every now and then. Better to wait 2-3 weeks for the recorded version &hellip; <a href=\"https:\/\/rakhesh.com\/windows\/notes-of-powershell-dsc-course-oneget-chocolatey\/\" class=\"more-link\">Continue reading <span class=\"screen-reader-text\">Notes of PowerShell DSC course, OneGet &#038; Chocolatey<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":true,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[85],"tags":[473,470,474,472,471,227,38],"jetpack_publicize_connections":[],"jetpack_sharing_enabled":true,"jetpack_featured_media_url":"","_links":{"self":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/2357"}],"collection":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/comments?post=2357"}],"version-history":[{"count":0,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/posts\/2357\/revisions"}],"wp:attachment":[{"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/media?parent=2357"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/categories?post=2357"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/rakhesh.com\/wp-json\/wp\/v2\/tags?post=2357"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}