Summit Discussion: Updating "end user" help

The question arose “How do I get around the Local Admin requirement for Update-Help?”

My first thought is to have someone that has admin rights (desktop support???) push the files saved from Save-Help to the target computers.

Anytime you have an action the has system wide impact - admin is a requirement.

Take the user out of this use case. Unless the user, uses PoSH daily or as a core job, this is not really a thing.

Yet, if you just want to make sure all systems have the most recent help updates. Set a scheduled job that runs a admin or system to execute update-help -force on a weekly bases, or push a small update-help script that is executed on startup as a background job or use GPO the below to get the idea.

About Group Policy Settings SHORT DESCRIPTION

Describes the Group Policy settings for Windows PowerShell

LONG DESCRIPTION

Windows PowerShell includes Group Policy settings to help you define consistent option values for servers in an enterprise environment.
SHORT DESCRIPTION

Group policy settings in the User Configuration path take precedence over Group Policy settings in the Computer Configuration path.

The policies are as follows:
• Turn on Script Execution: Sets the Windows PowerShell execution policy.
• Turn on Module Logging: Sets the LogPipelineExecutionDetails property of modules.
• Set the default source path for Update-Help: Sets the source for UpdatableHelp to a directory, not the Internet.

https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.core/about/about_group_policy_settings?view=powershell-6