Chocolatey packages contains powershell scripts that manage the desired software. It's a very flexible and powerful way to do it, since the scripts can deal with all kinds of checking and tweaking.
Also take a look at package feed.
Chocolatey is a solid package manager, but the question with Chocolatey is the quality of the packages. Not the architecture of the package, but the scripts inside the package.
The challenge with building a good package is to collect the information that is necessary to make the deployment silent, to not restart the computer, close programs, etc. This is a common challenge regardless of the deployment method.
The web portal helps you manage:
- Package creation and package uploads
- Application and license inventory
- Wake computers (WOL)
- Remote Powershell
Note: clear your browser's cache to get the latest version of the website.
Groups makes it easy to deploy applications on multiple computers simultaneously.
For example you can:
Name a group “My Office”, add all computers in your office to that group, and add multiple applications to it like 7zip, Adobe Reader etc.
Or, add a group named “Office 2016” and add all computers you want to have Office 2016, and then only add the app Microsoft Office 2016 to that group.
The nice thing with this is that when you later add a computer to one of your groups, that computer will automatically get all the apps that you have added to that group.
Consider group packages as policies. An installed group package will tell your computers to install that package according to your schedule (if any), but the actual deployment status of that package is in your computer view or in the group stats.
For example, if a group package says “Command: Install”, it means that the policy for that package and selected version is to install that package on the computers in that group, when possible.
Group package schedule
The schedule will be active between the start date and end date. It will run if the time range and week days are matching the current time of the computer.
Here's an example of keeping an application up to date (every day between 06:00 PM and 06:00 AM, until year 1 nov. 2024).
Application and license inventory
Collects all applications for all computers, and licenses for some applications like Microsoft Windows, Microsoft Office, AutoCAD etc.
It provide a complete list of all installed applications, and applications ever existed since installation of the Deployment client. This is handy if you are reinstalling a computer but lost the license key, or just want to keep track of what is installed on the computers.
There are two views, one for a single computer and one for all computers. In the view for a single computer, you can right click on the application (license field) and edit the license. In the view of all computers (link is in the domain view menu), a collective view appears that makes it easy to see all computers that have that program.
Download the MSI package in the domain view.
Installation package will:
- Copy files to %programfiles%\JAHA IT\Deployment client\.
- Install Deployment client as a service.
- Create two users, one named "deployment client", and one named "dpshare". First user is for running deploymentclient.exe as a service, and second is for sharing packages with other Deployify-computers in the same local network (with authentication, needs to be in the same Deployify domain, read only permissions, not in the administrators group).
- Generate a strong, random password, for the service user.
- Add service user to local administrators group.
- Start the service.
Note that the service password is not stored. We don't know the password and you don't know it. No one does. The local system account could be an alternative, but that is less secure and also doesn't work for some deployments.
- Install/upgrade Chocolatey
- Pair client with server
The installation package (MSI) contains a pairing key that is generated when you are downloading it from the Web portal. The pairing key is bound to the specific domain with a chosen expire date. After the MSI is installed on the computer, the service will start and pair the client with the server.
Pairing means that the computer gets a new unique key from the server with the help of the pairing key. The new key is bound to that specific computer (while the pairing key is not). The pairing key will be deleted after the pairing is completed.
Now that the computer has the computer-bound key, the first step to connect the computer to the server socket is to get a temporary authentication key. To do this, the computer first generates a time-limited token with hashed computer information that is used for asking the server for the temporary authentication key. When this is done and the temporary key is received, the connection socket connection can be made. The temporary key is invalidated the moment it is used.
This is a fairly complicated authentication procedure that makes it hard to replicate for bad intentions.
- Managing Chocolatey
- Synchronizing existing software
- Keeping track of schedules
- Managing local network sources
- Repository protection mechanism
Makes sure that Chocolatey is installed.
Synchronizing existing computer software with packages that exists in your package feed(s). Eg. if 7-zip is installed on a computer and exists in any of your feeds, then it will show on the website as installed. This means that you gain control of your software so that you can manage it immediately.
Keeping track of schedules, so that commands are being executed in the desired time window.
This is a beautiful feature that free up your internet connection.
Let's say you want to deploy an application with a size of 1 GB on 10 computers. If all of them would download the package from the repository at the same time, the internet connection of your repository would choke (or at least be awfully slow). Deployment client solves this by letting one computer install the package first, and then let the other computers get the package from that computer when the installation is done. It also makes sure that the computer that is downloading the package are the computer on the network with most resources.
So, as long as the package exist at some computer in the local network, it will be fetched locally by the other computers in the same network.
Yes, I know that this sounds dangerous, but this feature has secured communications and many measures to make sure that the package is the right one and only using computers in the same domain.
The video below was meant to demonstrate how to install a group package, but as I was recording it I realized that this nice feature was in action.
Note that this feature only applies for the repos that are included in Deployify.
If you are managing applications for multiple organizations, you may not want the organization to be able to access your repo. The URL to your feed can be logged or sniffed when Chocolatey installing packages, but with this feature that's not a problem.
First, the API key is never sent to your computer. The computer generates a token based on information that only the Deployment Client and the repo server has. The token is then baked into the URL that is passed to Chocolatey as a "source". That token is only valid a short time period and only have read permissions. The generated URL can still be used to download packages from the repo but only for a limited time period, and since there is only read permissions, no changes can be made with the generated URL.
What's a package feed?
It's simply a web service that contains information about packages, where to download them, and the packages themselves. Sometimes it's called a repository, repo, feed or just a source.
Chocolatey doesn't need a package feed, it can install packages directly from a file, or just a folder with package files (.nupkg).
You can have multiple feeds added in the Web portal. This let you access all packages through one portal. The url to the feed is stored in the Deployify database and pushed to the client on connection. See Repository protection mechanism in the section above.
Deployify provide you with a private and secure package feed automatically when you are signing up, but you can add as many as you want.
There's also a community feed that contains 5200+ packages that is automatically added into your portal.
Note that most of the packages in the community feed doesn't contain the actual software due to the lack of rights to distribute them. And since the packages doesn't contain the software, you don't have any use of the local network source feature we provide with the Deployment client. That's why we have made it really easy to create your own self-contained packages.
How to Get Started