feat(docs): How-to guides about UP4W agent startup #944
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using Intune Remediations sysadmins can monitor the value of the desired key and reduce the likelyhood of the inherent race condition of installing the MSIX and setting the registry value causing silent issues. Eventually Intune would pick up the non-compliant state and fix it up.
More descriptive, making more sense when read in the registry.
Including - Remediations: most often uncountable, in this case it is a countable word. - Center: mispelled in en_GB, but the portal name is en_US (Intune Admin Center)
and cross reference the other guide.
edibotopic
requested changes
Oct 18, 2024
There was a problem hiding this comment.
Thanks for doing this @CarlosNihelton -- this is very useful information!
I have included several suggestions, mainly focused on wording and clarity.
Two broader, non-blocking points I would like us to think about (in subsequent discussions and PRs):
- Explanatory content: there is quite a bit of explanatory content. While this is good material, I think it might be better placed in a dedicated explanation article in the docs (something focused on remote management). This would ensure that the how-to guides flow and mainly contain the information necessary for someone to complete the tasks involved. In addition, this would help prevent some duplication across the two guides.
- Separation of guides: I think the guides might need a cleaner separation in their titles. When thinking about that in the future, we should also think whether they would be better combined.
Instead of 'end user'.
... Enforcing with Intune & Registry guide.
... Guide on starting the agent with Intune.
For better searchability. Now a heading for the action of applying the scripts is needed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As agreed in WS037, I'm bringing two pieces of documentation about how system administrators can have UP4W background agent start without explicit end user interaction.
One guide relies on being able to start the agent via CLI (reason why this PR is based on #941 ) by deploying an one-shot PowerShell script via Intune to be executed with the current user's credentials.
The other guide relies on the registry, but leverages Intune Remediations to make that approach more reliable, by having that tool automatically checking and fixing non-compliant state, thus multi-shot (should end users disable the startup task, Intune would eventually find it and fix it).
This PR completes UDENG-4623 and closes #912 .