Андрей Смирнов
Время чтения: ~26 мин.
Просмотров: 6

Troubleshooting

Creating Packages

ERROR: Cannot bind parameter because parameter ‘fileType’ is specified more than once.

This error is seen sometimes on versions of Chocolatey older than 0.10.6. The problem is likely you have the following in your packaging:

didn’t have both a parameter and a parameter. PowerShell has a «feature» where it does partial matching of parameters. When you splat the parameters in, it tries to apply both and to and throws the above error.

Typically, when you are installing locally, you likely want to use anyway.

ERROR: This package does not support 64 bit architecture.

This means you have set up your arguments for a function and then called something like instead of . Note is for splatting, taking the values in the hash variable and using the key/values to pass those each as parameters to a function, where just passes the entire hash as the first parameter of the function.

NOTE: It is helpful to always use when creating packages, it has this correct and you never run into this error.

References:

ERROR: A null key is not allowed in a hash literal.

Typically you see this if you accidentally use a variable name on the left side of a hash:

Note the use of on the left side, which should be just . Once you fix that, things should start working appropriately.

Reference

Server

Many IT teams still rely on manual configurations, custom scripts, golden images or outdated tools to manage Windows infrastructure. This results in errors and slow deployments, or worse — unpatched environments that leave you susceptible to security incidents.

From a server point of view you need to ensure a consistent, reliable approach without having manual intervention, and allowing you to run the businesses on the software and having to care, water, and feed the servers.
When you get to the world of cloud and containers this is only amplified as you are managing the unknown.

Chocolatey provides a standardized, scalable approach to server management. From setting up a new server, to ensuring critical updates are in place, or supporting a migration project.

What Are Chocolatey Packages?

Chocolatey packages are known as nupkg files, which is a compiled NuSpec or a fancy zip file that knows about package metadata (including dependencies and versioning). These packages are an enhanced NuGet package, they have additional metadata that is specific to Chocolatey. Chocolatey is also compatible with vanilla NuGet packages. A Chocolatey package can contain embedded software and/or automation scripts.

The closer the underlying software a package represents is to the package (as in executables and files included in the package), the more Chocolatey behaves like a package manager.

Requirements

Chocolatey Clients

With Chocolatey clients, we ensure that Chocolatey is going to run with low memory footprints because you will have all aspects of things you will need to manage and different space and memory available across all of those clients. Chocolatey has a very wide reach into where it can be installed.

For Chocolatey clients, you will need the following:

  • Windows 7+/Windows 2003+ (Server Core also, but not Windows Nano Server)
  • Windows PowerShell v2+ (not PowerShell Core aka PowerShell 6 yet)
  • .NET Framework 4.x+

Chocolatey Components

  • Chocolatey CLI aka choco (or choco.exe) is a client (not a Windows service) that provides the core of Chocolatey and the installation store for locally installed packages. This is important as Chocolatey manages packages, not Programs and Features directly — Programs and Features is limited only to software that has «installers» and Chocolatey treats all aspects of Windows software as first class citizens (zips, scripts, binaries, installers), thus it needs to track and manage those things separately.
  • Chocolatey GUI is an application that runs when a user runs it (also not a Windows Service).

Space Requirements

  • Chocolatey CLI has an impact of 15 MB on default install plus the space the installed packages use up.
  • Chocolatey GUI takes up another 50-100 MB of space on default installation.
  • Chocolatey Agent (aka chocolatey-agent) is a Windows service available in Chocolatey for Business — it has an impact of about 10 MB.

RECOMMENDATION: We recommend enough free space for the applications you will install plus another 1 GB for allowing Chocolatey to process that. You will want to turn on Package Reducer (commercial editions) if you have it to really reduce the impact of embedded packages, which bring reliability but also increase footprint (unless you have Package Reducer). If you don’t have Package Reducer and you are embedding binaries into nupkgs, you will need 3 times the space of what you are installing unless you explicitly clean up the extracted installers/zips in your automated scripts — then you will need 2x the space when considering the nupkg will still contain embedded binaries (and the nupkg must stick around). Unfortunately, this is going to be a calculation to understand exact space requirements and it really depends on what you will install.

Memory Requirements

  • Chocolatey CLI only runs when called. It falls into managed memory thus can work in environments with low amounts of memory provided that they have enough memory available to manage software installations.
  • Chocolatey GUI only runs when the application is open and is also in managed memory. It can work on systems with low amounts of memory.
  • Chocolatey Agent (aka chocolatey-agent) — it is always running but has a very low footprint unless it is processing something.

