> For the complete documentation index, see [llms.txt](https://docs.foundryosd.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foundryosd.com/foundry-osd/network.md). # Network Configure network settings that Foundry Connect can use in Windows PE. ## Choose a connection type * Use [Wi-Fi](/foundry-osd/network/wifi.md) when target devices must connect wirelessly. * Use [Ethernet 802.1X](/foundry-osd/network/ethernet-802.1x.md) when wired access requires enterprise authentication. * Skip network provisioning when target devices use an unrestricted wired connection with DHCP. Only include profiles and certificates required for deployment. [Password protection](/foundry-osd/general.md#password-protection) does not protect embedded network credentials: anyone who can read the ISO or USB can recover them. Restrict media access and use dedicated network credentials that can be revoked. Foundry Connect uses these credentials before the technician enters the deployment password, so automatic network setup remains available. Use [deployment profiles](/foundry-osd/deployment-profiles.md) to retain network settings and explicitly selected passwords or files, or to transfer them in an encrypted package. Review missing credentials and local certificate paths after activating or importing a profile. ## Windows profile roaming Foundry can import selected Wi-Fi and wired 802.1X profiles into the installed Windows system before OOBE. Configure roaming separately for each connection type. When certificate authentication is configured, **Include private-key certificate material** also copies the corresponding PFX client certificate into the Windows local-computer personal certificate store. Enable this only when Windows must continue using that certificate after deployment, and apply the organization’s rotation and revocation policy. Profile roaming can also preserve a Wi-Fi profile created from a passphrase entered by the technician in Foundry Connect. Treat the resulting Windows network profile as sensitive because it contains the information required to reconnect. ## Before creating media Confirm that: * Required Windows PE network drivers are available. * The deployment network can reach Windows, driver, and required Microsoft service endpoints. * Certificates are valid for the deployment period. * Test credentials and production credentials are not mixed. * Profile and private-key roaming choices match the post-deployment connectivity requirement. --- # 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://docs.foundryosd.com/foundry-osd/network.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.