You can set registry values to influence the behaviour of Powershell on the computer, or you can use Group Policy to influence the behaviour of Powershell on all the computers to which the GPO applies.
If the GPO setting is ‘Not configured’ then your setting applied via the registry will take effect, but if the GPO value is set, it will override the local registry value.
You cannot set registry values on one client that will be reflected in Group Policy.
We are trying to set the policy in local group policy. and we are trying in the server that there GPO are not configured.
Whether it is Local Group Policy or AD Group Policy, there are tools provided for this, and directly hacking the registry is not going to set group policy (and the settings in group policy will keep re-applying).
You can set up a template for local group policy then distribute and apply this using Bigfix. There examples of this in the forum, or you can research how to do it and formulate your commands. Then, if required, there will be someone here who can help you convert it into a fixlet.
Leave BigFix out of it to start with. It’s much easier to first figure out how to solve your problem, and then use BigFix to mass-deploy your solution. Get a working, command-line script that works on one machine first.
You’ll likely need LGPO, the Local Group Policy management tool, described and available for download at https://www.microsoft.com/en-us/download/details.aspx?id=55319
Apply the settings in Local Group Policy on one machine, verify it does what you want, then use LGPO to export the policy to text. Determine which pieces of the policy affect what you’re trying to do, then save that portion of the text export. Clear your local group policy, verify that removes the behavior you’re testing, then reapply the policy using LGPO and your text export to verify you have the correct settings to manage what you’re trying to configure.
When you have correct piece of your local policy completed, you can use BigFix to deploy your configuration using LGPO based on the examples at https://bigfix.me/fixlet/details/24619
Thank You So much Jason and Trevor. Now I am able to change the policy.