Files
Open-Shell-Menu/Localization/English/PolicyDefinitions.rtf
Xenhat f4dd56155b Rebrand to Open-Shell (#36) (#58)
* Rebrand to Open-Shell

* Slight installer branding improvement
2018-08-05 15:22:10 -04:00

53 lines
3.2 KiB
Plaintext
Raw Blame History

This file contains invisible Unicode characters
This file contains invisible Unicode characters that are indistinguishable to humans but may be processed differently by a computer. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
{\rtf1\ansi\ansicpg1252\deff0\nouicompat\deflang1033\deflangfe1033{\fonttbl{\f0\froman\fprq2\fcharset0 Cambria;}{\f1\fswiss\fprq2\fcharset0 Calibri;}}
{\colortbl ;\red52\green52\blue52;\red45\green162\blue191;\red0\green0\blue255;}
{\stylesheet{ Normal;}{\s1 heading 1;}{\s2 heading 2;}}
{\*\generator Riched20 10.0.17134}{\*\mmathPr\mnaryLim0\mdispDef1\mwrapIndent1440 }\viewkind4\uc1
\pard\brdrb\brdrs\brdrw20\brsp80 \widctlpar\sa300\cf1\expndtw5\kerning28\f0\fs52\lang9 Open-Shell policy definitions\par
\pard\widctlpar\cf0\expndtw0\kerning0\f1\fs22\par
The provided ADMX files can be used by administrators to adjust the settings for multiple users.\par
\par
\pard\keep\keepn\widctlpar\s2\sb200\sl276\slmult1\cf2\b\f0\fs26 Installation\par
\pard\widctlpar\cf0\b0\f1\fs22\par
Copy the contents of the \b PolicyDefinitions\b0 folder (including the \b en-US\b0 sub-folder) to \b C:\\Windows\\PolicyDefinitions\b0 .\par
\par
After that you will be able to use the \b gpedit.msc\b0 tool edit the settings. They will show up under \b Administrative Templates -> Open-Shell\b0 .\par
\par
To edit a setting, change the policy from \b Not Configured\b0 to \b Enabled\b0 . Setting a policy to \b Disabled\b0 is not supported and has no effect.\par
\par
\pard\keep\keepn\widctlpar\s2\sb200\sl276\slmult1\cf2\b\f0\fs26 State\lang1033\par
\pard\widctlpar\cf0\b0\f1\fs22\lang9\par
Each setting has 2 components \endash state and value. The state can be:\par
\b\par
Locked to this value:\b0 The value you enter will be used for the setting. Users will not be able to change the setting using the Settings dialog.\par
\par
\b Locked to default:\b0 The setting will be locked to the default value determined by the software. The default value depends on the current OS version and configuration, current style, etc. The value you enter for the policy will be ignored.\par
\par
\b Unlocked:\b0 The value you enter will be used to replace the default value of the setting. The users will be able to override the setting from the Settings dialog.\par
\par
\pard\keep\keepn\widctlpar\s2\sb200\sl276\slmult1\cf2\b\f0\fs26 Precedence\par
\pard\widctlpar\cf0\b0\f1\fs22\par
There are 4 places where Open-Shell looks for settings. In order of precedence they are:\par
\b HKLM\\Software\\Policies\\OpenShell\b0 \endash this is where the Computer Configuration policies are stored\par
\b HKLM\\Software\\OpenShell\b0 \endash this is where you can manually store settings for all users\par
\b HKCU\\Software\\Policies\\OpenShell\b0 \endash this is where the User Configuration policies are stored\par
\b HKCU\\Software\\OpenShell\b0 \endash this is where the Settings dialog stores the per-user setting\par
\par
If a setting is locked in any of the first 3 locations, it will be grayed out in the Settings dialog and users can\rquote t change it.\par
\par
\par
\pard\keep\keepn\widctlpar\s2\sb200\sl276\slmult1\cf2\b\f0\fs26 Localization\par
\pard\widctlpar\cf0\b0\f1\fs22\par
You can download translations for the group policy settings. Look for the file \b PolicyDefinitions.zip\b0\par
here: {{\field{\*\fldinst{HYPERLINK http://www.classicshell.net/translations/ }}{\fldrslt{http://www.classicshell.net/translations/\ul0\cf0}}}}\f1\fs22\par
}