Skip to content

Commit

Permalink
Merge pull request #16609 from MicrosoftDocs/main
Browse files Browse the repository at this point in the history
Publish main to live, Tuesday 6:30PM PST, 11/12
  • Loading branch information
Stacyrch140 authored Nov 12, 2024
2 parents e903575 + e8a8cdc commit cfa90e6
Show file tree
Hide file tree
Showing 2 changed files with 2 additions and 2 deletions.
2 changes: 1 addition & 1 deletion memdocs/intune/enrollment/device-staging-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ In the second stage, an Intune admin or third-party vendor completes the followi

1. With the device, scan the staging token's QR code or enter the token string.

1. Complete the enrollment steps and setup wizard. When you get to the sign-in screen, stop. Don't sign in.
1. Complete the enrollment steps and setup wizard. At the end of setup, you are on the device's home screen.

1. Turn off the device and distribute it to the end user.

Expand Down
2 changes: 1 addition & 1 deletion windows-365/enterprise/troubleshoot-windows-365-boot.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ Get-AppxPackage –AllUsers -name *MicrosoftCorporationII*

This command shows all the Microsoft-maintained apps (like QuickAssist, Microsoft Family, and so on) on the physical device. In order for Windows 365 Boot to work correctly, confirm the following versions:

- Windows App version 1.1.162.0 or later.
- Windows App version 2.0.285 or later.
- Azure Virtual Desktop (HostApp) app version 1.2.4159. or later.

Windows 365 Boot also requires the latest version of Windows 11.
Expand Down

0 comments on commit cfa90e6

Please sign in to comment.