# Windows Autopilot VPN provisioning

**URL:** <https://forum.pritunl.com/t/windows-autopilot-vpn-provisioning/3097>\
**Category:** Pritunl VPN\
**Created:** [March 3, 2025, 9:58pm UTC](https://forum.pritunl.com/t/windows-autopilot-vpn-provisioning/3097 "2025-03-03T21:58:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![abdullah](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/a/aeb1de/32.png) [@abdullah](https://forum.pritunl.com/u/abdullah)\
**Post date:** [March 3, 2025, 9:58pm UTC](https://forum.pritunl.com/t/windows-autopilot-vpn-provisioning/3097/1 "2025-03-03T21:58:40Z")

</div>

Is anyone using Pritunl in an environment with Windows Autopilot and if so how are you provisioing the VPN profile?

I need this because we have a hybrid domain join environment so the endpoint needs to communicate with on premise AD for things like group policy.

Thanks

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [March 4, 2025, 3:26pm UTC](https://forum.pritunl.com/t/windows-autopilot-vpn-provisioning/3097/2 "2025-03-04T15:26:34Z")

</div>

This will be much easier in the next release when [**WinGet installer**](https://github.com/pritunl/pritunl-client-electron/tree/master/winget) is completed. There was an issue with the current installer that was killing all processes named Pritunl.exe to close the GUI client before installing. A fix has been implemented for this but won’t be available until the next release. This won’t cause issues when running the installer normally. But when it is run in [**silent mode**](https://docs.pritunl.com/docs/silent-automated-install) it will fork the installer and return an error on the original process. This will cause any automation software to believe the install fail. The `Pritunl.exe` installer should be renamed to avoid this issue.