RECOMMENDATION: At least 2GB of RAM at a bare minimum, but recommend at least 8GB for managing installations.

Chocolatey Repository Servers

Unforunately it’s harder to make recommendations here as it is really dependent on the repository that you choose and what requirements they have. It varies from a Windows deployment to Linux deployed repositories, from Java-based, to .NET-based, to PHP, and Rust-based repositories. The requirements vary wildly, plus you may use those repositories that address multiple types of packages and would need to figure out the space available for that.

SPACE RECOMMENDATION: Have enough space for 10x the size of the installers and other software you will store. This will allow for some default growth. We would recommend 100 GB at a minimum.

Requirements coming soon. Just imagine normal recommendations for an ASP.NET IIS deployment, a SQL Server back end, and 1+ Windows Services (depending on scale).

Преимущества данного способа установки программ

y http-equiv=»Content-Type» content=»text/html;charset=UTF-8″>le=»text-align: justify;»>Подводя итог, еще раз отмечу преимущества использования менеджера пакетов Chocolatey для установки программ (для начинающего пользователя):

  1. Вы получаете официальные программы из надежных источников и не рискуете, пытаясь найти то же ПО в Интернете.
  2. При установке программы не требуется следить за тем, чтобы не установилось чего-либо ненужного, будет установлено чистое приложение.
  3. Это действительно быстрее, чем поиск официального сайта и страницы загрузки на нем вручную.
  4. Вы можете создать файл сценария (.bat, .ps1) или просто установить сразу все нужные бесплатные программы одной командой (например, после переустановки Windows), то есть для установки двух десятков программ, включая антивирусы, утилиты и проигрыватели, вам нужно лишь один раз ввести команду, после чего даже не понадобиться нажимать кнопку «Далее».

Надеюсь, кому-то из моих читателей эта информация будет полезной.

А вдруг и это будет интересно:

Submitting Issues

  1. Start with Troubleshooting and the FAQ to see if your question or issue already has an answer.
  2. If not found or resolved, please follow one of the following avenues:
    • If you have found an issue with the GUI (Chocolatey GUI) or you want to submit an enhancement, please see .
    • If you have found an issue with the client (choco.exe), you are in the right place. Keep reading below.

Observe the following help for submitting an issue:

Prerequisites:

  • The issue has to do with choco itself and is not a package or website issue.
  • Please check to see if your issue already exists with a quick search of the issues. Start with one relevant term and then add if you get too many results.
  • You are not submitting an «Enhancement». Enhancements should observe CONTRIBUTING guidelines.
  • Please make sure you’ve read over and agree with the .

Submitting a ticket:

  • We’ll need debug and verbose output, so please run and capture the log with or . You can submit that with the issue or create a gist and link it.
  • Please note that the debug/verbose output for some commands may have sensitive data (passwords or apiKeys) related to Chocolatey, so please remove those if they are there prior to submitting the issue.
  • choco.exe logs to a file in . You can grab the specific log output from there so you don’t have to capture or redirect screen output. Please limit the amount included to just the command run (the log is appended to with every command).
  • Please save the log output in a gist (save the file as ) and link to the gist from the issue. Feel free to create it as secret so it doesn’t fill up against your public gists. Anyone with a direct link can still get to secret gists. If you accidentally include secret information in your gist, please delete it and create a new one (gist history can be seen by anyone) and update the link in the ticket (issue history is not retained except by email — deleting the gist ensures that no one can get to it). Using gists this way also keeps accidental secrets from being shared in the ticket in the first place as well.
  • We’ll need the entire log output from the run, so please don’t limit it down to areas you feel are relevant. You may miss some important details we’ll need to know. This will help expedite issue triage.
  • It’s helpful to include the version of choco, the version of the OS, and the version of PowerShell (Posh) — the debug script should capture all of those pieces of information.
  • Include screenshots and/or animated gifs whenever possible, they help show us exactly what the problem is.

Common Errors and Resolutions

When you are attempting to install the Simple Server, you may run into some errors depending on your configuration. Here are some common ones we’ve seen that you may get when you browse to the the site.

