Autopilot
Best Practices for using Pckgr applications with Autopilot
Last updated
Best Practices for using Pckgr applications with Autopilot
Last updated
When using applications deployed from Pckgr in Autopilot, there are a few factors to consider as Pckgr applications rely on Winget for the application to install correctly.
SYSTEM Vs User Applications
If you are going to be using the Enrollment Status Page to block applications, we highly recommend only adding applications that install with the SYSTEM account. You can check this by going to the application in Intune and checking the install behavior.
Most applications in the Pckgr are installed using the SYSTEM account or there is a SYSTEM alternative package like Zoom (Machine Install).
You can add an Enrollment Status Page to your application deployments to automatically keep it up to date. Read more about this on the Deployment Settings page.
Winget Pre-Install during Autopilot
The Winget Pre-Install step is crucial in the Autopilot process. It first verifies whether a compatible version of Winget is installed under the SYSTEM account. This check is essential because, although modern OS versions include Winget, older versions might not connect to the Content Delivery Network (CDN), leading to application installation failures. If the Pre-Install routine identifies a current version of Winget, it skips the installation stage and proceeds directly to the application installation phase. This ensures a smooth and efficient setup process.
What about User Install behavior?
During the Autopilot process, we can install the machine-wide (or system-wide) version of Winget. However, replicating this process for the AppData version of Winget, which facilitates 'User' install behavior, has proven challenging. To mitigate the risk of installation failures due to the absence of the AppData Winget, we have implemented a prerequisite script. This script checks for the presence of the Winget application in the AppData directory. If the script finds that Winget is missing, the application in question will be marked as 'Not applicable', and its installation will be skipped. This allows the device to attempt the installation again during its next check-in with Intune, ensuring a more reliable and efficient installation process.
Troubleshooting Tips
If you experience failures during the application installation phase of the Autopilot process, we suggest two primary troubleshooting methods. Firstly, conduct targeted tests to identify the specific application causing the build to fail. Alternatively, review the 'Managed Apps' section for the affected device in Intune, as it may already have a report on the failure. Don't forget to check under 'Device without user' in the 'Managed Apps' area, accessible via the dropdown menu.
If you discover an application that fails during Autopilot, please inform us at support@intunepckgr.com for further support.
As another solution, consider running the Autopilot process without restricting any applications. This method allows for real-time monitoring of the installation phase, helping to identify any failing applications.
Lastly, we advise including only essential applications in the Autopilot process. This strategy reduces the potential for errors and contributes to a faster, more efficient build time.
