> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/setup-and-licensing/it-administration/automating-activation-processe-3.md). # Automating the Process of Updating the PCC on Multiple Installations How to automate PCC updates across multiple SEL installations using the registry batch updater. ### How can we automate the process of updating the PCC in multiple SEL installations when the PCC is stored in the Windows Registry? Under normal conditions where our applications can contact our activation (license management) server, the applications will detect when a renewal has occurred and will automatically keep the PCC up to date. As such, there is typically no need to manually update the PCC after a renewal. If you’re using manual activation or our applications are unable to contact our activation server (including “air-gapped” networks), then it is best to update the PCC via automation. **Where the PCC is stored** Both methods below write the same registry string value, named PCC, at: `HKCU\Software\Enercalc\V20\ECLIC\` When run via SCCM, MECM, Intune, or similar unattended / automated systems management tools, the PCC update expects to be run under the user's Windows profile, as it updates values in HKCU. **Option 1 — ENERCALC's batch PCC updater** Download our PCC batch installer/updater from: The file `UpdateEnercalcPCCinRegistry.exe` is signed. The batch PCC updater can be run two different ways: `.\UpdateEnercalcPCCinRegistry.exe PCC="NewPCC"` or `.\UpdateEnercalcPCCinRegistry.exe PCCFILE="TextFileContainingTheNewPCC"` The PCCFILE= file spec can be any valid file spec, IE: `C:\somefolder\mypccfile.txt` or `\\myserver\myshareddrive\ThisIsMyPCCFile.txt` etc. If spaces are in the file name, the file name must be surrounded with double quotes as in the example above. Ensure the PCC text file contains only your PCC, with no additional text. Also, make sure any line breaks are removed from the text string. ![](https://1076748670-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtBL2fEQRwrlKSM2irFL0%2Fuploads%2Fgit-blob-32ae4877e593973b15b4132b8313d45f4dfc23d5%2FPCC%20text%20file.png?alt=media) **Option 2 — Any bulk registry update tool** Alternatively, ANY bulk registry update tool can be used to populate the PCC at the `HKCU\Software\Enercalc\V20\ECLIC\` key described above. The value to store the PCC text string in should be named `PCC` (it's a string value). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://enercalc.com/docs/sel-faq/setup-and-licensing/it-administration/automating-activation-processe-3.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.