Organizations will likely want to use these existing packages for their own purposes, and can certainly do so. choco config set virusCheckMinimumPositives 1 Internalizing community packagesĪs I noted above, the Chocolatey community repository has over 5,800 Windows packages available. Here I set my client to halt execution of any packages that return one vendor deeming the package as malware. If you want to configure the minimum positive results of a VirusTotal scan, you can set it here as well. Here I will configure my clients to use VirusTotal: choco config set virusScannerType VirusTotal You probably want to set your Chocolatey clients to use virus scanning at runtime (VirusTotal or whichever antivirus software you use). To reduce the size of Chocolatey packages after installation, we can also configure this: choco feature enable -name="'reduceInstalledPackageSpaceUsage'" It's mainly a matter of installing the license file and the package: choco upgrade chocolatey.extension -y -pre Next, let's add our internal repository as a source: choco source add -name="'choco-1'" -source="' -priority="'1'"įor a licensed version of Chocolatey, you'll have to install your license. Organizations should never have clients install packages from the community repository: choco source remove -name="'chocolatey'" I will illustrate a few examples here.įirst, let's remove the Chocolatey community feed as a source. Since we have Chocolatey Server set up (hostname choco-1), we can actually just point our clients there from PowerShell: Set-ExecutionPolicy Bypass -Scope Process -Force iex ((New-Object ).DownloadString(' Now that we've installed Chocolatey, there is some additional configuring to do for organizational use. To install the Chocolatey client software, we usually point to Chocolatey itself, which downloads the install script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |