community.chocolatey.org
Open in
urlscan Pro
2606:4700:10::6814:4a1c
Public Scan
URL:
https://community.chocolatey.org/packages/sql-server-management-studio
Submission: On August 31 via manual from US — Scanned from DE
Submission: On August 31 via manual from US — Scanned from DE
Form analysis 4 forms found in the DOM
GET /packages
<form class="search-box search-d-submit " autocomplete="off" role="search" action="/packages" method="get">
<div class="flex-grow-1">
<input name="q" type="search" class="form-control search-input" id="searchQuery" placeholder="Search Packages" aria-label="Search Packages" value="" autofocus="">
<i class="fa-solid fa-magnifying-glass" aria-hidden="true"></i>
<span class="d-none d-md-flex search-key-container">
<span class="badge font-monospace text-bg-primary search-key">ctrl</span>
<span class="badge font-monospace text-bg-primary">k</span>
</span>
</div>
<button type="submit" aria-label="Search Packages" class="btn btn-outline-primary ms-2" title="Search Packages" value="">Search</button>
<button type="button" aria-label="Close search" class="btn btn-search-close btn-outline-primary ms-2"><i class="fa-solid fa-xmark" aria-hidden="true"></i></button>
<div class="search-help position-absolute w-100 top-100 start-0 end-0">
<div class="arrow-up position-absolute">
<div class="arrow-up-inner position-relative"></div>
</div>
<div class="card card-body text-bg-theme-elevation-1 mt-3 me-3 rounded d-md-flex flex-md-row justify-content-md-between border">
<p class="mb-md-0 small"><strong>id:searchValue</strong> search by id only</p>
<p class="mb-0 small"><strong>tag:searchValue</strong> search by tags</p>
</div>
</div>
</form>POST /users/account/LogOff
<form action="/users/account/LogOff" method="post">
<fieldset>
<input name="__RequestVerificationToken" type="hidden" value="50me8ZYAR0onizfXg4QFrmQX/5w/yPVR/Qd3IaMphtk+QRqz7NyKluxVhL/JvuoYIzLG+MbkZnoRHGup32roSnAESpg6aXqqeUZKw21mkksgnNoHx3LjJIS5p1BkkZ+bUTUD4R755dHrbKHniVsxDHpXhc4JbWSEI+I8VK12kuk=">
<button class="btn link-theme m-0 p-0" type="submit"><i class="fa-solid fa-right-from-bracket fa-flip-horizontal text-primary w-15-px text-center me-3"></i>Sign Out</button>
</fieldset>
</form>POST /users/account/LogOff
<form action="/users/account/LogOff" class="w-100 user-authenticated" method="post">
<fieldset class="nav-link">
<input name="__RequestVerificationToken" type="hidden" value="v5OV8+vbv0O1KELL2MU5I5dXGqCcxp0jK/iso8CEH3ydfwO8wwPc1yPPH6BZuMfp7LfBg8nYv4j6OJWbFKzW2xzkAEv6wbT2nJ3i0DQZWIA30NoOUVj6PmVOEbtwtpkP7CNlLdjK8MOj31Z3hHQkoaSEHmxFhCdGryP+2dwWtQE=">
<button class="btn link-theme m-0 p-0" type="submit">Sign Out</button>
</fieldset>
</form>Name: mc-embedded-subscribe-form — POST //chocolatey.us8.list-manage.com/subscribe/post?u=86a6d80146a0da7f2223712e4&id=73b018498d
<form action="//chocolatey.us8.list-manage.com/subscribe/post?u=86a6d80146a0da7f2223712e4&id=73b018498d" method="post" id="mc-embedded-subscribe-form" name="mc-embedded-subscribe-form" class="validate" target="_blank" novalidate="">
<div class="row align-items-center justify-content-center">
<div class="col-md-auto text-center text-md-start">
<h3 class="mb-0">Signup for the Newsletter!</h3>
</div>
<div class="col-md-3">
<input type="email" title="Email Address for Newsletter" class="form-control email mt-2 mt-md-0" id="mce-EMAIL" placeholder="Your e-mail address" value="" name="EMAIL" required="">
</div>
<div style="position: absolute; left: -5000px;">
<input title="Invisible Field" type="text" name="b_86a6d80146a0da7f2223712e4_73b018498d" tabindex="-1" value="">
</div>
<div class="col-md-auto">
<button type="submit" class="btn btn-theme-background mt-2 mt-md-0 w-100" id="mc-embedded-subscribe"><strong>Subscribe</strong></button>
</div>
</div>
<p class="mb-0 mt-1 text-center"><i>Be the first to know about upcoming features, security releases, and news about Chocolatey.</i></p>
</form>Text Content
1
RESOURCES
Watch videos, read documentation, and hear Chocolatey success stories from
companies you trust.
View Resources
EVENTS
Find past and upcoming webinars, workshops, and conferences. New events have
recently been added!
View Events
COURSES
Step-by-step guides for all things Chocolatey! Earn badges as you learn through
interactive digital courses.
View Courses
--------------------------------------------------------------------------------
Join the Chocolatey Team on our regular monthly stream where we discuss all
things Community, what we do, how you can get involved and answer your
Chocolatey questions.
Add to Calendar
Learn More
--------------------------------------------------------------------------------
Join the Chocolatey Team on our regular monthly stream where we put a spotlight
on the most recent Chocolatey product releases. You'll have a chance to have
your questions answered in a live Ask Me Anything format.
Add to Calendar
Learn More
--------------------------------------------------------------------------------
Livestream from
Thursday, 9 June 2022
Join James and Josh to show you how you can get the Chocolatey For Business
recommended infrastructure and workflow, created, in Azure, in around 20
minutes.
Watch On-Demand
--------------------------------------------------------------------------------
Livestream from
Tuesday, 29 November 2022
Join Josh as he adds the ability to manage Chocolatey GUI config and features
with the Chocolatey Ansible Collection.
Watch On-Demand
--------------------------------------------------------------------------------
Livestream from
Thursday, 03 November 2022
Join Paul and Gary for this months Chocolatey product livestream where we look
at the latest release of Chocolatey 1.2.0, Chocolatey Licensed Extension 5.0.0
and shine a spotlight on the new hook scripts functionality. This opens up so
many possibilities for Chocolatey CLI users!
Watch On-Demand
--------------------------------------------------------------------------------
Livestream from
Thursday, 06 October 2022
We recently released our largest update to Chocolatey Central Management so far.
Join Gary and Steph to find out more about Chocolatey Central Management and the
new features and fixes we've added to this release.
Watch On-Demand
--------------------------------------------------------------------------------
Livestreams from
October 2022
For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory,
James, Gary, and Rain as they share knowledge on how to contribute to
open-source projects such as Chocolatey CLI.
Watch On-Demand
--------------------------------------------------------------------------------
Webinar from
Tuesday, 13 December 2022
Join Gary, Paul, and Maurice as they introduce and demonstrate how to use
Chocolatey! Questions will be answered live in an Ask Me Anything format.
Watch On-Demand
--------------------------------------------------------------------------------
Webinar Replay from
Wednesday, 30 March 2022
At Chocolatey Software we strive for simple, and teaching others. Let us teach
you just how simple it could be to keep your 3rd party applications updated
across your devices, all with Intune!
Watch On-Demand
--------------------------------------------------------------------------------
Livestream from
Thursday, 04 August 2022
Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the
not so distant future. We'll talk about some cool new features, long term asks
from Customers and Community and how you can get involved!
Watch On-Demand
--------------------------------------------------------------------------------
* Main
* Community
* Docs
* Blog
* Install
*
1
ctrl k
Search
id:searchValue search by id only
tag:searchValue search by tags
* * Main
* Community
* Docs
* Blog
* Install
*
* Packages
* Learn
* Resources
* Courses
* Product
Products
* Chocolatey for Business
* Pro Edition
* Chocolatey Open Source
* Compare Editions
* Pricing
* Support
Solutions
* Self-Service Anywhere
* Central Management Deployments
* Secure Offline Deployments
Ready to give Chocolatey for Business a Try?
We offer a 14 day white glove free trial to help get you started.
Start Trial
* Connect
* Events
* Careers
* Newsletter
* Chocolatey Community
* Support
* Contact
*
*
*
*
*
*
*
*
*
* --------------------------------------------------------------------------------
* Sign In
* Sign Up
* * Profile
* Account
* --------------------------------------------------------------------------------
* Sign Out
* Profile
* Account
* Sign Out
Welcome to the Chocolatey Community Package Repository! The packages found in
this section of the site are provided, maintained, and moderated by the
community.
MODERATION
Every version of each package undergoes a rigorous moderation process before it
goes live that typically includes:
* Security, consistency, and quality checking
* Installation testing
* Virus checking through VirusTotal
* Human moderators who give final review and sign off
More detail at Security and Moderation.
ORGANIZATIONAL USE
If you are an organization using Chocolatey, we want your experience to be fully
reliable. Due to the nature of this publicly offered repository, reliability
cannot be guaranteed. Packages offered here are subject to distribution rights,
which means they may need to reach out further to the internet to the official
locations to download files at runtime.
Fortunately, distribution rights do not apply for internal use. With any edition
of Chocolatey (including the free open source edition), you can host your own
packages and cache or internalize existing community packages.
DISCLAIMER
Your use of the packages on this site means you understand they are not
supported or guaranteed in any way. Learn more...
I Understand
Generate Script
0 B U I L D E R
* STEP1
Package Review
* STEP2
Integration Method
* STEP3
Install Script / Config
* STEP4
Environment Setup
* STEP5
Install Script
Previous Next
STEP 1: REVIEW YOUR PACKAGES
STEP 2: CHOOSE YOUR INTEGRATION METHOD
* Generic
* Individual
* Ansible
*
* PS DSC
*
STEP 3: ENTER YOUR INTERNAL REPOSITORY URL
(this should look similar to https://community.chocolatey.org/api/v2/)
STEP 3: COPY YOUR SCRIPT OR DOWNLOAD CONFIG
OPTION 1: COPY SCRIPT
OPTION 2: DOWNLOAD CONFIG
Save as .config File
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
You must enter your internal repository url above before proceeding.
## 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 = "http://internal/odata/repo"
### 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
}
Copy
See docs at
https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 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: http://internal/odata/repo
### 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
Copy
See docs at https://docs.chef.io/resource_chocolatey_package.html.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 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 = "http://internal/odata/repo"
### 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 = "http://internal/odata/repo/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
Copy
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
#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 = "http://internal/odata/repo",
### b. Chocolatey nupkg download url ###
#### This url should result in an immediate download when you navigate to it in
#### a web browser
$ChocolateyNupkgUrl = "http://internal/odata/repo/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
}
Copy
Requires Puppet Chocolatey Provider module. See docs at
https://forge.puppet.com/puppetlabs/chocolatey.
If Applicable - Chocolatey Configuration/Installation
You must enter your internal repository url above before proceeding.
## 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 = 'http://internal/odata/repo'
### 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 = 'http://internal/odata/repo/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'],
}
}
Copy
Previous Next
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
Delete and Add New Version Cancel
Downloads:
2,662,702
Downloads of v 19.1.56:
75,937
Last Update:
15 JUN 2023
Package Maintainer(s):
* flcdrg
Software Author(s):
* Microsoft
Tags:
sql server management studio ssms admin
* Software Specific:
* Software Site
* Software License
* Software Mailing List
* Software Issues
* Package Specific:
* Package Source
* Package outdated?
* Package broken?
* Contact Maintainers
* Contact Site Admins
* Software Vendor?
* Report Abuse
* Download
SQL SERVER MANAGEMENT STUDIO 19.1
* 1
* 2
* 3
19.1.56 | Updated: 15 Jun 2023
Show Additional Links
* Software Specific:
* Software Site
* Software License
* Software Mailing List
* Software Issues
* Package Specific:
* Package Source
* Package outdated?
* Package broken?
* Contact Maintainers
* Contact Site Admins
* Software Vendor?
* Report Abuse
* Download
Downloads:
2,662,702
Downloads of v 19.1.56:
75,937
Maintainer(s):
* flcdrg
Software Author(s):
* Microsoft
Tags:
sql server management studio ssms admin
SQL SERVER MANAGEMENT STUDIO 19.1 19.1.56
* 1
* 2
* 3
THIS PACKAGE CONTAINS AN EXEMPTED CHECK
Not All Tests Have Passed
Hide Checks
Hide Checks
--------------------------------------------------------------------------------
Validation Testing Passed
--------------------------------------------------------------------------------
Verification Testing Exemption:
Exempted due to necessary KB update not being available.
Details
--------------------------------------------------------------------------------
Scan Testing Successful:
No detections found in any package files
Details
*
*
* Generic
* Individual
* Ansible
*
* PS DSC
*
Add to Script Builder Learn More
--------------------------------------------------------------------------------
DEPLOYMENT METHOD: INDIVIDUAL INSTALL, UPGRADE, & UNINSTALL
* Install
* Upgrade
* Uninstall
To install SQL Server Management Studio 19.1, run the following command from the
command line or from PowerShell:
>
To upgrade SQL Server Management Studio 19.1, run the following command from the
command line or from PowerShell:
>
To uninstall SQL Server Management Studio 19.1, run the following command from
the command line or from PowerShell:
>
DEPLOYMENT METHOD:
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 sql-server-management-studio --internalize --source=https://community.chocolatey.org/api/v2/
Copy
* For package and dependencies run:
You must enter your internal repository url above before proceeding.
choco push --source="'http://internal/odata/repo'"
Copy
* Automate package internalization
--------------------------------------------------------------------------------
3. COPY YOUR SCRIPT
You must enter your internal repository url above before proceeding.
choco upgrade sql-server-management-studio -y --source="'http://internal/odata/repo'" [other options]
Copy
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:
You must enter your internal repository url above before proceeding.
choco upgrade sql-server-management-studio -y --source="'http://internal/odata/repo'"
$exitCode = $LASTEXITCODE
Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
Exit 0
}
Exit $exitCode
Copy
You must enter your internal repository url above before proceeding.
- name: Install sql-server-management-studio
win_chocolatey:
name: sql-server-management-studio
version: '19.1.56'
source: http://internal/odata/repo
state: present
Copy
See docs at
https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.
You must enter your internal repository url above before proceeding.
chocolatey_package 'sql-server-management-studio' do
action :install
source 'http://internal/odata/repo'
version '19.1.56'
end
Copy
See docs at https://docs.chef.io/resource_chocolatey_package.html.
You must enter your internal repository url above before proceeding.
cChocoPackageInstaller sql-server-management-studio
{
Name = "sql-server-management-studio"
Version = "19.1.56"
Source = "http://internal/odata/repo"
}
Copy
Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.
You must enter your internal repository url above before proceeding.
package { 'sql-server-management-studio':
ensure => '19.1.56',
provider => 'chocolatey',
source => 'http://internal/odata/repo',
}
Copy
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.
Package Approved
This package was approved as a trusted package on 15 Jun 2023.
Description
--------------------------------------------------------------------------------
SQL Server Management Studio (SSMS) is an integrated environment for managing
any SQL infrastructure, from SQL Server to Azure SQL Database. SSMS provides
tools to configure, monitor, and administer instances of SQL Server and
databases. Use SSMS to deploy, monitor, and upgrade the data-tier components
used by your applications and build queries and scripts.
The SSMS 19.x installation doesn't upgrade or replace SSMS versions 18.x or
earlier. SSMS 19.x installs alongside previous versions, so both versions are
available for use.
Beginning with SQL Server Management Studio (SSMS) 18.7, Azure Data Studio is
automatically installed alongside SSMS. As a consequence of this, uninstalling
this package will impact azure-data-studio if you had that package installed
previously.
VERSION NUMBER
This package is versioned using the published build number. The corresponding
'release number' is included in the package title.
SUPPORTED SQL OFFERINGS
* This version of SSMS works with SQL Server 2014 and higher and provides the
most significant level of support for working with the latest cloud features
in Azure SQL Database and Azure Synapse Analytics.
* Additionally, SSMS 19.x can be installed alongside with SSMS 18.x, SSMS 17.x,
SSMS 16.x.
* SQL Server Integration Services (SSIS) - SSMS version 17.x or later doesn't
support connecting to the legacy SQL Server Integration Services service. To
connect to an earlier version of the legacy Integration Services, use the
version of SSMS aligned with the version of SQL Server. For example, use SSMS
16.x to connect to the legacy SQL Server 2016 Integration Services service.
SSMS 17.x and SSMS 16.x can be installed side by side on the same computer.
Since the release of SQL Server 2012, the SSIS Catalog database, SSISDB, is
the recommended way to store, manage, run, and monitor Integration Services
packages. For details, see SSIS Catalog.
SSMS SYSTEM REQUIREMENTS
The current release of SSMS supports the following 64-bit platforms when used
with the latest available service pack:
Supported Operating Systems:
* Windows 11 (64-bit)
* Windows 10 (64-bit) version 1607 (10.0.14393) or later
* Windows Server 2022 (64-bit)
* Windows Server 2019 (64-bit)
* Windows Server 2016 (64-bit)
PACKAGE SPECIFIC
UPGRADING FROM 18.X TO 19.X
As mentioned above, SSMS 19.x doesn't upgrade 18.x but will install side by
side. If you don't wish to keep 18.x then you should run choco uninstall
sql-server-management-studio prior to installing the latest version of this
package.
PACKAGE PARAMETERS
* SSMSExePath:PathToFile - Use this installer exe instead of downloading
To pass parameters, use --params "''" (e.g. choco install packageID [other
options] --params="'/ITEM:value /ITEM2:value2 /FLAG_BOOLEAN'").
To have choco remember parameters on upgrade, be sure to set choco feature
enable -n=useRememberedArgumentsForUpgrades.
Example:
choco install sql-server-management-studio --params
"'/SSMSExePath:c:\Downloads\SSMS-Setup-ENU.exe'"
PACKAGE UPDATES
This package is automatically updated based on the same data source that SSMS
itself uses to determine when updates are available. This may mean that there
may sometimes be a delay between Microsoft releasing a new version and when they
'advertise' it as being generally available for SSMS to update.
Files
--------------------------------------------------------------------------------
Show tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop';
$release = '19.1'
$fullUrl = 'https://download.microsoft.com/download/a/c/a/aca4e29f-6925-4d50-a06b-5576c6ea629f/SSMS-Setup-ENU.exe'
$fullChecksum = 'FDC2CE3EA167882874B26D06796FE2DC21DE03394E6D3F72ACD28F0836C9FF9E'
$packageArgs = @{
packageName = $env:ChocolateyPackageName
fileType = 'EXE'
silentArgs = "/quiet /install /norestart /log `"$env:TEMP\chocolatey\$($env:ChocolateyPackageName)\$($env:ChocolateyPackageVersion)\SSMS.MsiInstall.log`""
validExitCodes= @(0, 3010, 1641)
softwareName = "SQL Server Management Studio - $release"
}
$pp = Get-PackageParameters
if ($pp['SSMSExePath'])
{
$packageArgs.file = $pp['SSMSExePath']
Install-ChocolateyInstallPackage @packageArgs
}
else
{
$packageArgs.url = $fullUrl
$packageArgs.checksum = $fullChecksum
$packageArgs.checksumType = 'SHA256'
Install-ChocolateyPackage @packageArgs
}
Virus Scan Results
--------------------------------------------------------------------------------
Log in or click on link to see number of positives.
* sql-server-management-studio.19.1.56.nupkg (5e384b51ad36) - ## / 63
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 SQL Server Management
Studio 19.1 19.1.56 75937 Thursday, June 15, 2023 Approved SQL Server Management
Studio 19.0.2 19.0.20209.0 97858 Thursday, March 23, 2023 Approved SQL Server
Management Studio 19.0.1 19.0.20200.0 68338 Saturday, February 4, 2023 Approved
SQL Server Management Studio 18.12.1 15.0.18424.0 272064 Friday, June 24, 2022
Exempted SQL Server Management Studio 18.11.1 15.0.18410.0 137484 Tuesday, March
15, 2022 Exempted SQL Server Management Studio 18.10 15.0.18390.0 225989
Wednesday, October 13, 2021 Exempted SQL Server Management Studio 18.9.2
15.0.18386.0 123041 Wednesday, July 21, 2021 Approved SQL Server Management
Studio 18.9.1 15.0.18384.0 142187 Friday, April 23, 2021 Approved SQL Server
Management Studio 18.8 15.0.18369.0 154670 Tuesday, December 22, 2020 Approved
SQL Server Management Studio 18.7.1 15.0.18358.0 82300 Friday, October 30, 2020
Approved SQL Server Management Studio 18.6 15.0.18338.0 106467 Friday, July 24,
2020 Approved SQL Server Management Studio 18.5.1 15.0.18333.0 46914 Wednesday,
June 17, 2020 Approved SQL Server Management Studio 18.5 15.0.18330.0 85010
Friday, April 10, 2020 Approved SQL Server Management Studio 18.4 15.0.18206.0
110633 Tuesday, November 19, 2019 Approved SQL Server Management Studio 18.3.1
15.0.18183.0 35781 Thursday, October 3, 2019 Approved SQL Server Management
Studio 18.2 15.0.18142.0 190 Thursday, October 3, 2019 Approved SQL Server
Management Studio 18.1 15.0.18131.0 99193 Friday, June 14, 2019 Approved SQL
Server Management Studio 18.0 15.0.18118.0 84800 Monday, April 29, 2019 Approved
SQL Server Management Studio 17.9.1 14.0.17289.1 348623 Wednesday, November 28,
2018 Approved SQL Server Management Studio 17.9 14.0.17285.0 82072 Thursday,
September 13, 2018 Approved SQL Server Management Studio 17.8.1 14.0.17277.0
54428 Tuesday, July 10, 2018 Approved SQL Server Management Studio 17.7
14.0.17254.0 48055 Friday, May 11, 2018 Approved SQL Server Management Studio
17.6 14.0.17230.0 11568 Friday, March 30, 2018 Approved SQL Server Management
Studio 17.5 14.0.17224.0 28017 Friday, February 16, 2018 Approved SQL Server
Management Studio 17.4 14.0.17213.0 30545 Friday, December 8, 2017 Approved SQL
Server Management Studio 17.3 14.0.17199.0 24166 Thursday, October 12, 2017
Approved SQL Server Management Studio 14.0.17177.0 32516 Tuesday, August 8, 2017
Approved SQL Server Management Studio 14.0.17119.0 18509 Monday, May 29, 2017
Approved SQL Server Management Studio 14.0.17099.20170503 3971 Wednesday, May 3,
2017 Approved SQL Server Management Studio 14.0.17099.0 1387 Friday, April 28,
2017 Approved SQL Server Management Studio 13.0.16106.4 14851 Saturday, January
28, 2017 Approved SQL Server Management Studio 13.0.16105.4 751 Tuesday, January
24, 2017 Approved SQL Server Management Studio 13.0.16100.1 1699 Tuesday,
December 6, 2016 Approved SQL Server Management Studio 13.0.16000.28 1977
Thursday, October 27, 2016 Approved SQL Server Management Studio 13.0.15900.1
961 Friday, September 30, 2016 Approved SQL Server Management Studio
13.0.15800.18 976 Wednesday, September 21, 2016 Approved SQL Server Management
Studio 13.0.15700.28 1684 Tuesday, August 16, 2016 Approved SQL Server
Management Studio 13.0.15600.2 1023 Monday, July 18, 2016 Approved SQL Server
Management Studio 13.0.15500.91 522 Thursday, July 7, 2016 Approved SQL Server
Management Studio 13.0.15000.23 587 Thursday, June 2, 2016 Approved SQL Server
Management Studio 13.0.14000.36-preview 532 Saturday, April 16, 2016 Exempted
SQL Server Management Studio 13.0.13000.55-preview 497 Saturday, April 2, 2016
Exempted SQL Server Management Studio 13.0.12500.29-preview 511 Sunday, March
20, 2016 Exempted SQL Server Management Studio 13.0.12000.65-preview 477
Tuesday, March 8, 2016 Exempted SQL Server Management Studio
13.0.11000.78-preview 504 Tuesday, March 1, 2016 Exempted
Show Additional Versions
Copyright
--------------------------------------------------------------------------------
Microsoft 2019
Release Notes
--------------------------------------------------------------------------------
https://docs.microsoft.com/en-au/sql/ssms/release-notes-ssms
If you have a preview versions of SSMS 18.0 installed, uninstall it and reboot
before installing SSMS 18.0 GA.
Dependencies
--------------------------------------------------------------------------------
This package has no dependencies.
Discussion for the SQL Server Management Studio 19.1 Package
--------------------------------------------------------------------------------
GROUND RULES:
* This discussion is only about SQL Server Management Studio 19.1 and the SQL
Server Management Studio 19.1 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 SQL Server Management Studio 19.1,
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.
SIGNUP FOR THE NEWSLETTER!
Subscribe
Be the first to know about upcoming features, security releases, and news about
Chocolatey.
OVERVIEW
* Getting Started Guide
* Security
* Privacy Policy
* Partner
* Terms of Use
PRODUCT
* C4B Trial
* Pricing
* Support
* Community Packages
LEARN
* Docs
* Courses
* Sitemap
* Blog
CONNECT
* Contact Us
* Support
* Newsletter
* Shop
* Report a Bug
* Status
* *
*
*
*
*
*
*
*
*
© 2023 Chocolatey Software, Inc.
Deployed from 5e383528a8. You are on EC2AMAZ-TCSQG95. Page generated 31 Aug 2023
17:16:32 +00:00.
chocolatey.org uses cookies to enhance the user experience of the site.
I accept I accept
chocolatey.org uses cookies to enhance the user experience of the site.
I accept I accept
Please enable JavaScript to view the comments powered by Disqus.