Step 1: Review Your Packages

Step 2: Choose Your Integration Method

Step 3: Copy Your Script or Download Config

Option 1: Copy Script

Option 2: Download Config

Step 4: Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the packages and push them to a repository
  Download Packages

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the packages:
  Download Packages
- Follow manual internalization instructions
Package Internalizer (C4B)
- Run: (additional options)
- For package and dependencies run:
- Automate package internalization

Step 5: Copy Your Script

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###

#### We initialize a few things that are needed by this script - there are no other requirements.
$ErrorActionPreference = "Stop"

#### Set TLS 1.2 (3072) as that is the minimum required by various up-to-date repositories.
#### Use integers because the enumeration value for TLS 1.2 won't exist
#### in .NET 4.0, even though they are addressable if .NET 4.5+ is
#### installed (.NET 4.5 is an in-place upgrade).
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072

#### We use this variable for future REST calls.
$RequestArguments = @{
    UseBasicParsing = $true
}

## 2. TOP LEVEL VARIABLES ##

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# $NugetRepositoryCredential = [PSCredential]::new(
#     "username",
#     ("password" | ConvertTo-SecureString -AsPlainText -Force)
# )
# $RequestArguments.Credential = $NugetRepositoryCredential

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it
$ChocolateyDownloadUrl = "$($NugetRepositoryUrl.TrimEnd('/'))/package/chocolatey.2.2.2.nupkg"

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# $ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

#### Download the Nupkg, appending .zip to the filename to handle archive cmdlet limitations
if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    $TempDirectory = Join-Path $env:Temp "chocolateyInstall"
    if (-not (Test-Path $TempDirectory -PathType Container)) {
        $null = New-Item -Path $TempDirectory -ItemType Directory
    }
    $DownloadedNupkg = Join-Path $TempDirectory "$(Split-Path $ChocolateyDownloadUrl -Leaf).zip"
    Invoke-WebRequest -Uri $ChocolateyDownloadUrl -OutFile $DownloadedNupkg @RequestArguments

    #### Extract the Nupkg, and run the chocolateyInstall script
    if (Get-Command Microsoft.PowerShell.Archive\Expand-Archive -ErrorAction SilentlyContinue) {
        Microsoft.PowerShell.Archive\Expand-Archive -Path $DownloadedNupkg -DestinationPath $TempDirectory -Force
    } else {
        # PowerShell versions <4.0 do not have this function available
        try {
            $shellApplication = New-Object -ComObject Shell.Application
            $zipPackage = $shellApplication.NameSpace($DownloadedNupkg)
            $destinationFolder = $shellApplication.NameSpace($TempDirectory)
            $destinationFolder.CopyHere($zipPackage.Items(), 0x10)
        } catch {
            Write-Warning "Unable to unzip package using built-in compression."
            throw $_
        }
    }

    & $(Join-Path $TempDirectory "tools\chocolateyInstall.ps1")
}