This can mean a couple of things:

  • You missed ensuring the website is using an app pool that is at least .NET 4.0. Check the app pool that your site is using, then ensure that app pool has enabled and the managed runtime version is (or some version of 4).
  • You have made a change to the xml file and it is not valid xml. This typically happens if you put an xml escape character into the password (). To do that you would need to set CData around the value or use a different password. It could also happen if you accidentallly change the xml and it is no longer valid.
  • You are attempting to set up Chocolatey Server next to WSUS Administration website. For an unknown reason, something won’t register correctly with Chocolatey Server and its need for ASP.NET 4.6+. So we recommend not putting the Chocolatey Server next to that website. Find a machine with the WSUS administration site.

Naming your package

The title of your package ( tag in the nuspec) should be the same as the name of the application. Follow the official spelling, use upper and lower case and don’t forget the spaces. Examples of correct package titles are: Google Chrome, CCleaner, PuTTY and FileZilla. The title will appear on the left side in the package list of the Chocolatey gallery, followed by the version.

There are some guidelines in terms of the package id ( tag in the nuspec):

  • Use only lowercase letters, even if you used uppercase letters in the package title. (This is considered a guideline because it is correctable in other ways). Once a package is submitted (even prior moderation), the Gallery will always show the id with the casing of the first package version. In addition, changing the casing of the package id may have negative side effects on dependencies (note: this last statement needs verified).
  • If the original application name consists of compound words without spaces (CamelCase), just as MKVToolNix, TightVNC and VirtualBox, the package id’s are simply the same (but lowercase of course): , , and .
  • If the name of the application contains multiple words separated by spaces, such as MusicBrainz Picard or Adobe Reader, replace the spaces with the hyphen-minus character “-” (U+002D) or just omit them. Don’t use dots. They should be used only if the original application name contains dots (e. g. Paint.NET). Hence the correct id’s of the previously mentioned applications can be or . It is highly suggested to use the hyphen method when there are long package names, because that increases readability.
  • For sub-packages, use the hyphen-minus character “-” (U+002D) as separator, not a dot. Sub-packages are intended for separate packages that include extensions, modules or additional features/files for other applications. Therefore is a proper package id, because it adds the language files for the main application which in this case is KeePass. Another example is for the help pack for LibreOffice, the open source office suite.

These guidelines are already commonly applied on packages for all major Linux distributions, because they lead to a more consistent look of software repositories, easier to remember package id’s and less considerations about the naming for package creators.

Note that a lot of packages in the Chocolatey Gallery don’t follow these guidelines. The simple reason is that the affected packages were created before the introduction of these guidelines.

Committers

Committers, you should be very familiar with COMMITTERS.

Compiling / Building Source

There is a / file that creates a necessary generated file named . It must be run at least once before Visual Studio will build.

Windows

Prerequisites:

  • .NET Framework 3.5 (This is a windows feature installation).
  • .NET Framework 4+
  • Visual Studio is helpful for working on source.
  • ReSharper is immensely helpful (and there is a file to help with code conventions).

Build Process:

Run build.bat.

Running the build on Windows should produce an artifact that is tested and ready to be used.

Prerequisites:
  • Install and configure Mono 5.20.x (Other versions may work but have not been tested).
# install prerequisites
sudo apt install apt-transport-https dirmngr gnupg ca-certificates
# add the key
sudo apt-key adv --keyserver hkp://keyserver.ubuntu.com:80 --recv-keys 3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF

# add the package repository
# Debian 10
echo "deb https://download.mono-project.com/repo/debian stable-buster main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list
# Debian 9
echo "deb https://download.mono-project.com/repo/debian stable-stretch main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list
# Ubuntu 18.04
echo "deb https://download.mono-project.com/repo/ubuntu stable-bionic main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list
# Ubuntu 16.04
echo "deb https://download.mono-project.com/repo/ubuntu stable-xenial main" | sudo tee /etc/apt/sources.list.d/mono-official-stable.list

# update package indexes
sudo apt-get update
# install
sudo apt-get install mono-devel -y

CentOS/RHEL

### NOT FULLY TESTED AND WORKING ###
# Switch to root shell
su
# Add the EPEL
yum install epel-release -y
# Add the key
pmkeys --import "http://pool.sks-keyservers.net/pks/lookup?op=get&search=0x3fa7e0328081bff6a14da29aa6a19b38d3d831ef"

