> For the complete documentation index, see [llms.txt](https://docs.intunemacadmins.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.intunemacadmins.com/deploy-files-on-a-mac/insights.md).

# Insights

Insights on how to deploy files on macOS devices using Intune.

## Security

* **PKG vs. Cloud Storage**: PKGs are more secure than public cloud storage. Example: Deploying font files via PKG instead of downloading from a public URL.
* **No Exposed Secrets**: PKGs eliminate the need for credentials in scripts. Example: Avoid scripts like `curl -u username:password https://example.com/file.zip`.

## Efficiency

* **Offline Deployment**: PKGs work without internet post-download. Example: Deploying large video files that work immediately after installation.
* **Version Control**: Use version numbers in PKG names. Example: `CompanyWallpapers_v1.2.pkg`

## User Experience

* **Silent Installation**: PKGs install without user interaction. Example: Deploying license files without interrupting user workflow.

## Troubleshooting

* **Logging**: Implement detailed logging in postinstall scripts. Example:

  ```bash
  echo "$(date): Copying files to /Library/Company/" >> /var/log/company_deployment.log
  ```

## Best Practices

* **Testing**: Always test in a controlled environment first. Example: Deploy to a test group of 5-10 devices before full rollout.
* **File Organization**: Structure content logically within the PKG. Example:

  ```
  Content/
  ├── Fonts/
  ├── Wallpapers/
  └── Documents/
  ```
* **Incremental Updates**: Design PKGs to support incremental updates. Example: Update only changed files instead of re-deploying the entire package.


---

# 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.intunemacadmins.com/deploy-files-on-a-mac/insights.md?ask=<question>&goal=<user_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.