if (-not (Get-Command choco.exe -ErrorAction SilentlyContinue)) {
    refreshenv
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# choco feature enable -n useFipsCompliantChecksums

### b. Apply Recommended Configuration ###
#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
choco config set --name cacheLocation --value C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
choco config set --name commandExecutionTimeoutSeconds --value 14400

#### Turn off download progress when running choco through integrations
choco feature disable --name showDownloadProgress

### c. Sources ###
#### Remove the default community package repository source
choco source list --limitoutput | ConvertFrom-Csv -Header 'Name', 'Location' -Delimiter '|' | ForEach-Object {
    if ($_.Location -eq 'https://community.chocolatey.org/api/v2/') {
        choco source remove -n $_.Name
    }
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
if ($NugetRepositoryCredential) {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --user $NugetRepositoryCredential.UserName --password $NugetRepositoryCredential.GetNetworkCredential().Password --priority 1
} else {
    choco source add --name ChocolateyInternal --source $NugetRepositoryUrl --priority 1
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
choco upgrade chocolatey --confirm

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
choco install chocolatey-license --source $NugetRepositoryUrl --confirm

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco source disable --name chocolatey.licensed
} else {
    Write-Warning "Not disabling 'chocolatey.licensed' feed, as Chocolatey-License has not been installed."
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
if ("chocolatey-license" -in (choco list --localonly --limitoutput | ConvertFrom-Csv -Header "Name" -Delimiter "|").Name) {
    choco install chocolatey.extension --source $NugetRepositoryUrl --confirm
} else {
    Write-Warning "Not installing 'chocolatey.extension', as Chocolatey-License has not been installed."
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
choco feature disable --name showNonElevatedWarnings
choco feature enable --name useBackgroundService
choco feature enable --name useBackgroundServiceWithNonAdministratorsOnly
choco feature enable --name allowBackgroundServiceUninstallsFromUserInstallsOnly
choco config set --name allowedBackgroundServiceCommands --value "install,upgrade,uninstall"

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if ($ChocolateyCentralManagementUrl) {
    choco install chocolatey-agent --source $NugetRepositoryUrl --confirm
    choco config set --name CentralManagementServiceUrl --value $ChocolateyCentralManagementUrl
    if ($ChocolateyCentralManagementClientSalt) {
        choco config set --name centralManagementClientCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementClientSalt
    }
    if ($ChocolateyCentralManagementServiceSalt) {
        choco config set --name centralManagementServiceCommunicationSaltAdditivePassword --value $ChocolateyCentralManagementServiceSalt
    }
    choco feature enable --name useChocolateyCentralManagement
    choco feature enable --name useChocolateyCentralManagementDeployments
}

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. chocolatey.chocolatey
##### You will require the chocolatey.chocolatey collection to be installed
##### on all machines using this playbook.
##### Please see https://github.com/chocolatey/chocolatey-ansible/#installing-the-collection-from-ansible-galaxy

- name: Install and Configure Chocolatey
  hosts: all

## 2. TOP LEVEL VARIABLES ##
  vars:

### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
    nuget_repository_url: INTERNAL REPO URL

### b. Internal Repository Credential ###
#### If required, add the repository access credential here and
#### uncomment lines with source_username and source_password below
#    nuget_repository_username: username
#    nuget_repository_password: password

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#    chocolatey_central_management_url: https://chocolatey-central-management:24020/ChocolateyManagementService

#### ii. If using a Client Salt, add it here
#    chocolatey_central_management_client_salt: clientsalt

#### iii. If using a Service Salt, add it here
#    chocolatey_central_management_service_salt: servicesalt

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository

  tasks:
  - name: Install chocolatey
    win_chocolatey:
      name: chocolatey
      source: ""{{ nuget_repository_url }}""
      # source_username: ""{{ nuget_repository_username }}""
      # source_password: ""{{ nuget_repository_password }}""

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#   - name: Enable FIPS compliance
#     win_chocolatey_feature:
#       name: useFipsCompliantChecksums
#       state: enabled

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
  - name: Set the cache location
    win_chocolatey_config:
      name: cacheLocation
      state: present
      value: C:\ProgramData\chocolatey\cache

#### Increase timeout to at least 4 hours
  - name: Set the command execution timeout
    win_chocolatey_config:
      name: commandExecutionTimeoutSeconds
      state: present
      value: 14400

#### Turn off download progress when running choco through integrations
  - name: Disable showing download progress
    win_chocolatey_feature:
      name: showDownloadProgress
      state: disabled

### c. Sources ###
#### Remove the default community package repository source
  - name: Remove Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey
      state: absent

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here
#### NOTE: This EXAMPLE may require changes
  - name: Add Internal Repository
    win_chocolatey_source:
      name: ChocolateyInternal
      state: present
      source: {{ nuget_repository_url }}
      # source_username: {{ nuget_repository_username }}
      # source_password: {{ nuget_repository_password }}
      priority: 1

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
  - name: Upgrade Chocolatey
    win_chocolatey:
      name: chocolatey
      state: latest

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.
### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
  - name: Install Chocolatey License
    win_chocolatey:
      name: chocolatey-license
      source: ChocolateyInternal
      state: latest

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
  - name: Disable Chocolatey Community Repository
    win_chocolatey_source:
      name: chocolatey.licensed
      state: disabled

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
  - name: Install Chocolatey Extension
    win_chocolatey:
      name: chocolatey.extension
      source: ChocolateyInternal
      state: latest

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
  - name: Hide not-elevated warnings
    win_chocolatey_feature:
      name: showNonElevatedWarnings
      state: disabled

  - name: Use background mode for self-service
    win_chocolatey_feature:
      name: useBackgroundService
      state: enabled

  - name: Use background service for non-admins
    win_chocolatey_feature:
      name: useBackgroundServiceWithNonAdministratorsOnly
      state: enabled

  - name: Allow background uninstallation for user installs
    win_chocolatey_feature:
      name: allowBackgroundServiceUninstallsFromUserInstallsOnly
      state: enabled

  - name: Set allowed background service commands
    win_chocolatey_config:
      name: backgroundServiceAllowedCommands
      state: present
      value: install,upgrade,uninstall

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
  - name: Install Chocolatey Agent
    when: chocolatey_central_management_url is defined
    win_chocolatey:
      name: chocolatey-agent
      source: ChocolateyInternal
      state: latest

  - name: Set the Central Management Service URL
    when: chocolatey_central_management_url is defined
    win_chocolatey_config:
      name: CentralManagementServiceUrl
      state: present
      value: {{ chocolatey_central_management_url }}

  - name: Set the Central Management Client Salt
    when: chocolatey_central_management_client_salt is defined
    win_chocolatey_config:
      name: centralManagementClientCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_client_salt }}

  - name: Set the Central Management Service Salt
    when: chocolatey_central_management_service_salt is defined
    win_chocolatey_config:
      name: centralManagementServiceCommunicationSaltAdditivePassword
      state: present
      value: {{ chocolatey_central_management_service_salt }}

  - name: Use Central Management
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagement
      state: enabled

  - name: Use Central Management Deployments
    when: chocolatey_central_management_url is defined
    win_chocolatey_feature:
      name: useChocolateyCentralManagementDeployments
      state: enabled

See docs at https://docs.chef.io/resource_chocolatey_package.html.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### The Chocolatey resources are available with any recent version of Chef.
#### We utilise the Chocolatey recipe to install the Chocolatey binaries.
include_recipe "chocolatey"

## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
NugetRepositoryUrl = "INTERNAL REPO URL"

### b. Internal Repository Credential ###
#### If required, add the repository access credential here
# NugetRepositoryUsername = "username"
# NugetRepositoryPassword = "password"

### c. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
ChocolateyNupkgUrl = "INTERNAL REPO URL/package/chocolatey.2.2.2.nupkg",

### d. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService"

#### ii. If using a Client Salt, add it here
# ChocolateyCentralManagementClientSalt = "clientsalt"

#### iii. If using a Service Salt, add it here
# ChocolateyCentralManagementServiceSalt = "servicesalt"

## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
node['chocolatey']['install vars'] = {
  'chocolateyDownloadUrl' => "#{ChocolateyNupkgUrl}",
}

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
# chocolatey_feature 'useFipsCompliantChecksums' do
#   action :enable
# end

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolatey_config 'cacheLocation' do
  value 'C:\ProgramData\chocolatey\cache'
end

#### Increase timeout to at least 4 hours
chocolatey_config 'commandExecutionTimeoutSeconds' do
  value '14400'
end

#### Turn off download progress when running choco through integrations
chocolatey_feature 'showDownloadProgress' do
  action :disable
end

### c. Sources ###
#### Remove the default community package repository source
chocolatey_source 'chocolatey' do
  action :remove
end

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE may require changes
chocolatey_source 'ChocolateyInternal' do
  source "#{NugetRepositoryUrl}"
  priority 1
  action   :add
end

execute 'ChocolateyInternal' do
  command "choco source add --name ChocolateyInternal -s #{NugetRepositoryUrl} -u=#{NugetRepositoryUsername} -p=#{NugetRepositoryPassword} --priority=1"
  only_if { NugetRepositoryUsername != nil || NugetRepositoryPassword != nil }
end

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
chocolatey_package 'chocolatey' do
  action :upgrade
  source "#{NugetRepositoryUrl}"
end

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
chocolatey_package 'chocolatey-license' do
  action :install
  source "#{NugetRepositoryUrl}"
end

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
chocolatey_source 'chocolatey.licensed' do
  action            :disable
end

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
chocolatey_package 'chocolatey.extention' do
  action     install
  source     "#{NugetRepositoryUrl}"
end

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolatey_feature 'showNonElevatedWarnings' do
  action :disable
end

chocolatey_feature 'useBackgroundService' do
  action :enable
end

chocolatey_feature 'useBackgroundServiceWithNonAdministratorsOnly' do
  action :enable
end

chocolatey_feature 'allowBackgroundServiceUninstallsFromUserInstallsOnly' do
  action :enable
end

chocolatey_config 'backgroundServiceAllowedCommands' do
  value 'install,upgrade,uninstall'
end

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
chocolatey_package 'chocolatey-agent' do
  action     install
  source     "#{NugetRepositoryUrl}"
  # user       "#{NugetRepositoryUsername}"
  # password   "#{NugetRepositoryPassword}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'CentralManagementServiceUrl' do
  value  "#{ChocolateyCentralManagementUrl}"
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_config 'centralManagementClientCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementClientSalt}"
  only_if { ChocolateyCentralManagementClientSalt != nil }
end

chocolatey_config 'centralManagementServiceCommunicationSaltAdditivePassword' do
  value   "#{ChocolateyCentralManagementServiceSalt}"
  only_if { ChocolateyCentralManagementServiceSalt != nil }
end

chocolatey_feature 'useChocolateyCentralManagement' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

chocolatey_feature 'useChocolateyCentralManagementDeployments' do
  action :enable
  only_if { ChocolateyCentralManagementUrl != nil }
end

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.

If Applicable - Chocolatey Configuration/Installation


#requires -Modules cChoco
## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires chocolatey\cChoco DSC module to be installed on the machine compiling the DSC manifest
#### NOTE: This will need to be installed before running the DSC portion of this script
if (-not (Get-Module cChoco -ListAvailable)) {
    $null = Install-PackageProvider -Name NuGet -MinimumVersion 2.8.5.201 -Force
    if (($PSGallery = Get-PSRepository -Name PSGallery).InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy Trusted
    }
    Install-Module -Name cChoco
    if ($PSGallery.InstallationPolicy -ne "Trusted") {
        Set-PSRepository -Name PSGallery -InstallationPolicy $PSGallery.InstallationPolicy
    }
}

#### ii. Requires a hosted copy of the install.ps1 script
##### This should be available to download without authentication.
##### The original script can be found here: https://community.chocolatey.org/install.ps1

Configuration ChocolateyConfig {
## 2. TOP LEVEL VARIABLES ##
    param(
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
        $NugetRepositoryUrl      = "INTERNAL REPO URL",

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
        $ChocolateyNupkgUrl      = "INTERNAL REPO URL/package/chocolatey.2.2.2.nupkg",

### c. Internal Repository Credential ###
#### If required, add the repository access credential here
#        $NugetRepositoryCredential = [PSCredential]::new(
#            "username",
#            ("password" | ConvertTo-SecureString -AsPlainText -Force)
#        ),

### d. Install.ps1 URL
#### The path to the hosted install script:
        $ChocolateyInstallPs1Url = "https://community.chocolatey.org/install.ps1"

### e. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
#        $ChocolateyCentralManagementUrl = "https://chocolatey-central-management:24020/ChocolateyManagementService",

#### ii. If using a Client Salt, add it here
#        $ChocolateyCentralManagementClientSalt = "clientsalt",

#### iii. If using a Service Salt, add it here
#        $ChocolateyCentralManagementServiceSalt = "servicesalt"
    )
    Import-DscResource -ModuleName PSDesiredStateConfiguration
    Import-DscResource -ModuleName cChoco

    Node 'localhost' {
## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
        Environment chocoDownloadUrl {
            Name  = "chocolateyDownloadUrl"
            Value = $ChocolateyNupkgUrl
        }

        cChocoInstaller installChocolatey {
            DependsOn = "[Environment]chocoDownloadUrl"
            InstallDir = Join-Path $env:ProgramData "chocolatey"
            ChocoInstallScriptUrl = $ChocolateyInstallPs1Url
        }

## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations
#        cChocoFeature featureFipsCompliance {
#            FeatureName = "useFipsCompliantChecksums"
#        }

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
        cChocoConfig cacheLocation {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "cacheLocation"
            Value      = "C:\ProgramData\chocolatey\cache"
        }

#### Increase timeout to at least 4 hours
        cChocoConfig commandExecutionTimeoutSeconds {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            ConfigName = "commandExecutionTimeoutSeconds"
            Value      = 14400
        }

#### Turn off download progress when running choco through integrations
        cChocoFeature showDownloadProgress {
            DependsOn   = "[cChocoInstaller]installChocolatey"
            FeatureName = "showDownloadProgress"
            Ensure      = "Absent"
        }

### c. Sources ###
#### Remove the default community package repository source
        cChocoSource removeCommunityRepository {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name       = "chocolatey"
            Ensure     = "Absent"
        }

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here.
#### NOTE: This EXAMPLE may require changes
        cChocoSource addInternalSource {
            DependsOn  = "[cChocoInstaller]installChocolatey"
            Name        = "ChocolateyInternal"
            Source      = $NugetRepositoryUrl
            Credentials = $NugetRepositoryCredential
            Priority    = 1
        }

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/
        cChocoPackageInstaller updateChocolatey {
            DependsOn   = "[cChocoSource]addInternalSource", "[cChocoSource]removeCommunityRepository"
            Name        = "chocolatey"
            AutoUpgrade = $true
        }

## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/how-tos/setup-offline-installation#exercise-4-create-a-package-for-the-license
        cChocoPackageInstaller chocolateyLicense {
            DependsOn = "[cChocoPackageInstaller]updateChocolatey"
            Name      = "chocolatey-license"
        }

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
        Script disableLicensedSource {
            DependsOn  = "[cChocoPackageInstaller]chocolateyLicense"
            GetScript  = {
                $Source = choco source list --limitoutput | `
                    ConvertFrom-Csv -Delimiter '|' -Header Name, Source, Disabled | `
                    Where-Object Name -eq "chocolatey.licensed"

                return @{
                    Result = if ($Source) {
                        [bool]::Parse($Source.Disabled)
                    } else {
                        Write-Warning "Source 'chocolatey.licensed' was not present."
                        $true  # Source does not need disabling
                    }
                }
            }
            SetScript  = {
                $null = choco source disable --name "chocolatey.licensed"
            }
            TestScript = {
                $State = [ScriptBlock]::Create($GetScript).Invoke()
                return $State.Result
            }
        }

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
        cChocoPackageInstaller chocolateyLicensedExtension {
            DependsOn = "[Script]disableLicensedSource"
            Name      = "chocolatey.extension"
        }

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
        cChocoFeature hideElevatedWarnings {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "showNonElevatedWarnings"
            Ensure      = "Absent"
        }

        cChocoFeature useBackgroundService {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundService"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceWithNonAdmins {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "useBackgroundServiceWithNonAdministratorsOnly"
            Ensure      = "Present"
        }

        cChocoFeature useBackgroundServiceUninstallsForUserInstalls {
            DependsOn   = "[cChocoPackageInstaller]chocolateyLicensedExtension"
            FeatureName = "allowBackgroundServiceUninstallsFromUserInstallsOnly"
            Ensure      = "Present"
        }

        cChocoConfig allowedBackgroundServiceCommands {
            DependsOn   = "[cChocoFeature]useBackgroundService"
            ConfigName = "backgroundServiceAllowedCommands"
            Value       = "install,upgrade,uninstall"
        }

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
        if ($ChocolateyCentralManagementUrl) {
            cChocoPackageInstaller chocolateyAgent {
                DependsOn = "[cChocoPackageInstaller]chocolateyLicensedExtension"
                Name      = "chocolatey-agent"
            }

            cChocoConfig centralManagementServiceUrl {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                ConfigName = "CentralManagementServiceUrl"
                Value       = $ChocolateyCentralManagementUrl
            }

            if ($ChocolateyCentralManagementClientSalt) {
                cChocoConfig centralManagementClientSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementClientCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementClientSalt
                }
            }

            if ($ChocolateyCentralManagementServiceSalt) {
                cChocoConfig centralManagementServiceSalt {
                    DependsOn  = "[cChocoPackageInstaller]chocolateyAgent"
                    ConfigName = "centralManagementServiceCommunicationSaltAdditivePassword"
                    Value      = $ChocolateyCentralManagementServiceSalt
                }
            }

            cChocoFeature useCentralManagement {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagement"
                Ensure      = "Present"
            }

            cChocoFeature useCentralManagementDeployments {
                DependsOn   = "[cChocoPackageInstaller]chocolateyAgent"
                FeatureName = "useChocolateyCentralManagementDeployments"
                Ensure      = "Present"
            }
        }
    }
}

# If working this into an existing configuration with a good method for
$ConfigData = @{
    AllNodes = @(
        @{
            NodeName                    = "localhost"
            PSDscAllowPlainTextPassword = $true
        }
    )
}

try {
    Push-Location $env:Temp
    $Config = ChocolateyConfig -ConfigurationData $ConfigData
    Start-DscConfiguration -Path $Config.PSParentPath -Wait -Verbose -Force
} finally {
    Pop-Location
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

If Applicable - Chocolatey Configuration/Installation


## 1. REQUIREMENTS ##
### Here are the requirements necessary to ensure this is successful.

### a. Internal/Private Cloud Repository Set Up ###
#### You'll need an internal/private cloud repository you can use. These are
####  generally really quick to set up and there are quite a few options.
####  Chocolatey Software recommends Nexus, Artifactory Pro, or ProGet as they
####  are repository servers and will give you the ability to manage multiple
####  repositories and types from one server installation.

### b. Download Chocolatey Package and Put on Internal Repository ###
#### You need to have downloaded the Chocolatey package as well.
####  Please see https://chocolatey.org/install#organization

### c. Other Requirements ###
#### i. Requires puppetlabs/chocolatey module
####  See https://forge.puppet.com/puppetlabs/chocolatey


## 2. TOP LEVEL VARIABLES ##
### a. Your internal repository url (the main one). ###
####  Should be similar to what you see when you browse
#### to https://community.chocolatey.org/api/v2/
$_repository_url = 'INTERNAL REPO URL'

### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$_choco_download_url = 'INTERNAL REPO URL/package/chocolatey.2.2.2.nupkg'

### c. Chocolatey Central Management (CCM) ###
#### If using CCM to manage Chocolatey, add the following:
#### i. Endpoint URL for CCM
# $_chocolatey_central_management_url = 'https://chocolatey-central-management:24020/ChocolateyManagementService'

#### ii. If using a Client Salt, add it here
# $_chocolatey_central_management_client_salt = "clientsalt"

#### iii. If using a Service Salt, add it here
# $_chocolatey_central_management_service_salt = 'servicesalt'


## 3. ENSURE CHOCOLATEY IS INSTALLED ##
### Ensure Chocolatey is installed from your internal repository
### Note: `chocolatey_download_url is completely different than normal
###  source locations. This is directly to the bare download url for the
###  chocolatey.nupkg, similar to what you see when you browse to
###  https://community.chocolatey.org/api/v2/package/chocolatey
class {'chocolatey':
  chocolatey_download_url => $_choco_download_url,
  use_7zip                => false,
}


## 4. CONFIGURE CHOCOLATEY BASELINE ##
### a. FIPS Feature ###
#### If you need FIPS compliance - make this the first thing you configure
#### before you do any additional configuration or package installations

#chocolateyfeature {'useFipsCompliantChecksums':
#  ensure => enabled,
#}

### b. Apply Recommended Configuration ###

#### Move cache location so Chocolatey is very deterministic about
#### cleaning up temporary data and the location is secured to admins
chocolateyconfig {'cacheLocation':
  value => 'C:\ProgramData\chocolatey\cache',
}

#### Increase timeout to at least 4 hours
chocolateyconfig {'commandExecutionTimeoutSeconds':
  value => '14400',
}

#### Turn off download progress when running choco through integrations
chocolateyfeature {'showDownloadProgress':
  ensure => disabled,
}

### c. Sources ###
#### Remove the default community package repository source
chocolateysource {'chocolatey':
  ensure   => absent,
  location => 'https://community.chocolatey.org/api/v2/',
}

#### Add internal default sources
#### You could have multiple sources here, so we will provide an example
#### of one using the remote repo variable here

#### NOTE: This EXAMPLE requires changes
chocolateysource {'internal_chocolatey':
  ensure             => present,
  location           => $_repository_url,
  priority           => 1,
  username           => 'optional',
  password           => 'optional,not ensured',
  bypass_proxy       => true,
  admin_only         => false,
  allow_self_service => false,
}

### b. Keep Chocolatey Up To Date ###
#### Keep chocolatey up to date based on your internal source
#### You control the upgrades based on when you push an updated version
####  to your internal repository.
#### Note the source here is to the OData feed, similar to what you see
####  when you browse to https://community.chocolatey.org/api/v2/

package {'chocolatey':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}


## 5. ENSURE CHOCOLATEY FOR BUSINESS ##
### If you don't have Chocolatey for Business (C4B), you'll want to remove from here down.

### a. Ensure The License File Is Installed ###
#### Create a license package using script from https://docs.chocolatey.org/en-us/guides/organizations/organizational-deployment-guide#exercise-4-create-a-package-for-the-license

# TODO: Add resource for installing/ensuring the chocolatey-license package
package {'chocolatey-license':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
}

### b. Disable The Licensed Source ###
#### The licensed source cannot be removed, so it must be disabled.
#### This must occur after the license has been set by the license package.
## Disabled sources still need all other attributes until
## https://tickets.puppetlabs.com/browse/MODULES-4449 is resolved.
## Password is necessary with user, but not ensurable, so it should not
## matter what it is set to here. If you ever do get into trouble here,
## the password is your license GUID.
chocolateysource {'chocolatey.licensed':
  ensure   => disabled,
  priority => '10',
  user     => 'customer',
  password => '1234',
  require  => Package['chocolatey-license'],
}

### c. Ensure Chocolatey Licensed Extension ###
#### You will have downloaded the licensed extension to your internal repository
#### as you have disabled the licensed repository in step 5b.

#### Ensure the chocolatey.extension package (aka Chocolatey Licensed Extension)
package {'chocolatey.extension':
  ensure   => latest,
  provider => chocolatey,
  source   => $_repository_url,
  require  => Package['chocolatey-license'],
}

#### The Chocolatey Licensed Extension unlocks all of the following, which also have configuration/feature items available with them. You may want to visit the feature pages to see what you might want to also enable:
#### - Package Builder - https://docs.chocolatey.org/en-us/features/paid/package-builder
#### - Package Internalizer - https://docs.chocolatey.org/en-us/features/paid/package-internalizer
#### - Package Synchronization (3 components) - https://docs.chocolatey.org/en-us/features/paid/package-synchronization
#### - Package Reducer - https://docs.chocolatey.org/en-us/features/paid/package-reducer
#### - Package Audit - https://docs.chocolatey.org/en-us/features/paid/package-audit
#### - Package Throttle - https://docs.chocolatey.org/en-us/features/paid/package-throttle
#### - CDN Cache Access - https://docs.chocolatey.org/en-us/features/paid/private-cdn
#### - Branding - https://docs.chocolatey.org/en-us/features/paid/branding
#### - Self-Service Anywhere (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/self-service-anywhere
#### - Chocolatey Central Management (more components will need to be installed and additional configuration will need to be set) - https://docs.chocolatey.org/en-us/features/paid/chocolatey-central-management
#### - Other - https://docs.chocolatey.org/en-us/features/paid/

### d. Ensure Self-Service Anywhere ###
#### If you have desktop clients where users are not administrators, you may
#### to take advantage of deploying and configuring Self-Service anywhere
chocolateyfeature {'showNonElevatedWarnings':
  ensure => disabled,
}

chocolateyfeature {'useBackgroundService':
  ensure => enabled,
}

chocolateyfeature {'useBackgroundServiceWithNonAdministratorsOnly':
  ensure => enabled,
}

chocolateyfeature {'allowBackgroundServiceUninstallsFromUserInstallsOnly':
  ensure => enabled,
}

chocolateyconfig {'backgroundServiceAllowedCommands':
  value => 'install,upgrade,uninstall',
}

### e. Ensure Chocolatey Central Management ###
#### If you want to manage and report on endpoints, you can set up and configure
### Central Management. There are multiple portions to manage, so you'll see
### a section on agents here along with notes on how to configure the server
### side components.
if $_chocolatey_central_management_url {
  package {'chocolatey-agent':
    ensure   => latest,
    provider => chocolatey,
    source   => $_repository_url,
    require  => Package['chocolatey-license'],
  }

  chocolateyconfig {'CentralManagementServiceUrl':
    value   => $_chocolatey_central_management_url,
  }

  if $_chocolatey_central_management_client_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  if $_chocolatey_central_management_service_salt {
    chocolateyconfig {'centralManagementClientCommunicationSaltAdditivePassword':
      value => $_chocolatey_central_management_client_salt,
    }
  }

  chocolateyfeature {'useChocolateyCentralManagement':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }

  chocolateyfeature {'useChocolateyCentralManagementDeployments':
    ensure  => enabled,
    require => Package['chocolatey-agent'],
  }
}

Need Help? View our docs or file an issue.

There is already a version of this package in your Script Builder

Current Version	New Version

Downloads:

13,766

Downloads of v 3.2.1.523301:

10,509

Last Update:

11 Jun 2018

Package Maintainer(s):

cole.mike

Software Author(s):

LogMeIn
Inc.

Tags:

viewer remote meeting admin

join.me

3.2.1.523301 | Updated: 11 Jun 2018

Downloads:

13,766

Downloads of v 3.2.1.523301:

10,509

Maintainer(s):

cole.mike

Software Author(s):

LogMeIn
Inc.

Tags:

viewer remote meeting admin

join.me 3.2.1.523301

All Checks are Passing

3 Passing Tests

Show Checks

Validation Testing Passed

Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details

Learn More

Deployment Method: Individual Install, Upgrade, & Uninstall

To install join.me, run the following command from the command line or from PowerShell:

To upgrade join.me, run the following command from the command line or from PowerShell:

To uninstall join.me, run the following command from the command line or from PowerShell:

NOTE

This applies to both open source and commercial editions of Chocolatey.

1. Enter Your Internal Repository Url

(this should look similar to https://community.chocolatey.org/api/v2/)

2. Setup Your Environment

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

2. Get the package into your environment

Option 1: Cached Package (Unreliable, Requires Internet - Same As Community)

Open Source or Commercial:
- Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://community.chocolatey.org/api/v2/. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
- You can also just download the package and push it to a repository Download

Option 2: Internalized Package (Reliable, Scalable)

Open Source
- Download the package:
  Download
- Follow manual internalization instructions

Package Internalizer (C4B)

Run: (additional options)

choco download join.me --internalize --source=https://community.chocolatey.org/api/v2/

For package and dependencies run:

choco push --source="'INTERNAL REPO URL'"

Automate package internalization

3. Copy Your Script

choco upgrade join.me -y --source="'INTERNAL REPO URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade join.me -y --source="'INTERNAL REPO URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode


- name: Install join.me
  win_chocolatey:
    name: join.me
    version: '3.2.1.523301'
    source: INTERNAL REPO URL
    state: present

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.


chocolatey_package 'join.me' do
  action    :install
  source   'INTERNAL REPO URL'
  version  '3.2.1.523301'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


cChocoPackageInstaller join.me
{
    Name     = "join.me"
    Version  = "3.2.1.523301"
    Source   = "INTERNAL REPO URL"
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'join.me':
  ensure   => '3.2.1.523301',
  provider => 'chocolatey',
  source   => 'INTERNAL REPO URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.

4. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

NOTE

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

Package Approved

This package was approved by moderator gep13 on 13 Jun 2018.

Description

Note:

The checksums for this installer constantly change, so it needs to run with --ignore-checksums if you have not turned off the feature allowEmptyChecksumsSecure.

A drop-dead simple online meeting and screen sharing service from LogMeIn, join.me is used by millions of people and hundreds of thousands of businesses for everything from online meetings, to ad hoc show and tell collaboration.

Files

license.txt

Terms & Conditions of Use for LogMeIn?s Cloud Services
IMPORTANT - PLEASE READ THESE TERMS AND CONDITIONS CAREFULLY WHEN PURCHASING OR ACCESSING THE LISTED SERVICES AND/OR SOFTWARE FROM LOGMEIN, INC. ("LMI INC.") OR ITS WHOLLY OWNED SUBSIDIARY, LOGMEIN IRELAND LTD. ("LMI IRELAND"), AS APPLICABLE, (LMI INC. AND LMI IRELAND, TOGETHER REFERRED TO HEREIN AS "LMI"). These terms and conditions ("Terms") govern the use and licensing by LMI of the following LogMeIn? cloud-based service(s): AppGuru?, LogMeIn Backup?, BoldChat?, LogMeIn? CentralTM, CubbyTM, LogMeIn Hamachi?, LogMeIn for Android or iOS, join.me?, LogMeIn Pro?, and LogMeIn Rescue? or LogMeIn? Rescue+MobileTM, along with their related software, including the Network ConsoleTM (altogether the ?Services,? and each a "Service"). Each Service may have additional terms and conditions that are unique to their particular functions and features.  You are encouraged to read the Service-specific Terms in Articles VI and VII below before purchasing or accessing any of the Services.  BY COMPLETING THE ELECTRONIC ACCEPTANCE PROCESS, CLICKING THE "SUBMIT" OR "ACCEPT" BUTTONS, USING ANY OF THE SERVICES OR OTHERWISE INDICATING ACCEPTANCE OF THESE TERMS, YOU AND ANY PARTY OR ENTITY THAT YOU ARE USING/PURCHASING THE SERVICE ON BEHALF OF (TOGETHER REFERRED TO AS "YOU" OR "YOUR"), REPRESENT AND WARRANT THAT: (i) YOU ARE AUTHORIZED TO BIND YOURSELF AND ANY OTHER PARTY ON WHOSE BEHALF YOU USE THE SERVICE AND/OR SOFTWARE; AND (ii) YOU AGREE TO BE BOUND BY ALL OF THESE TERMS (INCLUDING THE DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY SECTIONS SET FORTH BELOW) TO THE EXCLUSION OF ANY OTHER RIGHTS AND OBLIGATIONS, SUCH AS ANY RIGHTS, OBLIGATIONS OR OTHER TERMS LISTED ON A PURCHASE ORDER OR THE LIKE YOU MAY PROVIDE LMI AND YOU AGREE THAT ANY SUCH RIGHTS, OBLIGATIONS OR OTHER TERMS ARE HEREBY NULL AND VOID. YOU UNDERSTAND AND AGREE THAT WHEN ORDERING OR ACCESSING LMI'S SERVICES FROM COUNTRIES LOCATED OUTSIDE OF THE UNITED STATES YOU ARE ENTERING INTO A BINDING CONTRACT WITH LMI IRELAND, NOT LMI INC., AND LMI IRELAND SHALL SERVE AS THE SELLER OF RECORD TO YOU. FOR THE AVOIDANCE OF DOUBT, ANY REFERENCES TO "LMI" IN THESE TERMS RELATED TO (i) THE SALE OF SERVICES TO CUSTOMERS LOCATED OUTSIDE OF THE UNITED STATES OR (ii) THE REPORTING AND/OR PAYMENT OBLIGATIONS IN CONNECTION THEREWITH, SHALL BE CONSTRUED AS REFERENCES TO LMI IRELAND AND NOT LMI INC. 

Article I.	Your Data
1.1.	Account Data.  To use the Services, You must complete and submit an online registration form (the "Registration Form"). As part of this registration process, You agree to: (i) provide certain limited information about Yourself as prompted to do so during the registration process or thereafter by the Service (such information to be current, complete and accurate) and (ii) maintain and update this information as required to keep it current, complete and accurate. The information requested at the time of the original signup shall be referred to as account data (the "Account Data"). LMI may have limited access to data that may be stored, created, shared, or displayed through the Service, which shall be used solely for the purpose of delivering the Service.  LMI's Privacy Policy (https://secure.logmein.com/policies/privacy.aspx) describes how Account Data may be collected, used and disclosed.  You may not register for any Service if You are under 18 years of age. By registering, You represent to LMI that You are 18 years of age or older. If LMI discovers that any of Your Account Data is inaccurate, incomplete or not current, or if LMI determines, in its sole discretion, that You are not an appropriate subscriber or user of the Service, LMI may immediately terminate Your right to access, receive, use and license the Service and its related software.
1.2.	Personally Identifiable Information.  When using certain Service(s) provided by LMI hereunder, it may be possible for You to exchange limited personally identifiable information ("PII") with LMI. Your assent to these Terms constitutes an express understanding and agreement that when PII is provided to LMI in connection with the Services, through any of the LMI websites, or otherwise under these Terms, such PII may be maintained and/or processed in the United States by LMI, as LMI's Services, software and website are provided via equipment and other resources located in the United States. To ensure that Your PII is handled with due care, LMI annually certifies that it adheres to the Safe Harbor framework developed by the U.S. Department of Commerce in coordination with the European Union. The European Union's Directive on Data Protection prohibits the transfer of personal data to non-EU countries that do not provide an "adequate" level of privacy protection. Safe Harbor certification permits a "certified" entity to transfer personal data from the EU to the United States in accordance with the EU Directive. To learn more about the Safe Harbor program and to view LMI?s certification, please visit http://www.export.gov/safeharbor/. 
1.3.	Service Data.  When using the LMI Services You may view, collect, transmit, store and or share certain data, information, files, etc. (altogether ?Service Data?).  LMI does not own any Service Data and specifically disclaims any responsibility for any Service Data that You or any other user collects, posts or produces while using the Service.  LMI agrees that these Terms do not grant LMI any ownership rights to Service Data and LMI agrees not access or use any Service Data for any purpose other than to the extent necessary to provide the Service to You.  LMI does not select or screen Service Data and does not review, test, confirm, approve or verify the accuracy of any Service Data. You are solely responsible for any and all Service Data that You produce, transmit and/or store in the Service.  To the extent that any of Your Service Data contains third party information, files or data, it is solely Your responsibility to properly notify or obtain any applicable thirty-party consent.  

Article II.	 Using Your Account
2.1.	License Grant.  LMI hereby grants You a royalty-free, nonexclusive, worldwide, non-transferable, right and license to access, use, execute and deploy the Service and its related software for the applicable subscription term subject to the restrictions set forth in these Terms.  The Service is owned and operated by LMI and provided to You on a subscription basis; LMI is not transferring ownership or title to the Service to You.  
2.1.1. The Service is made available for download solely for use by You and only according to these Terms. Any reproduction, resale or redistribution of the Service that is not in accordance with these Terms is expressly prohibited, and may result in civil and criminal penalties. Violators will be prosecuted to the maximum extent possible. The license granted hereunder may not be transferred by You to any third party and is non-exclusive.
2.1.2. You acknowledge that the Services and their related software are proprietary to LMI and/or its suppliers and are protected by copyrights, trademarks, service marks, patents and/or other proprietary rights and laws. You may not remove any proprietary notices or labels from any of the Services. You may not alter, modify, redistribute, sell, auction, decompile, reverse engineer, disassemble or otherwise reduce any of the Services to a human-readable form. You may not reproduce, distribute or create any derivative works based on the Services without expressly being authorized in writing to do so by LMI. Further, You may not rent, lease, grant a security interest in or otherwise transfer any rights to the Services. All rights not expressly granted in these Terms are reserved to LMI and its suppliers. 
2.1.3. The license granted hereunder entitles You to receive any and all standard updates and support that LMI provides to all users of its Services, generally. Notwithstanding the previous sentence, LMI reserves the right to charge all of its users fees for any future versions of, or premium (i.e., charged for) upgrades to, the Services. You understand that LMI may update or modify any of the Services and their related software at any time, but is under no obligation to inform You of any such updates or modifications. For the avoidance of doubt, unless LMI chooses to provide such updates or modifications to all of its users, these Terms do not grant You any right, license or interest in or to any premium or ?VIP? support, maintenance, improvements, modifications, enhancements or upgrades to the Services or their related software. To the extent that LMI supplies any updates or upgrades to You, they will be deemed to be subject to these Terms, unless LMI indicates otherwise.  
2.1.4. ANY AND ALL CONTENT ON THE WEBSITES, SOFTWARE AND COMPUTER PROGRAMS ASSOCIATED WITH THE SERVICES ARE PROTECTED BY COPYRIGHT AND OTHER INTELLECTUAL PROPERTY LAWS. EXCEPT AS SPECIFICALLY PERMITTED HEREIN, NO PORTION OF THE INFORMATION OR CONTENT ON SUCH WEBSITES, SOFTWARE AND COMPUTER PROGRAMS MAY BE REPRODUCED IN ANY FORM, OR BY ANY MEANS, WITHOUT PRIOR WRITTEN PERMISSION FROM LMI. YOU AND ANY OTHER VISITOR OR USER ARE NOT PERMITTED TO MODIFY, DISTRIBUTE, PUBLISH, TRANSMIT OR CREATE DERIVATIVE WORKS OF ANY MATERIAL FOUND ON SUCH WEBSITES, SOFTWARE AND COMPUTER PROGRAMS FOR ANY PUBLIC OR COMMERCIAL PURPOSE.
2.2. End User Conduct.  You are solely responsible for the content of Your computer(s) and Your LMI account and any transmissions made when using the Services. Your use of the Services are subject to the Terms set forth herein and all applicable laws, rules and regulations, including local, state, national and international laws, rules and regulations (including without limitation those governing privacy, account collection, export control, consumer protection, unfair competition, anti-discrimination or false advertising). When using any of the Services You hereby agree: (i) to comply with all applicable laws, rules and regulations, including local, state, national and international laws, rules and regulations (including without limitation those governing privacy, account collection, export control, consumer protection, unfair competition, anti-discrimination or false advertising); (ii) not to use the Service to post, distribute, or otherwise make available or transmit any software or other computer files that contain a virus, trojan horse, worm or other harmful or destructive component; (iii) not to use the Service for any illegal purposes; (iv) not to delete from the Service or its related software, documentation or any LMI website used in connection with the Service, any legal notices, disclaimers, or proprietary notices such as copyright or trademark notices, or modify any logos that You do not own or have express permission to modify; (v) not to use the Service to interfere or disrupt any other networks connected to the Service; (vi) not to use the Service to infringe any third party's copyright, patent, trademark, trade secret or other proprietary rights or rights of publicity or privacy; and (vii) not to use the Service to distribute any unlawful, harassing, libelous, defamatory, racist, indecent, abusive, violent, threatening, intimidating, harmful, vulgar, obscene, offensive or otherwise objectionable material of any kind or nature. You shall not access or use someone else's LogMeIn account at any time, without first obtaining the permission of the account holder.  You agree that You are responsible for all actions and inactions of Your employees, consultants, or any other third party that You allow to access Your LMI account, and You agree to use commercially reasonable efforts to monitor such third party users. LMI reserves the right to disable Your account or take any other action that LMI in its sole discretion deems necessary or appropriate in the event that LMI has reason to believe that Your conduct while using any of the Services has violated the terms of this Section 2.2.
2.3.  Account Passwords & Security.  Certain Services provided by LMI hereunder require You to use an email address to create a username and choose a password for access to Your LogMeIn account (for security purposes, LMI recommends choosing a password for the Service that is different from the username and password to Your computer). LMI does not send emails asking for a user's LogMeIn username and/or password or any other username or password. To keep the Service secure, You should keep all usernames and passwords confidential.  Access to, and use of, password-protected and/or secure aspects of the Services are restricted to authorized users only. Unauthorized individuals attempting to use any of the Services may be subject to prosecution. You agree to carefully safeguard all of Your passwords. LMI does not maintain a database of user passwords so You are solely responsible if You do not maintain the confidentiality of Your passwords and account information. Furthermore, You are solely responsible for any and all activity that occurs under Your account.  LMI is not liable for any loss incurred by You resulting from another's use of Your password, account, or public/private key, as may be applicable, either with or without Your knowledge. However, You may be held liable for losses incurred by LMI or another party due to another's use of Your password, account, or public/private key, as may be applicable, either with or without Your knowledge. You agree to immediately notify LMI of any unauthorized use of Your account or any other suspected breach of security known to You, including if You believe that Your password and/or account information has been stolen or otherwise compromised.

Article III.  Payment Terms, Fees and Renewals
3.1.	Accepted Methods of Payment: 
3.1.1. Payment of Month-to-Month Subscriptions. In the event that Your subscription to a Service is on a monthly basis, payment of the subscription fee must be by preauthorized credit card charge, PayPal? charge or direct debit only, and Your subscription will automatically renew each calendar month unless You provide LMI with written notice of non-renewal during the prior calendar month. You will automatically be charged the applicable monthly subscription fee for each month or partial month that Your month-to-month subscription is in effect. 
3.1.2. Payment of Annual Subscriptions: 
3.1.2.1. Annual Subscriptions by Credit Card. In the event that Your subscription to the Service is for a year and the initial payment is by credit card, PayPal? charge or direct debit, Your subscription will automatically renew at the beginning of each subsequent anniversary year unless You give LMI prior written notice of non-renewal at least thirty (30) days prior to the expiration of Your current year subscription. 
3.1.2.2. Annual Subscriptions By Invoice. In the event that Your subscription to the Service is for a year and the initial payment is by check or bank draft against an invoice from LMI, payment shall be due within thirty (30) days' of the date of invoice. Additionally, Your subscription will automatically renew at the beginning of each subsequent anniversary year unless You or LMI give prior written notice of non-renewal at least thirty (30) days prior to the expiration of the current year subscription. 
3.1.3. Free Subscriptions. Notwithstanding the above, Your subscription to any of LMI's free Services does not require the payment of a subscription fee.  LMI reserves the right, in its sole and absolute discretion, to restrict, limit or terminate the use of ?free? or ?basic? versions of the Services by any individual, entity or group of entities.
3.2.		No Cancellations. Notwithstanding any provision of these Terms or any course of dealing between the parties, You may not cancel, terminate or rescind a subscription during its term. Any and all payments by You to LMI for access to the Services are final. 
3.3. 	Credit Card Authorization. In the event that You cancel the credit card provided to LMI to pay for the Service or the card expires or is otherwise terminated, You must immediately provide LMI with a new valid credit card number. You authorize LMI, from time to time, to undertake steps to determine whether the credit card number provided to LMI is a valid credit card number. In the event that You do not provide LMI with a current valid credit card number with sufficient credit upon request during the effective period of these Terms, You will be in violation of these Terms. You hereby authorize LMI to automatically update Your credit card information using software designed for updating purposes.
3.4. 	Paying via PayPal?. LMI also accepts payment via PayPal?. In order to pay with PayPal, You must have an account with PayPal. When You select PayPal to make payments, the transaction is re-directed from LMI's site to PayPal's payment site. When PayPal is used, Your financial information is not shared with LMI.  Once directed to PayPal's site, PayPal is charged with protecting Your personal and financial information. Your PayPal account and any activities related thereto shall be subject to PayPal's terms and conditions and any information provided to PayPal in relation thereto will be governed by PayPal's privacy policy. Once payment is complete via PayPal, PayPal will email a receipt for this transaction. LMI reserves the right to request proof of identity from any PayPal member. 
3.5. 	Payment Due. Unless otherwise provided for herein, payment of all fees are due and payable to LMI without demand, invoicing or notice before the commencement of the subscription period to which those fees apply. 
3.6.  Taxes. You agree to be responsible for and to pay any applicable sales, personal property, use, VAT, excise, withholding, or any other taxes that may be imposed, based on this license, or the use or possession of a Service, or any software or other product provided under these Terms, excluding any taxes based on net income payable by LMI. If You are exempt from paying any sales, use or other taxes, You must provide LMI with appropriate evidence of tax exemption for all relevant jurisdictions.
3.7.  Sales, Promotional Offers, Coupons, Credits. Sales, promotions and other special discounted pricing offers are temporary and upon the renewal of Your subscription, any such discounted pricing offers may expire.  LMI reserves the right to discontinue or modify any coupons, credits, sales and special promotional offers at its sole discretion. 

Article IV.  Legal Terms
4.1. Disclaimer of Warranties. Although LMI has attempted to provide accurate information with regard to the Service, LMI assumes no responsibility for the accuracy or inaccuracy of any information provided. Mention of non-LMI products or services is for information purposes only and constitutes neither an endorsement nor a recommendation. Your use of any of the Services is at Your own risk. ALL INFORMATION, DOCUMENTATION AND SERVICES PROVIDED BY LMI ARE PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE OR NON-INFRINGEMENT, OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. TO THE MAXIMUM EXTENT PERMITTED BY LAW, LMI EXPRESSLY DISCLAIMS ANY AND ALL WARRANTIES, CONDITIONS, REPRESENTATIONS, AND GUARANTEES WITH RESPECT TO THE SERVICE, WHETHER EXPRESS OR IMPLIED, ARISING BY LAW, CUSTOM, PRIOR ORAL OR WRITTEN STATEMENTS, OR OTHERWISE. LMI MAKES NO WARRANTY THAT THE SERVICE WILL MEET YOUR REQUIREMENTS OR THAT THE SERVICE WILL BE UNINTERRUPTED, TIMELY OR ERROR FREE. NOR DOES LMI MAKE ANY WARRANTY AS TO THE RESULTS THAT MAY BE OBTAINED FROM THE USE OF THE SERVICE OR THE ACCURACY OF ANY OTHER INFORMATION OBTAINED THROUGH THE SERVICE. YOU UNDERSTAND AND AGREE THAT ANY MATERIAL AND/OR DATA DOWNLOADED OR OTHERWISE OBTAINED THROUGH THE USE OF THE SERVICE IS DONE AT YOUR OWN RISK AND THAT YOU WILL BE SOLELY RESPONSIBLE FOR ANY DAMAGE TO ANY COMPUTER SYSTEM OR LOSS OF DATA THAT RESULTS FROM THE DOWNLOAD OF SUCH MATERIAL AND/OR DATA. NO REPRESENTATION OR OTHER AFFIRMATION OF FACT, INCLUDING, WITHOUT LIMITATION, STATEMENTS REGARDING CAPACITY, SUITABILITY FOR USE OR PERFORMANCE OF THE SERVICES, WHETHER MADE BY EMPLOYEES OF LMI OR OTHERWISE, WHICH IS NOT CONTAINED IN THIS AGREEMENT, SHALL BE DEEMED TO BE A WARRANTY BY LMI FOR ANY PURPOSE, OR GIVE RISE TO ANY LIABILITY OF LMI WHATSOEVER.
4.2.  Limitations of Damages and Liability. 
4.2.1. YOU AGREE THAT THE CONSIDERATION WHICH LMI IS RECEIVING HEREUNDER DOES NOT INCLUDE CONSIDERATION FOR ASSUMPTION BY LMI OF THE RISK OF YOUR SPECIAL, CONSEQUENTIAL, INCIDENTAL OR OTHER INDIRECT DAMAGES. LMI AND ITS SUPPLIERS SHALL NOT BE LIABLE FOR ANY SPECIAL, CONSEQUENTIAL, INCIDENTAL OR OTHER INDIRECT DAMAGES INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR REVENUES, COSTS OF REPLACEMENT PRODUCTS OR SERVICES, LOSS OR DAMAGE TO INFORMATION OR DATA ARISING OUT OF THE USE OR INABILITY TO USE THE SERVICE. UNDER NO CIRCUMSTANCES, INCLUDING, BUT NOT LIMITED TO, NEGLIGENCE, SHALL LMI BE LIABLE FOR DAMAGES RESULTING FROM USE OF THE SERVICE, OR RELIANCE ON THE INFORMATION PRESENTED IN CONNECTION WITH THE SERVICE, EVEN IF LMI OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. YOU AGREE NOT TO ASSERT ANY SUCH CLAIM AGAINST LMI OR ITS SUBSIDIARIES OR AFFILIATES OR THEIR RESPECTIVE OFFICERS, DIRECTORS, OR EMPLOYEES. 
4.2.2. YOU EXPRESSLY AGREE THAT YOUR USE OF THE SERVICE IS AT YOUR OWN RISK. IN NO EVENT SHALL LMI'S TOTAL LIABILITY FROM ALL DAMAGES, LOSSES, AND CAUSES OF ACTION (WHETHER IN CONTRACT, TORT OR OTHERWISE) EXCEED THE AMOUNT YOU PAID TO LMI, IF ANY, FOR THE SERVICE DURING THE 12 MONTHS IMMEDIATELY BEFORE THE CLAIM AROSE. IN THE EVENT THAT APPLICABLE LAW LIMITS THE EXCLUSION OF IMPLIED WARRANTIES OR THE ABOVE LIMITATIONS OF LIABILITY, THE MAXIMUM AMOUNT OF EXCLUSIONS ALLOWED UNDER APPLICABLE LAW SHALL BE APPLIED.
4.2.3. ALL DISCLAIMERS, LIMITATIONS OF WARRANTIES AND DAMAGES, AND CONFIDENTIAL COMMITMENTS SET FORTH IN THESE TERMS OR OTHERWISE EXISTING AT LAW (1) ARE OF THE ESSENCE OF THE AGREEMENT OF THE PARTIES, AND (2) SURVIVE ANY TERMINATION, EXPIRATION OR RESCISSION OF THESE TERMS.
4.3. 	Indemnification. You are responsible for maintaining the confidentiality of Your account and password(s). You are also responsible for all activities that occur under Your account. Therefore, You agree to indemnify, defend and hold LMI and its affiliates, employees, officers, directors, owners, information providers, agents, licensees, licensors (the "Indemnified Parties") harmless from and against any and all liabilities, claims, costs, including reasonable attorneys' fees, incurred by the Indemnified Parties in connection with any third party demand, claims, action, suit, or loss arising as a result of (a) any breach by You of these terms of use or claims arising from Your account; (b) any fraud or manipulation by You; (c) a third-party claim, action or allegation of infringement based on information, data, files or other content submitted by You; or (d) any claims of credit card fraud based on any information released by You. You agree to use best efforts to cooperate with LMI in the defense of any demand, claim, action or suit. LMI reserves the right to assume the exclusive defense of any matter subject to indemnification by You at LMI's own expense. 
4.4. 	Right to Terminate. LMI may, in its sole discretion, immediately terminate Your subscription, license and right to use the Service if (i) You fail to make timely payments of subscription fees as required for access to Your account or You declare bankruptcy, are involved in any bankruptcy proceedings or are otherwise insolvent; (ii) You breach these Terms; (iii) LMI is unable to verify or authenticate any information You provide to LMI; or (iv) LMI decides, in its sole discretion, to discontinue offering the Service to its users. LMI shall not be liable to You or any third party for termination of the Service or Your use of the Service. Upon expiration or termination for any reason, You shall no longer be authorized to use the Service. When Your access to the Service is terminated and/or Your subscription is canceled, You will no longer have access to data and other material that You may have stored in connection with the Service and that material may be deleted by LMI. All disclaimers, limitations of warranties and damages, and confidential commitments set forth in these Terms or otherwise existing at law shall survive any termination, expiration or rescission of these Terms.
4.5.  Title. Title, ownership rights and intellectual property rights in the Service shall remain with LMI or its suppliers, as applicable. The Service is protected by copyright and other intellectual property laws and by international treaties. Title and related rights in the content accessed through the Service is the property of the applicable content owner and is protected by applicable law. The licenses granted under these Terms give You no rights to such content. "LogMeIn," associated logos, and other names, logos, icons and marks identifying LMI's Services are trademarks or service marks of LMI (collectively the "Trademarks") and may not be used without the prior written permission of LMI. All other product names mentioned are used for identification purposes only and may be trademarks or service marks of their respective holders. Nothing should be construed as granting, by implication, estoppel, or otherwise, any license or right to use any Trademark without the written permission of LMI or such third party that may own the Trademarks. Your use of the Trademarks except as provided in these Terms is strictly prohibited.
4.6.	Feedback. LMI shall have a royalty-free, worldwide, perpetual license to use or incorporate into the Services any suggestions, ideas, enhancement requests, recommendations or other information provided by You relating to the operation of the Service (?Feedback?). 
4.7.  Confidentiality. You shall maintain the confidentiality of information that has been, and will continue to be, provided to You by LMI in connection with Your use of the Service. You specifically agree to the following confidentiality terms (the "Confidentiality Terms"):
4.7.1. Obligations. You shall (a) maintain in confidence all such information, including but not limited to the Service and its related software, (b) not disclose any such information to anyone except Your employees, agents, and consultants on a need-to-know basis (and who have been informed of and acknowledge their obligation to be bound by these Confidentiality Terms), and (c) not use LMI's confidential information for any purpose other than that for which it is disclosed. All confidential information shall remain the sole property of LMI. You shall have no right, title, or interest in or to the confidential information. 
4.7.2. Confidential Information. Information considered confidential by LMI includes, without limitation, information of LMI relating to (a) matters of a technical nature such as trade secret processes or devices, know-how, data, formulas, inventions (whether or not patentable or copyrighted), specifications and characteristics of products or services planned or being developed, and research subjects, methods and results, (b) matters of a business nature such as information about costs, profits, pricing, policies, markets, sales, suppliers, customers, product plans, and business concepts, plans or strategies, (c) matters of a human resources nature such as employment policies and practices, personnel, compensation and employee benefits, (d) other information of a similar nature not generally disclosed by LMI to the public or other information You should reasonably believe to be confidential given the circumstances, (e) information concerning Your use of the Service, and (f) the Service itself and its associated software. 
4.7.3. Exclusions. The obligations imposed by these Confidentiality Terms shall not apply to any information that (a) is proven by You to have been rightfully received from a third party without accompanying use or disclosure restrictions; (b) is or becomes generally publicly available through no wrongful act of You or any other person or entity with a confidentiality obligation; (c) is already known to You prior to the date of disclosure as evidenced by documentation bearing a date prior to the date of disclosure; (d) is approved for release in writing by an authorized representative of LMI; or (e) is required to be disclosed pursuant to a valid court order, duly authorized subpoena, or governmental authority (provided that You shall immediately give LMI written notice and an opportunity to contest such required disclosure). 
4.7.4. Remedies. The remedy at law for any breach of any of the covenants and agreements set forth in these Confidentiality Terms may be inadequate, so in the event of any such breach or threatened breach, LMI shall, in addition to all other remedies which may be available to it at law, be entitled to equitable relief in the form of preliminary and permanent injunctions, without the necessity of proving damages. You further agree that these Confidentiality Terms shall in no way restrict or limit any other remedies LMI may have available at law and LMI may be entitled to recover the costs, including reasonable attorney's fees, to enforce its rights under these Confidentiality Terms. 
4.7.5. Return of Confidential Information. Upon the written request of LMI, You shall return, or certify that You have destroyed, all information disclosed under these Confidentiality Terms and any memoranda, diagrams, or any other documents containing any information disclosed under these Confidentiality Terms. 
4.7.6. Enforceability. In the event any one or more of the provisions of these Confidentiality Terms shall be deemed invalid, illegal or unenforceable in any respect, the validity, legality and enforceability of the remaining provisions contained herein shall not in any way be affected or impaired thereby. 
4.7.7. Application. These Confidentiality Terms shall control in lieu of and notwithstanding any proprietary or restrictive legends or statements inconsistent with these Confidentiality Terms that may be associated with any particular information disclosed hereunder. 
4.7.8. Surviving Obligations. The confidentiality obligations imposed under these Confidentiality Terms shall survive any termination, expiration, or rescission of these Terms or Your subscription term, as well as continue beyond any time in which You were using the Service.
4.8. 	Disclaimer of High Risk Activities.  The Services are not fault-tolerant and are not designed, manufactured or intended for use or resale as or with on-line control equipment in hazardous environments requiring fail-safe performance, including, but not limited to, equipment used to operate nuclear facilities, aircraft navigation or aircraft communication systems or air traffic control, direct life support machines or weapon systems, in which the failure of the Services could lead directly to death, personal injury or severe physical or environmental damage ("High Risk Activities"). Accordingly, LMI and its suppliers specifically disclaim any express or implied warranty of fitness for such High Risk Activities.
4.9.	Compliance with Export Laws & Regulations. The Services and their related software are subject to United States Export Administration Regulations. No software or Service may be downloaded, used or exported (i) into (or to a national or resident of) Cuba, Iran, North Korea, Sudan, Syria, or any other country to which the United States has embargoed goods; or (ii) any person or entity on the United States Treasury Department's list of Specially Designated Nationals or the U.S. Commerce Department's Denied Persons List or Entity List, or otherwise designated as prohibited from receiving U.S. exports. By subscribing to the Service or using any of its related software, You represent and warrant that You are not- and are not controlled by - any such person or entity and are not controlled by a national or resident of any such country.
4.10. Force Majeure. No party shall be liable for any performance failure, delay in performance, or lost data under these Terms (other than for delay in the payment of money due and payable hereunder) to the extent said failures or delays are proximately caused by: (i) failures of software or other computer programming (other than the Service purchased hereunder); (ii) natural weather events; or (iii) any other causes beyond that party's reasonable control and occurring without its fault or negligence, including, without limitation, failure of suppliers, subcontractors, and carriers; provided that in any such event, as a condition to the claim of non-liability, the party experiencing the difficulty shall give the other prompt written notice, with full details following the occurrence of the cause relied upon.

Article V.  Miscellaneous Contract Terms
5.1.	Entire Agreement. These Terms represent the complete agreement concerning the subject matter of the license granted hereunder and Your use of any of the Services. LMI may amend these Terms at any time by (i) posting a revised Terms document on or accessible through https://secure.logmein.com and/or (ii) sending information regarding the Terms amendment to the email address You have provided to LMI. You are responsible for regularly reviewing the https://secure.logmein.com site to obtain timely notice of such amendments. You manifest intent to accept these amended terms if You continue to use the Service after such amended terms have been posted or sent to You. If You do not agree with any such amended terms You must notify LMI during the 30-day period after such amended terms have been posted and at the end of such 30-day period these Terms shall be deemed terminated unless LMI agrees to waive such amended terms to which You object. 
5.2. Governing Law & Venue. These Terms shall be governed by and construed in accordance with the laws of the Commonwealth of Massachusetts and the laws of the United States, without giving effect to any principles of conflict of law. You agree that any action at law or in equity arising out of or relating to these Terms shall be filed only in the state or federal courts located in Boston, Massachusetts, and You hereby consent and submit to the personal jurisdiction of such courts for the purposes of litigating any such action. The parties specifically disclaim applicability of (i) the United Nations Convention on the Sale of Goods and (ii) any Incoterms.
5.3. 	Severability. If any of the provisions of these Terms shall be unlawful, void, or for any reason unenforceable, then that provision shall be deemed severable from these Terms and shall not affect the validity and enforceability of any remaining provisions. 
5.4.	Publicity. LMI shall have the right to identify You as a user of the Service. You agree that LMI may use any logo and/or name associated with You on LMI's website and other materials in order to identify You as a LMI user. 
5.5. 	Notices. Notices by LMI to You may be sent to the email address You provide on the Registration Form or otherwise by any means that LMI determines in its sole discretion as likely to come to Your attention. All notices sent by You to LMI in connection with these Terms shall be in writing and sent by first class mail or certified mail (receipt being deemed 72 hours after postage and return receipt requested) or personally delivered at the address of LMI set forth herein. 
5.6. 	Waiver. You agree not to bring or participate in any class action lawsuit against LMI or any of its employees or affiliates. You agree not to bring a claim under these Terms more than two years after the expiration of these Terms. The failure of LMI to partially or fully exercise any right shall not prevent the subsequent exercise of such right. The waiver by LMI of any breach shall not be deemed a waiver of any subsequent breach of the same or any other term of these Terms. No remedy made available to LMI by any of the provisions of these Terms is intended to be exclusive of any other remedy, and each and every remedy shall be cumulative and in addition to every other remedy available at law or in equity.
5.7. No Exclusivity. You acknowledge and agree that LMI is in the business of providing remote access, remote support, collaboration and data management solutions and that LMI may provide such services to third parties, including any competitors of You, which are the same or similar to the Services provided to You hereunder.
5.8. 	Assignment. These Terms shall be binding upon and inure to the benefit of the parties and their permitted assigns. Neither party may assign this Agreement, assign its rights or delegate its duties hereunder (whether directly or indirectly, in whole or in part, by operation of law or otherwise), without the prior written consent of the other party, which shall not be unreasonably withheld or delayed. Notwithstanding the foregoing, LMI may assign this Agreement, without Your prior written consent in connection with a merger, acquisition, change of control or sale of substantially all of its assets (or any substantially similar transaction). Additionally, LMI may assign all or any part of the performance of this Agreement to an Affiliate Entity without Your prior written consent. For the purposes of this section, the term "Affiliate Entity" shall mean any entity that now or in the future controls, is controlled by, or is under common control with LMI.

Article VI.  Additional Terms for Remote Access, Management & Support Services
6.1.	Using Remote Access, Management & Control Features. Certain features of LMI?s remote access, management and support services, such as LogMeIn? CentralTM, LogMeIn for Android or iOS, LogMeIn Pro?, AppGuru?, LogMeIn Rescue? and LogMeIn? Rescue+MobileTM, allow You to remotely access and/or remotely control a computer, server or other device; remotely monitor and manage certain cloud applications; and/or remotely transfer files from one device to another.  By clicking through these Terms, using any of these Services or otherwise indicating Your acceptance of these Terms, You hereby agree that You will not (i) use any of our remote access, management and support Services to attempt to gain unauthorized access to computer systems or devices that you do not have permission to access or otherwise interfere with another User's use and enjoyment of our Services or other cloud applications; (ii) use the Services to distribute or transmit any software or other computer files that contain a virus, Trojan horse, worm or other harmful or destructive component;  (iii) use the Services under false pretenses to gain access to a third party?s PII, computer systems or other devices or applications; or (iv) use the Services for any other illegal or unauthorized purposes.  You agree that You are responsible for the actions and inactions of Your employees and consultants and will use commercially reasonable efforts to monitor Your employees and consultants. LMI reserves the right to disable Your account or take any other action that LMI in its sole discretion deems necessary or appropriate, including pursuing legal action, in the event that LMI has reason to believe that You have violated the terms of this Section.
6.2.	SMS Messaging. If You are licensing Rescue+Mobile pursuant to these Terms, You are entitled to a combined maximum of one hundred (100) SMS text messages per seat, per month. If You exceed this combined maximum amount per seat, per month, You agree to negotiate in good faith with LMI a commercially reasonable rate per text message over one hundred (100) per seat, per month.

Article VII.  Additional Terms for Collaboration Services
7.1.	Using LMI?s Collaboration Services. LMI?s Collaboration Services, CubbyTM and join.me?, allow You to host online meetings, share Your screen and files with other users and sync and store Your files in the cloud and/or across multiple devices so that they can easily be shared with others.  By clicking through these Terms, using any of these Collaboration Services or otherwise indicating Your acceptance of these Terms, You hereby agree that You will not (i) use the Services to share, store or transmit any unlawful, harassing, libelous, defamatory, racist, indecent, abusive, violent, threatening, intimidating, harmful, vulgar, obscene, offensive or otherwise objectionable material of any kind or nature; or (ii) use the Services to share copyrighted material that You do not own or have permission to share or distribute.
7.2.	Collaboration Disclaimer. LMI is not responsible for the images/sounds/etc. you may view or experience while viewing another party?s screen, folders, files, etc.  LMI has no obligation to monitor any information stored on or shared through the Services and is not responsible for the accuracy, appropriateness or legality of any files, posts, links or other information You may be able to share or access while using the Services.
7.3.	Use of the join.me Conference Line.  The join.me conference line is licensed by LMI from a third-party telecommunications provider that grants You access to the conference line directly.  For the avoidance of doubt, LMI is not itself a telecommunications provider and does not itself provide any telecommunications-related services.  If You are licensing join.me pursuant to these Terms, the join.me conference line is free to use, but it is not a toll-free number. While LMI does not charge You for the use of the conference line, applicable roaming, data and other operator or carrier charges/fees may apply.  You understand and agree that You are solely responsible for paying for any such charges/fees.  International dial-in numbers are only active on calls hosted by a pro subscriber.
7.4.  Recording Disclosure.  Customer understands that use of join.me?s conference recording feature may subject Customer to laws or regulations regarding the recording of telephone calls and other electronic communications, and that it is thus Customer?s responsibility to properly notify all participants in a recorded join.me meeting that the meeting is being recorded.  LMI will not be held liable for Customer?s failure to do so.  Although features may exist in the Service to alert participants that a meeting is being recorded, such notice may not be relied upon as definitive disclosure for Customer?s compliance with applicable laws.
7.5.	Sharing Your Cubby. The Cubby Service permits You to share Your Cubby with others or make Your Cubby public. You shall retain full ownership of the files that You store within Your Cubby and these Terms do not grant LMI any title, ownership or intellectual property rights to any of Your files, except for the limited rights that are required to provide the Service to You.  However, You should carefully consider what You choose to share with other users as LMI has no responsibility for any files that You share with others. You agree not to use Cubby to share any files that You do not have the legal right to share with others. You understand and agree that purchasing or otherwise legally obtaining documents, videos, music, software or other forms of media does not necessarily grant You the right to distribute or publicly share those files with third parties through the Service. By sharing Your Cubby with other users, You are representing that You either (i) own all copyrights in the files You have placed in Your Cubby or (ii) have obtained permission from the rightful copyright holder to share such files.

_________________________________________________________________________________________________________Copyright ? 2003 - 2016 LogMeIn, Inc. All rights reserved.
Certain Services may contain open source software. Please review https://secure.logmein.com/policies/openSourceDisclosure.aspx for the required disclosures and disclaimers regarding such open source software.   Certain Services use code of http://ffmpeg.org licensed under the http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html and its source can be downloaded http://ffmpeg.org.
Certain Services are provided under U.S. patent No. 7,310,736 and related patents.

tools\chocolateyInstall.ps1

$packageArgs = @{
  packageName   = 'join.me'
  unzipLocation = "$(Split-Path -parent $MyInvocation.MyCommand.Definition)"
  fileType      = 'msi'
  url           = 'https://www.join.me/Download.aspx?installer=win&webdownload=true'
  silentArgs    = '/quiet'
  validExitCodes= @(0)
  softwareName  = 'join.me*'
}

Install-ChocolateyPackage @packageArgs

Virus Scan Results

join.me.msi (2aa50e2590c4) - ## / 61
join.me.msi (dd5c7918fe1f) - ## / 61
join.me.3.2.1.523301.nupkg (bfa314eda35f) - ## / 60

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version History

Add to Builder	Version	Downloads	Last Updated	Status
	join.me 3.2.1.523301	10509	Monday, June 11, 2018	Approved
	join.me 3.2.1.5233	1103	Wednesday, July 12, 2017	Approved

Dependencies

This package has no dependencies.

Discussion for the join.me Package

Ground Rules:

This discussion is only about join.me and the join.me package. If you have feedback for Chocolatey, please contact the Google Group.
This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
Tell us what you love about the package or join.me, or tell us what needs improvement.
Share your experiences with the package, or extra configuration or gotchas that you've found.
If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.

Resources

Events

Courses

13,766

10,509

11 Jun 2018

join.me

join.me 3.2.1.523301

All Checks are Passing

Deployment Method: Individual Install, Upgrade, & Uninstall

Deployment Method:

1. Enter Your Internal Repository Url

2. Setup Your Environment

1. Ensure you are set for organizational deployment

2. Get the package into your environment

3. Copy Your Script

4. If applicable - Chocolatey configuration/installation

Note:

Ground Rules: