Chocolatey Central Mangement (CCM)
Chocolatey Central Management (CCM) provides you insights across your desktop and endpoint environments. CCM is available with Chocolatey for Business only.
Once installed and configured, you can use CCM to:
- Bring reporting to the organizational level
- Quickly see all software across the organization and see what needs attention immediately
- Create reports for tracking and auditing purposes
- Manage endpoints with deployments through groups and collections
This provides an overview on Chocolatey Central Mangement (CCM). It provides both setup and use of CCM.
- CCM Components
- Getting CCM
- Stay Up To Date
- Related Articles
- How do I take advantage of Chocolatey Central Management?
- I'm a licensed customer, now what?
- Will this become available for lower editions of Chocolatey?
- What's the minimum version of the Chocolatey packages I need to use CCM?
- Where can I find all the log files for Chocolatey Central Management
- Where can I find the changelog or release notes for Chocolatey Central Management?
- How do I get support?
- How do I set up Chocolatey Central Management?
- What is the CCM compatibility matrix?
- If I update the license file, do I need to restart my services and web?
- Common Errors and Resolutions
The following are all of the Chocolatey components required for Central Management to work.
- Chocolatey (
- Chocolatey for Business (C4B) Edition.
- Chocolatey Licensed Extension (
- Chocolatey Agent (
- CCM Database (
- This deploys the CCM database schema to a specified SQL Server instance
- CCM Service (
- This installs the CCM Service, which the Chocolatey Agent will communicate with.
- CCM Website (
- This is the CCM front end website that is the main user interface of the application
CCM Component Compatibility Matrix
Central Management has specific needs that are mostly handled by packaging aspects. As the Chocolatey Agent and Central Management communicate with each other, there are some versions that may not be compatible with each other due to mistakes or fixes that needed to be implemented. This serves as a means of capturing that for you.
Central Management packages (all three) are treated as a singular unit, meaning all three packages across one or more machines must all be on the same version. Using different versions of Central Management packages (db, service, web) is completely unsupported and likely will not even work properly.
|Central Management||Chocolatey Agent||Chocolatey Licensed Extension||Chocolatey|
CCM is only available for Chocolatey for Business (C4B) customers. If you are a C4B customer, you can head to the install components section:
If you are not a customer yet, you can reach out for a trial.
Trials are limited to organizations. If you are personally wanting to work with CCM and other C4B components, you can purchase a C4B starter pack - see pricing.
Stay Up To Date
Setup / Installation
- Central Management Setup
- Central Management Client Setup
Setup / Upgrade
Using Central Management
Chocolatey Central Management will allow:
Centralized Software Management for your entire organization.Completed June 2020. Centralized reporting of software.Completed May 2019 Know immediately what software is out of date and on what machines.Completed May 2019 Know within seconds the entire estate of software and what versions are installed.Completed May 2019 Including zips and archives* that do not show up in Programs and FeaturesCompleted May 2019 Including internal software* that does not show up in Programs and FeaturesCompleted May 2019
- Adhoc reporting for a particular machine or set of machines
Run arbitrary Chocolatey commands against one or more machinesCompleted June 2020. See how many machines you are actively managing in your organizationCompleted May 2019
* - When deployed through Chocolatey.
How do I take advantage of Chocolatey Central Management?
You must have a Business edition of Chocolatey. Business editions are great for organizations that need to manage the total software lifecycle.
I'm a licensed customer, now what?
See Getting CCM.
Will this become available for lower editions of Chocolatey?
CCM will only be available in Chocolatey for Business (C4B).
What's the minimum version of the Chocolatey packages I need to use CCM?
See CCM Components.
Where can I find all the log files for Chocolatey Central Management
Chocolatey Central Management is made up of a number of components, so there will be a few possible places to find the log files, which you may be asked for when engaging with support.
- The Chocolatey Central Management Website log file located at
c:\tools\chocolatey-management-web\App_Data\Logs\ccm-website.log. If you are on a version of CCM prior to 0.2.0, the log will be located at
- The Chocolatey Central Management service log file is located at
$env:ChocolateyInstall\logs\ccm-service.log. If you are on a version of CCM prior to 0.2.0, the log will be located at
- The Chocolatey Agent log file is located at
$env:ChocolateyInstall\logs\chocolatey-agent.log. If you are on a version of Chocolatey Agent prior to 0.10.0, the log will be located at
Where can I find the changelog or release notes for Chocolatey Central Management?
Please see Release Notes Central Management.
How do I get support?
choco support from a licensed edition and follow the instructions.
How do I set up Chocolatey Central Management?
What is the CCM compatibility matrix?
Central Management has specific compatibility requirements with quite a few moving parts. It is important to understand that there are some Chocolatey Agent versions that may not be able to communicate with some versions of CCM and vice versa. Please see the CCM Component Compatibility Matrix for details.
If I update the license file, do I need to restart my services and web?
Yes, you do need to restart the agents, the service, and the web to pick up the license. Here's a handy script:
Get-Service chocolatey-* | Stop-Service Get-Process ChocolateySoftware.ChocolateyManagement.Web.Mvc | Stop-Process Get-Service chocolatey-* | Start-Service
For your agent machines:
Get-Service chocolatey-* | Stop-Service Get-Service chocolatey-* | Start-Service
Common Errors and Resolutions
Computers checking in are overwriting each other
You are generating machines from a base image that already had Chocolatey commercial code on it. This is okay, but you need to remove the Chocolatey Machine Id Guid, which is used to identify a machine as unique.
When the licensed agent service is installed on a machine, a unique machine id is given to the machine. If you are starting from a template, there is no opportunity for that to be different and when those machines start checking in, they will start overwriting each other.
Basically you need to go find the machine id at
UniqueId) and remove it as part of your image deployment mechanism.
Write-Host "Removing Chocolatey Unique Machine GUID" Remove-ItemProperty -Path "HKLM:\Software\Chocolatey" -Name "UniqueId" -Force # Restart the Agent Service if it is running
Once you've removed this, you'll need to restart the Agent Service to get it regenerated.
ℹ️ You may also need to remove the ChocolateyLocalAdmin user (if you are using it for services) and reinstall the Agent service (and CCM service if on this machine) to get that password corrected.
An Internal error occurred during your request
Check the log files. You may have incorrect database access, but most likely it can come because you didn't follow the steps for setup appropriately.
System.Data.SqlClient.SqlException: Invalid column name
This means you are upgrading things out of order. Please make sure your database is upgraded first, then the service, then the web.