* fixed issue with h1s from hotlinked note-articles rendering as duplicate h1s
* testing path is correct
* find & replace old path > new path
attempting to fix issue with note-articles not being in seperate /includes dir
* fixed link on note page
* Adding a sentence to dynamic lock
* Add titleSuffix for mdop
* Add titleSuffix for smb
* Add titleSuffix for surface-hub
* Add titleSuffix for Edge
* Add titleSufix for client-management
* Correct metadata attribute
* Add titleSuffix for application-management
* Add titleSuffix for surface
* Add titleSuffix for hub
* pencil edit
line 27
* Add titleSuffix for deployment
* pencil edit
line 27
* pencil edit
line 27
* pencil edit
line 27
* Add titleSuffix for internet-explorer
* Add titleSuffix for privacy
Also added one tab spacing for lines 43-47 for beautification
* Add titleSuffix for whats-new
* Add titleSuffix for security
* Add titleSuffix for configuration
* CAT Auto Pulish for Windows Release Messages - CAT_AutoPublish_20191210080851 (#1678)
https://docs.microsoft.com/en-us/intune/fundamentals/whats-new#week-of-july-15-2019
Windows Autopilot reset removes the device's primary user
When Autopilot reset is used on a device, the device's primary user will be removed. The next user who signs in after the reset will be set as the primary user. This feature will be rolled out to all customers over the next few days.
From testing, this seems to be the tech flow behavior regarding software deployment - additionally, the behavior we've seen is that the green screen appears once enrollment is done, not once everything is applied - this means the screen can go green but the reseal button won't appear until configuration and install is complete.
Without ESP, the device enrolls, the screen goes green, the reseal button appears, but launching a command prompt and exploring the disk validates software didn't install. With ESP, the screen goes green within the same period, but there's a 20 minute delay after that before the reseal button appears - in this scenario, at reseal, the software is installed as expected.
Mostly just trying to get this behavior documented if it's correct, but if it's incorrect, some clarification on the software install behavior during tech flow would be good, because the expectation that software will install during the technician flow seems to not be consistent and this is the only reason I could find from the documentation that explains the behavior we're seeing.
Description:
As suggested in issue ticket #5603
(USMT XML Ref typo - File.txt => file].txt),
the example filename should contain the aforementioned bracket
that this section is all about, as well as preferably use the same case
(lowercase) as the directly following XML code.
Thanks to ChadMcCaffery for reporting this typo.
Changes proposed:
- add the missing example bracket character
- convert the filename "File" to lowercase "file"
- add bold text for the filename to be more visible
issue ticket closure or reference:
Closes#5603