# Add the package repository
# CentOS/RHEL 8
su -c 'curl https://download.mono-project.com/repo/centos8-stable.repo | tee /etc/yum.repos.d/mono-centos8-stable.repo'
# CentOS/RHEL 7
su -c 'curl https://download.mono-project.com/repo/centos7-stable.repo | tee /etc/yum.repos.d/mono-centos7-stable.repo'
# CentOS/RHEL 6
rpm --import "http://pool.sks-keyservers.net/pks/lookup?op=get&search=0x3fa7e0328081bff6a14da29aa6a19b38d3d831ef"

# Update your system
yum update -y

# Install mono-devel
yum install mono-devel -y

Fedora

### NOT FULLY TESTED AND WORKING ###

# Switch to root shell
su
# Add the key
rpm --import "https://keyserver.ubuntu.com/pks/lookup?op=get&search=0x3FA7E0328081BFF6A14DA29AA6A19B38D3D831EF"

# Add the package repository
# Fedora 29
su -c 'curl https://download.mono-project.com/repo/centos8-stable.repo | tee /etc/yum.repos.d/mono-centos8-stable.repo'
# Fedora 28
su -c 'curl https://download.mono-project.com/repo/centos7-stable.repo | tee /etc/yum.repos.d/mono-centos7-stable.repo'

# Update
dnf update

# Install mono-devel
dnf install mono-devel -y
  • Xamarin Studio is helpful for working on source.
  • Consider adding the following to your (or other relevant dot source file):
# mono
# http://www.michaelruck.de/2010/03/solving-pkg-config-and-mono-35-profile.html
# http://cloudgen.wordpress.com/2013/03/06/configure-nant-to-run-under-mono-3-06-beta-for-mac-osx/
export PKG_CONFIG_PATH=/opt/local/lib/pkgconfig:/Library/Frameworks/Mono.framework/Versions/Current/lib/pkgconfig:$PKG_CONFIG_PATH

Set your permissions correctly:

chmod +x build.sh
chmod +x zip.sh
Build Process:

Run ./build.sh.

Running the build on Mono produces an artifact similar to Windows but may have more rough edges. You may get a failure or two in the build script that can be safely ignored.

0.10.3

BREAKING CHANGES

Fix — Do Not Check $LastExitCode — Only error a package install if script errors or set a different exit code when it is specifically set — see #1000

Starting in v0.9.10, Chocolatey started checking in addition to the script command success as a way to be more helpful in determining package failures. This meant it offered the ability to capture when a script exited with and handle that accordingly. However that really has never been a recommended scenario for returning errors from scripts and is not seen in the wild anywhere so it is believed that those that may be affected are very few.

