Explain how MSIX deployment works (staging and registration)#490
Explain how MSIX deployment works (staging and registration)#490RDMacLachlan wants to merge 6 commits into
Conversation
Add a "How MSIX deployment works: staging and registration" concept section to the Manage your MSIX deployment overview. It describes the platform model requested in this bug: staging (once per machine), registration (once per user at sign-in), provisioning (stage + all-user registration flag + event), and how an update applied for one user propagates to every other user of the machine. Cross-links to Preinstalling packaged apps and App package updates. Resolves AB#36938354 Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
|
Learn Build status updates of commit 76e1ce2: ✅ Validation status: passed
For more details, please refer to the build report. |
| ## How MSIX deployment works: staging and registration | ||
|
|
||
|
|
||
| To plan deployments—especially on multi-user machines—it helps to understand what Windows does under the covers when a package is installed. Installing an MSIX package is really two distinct operations: **staging** and **registration**. |
There was a problem hiding this comment.
Installing an MSIX package is really two distinct operations: staging and registration
The following subsections are Staging, Registration, Provisioning, and How updates reach other users. Why does the first paragraph say there are only two distinct operations, though four are documented? Are there actually four distinct operations? If not, how are the extra two not distinct from the others?
There was a problem hiding this comment.
I believe I've updated the doc change to prevent confusion when reading. Let me know your thoughts :-).
There was a problem hiding this comment.
Looks good to me! It's much clearer now. I also appreciate the detail about Windows 10 2004, that's very helpful when trying to debug deployments.
- Reword intro so "two distinct operations" is consistent with the four subsections (provisioning and updates build on staging + registration). - Scope re-provisioning reinstall to Windows 10, version 2004+ / force provisioning. - Scope update propagation to users who have the app registered. - Bump ms.date. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 18e32334-aec6-40fd-a4f8-0631ef4d5840
|
Learn Build status updates of commit 3801087: ✅ Validation status: passed
For more details, please refer to the build report. |
Align with documentation style (no emdashes / AI-style formatting characters); use commas matching the surrounding content. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 18e32334-aec6-40fd-a4f8-0631ef4d5840
|
Learn Build status updates of commit 2084fc1: ✅ Validation status: passed
For more details, please refer to the build report. |
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 18e32334-aec6-40fd-a4f8-0631ef4d5840
|
Learn Build status updates of commit e18ffa2: ✅ Validation status: passed
For more details, please refer to the build report. |
|
Learn Build status updates of commit 30552d7: ✅ Validation status: passed
For more details, please refer to the build report. |
- Use sentence case for the 'MSIX install operations' heading. - Lowercase 'staging and registration' in the section intro for consistency. - Rename the second H2 to 'Provisioning and updates across users' for clarity. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> Copilot-Session: 18e32334-aec6-40fd-a4f8-0631ef4d5840
|
Learn Build status updates of commit 4a2a921: ✅ Validation status: passed
For more details, please refer to the build report. |
2 participants
Summary
Adds a How MSIX deployment works: staging and registration concept section to
msix-src/desktop/managing-your-msix-deployment-overview.md, providing the more advanced deployment explanation requested in this bug.The new section covers the platform model described by the MSIX team in the work item:
%ProgramFiles%\WindowsApps, done once per machine and without a signed-in user.Cross-links to Preinstalling packaged apps (provisioning tools) and App package updates (differential download). Placed at the end of the file to avoid overlapping with the still-open PR #484, which edits the intro of the same document.
Resolves AB#36938354