> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/2pxe-server/4.0/planning/permissions.md). # Permissions {% hint style="danger" %} **Configuration Manager compatibility** The Configuration Manager permissions and SQL access instructions on this page relate to an integration that is not currently supported by 2PXE Server 4.0. They are retained for reference only. {% endhint %} ## Configuration Manager Permissions ### Distribution Point Package Share IIS Permissions See [DP Package Share IIS Permissions](/2pxe-server/4.0/troubleshooting/dp-package-share-iis-permissions.md) for an IIS permission issue that can result in access denied errors when a client attempts to download a boot image. ### **Allowing Access to the Configuration Manager SQL Database** 2PXE uses SQL as the fastest way to retrieve boot actions for a system. Add the service account (by default, the computer account of the Distribution Point) to the *ConfigMgr\_DViewAccess* local group on the Configuration Manager Site Server. Members of this group have the access required to use distributed views against the Configuration Manager database. The account only requires read rights and can be further locked down if necessary. {% hint style="info" %} Note: Make sure the 2PXE server can reach the Configuration Manager database server by ensuring the necessary firewall ports are open. This is typically port 1433; however, it is configurable as described in the Microsoft Configuration Manager documentation. {% endhint %} {% embed url="" %} ## Security without Configuration Manager If you are not using Configuration Manager, the only security-related requirement is to ensure that the boot URL returned from the PowerShell command is accessible with anonymous security or by using an ACL and the iPXE Network Access Account. --- # 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://documentation.2pintsoftware.com/2pxe-server/4.0/planning/permissions.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.