$NuGetPackages = choco list -source=$NuGetServer -r New-PSDrive -Name 'MDT' -PSProvider 'MDTProvider' -Root $MDTRoot The two variables here are the MDT root of the deployment share - $MDTRoot - and the name of the Chocolatey server from which to install software - $NuGetServer. Chocolatey with PowerShellįor packages stored in an internal Chocolatey server, IT can add applications to MDT by running a PowerShell script. This is much more difficult than using the internal Chocolatey repository, which recompiles Chocolatey community packages when new versions of the application release. The default alternative to this is to use the native Google Chrome install command and constantly change the installer on the network to the latest version. Under the deployment share in the MDT graphical user interface, the application summary will look like this: Figure B: Summary of the application being installed It is fairly simple to create a Chocolatey package in MDT. IT can replace with the host name of the organization's internal repository with the latest version of the Chocolatey server package. Set-ExecutionPolicy Bypass -Scope Process -Force iex ((New-Object ).DownloadString('')) They can also do this in MDT by running the following command in the application:

IT pros need to install and configure the Chocolatey manager and repository in the task sequence before they add a package.

IT administrators typically use their own internal repositories that their Chocolatey clients point to. These packages can take various forms, but they usually become web servers or network shares.

Chocolatey downloads these files from the command-line input, so IT should select Application without source files or elsewhere on the network (Figure A) when installing.Ĭhocolatey uses software repositories to store Chocolatey packages or NuGet files. When using the Chocolatey package manager, the application source installer will either be embedded into a NuGet file or it will be kept at a different location.

Chocolatey install google chrome