Checking checks the last executable’s exit code when the script specifically does not call (which is . This can lead to very perplexing failures, such as running a successful xcopy that exits with and seeing package failures without understanding why. Since it is not typically recommended to call to return a value from PowerShell because of issues with different hosts, it’s less of a concern to only look at explicit failures. For folks that may need it, allow failing a package again by the last external command exit code or from a PowerShell script. Note that it is not recommended to use exit with a number to return from PowerShell scripts. Instead you should use or (first available in v0.9.10) to ensure proper setting of the exit code.

If you need the prior behavior, please turn on the feature .

Character encoding

  • Byte Order Mark (BOM) is optional for .. A is not required but it won’t hurt anything if it is found.
  • PowerShell scripts need to be saved in UTF-8 with . PowerShell is ignoring the standards and needs a in order to recognize scripts as . Otherwise it processes non characters incorrectly.
  • Don’t use the default Windows Editor. While newer versions of Notepad have improved its ability to handle line endings and UTF-8 w/out BOM, it is still behind in capabilities as compared to other editors. Alternatives:
  • Use this XML declaration: .

Note: There is a lot of confusion in the world of character encodings: For example, is an incorrect term for the internal Windows character encodings, e. g. . But you should not use this encoding family anyway.

Package icon guidelines

If there is an icon which is suitable for your package, you can specify it in the tag in the nuspec. But there are a few things you should consider:

  • Avoid hotlinking icons from sites where you don’t have control over the file. If you have a packages repository (recommended), use your own copy of the icon and put it there.
  • Use package icons with at least 128 pixels in width or height if available. However, avoid very high resolutions, because this would only unnecessarily increase the page load time. If there are only icons with less than 128 pixels available, choose the icon with the highest resolution you can find without upscaling it. Don’t use low resolution favicons as package icons.
  • Use icons with transparent background if available.
  • Don’t use distorted or blurry icons.
  • The package list in the gallery shows the icons with a maximum of 48 pixels in width/height. Application logos with very detailed graphics that are barely visible at that dimension are not suitable as package icons.
  • PNG is the preferred format for raster package icons. Avoid ICO, GIF and JPEG graphics.

The icon shown on the Chocolatey.org package page is saved, and served, locally to mitigate against cross scripting attacks and to prevent getting non HTTPS assets errors on the website. Sometimes the page loads faster than the image can be served and the default image gets cached and as a result the new package icon may not be shown until you clear the browser cache for Chocolatey.org and wait 3 hours before reloading the page.

0.10.1

Perhaps the biggest improvement in this release is that Chocolatey will automatically look to see if it can download binaries over HTTPS when provided an HTTP url. If so, Chocolatey will switch to downloading the binaries over SSL. This provides better security in downloading and knowing you are getting the binary from the source location instead of a possible man in the middle location, especially when the package does not provide checksums for verification.

Another improvement you may not even notice, but we think you will love is that Chocolatey now supports TLS v1.2 transport which presents a nice transparent increase in security. You will need to have at least .NET Framework 4.5 installed to take advantage of this feature.

Requirements

  • .NET Framework 4.6+.
  • You need a Windows box with at least 50GB of free space (or where ever you are going to put the packages).
  • 50GB of free space for where ever you will put packages.
  • We recommend at least 8GB RAM, but more if you can.
  • Ability to set up an IIS site and unblock website ports.
  • If you have an IIS site for WSUS administration, Chocolatey.Server website will not come up at all, even if everything looks right. We have not yet been able to determine the issue, but believe it is related to ASP.NET 4.6+. Installing all of the required components for Chocolatey.Server may also affect your WSUS admin site. Please seek a different box.
  • If you can ensure your server is up to date with all of the Windows Updates, you will move through this process quite a bit quicker.

Package description and release notes

The of the package should contain a short text or at least a few words about the software for which the package is made. Here are a few things that should be respected:

  • The description should always be written in English, even if the packaged software does not provide an UI in English. You can also include the software’s description in its original language, but insert it after the English description.
  • The description should not just contain a repetition of the package name.
  • It should not just consist of a link where more information can be found. For that purpose there’s already .
  • The contents of and also are parsed as Markdown, so don’t insert line breaks in the middle of sentences. Remember to add empty lines to separate paragraphs and add an empty line before a list.

Using Chocolatey

  1. Open a command line.
  2. Type and press Enter.
  3. If you have UAC turned on or are not an administrator, Chocolatey is going to request administrative permission at some point (at least once during the process). Otherwise it will not be able to finish what it is doing successfully. If you don’t have UAC turned on, it will just continue on without stopping to bother you.
  4. That’s it. Pretty simple but powerful little concept!

Overriding default install directory or other advanced install concepts

  1. If you wanted to pass native argument to the installer, like the install directory, you would need to know the silent argument passed to that particular installer and then you would specify it on the command line or in the packages.config.

Rules to be observed before publishing packages

There are a few rules that you have to follow before pushing packages to chocolatey.org:

  1. Don’t package illegal software. Packages of software that is illegal in most countries in the world are prohibited to publish on Chocolatey.org. This applies in particular to software that violates the copyright, pirated software and activation cracks. Remember that this also affects software that is especially designed to accomplish software piracy.
  2. Packaging commercial or trial software? Clearly state this in the package description. Does it require an activation key? Is there a trial period if you don’t have a key? How long is this trial period?
  3. Do not publish junk or malware packages.
  4. Split dependencies into multiple packages. Try to split up packages as much as possible. If for example a program comes with additional modules/installers that are optional, make different packages for them instead of including all the things into one package. This idea is already widely applied for Linux packages, because it leads to a more lightweight system and reduces potential issues and conflicts.

Where are Chocolatey packages installed to?

Chocolatey packages are installed to , but the software could go to various locations, depending on how the package maintainer created the package.

Some packages are installed under , others — especially packages that are based on Windows installers (.msi files) — install to the default path of the original installer (which is most likely within ).

There are also packages for which you can set a custom installation path. These packages (like ruby) use the environment variable. If this variable does not exist, it will be created as e.g. . To change this behaviour, you can set to an existing folder, e. g. . Packages that use the environment variable, will then be installed in the given subfolder, f. ex. .

Используем менеджер пакетов Chocolatey в Windows

Для того, чтобы скачать и установить любую программу с использованием менеджера пакетов, вы можете использовать командную строку или Windows PowerShell, запущенные от имени администратора. Для этого вам достаточно всего лишь ввести одну из команд (пример для установки Skype):

  • choco install skype
  • cinst skype

При этом, будет автоматически загружена и установлена последняя официальная версия программы. Более того, вы не увидите предложений согласиться на установку нежелательного ПО, расширений, изменения поиска по умолчанию и стартовой страницы браузера. Ну и последнее: если вы укажите через пробел несколько названий, то все они будут по очереди установлены на компьютер.

В настоящий момент таким образом можно установить около 3000 бесплатных и условно бесплатных программ и, естественно, вы не можете знать названия всех из них. В этом случае вам поможет команда choco search.

К примеру, если попробовать установить браузер Mozilla, то вы получите сообщение об ошибке, что такая программа не найдена (еще бы, ведь браузер называется Firefox), однако choco search mozilla позволит понять в чем ошибка и следующим шагом достаточно будет ввести cinst firefox (номер версии указывать не требуется).

Отмечу, что поиск работает не только по названиям, но и по описанию доступных приложений. Например, для поиска программы записи дисков, можно поискать по ключевому слову burn, и в результате получить список с нужными программами, включая те, в названии которых burn не фигурирует. Полный список доступных приложений вы можете посмотреть на сайте chocolatey.org.

Аналогичным образом можно удалить программу:

  • choco uninstall имя_программы
  • cuninst имя_программы

или обновить ее с помощью команд choco update или cup. Вместо имени программы можно использовать слово all, то есть choco update all обновит все программы, установленные с помощью Chocolatey.

How Do I Install The Licensed Edition?

  1. You received a license file in email.
  2. Open PowerShell.exe as an administrative shell. You can type Windows Key + X + A (Windows 8+ — when that comes up if it is cmd.exe, simply type to get into it).
  3. In PowerShell, run — this creates the license directory. Alternatively, you can put the license in your user profile directory, e.g. , however we only recommend you do this for Professional licenses as for other licensing you may need it to be recognized by multiple users.
  4. Now place that license file in that license folder. You can do this manually, or you can adapt this PowerShell command — . (See image below)
  5. Verify the license file is set properly. In PowerShell, run If that returns something, it means you are good to go. If not, something is misspelled or misplaced somewhere.
  6. Run this command: (or you can call instead of ). You will see an error you can safely ignore.
  7. Run this command: . You should not see any error message logged anymore (like you saw in the previous run asking you to install the licensed extension). If you do see an error message still, you may need to revisit these steps and determine what might have been missed or mistyped.
  8. That’s it! You are good to go.

How Do I Install The Trial Edition?

If you’ve received a trial license, you will also receive a link to download a recent version of the package. You will not be able to install or upgrade the licensed edition through regular means. Chocolatey may add the licensed source, but your license will not be recognized on the server.

  1. Install a recent version of Chocolatey (0.10.8+) — (due to a tight integration, may need a newer version than what is listed here).
  2. You received a license file in email. That email also contains links to download licensed nupkgs. If you received the license file from another party but not the email, please ask them to forward it over to you as you will need it.
  3. Obtain the and download the licensed nupkgs from the locations noted in the trial license email to a local folder. Note this location, you will need it later.
  4. Open PowerShell.exe as an administrative shell. You can type Windows Key + X + A (Windows 8+ — when that comes up if it is cmd.exe, simply type to get into it).
  5. In PowerShell, run — this creates the license directory. Alternatively, you can put the license in your user profile directory, e.g. , however we only recommend you do this for Professional licenses as for other licensing you may need it to be recognized by multiple users.
  6. Now place that license file in that license folder. You can do this manually, or you can adapt this PowerShell command — . (See image below)
  7. Verify the license file is set properly. In PowerShell, run If that returns something, it means you are good to go. If not, something is misspelled or misplaced somewhere.
  8. Run this command: (or you can use instead of ). Note: Source location is not , it is . You will see an error you can safely ignore.
  9. Run this command: . You should not see any error message logged anymore (like you saw in the previous run asking you to install the licensed extension). If you do see an error message still, you may need to revisit these steps and determine what might have been missed or mistyped.
  10. That’s it! You are good to go.

Notes on the Trial Version

Very little functionality if any is held back. With the movement forward on things like Central Management and GUI branding, those are now available with a trial as well.

Рейтинг автора
5
Материал подготовил
Максим Иванов
Наш эксперт
Написано статей
129
Ссылка на основную публикацию
Похожие публикации