InstChoco for Windows

Standard Features: InstChoco uses Rob's "Install with cmd.exe" method for installing Chocolatey. InstChoco will enable up to four choco features if you pass them as parameters, i.e. allowGlobalConfirmation, failOnAutoUninstaller, allowEmptyChecksums, useRememberedArgumentsForUpgrades. InstChoco will automatically search for a PACKAGES.CONFIG file in various locations and install packages from it if found. InstChoco has baked in support for Choco Package List Backup to Local and Cloud. InstChoco will use the first found PACKAGES.CONFIG in the following order: current directory, Documents folder, HOMESHARE, Dropbox, Google Drive, OneDrive, ReadyCLOUD, Resilio Sync, or Tonido Sync (v1.10+). InstChoco has baked in support for Choco Persistent Packages. InstChoco will use PERSISTANTPACKAGES.CONFIG and install packages from it if found - always (v1.10+).

Special Features for Windows Active Directory Domains: InstChoco will use domainnamePACKAGES.CONFIG and install packages from it if found - always. This allows Windows domain joined computers to have installed a common base setup of Chocolatey packages across all organizational computers. To use this feature, system administrators of Windows domains need to create a domainnamePACKAGES.CONFIG file and put it in your logon server's NETLOGON directory; i.e. \Contoso\NETLOGON\ContosoPACKAGES.CONFIG (NEW in v1.20). InstChoco will use usernamePACKAGES.CONFIG and install packages from it if found - always. This allows users of Windows domain joined computers to have their own specific Chocolatey packages installed for them (useful for roaming users). To use this feature, system administrators or users of Windows domains need to create a usernamePACKAGES.CONFIG file and put it in the root of the user's HOMESHARE; i.e. \Contoso\UserName$\UserNamePACKAGES.CONFIG (NEW in v1.20).Usage: InstChoco -y or InstChoco -ynp to install Chocolatey but no packages.