diff --git a/policy_templates/PolicyDefinitions/AVSValidationGP.admx b/policy_templates/PolicyDefinitions/AVSValidationGP.admx
deleted file mode 100644
index 3956f4e..0000000
--- a/policy_templates/PolicyDefinitions/AVSValidationGP.admx
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AccountNotifications.admx b/policy_templates/PolicyDefinitions/AccountNotifications.admx
deleted file mode 100644
index 223015e..0000000
--- a/policy_templates/PolicyDefinitions/AccountNotifications.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ActiveXInstallService.admx b/policy_templates/PolicyDefinitions/ActiveXInstallService.admx
deleted file mode 100644
index ba0e6f9..0000000
--- a/policy_templates/PolicyDefinitions/ActiveXInstallService.admx
+++ /dev/null
@@ -1,113 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AddRemovePrograms.admx b/policy_templates/PolicyDefinitions/AddRemovePrograms.admx
deleted file mode 100644
index d1b76d1..0000000
--- a/policy_templates/PolicyDefinitions/AddRemovePrograms.admx
+++ /dev/null
@@ -1,63 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AllowBuildPreview.admx b/policy_templates/PolicyDefinitions/AllowBuildPreview.admx
deleted file mode 100644
index 3ec637b..0000000
--- a/policy_templates/PolicyDefinitions/AllowBuildPreview.admx
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AppCompat.admx b/policy_templates/PolicyDefinitions/AppCompat.admx
deleted file mode 100644
index 5e6bc1b..0000000
--- a/policy_templates/PolicyDefinitions/AppCompat.admx
+++ /dev/null
@@ -1,88 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AppHVSI.admx b/policy_templates/PolicyDefinitions/AppHVSI.admx
deleted file mode 100644
index 2f0dbee..0000000
--- a/policy_templates/PolicyDefinitions/AppHVSI.admx
+++ /dev/null
@@ -1,203 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AppPrivacy.admx b/policy_templates/PolicyDefinitions/AppPrivacy.admx
deleted file mode 100644
index ec51933..0000000
--- a/policy_templates/PolicyDefinitions/AppPrivacy.admx
+++ /dev/null
@@ -1,784 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AppXRuntime.admx b/policy_templates/PolicyDefinitions/AppXRuntime.admx
deleted file mode 100644
index d95a1c4..0000000
--- a/policy_templates/PolicyDefinitions/AppXRuntime.admx
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AppxPackageManager.admx b/policy_templates/PolicyDefinitions/AppxPackageManager.admx
deleted file mode 100644
index f392097..0000000
--- a/policy_templates/PolicyDefinitions/AppxPackageManager.admx
+++ /dev/null
@@ -1,116 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AttachmentManager.admx b/policy_templates/PolicyDefinitions/AttachmentManager.admx
deleted file mode 100644
index 0fe5cac..0000000
--- a/policy_templates/PolicyDefinitions/AttachmentManager.admx
+++ /dev/null
@@ -1,113 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AuditSettings.admx b/policy_templates/PolicyDefinitions/AuditSettings.admx
deleted file mode 100644
index 278fe76..0000000
--- a/policy_templates/PolicyDefinitions/AuditSettings.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/AutoPlay.admx b/policy_templates/PolicyDefinitions/AutoPlay.admx
deleted file mode 100644
index ad7ff54..0000000
--- a/policy_templates/PolicyDefinitions/AutoPlay.admx
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Biometrics.admx b/policy_templates/PolicyDefinitions/Biometrics.admx
deleted file mode 100644
index 24642d0..0000000
--- a/policy_templates/PolicyDefinitions/Biometrics.admx
+++ /dev/null
@@ -1,66 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Bits.admx b/policy_templates/PolicyDefinitions/Bits.admx
deleted file mode 100644
index cfba717..0000000
--- a/policy_templates/PolicyDefinitions/Bits.admx
+++ /dev/null
@@ -1,1423 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/CEIPEnable.admx b/policy_templates/PolicyDefinitions/CEIPEnable.admx
deleted file mode 100644
index 746ca2e..0000000
--- a/policy_templates/PolicyDefinitions/CEIPEnable.admx
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/COM.admx b/policy_templates/PolicyDefinitions/COM.admx
deleted file mode 100644
index 0e1c083..0000000
--- a/policy_templates/PolicyDefinitions/COM.admx
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Camera.admx b/policy_templates/PolicyDefinitions/Camera.admx
deleted file mode 100644
index 9752441..0000000
Binary files a/policy_templates/PolicyDefinitions/Camera.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/CipherSuiteOrder.admx b/policy_templates/PolicyDefinitions/CipherSuiteOrder.admx
deleted file mode 100644
index 36fb856..0000000
--- a/policy_templates/PolicyDefinitions/CipherSuiteOrder.admx
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/CloudContent.admx b/policy_templates/PolicyDefinitions/CloudContent.admx
deleted file mode 100644
index 2be5474..0000000
--- a/policy_templates/PolicyDefinitions/CloudContent.admx
+++ /dev/null
@@ -1,156 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Conf.admx b/policy_templates/PolicyDefinitions/Conf.admx
deleted file mode 100644
index 69dd379..0000000
--- a/policy_templates/PolicyDefinitions/Conf.admx
+++ /dev/null
@@ -1,203 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ControlPanel.admx b/policy_templates/PolicyDefinitions/ControlPanel.admx
deleted file mode 100644
index 5fe7095..0000000
--- a/policy_templates/PolicyDefinitions/ControlPanel.admx
+++ /dev/null
@@ -1,68 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ControlPanelDisplay.admx b/policy_templates/PolicyDefinitions/ControlPanelDisplay.admx
deleted file mode 100644
index abb53d8..0000000
--- a/policy_templates/PolicyDefinitions/ControlPanelDisplay.admx
+++ /dev/null
@@ -1,274 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Cpls.admx b/policy_templates/PolicyDefinitions/Cpls.admx
deleted file mode 100644
index b9fc894..0000000
--- a/policy_templates/PolicyDefinitions/Cpls.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/CredSsp.admx b/policy_templates/PolicyDefinitions/CredSsp.admx
deleted file mode 100644
index b49824e..0000000
--- a/policy_templates/PolicyDefinitions/CredSsp.admx
+++ /dev/null
@@ -1,277 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/CredUI.admx b/policy_templates/PolicyDefinitions/CredUI.admx
deleted file mode 100644
index e36be7a..0000000
--- a/policy_templates/PolicyDefinitions/CredUI.admx
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/CredentialProviders.admx b/policy_templates/PolicyDefinitions/CredentialProviders.admx
deleted file mode 100644
index be33e3d..0000000
--- a/policy_templates/PolicyDefinitions/CredentialProviders.admx
+++ /dev/null
@@ -1,78 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/CtrlAltDel.admx b/policy_templates/PolicyDefinitions/CtrlAltDel.admx
deleted file mode 100644
index d3a1d28..0000000
--- a/policy_templates/PolicyDefinitions/CtrlAltDel.admx
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DCOM.admx b/policy_templates/PolicyDefinitions/DCOM.admx
deleted file mode 100644
index e67ec99..0000000
--- a/policy_templates/PolicyDefinitions/DCOM.admx
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DFS.admx b/policy_templates/PolicyDefinitions/DFS.admx
deleted file mode 100644
index 80c600f..0000000
--- a/policy_templates/PolicyDefinitions/DFS.admx
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DWM.admx b/policy_templates/PolicyDefinitions/DWM.admx
deleted file mode 100644
index 77fba56..0000000
--- a/policy_templates/PolicyDefinitions/DWM.admx
+++ /dev/null
@@ -1,121 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DataCollection.admx b/policy_templates/PolicyDefinitions/DataCollection.admx
deleted file mode 100644
index 603455e..0000000
--- a/policy_templates/PolicyDefinitions/DataCollection.admx
+++ /dev/null
@@ -1,263 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/DeliveryOptimization.admx b/policy_templates/PolicyDefinitions/DeliveryOptimization.admx
deleted file mode 100644
index ae0e3b4..0000000
--- a/policy_templates/PolicyDefinitions/DeliveryOptimization.admx
+++ /dev/null
@@ -1,1140 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Desktop.admx b/policy_templates/PolicyDefinitions/Desktop.admx
deleted file mode 100644
index 347cf28..0000000
--- a/policy_templates/PolicyDefinitions/Desktop.admx
+++ /dev/null
@@ -1,193 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 0
-
-
-
-
- 1
-
-
-
-
- 2
-
-
-
-
- 3
-
-
-
-
- 4
-
-
-
-
- 5
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DesktopAppInstaller.admx b/policy_templates/PolicyDefinitions/DesktopAppInstaller.admx
deleted file mode 100644
index 44be8a5..0000000
--- a/policy_templates/PolicyDefinitions/DesktopAppInstaller.admx
+++ /dev/null
@@ -1,130 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/DeviceCompat.admx b/policy_templates/PolicyDefinitions/DeviceCompat.admx
deleted file mode 100644
index e7b01b9..0000000
--- a/policy_templates/PolicyDefinitions/DeviceCompat.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DeviceCredential.admx b/policy_templates/PolicyDefinitions/DeviceCredential.admx
deleted file mode 100644
index dfd33ef..0000000
--- a/policy_templates/PolicyDefinitions/DeviceCredential.admx
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DeviceGuard.admx b/policy_templates/PolicyDefinitions/DeviceGuard.admx
deleted file mode 100644
index 6e0643d..0000000
--- a/policy_templates/PolicyDefinitions/DeviceGuard.admx
+++ /dev/null
@@ -1,171 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DeviceInstallation.admx b/policy_templates/PolicyDefinitions/DeviceInstallation.admx
deleted file mode 100644
index bd7e385..0000000
--- a/policy_templates/PolicyDefinitions/DeviceInstallation.admx
+++ /dev/null
@@ -1,264 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DeviceSetup.admx b/policy_templates/PolicyDefinitions/DeviceSetup.admx
deleted file mode 100644
index 2074f13..0000000
--- a/policy_templates/PolicyDefinitions/DeviceSetup.admx
+++ /dev/null
@@ -1,127 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DigitalLocker.admx b/policy_templates/PolicyDefinitions/DigitalLocker.admx
deleted file mode 100644
index 005f40d..0000000
--- a/policy_templates/PolicyDefinitions/DigitalLocker.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DiskDiagnostic.admx b/policy_templates/PolicyDefinitions/DiskDiagnostic.admx
deleted file mode 100644
index d6cad74..0000000
--- a/policy_templates/PolicyDefinitions/DiskDiagnostic.admx
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DiskNVCache.admx b/policy_templates/PolicyDefinitions/DiskNVCache.admx
deleted file mode 100644
index e7b68cc..0000000
--- a/policy_templates/PolicyDefinitions/DiskNVCache.admx
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DiskQuota.admx b/policy_templates/PolicyDefinitions/DiskQuota.admx
deleted file mode 100644
index 5b1db70..0000000
--- a/policy_templates/PolicyDefinitions/DiskQuota.admx
+++ /dev/null
@@ -1,132 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Display.admx b/policy_templates/PolicyDefinitions/Display.admx
deleted file mode 100644
index 48564be..0000000
--- a/policy_templates/PolicyDefinitions/Display.admx
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DistributedLinkTracking.admx b/policy_templates/PolicyDefinitions/DistributedLinkTracking.admx
deleted file mode 100644
index 14701f8..0000000
--- a/policy_templates/PolicyDefinitions/DistributedLinkTracking.admx
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/DmaGuard.admx b/policy_templates/PolicyDefinitions/DmaGuard.admx
deleted file mode 100644
index d9d01d7..0000000
--- a/policy_templates/PolicyDefinitions/DmaGuard.admx
+++ /dev/null
@@ -1,74 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/DnsClient.admx b/policy_templates/PolicyDefinitions/DnsClient.admx
deleted file mode 100644
index 2055295..0000000
--- a/policy_templates/PolicyDefinitions/DnsClient.admx
+++ /dev/null
@@ -1,302 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/EAIME.admx b/policy_templates/PolicyDefinitions/EAIME.admx
deleted file mode 100644
index 59e43eb..0000000
--- a/policy_templates/PolicyDefinitions/EAIME.admx
+++ /dev/null
@@ -1,153 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/EarlyLaunchAM.admx b/policy_templates/PolicyDefinitions/EarlyLaunchAM.admx
deleted file mode 100644
index caec7de..0000000
--- a/policy_templates/PolicyDefinitions/EarlyLaunchAM.admx
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/EdgeUI.admx b/policy_templates/PolicyDefinitions/EdgeUI.admx
deleted file mode 100644
index 95d9ecf..0000000
--- a/policy_templates/PolicyDefinitions/EdgeUI.admx
+++ /dev/null
@@ -1,86 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/EncryptFilesonMove.admx b/policy_templates/PolicyDefinitions/EncryptFilesonMove.admx
deleted file mode 100644
index 4e661e1..0000000
--- a/policy_templates/PolicyDefinitions/EncryptFilesonMove.admx
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/EnhancedStorage.admx b/policy_templates/PolicyDefinitions/EnhancedStorage.admx
deleted file mode 100644
index f1df3e7..0000000
--- a/policy_templates/PolicyDefinitions/EnhancedStorage.admx
+++ /dev/null
@@ -1,92 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ErrorReporting.admx b/policy_templates/PolicyDefinitions/ErrorReporting.admx
deleted file mode 100644
index 043317e..0000000
--- a/policy_templates/PolicyDefinitions/ErrorReporting.admx
+++ /dev/null
@@ -1,518 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/EventForwarding.admx b/policy_templates/PolicyDefinitions/EventForwarding.admx
deleted file mode 100644
index 1381a2a..0000000
--- a/policy_templates/PolicyDefinitions/EventForwarding.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/EventLog.admx b/policy_templates/PolicyDefinitions/EventLog.admx
deleted file mode 100644
index 62db8eb..0000000
--- a/policy_templates/PolicyDefinitions/EventLog.admx
+++ /dev/null
@@ -1,230 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/EventLogging.admx b/policy_templates/PolicyDefinitions/EventLogging.admx
deleted file mode 100644
index 726f789..0000000
--- a/policy_templates/PolicyDefinitions/EventLogging.admx
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/EventViewer.admx b/policy_templates/PolicyDefinitions/EventViewer.admx
deleted file mode 100644
index 3e78da3..0000000
--- a/policy_templates/PolicyDefinitions/EventViewer.admx
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ExploitGuard.admx b/policy_templates/PolicyDefinitions/ExploitGuard.admx
deleted file mode 100644
index 38e5400..0000000
--- a/policy_templates/PolicyDefinitions/ExploitGuard.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Explorer.admx b/policy_templates/PolicyDefinitions/Explorer.admx
deleted file mode 100644
index 05261a4..0000000
--- a/policy_templates/PolicyDefinitions/Explorer.admx
+++ /dev/null
@@ -1,88 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/ExternalBoot.admx b/policy_templates/PolicyDefinitions/ExternalBoot.admx
deleted file mode 100644
index 7b5fc3f..0000000
--- a/policy_templates/PolicyDefinitions/ExternalBoot.admx
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/FeedbackNotifications.admx b/policy_templates/PolicyDefinitions/FeedbackNotifications.admx
deleted file mode 100644
index f0caa7f..0000000
--- a/policy_templates/PolicyDefinitions/FeedbackNotifications.admx
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/FileHistory.admx b/policy_templates/PolicyDefinitions/FileHistory.admx
deleted file mode 100644
index 44f2fdf..0000000
--- a/policy_templates/PolicyDefinitions/FileHistory.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/FileRecovery.admx b/policy_templates/PolicyDefinitions/FileRecovery.admx
deleted file mode 100644
index a64988d..0000000
--- a/policy_templates/PolicyDefinitions/FileRecovery.admx
+++ /dev/null
@@ -1,45 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/FileRevocation.admx b/policy_templates/PolicyDefinitions/FileRevocation.admx
deleted file mode 100644
index d3dcb0f..0000000
--- a/policy_templates/PolicyDefinitions/FileRevocation.admx
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/FileServerVSSProvider.admx b/policy_templates/PolicyDefinitions/FileServerVSSProvider.admx
deleted file mode 100644
index 516df43..0000000
--- a/policy_templates/PolicyDefinitions/FileServerVSSProvider.admx
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/FileSys.admx b/policy_templates/PolicyDefinitions/FileSys.admx
deleted file mode 100644
index f0895e0..0000000
--- a/policy_templates/PolicyDefinitions/FileSys.admx
+++ /dev/null
@@ -1,256 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/FindMy.admx b/policy_templates/PolicyDefinitions/FindMy.admx
deleted file mode 100644
index 62f7e3f..0000000
--- a/policy_templates/PolicyDefinitions/FindMy.admx
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/FolderRedirection.admx b/policy_templates/PolicyDefinitions/FolderRedirection.admx
deleted file mode 100644
index 1397e21..0000000
--- a/policy_templates/PolicyDefinitions/FolderRedirection.admx
+++ /dev/null
@@ -1,95 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/FramePanes.admx b/policy_templates/PolicyDefinitions/FramePanes.admx
deleted file mode 100644
index c4f0913..0000000
--- a/policy_templates/PolicyDefinitions/FramePanes.admx
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/GameDVR.admx b/policy_templates/PolicyDefinitions/GameDVR.admx
deleted file mode 100644
index 59a192d..0000000
--- a/policy_templates/PolicyDefinitions/GameDVR.admx
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/Globalization.admx b/policy_templates/PolicyDefinitions/Globalization.admx
deleted file mode 100644
index 73861d5..0000000
--- a/policy_templates/PolicyDefinitions/Globalization.admx
+++ /dev/null
@@ -1,874 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- en-US
-
-
-
-
- ja-JP
-
-
-
-
- ko-KR
-
-
-
-
- de-DE
-
-
-
-
- zh-CN
-
-
-
-
- zh-TW
-
-
-
-
- fr-FR
-
-
-
-
- es-ES
-
-
-
-
- it-IT
-
-
-
-
- sv-SE
-
-
-
-
- nl-NL
-
-
-
-
- pt-BR
-
-
-
-
- fi-FI
-
-
-
-
- nb-NO
-
-
-
-
- da-DK
-
-
-
-
- hu-HU
-
-
-
-
- pl-PL
-
-
-
-
- ru-RU
-
-
-
-
- cs-CZ
-
-
-
-
- el-GR
-
-
-
-
- pt-PT
-
-
-
-
- tr-TR
-
-
-
-
- ar-SA
-
-
-
-
- he-IL
-
-
-
-
- sk-SK
-
-
-
-
- sl-SI
-
-
-
-
- ro-RO
-
-
-
-
- hr-HR
-
-
-
-
- bg-BG
-
-
-
-
- et-EE
-
-
-
-
- lt-LT
-
-
-
-
- lv-LV
-
-
-
-
- th-TH
-
-
-
-
- zh-HK
-
-
-
-
- sr-Latn-CS
-
-
-
-
- uk-UA
-
-
-
-
-
-
-
-
-
-
-
-
- en-US
-
-
-
-
- ja-JP
-
-
-
-
- ko-KR
-
-
-
-
- de-DE
-
-
-
-
- zh-CN
-
-
-
-
- zh-TW
-
-
-
-
- fr-FR
-
-
-
-
- es-ES
-
-
-
-
- it-IT
-
-
-
-
- sv-SE
-
-
-
-
- nl-NL
-
-
-
-
- pt-BR
-
-
-
-
- fi-FI
-
-
-
-
- nb-NO
-
-
-
-
- da-DK
-
-
-
-
- hu-HU
-
-
-
-
- pl-PL
-
-
-
-
- ru-RU
-
-
-
-
- cs-CZ
-
-
-
-
- el-GR
-
-
-
-
- pt-PT
-
-
-
-
- tr-TR
-
-
-
-
- ar-SA
-
-
-
-
- he-IL
-
-
-
-
- sk-SK
-
-
-
-
- sl-SI
-
-
-
-
- ro-RO
-
-
-
-
- hr-HR
-
-
-
-
- bg-BG
-
-
-
-
- et-EE
-
-
-
-
- lt-LT
-
-
-
-
- lv-LV
-
-
-
-
- th-TH
-
-
-
-
- zh-HK
-
-
-
-
- sr-Latn-CS
-
-
-
-
- uk-UA
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 00000409
-
-
-
-
- 00000411
-
-
-
-
- 00000412
-
-
-
-
- 00000407
-
-
-
-
- 00000804
-
-
-
-
- 00000404
-
-
-
-
- 0000040c
-
-
-
-
- 00000c0a
-
-
-
-
- 00000410
-
-
-
-
- 0000041d
-
-
-
-
- 00000413
-
-
-
-
- 00000416
-
-
-
-
- 0000040b
-
-
-
-
- 00000414
-
-
-
-
- 00000406
-
-
-
-
- 0000040e
-
-
-
-
- 00000415
-
-
-
-
- 00000419
-
-
-
-
- 00000405
-
-
-
-
- 00000408
-
-
-
-
- 00000816
-
-
-
-
- 0000041f
-
-
-
-
- 00000401
-
-
-
-
- 0000040d
-
-
-
-
- 0000041b
-
-
-
-
- 00000424
-
-
-
-
- 00000418
-
-
-
-
- 0000041a
-
-
-
-
- 00000402
-
-
-
-
- 00000425
-
-
-
-
- 00000427
-
-
-
-
- 00000426
-
-
-
-
- 0000041e
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/GroupPolicy.admx b/policy_templates/PolicyDefinitions/GroupPolicy.admx
deleted file mode 100644
index 9f6bf4e..0000000
--- a/policy_templates/PolicyDefinitions/GroupPolicy.admx
+++ /dev/null
@@ -1,665 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1000000000000
-
-
-
-
- 2000000000000
-
-
-
-
- 3000000000000
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Handwriting.admx b/policy_templates/PolicyDefinitions/Handwriting.admx
deleted file mode 100644
index 3ccf4de..0000000
--- a/policy_templates/PolicyDefinitions/Handwriting.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Help.admx b/policy_templates/PolicyDefinitions/Help.admx
deleted file mode 100644
index 4fa01d9..0000000
--- a/policy_templates/PolicyDefinitions/Help.admx
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/HelpAndSupport.admx b/policy_templates/PolicyDefinitions/HelpAndSupport.admx
deleted file mode 100644
index 6293ed1..0000000
--- a/policy_templates/PolicyDefinitions/HelpAndSupport.admx
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ICM.admx b/policy_templates/PolicyDefinitions/ICM.admx
deleted file mode 100644
index 2d0c3d3..0000000
--- a/policy_templates/PolicyDefinitions/ICM.admx
+++ /dev/null
@@ -1,782 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/IIS.admx b/policy_templates/PolicyDefinitions/IIS.admx
deleted file mode 100644
index 360215f..0000000
--- a/policy_templates/PolicyDefinitions/IIS.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Kerberos.admx b/policy_templates/PolicyDefinitions/Kerberos.admx
deleted file mode 100644
index 82680ea..0000000
--- a/policy_templates/PolicyDefinitions/Kerberos.admx
+++ /dev/null
@@ -1,286 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/LAPS.admx b/policy_templates/PolicyDefinitions/LAPS.admx
deleted file mode 100644
index 579cd2f..0000000
--- a/policy_templates/PolicyDefinitions/LAPS.admx
+++ /dev/null
@@ -1,279 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/LanmanServer.admx b/policy_templates/PolicyDefinitions/LanmanServer.admx
deleted file mode 100644
index b39e665..0000000
--- a/policy_templates/PolicyDefinitions/LanmanServer.admx
+++ /dev/null
@@ -1,151 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/LanmanWorkstation.admx b/policy_templates/PolicyDefinitions/LanmanWorkstation.admx
deleted file mode 100644
index 4f6d9f1..0000000
--- a/policy_templates/PolicyDefinitions/LanmanWorkstation.admx
+++ /dev/null
@@ -1,125 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/LeakDiagnostic.admx b/policy_templates/PolicyDefinitions/LeakDiagnostic.admx
deleted file mode 100644
index 1c9ff85..0000000
--- a/policy_templates/PolicyDefinitions/LeakDiagnostic.admx
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/LinkLayerTopologyDiscovery.admx b/policy_templates/PolicyDefinitions/LinkLayerTopologyDiscovery.admx
deleted file mode 100644
index a0c5608..0000000
--- a/policy_templates/PolicyDefinitions/LinkLayerTopologyDiscovery.admx
+++ /dev/null
@@ -1,88 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/LocalSecurityAuthority.admx b/policy_templates/PolicyDefinitions/LocalSecurityAuthority.admx
deleted file mode 100644
index 54087c6..0000000
--- a/policy_templates/PolicyDefinitions/LocalSecurityAuthority.admx
+++ /dev/null
@@ -1,49 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/LocationProviderAdm.admx b/policy_templates/PolicyDefinitions/LocationProviderAdm.admx
deleted file mode 100644
index 413d15d..0000000
--- a/policy_templates/PolicyDefinitions/LocationProviderAdm.admx
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Logon.admx b/policy_templates/PolicyDefinitions/Logon.admx
deleted file mode 100644
index d38c3ff..0000000
--- a/policy_templates/PolicyDefinitions/Logon.admx
+++ /dev/null
@@ -1,176 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/MDM.admx b/policy_templates/PolicyDefinitions/MDM.admx
deleted file mode 100644
index abfac4e..0000000
--- a/policy_templates/PolicyDefinitions/MDM.admx
+++ /dev/null
@@ -1,53 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/MMC.admx b/policy_templates/PolicyDefinitions/MMC.admx
deleted file mode 100644
index deef7be..0000000
--- a/policy_templates/PolicyDefinitions/MMC.admx
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/MMCSnapins.admx b/policy_templates/PolicyDefinitions/MMCSnapins.admx
deleted file mode 100644
index 433cc0f..0000000
--- a/policy_templates/PolicyDefinitions/MMCSnapins.admx
+++ /dev/null
@@ -1,1111 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/MSAPolicy.admx b/policy_templates/PolicyDefinitions/MSAPolicy.admx
deleted file mode 100644
index 44b963d..0000000
--- a/policy_templates/PolicyDefinitions/MSAPolicy.admx
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/MSDT.admx b/policy_templates/PolicyDefinitions/MSDT.admx
deleted file mode 100644
index 6effb78..0000000
--- a/policy_templates/PolicyDefinitions/MSDT.admx
+++ /dev/null
@@ -1,114 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/MSI.admx b/policy_templates/PolicyDefinitions/MSI.admx
deleted file mode 100644
index 410e0e4..0000000
--- a/policy_templates/PolicyDefinitions/MSI.admx
+++ /dev/null
@@ -1,348 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/MicrosoftEdge.admx b/policy_templates/PolicyDefinitions/MicrosoftEdge.admx
deleted file mode 100644
index 81ff623..0000000
--- a/policy_templates/PolicyDefinitions/MicrosoftEdge.admx
+++ /dev/null
@@ -1,993 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/MobilePCMobilityCenter.admx b/policy_templates/PolicyDefinitions/MobilePCMobilityCenter.admx
deleted file mode 100644
index e2b8fc9..0000000
--- a/policy_templates/PolicyDefinitions/MobilePCMobilityCenter.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/MobilePCPresentationSettings.admx b/policy_templates/PolicyDefinitions/MobilePCPresentationSettings.admx
deleted file mode 100644
index 24491fa..0000000
--- a/policy_templates/PolicyDefinitions/MobilePCPresentationSettings.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Msi-FileRecovery.admx b/policy_templates/PolicyDefinitions/Msi-FileRecovery.admx
deleted file mode 100644
index c022ca9..0000000
--- a/policy_templates/PolicyDefinitions/Msi-FileRecovery.admx
+++ /dev/null
@@ -1,45 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Multitasking.admx b/policy_templates/PolicyDefinitions/Multitasking.admx
deleted file mode 100644
index 694ee58..0000000
--- a/policy_templates/PolicyDefinitions/Multitasking.admx
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/NCSI.admx b/policy_templates/PolicyDefinitions/NCSI.admx
deleted file mode 100644
index f7e7c4c..0000000
--- a/policy_templates/PolicyDefinitions/NCSI.admx
+++ /dev/null
@@ -1,79 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Netlogon.admx b/policy_templates/PolicyDefinitions/Netlogon.admx
deleted file mode 100644
index 68f39cc..0000000
--- a/policy_templates/PolicyDefinitions/Netlogon.admx
+++ /dev/null
@@ -1,303 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/NetworkConnections.admx b/policy_templates/PolicyDefinitions/NetworkConnections.admx
deleted file mode 100644
index aabeb4a..0000000
--- a/policy_templates/PolicyDefinitions/NetworkConnections.admx
+++ /dev/null
@@ -1,328 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Enabled
-
-
-
-
- Disabled
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/NetworkIsolation.admx b/policy_templates/PolicyDefinitions/NetworkIsolation.admx
deleted file mode 100644
index ff42b21..0000000
--- a/policy_templates/PolicyDefinitions/NetworkIsolation.admx
+++ /dev/null
@@ -1,99 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/NetworkProvider.admx b/policy_templates/PolicyDefinitions/NetworkProvider.admx
deleted file mode 100644
index 8b80d76..0000000
--- a/policy_templates/PolicyDefinitions/NetworkProvider.admx
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/NewsAndInterests.admx b/policy_templates/PolicyDefinitions/NewsAndInterests.admx
deleted file mode 100644
index e667ad1..0000000
--- a/policy_templates/PolicyDefinitions/NewsAndInterests.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/OOBE.admx b/policy_templates/PolicyDefinitions/OOBE.admx
deleted file mode 100644
index 86cee52..0000000
--- a/policy_templates/PolicyDefinitions/OOBE.admx
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/OSPolicy.admx b/policy_templates/PolicyDefinitions/OSPolicy.admx
deleted file mode 100644
index 05dcd43..0000000
--- a/policy_templates/PolicyDefinitions/OSPolicy.admx
+++ /dev/null
@@ -1,66 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/OfflineFiles.admx b/policy_templates/PolicyDefinitions/OfflineFiles.admx
deleted file mode 100644
index 02d0590..0000000
--- a/policy_templates/PolicyDefinitions/OfflineFiles.admx
+++ /dev/null
@@ -1,429 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/P2P-pnrp.admx b/policy_templates/PolicyDefinitions/P2P-pnrp.admx
deleted file mode 100644
index f3faf83..0000000
--- a/policy_templates/PolicyDefinitions/P2P-pnrp.admx
+++ /dev/null
@@ -1,154 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Passport.admx b/policy_templates/PolicyDefinitions/Passport.admx
deleted file mode 100644
index f64a72f..0000000
--- a/policy_templates/PolicyDefinitions/Passport.admx
+++ /dev/null
@@ -1,255 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/PeerToPeerCaching.admx b/policy_templates/PolicyDefinitions/PeerToPeerCaching.admx
deleted file mode 100644
index 1769e5a..0000000
--- a/policy_templates/PolicyDefinitions/PeerToPeerCaching.admx
+++ /dev/null
@@ -1,166 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/PenTraining.admx b/policy_templates/PolicyDefinitions/PenTraining.admx
deleted file mode 100644
index c499ac0..0000000
--- a/policy_templates/PolicyDefinitions/PenTraining.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/PerformanceDiagnostics.admx b/policy_templates/PolicyDefinitions/PerformanceDiagnostics.admx
deleted file mode 100644
index 5949112..0000000
--- a/policy_templates/PolicyDefinitions/PerformanceDiagnostics.admx
+++ /dev/null
@@ -1,159 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Power.admx b/policy_templates/PolicyDefinitions/Power.admx
deleted file mode 100644
index 6253990..0000000
--- a/policy_templates/PolicyDefinitions/Power.admx
+++ /dev/null
@@ -1,678 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 381b4222-f694-41f0-9685-ff5bb260df2e
-
-
-
-
- a1841308-3541-4fab-bc81-f71556f20b4a
-
-
-
-
- 8c5e7fda-e8bf-4a96-9a85-a6e23a8c635c
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/PowerShellExecutionPolicy.admx b/policy_templates/PolicyDefinitions/PowerShellExecutionPolicy.admx
deleted file mode 100644
index 8283855..0000000
--- a/policy_templates/PolicyDefinitions/PowerShellExecutionPolicy.admx
+++ /dev/null
@@ -1,102 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- AllSigned
-
-
-
-
- RemoteSigned
-
-
-
-
- Unrestricted
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/PreviousVersions.admx b/policy_templates/PolicyDefinitions/PreviousVersions.admx
deleted file mode 100644
index 53d2fa0..0000000
--- a/policy_templates/PolicyDefinitions/PreviousVersions.admx
+++ /dev/null
@@ -1,148 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Printing.admx b/policy_templates/PolicyDefinitions/Printing.admx
deleted file mode 100644
index 85072d1..0000000
--- a/policy_templates/PolicyDefinitions/Printing.admx
+++ /dev/null
@@ -1,1085 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Printing2.admx b/policy_templates/PolicyDefinitions/Printing2.admx
deleted file mode 100644
index 9a16806..0000000
--- a/policy_templates/PolicyDefinitions/Printing2.admx
+++ /dev/null
@@ -1,413 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Programs.admx b/policy_templates/PolicyDefinitions/Programs.admx
deleted file mode 100644
index 3f9688a..0000000
--- a/policy_templates/PolicyDefinitions/Programs.admx
+++ /dev/null
@@ -1,57 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/PushToInstall.admx b/policy_templates/PolicyDefinitions/PushToInstall.admx
deleted file mode 100644
index 3b85c3a..0000000
--- a/policy_templates/PolicyDefinitions/PushToInstall.admx
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/QOS.admx b/policy_templates/PolicyDefinitions/QOS.admx
deleted file mode 100644
index 0a5c931..0000000
--- a/policy_templates/PolicyDefinitions/QOS.admx
+++ /dev/null
@@ -1,158 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/RPC.admx b/policy_templates/PolicyDefinitions/RPC.admx
deleted file mode 100644
index cecf06d..0000000
--- a/policy_templates/PolicyDefinitions/RPC.admx
+++ /dev/null
@@ -1,136 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/RacWmiProv.admx b/policy_templates/PolicyDefinitions/RacWmiProv.admx
deleted file mode 100644
index 05b5416..0000000
--- a/policy_templates/PolicyDefinitions/RacWmiProv.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Radar.admx b/policy_templates/PolicyDefinitions/Radar.admx
deleted file mode 100644
index ce356d7..0000000
--- a/policy_templates/PolicyDefinitions/Radar.admx
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ReAgent.admx b/policy_templates/PolicyDefinitions/ReAgent.admx
deleted file mode 100644
index 493f42f..0000000
--- a/policy_templates/PolicyDefinitions/ReAgent.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Reliability.admx b/policy_templates/PolicyDefinitions/Reliability.admx
deleted file mode 100644
index 63a8227..0000000
--- a/policy_templates/PolicyDefinitions/Reliability.admx
+++ /dev/null
@@ -1,74 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/RemoteAssistance.admx b/policy_templates/PolicyDefinitions/RemoteAssistance.admx
deleted file mode 100644
index 3b01b2f..0000000
--- a/policy_templates/PolicyDefinitions/RemoteAssistance.admx
+++ /dev/null
@@ -1,163 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/RemovableStorage.admx b/policy_templates/PolicyDefinitions/RemovableStorage.admx
deleted file mode 100644
index 2788dc9..0000000
--- a/policy_templates/PolicyDefinitions/RemovableStorage.admx
+++ /dev/null
@@ -1,420 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Scripts.admx b/policy_templates/PolicyDefinitions/Scripts.admx
deleted file mode 100644
index 82a6f6d..0000000
--- a/policy_templates/PolicyDefinitions/Scripts.admx
+++ /dev/null
@@ -1,127 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Search.admx b/policy_templates/PolicyDefinitions/Search.admx
deleted file mode 100644
index 3891d0a..0000000
Binary files a/policy_templates/PolicyDefinitions/Search.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/Securitycenter.admx b/policy_templates/PolicyDefinitions/Securitycenter.admx
deleted file mode 100644
index 7b38373..0000000
--- a/policy_templates/PolicyDefinitions/Securitycenter.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Sensors.admx b/policy_templates/PolicyDefinitions/Sensors.admx
deleted file mode 100644
index 9025693..0000000
--- a/policy_templates/PolicyDefinitions/Sensors.admx
+++ /dev/null
@@ -1,273 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ServerManager.admx b/policy_templates/PolicyDefinitions/ServerManager.admx
deleted file mode 100644
index 1bc1770..0000000
--- a/policy_templates/PolicyDefinitions/ServerManager.admx
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ServiceControlManager.admx b/policy_templates/PolicyDefinitions/ServiceControlManager.admx
deleted file mode 100644
index 384552a..0000000
--- a/policy_templates/PolicyDefinitions/ServiceControlManager.admx
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Servicing.admx b/policy_templates/PolicyDefinitions/Servicing.admx
deleted file mode 100644
index a3a9cec..0000000
--- a/policy_templates/PolicyDefinitions/Servicing.admx
+++ /dev/null
@@ -1,48 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/SettingSync.admx b/policy_templates/PolicyDefinitions/SettingSync.admx
deleted file mode 100644
index fb871e3..0000000
--- a/policy_templates/PolicyDefinitions/SettingSync.admx
+++ /dev/null
@@ -1,258 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Setup.admx b/policy_templates/PolicyDefinitions/Setup.admx
deleted file mode 100644
index 35cf958..0000000
--- a/policy_templates/PolicyDefinitions/Setup.admx
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/SharedFolders.admx b/policy_templates/PolicyDefinitions/SharedFolders.admx
deleted file mode 100644
index c9ada2a..0000000
--- a/policy_templates/PolicyDefinitions/SharedFolders.admx
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Sharing.admx b/policy_templates/PolicyDefinitions/Sharing.admx
deleted file mode 100644
index 28c1232..0000000
--- a/policy_templates/PolicyDefinitions/Sharing.admx
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Shell-CommandPrompt-RegEditTools.admx b/policy_templates/PolicyDefinitions/Shell-CommandPrompt-RegEditTools.admx
deleted file mode 100644
index 09a37bb..0000000
--- a/policy_templates/PolicyDefinitions/Shell-CommandPrompt-RegEditTools.admx
+++ /dev/null
@@ -1,67 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ShellWelcomeCenter.admx b/policy_templates/PolicyDefinitions/ShellWelcomeCenter.admx
deleted file mode 100644
index 5622d25..0000000
--- a/policy_templates/PolicyDefinitions/ShellWelcomeCenter.admx
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Sidebar.admx b/policy_templates/PolicyDefinitions/Sidebar.admx
deleted file mode 100644
index 366a5df..0000000
--- a/policy_templates/PolicyDefinitions/Sidebar.admx
+++ /dev/null
@@ -1,76 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/SkyDrive.admx b/policy_templates/PolicyDefinitions/SkyDrive.admx
deleted file mode 100644
index b4702d8..0000000
--- a/policy_templates/PolicyDefinitions/SkyDrive.admx
+++ /dev/null
@@ -1,73 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/SmartScreen.admx b/policy_templates/PolicyDefinitions/SmartScreen.admx
deleted file mode 100644
index ab102ec..0000000
--- a/policy_templates/PolicyDefinitions/SmartScreen.admx
+++ /dev/null
@@ -1,108 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Block
-
-
-
-
- Warn
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Anywhere
-
-
-
-
- Recommendations
-
-
-
-
- PreferStore
-
-
-
-
- StoreOnly
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Smartcard.admx b/policy_templates/PolicyDefinitions/Smartcard.admx
deleted file mode 100644
index eb8a49d..0000000
--- a/policy_templates/PolicyDefinitions/Smartcard.admx
+++ /dev/null
@@ -1,191 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Snmp.admx b/policy_templates/PolicyDefinitions/Snmp.admx
deleted file mode 100644
index 9f7bf93..0000000
--- a/policy_templates/PolicyDefinitions/Snmp.admx
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/SoundRec.admx b/policy_templates/PolicyDefinitions/SoundRec.admx
deleted file mode 100644
index dbb49f0..0000000
--- a/policy_templates/PolicyDefinitions/SoundRec.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Speech.admx b/policy_templates/PolicyDefinitions/Speech.admx
deleted file mode 100644
index 1f7b910..0000000
--- a/policy_templates/PolicyDefinitions/Speech.admx
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/StartMenu.admx b/policy_templates/PolicyDefinitions/StartMenu.admx
deleted file mode 100644
index 05593a1..0000000
--- a/policy_templates/PolicyDefinitions/StartMenu.admx
+++ /dev/null
@@ -1,587 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/StorageHealth.admx b/policy_templates/PolicyDefinitions/StorageHealth.admx
deleted file mode 100644
index a0b13f2..0000000
--- a/policy_templates/PolicyDefinitions/StorageHealth.admx
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/StorageSense.admx b/policy_templates/PolicyDefinitions/StorageSense.admx
deleted file mode 100644
index e0449c8..0000000
--- a/policy_templates/PolicyDefinitions/StorageSense.admx
+++ /dev/null
@@ -1,121 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/SystemRestore.admx b/policy_templates/PolicyDefinitions/SystemRestore.admx
deleted file mode 100644
index a47dbcf..0000000
--- a/policy_templates/PolicyDefinitions/SystemRestore.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/TPM.admx b/policy_templates/PolicyDefinitions/TPM.admx
deleted file mode 100644
index cf05a2e..0000000
--- a/policy_templates/PolicyDefinitions/TPM.admx
+++ /dev/null
@@ -1,126 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/TabletPCInputPanel.admx b/policy_templates/PolicyDefinitions/TabletPCInputPanel.admx
deleted file mode 100644
index a39ff8a..0000000
--- a/policy_templates/PolicyDefinitions/TabletPCInputPanel.admx
+++ /dev/null
@@ -1,272 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/TabletShell.admx b/policy_templates/PolicyDefinitions/TabletShell.admx
deleted file mode 100644
index 8b038fd..0000000
--- a/policy_templates/PolicyDefinitions/TabletShell.admx
+++ /dev/null
@@ -1,248 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/TaskScheduler.admx b/policy_templates/PolicyDefinitions/TaskScheduler.admx
deleted file mode 100644
index 11b0c1d..0000000
--- a/policy_templates/PolicyDefinitions/TaskScheduler.admx
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Taskbar.admx b/policy_templates/PolicyDefinitions/Taskbar.admx
deleted file mode 100644
index b20938a..0000000
--- a/policy_templates/PolicyDefinitions/Taskbar.admx
+++ /dev/null
@@ -1,303 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/TenantRestrictions.admx b/policy_templates/PolicyDefinitions/TenantRestrictions.admx
deleted file mode 100644
index 5622758..0000000
--- a/policy_templates/PolicyDefinitions/TenantRestrictions.admx
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/TerminalServer.admx b/policy_templates/PolicyDefinitions/TerminalServer.admx
deleted file mode 100644
index b398416..0000000
--- a/policy_templates/PolicyDefinitions/TerminalServer.admx
+++ /dev/null
@@ -1,2224 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- G:
-
-
-
-
- H:
-
-
-
-
- I:
-
-
-
-
- J:
-
-
-
-
- K:
-
-
-
-
- L:
-
-
-
-
- M:
-
-
-
-
- N:
-
-
-
-
- O:
-
-
-
-
- P:
-
-
-
-
- Q:
-
-
-
-
- R:
-
-
-
-
- S:
-
-
-
-
- T:
-
-
-
-
- U:
-
-
-
-
- V:
-
-
-
-
- W:
-
-
-
-
- X:
-
-
-
-
- Y:
-
-
-
-
- Z:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/TextInput.admx b/policy_templates/PolicyDefinitions/TextInput.admx
deleted file mode 100644
index fe6de26..0000000
--- a/policy_templates/PolicyDefinitions/TextInput.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Thumbnails.admx b/policy_templates/PolicyDefinitions/Thumbnails.admx
deleted file mode 100644
index efa3a11..0000000
--- a/policy_templates/PolicyDefinitions/Thumbnails.admx
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/TouchInput.admx b/policy_templates/PolicyDefinitions/TouchInput.admx
deleted file mode 100644
index cbe35ed..0000000
--- a/policy_templates/PolicyDefinitions/TouchInput.admx
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/UserExperienceVirtualization.admx b/policy_templates/PolicyDefinitions/UserExperienceVirtualization.admx
deleted file mode 100644
index 15ea889..0000000
--- a/policy_templates/PolicyDefinitions/UserExperienceVirtualization.admx
+++ /dev/null
@@ -1,2959 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- SyncProvider
-
-
-
-
- None
-
-
-
-
- External
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/UserProfiles.admx b/policy_templates/PolicyDefinitions/UserProfiles.admx
deleted file mode 100644
index 452b5e9..0000000
--- a/policy_templates/PolicyDefinitions/UserProfiles.admx
+++ /dev/null
@@ -1,444 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- G:
-
-
-
-
- H:
-
-
-
-
- I:
-
-
-
-
- J:
-
-
-
-
- K:
-
-
-
-
- L:
-
-
-
-
- M:
-
-
-
-
- N:
-
-
-
-
- O:
-
-
-
-
- P:
-
-
-
-
- Q:
-
-
-
-
- R:
-
-
-
-
- S:
-
-
-
-
- T:
-
-
-
-
- U:
-
-
-
-
- V:
-
-
-
-
- W:
-
-
-
-
- X:
-
-
-
-
- Y:
-
-
-
-
- Z:
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/VolumeEncryption.admx b/policy_templates/PolicyDefinitions/VolumeEncryption.admx
deleted file mode 100644
index fb71331..0000000
--- a/policy_templates/PolicyDefinitions/VolumeEncryption.admx
+++ /dev/null
@@ -1,1892 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FAT32
-
-
- <none>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- FAT32
-
-
- <none>
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/W32Time.admx b/policy_templates/PolicyDefinitions/W32Time.admx
deleted file mode 100644
index 6727ca9..0000000
--- a/policy_templates/PolicyDefinitions/W32Time.admx
+++ /dev/null
@@ -1,103 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- NoSync
-
-
-
-
- NTP
-
-
-
-
- NT5DS
-
-
-
-
- AllSync
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WCM.admx b/policy_templates/PolicyDefinitions/WCM.admx
deleted file mode 100644
index 611563d..0000000
--- a/policy_templates/PolicyDefinitions/WCM.admx
+++ /dev/null
@@ -1,85 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WDI.admx b/policy_templates/PolicyDefinitions/WDI.admx
deleted file mode 100644
index 783cb24..0000000
--- a/policy_templates/PolicyDefinitions/WDI.admx
+++ /dev/null
@@ -1,48 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WPN.admx b/policy_templates/PolicyDefinitions/WPN.admx
deleted file mode 100644
index 3a260bf..0000000
--- a/policy_templates/PolicyDefinitions/WPN.admx
+++ /dev/null
@@ -1,128 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WebThreatDefense.admx b/policy_templates/PolicyDefinitions/WebThreatDefense.admx
deleted file mode 100644
index 28db87a..0000000
--- a/policy_templates/PolicyDefinitions/WebThreatDefense.admx
+++ /dev/null
@@ -1,65 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WinCal.admx b/policy_templates/PolicyDefinitions/WinCal.admx
deleted file mode 100644
index 38488fe..0000000
--- a/policy_templates/PolicyDefinitions/WinCal.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WinInit.admx b/policy_templates/PolicyDefinitions/WinInit.admx
deleted file mode 100644
index c9cd039..0000000
--- a/policy_templates/PolicyDefinitions/WinInit.admx
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WinLogon.admx b/policy_templates/PolicyDefinitions/WinLogon.admx
deleted file mode 100644
index 433738d..0000000
--- a/policy_templates/PolicyDefinitions/WinLogon.admx
+++ /dev/null
@@ -1,149 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WinMaps.admx b/policy_templates/PolicyDefinitions/WinMaps.admx
deleted file mode 100644
index 11faa33..0000000
--- a/policy_templates/PolicyDefinitions/WinMaps.admx
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Windows.admx b/policy_templates/PolicyDefinitions/Windows.admx
deleted file mode 100644
index aa5cb00..0000000
--- a/policy_templates/PolicyDefinitions/Windows.admx
+++ /dev/null
@@ -1,639 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsAnytimeUpgrade.admx b/policy_templates/PolicyDefinitions/WindowsAnytimeUpgrade.admx
deleted file mode 100644
index 3bc9ad2..0000000
--- a/policy_templates/PolicyDefinitions/WindowsAnytimeUpgrade.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsBackup.admx b/policy_templates/PolicyDefinitions/WindowsBackup.admx
deleted file mode 100644
index effe64f..0000000
--- a/policy_templates/PolicyDefinitions/WindowsBackup.admx
+++ /dev/null
@@ -1,71 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsColorSystem.admx b/policy_templates/PolicyDefinitions/WindowsColorSystem.admx
deleted file mode 100644
index 618ba9f..0000000
--- a/policy_templates/PolicyDefinitions/WindowsColorSystem.admx
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsConnectNow.admx b/policy_templates/PolicyDefinitions/WindowsConnectNow.admx
deleted file mode 100644
index e080609..0000000
--- a/policy_templates/PolicyDefinitions/WindowsConnectNow.admx
+++ /dev/null
@@ -1,93 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsDefender.admx b/policy_templates/PolicyDefinitions/WindowsDefender.admx
deleted file mode 100644
index 504cac6..0000000
--- a/policy_templates/PolicyDefinitions/WindowsDefender.admx
+++ /dev/null
@@ -1,1523 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- "
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsDefenderSecurityCenter.admx b/policy_templates/PolicyDefinitions/WindowsDefenderSecurityCenter.admx
deleted file mode 100644
index 7ac69e6..0000000
--- a/policy_templates/PolicyDefinitions/WindowsDefenderSecurityCenter.admx
+++ /dev/null
@@ -1,254 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/WindowsExplorer.admx b/policy_templates/PolicyDefinitions/WindowsExplorer.admx
deleted file mode 100644
index 9cd73c1..0000000
--- a/policy_templates/PolicyDefinitions/WindowsExplorer.admx
+++ /dev/null
@@ -1,812 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Block
-
-
-
-
- Warn
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsFileProtection.admx b/policy_templates/PolicyDefinitions/WindowsFileProtection.admx
deleted file mode 100644
index 6d437c6..0000000
--- a/policy_templates/PolicyDefinitions/WindowsFileProtection.admx
+++ /dev/null
@@ -1,58 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsFirewall.admx b/policy_templates/PolicyDefinitions/WindowsFirewall.admx
deleted file mode 100644
index e72431f..0000000
--- a/policy_templates/PolicyDefinitions/WindowsFirewall.admx
+++ /dev/null
@@ -1,550 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsInkWorkspace.admx b/policy_templates/PolicyDefinitions/WindowsInkWorkspace.admx
deleted file mode 100644
index 89f9b2d..0000000
--- a/policy_templates/PolicyDefinitions/WindowsInkWorkspace.admx
+++ /dev/null
@@ -1,54 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsMessenger.admx b/policy_templates/PolicyDefinitions/WindowsMessenger.admx
deleted file mode 100644
index d1584fa..0000000
--- a/policy_templates/PolicyDefinitions/WindowsMessenger.admx
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsProducts.admx b/policy_templates/PolicyDefinitions/WindowsProducts.admx
deleted file mode 100644
index 7edbd17..0000000
--- a/policy_templates/PolicyDefinitions/WindowsProducts.admx
+++ /dev/null
@@ -1,141 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsRemoteManagement.admx b/policy_templates/PolicyDefinitions/WindowsRemoteManagement.admx
deleted file mode 100644
index 8743922..0000000
--- a/policy_templates/PolicyDefinitions/WindowsRemoteManagement.admx
+++ /dev/null
@@ -1,206 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- None
-
-
-
-
- Relaxed
-
-
-
-
- Strict
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsRemoteShell.admx b/policy_templates/PolicyDefinitions/WindowsRemoteShell.admx
deleted file mode 100644
index 0a32d53..0000000
--- a/policy_templates/PolicyDefinitions/WindowsRemoteShell.admx
+++ /dev/null
@@ -1,68 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- "
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsSandbox.admx b/policy_templates/PolicyDefinitions/WindowsSandbox.admx
deleted file mode 100644
index 276e4ee..0000000
--- a/policy_templates/PolicyDefinitions/WindowsSandbox.admx
+++ /dev/null
@@ -1,123 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsStore.admx b/policy_templates/PolicyDefinitions/WindowsStore.admx
deleted file mode 100644
index 8b557eb..0000000
--- a/policy_templates/PolicyDefinitions/WindowsStore.admx
+++ /dev/null
@@ -1,151 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WindowsUpdate.admx b/policy_templates/PolicyDefinitions/WindowsUpdate.admx
deleted file mode 100644
index fd6353f..0000000
--- a/policy_templates/PolicyDefinitions/WindowsUpdate.admx
+++ /dev/null
@@ -1,2820 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/Winsrv.admx b/policy_templates/PolicyDefinitions/Winsrv.admx
deleted file mode 100644
index a76ecd9..0000000
--- a/policy_templates/PolicyDefinitions/Winsrv.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WirelessDisplay.admx b/policy_templates/PolicyDefinitions/WirelessDisplay.admx
deleted file mode 100644
index 1fd83da..0000000
--- a/policy_templates/PolicyDefinitions/WirelessDisplay.admx
+++ /dev/null
@@ -1,48 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/WordWheel.admx b/policy_templates/PolicyDefinitions/WordWheel.admx
deleted file mode 100644
index 867fb0e..0000000
--- a/policy_templates/PolicyDefinitions/WordWheel.admx
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WorkFolders-Client.admx b/policy_templates/PolicyDefinitions/WorkFolders-Client.admx
deleted file mode 100644
index ef23189..0000000
--- a/policy_templates/PolicyDefinitions/WorkFolders-Client.admx
+++ /dev/null
@@ -1,88 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/WorkplaceJoin.admx b/policy_templates/PolicyDefinitions/WorkplaceJoin.admx
deleted file mode 100644
index d072a5c..0000000
--- a/policy_templates/PolicyDefinitions/WorkplaceJoin.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/access16.admx b/policy_templates/PolicyDefinitions/access16.admx
deleted file mode 100644
index 26077b5..0000000
Binary files a/policy_templates/PolicyDefinitions/access16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/appv.admx b/policy_templates/PolicyDefinitions/appv.admx
deleted file mode 100644
index b7efabd..0000000
--- a/policy_templates/PolicyDefinitions/appv.admx
+++ /dev/null
@@ -1,776 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/chrome.admx b/policy_templates/PolicyDefinitions/chrome.admx
deleted file mode 100644
index 58ef6af..0000000
Binary files a/policy_templates/PolicyDefinitions/chrome.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/excel16.admx b/policy_templates/PolicyDefinitions/excel16.admx
deleted file mode 100644
index c44898e..0000000
Binary files a/policy_templates/PolicyDefinitions/excel16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/feeds.admx b/policy_templates/PolicyDefinitions/feeds.admx
deleted file mode 100644
index 4d4ffd8..0000000
--- a/policy_templates/PolicyDefinitions/feeds.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/firefox.admx b/policy_templates/PolicyDefinitions/firefox.admx
deleted file mode 100644
index ba3436e..0000000
--- a/policy_templates/PolicyDefinitions/firefox.admx
+++ /dev/null
@@ -1,4137 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- always
-
-
-
-
- never
-
-
-
-
- from-visited
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- accept
-
-
-
-
- reject-foreign
-
-
-
-
- reject
-
-
-
-
- limit-foreign
-
-
-
-
- reject-tracker
-
-
-
-
- reject-tracker-and-partition-foreign
-
-
-
-
-
-
-
-
-
-
-
-
- accept
-
-
-
-
- reject-foreign
-
-
-
-
- reject
-
-
-
-
- limit-foreign
-
-
-
-
- reject-tracker
-
-
-
-
- reject-tracker-and-partition-foreign
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- allow-audio-video
-
-
-
-
- block-audio
-
-
-
-
- block-audio-video
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- always
-
-
-
-
- never
-
-
-
-
- newtab
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- always
-
-
-
-
- never
-
-
-
-
- default-on
-
-
-
-
- default-off
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- none
-
-
-
-
- homepage
-
-
-
-
- previous-session
-
-
-
-
- homepage-locked
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- toolbar
-
-
-
-
- menu
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- none
-
-
-
-
- system
-
-
-
-
- manual
-
-
-
-
- autoDetect
-
-
-
-
- autoConfig
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- unified
-
-
-
-
- separate
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- GET
-
-
-
-
- POST
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- GET
-
-
-
-
- POST
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- GET
-
-
-
-
- POST
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- GET
-
-
-
-
- POST
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- GET
-
-
-
-
- POST
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- tls1
-
-
-
-
- tls1.1
-
-
-
-
- tls1.2
-
-
-
-
- tls1.3
-
-
-
-
-
-
-
-
-
-
-
-
- tls1
-
-
-
-
- tls1.1
-
-
-
-
- tls1.2
-
-
-
-
- tls1.3
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Ask Every Time
-
-
-
-
- Select Automatically
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/fthsvc.admx b/policy_templates/PolicyDefinitions/fthsvc.admx
deleted file mode 100644
index aaa2c36..0000000
--- a/policy_templates/PolicyDefinitions/fthsvc.admx
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/grouppolicy-server.admx b/policy_templates/PolicyDefinitions/grouppolicy-server.admx
deleted file mode 100644
index d6ebd9f..0000000
--- a/policy_templates/PolicyDefinitions/grouppolicy-server.admx
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/grouppolicypreferences.admx b/policy_templates/PolicyDefinitions/grouppolicypreferences.admx
deleted file mode 100644
index 5f5b842..0000000
--- a/policy_templates/PolicyDefinitions/grouppolicypreferences.admx
+++ /dev/null
@@ -1,2351 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Applications Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Data Sources Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Devices Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Drive Maps Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Environment Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Files Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Folder Options Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Folders Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Ini Files Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Internet Settings Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Local Users and Groups Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Network Options Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Network Shares Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Power Options Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Printers Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Regional Options Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Registry Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Scheduled Tasks Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Services Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Shortcuts Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Start Menu Policy Processing
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/hotspotauth.admx b/policy_templates/PolicyDefinitions/hotspotauth.admx
deleted file mode 100644
index c8812f1..0000000
--- a/policy_templates/PolicyDefinitions/hotspotauth.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/iSCSI.admx b/policy_templates/PolicyDefinitions/iSCSI.admx
deleted file mode 100644
index 6c5cd9d..0000000
--- a/policy_templates/PolicyDefinitions/iSCSI.admx
+++ /dev/null
@@ -1,125 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/inetres.admx b/policy_templates/PolicyDefinitions/inetres.admx
deleted file mode 100644
index 2e82e08..0000000
--- a/policy_templates/PolicyDefinitions/inetres.admx
+++ /dev/null
@@ -1,35737 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- PMEM
-
-
- PMIL
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
-
-
- no
-
-
-
-
- hover
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- yes
-
-
- no
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1
-
-
- 0
-
-
-
-
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
- 1
-
-
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 0
-
-
- 1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/inkwatson.admx b/policy_templates/PolicyDefinitions/inkwatson.admx
deleted file mode 100644
index eed7eba..0000000
--- a/policy_templates/PolicyDefinitions/inkwatson.admx
+++ /dev/null
@@ -1,31 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/kdc.admx b/policy_templates/PolicyDefinitions/kdc.admx
deleted file mode 100644
index 216f475..0000000
--- a/policy_templates/PolicyDefinitions/kdc.admx
+++ /dev/null
@@ -1,220 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/lync16.admx b/policy_templates/PolicyDefinitions/lync16.admx
deleted file mode 100644
index 25d98d1..0000000
Binary files a/policy_templates/PolicyDefinitions/lync16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/messaging.admx b/policy_templates/PolicyDefinitions/messaging.admx
deleted file mode 100644
index 3089b95..0000000
--- a/policy_templates/PolicyDefinitions/messaging.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/mmcsnapins2.admx b/policy_templates/PolicyDefinitions/mmcsnapins2.admx
deleted file mode 100644
index e59d080..0000000
--- a/policy_templates/PolicyDefinitions/mmcsnapins2.admx
+++ /dev/null
@@ -1,124 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/mozilla.admx b/policy_templates/PolicyDefinitions/mozilla.admx
deleted file mode 100644
index 9b61a8a..0000000
--- a/policy_templates/PolicyDefinitions/mozilla.admx
+++ /dev/null
@@ -1,10 +0,0 @@
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/msched.admx b/policy_templates/PolicyDefinitions/msched.admx
deleted file mode 100644
index c5b2af1..0000000
--- a/policy_templates/PolicyDefinitions/msched.admx
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/nca.admx b/policy_templates/PolicyDefinitions/nca.admx
deleted file mode 100644
index 47bb0d5..0000000
--- a/policy_templates/PolicyDefinitions/nca.admx
+++ /dev/null
@@ -1,90 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/office16.admx b/policy_templates/PolicyDefinitions/office16.admx
deleted file mode 100644
index 4a273f6..0000000
Binary files a/policy_templates/PolicyDefinitions/office16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/onent16.admx b/policy_templates/PolicyDefinitions/onent16.admx
deleted file mode 100644
index 1df6cfc..0000000
Binary files a/policy_templates/PolicyDefinitions/onent16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/outlk16.admx b/policy_templates/PolicyDefinitions/outlk16.admx
deleted file mode 100644
index 3568e5d..0000000
Binary files a/policy_templates/PolicyDefinitions/outlk16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/pca.admx b/policy_templates/PolicyDefinitions/pca.admx
deleted file mode 100644
index c085ae4..0000000
--- a/policy_templates/PolicyDefinitions/pca.admx
+++ /dev/null
@@ -1,207 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/performanceperftrack.admx b/policy_templates/PolicyDefinitions/performanceperftrack.admx
deleted file mode 100644
index 90feaba..0000000
--- a/policy_templates/PolicyDefinitions/performanceperftrack.admx
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/ppt16.admx b/policy_templates/PolicyDefinitions/ppt16.admx
deleted file mode 100644
index 4d00968..0000000
Binary files a/policy_templates/PolicyDefinitions/ppt16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/proj16.admx b/policy_templates/PolicyDefinitions/proj16.admx
deleted file mode 100644
index f37411b..0000000
Binary files a/policy_templates/PolicyDefinitions/proj16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/pub16.admx b/policy_templates/PolicyDefinitions/pub16.admx
deleted file mode 100644
index 743fd05..0000000
Binary files a/policy_templates/PolicyDefinitions/pub16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/sam.admx b/policy_templates/PolicyDefinitions/sam.admx
deleted file mode 100644
index 6302811..0000000
--- a/policy_templates/PolicyDefinitions/sam.admx
+++ /dev/null
@@ -1,64 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/sdiageng.admx b/policy_templates/PolicyDefinitions/sdiageng.admx
deleted file mode 100644
index e9a2ee9..0000000
--- a/policy_templates/PolicyDefinitions/sdiageng.admx
+++ /dev/null
@@ -1,46 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/sdiagschd.admx b/policy_templates/PolicyDefinitions/sdiagschd.admx
deleted file mode 100644
index 202fefc..0000000
--- a/policy_templates/PolicyDefinitions/sdiagschd.admx
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/searchocr.admx b/policy_templates/PolicyDefinitions/searchocr.admx
deleted file mode 100644
index 54607a0..0000000
--- a/policy_templates/PolicyDefinitions/searchocr.admx
+++ /dev/null
@@ -1,511 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- ar
-
-
-
-
- bs-latn-ba
-
-
-
-
- bg
-
-
-
-
- hr
-
-
-
-
- sl
-
-
-
-
- cs
-
-
-
-
- hu
-
-
-
-
- pl
-
-
-
-
- ru
-
-
-
-
- da
-
-
-
-
- nl
-
-
-
-
- en
-
-
-
-
- fi
-
-
-
-
- fr
-
-
-
-
- de
-
-
-
-
- it
-
-
-
-
- nb
-
-
-
-
- pt
-
-
-
-
- ro
-
-
-
-
- sr-cyrl-rs
-
-
-
-
- sr-latn-rs
-
-
-
-
- sk
-
-
-
-
- es
-
-
-
-
- sv
-
-
-
-
- el
-
-
-
-
- tr
-
-
-
-
- zh-Hans
-
-
-
-
- zh-Hant
-
-
-
-
- ja
-
-
-
-
- ko
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
\ No newline at end of file
diff --git a/policy_templates/PolicyDefinitions/shapecollector.admx b/policy_templates/PolicyDefinitions/shapecollector.admx
deleted file mode 100644
index 0a0b101..0000000
--- a/policy_templates/PolicyDefinitions/shapecollector.admx
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/srm-fci.admx b/policy_templates/PolicyDefinitions/srm-fci.admx
deleted file mode 100644
index 0d13105..0000000
--- a/policy_templates/PolicyDefinitions/srm-fci.admx
+++ /dev/null
@@ -1,61 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/tcpip.admx b/policy_templates/PolicyDefinitions/tcpip.admx
deleted file mode 100644
index 7af2896..0000000
--- a/policy_templates/PolicyDefinitions/tcpip.admx
+++ /dev/null
@@ -1,213 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Default
-
-
-
-
-
- Enabled
-
-
-
-
-
- Disabled
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Default
-
-
-
-
-
- Enabled
-
-
-
-
-
- Disabled
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Default
-
-
-
-
-
- Disabled
-
-
-
-
-
- Client
-
-
-
-
-
- Enterprise Client
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Enabled
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/teams16.admx b/policy_templates/PolicyDefinitions/teams16.admx
deleted file mode 100644
index f6b4176..0000000
Binary files a/policy_templates/PolicyDefinitions/teams16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/terminalserver-server.admx b/policy_templates/PolicyDefinitions/terminalserver-server.admx
deleted file mode 100644
index e573975..0000000
--- a/policy_templates/PolicyDefinitions/terminalserver-server.admx
+++ /dev/null
@@ -1,404 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/visio16.admx b/policy_templates/PolicyDefinitions/visio16.admx
deleted file mode 100644
index ae2093a..0000000
Binary files a/policy_templates/PolicyDefinitions/visio16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/windowsmediadrm.admx b/policy_templates/PolicyDefinitions/windowsmediadrm.admx
deleted file mode 100644
index 12b1b7a..0000000
--- a/policy_templates/PolicyDefinitions/windowsmediadrm.admx
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/windowsmediaplayer.admx b/policy_templates/PolicyDefinitions/windowsmediaplayer.admx
deleted file mode 100644
index faef9fc..0000000
--- a/policy_templates/PolicyDefinitions/windowsmediaplayer.admx
+++ /dev/null
@@ -1,520 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- no
-
-
- yes
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/windowsserver.admx b/policy_templates/PolicyDefinitions/windowsserver.admx
deleted file mode 100644
index bf409af..0000000
--- a/policy_templates/PolicyDefinitions/windowsserver.admx
+++ /dev/null
@@ -1,28 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/wlansvc.admx b/policy_templates/PolicyDefinitions/wlansvc.admx
deleted file mode 100644
index 5c2ec61..0000000
--- a/policy_templates/PolicyDefinitions/wlansvc.admx
+++ /dev/null
@@ -1,79 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/PolicyDefinitions/word16.admx b/policy_templates/PolicyDefinitions/word16.admx
deleted file mode 100644
index c12c5a0..0000000
Binary files a/policy_templates/PolicyDefinitions/word16.admx and /dev/null differ
diff --git a/policy_templates/PolicyDefinitions/wwansvc.admx b/policy_templates/PolicyDefinitions/wwansvc.admx
deleted file mode 100644
index a868d71..0000000
--- a/policy_templates/PolicyDefinitions/wwansvc.admx
+++ /dev/null
@@ -1,120 +0,0 @@
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/AVSValidationGP.adml b/policy_templates/en-US/AVSValidationGP.adml
deleted file mode 100644
index 34eb5a2..0000000
--- a/policy_templates/en-US/AVSValidationGP.adml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
- Licensing Group Policy
- Licensing Group Policy
-
-
- Turn off KMS Client Online AVS Validation
-
- This policy setting lets you opt-out of sending KMS client activation data to Microsoft automatically. Enabling this setting prevents this computer from sending data to Microsoft regarding its activation state.
- If you disable or do not configure this policy setting, KMS client activation data will be sent to Microsoft services when this device activates.
- Policy Options:
- - Not Configured (default -- data will be automatically sent to Microsoft)
- - Disabled (data will be automatically sent to Microsoft)
- - Enabled (data will not be sent to Microsoft)
-
- Control Device Reactivation for Retail devices
-
- This policy setting controls whether OS Reactivation is blocked on a device.
- Policy Options:
- - Not Configured (default -- Windows registration and reactivation is allowed)
- - Disabled (Windows registration and reactivation is not allowed)
- - Enabled (Windows registration is allowed)
-
- Software Protection Platform
-
-
-
diff --git a/policy_templates/en-US/AccountNotifications.adml b/policy_templates/en-US/AccountNotifications.adml
deleted file mode 100644
index 3379d4c..0000000
--- a/policy_templates/en-US/AccountNotifications.adml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Account Notifications
- Turn off account notifications in Start
-
- This policy allows you to prevent Windows from displaying notifications to Microsoft account (MSA) and local users in Start (user tile).
-
- Notifications include getting users to: reauthenticate; backup their device; manage cloud storage quotas as well as manage their Microsoft 365 or XBOX subscription.
-
- If you enable this policy setting, Windows will not send account related notifications for local and MSA users to the user tile in Start.
-
- If you disable or do not configure this policy setting, Windows will send account related notifications for local and MSA users to the user tile in Start.
-
- No reboots or service restarts are required for this policy setting to take effect.
-
-
-
-
diff --git a/policy_templates/en-US/ActiveXInstallService.adml b/policy_templates/en-US/ActiveXInstallService.adml
deleted file mode 100644
index 5d11d23..0000000
--- a/policy_templates/en-US/ActiveXInstallService.adml
+++ /dev/null
@@ -1,77 +0,0 @@
-
-
-
- ActiveX Installer Service
- Installs ActiveX controls from approved installation sites
-
-
- ActiveX Installer Service
- Establish ActiveX installation policy for sites in Trusted zones
- This policy setting controls the installation of ActiveX controls for sites in Trusted zone.
-
-If you enable this policy setting, ActiveX controls are installed according to the settings defined by this policy setting.
-
-If you disable or do not configure this policy setting, ActiveX controls prompt the user before installation.
-
-If the trusted site uses the HTTPS protocol, this policy setting can also control how ActiveX Installer Service responds to certificate errors. By default all HTTPS connections must supply a server certificate that passes all validation criteria. If you are aware that a trusted site has a certificate error but you want to trust it anyway you can select the certificate errors that you want to ignore.
-
-Note: This policy setting applies to all sites in Trusted zones.
-
- Don't install
- Prompt the user
- Silently install
- Approved Installation Sites for ActiveX Controls
- This policy setting determines which ActiveX installation sites standard users in your organization can use to install ActiveX controls on their computers. When this setting is enabled, the administrator can create a list of approved Activex Install sites specified by host URL.
-
-If you enable this setting, the administrator can create a list of approved ActiveX Install sites specified by host URL.
-
-If you disable or do not configure this policy setting, ActiveX controls prompt the user for administrative credentials before installation.
-
-Note: Wild card characters cannot be used when specifying the host URLs.
-
-
-
-
- Installation Policy for ActiveX control signed by trusted publisher
- Installation Policy for signed ActiveX control
- Installation Policy for unsigned ActiveX control
- Permit connection to trusted sites with the following server certificate errors.
- Unknown certifcation authority (CA)
- Invalid certificate name (CN)
- Expired certificate validation date
- Wrong certificate usage
-
-
-
- Host URLs
- Contains policy for the host URL.
- For example
- HostName: http://activex.microsoft.com
- Value: 2,1,0,0
- The value for each Host URL is four settings in CSV format.
- Which represents "TPSSignedControl,SignedControl,UnsignedControl,ServerCertificatePolicy
- The three left most values in the policy control the installation of ActiveX controls based on their signature.
- They can be one of the following.
- 0: ActiveX control will not be installed
- 1: Prompt the user to install ActiveX control
- 2: ActiveX control will be silently installed
- Controls signed by certificates in trusted publisher store will be silently installed
- Silent installation for unsigned controls is not supported
-
- The right most value in the policy is a bitmasked flag
- The flags are used for ignoring https certificate errors.
- The default value is 0.
- Which means that the https connections must pass all security checks
-
- Use the combination of the following values
- to ignore invalid certificate errors
- 0x00000100 Ignore Unknown CA
- 0x00001000 Ignore invalid CN
- 0x00002000 Ignore invalid certificate date
- 0x00000200 Ignore wrong certificate usage
-
-
-
-
-
-
diff --git a/policy_templates/en-US/AddRemovePrograms.adml b/policy_templates/en-US/AddRemovePrograms.adml
deleted file mode 100644
index a805e8e..0000000
--- a/policy_templates/en-US/AddRemovePrograms.adml
+++ /dev/null
@@ -1,124 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Add or Remove Programs
- Specify default category for Add New Programs
- Specifies the category of programs that appears when users open the "Add New Programs" page.
-
-If you enable this setting, only the programs in the category you specify are displayed when the "Add New Programs" page opens. Users can use the Category box on the "Add New Programs" page to display programs in other categories.
-
-To use this setting, type the name of a category in the Category box for this setting. You must enter a category that is already defined in Add or Remove Programs. To define a category, use Software Installation.
-
-If you disable this setting or do not configure it, all programs (Category: All) are displayed when the "Add New Programs" page opens.
-
-You can use this setting to direct users to the programs they are most likely to need.
-
-Note: This setting is ignored if either the "Remove Add or Remove Programs" setting or the "Hide Add New Programs page" setting is enabled.
- Hide the "Add a program from CD-ROM or floppy disk" option
- Removes the "Add a program from CD-ROM or floppy disk" section from the Add New Programs page. This prevents users from using Add or Remove Programs to install programs from removable media.
-
-If you disable this setting or do not configure it, the "Add a program from CD-ROM or floppy disk" option is available to all users.
-
-This setting does not prevent users from using other tools and methods to add or remove program components.
-
-Note: If the "Hide Add New Programs page" setting is enabled, this setting is ignored. Also, if the "Prevent removable media source for any install" setting (located in User Configuration\Administrative Templates\Windows Components\Windows Installer) is enabled, users cannot add programs from removable media, regardless of this setting.
- Hide the "Add programs from Microsoft" option
- Removes the "Add programs from Microsoft" section from the Add New Programs page. This setting prevents users from using Add or Remove Programs to connect to Windows Update.
-
-If you disable this setting or do not configure it, "Add programs from Microsoft" is available to all users.
-
-This setting does not prevent users from using other tools and methods to connect to Windows Update.
-
-Note: If the "Hide Add New Programs page" setting is enabled, this setting is ignored.
- Hide the "Add programs from your network" option
- Prevents users from viewing or installing published programs.
-
-This setting removes the "Add programs from your network" section from the Add New Programs page. The "Add programs from your network" section lists published programs and provides an easy way to install them.
-
-Published programs are those programs that the system administrator has explicitly made available to the user with a tool such as Windows Installer. Typically, system administrators publish programs to notify users that the programs are available, to recommend their use, or to enable users to install them without having to search for installation files.
-
-If you enable this setting, users cannot tell which programs have been published by the system administrator, and they cannot use Add or Remove Programs to install published programs. However, they can still install programs by using other methods, and they can view and install assigned (partially installed) programs that are offered on the desktop or on the Start menu.
-
-If you disable this setting or do not configure it, "Add programs from your network" is available to all users.
-
-Note: If the "Hide Add New Programs page" setting is enabled, this setting is ignored.
- Hide Add New Programs page
- Removes the Add New Programs button from the Add or Remove Programs bar. As a result, users cannot view or change the attached page.
-
-The Add New Programs button lets users install programs published or assigned by a system administrator.
-
-If you disable this setting or do not configure it, the Add New Programs button is available to all users.
-
-This setting does not prevent users from using other tools and methods to install programs.
- Remove Add or Remove Programs
- Prevents users from using Add or Remove Programs.
-
-This setting removes Add or Remove Programs from Control Panel and removes the Add or Remove Programs item from menus.
-
-Add or Remove Programs lets users install, uninstall, repair, add, and remove features and components of Windows 2000 Professional and a wide variety of Windows programs. Programs published or assigned to the user appear in Add or Remove Programs.
-
-If you disable this setting or do not configure it, Add or Remove Programs is available to all users.
-
-When enabled, this setting takes precedence over the other settings in this folder.
-
-This setting does not prevent users from using other tools and methods to install or uninstall programs.
- Hide the Set Program Access and Defaults page
- Removes the Set Program Access and Defaults button from the Add or Remove Programs bar. As a result, users cannot view or change the associated page.
-
-The Set Program Access and Defaults button lets administrators specify default programs for certain activities, such as Web browsing or sending e-mail, as well as which programs are accessible from the Start menu, desktop, and other locations.
-
-If you disable this setting or do not configure it, the Set Program Access and Defaults button is available to all users.
-
-This setting does not prevent users from using other tools and methods to change program access or defaults.
-
-This setting does not prevent the Set Program Access and Defaults icon from appearing on the Start menu. See the "Remove Set Program Access and Defaults from Start menu" setting.
- Hide Change or Remove Programs page
- Removes the Change or Remove Programs button from the Add or Remove Programs bar. As a result, users cannot view or change the attached page.
-
-The Change or Remove Programs button lets users uninstall, repair, add, or remove features of installed programs.
-
-If you disable this setting or do not configure it, the Change or Remove Programs page is available to all users.
-
-This setting does not prevent users from using other tools and methods to delete or uninstall programs.
- Go directly to Components Wizard
- Prevents users from using Add or Remove Programs to configure installed services.
-
-This setting removes the "Set up services" section of the Add/Remove Windows Components page. The "Set up services" section lists system services that have not been configured and offers users easy access to the configuration tools.
-
-If you disable this setting or do not configure it, "Set up services" appears only when there are unconfigured system services. If you enable this setting, "Set up services" never appears.
-
-This setting does not prevent users from using other methods to configure services.
-
-Note: When "Set up services" does not appear, clicking the Add/Remove Windows Components button starts the Windows Component Wizard immediately. Because the only remaining option on the Add/Remove Windows Components page starts the wizard, that option is selected automatically, and the page is bypassed.
-
-To remove "Set up services" and prevent the Windows Component Wizard from starting, enable the "Hide Add/Remove Windows Components page" setting. If the "Hide Add/Remove Windows Components page" setting is enabled, this setting is ignored.
- Remove Support Information
- Removes links to the Support Info dialog box from programs on the Change or Remove Programs page.
-
-Programs listed on the Change or Remove Programs page can include a "Click here for support information" hyperlink. When clicked, the hyperlink opens a dialog box that displays troubleshooting information, including a link to the installation files and data that users need to obtain product support, such as the Product ID and version number of the program. The dialog box also includes a hyperlink to support information on the Internet, such as the Microsoft Product Support Services Web page.
-
-If you disable this setting or do not configure it, the Support Info hyperlink appears.
-
-Note: Not all programs provide a support information hyperlink.
- Hide Add/Remove Windows Components page
- Removes the Add/Remove Windows Components button from the Add or Remove Programs bar. As a result, users cannot view or change the associated page.
-
-The Add/Remove Windows Components button lets users configure installed services and use the Windows Component Wizard to add, remove, and configure components of Windows from the installation files.
-
-If you disable this setting or do not configure it, the Add/Remove Windows Components button is available to all users.
-
-This setting does not prevent users from using other tools and methods to configure services or add or remove program components. However, this setting blocks user access to the Windows Component Wizard.
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/AllowBuildPreview.adml b/policy_templates/en-US/AllowBuildPreview.adml
deleted file mode 100644
index 16514db..0000000
--- a/policy_templates/en-US/AllowBuildPreview.adml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Toggle user control over Insider builds
- This policy setting determines whether users can get preview builds of Windows, by configuring controls in Settings > Update and security > Windows Insider Program.
-
-If you enable or do not configure this policy setting, users can download and install preview builds of Windows by configuring Windows Insider Program settings.
-
-If you disable this policy setting, Windows Insider Program settings will be unavailable to users through the Settings app.
-
-This policy is only supported up to Windows 10, Version 1703. Please use 'Manage preview builds' under 'Windows Update for Business' for newer Windows 10 versions.
-
-
-
diff --git a/policy_templates/en-US/AppCompat.adml b/policy_templates/en-US/AppCompat.adml
deleted file mode 100644
index a39cd5e..0000000
--- a/policy_templates/en-US/AppCompat.adml
+++ /dev/null
@@ -1,92 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Application Compatibility
- Specifies whether to prevent the MS-DOS subsystem (ntvdm.exe) from running on this computer. This setting affects the launching of 16-bit applications in the operating system.
-
-You can use this setting to turn off the MS-DOS subsystem, which will reduce resource usage and prevent users from running 16-bit applications. To run any 16-bit application or any application with 16-bit components, ntvdm.exe must be allowed to run. The MS-DOS subsystem starts when the first 16-bit application is launched. While the MS-DOS subsystem is running, any subsequent 16-bit applications launch faster, but overall resource usage on the system is increased.
-
-If the status is set to Enabled, the MS-DOS subsystem is prevented from running, which then prevents any 16-bit applications from running. In addition, any 32-bit applications with 16-bit installers or other 16-bit components cannot run.
-
-If the status is set to Disabled, the MS-DOS subsystem runs for all users on this computer.
-
-If the status is set to Not Configured, the OS falls back on a local policy set by the registry DWORD value HKLM\System\CurrentControlSet\Control\WOW\DisallowedPolicyDefault. If that value is non-0, this prevents all 16-bit applications from running. If that value is 0, 16-bit applications are allowed to run. If that value is also not present, on Windows 10 and above the OS will launch the 16-bit application support control panel to allow an elevated administrator to make the decision; on windows 7 and downlevel, the OS will allow 16-bit applications to run.
-
-Note: This setting appears in only Computer Configuration.
- This policy controls the visibility of the Program Compatibility property page shell extension. This shell extension is visible on the property context-menu of any program shortcut or executable file.
-
-The compatibility property page displays a list of options that can be selected and applied to the application to resolve the most common issues affecting legacy applications. Enabling this policy setting removes the property page from the context-menus, but does not affect previous compatibility settings applied to application using this interface.
- The policy controls the state of the Application Telemetry engine in the system.
-
-Application Telemetry is a mechanism that tracks anonymous usage of specific Windows system components by applications.
-
-Turning Application Telemetry off by selecting "enable" will stop the collection of usage data.
-
-If the customer Experience Improvement program is turned off, Application Telemetry will be turned off regardless of how this policy is set.
-
-Disabling telemetry will take effect on any newly launched applications. To ensure that telemetry collection has stopped for all applications, please reboot your machine.
- This policy controls the state of the application compatibility engine in the system.
-
-The engine is part of the loader and looks through a compatibility database every time an application is started on the system. If a match for the application is found it provides either run-time solutions or compatibility fixes, or displays an Application Help message if the application has a know problem.
-
-Turning off the application compatibility engine will boost system performance. However, this will degrade the compatibility of many popular legacy applications, and will not block known incompatible applications from installing. (For Instance: This may result in a blue screen if an old anti-virus application is installed.)
-
-The Windows Resource Protection and User Account Control features of Windows use the application compatibility engine to provide mitigations for application problems. If the engine is turned off, these mitigations will not be applied to applications and their installers and these applications may fail to install or run properly.
-
-This option is useful to server administrators who require faster performance and are aware of the compatibility of the applications they are using. It is particularly useful for a web server where applications may be launched several hundred times a second, and the performance of the loader is essential.
-
-NOTE: Many system processes cache the value of this setting for performance reasons. If you make changes to this setting, please reboot to ensure that your system accurately reflects those changes.
- This policy setting controls the state of the Program Compatibility Assistant (PCA).
-
-The PCA monitors applications run by the user. When a potential compatibility issue with an application is detected, the PCA will prompt the user with recommended solutions. To configure the diagnostic settings for the PCA, go to System->Troubleshooting and Diagnostics->Application Compatibility Diagnostics.
-
-If you enable this policy setting, the PCA will be turned off. The user will not be presented with solutions to known compatibility issues when running applications. Turning off the PCA can be useful for system administrators who require better performance and are already aware of application compatibility issues.
-
-If you disable or do not configure this policy setting, the PCA will be turned on. To configure the diagnostic settings for the PCA, go to System->Troubleshooting and Diagnostics->Application Compatibility Diagnostics.
-
-Note: The Diagnostic Policy Service (DPS) and Program Compatibility Assistant Service must be running for the PCA to run. These services can be configured by using the Services snap-in to the Microsoft Management Console.
- This setting exists only for backward compatibility, and is not valid for this version of Windows. To configure the Program Compatibility Assistant, use the 'Turn off Program Compatibility Assistant' setting under Computer Configuration\Administrative Templates\Windows Components\Application Compatibility.
- This policy setting controls the state of Steps Recorder.
-
-Steps Recorder keeps a record of steps taken by the user. The data generated by Steps Recorder can be used in feedback systems such as Windows Error Reporting to help developers understand and fix problems. The data includes user actions such as keyboard input and mouse input, user interface data, and screen shots. Steps Recorder includes an option to turn on and off data collection.
-
-If you enable this policy setting, Steps Recorder will be disabled.
-
-If you disable or do not configure this policy setting, Steps Recorder will be enabled.
- The policy controls the state of the Switchback compatibility engine in the system.
-
-Switchback is a mechanism that provides generic compatibility mitigations to older applications by providing older behavior to old applications and new behavior to new applications.
-
-Switchback is on by default.
-
-If you enable this policy setting, Switchback will be turned off. Turning Switchback off may degrade the compatibility of older applications. This option is useful for server administrators who require performance and are aware of compatibility of the applications they are using.
-
-If you disable or do not configure this policy setting, the Switchback will be turned on.
-
-Please reboot the system after changing the setting to ensure that your system accurately reflects those changes.
- This policy setting controls the state of the Inventory Collector.
-
-The Inventory Collector inventories applications, files, devices, and drivers on the system and sends the information to Microsoft. This information is used to help diagnose compatibility problems.
-
-If you enable this policy setting, the Inventory Collector will be turned off and data will not be sent to Microsoft. Collection of installation data through the Program Compatibility Assistant is also disabled.
-
-If you disable or do not configure this policy setting, the Inventory Collector will be turned on.
-
-Note: This policy setting has no effect if the Customer Experience Improvement Program is turned off. The Inventory Collector will be off.
-
- Prevent access to 16-bit applications
- Prevent access to 16-bit applications
- Remove Program Compatibility Property Page
- Turn off Application Telemetry
- Turn off Application Compatibility Engine
- Turn off Program Compatibility Assistant
- Turn off SwitchBack Compatibility Engine
- Turn off Steps Recorder
- Turn off Inventory Collector
-
-
-
diff --git a/policy_templates/en-US/AppHVSI.adml b/policy_templates/en-US/AppHVSI.adml
deleted file mode 100644
index 4776e10..0000000
--- a/policy_templates/en-US/AppHVSI.adml
+++ /dev/null
@@ -1,169 +0,0 @@
-
-
-
- Microsoft Defender Application Guard
- Turn on Microsoft Defender Application Guard in Managed Mode
-
-
- Microsoft Defender Application Guard
- Turn on Microsoft Defender Application Guard in Managed Mode
- This policy setting enables application isolation through Microsoft Defender Application Guard.
-
-Application Guard uses Windows Hypervisor to create a virtualized environment for apps that are configured to use virtualization-based security isolation. While in isolation, improper user interactions and app vulnerabilities can’t compromise the kernel or any other apps running outside of the virtualized environment.
-
-If you enable this setting, Application Guard is turned on for your organization.
-
- Configure Microsoft Defender Application Guard clipboard settings
- This policy setting allows you to decide how the clipboard behaves while in Microsoft Defender Application Guard.
-
-If you enable this setting, you must choose from the following behaviors:
-
-- Disable clipboard functionality completely between the host and Application Guard
-
-- Enable the clipboard to copy content from Application Guard to the host
-
-- Enable the clipboard to copy content from the host to Application Guard.
-
-Note:
-We recommend that you don't enable copying from the host to Application Guard. If you enable this functionality, a potentially compromised Application Guard session will have access to the host device’s clipboard and its content.
-
-If you choose to enable copying, you must also choose the type of content that can be copied, by using the content options:
-
-- 1. Allows text copying.
-
-- 2. Allows image copying.
-
-- 3. Allows both text and image copying.
-
-If you disable or don't configure this setting, all clipboard functionality is turned off in Application Guard.
-
- Block clipboard operations(default)
- Enable clipboard operation from an isolated session to the host
- Enable clipboard operation from an host to the isolated session
- Enable clipboard operation both directions
- Configure Microsoft Defender Application Guard print settings
- This policy setting allows you to decide how the print functionality behaves while in Microsoft Defender Application Guard.
-
-If you enable this setting, you must choose one or many of the following behaviors:
-
-- Disable all print functionality in Application Guard.
-
-- Enable printing to existing network printers.
-
-- Enable printing to local printers.
-
-- Enable printing to PDF, allows people to print as PDF and save the resulting file on the host.
-
-- Enable printing to XPS, allows people to print as XPS and save the resulting file on the host.
-
-If you disable or don't configure this setting, all print functionality is turned off in Application Guard.
-
-
- Allow Microsoft Defender Application Guard to use Root Certificate Authorities from the user’s device
- This policy setting allows certain device level Root Certificates to be shared with the Microsoft Defender Application Guard container.
-
-If you enable this setting, certificates with a thumbprint matching the ones specified will be transferred into the container. Multiple certificates can be specified by using a comma to separate the thumbprints for each certificate you want to transfer.
-
-If you disable or don’t configure this setting, certificates are not shared with the Microsoft Defender Application Guard container.
-
-Example: b4e72779a8a362c860c36a6461f31e3aa7e58c14,1b1d49f06d2a697a544a1059bd59a7b058cda924
-
-
- Prevent enterprise websites from loading non-enterprise content in Microsoft Edge and Internet Explorer
- This policy setting allows you to decide whether websites can load non-enterprise content in Microsoft Edge and Internet Explorer.
-
-If you enable this setting, non-enterprise content embedded on enterprise sites are stopped from opening in Internet Explorer or Microsoft Edge outside of Microsoft Defender Application Guard.
-
-If you disable or don't configure this setting, non-enterprise sites can open outside of the Microsoft Defender Application Guard container, directly in Internet Explorer and Microsoft Edge.
-
- Allow camera and microphone access in Microsoft Defender Application Guard
- The policy allows you to determine whether applications inside Microsoft Defender Application Guard can access the device’s camera and microphone when these settings are enabled on the user’s device.
-
-If you enable this policy, applications inside Microsoft Defender Application Guard will be able to access the camera and microphone on the user’s device.
-
-If you disable or don't configure this policy, applications inside Microsoft Defender Application Guard will be unable to access the camera and microphone on the user’s device.
-
-Important: If you turn on this policy, a compromised container could bypass camera and microphone permissions and access the camera and microphone without the user’s knowledge. To prevent unauthorized access, we recommend that camera and microphone privacy settings be turned off on the user’s device when they are not needed.
-
- Allow data persistence for Microsoft Defender Application Guard
- This policy setting allows you to decide whether data should persist across different sessions in Microsoft Defender Application Guard.
-
-If you enable this setting, Application Guard saves user-downloaded files and other items (such as, cookies, Favorites, and so on) for use in future Application Guard sessions.
-
-Note:
-If you enable this setting, you can still delete a user's data from a specific device using the Reset-ApplicationGuard PowerShell command. Running this command deletes all employee data, regardless of configuration, and can result in data loss for the employee.
-
-If you disable or don't configure this setting, Application Guard deletes all user data within the Application Guard container.
-
- Allow hardware-accelerated rendering for Microsoft Defender Application Guard
- This policy setting determines whether Microsoft Defender Application Guard renders graphics using hardware or software acceleration.
-
-If you enable this setting, Microsoft Defender Application Guard uses Hyper-V to access supported, high-security rendering graphics hardware (GPUs). These GPUs improve rendering performance and battery life while using Microsoft Defender Application Guard, particularly for video playback and other graphics-intensive use cases. If you enable this setting without connecting any high-security rendering graphics hardware, Microsoft Defender Application Guard will automatically revert to software-based (CPU) rendering.
-
-Note:
-Be aware that enabling this setting with potentially compromised graphics devices or drivers might pose a risk to the host device.
-
-If you disable or don’t configure this setting, Microsoft Defender Application Guard uses software-based (CPU) rendering and won’t load any third-party graphics drivers or interact with any connected graphics hardware.
-
- Allow auditing events in Microsoft Defender Application Guard
- This policy setting allows you to decide whether auditing events can be collected from Microsoft Defender Application Guard.
-
-If you enable this setting, Application Guard inherits auditing policies from your device and logs system events from the Application Guard container to your host.
-
-If you disable or don't configure this setting, event logs aren't collected from your Application Guard container.
-
-
- Allow files to download and save to the host operating system from Microsoft Defender Application Guard
- This policy setting determines whether to save downloaded files to the host operating system from the Microsoft Defender Application Guard container.
-
-If you enable this setting, people can save downloaded files from the Microsoft Defender Application Guard container to the host operating system.
-
-If you disable or don't configure this setting, people can't save downloaded files from the Microsoft Defender Application Guard container to the host operating system.
-
-
-
-
-
-
-Options:
-0. Disable Microsoft Defender Application Guard
-1. Enable Microsoft Defender Application Guard for Microsoft Edge ONLY
-2. Enable Microsoft Defender Application Guard for isolated Windows environments ONLY
-3. Enable Microsoft Defender Application Guard for Microsoft Edge AND isolated Windows environments
-
-
-
- Clipboard behavior setting.
- Clipboard content options.
-
-
-
- Allowed print types in Application Guard.
-
- To determine which types of printing to allow, you must choose:
- - 0. Disables all print functionality.
- - 1. Enables only XPS printing.
- - 2. Enables only PDF printing.
- - 3. Enables both PDF and XPS printing.
- - 4. Enables only local printing.
- - 5. Enables both local and XPS printing.
- - 6. Enables both local and PDF printing.
- - 7. Enables local, PDF, and XPS printing.
- - 8. Enables only network printing.
- - 9. Enables both network and XPS printing.
- - 10. Enables both network and PDF printing.
- - 11. Enables network, PDF, and XPS printing.
- - 12. Enables both network and local printing.
- - 13. Enables network, local, and XPS printing.
- - 14. Enables network, local, and PDF printing.
- - 15. Enables all printing.
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/AppPrivacy.adml b/policy_templates/en-US/AppPrivacy.adml
deleted file mode 100644
index 41c3e74..0000000
--- a/policy_templates/en-US/AppPrivacy.adml
+++ /dev/null
@@ -1,601 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- App Privacy
- User is in control
- Force Allow
- Force Deny
- Let Windows apps access account information
- This policy setting specifies whether Windows apps can access account information.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access account information by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access account information and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access account information and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access account information by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access the calendar
- This policy setting specifies whether Windows apps can access the calendar.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access the calendar by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access the calendar and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access the calendar and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access the calendar by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access call history
- This policy setting specifies whether Windows apps can access call history.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access call history by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access the call history and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access the call history and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access the call history by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access the camera
- This policy setting specifies whether Windows apps can access the camera.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access the camera by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access the camera and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access the camera and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access the camera by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access contacts
- This policy setting specifies whether Windows apps can access contacts.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access contacts by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access contacts and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access contacts and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access contacts by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access email
- This policy setting specifies whether Windows apps can access email.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access email by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access email and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access email and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access email by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps take screenshots of various windows or displays
- This policy setting specifies whether Windows apps can take screenshots of various windows or displays.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can take screenshots of various windows or displays by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to take screenshots of various windows or displays and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to take screenshots of various windows or displays and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can take screenshots of various windows or displays by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps turn off the screenshot border
- This policy setting specifies whether Windows apps can turn off the screenshot border.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can turn off the screenshot border by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to turn off the screenshot border and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to turn off the screenshot border and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can turn off the screenshot border by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access presence sensing
- This policy setting specifies whether Windows apps can access presence sensing.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access presence sensing and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access presence sensing and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access presence sensing by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access location
- This policy setting specifies whether Windows apps can access location.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access location by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access location and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access location and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access location by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access messaging
- This policy setting specifies whether Windows apps can read or send messages (text or MMS).
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can read or send messages by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps can read or send messages and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps cannot read or send messages and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can read or send messages by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access the microphone
- This policy setting specifies whether Windows apps can access the microphone.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access the microphone by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access the microphone and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access the microphone and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access the microphone by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access motion
- This policy setting specifies whether Windows apps can access motion data.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access motion data by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access motion data and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access motion data and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access motion data by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access notifications
- This policy setting specifies whether Windows apps can access notifications.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access notifications by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access notifications and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access notifications and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access notifications by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps make phone calls
- This policy setting specifies whether Windows apps can make phone calls.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can make phone calls by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to make phone calls and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to make phone calls and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can make phone calls by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps control radios
- This policy setting specifies whether Windows apps have access to control radios.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps have access to control radios by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps will have access to control radios and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps will not have access to control radios and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps have access to control radios by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps communicate with unpaired devices
- This policy setting specifies whether Windows apps can communicate with unpaired wireless devices.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can communicate with unpaired wireless devices by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to communicate with unpaired wireless devices and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to communicate with unpaired wireless devices and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can communicate with unpaired wireless devices by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access Tasks
- This policy setting specifies whether Windows apps can access tasks.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access tasks by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access tasks and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access tasks and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access tasks by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access trusted devices
- This policy setting specifies whether Windows apps can access trusted devices.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access trusted devices by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access trusted devices and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access trusted devices and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access trusted devices by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps run in the background
- This policy setting specifies whether Windows apps can run in the background.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can run in the background by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to run in the background and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to run in the background and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can run in the background by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access diagnostic information about other apps
- This policy setting specifies whether Windows apps can get diagnostic information about other Windows apps, including user name.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can get diagnostic information about other apps using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to get diagnostic information about other apps and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to get diagnostic information about other apps and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can get diagnostic information about other apps by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps access an eye tracker device
- This policy setting specifies whether Windows apps can access the eye tracker.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access the eye tracker by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access the eye tracker and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access the eye tracker and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access the eye tracker by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
- Let Windows apps activate with voice
- This policy setting specifies whether Windows apps can be activated by voice.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can be activated with a voice keyword by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to be activated with a voice keyword and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to be activated with a voice keyword and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can be activated with a voice keyword by using Settings > Privacy on the device.
-
-This policy is applied to Windows apps and Cortana.
-
- Let Windows apps activate with voice while the system is locked
-
-This policy setting specifies whether Windows apps can be activated by voice while the system is locked.
-
-If you choose the "User is in control" option, employees in your organization can decide whether users can interact with applications using speech while the system is locked by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, users can interact with applications using speech while the system is locked and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, users cannot interact with applications using speech while the system is locked and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether users can interact with applications using speech while the system is locked by using Settings > Privacy on the device.
-
-This policy is applied to Windows apps and Cortana. It takes precedence of the “Allow Cortana above lock” policy. This policy is applicable only when “Allow voice activation” policy is configured to allow applications to be activated with voice.
-
- Let Windows apps access user movements while running in the background
- This policy setting specifies whether Windows apps can access the movement of the user's head, hands, motion controllers, and other tracked objects, while the apps are running in the background.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access the user's movements while the apps are running in the background by using Settings > Privacy on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access user movements while the apps are running in the background and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access user movements while the apps are running in the background and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access the user's movements while the apps are running in the background by using Settings > Privacy on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
- Default for all apps:
-
-
- Default for all apps:
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
-
-
diff --git a/policy_templates/en-US/AppXRuntime.adml b/policy_templates/en-US/AppXRuntime.adml
deleted file mode 100644
index 60fc503..0000000
--- a/policy_templates/en-US/AppXRuntime.adml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- App runtime
- App runtime policies
-
-
- App runtime
- Contains settings to manage the behavior of Windows Store apps.
- Block launching desktop apps associated with a file.
- This policy setting lets you control whether Windows Store apps can open files using the default desktop app for a file type. Because desktop apps run at a higher integrity level than Windows Store apps, there is a risk that a Windows Store app might compromise the system by opening a file in the default desktop app for a file type.
-
-If you enable this policy setting, Windows Store apps cannot open files in the default desktop app for a file type; they can open files only in other Windows Store apps.
-
-If you disable or do not configure this policy setting, Windows Store apps can open files in the default desktop app for a file type.
- Block launching desktop apps associated with a URI scheme
- This policy setting lets you control whether Windows Store apps can open URIs using the default desktop app for a URI scheme. Because desktop apps run at a higher integrity level than Windows Store apps, there is a risk that a URI scheme launched by a Windows Store app might compromise the system by launching a desktop app.
-
-If you enable this policy setting, Windows Store apps cannot open URIs in the default desktop app for a URI scheme; they can open URIs only in other Windows Store apps.
-
-If you disable or do not configure this policy setting, Windows Store apps can open URIs in the default desktop app for a URI scheme.
-
-Note: Enabling this policy setting does not block Windows Store apps from opening the default desktop app for the http, https, and mailto URI schemes. The handlers for these URI schemes are hardened against URI-based vulnerabilities from untrusted sources, reducing the associated risk.
- Turn on dynamic Content URI Rules for Windows store apps
- This policy setting lets you turn on Content URI Rules to supplement the static Content URI Rules that were defined as part of the app manifest and apply to all Windows Store apps that use the enterpriseAuthentication capability on a computer.
-
-If you enable this policy setting, you can define additional Content URI Rules that all Windows Store apps that use the enterpriseAuthentication capability on a computer can use.
-
-If you disable or don't set this policy setting, Windows Store apps will only use the static Content URI Rules.
- Allow Microsoft accounts to be optional
- This policy setting lets you control whether Microsoft accounts are optional for Windows Store apps that require an account to sign in. This policy only affects Windows Store apps that support it.
-
-If you enable this policy setting, Windows Store apps that typically require a Microsoft account to sign in will allow users to sign in with an enterprise account instead.
-
-If you disable or do not configure this policy setting, users will need to sign in with a Microsoft account.
- Block launching Universal Windows apps with Windows Runtime API access from hosted content.
-
- This policy setting controls whether Universal Windows apps with Windows Runtime API access directly from web content can be launched.
-
- If you enable this policy setting, Universal Windows apps which declare Windows Runtime API access in ApplicationContentUriRules section of the manifest cannot be launched; Universal Windows apps which have not declared Windows Runtime API access in the manifest are not affected.
-
- If you disable or do not configure this policy setting, all Universal Windows apps can be launched.
-
- This policy should not be enabled unless recommended by Microsoft as a security response because it can cause severe app compatibility issues.
-
-
-
-
- To turn on dynamic Content URI Rules, click Show, and then type the Content URI Rules in the list.
- Content URI Rules:
- Only https:// URIs are supported.
-
-
-
-
diff --git a/policy_templates/en-US/AppxPackageManager.adml b/policy_templates/en-US/AppxPackageManager.adml
deleted file mode 100644
index 02732a6..0000000
--- a/policy_templates/en-US/AppxPackageManager.adml
+++ /dev/null
@@ -1,97 +0,0 @@
-
-
-
-
- Appx Package Manager
- Appx Package Manager
-
-
- App Package Deployment
- Allow all trusted apps to install
- This policy setting allows you to manage the installation of trusted line-of-business (LOB) or developer-signed Windows Store apps.
-
-If you enable this policy setting, you can install any LOB or developer-signed Windows Store app (which must be signed with a certificate chain that can be successfully validated by the local computer).
-
-If you disable or do not configure this policy setting, you cannot install LOB or developer-signed Windows Store apps.
- Archive infrequently used apps
- This policy setting controls whether the system can archive infrequently used apps.
-
-If you enable this policy setting, then the system will periodically check for and archive infrequently used apps.
-
-If you disable this policy setting, then the system will not archive any apps.
-
-If you do not configure this policy setting (default), then the system will follow default behavior, which is to periodically check for and archive infrequently used apps, and the user will be able to configure this setting themselves.
- Allow deployment operations in special profiles
- This policy setting allows you to manage the deployment of Windows Store apps when the user is signed in using a special profile. Special profiles are the following user profiles, where changes are discarded after the user signs off:
-
-Roaming user profiles to which the "Delete cached copies of roaming profiles" Group Policy setting applies
-
-Mandatory user profiles and super-mandatory profiles, which are created by an administrator
-
-Temporary user profiles, which are created when an error prevents the correct profile from loading
-
-User profiles for the Guest account and members of the Guests group
-
-
-If you enable this policy setting, Group Policy allows deployment operations (adding, registering, staging, updating, or removing an app package) of Windows Store apps when using a special profile.
-
-If you disable or do not configure this policy setting, Group Policy blocks deployment operations of Windows Store apps when using a special profile.
- Allows development of Windows Store apps and installing them from an integrated development environment (IDE)
-
- Allows or denies development of Microsoft Store applications and installing them directly from an IDE.
-
- If you enable this setting and enable the "Allow all trusted apps to install" Group Policy, you can develop Microsoft Store apps and install them directly from an IDE.
-
- If you disable or do not configure this setting, you cannot develop Microsoft Store apps or install them directly from an IDE.
-
- Disable installing Windows apps on non-system volumes
-
- This policy setting allows you to manage installing Windows apps on additional volumes such as secondary partitions, USB drives, or SD cards.
-
- If you enable this setting, you can't move or install Windows apps on volumes that are not the system volume.
-
- If you disable or do not configure this setting, you can move or install Windows apps on other volumes.
-
- Prevent users' app data from being stored on non-system volumes
-
- Prevent users' app data from moving to another location when an app is moved or installed on another location.
-
- If you enable this setting, all users' app data will stay on the system volume, regardless of where the app is installed.
-
- If you disable or do not configure this setting, then when an app is moved to a different volume, the users' app data will also move to this volume.
-
- Allow a Windows app to share application data between users
- Manages a Windows app's ability to share data between users who have installed the app.
-
- If you enable this policy, a Windows app can share app data with other instances of that app. Data is shared through the SharedLocal folder. This folder is available through the Windows.Storage API.
-
- If you disable this policy, a Windows app can't share app data with other instances of that app. If this policy was previously enabled, any previously shared app data will remain in the SharedLocal folder.
-
- Prevent non-admin users from installing packaged Windows apps
- Manages non-Administrator users' ability to install Windows app packages.
-
- If you enable this policy, non-Administrators will be unable to initiate installation of Windows app packages. Administrators who wish to install an app will need to do so from an Administrator context (for example, an Administrator PowerShell window). All users will still be able to install Windows app packages via the Microsoft Store, if permitted by other policies.
-
- If you disable or do not configure this policy, all users will be able to initiate installation of Windows app packages.
-
- Not allow sideloaded apps to auto-update in the background
- Manages a sideloaded apps' ability to auto-update in the background.
-
- If you enable this policy, sideloaded apps will not auto-update in the background.
-
- If you disable this policy, sideloaded apps will auto-update in the background.
-
- Default is 'disabled' (key not present).
-
- Not allow sideloaded apps to auto-update in the background on a metered network
- Manages a sideloaded apps' ability to auto-update in the background on a metered network.
-
- If you enable this policy, sideloaded apps will not auto-update in the background on a metered network.
-
- If you disable this policy, sideloaded apps will auto-update in the background on a metered network.
-
- Default is 'disabled' (key not present).
-
-
-
-
diff --git a/policy_templates/en-US/AttachmentManager.adml b/policy_templates/en-US/AttachmentManager.adml
deleted file mode 100644
index a58d60d..0000000
--- a/policy_templates/en-US/AttachmentManager.adml
+++ /dev/null
@@ -1,116 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Attachment Manager
- Notify antivirus programs when opening attachments
- Trust logic for file attachments
- This policy setting allows you to manage the behavior for notifying registered antivirus programs. If multiple programs are registered, they will all be notified. If the registered antivirus program already performs on-access checks or scans files as they arrive on the computer's email server, additional calls would be redundant.
-
-If you enable this policy setting, Windows tells the registered antivirus program to scan the file when a user opens a file attachment. If the antivirus program fails, the attachment is blocked from being opened.
-
-If you disable this policy setting, Windows does not call the registered antivirus programs when file attachments are opened.
-
-If you do not configure this policy setting, Windows does not call the registered antivirus programs when file attachments are opened.
- This policy setting allows you to configure the logic that Windows uses to determine the risk for file attachments.
-
-Preferring the file handler instructs Windows to use the file handler data over the file type data. For example, trust notepad.exe, but don't trust .txt files.
-
-Preferring the file type instructs Windows to use the file type data over the file handler data. For example, trust .txt files, regardless of the file handler.
-
-Using both the file handler and type data is the most restrictive option. Windows chooses the more restrictive recommendation which will cause users to see more trust prompts than choosing the other options.
-
-If you enable this policy setting, you can choose the order in which Windows processes risk assessment data.
-
-If you disable this policy setting, Windows uses its default trust logic, which prefers the file handler over the file type.
-
-If you do not configure this policy setting, Windows uses its default trust logic, which prefers the file handler over the file type.
- This policy setting allows you to manage whether Windows marks file attachments with information about their zone of origin (such as restricted, Internet, intranet, local). This requires NTFS in order to function correctly, and will fail without notice on FAT32. By not preserving the zone information, Windows cannot make proper risk assessments.
-
-If you enable this policy setting, Windows does not mark file attachments with their zone information.
-
-If you disable this policy setting, Windows marks file attachments with their zone information.
-
-If you do not configure this policy setting, Windows marks file attachments with their zone information.
- This policy setting allows you to manage whether users can manually remove the zone information from saved file attachments by clicking the Unblock button in the file's property sheet or by using a check box in the security warning dialog. Removing the zone information allows users to open potentially dangerous file attachments that Windows has blocked users from opening.
-
-If you enable this policy setting, Windows hides the check box and Unblock button.
-
-If you disable this policy setting, Windows shows the check box and Unblock button.
-
-If you do not configure this policy setting, Windows hides the check box and Unblock button.
- This policy setting allows you to manage the default risk level for file types. To fully customize the risk level for file attachments, you may also need to configure the trust logic for file attachments.
-
-High Risk: If the attachment is in the list of high-risk file types and is from the restricted zone, Windows blocks the user from accessing the file. If the file is from the Internet zone, Windows prompts the user before accessing the file.
-
-Moderate Risk: If the attachment is in the list of moderate-risk file types and is from the restricted or Internet zone, Windows prompts the user before accessing the file.
-
-Low Risk: If the attachment is in the list of low-risk file types, Windows will not prompt the user before accessing the file, regardless of the file's zone information.
-
-If you enable this policy setting, you can specify the default risk level for file types.
-
-If you disable this policy setting, Windows sets the default risk level to moderate.
-
-If you do not configure this policy setting, Windows sets the default risk level to moderate.
- This policy setting allows you to configure the list of high-risk file types. If the file attachment is in the list of high-risk file types and is from the restricted zone, Windows blocks the user from accessing the file. If the file is from the Internet zone, Windows prompts the user before accessing the file. This inclusion list takes precedence over the medium-risk and low-risk inclusion lists (where an extension is listed in more than one inclusion list).
-
-If you enable this policy setting, you can create a custom list of high-risk file types.
-
-If you disable this policy setting, Windows uses its built-in list of file types that pose a high risk.
-
-If you do not configure this policy setting, Windows uses its built-in list of high-risk file types.
- This policy setting allows you to configure the list of low-risk file types. If the attachment is in the list of low-risk file types, Windows will not prompt the user before accessing the file, regardless of the file's zone information. This inclusion list overrides the list of high-risk file types built into Windows and has a lower precedence than the high-risk or medium-risk inclusion lists (where an extension is listed in more than one inclusion list).
-
-If you enable this policy setting, you can specify file types that pose a low risk.
-
-If you disable this policy setting, Windows uses its default trust logic.
-
-If you do not configure this policy setting, Windows uses its default trust logic.
- This policy setting allows you to configure the list of moderate-risk file types. If the attachment is in the list of moderate-risk file types and is from the restricted or Internet zone, Windows prompts the user before accessing the file. This inclusion list overrides the list of potentially high-risk file types built into Windows and it takes precedence over the low-risk inclusion list but has a lower precedence than the high-risk inclusion list (where an extension is listed in more than one inclusion list).
-
-If you enable this policy setting, you can specify file types which pose a moderate risk.
-
-If you disable this policy setting, Windows uses its default trust logic.
-
-If you do not configure this policy setting, Windows uses its default trust logic.
- Preferring the file handler
- Preferring the file type
- Looking at the file handler and type
- High Risk
- Low Risk
- Do not preserve zone information in file attachments
- Moderate Risk
- Hide mechanisms to remove zone information
- Default risk level for file attachments
- Inclusion list for high risk file types
- Inclusion list for low file types
- Inclusion list for moderate risk file types
-
-
-
- Determine risk by
-
-
- Set the default risk level
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/AuditSettings.adml b/policy_templates/en-US/AuditSettings.adml
deleted file mode 100644
index 7a102ee..0000000
--- a/policy_templates/en-US/AuditSettings.adml
+++ /dev/null
@@ -1,26 +0,0 @@
-
-
-
- Audit Process Creation
- Configuration settings for auditing process creation.
-
-
- Audit Process Creation
- Include command line in process creation events
- This policy setting determines what information is logged in security audit events when a new process has been created.
-
-This setting only applies when the Audit Process Creation policy is enabled. If you enable this policy setting the command line information for every process will be logged in plain text in the security event log as part of the Audit Process Creation event 4688, "a new process has been created," on the workstations and servers on which this policy setting is applied.
-
-If you disable or do not configure this policy setting, the process's command line information will not be included in Audit Process Creation events.
-
-Default: Not configured
-
-Note: When this policy setting is enabled, any user with access to read the security events will be able to read the command line arguments for any successfully created process. Command line arguments can contain sensitive or private information such as passwords or user data.
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/AutoPlay.adml b/policy_templates/en-US/AutoPlay.adml
deleted file mode 100644
index f457699..0000000
--- a/policy_templates/en-US/AutoPlay.adml
+++ /dev/null
@@ -1,67 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- AutoPlay Policies
- Configure various AutoPlay behaviors.
- Set the default behavior for AutoRun
- This policy setting sets the default behavior for Autorun commands.
-
- Autorun commands are generally stored in autorun.inf files. They often launch the installation program or other routines.
-
- Prior to Windows Vista, when media containing an autorun command is inserted, the system will automatically execute the program without user intervention.
-
- This creates a major security concern as code may be executed without user's knowledge. The default behavior starting with Windows Vista is to prompt the user whether autorun command is to be run. The autorun command is represented as a handler in the Autoplay dialog.
-
- If you enable this policy setting, an Administrator can change the default Windows Vista or later behavior for autorun to:
-
- a) Completely disable autorun commands, or
- b) Revert back to pre-Windows Vista behavior of automatically executing the autorun command.
-
- If you disable or not configure this policy setting, Windows Vista or later will prompt the user whether autorun command is to be run.
- Do not execute any autorun commands
- Automatically execute autorun commands
- Prevent AutoPlay from remembering user choices.
- This policy setting allows you to prevent AutoPlay from remembering user's choice of what to do when a device is connected.
-
- If you enable this policy setting, AutoPlay prompts the user to choose what to do when a device is connected.
-
- If you disable or do not configure this policy setting, AutoPlay remembers user's choice of what to do when a device is connected.
- Disallow Autoplay for non-volume devices
- This policy setting disallows AutoPlay for MTP devices like cameras or phones.
-
- If you enable this policy setting, AutoPlay is not allowed for MTP devices like cameras or phones.
-
- If you disable or do not configure this policy setting, AutoPlay is enabled for non-volume devices.
- Turn off Autoplay
- This policy setting allows you to turn off the Autoplay feature.
-
- Autoplay begins reading from a drive as soon as you insert media in the drive. As a result, the setup file of programs and the music on audio media start immediately.
-
- Prior to Windows XP SP2, Autoplay is disabled by default on removable drives, such as the floppy disk drive (but not the CD-ROM drive), and on network drives.
-
- Starting with Windows XP SP2, Autoplay is enabled for removable drives as well, including Zip drives and some USB mass storage devices.
-
- If you enable this policy setting, Autoplay is disabled on CD-ROM and removable media drives, or disabled on all drives.
-
- This policy setting disables Autoplay on additional types of drives. You cannot use this setting to enable Autoplay on drives on which it is disabled by default.
-
- If you disable or do not configure this policy setting, AutoPlay is enabled.
-
- Note: This policy setting appears in both the Computer Configuration and User Configuration folders. If the policy settings conflict, the policy setting in Computer Configuration takes precedence over the policy setting in User Configuration.
- CD-ROM and removable media drives
- All drives
-
-
-
- Default AutoRun Behavior
-
-
- Turn off Autoplay on:
-
-
-
-
diff --git a/policy_templates/en-US/Biometrics.adml b/policy_templates/en-US/Biometrics.adml
deleted file mode 100644
index cfe8b3c..0000000
--- a/policy_templates/en-US/Biometrics.adml
+++ /dev/null
@@ -1,60 +0,0 @@
-
-
-
- Biometrics Configuration Settings
- Biometrics Configuration Settings
-
-
- Biometrics
- Facial Features
- Allow the use of biometrics
- This policy setting allows or prevents the Windows Biometric Service to run on this computer.
-
-If you enable or do not configure this policy setting, the Windows Biometric Service is available, and users can run applications that use biometrics on Windows. If you want to enable the ability to log on with biometrics, you must also configure the "Allow users to log on using biometrics" policy setting.
-
-If you disable this policy setting, the Windows Biometric Service is unavailable, and users cannot use any biometric feature in Windows.
-
-Note: Users who log on using biometrics should create a password recovery disk; this will prevent data loss in the event that someone forgets their logon credentials.
-
- Allow users to log on using biometrics
- This policy setting determines whether users can log on or elevate User Account Control (UAC) permissions using biometrics. By default, local users will be able to log on to the local computer, but the "Allow domain users to log on using biometrics" policy setting will need to be enabled for domain users to log on to the domain.
-
-If you enable or do not configure this policy setting, all users can log on to a local Windows-based computer and can elevate permissions with UAC using biometrics.
-
-If you disable this policy setting, biometrics cannot be used by any users to log on to a local Windows-based computer.
-
-Note: Users who log on using biometrics should create a password recovery disk; this will prevent data loss in the event that someone forgets their logon credentials.
-
- Allow domain users to log on using biometrics
- This policy setting determines whether users with a domain account can log on or elevate User Account Control (UAC) permissions using biometrics.
-
-If you enable or do not configure this policy setting, Windows allows domain users to log on to a domain-joined computer using biometrics.
-
-If you disable this policy setting, Windows prevents domain users from logging on to a domain-joined computer using biometrics.
-
-Note: Prior to Windows 10, not configuring this policy setting would have prevented domain users from using biometrics to log on.
-
- Specify timeout for fast user switching events
- This policy setting specifies the number of seconds a pending fast user switch event will remain active before the switch is initiated. By default, a fast user switch event is active for 10 seconds before becoming inactive.
-
-If you enable this policy setting, you can configure the fast user switch event timeout to specify the number of seconds the event remains active. This value cannot exceed 60 seconds.
-
-If you disable or do not configure this policy setting, a default value of 10 seconds is used for fast-user switch event timeouts.
-
- Configure enhanced anti-spoofing
- This policy setting determines whether enhanced anti-spoofing is required for Windows Hello face authentication.
-
-If you enable this setting, Windows requires all users on managed devices to use enhanced anti-spoofing for Windows Hello face authentication. This disables Windows Hello face authentication on devices that do not support enhanced anti-spoofing.
-
-If you disable or don't configure this setting, Windows doesn't require enhanced anti-spoofing for Windows Hello face authentication.
-
-Note that enhanced anti-spoofing for Windows Hello face authentication is not required on unmanaged devices.
-
-
-
-
- Timeout in seconds:
-
-
-
-
diff --git a/policy_templates/en-US/Bits.adml b/policy_templates/en-US/Bits.adml
deleted file mode 100644
index 7e857c5..0000000
--- a/policy_templates/en-US/Bits.adml
+++ /dev/null
@@ -1,387 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
-
- Windows XP SP2 or Windows Server 2003 SP1, or computers with BITS 2.0 installed.
- Windows XP or Windows Server 2003, or computers with BITS 1.5 installed.
- Windows 7 or computers with BITS 3.5 installed.
- Windows 8 or Windows Server 2012 or Windows RT or computers with BITS 5 installed.
-
-
-
- Background Intelligent Transfer Service (BITS)
-
-
-
- Timeout for inactive BITS jobs
- This policy setting specifies the number of days a pending BITS job can remain inactive before the job is considered abandoned. By default BITS will wait 90 days before considering an inactive job abandoned. After a job is determined to be abandoned, the job is deleted from BITS and any downloaded files for the job are deleted from the disk.
- Note: Any property changes to the job or any successful download action will reset this timeout.
-
- Consider increasing the timeout value if computers tend to stay offline for a long period of time and still have pending jobs.
- Consider decreasing this value if you are concerned about orphaned jobs occupying disk space.
-
- If you enable this policy setting, you can configure the inactive job timeout to specified number of days.
-
- If you disable or do not configure this policy setting, the default value of 90 (days) will be used for the inactive job timeout.
-
-
-
-
- Limit the maximum BITS job download time
- This policy setting limits the amount of time that Background Intelligent Transfer Service (BITS) will take to download the files in a BITS job.
-
- The time limit applies only to the time that BITS is actively downloading files. When the cumulative download time exceeds this limit, the job is placed in the error state.
-
- By default BITS uses a maximum download time of 90 days (7,776,000 seconds).
-
- If you enable this policy setting, you can set the maximum job download time to a specified number of seconds.
-
- If you disable or do not configure this policy setting, the default value of 90 days (7,776,000 seconds) will be used.
-
-
-
-
- Limit the maximum network bandwidth for BITS background transfers
- This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers. (This policy setting does not affect foreground transfers.)
-
- You can specify a limit to use during a specific time interval and at all other times. For example, limit the use of network bandwidth to 10 Kbps from 8:00 A.M. to 5:00 P.M., and use all available unused bandwidth the rest of the day's hours.
-
- If you enable this policy setting, BITS will limit its bandwidth usage to the specified values. You can specify the limit in kilobits per second (Kbps). If you specify a value less than 2 kilobits, BITS will continue to use approximately 2 kilobits. To prevent BITS transfers from occurring, specify a limit of 0.
-
- If you disable or do not configure this policy setting, BITS uses all available unused bandwidth.
-
- Note: You should base the limit on the speed of the network link, not the computer's network interface card (NIC). This policy setting does not affect Peercaching transfers between peer computers (it does affect transfers from the origin server); the "Limit the maximum network bandwidth used for Peercaching" policy setting should be used for that purpose.
-
- Consider using this setting to prevent BITS transfers from competing for network bandwidth when the client computer has a fast network card (10Mbs), but is connected to the network via a slow link (56Kbs).
-
- 10 AM
- 10 PM
- 11 AM
- 11 PM
- 12 AM
- 12 PM
- 1 AM
- 1 PM
- 2 AM
- 2 PM
- 3 AM
- 3 PM
- 4 AM
- 4 PM
- 5 AM
- 5 PM
- 6 AM
- 6 PM
- 7 AM
- 7 PM
- 8 AM
- 8 PM
- 9 AM
- 9 PM
-
- Sunday
- Monday
- Tuesday
- Wednesday
- Thursday
- Friday
- Saturday
-
- Kbps
- Mbps
- Unlimited
-
- Set up a work schedule to limit the maximum network bandwidth used for BITS background transfers
- This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers during the work and nonwork days and hours. The work schedule is defined using a weekly calendar, which consists of days of the week and hours of the day. All hours and days that are not defined in a work schedule are considered non-work hours.
-
- If you enable this policy setting, you can set up a schedule for limiting network bandwidth during both work and nonwork hours. After the work schedule is defined, you can set the bandwidth usage limits for each of the three BITS background priority levels: high, normal, and low.
-
- You can specify a limit to use for background jobs during a work schedule. For example, you can limit the network bandwidth of low priority jobs to 128 Kbps from 8:00 A.M. to 5:00 P.M. on Monday through Friday, and then set the limit to 512 Kbps for nonwork hours.
-
- If you disable or do not configure this policy setting, BITS uses all available unused bandwidth for background job transfers.
-
-
- Set up a maintenance schedule to limit the maximum network bandwidth used for BITS background transfers
- This policy setting limits the network bandwidth that Background Intelligent Transfer Service (BITS) uses for background transfers during the maintenance days and hours. Maintenance schedules further limit the network bandwidth that is used for background transfers.
-
- If you enable this policy setting, you can define a separate set of network bandwidth limits and set up a schedule for the maintenance period.
-
- You can specify a limit to use for background jobs during a maintenance schedule. For example, if normal priority jobs are currently limited to 256 Kbps on a work schedule, you can further limit the network bandwidth of normal priority jobs to 0 Kbps from 8:00 A.M. to 10:00 A.M. on a maintenance schedule.
-
- If you disable or do not configure this policy setting, the limits defined for work or nonwork schedules will be used.
-
- Note: The bandwidth limits that are set for the maintenance period supersede any limits defined for work and other schedules.
-
-
-
-
-
-
- Set default download behavior for BITS jobs on costed networks
-
- This policy setting defines the default behavior that the Background Intelligent Transfer Service (BITS) uses for background transfers when the system is connected to a costed network (3G, etc.). Download behavior policies further limit the network usage of background transfers.
-
- If you enable this policy setting, you can define a default download policy for each BITS job priority. This setting does not override a download policy explicitly configured by the application that created the BITS job, but does apply to jobs that are created by specifying only a priority.
-
- For example, you can specify that background jobs are by default to transfer only when on uncosted network connections, but foreground jobs should proceed only when not roaming. The values that can be assigned are:
- - Always transfer
- - Transfer unless roaming
- - Transfer unless surcharge applies (when not roaming or overcap)
- - Transfer unless nearing limit (when not roaming or nearing cap)
- - Transfer only if unconstrained
- - Custom--allows you to specify a bitmask, in which the bits describe cost states allowed or disallowed for this priority: (bits described here)
- 0x1 - The cost is unknown or the connection is unlimited and is considered to be unrestricted of usage charges and capacity constraints.
- 0x2 - The usage of this connection is unrestricted up to a certain data limit
- 0x4 - The usage of this connection is unrestricted up to a certain data limit and plan usage is less than 80 percent of the limit.
- 0x8 - Usage of this connection is unrestricted up to a certain data limit and plan usage is between 80 percent and 100 percent of the limit.
- 0x10 - Usage of this connection is unrestricted up to a certain data limit, which has been exceeded. Surcharge applied or unknown.
- 0x20 - Usage of this connection is unrestricted up to a certain data limit, which has been exceeded. No surcharge applies, but speeds are likely reduced.
- 0x40 - The connection is costed on a per-byte basis.
- 0x80 - The connection is roaming.
- 0x80000000 - Ignore congestion.
-
- Always transfer
- Transfer unless roaming
- Transfer unless surcharge applies (when not roaming or overcap)
- Transfer unless nearing limit (when not roaming or nearing cap)
- Transfer only if unconstrained
- Custom
-
-
-
-
- Allow BITS Peercaching
- This policy setting determines if the Background Intelligent Transfer Service (BITS) peer caching feature is enabled on a specific computer. By default, the files in a BITS job are downloaded only from the origin server specified by the job's owner.
-
- If BITS peer caching is enabled, BITS caches downloaded files and makes them available to other BITS peers. When transferring a download job, BITS first requests the files for the job from its peers in the same IP subnet. If none of the peers in the subnet have the requested files, BITS downloads them from the origin server.
-
- If you enable this policy setting, BITS downloads files from peers, caches the files, and responds to content requests from peers. Using the "Do not allow the computer to act as a BITS peer caching server" and "Do not allow the computer to act as a BITS peer caching client" policy settings, it is possible to control BITS peer caching functionality at a more detailed level. However, it should be noted that the "Allow BITS peer caching" policy setting must be enabled for the other two policy settings to have any effect.
-
- If you disable or do not configure this policy setting, the BITS peer caching feature will be disabled, and BITS will download files directly from the origin server.
-
-
-
-
- Limit the BITS Peercache size
- This policy setting limits the maximum amount of disk space that can be used for the BITS peer cache, as a percentage of the total system disk size. BITS will add files to the peer cache and make those files available to peers until the cache content reaches the specified cache size. By default, BITS will use 1 percent of the total system disk for the peercache.
-
- If you enable this policy setting, you can enter the percentage of disk space to be used for the BITS peer cache. You can enter a value between 1 percent and 80 percent.
-
- If you disable or do not configure this policy setting, the default size of the BITS peer cache is 1 percent of the total system disk size.
-
- Note: This policy setting has no effect if the "Allow BITS peer caching" setting is disabled or not configured.
-
-
-
-
- Limit the age of files in the BITS Peercache
- This policy setting limits the maximum age of files in the Background Intelligent Transfer Service (BITS) peer cache. In order to make the most efficient use of disk space, by default BITS removes any files in the peer cache that have not been accessed in the past 90 days.
-
- If you enable this policy setting, you can specify in days the maximum age of files in the cache. You can enter a value between 1 and 120 days.
-
- If you disable or do not configure this policy setting, files that have not been accessed for the past 90 days will be removed from the peer cache.
-
- Note: This policy setting has no effect if the "Allow BITS Peercaching" policy setting is disabled or not configured.
-
-
-
-
- Do not allow the computer to act as a BITS Peercaching client
- This policy setting specifies whether the computer will act as a BITS peer caching client. By default, when BITS peer caching is enabled, the computer acts as both a peer caching server (offering files to its peers) and a peer caching client (downloading files from its peers).
-
- If you enable this policy setting, the computer will no longer use the BITS peer caching feature to download files; files will be downloaded only from the origin server. However, the computer will still make files available to its peers.
-
- If you disable or do not configure this policy setting, the computer attempts to download peer-enabled BITS jobs from peer computers before reverting to the origin server.
-
- Note: This policy setting has no effect if the "Allow BITS peer caching" policy setting is disabled or not configured.
-
-
-
-
- Do not allow the computer to act as a BITS Peercaching server
- This policy setting specifies whether the computer will act as a BITS peer caching server. By default, when BITS peer caching is enabled, the computer acts as both a peer caching server (offering files to its peers) and a peer caching client (downloading files from its peers).
-
- If you enable this policy setting, the computer will no longer cache downloaded files and offer them to its peers. However, the computer will still download files from peers.
-
- If you disable or do not configure this policy setting, the computer will offer downloaded and cached files to its peers.
-
- Note: This setting has no effect if the "Allow BITS peer caching" setting is disabled or not configured.
-
-
-
-
- Limit the maximum network bandwidth used for Peercaching
- This policy setting limits the network bandwidth that BITS uses for peer cache transfers (this setting does not affect transfers from the origin server).
- To prevent any negative impact to a computer caused by serving other peers, by default BITS will use up to 30 percent of the bandwidth of the slowest active network interface. For example, if a computer has both a 100 Mbps network card and a 56 Kbps modem, and both are active, BITS will use a maximum of 30 percent of 56 Kbps.
- You can change the default behavior of BITS, and specify a fixed maximum bandwidth that BITS will use for peer caching.
-
- If you enable this policy setting, you can enter a value in bits per second (bps) between 1048576 and 4294967200 to use as the maximum network bandwidth used for peer caching.
-
- If you disable this policy setting or do not configure it, the default value of 30 percent of the slowest active network interface will be used.
-
- Note: This setting has no effect if the "Allow BITS peer caching" policy setting is disabled or not configured.
-
-
-
-
- Limit the maximum number of BITS jobs for this computer
- This policy setting limits the number of BITS jobs that can be created for all users of the computer. By default, BITS limits the total number of jobs that can be created on the computer to 300 jobs. You can use this policy setting to raise or lower the maximum number of user BITS jobs.
-
- If you enable this policy setting, BITS will limit the maximum number of BITS jobs to the specified number.
-
- If you disable or do not configure this policy setting, BITS will use the default BITS job limit of 300 jobs.
-
- Note: BITS jobs created by services and the local administrator account do not count toward this limit.
-
-
-
-
- Limit the maximum number of BITS jobs for each user
- This policy setting limits the number of BITS jobs that can be created by a user. By default, BITS limits the total number of jobs that can be created by a user to 60 jobs. You can use this setting to raise or lower the maximum number of BITS jobs a user can create.
-
- If you enable this policy setting, BITS will limit the maximum number of BITS jobs a user can create to the specified number.
-
- If you disable or do not configure this policy setting, BITS will use the default user BITS job limit of 300 jobs.
-
- Note: This limit must be lower than the setting specified in the "Maximum number of BITS jobs for this computer" policy setting, or 300 if the "Maximum number of BITS jobs for this computer" policy setting is not configured. BITS jobs created by services and the local administrator account do not count toward this limit.
-
-
-
-
- Limit the maximum number of files allowed in a BITS job
- This policy setting limits the number of files that a BITS job can contain. By default, a BITS job is limited to 200 files. You can use this setting to raise or lower the maximum number of files a BITS jobs can contain.
-
- If you enable this policy setting, BITS will limit the maximum number of files a job can contain to the specified number.
-
- If you disable or do not configure this policy setting, BITS will use the default value of 200 for the maximum number of files a job can contain.
-
- Note: BITS Jobs created by services and the local administrator account do not count toward this limit.
-
-
-
- Limit the maximum number of ranges that can be added to the file in a BITS job
- This policy setting limits the number of ranges that can be added to a file in a BITS job. By default, files in a BITS job are limited to 500 ranges per file. You can use this setting to raise or lower the maximum number ranges per file.
-
- If you enable this policy setting, BITS will limit the maximum number of ranges that can be added to a file to the specified number.
-
- If you disable or do not configure this policy setting, BITS will limit ranges to 500 ranges per file.
-
- Note: BITS Jobs created by services and the local administrator account do not count toward this limit.
-
-
-
- Do not allow the BITS client to use Windows Branch Cache
- This setting affects whether the BITS client is allowed to use Windows Branch Cache. If the Windows Branch Cache component is installed and enabled on a computer, BITS jobs on that computer can use Windows Branch Cache by default.
-
- If you enable this policy setting, the BITS client does not use Windows Branch Cache.
-
- If you disable or do not configure this policy setting, the BITS client uses Windows Branch Cache.
-
- Note: This policy setting does not affect the use of Windows Branch Cache by applications other than BITS. This policy setting does not apply to BITS transfers over SMB. This setting has no effect if the computer's administrative settings for Windows Branch Cache disable its use entirely.
-
-
-
-
-
-
- Inactive Job Timeout in Days:
-
-
- Active Job Timeout in seconds:
-
-
- Limit background transfer rate (Kbps) to:
- From
- to
- At all other times
- Use all available unused bandwidth
- OR
- Limit background transfer rate (Kbps) to:
-
-
- Number of days:
-
-
- Percentage of disk space to be used for the BITS peercache:
-
-
- Maximum network bandwidth used for Peercaching (bps):
-
-
-
- Maximum number of BITS jobs for this computer:
-
-
- Maximum number of BITS jobs for each user:
-
-
- Maximum number of files allowed in a BITS job:
-
-
- Maximum number of ranges that can be added to the file in a BITS job:
-
-
-
- Ignore bandwidth limits if the source and the destination are on the same subnet.
- Work Days
- From
- To
-
- Daily Work Hours
- From
- To
-
- Bandwidth Limits During Work Hours
- High Priority Limit:
- High Priority Unit:
- Normal Priority Limit:
- Normal Priority Unit:
- Low Priority Limit:
- Low Priority Unit:
-
- Bandwidth Limits During Non-Work Hours
- High Priority Limit:
- High Priority Unit:
- Normal Priority Limit:
- Normal Priority Unit:
- Low Priority Limit:
- Low Priority Unit:
-
-
-
- Set default transfer behaviour for BITS jobs on costed network
- Foreground
- Foreground (Custom)
- High
- High (Custom)
- Normal
- Normal (Custom)
- Low
- Low (Custom)
-
-
-
- Maintenance Days
- From
- To
-
- Daily Maintenance Hours
- From
- To
-
- Bandwidth Limits During Maintenance Hours
- High Priority Limit:
- High Priority Unit:
- Normal Priority Limit:
- Normal Priority Unit:
- Low Priority Limit:
- Low Priority Unit:
-
-
-
-
-
diff --git a/policy_templates/en-US/CEIPEnable.adml b/policy_templates/en-US/CEIPEnable.adml
deleted file mode 100644
index 2c206f1..0000000
--- a/policy_templates/en-US/CEIPEnable.adml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Windows Customer Experience Improvement Program
- Allow Corporate redirection of Customer Experience Improvement uploads
- If you enable this setting all Customer Experience Improvement Program uploads are redirected to Microsoft Operations Manager server.
-
-If you disable this setting uploads are not redirected to a Microsoft Operations Manager server.
-
-If you do not configure this setting uploads are not redirected to a Microsoft Operations Manager server.
- Tag Windows Customer Experience Improvement data with Study Identifier
- This policy setting will enable tagging of Windows Customer Experience Improvement data when a study is being conducted.
-
-If you enable this setting then Windows CEIP data uploaded will be tagged.
-
-If you do not configure this setting or disable it, then CEIP data will not be tagged with the Study Identifier.
-
-
-
-
-
-
-
-
-
- Study Identifier:
-
-
-
-
diff --git a/policy_templates/en-US/COM.adml b/policy_templates/en-US/COM.adml
deleted file mode 100644
index f11eec1..0000000
--- a/policy_templates/en-US/COM.adml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Download missing COM components
- This policy setting directs the system to search Active Directory for missing Component Object Model (COM) components that a program requires.
-
-Many Windows programs, such as the MMC snap-ins, use the interfaces provided by the COM components. These programs cannot perform all their functions unless Windows has internally registered the required components.
-
-If you enable this policy setting and a component registration is missing, the system searches for it in Active Directory and, if it is found, downloads it. The resulting searches might make some programs start or run slowly.
-
-If you disable or do not configure this policy setting, the program continues without the registration. As a result, the program might not perform all its functions, or it might stop.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-
-
diff --git a/policy_templates/en-US/Camera.adml b/policy_templates/en-US/Camera.adml
deleted file mode 100644
index e19ae65..0000000
Binary files a/policy_templates/en-US/Camera.adml and /dev/null differ
diff --git a/policy_templates/en-US/CipherSuiteOrder.adml b/policy_templates/en-US/CipherSuiteOrder.adml
deleted file mode 100644
index 9ab5658..0000000
--- a/policy_templates/en-US/CipherSuiteOrder.adml
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- SSL Configuration Settings
- SSL Cipher Suite Order
- This policy setting determines the cipher suites used by the Secure Socket Layer (SSL).
-
-If you enable this policy setting, SSL cipher suites are prioritized in the order specified.
-
-If you disable or do not configure this policy setting, default cipher suite order is used.
-
-Link for all the cipherSuites: http://go.microsoft.com/fwlink/?LinkId=517265
-
-
-
- ECC Curve Order
- This policy setting determines the priority order of ECC curves used with ECDHE cipher suites.
-
-If you enable this policy setting, ECC curves are prioritized in the order specified.(Enter one Curve name per line)
-
-If you disable or do not configure this policy setting, the default ECC curve order is used.
-
-Default Curve Order
-============
-curve25519
-NistP256
-NistP384
-
-To See all the curves supported on the system, Use the following command:
-
-CertUtil.exe -DisplayEccCurve
-
-
-
-
-
-
-
- TLS_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_NULL_SHA256,TLS_RSA_WITH_NULL_SHA,TLS_PSK_WITH_AES_256_GCM_SHA384,TLS_PSK_WITH_AES_128_GCM_SHA256,TLS_PSK_WITH_AES_256_CBC_SHA384,TLS_PSK_WITH_AES_128_CBC_SHA256,TLS_PSK_WITH_NULL_SHA384,TLS_PSK_WITH_NULL_SHA256
-
-
-
- Type the ECC curve names in the preferred order (one curve name per line)
- ECC Curve Order:
-
-
-
-
diff --git a/policy_templates/en-US/CloudContent.adml b/policy_templates/en-US/CloudContent.adml
deleted file mode 100644
index 7682460..0000000
--- a/policy_templates/en-US/CloudContent.adml
+++ /dev/null
@@ -1,102 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Cloud Content
- Configure Windows spotlight on lock screen
- This policy setting lets you configure Windows spotlight on the lock screen.
-
-If you enable this policy setting, "Windows spotlight" will be set as the lock screen provider and users will not be able to modify their lock screen. "Windows spotlight" will display daily images from Microsoft on the lock screen.
-
-Additionally, if you check the "Include content from Enterprise spotlight" checkbox and your organization has setup an Enterprise spotlight content service in Azure, the lock screen will display internal messages and communications configured in that service, when available. If your organization does not have an Enterprise spotlight content service, the checkbox will have no effect.
-
-If you disable this policy setting, Windows spotlight will be turned off and users will no longer be able to select it as their lock screen. Users will see the default lock screen image and will be able to select another image, unless you have enabled the "Prevent changing lock screen image" policy.
-
-If you do not configure this policy, Windows spotlight will be available on the lock screen and will be selected by default, unless you have configured another default lock screen image using the "Force a specific default lock screen and logon image" policy.
-
-Note: This policy is only available for Enterprise SKUs
- Turn off all Windows spotlight features
- This policy setting lets you turn off all Windows Spotlight features at once.
-
-If you enable this policy setting, Windows spotlight on lock screen, Windows tips, Microsoft consumer features and other related features will be turned off. You should enable this policy setting if your goal is to minimize network traffic from target devices.
-
-If you disable or do not configure this policy setting, Windows spotlight features are allowed and may be controlled individually using their corresponding policy settings.
- Turn off Windows Spotlight on Action Center
- If you enable this policy, Windows Spotlight notifications will no longer be shown on Action Center.
-
-If you disable or do not configure this policy, Microsoft may display notifications in Action Center that will suggest apps or features to help users be more productive on Windows.
- Turn off Windows Spotlight on Settings
- If you enable this policy, Windows Spotlight suggestions will no longer be shown in Settings app.
-
-If you disable or do not configure this policy, Microsoft may suggest apps or features in Settings app to help users be productive on Windows or their linked phone.
- Do not use diagnostic data for tailored experiences
- This policy setting lets you prevent Windows from using diagnostic data to provide tailored experiences to the user.
-
-If you enable this policy setting, Windows will not use diagnostic data from this device (this data may include browser, app and feature usage, depending on the "diagnostic data" setting value) to customize content shown on lock screen, Windows tips, Microsoft consumer features and other related features. If these features are enabled, users will still see recommendations, tips and offers, but they may be less relevant.
-
-If you disable or do not configure this policy setting, Microsoft will use diagnostic data to provide personalized recommendations, tips and offers to tailor Windows for the user's needs, and make it work better for them.
-
-Note: this setting does not control Cortana tailored experiences, since there are separate policies to configure it.
- Turn off Microsoft consumer experiences
- This policy setting turns off experiences that help consumers make the most of their devices and Microsoft account.
-
-If you enable this policy setting, users will no longer see personalized recommendations from Microsoft and notifications about their Microsoft account.
-
-If you disable or do not configure this policy setting, users may see suggestions from Microsoft and notifications about their Microsoft account.
-
-Note: This setting only applies to Enterprise and Education SKUs.
- Do not show Windows tips
- This policy setting prevents Windows tips from being shown to users.
-
-If you enable this policy setting, users will no longer see Windows tips.
-
-If you disable or do not configure this policy setting, users may see contextual popups explaining how to use Windows. Microsoft uses diagnostic data to determine which tips to show.
-
-Note: If you disable or do not configure this policy setting, but enable the "Computer Configuration\Administrative Templates\Windows Components\Data Collection and Preview Builds\Allow Telemetry" policy setting with a level of "Basic" or below, users may see a limited set of tips.
-Also, this setting only applies to Enterprise and Education SKUs.
- Do not suggest third-party content in Windows spotlight
- If you enable this policy, Windows spotlight features like lock screen spotlight, suggested apps in Start menu or Windows tips will no longer suggest apps and content from third-party software publishers. Users may still see suggestions and tips to make them more productive with Microsoft features and apps.
-
-If you disable or do not configure this policy, Windows spotlight features may suggest apps and content from third-party software publishers in addition to Microsoft apps and content.
- Turn off the Windows Welcome Experience
- This policy setting lets you turn off the Windows Spotlight Windows Welcome experience. This feature helps onboard users to Windows, for instance launching Microsoft Edge with a web page highlighting new features.
-
-If you enable this policy, the Windows Welcome Experience will no longer display when there are updates and changes to Windows and its apps.
-
-If you disable or do not configure this policy, the Windows Welcome Experience will be launched to help onboard users to Windows telling them about what's new, changed, and suggested.
- Turn off cloud optimized content
- This policy setting lets you turn off cloud optimized content in all Windows experiences.
-
-If you enable this policy, Windows experiences that use the cloud optimized content client component, will instead present the default fallback content.
-
-If you disable or do not configure this policy, Windows experiences will be able to use cloud optimized content.
- Turn off Spotlight collection on Desktop
- This policy setting removes the Spotlight collection setting in Personalization, rendering the user unable to select and subsequentyly download daily images from Microsoft to desktop.
-
-If you enable this policy, "Spotlight collection" will not be available as an option in Personalization settings.
-
-If you disable or do not configure this policy, "Spotlight collection" will appear as an option in Personalization settings, allowing the user to select "Spotlight collection" as the Desktop provider and display daily images from Microsoft on the desktop.
- Turn off cloud consumer account state content
- This policy setting lets you turn off cloud consumer account state content in all Windows experiences.
-
- If you enable this policy, Windows experiences that use the cloud consumer account state content client component, will instead present the default fallback content.
-
- If you disable or do not configure this policy, Windows experiences will be able to use cloud consumer account state content.
-
- Enable Organizational Messages
- Organizational messages allow Administrators to deliver messages to their end users on selected Windows 11 experiences. Organizational messages are available to Administrators via services like Microsoft Endpoint Manager.
-
-By default, this policy is disabled. If you enable this policy, these experiences will show content booked by Administrators.
-
-Enabling this policy will have no impact on existing MDM policy settings governing delivery of content from Microsoft on Windows experiences.
-
-
-
- Include content from Enterprise spotlight
-
-
-
-
diff --git a/policy_templates/en-US/Conf.adml b/policy_templates/en-US/Conf.adml
deleted file mode 100644
index 25a036a..0000000
--- a/policy_templates/en-US/Conf.adml
+++ /dev/null
@@ -1,124 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow persisting automatic acceptance of Calls
- Make the automatic acceptance of incoming calls persistent.
- Application Sharing
- Audio & Video
- Disable the Advanced Calling button
- Disables the Advanced Calling button on the General Options page. Users will not then be able to change the call placement method and the servers used.
- Disable application Sharing
- Disables the application sharing feature of NetMeeting completely. Users will not be able to host or view shared applications.
- Hide the Audio page
- Hides the Audio page of the Tools Options dialog. Users will not then be able to change audio settings.
- Disable Chat
- Disables the Chat feature of NetMeeting.
- Hide the General page
- Hides the General page of the Tools Options dialog. Users will not then be able to change personal identification and bandwidth settings.
- Disable Whiteboard
- Disables the T.126 whiteboard feature of NetMeeting.
- Disable NetMeeting 2.x Whiteboard
- Disables the 2.x whiteboard feature of NetMeeting.
-
-The 2.x whiteboard is available for compatibility with older versions of NetMeeting only.
-
-Deployers who do not need it can save bandwidth by disabling it.
- Disable remote Desktop Sharing
- Disables the remote desktop sharing feature of NetMeeting. Users will not be able to set it up or use it for controlling their computers remotely.
- Hide the Security page
- Hides the Security page of the Tools Options dialog. Users will not then be able to change call security and authentication settings.
- Hide the Video page
- Hides the Video page of the Tools Options dialog. Users will not then be able to change video settings.
- Enable Automatic Configuration
- Configures NetMeeting to download settings for users each time it starts.
-
-The settings are downloaded from the URL listed in the "Configuration URL:" text box.
-
-Group Policy based settings have precedence over any conflicting settings set by downloading them from this URL.
- NetMeeting
- Options Page
- Prevent adding Directory servers
- Prevents users from adding directory (ILS) servers to the list of those they can use for placing calls.
- Disable Audio
- Disables the audio feature of NetMeeting. Users will not be able to send or receive audio.
- Prevent automatic acceptance of Calls
- Prevents users from turning on automatic acceptance of incoming calls.
-
-This ensures that others cannot call and connect to NetMeeting when the user is not present.
-
-This policy is recommended when deploying NetMeeting to run always.
- Prevent changing DirectSound Audio setting
- Prevents user from changing the DirectSound audio setting. DirectSound provides much better audio quality, but older audio hardware may not support it.
- Prevent changing Call placement method
- Prevents users from changing the way calls are placed, either directly or via a gatekeeper server.
- Disable Directory services
- Disables the directory feature of NetMeeting.
-
-Users will not logon to a directory (ILS) server when NetMeeting starts. Users will also not be able to view or place calls via a NetMeeting directory.
-
-This policy is for deployers who have their own location or calling schemes such as a Web site or an address book."
- Disable full duplex Audio
- Disables full duplex mode audio. Users will not be able to listen to incoming audio while speaking into the microphone. Older audio hardware does not perform well when in full duplex mode.
- Prevent Control
- Prevents users from allowing others in a conference to control what they have shared. This enforces a read-only mode; the other participants cannot change the data in the shared application.
- Prevent receiving files
- Prevents users from receiving files from others in a conference.
- Prevent receiving Video
- Prevents users from receiving video. Users will still be able to send video provided they have the hardware."
- Prevent sending files
- Prevents users from sending files to others in a conference.
- Prevent sending Video
- Prevents users from sending video if they have the hardware. Users will still be able to receive video from others.
- Prevent Sharing
- Prevents users from sharing anything themselves. They will still be able to view shared applications/desktops from others.
- Prevent Sharing Command Prompts
- Prevents users from sharing command prompts. This prevents users from inadvertently sharing out applications, since command prompts can be used to launch other applications.
- Prevent Desktop Sharing
- Prevents users from sharing the whole desktop. They will still be able to share individual applications.
- Prevent Sharing Explorer windows
- Prevents users from sharing Explorer windows. This prevents users from inadvertently sharing out applications, since Explorer windows can be used to launch other applications.
- Prevent Application Sharing in true color
- Prevents users from sharing applications in true color. True color sharing uses more bandwidth in a conference.
- Prevent viewing Web directory
- Prevents users from viewing directories as Web pages in a browser.
- Limit the size of sent files
- Limits the size of files users can send to others in a conference.
- Disabled
- Required
- Limit the bandwidth of Audio and Video
- Limits the bandwidth audio and video will consume when in a conference. This setting will guide NetMeeting to choose the right formats and send rate so that the bandwidth is limited.
- Set the intranet support Web page
- Sets the URL NetMeeting will display when the user chooses the Help Online Support command.
- Set Call Security options
- Sets the level of security for both outgoing and incoming NetMeeting calls.
- at least Windows NetMeeting v3.0
-
-
-
-
-
-
-
-
- Maximum size in Kbytes
- Value is size in Kbytes, only files smaller
- than this size can be sent by the user.
-
-
- Maximum bandwidth in Kilobytes per second:
-
-
-
-
-
-
-
- Call security
-
-
-
-
diff --git a/policy_templates/en-US/ControlPanel.adml b/policy_templates/en-US/ControlPanel.adml
deleted file mode 100644
index 3403f72..0000000
--- a/policy_templates/en-US/ControlPanel.adml
+++ /dev/null
@@ -1,105 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Hide specified Control Panel items
- This setting allows you to display or hide specified Control Panel items, such as Mouse, System, or Personalization, from the Control Panel window and the Start screen. The setting affects the Start screen and Control Panel window, as well as other ways to access Control Panel items, such as shortcuts in Help and Support or command lines that use control.exe. This policy has no effect on items displayed in PC settings.
-
-If you enable this setting, you can select specific items not to display on the Control Panel window and the Start screen.
-
-To hide a Control Panel item, enable this policy setting and click Show to access the list of disallowed Control Panel items. In the Show Contents dialog box in the Value column, enter the Control Panel item's canonical name. For example, enter Microsoft.Mouse, Microsoft.System, or Microsoft.Personalization.
-
-Note: For Windows Vista, Windows Server 2008, and earlier versions of Windows, the module name should be entered, for example timedate.cpl or inetcpl.cpl. If a Control Panel item does not have a CPL file, or the CPL file contains multiple applets, then its module name and string resource identification number should be entered, for example @systemcpl.dll,-1 for System, or @themecpl.dll,-1 for Personalization. A complete list of canonical and module names can be found in MSDN by searching "Control Panel items".
-
-If both the "Hide specified Control Panel items" setting and the "Show only specified Control Panel items" setting are enabled, the "Show only specified Control Panel items" setting is ignored.
-
-Note: The Display Control Panel item cannot be hidden in the Desktop context menu by using this setting. To hide the Display Control Panel item and prevent users from modifying the computer's display settings use the "Disable Display Control Panel" setting instead.
-
-Note: To hide pages in the System Settings app, use the "Settings Page Visibility" setting under Computer Configuration.
- Always open All Control Panel Items when opening Control Panel
- This policy setting controls the default Control Panel view, whether by category or icons.
-
-If this policy setting is enabled, the Control Panel opens to the icon view.
-
-If this policy setting is disabled, the Control Panel opens to the category view.
-
-If this policy setting is not configured, the Control Panel opens to the view used in the last Control Panel session.
-Note: Icon size is dependent upon what the user has set it to in the previous session.
- Prohibit access to Control Panel and PC settings
- Disables all Control Panel programs and the PC settings app.
-
-This setting prevents Control.exe and SystemSettings.exe, the program files for Control Panel and PC settings, from starting. As a result, users cannot start Control Panel or PC settings, or run any of their items.
-
-This setting removes Control Panel from:
-The Start screen
-File Explorer
-
-This setting removes PC settings from:
-The Start screen
-Settings charm
-Account picture
-Search results
-
-If users try to select a Control Panel item from the Properties item on a context menu, a message appears explaining that a setting prevents the action.
- Show only specified Control Panel items
- This policy setting controls which Control Panel items such as Mouse, System, or Personalization, are displayed on the Control Panel window and the Start screen. The only items displayed in Control Panel are those you specify in this setting. This setting affects the Start screen and Control Panel, as well as other ways to access Control Panel items such as shortcuts in Help and Support or command lines that use control.exe. This policy has no effect on items displayed in PC settings.
-
-To display a Control Panel item, enable this policy setting and click Show to access the list of allowed Control Panel items. In the Show Contents dialog box in the Value column, enter the Control Panel item's canonical name. For example, enter Microsoft.Mouse, Microsoft.System, or Microsoft.Personalization.
-
-Note: For Windows Vista, Windows Server 2008, and earlier versions of Windows, the module name, for example timedate.cpl or inetcpl.cpl, should be entered. If a Control Panel item does not have a CPL file, or the CPL file contains multiple applets, then its module name and string resource identification number should be entered. For example, enter @systemcpl.dll,-1 for System or @themecpl.dll,-1 for Personalization. A complete list of canonical and module names of Control Panel items can be found in MSDN by searching "Control Panel items".
-
-If both the "Hide specified Control Panel items" setting and the "Show only specified Control Panel items" setting are enabled, the "Show only specified Control Panel items" setting is ignored.
-
-Note: The Display Control Panel item cannot be hidden in the Desktop context menu by using this setting. To hide the Display Control Panel item and prevent users from modifying the computer's display settings use the "Disable Display Control Panel" setting instead.
-
-Note: To hide pages in the System Settings app, use the "Settings Page Visibility" setting under Computer Configuration.
- Settings Page Visibility
- Specifies the list of pages to show or hide from the System Settings app.
-
-This policy allows an administrator to block a given set of pages from the System Settings app. Blocked pages will not be visible in the app, and if all pages in a category are blocked the category will be hidden as well. Direct navigation to a blocked page via URI, context menu in Explorer or other means will result in the front page of Settings being shown instead.
-
-This policy has two modes: it can either specify a list of settings pages to show or a list of pages to hide. To specify a list of pages to show, the policy string must begin with "showonly:" (without quotes), and to specify a list of pages to hide, it must begin with "hide:". If a page in a showonly list would normally be hidden for other reasons (such as a missing hardware device), this policy will not force that page to appear. After this, the policy string must contain a semicolon-delimited list of settings page identifiers. The identifier for any given settings page is the published URI for that page, minus the "ms-settings:" protocol part.
-
-Example: to specify that only the About and Bluetooth pages should be shown (their respective URIs are ms-settings:about and ms-settings:bluetooth) and all other pages hidden:
-
-showonly:about;bluetooth
-
-Example: to specify that only the Bluetooth page (which has URI ms-settings:bluetooth) should be hidden:
-
-hide:bluetooth
-
-The availability of per-user support is documented here: https://go.microsoft.com/fwlink/?linkid=2102995
- Allow Online Tips
- Enables or disables the retrieval of online tips and help for the Settings app.
-
-If disabled, Settings will not contact Microsoft content services to retrieve tips and help content.
- Hide messages when Windows system requirements are not met
- This policy controls messages which are shown when Windows is running on a device that does not meet the minimum system requirements for this OS version.
-
-If you enable this policy setting, these messages will never appear on desktop or in the Settings app.
-
-If you disable or do not configure this policy setting, these messages will appear on desktop and in the Settings app when Windows is running on a device that does not meet the minimum system requirements for this OS version.
-
-
-
- List of disallowed Control Panel items
-
-
- List of allowed Control Panel items
-
-
-
-
-
-
-
-
- Allow Settings to retrieve online tips.
-
-
-
-
-
diff --git a/policy_templates/en-US/ControlPanelDisplay.adml b/policy_templates/en-US/ControlPanelDisplay.adml
deleted file mode 100644
index 6b8bb99..0000000
--- a/policy_templates/en-US/ControlPanelDisplay.adml
+++ /dev/null
@@ -1,279 +0,0 @@
-
-
- enter display name here
- enter description here
-
-
- Display
- Disable the Display Control Panel
- Disables the Display Control Panel.
-
-If you enable this setting, the Display Control Panel does not run. When users try to start Display, a message appears explaining that a setting prevents the action.
-
-Also, see the "Prohibit access to the Control Panel" (User Configuration\Administrative Templates\Control Panel) and "Remove programs on Settings menu" (User Configuration\Administrative Templates\Start Menu & Taskbar) settings.
- Hide Settings tab
- Removes the Settings tab from Display in Control Panel.
-
-This setting prevents users from using Control Panel to add, configure, or change the display settings on the computer.
- Personalization
- Prevent changing color and appearance
- Disables the Color (or Window Color) page in the Personalization Control Panel, or the Color Scheme dialog in the Display Control Panel on systems where the Personalization feature is not available.
-
-This setting prevents users from using Control Panel to change the window border and taskbar color (on Windows 8), glass color (on Windows Vista and Windows 7), system colors, or color scheme of the desktop and windows.
-
-If this setting is disabled or not configured, the Color (or Window Color) page or Color Scheme dialog is available in the Personalization or Display Control Panel.
-
-For systems prior to Windows Vista, this setting hides the Appearance and Themes tabs in the in Display in Control Panel.
- Prevent changing screen saver
-
- Prevents the Screen Saver dialog from opening in the Personalization or Display Control Panel.
-
-This setting prevents users from using Control Panel to add, configure, or change the screen saver on the computer. It does not prevent a screen saver from running.
-
- Enable screen saver
- Enables desktop screen savers.
-
-If you disable this setting, screen savers do not run. Also, this setting disables the Screen Saver section of the Screen Saver dialog in the Personalization or Display Control Panel. As a result, users cannot change the screen saver options.
-
-If you do not configure it, this setting has no effect on the system.
-
-If you enable it, a screen saver runs, provided the following two conditions hold: First, a valid screen saver on the client is specified through the "Screen Saver executable name" setting or through Control Panel on the client computer. Second, the screen saver timeout is set to a nonzero value through the setting or Control Panel.
-
-Also, see the "Prevent changing Screen Saver" setting.
- Force specific screen saver
- Specifies the screen saver for the user's desktop.
-
-If you enable this setting, the system displays the specified screen saver on the user's desktop. Also, this setting disables the drop-down list of screen savers in the Screen Saver dialog in the Personalization or Display Control Panel, which prevents users from changing the screen saver.
-
-If you disable this setting or do not configure it, users can select any screen saver.
-
-If you enable this setting, type the name of the file that contains the screen saver, including the .scr file name extension. If the screen saver file is not in the %Systemroot%\System32 directory, type the fully qualified path to the file.
-
-If the specified screen saver is not installed on a computer to which this setting applies, the setting is ignored.
-
-Note: This setting can be superseded by the "Enable Screen Saver" setting. If the "Enable Screen Saver" setting is disabled, this setting is ignored, and screen savers do not run.
- Password protect the screen saver
- Determines whether screen savers used on the computer are password protected.
-
-If you enable this setting, all screen savers are password protected. If you disable this setting, password protection cannot be set on any screen saver.
-
-This setting also disables the "Password protected" checkbox on the Screen Saver dialog in the Personalization or Display Control Panel, preventing users from changing the password protection setting.
-
-If you do not configure this setting, users can choose whether or not to set password protection on each screen saver.
-
-To ensure that a computer will be password protected, enable the "Enable Screen Saver" setting and specify a timeout via the "Screen Saver timeout" setting.
-
-Note: To remove the Screen Saver dialog, use the "Prevent changing Screen Saver" setting.
- Screen saver timeout
- Specifies how much user idle time must elapse before the screen saver is launched.
-
-When configured, this idle time can be set from a minimum of 1 second to a maximum of 86,400 seconds, or 24 hours. If set to zero, the screen saver will not be started.
-
-This setting has no effect under any of the following circumstances:
-
- - The setting is disabled or not configured.
-
- - The wait time is set to zero.
-
- - The "Enable Screen Saver" setting is disabled.
-
- - Neither the "Screen saver executable name" setting nor the Screen Saver dialog of the client computer's Personalization or Display Control Panel specifies a valid existing screen saver program on the client.
-
-When not configured, whatever wait time is set on the client through the Screen Saver dialog in the Personalization or Display Control Panel is used. The default is 15 minutes.
- Prevent changing desktop background
- Prevents users from adding or changing the background design of the desktop.
-
-By default, users can use the Desktop Background page in the Personalization or Display Control Panel to add a background design (wallpaper) to their desktop.
-
-If you enable this setting, none of the Desktop Background settings can be changed by the user.
-
-To specify wallpaper for a group, use the "Desktop Wallpaper" setting.
-
-Note: You must also enable the "Desktop Wallpaper" setting to prevent users from changing the desktop wallpaper. Refer to KB article: Q327998 for more information.
-
-Also, see the "Allow only bitmapped wallpaper" setting.
- Prevent changing sounds
- Prevents users from changing the sound scheme.
-
-By default, users can use the Sounds tab in the Sound Control Panel to add, remove, or change the system Sound Scheme.
-
-If you enable this setting, none of the Sound Scheme settings can be changed by the user.
- Prevent changing mouse pointers
- Prevents users from changing the mouse pointers.
-
-By default, users can use the Pointers tab in the Mouse Control Panel to add, remove, or change the mouse pointers.
-
-If you enable this setting, none of the mouse pointer scheme settings can be changed by the user.
- Prevent changing desktop icons
- Prevents users from changing the desktop icons.
-
-By default, users can use the Desktop Icon Settings dialog in the Personalization or Display Control Panel to show, hide, or change the desktop icons.
-
-If you enable this setting, none of the desktop icons can be changed by the user.
-
-For systems prior to Windows Vista, this setting also hides the Desktop tab in the Display Control Panel.
- Prevent changing color scheme
- This setting forces the theme color scheme to be the default color scheme.
-
-If you enable this setting, a user cannot change the color scheme of the current desktop theme.
-
-If you disable or do not configure this setting, a user may change the color scheme of the current desktop theme.
-
-For Windows 7 and later, use the "Prevent changing color and appearance" setting.
- Prevent changing theme
- This setting disables the theme gallery in the Personalization Control Panel.
-
-If you enable this setting, users cannot change or save a theme. Elements of a theme such as the desktop background, color, sounds, and screen saver can still be changed (unless policies are set to turn them off).
-
-If you disable or do not configure this setting, there is no effect.
-
-Note: If you enable this setting but do not specify a theme using the "load a specific theme" setting, the theme defaults to whatever the user previously set or the system default.
- Load a specific theme
- Specifies which theme file is applied to the computer the first time a user logs on.
-
-If you enable this setting, the theme that you specify will be applied when a new user logs on for the first time. This policy does not prevent the user from changing the theme or any of the theme elements such as the desktop background, color, sounds, or screen saver after the first logon.
-
-If you disable or do not configure this setting, the default theme will be applied at the first logon.
- Prevent changing visual style for windows and buttons
- Prevents users or applications from changing the visual style of the windows and buttons displayed on their screens.
-
-When enabled on Windows XP, this setting disables the "Windows and buttons" drop-down list on the Appearance tab in Display Properties.
-
-When enabled on Windows XP and later systems, this setting prevents users and applications from changing the visual style through the command line. Also, a user may not apply a different visual style when changing themes.
- Force a specific visual style file or force Windows Classic
- This setting allows you to force a specific visual style file by entering the path (location) of the visual style file.
-
-This can be a local computer visual style (aero.msstyles), or a file located on a remote server using a UNC path (\\Server\Share\aero.msstyles).
-
-If you enable this setting, the visual style file that you specify will be used. Also, a user may not apply a different visual style when changing themes.
-
-If you disable or do not configure this setting, the users can select the visual style that they want to use by changing themes (if the Personalization Control Panel is available).
-
-Note: If this setting is enabled and the file is not available at user logon, the default visual style is loaded.
-
-Note: When running Windows XP, you can select the Luna visual style by typing %windir%\resources\Themes\Luna\Luna.msstyles
-
-Note: To select the Windows Classic visual style, leave the box blank beside "Path to Visual Style:" and enable this setting. When running Windows 8 or Windows RT, you cannot apply the Windows Classic visual style.
- Prohibit selection of visual style font size
- Prevents users from changing the size of the font in the windows and buttons displayed on their screens.
-
-If this setting is enabled, the "Font size" drop-down list on the Appearance tab in Display Properties is disabled.
-
-If you disable or do not configure this setting, a user may change the font size using the "Font size" drop-down list on the Appearance tab.
- Do not display the lock screen
- This policy setting controls whether the lock screen appears for users.
-
-If you enable this policy setting, users that are not required to press CTRL + ALT + DEL before signing in will see their selected tile after locking their PC.
-
-If you disable or do not configure this policy setting, users that are not required to press CTRL + ALT + DEL before signing in will see a lock screen after locking their PC. They must dismiss the lock screen using touch, the keyboard, or by dragging it with the mouse.
- Prevent changing lock screen and logon image
- Prevents users from changing the background image shown when the machine is locked or when on the logon screen.
-
-By default, users can change the background image shown when the machine is locked or displaying the logon screen.
-
-If you enable this setting, the user will not be able to change their lock screen and logon image, and they will instead see the default image.
- Prevent lock screen background motion
- This policy setting controls whether the lock screen image is static or has a subtle panning effect driven by the device's accelerometer output.
-
-If you enable this setting, motion will be prevented and the user will see the traditional static lock screen background image.
-
-If you disable this setting (and the device has an accelerometer), the user will see the lock screen background pan around a still image as they physically move their device.
- Force a specific default lock screen and logon image
- This setting allows you to force a specific default lock screen and logon image by entering the path (location) of the image file. The same image will be used for both the lock and logon screens.
-
-This setting lets you specify the default lock screen and logon image shown when no user is signed in, and also sets the specified image as the default for all users (it replaces the inbox default image).
-
-To use this setting, type the fully qualified path and name of the file that stores the default lock screen and logon image. You can type a local path, such as C:\Windows\Web\Screen\img104.jpg or a UNC path, such as \\Server\Share\Corp.jpg.
-
-This can be used in conjunction with the "Prevent changing lock screen and logon image" setting to always force the specified lock screen and logon image to be shown.
-
-Note: This setting only applies to Enterprise, Education, and Server SKUs.
- Prevent enabling lock screen camera
- Disables the lock screen camera toggle switch in PC Settings and prevents a camera from being invoked on the lock screen.
-
-By default, users can enable invocation of an available camera on the lock screen.
-
-If you enable this setting, users will no longer be able to enable or disable lock screen camera access in PC Settings, and the camera cannot be invoked on the lock screen.
- Prevent enabling lock screen slide show
- Disables the lock screen slide show settings in PC Settings and prevents a slide show from playing on the lock screen.
-
-By default, users can enable a slide show that will run after they lock the machine.
-
-If you enable this setting, users will no longer be able to modify slide show settings in PC Settings, and no slide show will ever start.
- Force a specific background and accent color
- Forces Windows to use the specified colors for the background and accent. The color values are specified in hex as #RGB.
-
-By default, users can change the background and accent colors.
-
-If this setting is enabled, the background and accent colors of Windows will be set to the specified colors and users cannot change those colors. This setting will not be applied if the specified colors do not meet a contrast ratio of 2:1 with white text.
- Force a specific Start background
- Forces the Start screen to use one of the available backgrounds, 1 through 20, and prevents the user from changing it.
-
-If this setting is set to zero or not configured, then Start uses the default background, and users can change it.
-
-If this setting is set to a nonzero value, then Start uses the specified background, and users cannot change it. If the specified background is not supported, the default background is used.
-
- Prevent changing start menu background
- Prevents users from changing the look of their start menu background, such as its color or accent.
-
-By default, users can change the look of their start menu background, such as its color or accent.
-
-If you enable this setting, the user will be assigned the default start menu background and colors and will not be allowed to change them.
-
-If the "Force a specific background and accent color" policy is also set on a supported version of Windows, then those colors take precedence over this policy.
-
-If the "Force a specific Start background" policy is also set on a supported version of Windows, then that background takes precedence over this policy.
-
-
-
-
-
-
-
-
-
- Number of seconds to wait to enable the screen saver
-
- Seconds:
-
-
-
-
-
- To select Aero type:
- %windir%\resources\Themes\Aero\aero.msstyles
-
- To select a different visual style, type:
- ie: \\<server>\share\Corp.msstyles
-
- To select Windows Classic, leave the box
- above blank and enable this setting
-
-
-
-
-
-
-
-
-
-
- Example: Using a local path: C:\windows\web\screen\lockscreen.jpg
- Example: Using a UNC path: \\Server\Share\Corp.jpg
-
- Turn off fun facts, tips, tricks, and more on lock screen
-
-
-
-
-
-
-
-
-
-
- Background ID:
-
-
-
-
diff --git a/policy_templates/en-US/Cpls.adml b/policy_templates/en-US/Cpls.adml
deleted file mode 100644
index af28430..0000000
--- a/policy_templates/en-US/Cpls.adml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- User Accounts
- Contains settings to control the behavior of User Accounts
- Apply the default account picture to all users
- This policy setting allows an administrator to standardize the account pictures for all users on a system to the default account picture. One application for this policy setting is to standardize the account pictures to a company logo.
-
-Note: The default account picture is stored at %PROGRAMDATA%\Microsoft\User Account Pictures\user.jpg. The default guest picture is stored at %PROGRAMDATA%\Microsoft\User Account Pictures\guest.jpg. If the default pictures do not exist, an empty frame is displayed.
-
-If you enable this policy setting, the default user account picture will display for all users on the system with no customization allowed.
-
-If you disable or do not configure this policy setting, users will be able to customize their account pictures.
-
-
-
-
diff --git a/policy_templates/en-US/CredSsp.adml b/policy_templates/en-US/CredSsp.adml
deleted file mode 100644
index 5994376..0000000
--- a/policy_templates/en-US/CredSsp.adml
+++ /dev/null
@@ -1,259 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow delegating default credentials
- This policy setting applies to applications using the Cred SSP component (for example: Remote Desktop Connection).
-
-This policy setting applies when server authentication was achieved by using a trusted X509 certificate or Kerberos.
-
-If you enable this policy setting, you can specify the servers to which the user's default credentials can be delegated (default credentials are those that you use when first logging on to Windows).
-
-The policy becomes effective the next time the user signs on to a computer running Windows.
-
-If you disable or do not configure (by default) this policy setting, delegation of default credentials is not permitted to any computer. Applications depending upon this delegation behavior might fail authentication. For more information, see KB.
-
-FWlink for KB:
-http://go.microsoft.com/fwlink/?LinkId=301508
-
-Note: The "Allow delegating default credentials" policy setting can be set to one or more Service Principal Names (SPNs). The SPN represents the target server to which the user credentials can be delegated. The use of a single wildcard character is permitted when specifying the SPN.
-
-For Example:
-TERMSRV/host.humanresources.fabrikam.com Remote Desktop Session Host running on host.humanresources.fabrikam.com machine
-TERMSRV/* Remote Desktop Session Host running on all machines.
-TERMSRV/*.humanresources.fabrikam.com Remote Desktop Session Host running on all machines in .humanresources.fabrikam.com
- Allow delegating default credentials with NTLM-only server authentication
- This policy setting applies to applications using the Cred SSP component (for example: Remote Desktop Connection).
-
-This policy setting applies when server authentication was achieved via NTLM.
-
-If you enable this policy setting, you can specify the servers to which the user's default credentials can be delegated (default credentials are those that you use when first logging on to Windows).
-
-If you disable or do not configure (by default) this policy setting, delegation of default credentials is not permitted to any machine.
-
-Note: The "Allow delegating default credentials with NTLM-only server authentication" policy setting can be set to one or more Service Principal Names (SPNs). The SPN represents the target server to which the user credentials can be delegated. The use of a single wildcard character is permitted when specifying the SPN.
-
-For Example:
-TERMSRV/host.humanresources.fabrikam.com Remote Desktop Session Host running on host.humanresources.fabrikam.com machine
-TERMSRV/* Remote Desktop Session Host running on all machines.
-TERMSRV/*.humanresources.fabrikam.com Remote Desktop Session Host running on all machines in .humanresources.fabrikam.com
- Allow delegating fresh credentials
- This policy setting applies to applications using the Cred SSP component (for example: Remote Desktop Connection).
-
-This policy setting applies when server authentication was achieved via a trusted X509 certificate or Kerberos.
-
-If you enable this policy setting, you can specify the servers to which the user's fresh credentials can be delegated (fresh credentials are those that you are prompted for when executing the application).
-
-If you do not configure (by default) this policy setting, after proper mutual authentication, delegation of fresh credentials is permitted to Remote Desktop Session Host running on any machine (TERMSRV/*).
-
-If you disable this policy setting, delegation of fresh credentials is not permitted to any machine.
-
-Note: The "Allow delegating fresh credentials" policy setting can be set to one or more Service Principal Names (SPNs). The SPN represents the target server to which the user credentials can be delegated. The use of a single wildcard is permitted when specifying the SPN.
-
-For Example:
-TERMSRV/host.humanresources.fabrikam.com
-Remote Desktop Session Host running on host.humanresources.fabrikam.com machine
-TERMSRV/* Remote Desktop Session Host running on all machines.
-TERMSRV/*.humanresources.fabrikam.com Remote Desktop Session Host running on all machines in .humanresources.fabrikam.com
- Allow delegating fresh credentials with NTLM-only server authentication
- This policy setting applies to applications using the Cred SSP component (for example: Remote Desktop Connection).
-
-This policy setting applies when server authentication was achieved via NTLM.
-
-If you enable this policy setting, you can specify the servers to which the user's fresh credentials can be delegated (fresh credentials are those that you are prompted for when executing the application).
-
-If you do not configure (by default) this policy setting, after proper mutual authentication, delegation of fresh credentials is permitted to Remote Desktop Session Host running on any machine (TERMSRV/*).
-
-If you disable this policy setting, delegation of fresh credentials is not permitted to any machine.
-
-Note: The "Allow delegating fresh credentials with NTLM-only server authentication" policy setting can be set to one or more Service Principal Names (SPNs). The SPN represents the target server to which the user credentials can be delegated. The use of a single wildcard character is permitted when specifying the SPN.
-
-For Example:
-TERMSRV/host.humanresources.fabrikam.com Remote Desktop Session Host running on host.humanresources.fabrikam.com machine
-TERMSRV/* Remote Desktop Session Host running on all machines.
-TERMSRV/*.humanresources.fabrikam.com Remote Desktop Session Host running on all machines in humanresources.fabrikam.com
- Allow delegating saved credentials
- This policy setting applies to applications using the Cred SSP component (for example: Remote Desktop Connection).
-
-This policy setting applies when server authentication was achieved via a trusted X509 certificate or Kerberos.
-
-If you enable this policy setting, you can specify the servers to which the user's saved credentials can be delegated (saved credentials are those that you elect to save/remember using the Windows credential manager).
-
-If you do not configure (by default) this policy setting, after proper mutual authentication, delegation of saved credentials is permitted to Remote Desktop Session Host running on any machine (TERMSRV/*).
-
-If you disable this policy setting, delegation of saved credentials is not permitted to any machine.
-
-Note: The "Allow delegating saved credentials" policy setting can be set to one or more Service Principal Names (SPNs). The SPN represents the target server to which the user credentials can be delegated. The use of a single wildcard character is permitted when specifying the SPN.
-
-For Example:
-TERMSRV/host.humanresources.fabrikam.com Remote Desktop Session Host running on host.humanresources.fabrikam.com machine
-TERMSRV/* Remote Desktop Session Host running on all machines.
-TERMSRV/*.humanresources.fabrikam.com Remote Desktop Session Host running on all machines in humanresources.fabrikam.com
- Allow delegating saved credentials with NTLM-only server authentication
- This policy setting applies to applications using the Cred SSP component (for example: Remote Desktop Connection).
-
-This policy setting applies when server authentication was achieved via NTLM.
-
-If you enable this policy setting, you can specify the servers to which the user's saved credentials can be delegated (saved credentials are those that you elect to save/remember using the Windows credential manager).
-
-If you do not configure (by default) this policy setting, after proper mutual authentication, delegation of saved credentials is permitted to Remote Desktop Session Host running on any machine (TERMSRV/*) if the client machine is not a member of any domain. If the client is domain-joined, by default the delegation of saved credentials is not permitted to any machine.
-
-If you disable this policy setting, delegation of saved credentials is not permitted to any machine.
-
-Note: The "Allow delegating saved credentials with NTLM-only server authentication" policy setting can be set to one or more Service Principal Names (SPNs). The SPN represents the target server to which the user credentials can be delegated. The use of a single wildcard character is permitted when specifying the SPN.
-
-For Example:
-TERMSRV/host.humanresources.fabrikam.com Remote Desktop Session Host running on host.humanresources.fabrikam.com machine
-TERMSRV/* Remote Desktop Session Host running on all machines.
-TERMSRV/*.humanresources.fabrikam.com Remote Desktop Session Host running on all machines in humanresources.fabrikam.com
- Credentials Delegation
- Deny delegating default credentials
- This policy setting applies to applications using the Cred SSP component (for example: Remote Desktop Connection).
-
-If you enable this policy setting, you can specify the servers to which the user's default credentials cannot be delegated (default credentials are those that you use when first logging on to Windows).
-
-If you disable or do not configure (by default) this policy setting, this policy setting does not specify any server.
-
-Note: The "Deny delegating default credentials" policy setting can be set to one or more Service Principal Names (SPNs). The SPN represents the target server to which the user credentials cannot be delegated. The use of a single wildcard character is permitted when specifying the SPN.
-
-For Example:
-TERMSRV/host.humanresources.fabrikam.com Remote Desktop Session Host running on host.humanresources.fabrikam.com machine
-TERMSRV/* Remote Desktop Session Host running on all machines.
-TERMSRV/*.humanresources.fabrikam.com Remote Desktop Session Host running on all machines in .humanresources.fabrikam.com
-
-This policy setting can be used in combination with the "Allow delegating default credentials" policy setting to define exceptions for specific servers that are otherwise permitted when using wildcard characters in the "Allow delegating default credentials" server list.
- Deny delegating fresh credentials
- This policy setting applies to applications using the Cred SSP component (for example: Remote Desktop Connection).
-
-If you enable this policy setting, you can specify the servers to which the user's fresh credentials cannot be delegated (fresh credentials are those that you are prompted for when executing the application).
-
-If you disable or do not configure (by default) this policy setting, this policy setting does not specify any server.
-
-Note: The "Deny delegating fresh credentials" policy setting can be set to one or more Service Principal Names (SPNs). The SPN represents the target server to which the user credentials cannot be delegated. The use of a single wildcard character is permitted when specifying the SPN.
-
-For Example:
-TERMSRV/host.humanresources.fabrikam.com Remote Desktop Session Host running on host.humanresources.fabrikam.com machine
-TERMSRV/* Remote Desktop Session Host running on all machines.
-TERMSRV/*.humanresources.fabrikam.com Remote Desktop Session Host running on all machines in .humanresources.fabrikam.com
-
-This policy setting can be used in combination with the "Allow delegating fresh credentials" policy setting to define exceptions for specific servers that are otherwise permitted when using wildcard characters in the "Allow delegating fresh credentials" server list.
- Deny delegating saved credentials
- This policy setting applies to applications using the Cred SSP component (for example: Remote Desktop Connection).
-
-If you enable this policy setting, you can specify the servers to which the user's saved credentials cannot be delegated (saved credentials are those that you elect to save/remember using the Windows credential manager).
-
-If you disable or do not configure (by default) this policy setting, this policy setting does not specify any server.
-
-Note: The "Deny delegating saved credentials" policy setting can be set to one or more Service Principal Names (SPNs). The SPN represents the target server to which the user credentials cannot be delegated. The use of a single wildcard character is permitted when specifying the SPN.
-
-For Example:
-TERMSRV/host.humanresources.fabrikam.com Remote Desktop Session Host running on host.humanresources.fabrikam.com machine
-TERMSRV/* Remote Desktop Session Host running on all machines.
-TERMSRV/*.humanresources.fabrikam.com Remote Desktop Session Host running on all machines in .humanresources.fabrikam.com
-
-This policy setting can be used in combination with the "Allow delegating saved credentials" policy setting to define exceptions for specific servers that are otherwise permitted when using wildcard characters in the "Allow delegating saved credentials" server list.
- Restrict delegation of credentials to remote servers
- When running in Restricted Admin or Remote Credential Guard mode, participating apps do not expose signed in or supplied credentials to a remote host. Restricted Admin limits access to resources located on other servers or networks from the remote host because credentials are not delegated. Remote Credential Guard does not limit access to resources because it redirects all requests back to the client device.
-
-Participating apps:
-Remote Desktop Client
-
-If you enable this policy setting, the following options are supported:
-
-Restrict credential delegation: Participating applications must use Restricted Admin or Remote Credential Guard to connect to remote hosts.
-
-Require Remote Credential Guard: Participating applications must use Remote Credential Guard to connect to remote hosts.
-
-Require Restricted Admin: Participating applications must use Restricted Admin to connect to remote hosts.
-
-If you disable or do not configure this policy setting, Restricted Admin and Remote Credential Guard mode are not enforced and participating apps can delegate credentials to remote devices.
-
-Note: To disable most credential delegation, it may be sufficient to deny delegation in Credential Security Support Provider (CredSSP) by modifying Administrative template settings (located at Computer Configuration\Administrative Templates\System\Credentials Delegation).
-
-Note: On Windows 8.1 and Windows Server 2012 R2, enabling this policy will enforce Restricted Administration mode, regardless of the mode chosen. These versions do not support Remote Credential Guard.
-
- Windows Vista
- Restrict Credential Delegation
- Require Remote Credential Guard
- Require Restricted Admin
- Remote host allows delegation of non-exportable credentials
- Remote host allows delegation of non-exportable credentials
-
-When using credential delegation, devices provide an exportable version of credentials to the remote host. This exposes users to the risk of credential theft from attackers on the remote host.
-
-If you enable this policy setting, the host supports Restricted Admin or Remote Credential Guard mode.
-
-If you disable or do not configure this policy setting, Restricted Administration and Remote Credential Guard mode are not supported. User will always need to pass their credentials to the host.
- Encryption Oracle Remediation
- Encryption Oracle Remediation
-
-This policy setting applies to applications using the CredSSP component (for example: Remote Desktop Connection).
-
-Some versions of the CredSSP protocol are vulnerable to an encryption oracle attack against the client. This policy controls compatibility with vulnerable clients and servers. This policy allows you to set the level of protection desired for the encryption oracle vulnerability.
-
-If you enable this policy setting, CredSSP version support will be selected based on the following options:
-
-Force Updated Clients: Client applications which use CredSSP will not be able to fall back to the insecure versions and services using CredSSP will not accept unpatched clients. Note: this setting should not be deployed until all remote hosts support the newest version.
-
-Mitigated: Client applications which use CredSSP will not be able to fall back to the insecure version but services using CredSSP will accept unpatched clients. See the link below for important information about the risk posed by remaining unpatched clients.
-
-Vulnerable: Client applications which use CredSSP will expose the remote servers to attacks by supporting fall back to the insecure versions and services using CredSSP will accept unpatched clients.
-
-For more information about the vulnerability and servicing requirements for protection, see https://go.microsoft.com/fwlink/?linkid=866660
- Force Updated Clients
- Mitigated
- Vulnerable
-
-
-
-
- Add servers to the list:
- Concatenate OS defaults with input above
-
-
- Add servers to the list:
- Concatenate OS defaults with input above
-
-
- Add servers to the list:
- Concatenate OS defaults with input above
-
-
- Add servers to the list:
- Concatenate OS defaults with input above
-
-
- Add servers to the list:
- Concatenate OS defaults with input above
-
-
- Add servers to the list:
- Concatenate OS defaults with input above
-
-
- Add servers to the list:
- Concatenate OS defaults with input above
-
-
- Add servers to the list:
- Concatenate OS defaults with input above
-
-
- Add servers to the list:
- Concatenate OS defaults with input above
-
-
- Use the following restricted mode:
-
-
-
-
- Protection Level:
-
-
-
-
-
diff --git a/policy_templates/en-US/CredUI.adml b/policy_templates/en-US/CredUI.adml
deleted file mode 100644
index 5f586af..0000000
--- a/policy_templates/en-US/CredUI.adml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Credential User Interface
- Contains settings to control the behavior of credential collection.
- Enumerate administrator accounts on elevation
- This policy setting controls whether administrator accounts are displayed when a user attempts to elevate a running application. By default, administrator accounts are not displayed when the user attempts to elevate a running application.
-
-If you enable this policy setting, all local administrator accounts on the PC will be displayed so the user can choose one and enter the correct password.
-
-If you disable this policy setting, users will always be required to type a user name and password to elevate.
- Require trusted path for credential entry
- This policy setting requires the user to enter Microsoft Windows credentials using a trusted path, to prevent a Trojan horse or other types of malicious code from stealing the user’s Windows credentials.
-
-Note: This policy affects nonlogon authentication tasks only. As a security best practice, this policy should be enabled.
-
-If you enable this policy setting, users will be required to enter Windows credentials on the Secure Desktop by means of the trusted path mechanism.
-
-If you disable or do not configure this policy setting, users will enter Windows credentials within the user’s desktop session, potentially allowing malicious code access to the user’s Windows credentials.
- Do not display the password reveal button
- This policy setting allows you to configure the display of the password reveal button in password entry user experiences.
-
-If you enable this policy setting, the password reveal button will not be displayed after a user types a password in the password entry text box.
-
-If you disable or do not configure this policy setting, the password reveal button will be displayed after a user types a password in the password entry text box.
-
-By default, the password reveal button is displayed after a user types a password in the password entry text box. To display the password, click the password reveal button.
-
-The policy applies to all Windows components and applications that use the Windows system controls, including Internet Explorer.
- Prevent the use of security questions for local accounts
- If you turn this policy setting on, local users won’t be able to set up and use security questions to reset their passwords.
-
-
-
diff --git a/policy_templates/en-US/CredentialProviders.adml b/policy_templates/en-US/CredentialProviders.adml
deleted file mode 100644
index 5475228..0000000
--- a/policy_templates/en-US/CredentialProviders.adml
+++ /dev/null
@@ -1,100 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Assign a default domain for logon
- This policy setting specifies a default logon domain, which might be a different domain than the domain to which the computer is joined. Without this policy setting, at logon, if a user does not specify a domain for logon, the domain to which the computer belongs is assumed as the default domain. For example if the computer belongs to the Fabrikam domain, the default domain for user logon is Fabrikam.
-
-If you enable this policy setting, the default logon domain is set to the specified domain, which might be different than the domain to which the computer is joined.
-
-If you disable or do not configure this policy setting, the default logon domain is always set to the domain to which the computer is joined.
- Exclude credential providers
- This policy setting allows the administrator to exclude the specified
-credential providers from use during authentication.
-
-Note: credential providers are used to process and validate user
-credentials during logon or when authentication is required.
-Windows Vista provides two default credential providers:
-Password and Smart Card. An administrator can install additional
-credential providers for different sets of credentials
-(for example, to support biometric authentication).
-
-If you enable this policy, an administrator can specify the CLSIDs
-of the credential providers to exclude from the set of installed
-credential providers available for authentication purposes.
-
-If you disable or do not configure this policy, all installed and otherwise enabled credential providers are available for authentication purposes.
- Logon
- Turn on convenience PIN sign-in
- This policy setting allows you to control whether a domain user can sign in using a convenience PIN.
-
-If you enable this policy setting, a domain user can set up and sign in with a convenience PIN.
-
-If you disable or don't configure this policy setting, a domain user can't set up and use a convenience PIN.
-
-Note: The user's domain password will be cached in the system vault when using this feature.
-
-To configure Windows Hello for Business, use the Administrative Template policies under Windows Hello for Business.
- Turn off picture password sign-in
- This policy setting allows you to control whether a domain user can sign in using a picture password.
-
-If you enable this policy setting, a domain user can't set up or sign in with a picture password.
-
-If you disable or don't configure this policy setting, a domain user can set up and use a picture password.
-
-Note that the user's domain password will be cached in the system vault when using this feature.
- Allow users to select when a password is required when resuming from connected standby
- This policy setting allows you to control whether a user can change the time before a password is required when a Connected Standby device screen turns off.
-
-If you enable this policy setting, a user on a Connected Standby device can change the amount of time after the device's screen turns off before a password is required when waking the device. The time is limited by any EAS settings or Group Policies that affect the maximum idle time before a device locks. Additionally, if a password is required when a screensaver turns on, the screensaver timeout will limit the options the user may choose.
-
-If you disable this policy setting, a user cannot change the amount of time after the device's screen turns off before a password is required when waking the device. Instead, a password is required immediately after the screen turns off.
-
-If you don't configure this policy setting on a domain-joined device, a user cannot change the amount of time after the device's screen turns off before a password is required when waking the device. Instead, a password is required immediately after the screen turns off.
-
-If you don't configure this policy setting on a workgroup device, a user on a Connected Standby device can change the amount of time after the device's screen turns off before a password is required when waking the device. The time is limited by any EAS settings or Group Policies that affect the maximum idle time before a device locks. Additionally, if a password is required when a screensaver turns on, the screensaver timeout will limit the options the user may choose.
- Assign a default credential provider
- This policy setting allows the administrator to assign a specified credential provider as the default credential provider.
-
-If you enable this policy setting, the specified credential provider is selected on other user tile.
-
-If you disable or do not configure this policy setting, the system picks the default credential provider on other user tile.
-
-Note: A list of registered credential providers and their GUIDs can be found in the registry at HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Authentication\Credential Providers.
- Turn on security key sign-in
- This policy setting allows you to control whether users can sign in using external security keys.
-
-If you enable this policy setting, users can sign in with external security keys.
-
-If you disable or don't configure this policy setting, users can't sign in with external security keys.
-
-
-
-
-
-
- Enter the name of the domain
-
-
-
-
-
- Enter the comma-separated CLSIDs for multiple credential providers
-to be excluded from use during authentication.
-
-For example: {ba0dd1d5-9754-4ba3-973c-40dce7901283},{383f1aa4-65dd-45bc-9f5a-ddd2f222f07d}
-
-
-
-
-
- Enter the CLSID of a credential provider to be the default credential provider.
-
-For example: {ba0dd1d5-9754-4ba3-973c-40dce7901283}
-
-
-
-
diff --git a/policy_templates/en-US/CtrlAltDel.adml b/policy_templates/en-US/CtrlAltDel.adml
deleted file mode 100644
index 54928b0..0000000
--- a/policy_templates/en-US/CtrlAltDel.adml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Ctrl+Alt+Del Options
- Remove Change Password
- This policy setting prevents users from changing their Windows password on demand.
-
-If you enable this policy setting, the 'Change Password' button on the Windows Security dialog box will not appear when you press Ctrl+Alt+Del.
-
-However, users are still able to change their password when prompted by the system. The system prompts users for a new password when an administrator requires a new password or their password is expiring.
- Remove Lock Computer
- This policy setting prevents users from locking the system.
-
-While locked, the desktop is hidden and the system cannot be used. Only the user who locked the system or the system administrator can unlock it.
-
-If you enable this policy setting, users cannot lock the computer from the keyboard using Ctrl+Alt+Del.
-
-If you disable or do not configure this policy setting, users will be able to lock the computer from the keyboard using Ctrl+Alt+Del.
-
-Tip:To lock a computer without configuring a setting, press Ctrl+Alt+Delete, and then click Lock this computer.
- Remove Task Manager
- This policy setting prevents users from starting Task Manager.
-
-Task Manager (taskmgr.exe) lets users start and stop programs; monitor the performance of their computers; view and monitor all programs running on their computers, including system services; find the executable names of programs; and change the priority of the process in which programs run.
-
-If you enable this policy setting, users will not be able to access Task Manager. If users try to start Task Manager, a message appears explaining that a policy prevents the action.
-
-If you disable or do not configure this policy setting, users can access Task Manager to start and stop programs, monitor the performance of their computers, view and monitor all programs running on their computers, including system services, find the executable names of programs, and change the priority of the process in which programs run.
- Remove Logoff
- This policy setting disables or removes all menu items and buttons that log the user off the system.
-
-If you enable this policy setting, users will not see the Log off menu item when they press Ctrl+Alt+Del. This will prevent them from logging off unless they restart or shutdown the computer, or clicking Log off from the Start menu.
-
-Also, see the 'Remove Logoff on the Start Menu' policy setting.
-
-If you disable or do not configure this policy setting, users can see and select the Log off menu item when they press Ctrl+Alt+Del.
-
-
-
diff --git a/policy_templates/en-US/DCOM.adml b/policy_templates/en-US/DCOM.adml
deleted file mode 100644
index a0b0b4d..0000000
--- a/policy_templates/en-US/DCOM.adml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Distributed COM
- Allow local activation security check exemptions
- Allows you to specify that local computer administrators can supplement the "Define Activation Security Check exemptions" list.
-
-If you enable this policy setting, and DCOM does not find an explicit entry for a DCOM server application id (appid) in the "Define Activation Security Check exemptions" policy (if enabled), DCOM will look for an entry in the locally configured list.
-
-If you disable this policy setting, DCOM will not look in the locally configured DCOM activation security check exemption list.
-
-If you do not configure this policy setting, DCOM will only look in the locally configured exemption list if the "Define Activation Security Check exemptions" policy is not configured.
-
- Define Activation Security Check exemptions
- Allows you to view and change a list of DCOM server application ids (appids) which are exempted from the DCOM Activation security check. DCOM uses two such lists, one configured via Group Policy through this policy setting, and the other via the actions of local computer administrators. DCOM ignores the second list when this policy setting is configured, unless the "Allow local activation security check exemptions" policy is enabled.
-
-DCOM server appids added to this policy must be listed in curly-brace format. For example: {b5dcb061-cefb-42e0-a1be-e6a6438133fe}. If you enter a non-existent or improperly formatted appid DCOM will add it to the list without checking for errors.
-
-If you enable this policy setting, you can view and change the list of DCOM activation security check exemptions defined by Group Policy settings. If you add an appid to this list and set its value to 1, DCOM will not enforce the Activation security check for that DCOM server. If you add an appid to this list and set its value to 0 DCOM will always enforce the Activation security check for that DCOM server regardless of local settings.
-
-If you disable this policy setting, the appid exemption list defined by Group Policy is deleted, and the one defined by local computer administrators is used.
-
-If you do not configure this policy setting, the appid exemption list defined by local computer administrators is used.
-
-Notes:
-
-The DCOM Activation security check is done after a DCOM server process is started, but before an object activation request is dispatched to the server process. This access check is done against the DCOM server's custom launch permission security descriptor if it exists, or otherwise against the configured defaults.
-
-If the DCOM server's custom launch permission contains explicit DENY entries this may mean that object activations that would have previously succeeded for such specified users, once the DCOM server process was up and running, might now fail instead. The proper action in this situation is to re-configure the DCOM server's custom launch permission settings for correct security settings, but this policy setting may be used in the short-term as an application compatibility deployment aid.
-
-DCOM servers added to this exemption list are only exempted if their custom launch permissions do not contain specific LocalLaunch, RemoteLaunch, LocalActivate, or RemoteActivate grant or deny entries for any users or groups. Also note, exemptions for DCOM Server Appids added to this list will apply to both 32-bit and 64-bit versions of the server if present.
- Application Compatibility Settings
-
-
-
- Enter DCOM server appids paired with an action value listed below.
- The appid should include the opening and closing curly braces.
-
- Add\remove DCOM servers to the exemption list:
-
- Values:
- 0 = The specified appid is not exempt from the Activation security check
- 1 = The specified appid is exempt from the Activation security check
-
-
-
-
diff --git a/policy_templates/en-US/DFS.adml b/policy_templates/en-US/DFS.adml
deleted file mode 100644
index 2ff187b..0000000
--- a/policy_templates/en-US/DFS.adml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Configure how often a DFS client discovers domain controllers
- This policy setting allows you to configure how often a Distributed File System (DFS) client attempts to discover domain controllers on a network. By default, a DFS client attempts to discover domain controllers every 15 minutes.
-
-If you enable this policy setting, you can configure how often a DFS client attempts to discover domain controllers. This value is specified in minutes.
-
-If you disable or do not configure this policy setting, the default value of 15 minutes applies.
-
-Note: The minimum value you can select is 15 minutes. If you try to set this setting to a value less than 15 minutes, the default value of 15 minutes is applied.
-
-
-
- Time in minutes:
-
-
-
-
diff --git a/policy_templates/en-US/DWM.adml b/policy_templates/en-US/DWM.adml
deleted file mode 100644
index 1bd95fc..0000000
--- a/policy_templates/en-US/DWM.adml
+++ /dev/null
@@ -1,66 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Desktop Window Manager
- Window Frame Coloring
- Specify a default color
- This policy setting controls the default color for window frames when the user does not specify a color.
-
-If you enable this policy setting and specify a default color, this color is used in glass window frames, if the user does not specify a color.
-
-If you disable or do not configure this policy setting, the default internal color is used, if the user does not specify a color.
-
-Note: This policy setting can be used in conjunction with the "Prevent color changes of window frames" setting, to enforce a specific color for window frames that cannot be changed by users.
- Do not allow window animations
- This policy setting controls the appearance of window animations such as those found when restoring, minimizing, and maximizing windows.
-
-If you enable this policy setting, window animations are turned off.
-
-If you disable or do not configure this policy setting, window animations are turned on.
-
-Changing this policy setting requires a logoff for it to be applied.
- Do not allow color changes
- This policy setting controls the ability to change the color of window frames.
-
-If you enable this policy setting, you prevent users from changing the default window frame color.
-
-If you disable or do not configure this policy setting, you allow users to change the default window frame color.
-
-Note: This policy setting can be used in conjunction with the "Specify a default color for window frames" policy setting, to enforce a specific color for window frames that cannot be changed by users.
- Do not allow Flip3D invocation
- This policy setting allows you to configure the accessibility of the Flip 3D feature. Flip 3D allows the user to view items on the Windows desktop as they are being flipped through in three dimensions.
-
-If you enable this policy setting, Flip 3D is inaccessible.
-
-If you disable or do not configure this policy setting, Flip 3D is accessible, if desktop composition is turned on. When Windows Flip 3D is activated with the Windows+Tab keys, a visual version of the desktop is presented and items can be flipped through to select.
-
-Changing this policy setting requires a logoff for it to be applied.
- Use solid color for Start background
- This policy setting controls the Start background visuals.
-
-If you enable this policy setting, the Start background will use a solid color.
-
-If you disable or do not configure this policy setting, the Start background will use the default visuals.
-
-Note: If this policy setting is enabled, users can continue to select a color in Start Personalization. However, setting the accent will have no effect.
-
-
-
- Alpha
- Red
- Green
- Blue
-
-
- Alpha
- Red
- Green
- Blue
-
-
-
-
diff --git a/policy_templates/en-US/DataCollection.adml b/policy_templates/en-US/DataCollection.adml
deleted file mode 100644
index 05901d5..0000000
--- a/policy_templates/en-US/DataCollection.adml
+++ /dev/null
@@ -1,234 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow Diagnostic Data
- Diagnostic data off (not recommended)
- Send required diagnostic data
- Send optional diagnostic data
- By configuring this policy setting you can adjust what diagnostic data is collected from Windows. This policy setting also restricts the user from increasing the amount of diagnostic data collection via the Settings app. The diagnostic data collected under this policy impacts the operating system and apps that are considered part of Windows and does not apply to any additional apps installed by your organization.
-
- - Diagnostic data off (not recommended). Using this value, no diagnostic data is sent from the device. This value is only supported on Enterprise, Education, and Server editions.
- - Send required diagnostic data. This is the minimum diagnostic data necessary to keep Windows secure, up to date, and performing as expected. Using this value disables the "Optional diagnostic data" control in the Settings app.
- - Send optional diagnostic data. Additional diagnostic data is collected that helps us to detect, diagnose and fix issues, as well as make product improvements. Required diagnostic data will always be included when you choose to send optional diagnostic data. Optional diagnostic data can also include diagnostic log files and crash dumps. Use the "Limit Dump Collection" and the "Limit Diagnostic Log Collection" policies for more granular control of what optional diagnostic data is sent.
-
-If you disable or do not configure this policy setting, the device will send required diagnostic data and the end user can choose whether to send optional diagnostic data from the Settings app.
-
-Note:
-The "Configure diagnostic data opt-in settings user interface" group policy can be used to prevent end users from changing their data collection settings.
-
-
- Configure Connected User Experiences and Telemetry
- With this policy setting, you can forward Connected User Experience and Telemetry requests to a proxy server.
-
-If you enable this policy setting, you can specify the FQDN or IP address of the destination device within your organization's network (and optionally a port number, if desired). The connection will be made over a Secure Sockets Layer (SSL) connection. If the named proxy fails, or if you disable or do not configure this policy setting, Connected User Experience and Telemetry data will be sent to Microsoft using the default proxy configuration.
-
-The format for this setting is <server>:<port>
-
-
- Configure the Commercial ID
- This policy setting defines the identifier used to uniquely associate this device’s diagnostic data data as belonging to a given organization. If your organization is participating in a program that requires this device to be identified as belonging to your organization then use this setting to provide that identification. The value for this setting will be provided by Microsoft as part of the onboarding process for the program.
-
-If you disable or do not configure this policy setting, then Microsoft will not be able to use this identifier to associate this machine and its diagnostic data data with your organization.
-
-
- Configure Authenticated Proxy usage for the Connected User Experience and Telemetry service
- Enable Authenticated Proxy usage
- Disable Authenticated Proxy usage
- This policy setting blocks the Connected User Experience and Telemetry service from automatically using an authenticated proxy to send data back to Microsoft on Windows 10. If you disable or do not configure this policy setting, the Connected User Experience and Telemetry service will automatically use an authenticated proxy to send data back to Microsoft. Enabling this policy will block the Connected User Experience and Telemetry service from automatically using an authenticated proxy.
-
- Limit optional diagnostic data for Desktop Analytics
- Enable Desktop Analytics collection
- Disable Desktop Analytics collection
- This policy setting, in combination with the "Allow Diagnostic Data" policy setting, enables organizations to send the minimum data required by Desktop Analytics.
-
-To enable the behavior described above, complete the following steps:
- 1. Enable this policy setting
- 2. Set the "Allow Diagnostic Data" policy to "Send optional diagnostic data"
- 3. Enable the "Limit Dump Collection" policy
- 4. Enable the "Limit Diagnostic Log Collection" policy
-
-When these policies are configured, Microsoft will collect only required diagnostic data and the events required by Desktop Analytics, which can be viewed at https://go.microsoft.com/fwlink/?linkid=2116020.
-
-If you disable or do not configure this policy setting, diagnostic data collection is determined by the "Allow Diagnostic Data" policy setting or by the end user from the Settings app.
-
-
- Allow device name to be sent in Windows diagnostic data
- This policy allows the device name to be sent to Microsoft as part of Windows diagnostic data.
-
-If you disable or do not configure this policy setting, then device name will not be sent to Microsoft as part of Windows diagnostic data.
-
-
- Configure diagnostic data opt-in settings user interface
- Disable diagnostic data opt-in settings
- Enable diagnostic data opt-in setings
- This policy setting determines whether an end user can change diagnostic data settings in the Settings app.
-
-If you set this policy setting to "Disable diagnostic data opt-in settings", diagnostic data settings are disabled in the Settings app.
-
-If you don't configure this policy setting, or you set it to "Enable diagnostic data opt-in settings", end users can change the device diagnostic settings in the Settings app.
-
-Note:
-To set a limit on the amount of diagnostic data that is sent to Microsoft by your organization, use the "Allow Diagnostic Data" policy setting.
-
-
- Configure diagnostic data opt-in change notifications
- Disable diagnostic data change notifications
- Enable diagnostic data change notifications
- This policy setting controls whether notifications are shown, following a change to diagnostic data opt-in settings, on first logon and when the changes occur in settings.
-
-If you set this policy setting to "Disable diagnostic data change notifications", diagnostic data opt-in change notifications will not appear.
-
-If you set this policy setting to "Enable diagnostic data change notifications" or don't configure this policy setting, diagnostic data opt-in change notifications appear at first logon and when the changes occur in Settings.
-
-
- Disable deleting diagnostic data
- This policy setting controls whether the Delete diagnostic data button is enabled in Diagnostic & feedback Settings page.
-
-If you enable this policy setting, the Delete diagnostic data button will be disabled in Settings page, preventing the deletion of diagnostic data collected by Microsoft from the device.
-
-If you disable or don't configure this policy setting, the Delete diagnostic data button will be enabled in Settings page, which allows people to erase all diagnostic data collected by Microsoft from that device.
-
-
- Disable diagnostic data viewer
- This policy setting controls whether users can enable and launch the Diagnostic Data Viewer from the Diagnostic & feedback Settings page.
-
-If you enable this policy setting, the Diagnostic Data Viewer will not be enabled in Settings page, and it will prevent the viewer from showing diagnostic data collected by Microsoft from the device.
-
-If you disable or don't configure this policy setting, the Diagnostic Data Viewer will be enabled in Settings page.
-
-
- Configure diagnostic data upload endpoint for Desktop Analytics
- This policy sets the upload endpoint for this device’s diagnostic data as part of the Desktop Analytics program.
-
-If your organization is participating in the program and has been instructed to configure a custom upload endpoint, then use this setting to define that endpoint.
-The value for this setting will be provided by Microsoft as part of the onboarding process for the program.
-
-
- Allow Update Compliance Processing
-
-This policy is deprecated and will only work on Windows 10 version 1809. Setting this policy will have no effect for other supported versions of Windows.
-
-This policy setting, in combination with the Allow Telemetry and Configure the Commercial ID, enables organizations to configure the device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at https://go.microsoft.com/fwlink/?linkid=2185086.
-To enable this behavior:
- 1. Enable this policy setting
- 2. Join an Azure Active Directory account to the device
- 3. Set Allow Telemetry to value 1 - Required, or higher
- 4. Set the Configure the Commercial ID setting for your Update Compliance workspace
-
-When these policies are configured, Windows diagnostic data collected from the device will be subject to Microsoft processor commitments.
-If you disable or do not configure this policy setting, devices will not appear in Update Compliance.
-
-
- Allow Desktop Analytics Processing
-
-This policy is deprecated and will only work on Windows 10 version 1809. Setting this policy will have no effect for other supported versions of Windows.
-
-This policy setting, in combination with the Allow Telemetry and Configure the Commercial ID, enables organizations to configure the device so that Microsoft is the processor for Windows diagnostic data collected from the device, subject to the Product Terms at https://go.microsoft.com/fwlink/?linkid=2185086.
-To enable this behavior:
- 1. Enable this policy setting
- 2. Join an Azure Active Directory account to the device
- 3. Set Allow Telemetry to value 1 - Required, or higher
- 4. Set the Configure the Commercial ID setting for your Desktop Analytics workspace
-
-When these policies are configured, Windows diagnostic data collected from the device will be subject to Microsoft processor commitments.
-This setting has no effect on devices unless they are properly enrolled in Desktop Analytics. If you disable this policy setting, devices will not appear in Desktop Analytics.
-
-
- Allow WUfB Cloud Processing
-
-This policy is deprecated and will only work on Windows 10 version 1809. Setting this policy will have no effect for other supported versions of Windows.
-
-This policy setting configures an Azure Active Directory joined device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at https://go.microsoft.com/fwlink/?linkid=2185086.
-To enable this behavior:
- 1. Enable this policy setting
- 2. Join an Azure Active Directory account to the device
- 3. Set Allow Telemetry to value 1 - Required, or higher
-
-When these policies are configured, Windows diagnostic data collected from the device will be subject to Microsoft processor commitments.
-If you disable or do not configure this policy setting, devices enrolled to the Windows Update for Business deployment service will not be able to take advantage of some deployment service features.
-
-
- Allow commercial data pipeline
-
-This policy is deprecated and will only work on Windows 10 version 1809. Setting this policy will have no effect for other supported versions of Windows.
-
-AllowCommercialDataPipeline configures an Azure Active Directory joined device so that Microsoft is the processor of the Windows diagnostic data collected from the device, subject to the Product Terms at https://go.microsoft.com/fwlink/?linkid=2185086.
-To enable this behavior:
- 1. Enable this policy setting
- 2. Join an Azure Active Directory account to the device
-
-Windows diagnostic data is collected when the Allow Telemetry policy setting is set to value 1 - Required or above. Configuring this setting does not change the Windows diagnostic data collection level set for the device.
-If you disable or do not configure this setting, Microsoft will be the controller of the Windows diagnostic data collected from the device and processed in accordance with Microsoft's privacy statement at https://go.microsoft.com/fwlink/?LinkId=521839 unless you have enabled policies like 'Allow Update Compliance Processing' or 'Allow Desktop Analytics Processing'.
-See the documentation at https://go.microsoft.com/fwlink/?linkid=2011107 for information on this and other policies that will result in Microsoft being the processor of Windows diagnostic data.
-
-
- Limit Diagnostic Log Collection
- This policy setting controls whether additional diagnostic logs are collected when more information is needed to troubleshoot a problem on the device. Diagnostic logs are only sent when the device has been configured to send optional diagnostic data.
-
-By enabling this policy setting, diagnostic logs will not be collected.
-
-If you disable or do not configure this policy setting, we may occasionally collect diagnostic logs if the device has been configured to send optional diagnostic data.
-
-
- Limit Dump Collection
- This policy setting limits the type of dumps that can be collected when more information is needed to troubleshoot a problem. Dumps are only sent when the device has been configured to send optional diagnostic data.
-
-By enabling this setting, Windows Error Reporting is limited to sending kernel mini dumps and user mode triage dumps.
-
-If you disable or do not configure this policy setting, we may occasionally collect full or heap dumps if the user has opted to send optional diagnostic data.
-
-
- Enable OneSettings Auditing
- This policy setting controls whether Windows records attempts to connect with the OneSettings service to the EventLog.
-
-If you enable this policy, Windows will record attempts to connect with the OneSettings service to the Microsoft\Windows\Privacy-Auditing\Operational EventLog channel.
-
-If you disable or don't configure this policy setting, Windows will not record attempts to connect with the OneSettings service to the EventLog.
-
-
- Disable OneSettings Downloads
- This policy setting controls whether Windows attempts to connect with the OneSettings service.
-
-If you enable this policy, Windows will not attempt to connect with the OneSettings Service.
-
-If you disable or don't configure this policy setting, Windows will periodically attempt to connect with the OneSettings service to download configuration settings.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/DeliveryOptimization.adml b/policy_templates/en-US/DeliveryOptimization.adml
deleted file mode 100644
index e82660e..0000000
--- a/policy_templates/en-US/DeliveryOptimization.adml
+++ /dev/null
@@ -1,345 +0,0 @@
-
-
- Delivery Optimization GP
- This file describes the Delivery Optimization GP settings
-
-
- Delivery Optimization
- Download Mode
- Specifies the download method that Delivery Optimization can use in downloads of Windows Updates, Apps and App updates.
-
-The following list shows the supported values:
-
-0 = HTTP only, no peering.
-
-1 = HTTP blended with peering behind the same NAT.
-
-2 = HTTP blended with peering across a private group. Peering occurs on devices in the same Active Directory Site (if exist) or the same domain by default. When this option is selected, peering will cross NATs. To create a custom group use Group ID in combination with Mode 2.
-
-3 = HTTP blended with Internet Peering.
-
-99 = Simple download mode with no peering. Delivery Optimization downloads using HTTP only and does not attempt to contact the Delivery Optimization cloud services.
-
-100 = Bypass mode. Windows 10: Do not use Delivery Optimization and use BITS instead. Windows 11: Deprecated, use Simple mode instead.
- HTTP only (0)
- LAN (1)
- Group (2)
- Internet (3)
- Simple (99)
- Bypass (100)
- Group ID
- Group ID must be set as a GUID. This Policy specifies an arbitrary group ID that the device belongs to.
-
-Use this if you need to create a single group for Local Network Peering for branches that are on different domains or are not on the same LAN.
-
-Note: this is a best effort optimization and should not be relied on for an authentication of identity.
- Max Cache Size (percentage)
- Specifies the maximum cache size that Delivery Optimization uses as a percentage of available disk size (1-100).
- Absolute Max Cache Size (in GB)
- Specifies the maximum size in GB of Delivery Optimization cache.
-
-This policy overrides the DOMaxCacheSize policy.
-
-The value 0 (zero) means "unlimited" cache; Delivery Optimization will clear the cache when the device runs low on disk space.
- Max Cache Age (in seconds)
- Specifies the maximum time in seconds that each file is held in the Delivery Optimization cache after downloading successfully.
-
-The value 0 (zero) means "unlimited"; Delivery Optimization will hold the files in the cache longer and make the files available for uploads to other devices, as long as the cache size has not exceeded.
- Monthly Upload Data Cap (in GB)
- Specifies the maximum total bytes in GB that Delivery Optimization is allowed to upload to Internet peers in each calendar month.
-
-The value 0 (zero) means "unlimited"; No monthly upload limit is applied if 0 is set.
- Minimum Background QoS (in KB/s)
- Specifies the minimum download QoS (Quality of Service or speed) for background downloads in KiloBytes/second.
-
-This policy affects the blending of peer and HTTP sources. Delivery Optimization complements the download from HTTP source to achieve the specified minimum QoS value.
- Modify Cache Drive
- Specifies the drive Delivery Optimization shall use for its cache.
-
-By default, %SystemDrive% is used to store the cache. The drive location can be specified using environment variables, drive letter or using a full path.
- Maximum Background Download Bandwidth (in KB/s)
- Specifies the maximum background download bandwidth in KiloBytes/second that the device can use across all concurrent download activities using Delivery Optimization.
-
-The default value 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads.
-
- Maximum Foreground Download Bandwidth (in KB/s)
- Specifies the maximum foreground download bandwidth in KiloBytes/second that the device can use across all concurrent download activities using Delivery Optimization.
-
-The default value 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for downloads.
-
- Maximum Background Download Bandwidth (percentage)
- Specifies the maximum background download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth.
-
-The default value 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for background downloads.
- Maximum Foreground Download Bandwidth (percentage)
- Specifies the maximum foreground download bandwidth that Delivery Optimization uses across all concurrent download activities as a percentage of available download bandwidth.
-
-The default value 0 (zero) means that Delivery Optimization dynamically adjusts to use the available bandwidth for foreground downloads.
- Minimum Peer Caching Content File Size (in MB)
- Specifies the minimum content file size in MB enabled to use Peer Caching.
-
-Recommended values: 1 MB to 100000 MB.
- Enable Peer Caching while the device connects via VPN
- Specify "true" to allow the device to participate in Peer Caching while connected via VPN to the domain network.
-
-This means the device can download from or upload to other domain network devices, either on VPN or on the corporate domain network.
- Minimum RAM capacity (inclusive) required to enable use of Peer Caching (in GB)
- Specifies the minimum RAM size in GB required to use Peer Caching.
-
-For example if the minimum set is 1 GB, then devices with 1 GB or higher available RAM will be allowed to use Peer caching.
-
-Recommended values: 1 GB to 4 GB.
- Minimum disk size allowed to use Peer Caching (in GB)
- Specifies the required minimum disk size (capacity in GB) for the device to use Peer Caching. The cloud service set default value will be used.
-
-Recommended values: 64 GB to 256 GB.
-
-Note: If the DOModifyCacheDrive policy is set, the disk size check will apply to the new working directory specified by this policy.
- Allow uploads while the device is on battery while under set Battery level (percentage)
- Specify any value between 1 and 100 (in percentage) to allow the device to upload data to LAN and Group peers while on DC power (Battery).
-
-The recommended value to set if you allow uploads on battery is 40 (for 40%). The device can download from peers while on battery regardless of this policy.
-
-The value 0 means "not-limited"; The cloud service set default value will be used.
- Cache Server Hostname
- This policy allows you to set one or more Microsoft Connected Cache servers that will be used by your client(s).
-
-One or more values can be added as either fully qualified domain names (FQDN) or IP addresses. To add multiple values, separate each FQDN or IP address by commas.
-
- Cache Server Hostname Source
- This policy allows you to specify how your client(s) can discover Microsoft Connected Cache servers dynamically.
-
-Options available are:
-
-0 = Disable DNS-SD.
-
-1 = DHCP Option 235.
-
-2 = DHCP Option 235 Force.
-
-If this policy is not configured, the client will attempt to automatically find a cache server using DNS-SD. If set to 0, the client will not use DNS-SD to automatically find a cache server. If set to 1 or 2, the client will query DHCP Option ID 235 and use the returned value as the Cache Server Hostname. Option 2 overrides the Cache Server Hostname policy, if configured.
- DHCP Option 235
- DHCP Option 235 Force
- Select the source of Group IDs
- Set this policy to restrict peer selection to a specific source.
-
-Options available are:
-
-1 = AD Site.
-
-2 = Authenticated domain SID.
-
-3 = DHCP Option ID.
-
-4 = DNS Suffix.
-
-5 = AAD Tenant ID.
-
-When set, the Group ID will be assigned automatically from the selected source. This policy is ignored if the GroupID policy is also set.
-
-The options set in this policy only apply to Group (2) download mode. If Group (2) isn't set as Download mode, this policy will be ignored.
-
-For option 3 - DHCP Option ID, the client will query DHCP Option ID 234 and use the returned GUID value as the Group ID.
- Unset (0)
- AD Site (1)
- Authenticated domain SID (2)
- DHCP Option ID (3)
- DNS Suffix (4)
- AAD Tenant ID (5)
- Delay background download from http (in secs)
- This policy allows you to delay the use of an HTTP source in a background download that is allowed to use P2P.
-
-After the max delay has reached, the download will resume using HTTP, either downloading the entire payload or complementing the bytes that could not be downloaded from Peers.
-
-Note that a download that is waiting for peer sources, will appear to be stuck for the end user.
-
-The recommended value is 1 hour (3600).
- Delay Foreground download from http (in secs)
- This policy allows you to delay the use of an HTTP source in a foreground (interactive) download that is allowed to use P2P.
-
-After the max delay has reached, the download will resume using HTTP, either downloading the entire payload or complementing the bytes that could not be downloaded from Peers.
-
-Note that a download that is waiting for peer sources, will appear to be stuck for the end user.
-
-The recommended value is 1 minute (60).
- Delay Background download Cache Server fallback (in seconds)
- Set this policy to delay the fallback from Cache Server to the HTTP source for a background content download by X seconds.
-
-Note: if you set the policy to delay background download from http, it will apply first (to allow downloads from peers first).
- Delay Foreground download Cache Server fallback (in seconds)
- Set this policy to delay the fallback from Cache Server to the HTTP source for a foreground content download by X seconds.
-
-Note: if you set the policy to delay foreground download from http, it will apply first (to allow downloads from peers first).
- Select a method to restrict Peer Selection
- Set this policy to restrict peer selection via selected option.
-
-Options available are:
-0 = NAT.
-1 = Subnet mask.
-2 = Local discovery (DNS-SD).
-
-The default value has changed from 0 (no restriction) to 1 (restrict to the subnet).
-
-These options apply to both Download Mode LAN (1) and Group (2).
- NAT
- Subnet
- Local discovery
- Set Business Hours to Limit Background Download Bandwidth
- Specifies the maximum background download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth.
- Set Business Hours to Limit Foreground Download Bandwidth
- Specifies the maximum foreground download bandwidth that Delivery Optimization uses during and outside business hours across all concurrent download activities as a percentage of available download bandwidth.
- 1 AM
- 1 PM
- 2 AM
- 2 PM
- 3 AM
- 3 PM
- 4 AM
- 4 PM
- 5 AM
- 5 PM
- 6 AM
- 6 PM
- 7 AM
- 7 PM
- 8 AM
- 8 PM
- 9 AM
- 9 PM
- 10 AM
- 10 PM
- 11 AM
- 11 PM
- 12 AM
- 12 PM
-
-
-
- Download Mode:
-
-
-
-
-
-
-
- Max Cache Size (Percentage):
- The default value is 20%
-
-
- Absolute Max Cache Size (in GB):
- The default value is 10GB
-
-
- Max Cache Age (in seconds):
- The default value is 7 days
-
-
- Monthly Upload Data Cap (in GB):
- The default value is 5 TB
-
-
- Minimum Background QoS (in KB/s):
- The default value is 20 MB/s
-
-
-
-
-
-
-
- Maximum Background Download Bandwidth (in KB/s):
- The default value is 0 (unlimited)
-
-
- Maximum Foreground Download Bandwidth (in KB/s):
- The default value is 0 (unlimited)
-
-
- Maximum Background Download Bandwidth (Percentage):
- The default value is 0 (unlimited)
-
-
- Maximum Foreground Download Bandwidth (Percentage):
- The default value is 0 (unlimited)
-
-
- Minimum Peer Caching Content File Size (in MB):
- The default value is 100MB
-
-
- Enable Peer Caching while the device connects via VPN
-
-
- Minimum RAM capacity (inclusive) required to enable use of Peer Caching (in GB):
- The default value is 4GB
-
-
- Minimum disk size allowed to use Peer Caching (in GB):
- The default value is 32GB
-
-
- Minimum battery level (Percentage):
- The default value is 0 (unlimited)
-
-
-
-
-
-
-
- Cache Server Hostname Source:
-
-
- Source of Group IDs:
-
-
- Delay background download from http (in secs):
- The default value is 0 (no delay)
-
-
- Delay Foreground download from http (in secs):
- The default value is 0 (no delay)
-
-
- Delay Background download Cache Server fallback (in secs):
- The default value is 0 (no delay)
-
-
- Delay Foreground download Cache Server fallback (in secs):
- The default value is 0 (no delay)
-
-
- Restrict Peer Selection By:
-
-
-
- Set Business Hours to Limit Background Download Bandwidth:
- From:
- To:
-
- Maximum Background Download Bandwidth (percentage) during Business Hours:
-
- The default value is 0 (unlimited)
-
- Maximum Background Download Bandwidth (percentage) outside of Business Hours:
-
- The default value is 0 (unlimited)
-
-
-
- Set Business Hours to Limit Foreground Download Bandwidth:
- From:
- To:
-
- Maximum Foreground Download Bandwidth (percentage) during Business Hours:
-
- The default value is 0 (unlimited)
-
- Maximum Foreground Download Bandwidth (percentage) outside of Business Hours:
-
- The default value is 0 (unlimited)
-
-
-
-
diff --git a/policy_templates/en-US/Desktop.adml b/policy_templates/en-US/Desktop.adml
deleted file mode 100644
index 1493e29..0000000
--- a/policy_templates/en-US/Desktop.adml
+++ /dev/null
@@ -1,264 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Desktop
- Active Directory
- Enable filter in Find dialog box
- Displays the filter bar above the results of an Active Directory search. The filter bar consists of buttons for applying additional filters to search results.
-
-If you enable this setting, the filter bar appears when the Active Directory Find dialog box opens, but users can hide it.
-
-If you disable this setting or do not configure it, the filter bar does not appear, but users can display it by selecting "Filter" on the "View" menu.
-
-To see the filter bar, open Network Locations, click Entire Network, and then click Directory. Right-click the name of a Windows domain, and click Find. Type the name of an object in the directory, such as "Administrator." If the filter bar does not appear above the resulting display, on the View menu, click Filter.
- Hide Active Directory folder
- Hides the Active Directory folder in Network Locations.
-
-The Active Directory folder displays Active Directory objects in a browse window.
-
-If you enable this setting, the Active Directory folder does not appear in the Network Locations folder.
-
-If you disable this setting or do not configure it, the Active Directory folder appears in the Network Locations folder.
-
-This setting is designed to let users search Active Directory but not tempt them to casually browse Active Directory.
-
- Maximum size of Active Directory searches
- Specifies the maximum number of objects the system displays in response to a command to browse or search Active Directory. This setting affects all browse displays associated with Active Directory, such as those in Local Users and Groups, Active Directory Users and Computers, and dialog boxes used to set permissions for user or group objects in Active Directory.
-
-If you enable this setting, you can use the "Number of objects returned" box to limit returns from an Active Directory search.
-
-If you disable this setting or do not configure it, the system displays up to 10,000 objects. This consumes approximately 2 MB of memory or disk space.
-
-This setting is designed to protect the network and the domain controller from the effect of expansive searches.
- Adds and deletes specified Web content items.
-
-You can use the "Add" box in this setting to add particular Web-based items or shortcuts to users' desktops. Users can close or delete the items (if settings allow), but the items are added again each time the setting is refreshed.
-
-You can also use this setting to delete particular Web-based items from users' desktops. Users can add the item again (if settings allow), but the item is deleted each time the setting is refreshed.
-
-Note: Removing an item from the "Add" list for this setting is not the same as deleting it. Items that are removed from the "Add" list are not removed from the desktop. They are simply not added again.
-
-Note: For this setting to take affect, you must log off and log on to the system.
- Removes Active Desktop content and prevents users from adding Active Desktop content.
-
-This setting removes all Active Desktop items from the desktop. It also removes the Web tab from Display in Control Panel. As a result, users cannot add Web pages or pictures from the Internet or an intranet to the desktop.
-
-Note: This setting does not disable Active Desktop. Users can still use image formats, such as JPEG and GIF, for their desktop wallpaper.
- Prohibit User from manually redirecting Profile Folders
- Prevents users from changing the path to their profile folders.
-
-By default, a user can change the location of their individual profile folders like Documents, Music etc. by typing a new path in the Locations tab of the folder's Properties dialog box.
-
-If you enable this setting, users are unable to type a new location in the Target box.
- Enable Active Desktop
- Enables Active Desktop and prevents users from disabling it.
-
-This setting prevents users from trying to enable or disable Active Desktop while a policy controls it.
-
-If you disable this setting or do not configure it, Active Desktop is disabled by default, but users can enable it.
-
-Note: If both the "Enable Active Desktop" setting and the "Disable Active Desktop" setting are enabled, the "Disable Active Desktop" setting is ignored. If the "Turn on Classic Shell" setting ( in User Configuration\Administrative Templates\Windows Components\Windows Explorer) is enabled, Active Desktop is disabled, and both of these policies are ignored.
- Disable Active Desktop
- Disables Active Desktop and prevents users from enabling it.
-
-This setting prevents users from trying to enable or disable Active Desktop while a policy controls it.
-
-If you disable this setting or do not configure it, Active Desktop is disabled by default, but users can enable it.
-
-Note: If both the "Enable Active Desktop" setting and the "Disable Active Desktop" setting are enabled, the "Disable Active Desktop" setting is ignored. If the "Turn on Classic Shell" setting (in User Configuration\Administrative Templates\Windows Components\Windows Explorer) is enabled, Active Desktop is disabled, and both these policies are ignored.
- Prohibit changes
- Prevents the user from enabling or disabling Active Desktop or changing the Active Desktop configuration.
-
-This is a comprehensive setting that locks down the configuration you establish by using other policies in this folder. This setting removes the Web tab from Display in Control Panel. As a result, users cannot enable or disable Active Desktop. If Active Desktop is already enabled, users cannot add, remove, or edit Web content or disable, lock, or synchronize Active Desktop components.
- Prevents users from adding Web content to their Active Desktop.
-
-This setting removes the "New" button from Web tab in Display in Control Panel. As a result, users cannot add Web pages or pictures from the Internet or an intranet to the desktop. This setting does not remove existing Web content from their Active Desktop, or prevent users from removing existing Web content.
-
-Also, see the "Disable all items" setting.
- Prevents users from manipulating desktop toolbars.
-
-If you enable this setting, users cannot add or remove toolbars from the desktop. Also, users cannot drag toolbars on to or off of docked toolbars.
-
-Note: If users have added or removed toolbars, this setting prevents them from restoring the default configuration.
-
-Tip: To view the toolbars that can be added to the desktop, right-click a docked toolbar (such as the taskbar beside the Start button), and point to "Toolbars."
-
-Also, see the "Prohibit adjusting desktop toolbars" setting.
- Prevents users from removing Web content from their Active Desktop.
-
-In Active Desktop, you can add items to the desktop but close them so they are not displayed.
-
-If you enable this setting, items added to the desktop cannot be closed; they always appear on the desktop. This setting removes the check boxes from items on the Web tab in Display in Control Panel.
-
-Note: This setting does not prevent users from deleting items from their Active Desktop.
- Prevents users from deleting Web content from their Active Desktop.
-
-This setting removes the Delete button from the Web tab in Display in Control Panel. As a result, users can temporarily remove, but not delete, Web content from their Active Desktop.
-
-This setting does not prevent users from adding Web content to their Active Desktop.
-
-Also, see the "Prohibit closing items" and "Disable all items" settings.
- Hide and disable all items on the desktop
- Removes icons, shortcuts, and other default and user-defined items from the desktop, including Briefcase, Recycle Bin, Computer, and Network Locations.
-
-Removing icons and shortcuts does not prevent the user from using another method to start the programs or opening the items they represent.
-
-Also, see "Items displayed in Places Bar" in User Configuration\Administrative Templates\Windows Components\Common Open File Dialog to remove the Desktop icon from the Places Bar. This will help prevent users from saving data to the Desktop.
- Remove the Desktop Cleanup Wizard
- Prevents users from using the Desktop Cleanup Wizard.
-
-If you enable this setting, the Desktop Cleanup wizard does not automatically run on a users workstation every 60 days. The user will also not be able to access the Desktop Cleanup Wizard.
-
-If you disable this setting or do not configure it, the default behavior of the Desktop Clean Wizard running every 60 days occurs.
-
-Note: When this setting is not enabled, users can run the Desktop Cleanup Wizard, or have it run automatically every 60 days from Display, by clicking the Desktop tab and then clicking the Customize Desktop button.
- Prevents users from changing the properties of Web content items on their Active Desktop.
-
-This setting disables the Properties button on the Web tab in Display in Control Panel. Also, it removes the Properties item from the menu for each item on the Active Desktop. As a result, users cannot change the properties of an item, such as its synchronization schedule, password, or display characteristics.
- Permits only bitmap images for wallpaper. This setting limits the desktop background ("wallpaper") to bitmap (.bmp) files. If users select files with other image formats, such as JPEG, GIF, PNG, or HTML, through the Browse button on the Desktop tab, the wallpaper does not load. Files that are autoconverted to a .bmp format, such as JPEG, GIF, and PNG, can be set as Wallpaper by right-clicking the image and selecting "Set as Wallpaper".
-
-Also, see the "Desktop Wallpaper" and the "Prevent changing wallpaper" (in User Configuration\Administrative Templates\Control Panel\Display) settings.
- Hide Internet Explorer icon on desktop
- Removes the Internet Explorer icon from the desktop and from the Quick Launch bar on the taskbar.
-
-This setting does not prevent the user from starting Internet Explorer by using other methods.
- Prevents users from adjusting the length of desktop toolbars. Also, users cannot reposition items or toolbars on docked toolbars.
-
-This setting does not prevent users from adding or removing toolbars on the desktop.
-
-Note: If users have adjusted their toolbars, this setting prevents them from restoring the default configuration.
-
-Also, see the "Prevent adding, dragging, dropping and closing the Taskbar's toolbars" setting.
- Remove Computer icon on the desktop
- This setting hides Computer from the desktop and from the new Start menu. It also hides links to Computer in the Web view of all Explorer windows, and it hides Computer in the Explorer folder tree pane. If the user navigates into Computer via the "Up" button while this setting is enabled, they view an empty Computer folder. This setting allows administrators to restrict their users from seeing Computer in the shell namespace, allowing them to present their users with a simpler desktop environment.
-
-If you enable this setting, Computer is hidden on the desktop, the new Start menu, the Explorer folder tree pane, and the Explorer Web views. If the user manages to navigate to Computer, the folder will be empty.
-
-If you disable this setting, Computer is displayed as usual, appearing as normal on the desktop, Start menu, folder tree pane, and Web views, unless restricted by another setting.
-
-If you do not configure this setting, the default is to display Computer as usual.
-
-Note: In operating systems earlier than Microsoft Windows Vista, this policy applies to the My Computer icon. Hiding Computer and its contents does not hide the contents of the child folders of Computer. For example, if the users navigate into one of their hard drives, they see all of their folders and files there, even if this setting is enabled.
- Remove My Documents icon on the desktop
- Removes most occurrences of the My Documents icon.
-
-This setting removes the My Documents icon from the desktop, from File Explorer, from programs that use the File Explorer windows, and from the standard Open dialog box.
-
-This setting does not prevent the user from using other methods to gain access to the contents of the My Documents folder.
-
-This setting does not remove the My Documents icon from the Start menu. To do so, use the "Remove My Documents icon from Start Menu" setting.
-
-Note: To make changes to this setting effective, you must log off from and log back on to Windows 2000 Professional.
- Hide Network Locations icon on desktop
- Removes the Network Locations icon from the desktop.
-
-This setting only affects the desktop icon. It does not prevent users from connecting to the network or browsing for shared computers on the network.
-
-Note: In operating systems earlier than Microsoft Windows Vista, this policy applies to the My Network Places icon.
- Remove Properties from the Computer icon context menu
- This setting hides Properties on the context menu for Computer.
-
-If you enable this setting, the Properties option will not be present when the user right-clicks My Computer or clicks Computer and then goes to the File menu. Likewise, Alt-Enter does nothing when Computer is selected.
-
-If you disable or do not configure this setting, the Properties option is displayed as usual.
- Remove Properties from the Documents icon context menu
- This policy setting hides the Properties menu command on the shortcut menu for the My Documents icon.
-
-If you enable this policy setting, the Properties menu command will not be displayed when the user does any of the following:
-
-Right-clicks the My Documents icon.
-Clicks the My Documents icon, and then opens the File menu.
-Clicks the My Documents icon, and then presses ALT+ENTER.
-
-If you disable or do not configure this policy setting, the Properties menu command is displayed.
- Do not add shares of recently opened documents to Network Locations
- Remote shared folders are not added to Network Locations whenever you open a document in the shared folder.
-
-If you disable this setting or do not configure it, when you open a document in a remote shared folder, the system adds a connection to the shared folder to Network Locations.
-
-If you enable this setting, shared folders are not added to Network Locations automatically when you open a document in the shared folder.
- Remove Recycle Bin icon from desktop
- Removes most occurrences of the Recycle Bin icon.
-
-This setting removes the Recycle Bin icon from the desktop, from File Explorer, from programs that use the File Explorer windows, and from the standard Open dialog box.
-
-This setting does not prevent the user from using other methods to gain access to the contents of the Recycle Bin folder.
-
-Note: To make changes to this setting effective, you must log off and then log back on.
- Remove Properties from the Recycle Bin context menu
- Removes the Properties option from the Recycle Bin context menu.
-
-If you enable this setting, the Properties option will not be present when the user right-clicks on Recycle Bin or opens Recycle Bin and then clicks File. Likewise, Alt-Enter does nothing when Recycle Bin is selected.
-
-If you disable or do not configure this setting, the Properties option is displayed as usual.
- Don't save settings at exit
- Prevents users from saving certain changes to the desktop.
-
-If you enable this setting, users can change the desktop, but some changes, such as the position of open windows or the size and position of the taskbar, are not saved when users log off. However, shortcuts placed on the desktop are always saved.
- Add/Delete items
- Prohibit adding items
- Prohibit closing items
- Prohibit deleting items
- Prohibit editing items
- Disable all items
- Prevent adding, dragging, dropping and closing the Taskbar's toolbars
- Prohibit adjusting desktop toolbars
- Allow only bitmapped wallpaper
- Desktop Wallpaper
- Specifies the desktop background ("wallpaper") displayed on all users' desktops.
-
-This setting lets you specify the wallpaper on users' desktops and prevents users from changing the image or its presentation. The wallpaper you specify can be stored in a bitmap (*.bmp) or JPEG (*.jpg) file.
-
-To use this setting, type the fully qualified path and name of the file that stores the wallpaper image. You can type a local path, such as C:\Windows\web\wallpaper\home.jpg or a UNC path, such as \\Server\Share\Corp.jpg. If the specified file is not available when the user logs on, no wallpaper is displayed. Users cannot specify alternative wallpaper. You can also use this setting to specify that the wallpaper image be centered, tiled, or stretched. Users cannot change this specification.
-
-If you disable this setting or do not configure it, no wallpaper is displayed. However, users can select the wallpaper of their choice.
-
-Also, see the "Allow only bitmapped wallpaper" in the same location, and the "Prevent changing wallpaper" setting in User Configuration\Administrative Templates\Control Panel.
-
-Note: This setting does not apply to remote desktop server sessions.
- Center
- Stretch
- Tile
- Fit
- Fill
- Span
- Turn off Aero Shake window minimizing mouse gesture
- Prevents windows from being minimized or restored when the active window is shaken back and forth with the mouse.
-
-If you enable this policy, application windows will not be minimized or restored when the active window is shaken back and forth with the mouse.
-
-If you disable or do not configure this policy, this window minimizing and restoring gesture will apply.
-
-
-
- Number of objects returned:
-
-
- Allows HTML and JPEG Wallpaper
-
-
- Disallows HTML and Jpg Wallpaper
-
-
-
-
-
-
-
-
-
-
-
-
-
- Example: Using a local path: C:\windows\web\wallpaper\home.jpg
- Example: Using a UNC path: \\Server\Share\Corp.jpg
- Wallpaper Style:
-
-
-
-
diff --git a/policy_templates/en-US/DesktopAppInstaller.adml b/policy_templates/en-US/DesktopAppInstaller.adml
deleted file mode 100644
index 3a9ce3c..0000000
--- a/policy_templates/en-US/DesktopAppInstaller.adml
+++ /dev/null
@@ -1,97 +0,0 @@
-
-
-
- App Installer
- App Installer
-
-
- Desktop App Installer
- Enable App Installer
- This policy controls whether the Windows Package Manager can be used by users.
-
-If you enable or do not configure this setting, users will be able to use the Windows Package Manager.
-
-If you disable this setting, users will not be able to use the Windows Package Manager.
- Enable App Installer Settings
- This policy controls whether users can change their settings.
-
-If you enable or do not configure this setting, users will be able to change settings for the Windows Package Manager.
-
-If you disable this setting, users will not be able to change settings for the Windows Package Manager.
- Enable App Installer Experimental Features
- This policy controls whether users can enable experimental features in the Windows Package Manager.
-
-If you enable or do not configure this setting, users will be able to enable experimental features for the Windows Package Manager.
-
-If you disable this setting, users will not be able to enable experimental features for the Windows Package Manager.
- Enable App Installer Local Manifest Files
- This policy controls whether users can install packages with local manifest files.
-
-If you enable or do not configure this setting, users will be able to install packages with local manifests using the Windows Package Manager.
-
-If you disable this setting, users will not be able to install packages with local manifests using the Windows Package Manager.
- Enable App Installer Hash Override
- This policy controls whether or not the Windows Package Manager can be configured to enable the ability override the SHA256 security validation in settings.
-
-If you enable or do not configure this policy, users will be able to enable the ability override the SHA256 security validation in the Windows Package Manager settings.
-
-If you disable this policy, users will not be able to enable the ability override the SHA256 security validation in the Windows Package Manager settings.
- Enable App Installer Default Source
- This policy controls the default source included with the Windows Package Manager.
-
-If you do not configure this setting, the default source for the Windows Package Manager will be available and can be removed.
-
-If you enable this setting, the default source for the Windows Package Manager will be available and cannot be removed.
-
-If you disable this setting the default source for the Windows Package Manager will not be available.
- Enable App Installer Microsoft Store Source
- This policy controls the Microsoft Store source included with the Windows Package Manager.
-
-If you do not configure this setting, the Microsoft Store source for the Windows Package manager will be available and can be removed.
-
-If you enable this setting, the Microsoft Store source for the Windows Package Manager will be available and cannot be removed.
-
-If you disable this setting the Microsoft Store source for the Windows Package Manager will not be available.
- Set App Installer Source Auto Update Interval In Minutes
- This policy controls the auto update interval for package-based sources.
-
-If you disable or do not configure this setting, the default interval or the value specified in settings will be used by the Windows Package Manager.
-
-If you enable this setting, the number of minutes specified will be used by the Windows Package Manager.
- Enable App Installer Additional Sources
- This policy controls additional sources provided by the enterprise IT administrator.
-
-If you do not configure this policy, no additional sources will be configured for the Windows Package Manager.
-
-If you enable this policy, the additional sources will be added to the Windows Package Manager and cannot be removed. The representation for each additional source can be obtained from installed sources using 'winget source export'.
-
-If you disable this policy, no additional sources can be configured for the Windows Package Manager.
- Enable App Installer Allowed Sources
- This policy controls additional sources allowed by the enterprise IT administrator.
-
-If you do not configure this policy, users will be able to add or remove additional sources other than those configured by policy.
-
-If you enable this policy, only the sources specified can be added or removed from the Windows Package Manager. The representation for each allowed source can be obtained from installed sources using 'winget source export'.
-
-If you disable this policy, no additional sources can be configured for the Windows Package Manager.
- Enable App Installer ms-appinstaller protocol
- This policy controls whether users can install packages from a website that is using the ms-appinstaller protocol.
-
-If you enable or do not configure this setting, users will be able to install packages from websites that use this protocol.
-
-If you disable this setting, users will not be able to install packages from websites that use this protocol.
-
-
-
- Source Auto Update Interval In Minutes
-
-
- Additional Sources:
-
-
- Allowed Sources:
-
-
-
-
diff --git a/policy_templates/en-US/DeviceCompat.adml b/policy_templates/en-US/DeviceCompat.adml
deleted file mode 100644
index b4b491b..0000000
--- a/policy_templates/en-US/DeviceCompat.adml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Device and Driver Compatibility
- Device compatibility settings
- Driver compatibility settings
- Changes behavior of Microsoft bus drivers to work with specific devices.
- Changes behavior of 3rd-party drivers to work around incompatibilities introduced between OS versions.
-
-
-
diff --git a/policy_templates/en-US/DeviceCredential.adml b/policy_templates/en-US/DeviceCredential.adml
deleted file mode 100644
index ee3292a..0000000
--- a/policy_templates/en-US/DeviceCredential.adml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Microsoft Secondary Authentication Factor
- Configuration for Microsoft Microsoft Secondary Authentication Factor
-
-
- Microsoft Secondary Authentication Factor
- Allow companion device for secondary authentication
- This policy allows users to use a companion device, such as a phone, fitness band, or IoT device, to sign on to a desktop computer running Windows 10. The companion device provides a second factor of authentication with Windows Hello.
-
-If you enable or do not configure this policy setting, users can authenticate to Windows Hello using a companion device.
-
-If you disable this policy, users cannot use a companion device to authenticate with Windows Hello.
-
-
-
diff --git a/policy_templates/en-US/DeviceGuard.adml b/policy_templates/en-US/DeviceGuard.adml
deleted file mode 100644
index 6bcb149..0000000
--- a/policy_templates/en-US/DeviceGuard.adml
+++ /dev/null
@@ -1,114 +0,0 @@
-
-
-
- Microsoft Windows Device Guard
- Windows Device Guard Security
-
-
- Device Guard
- Turn On Virtualization Based Security
- Specifies whether Virtualization Based Security is enabled.
-
-Virtualization Based Security uses the Windows Hypervisor to provide support for security services. Virtualization Based Security requires Secure Boot, and can optionally be enabled with the use of DMA Protections. DMA protections require hardware support and will only be enabled on correctly configured devices.
-
-Virtualization Based Protection of Code Integrity
-
-This setting enables virtualization based protection of Kernel Mode Code Integrity. When this is enabled, kernel mode memory protections are enforced and the Code Integrity validation path is protected by the Virtualization Based Security feature.
-
-The "Disabled" option turns off Virtualization Based Protection of Code Integrity remotely if it was previously turned on with the "Enabled without lock" option.
-
-The "Enabled with UEFI lock" option ensures that Virtualization Based Protection of Code Integrity cannot be disabled remotely. In order to disable the feature, you must set the Group Policy to "Disabled" as well as remove the security functionality from each computer, with a physically present user, in order to clear configuration persisted in UEFI.
-
-The "Enabled without lock" option allows Virtualization Based Protection of Code Integrity to be disabled remotely by using Group Policy.
-
-The "Not Configured" option leaves the policy setting undefined. Group Policy does not write the policy setting to the registry, and so it has no impact on computers or users. If there is a current setting in the registry it will not be modified.
-
-The "Require UEFI Memory Attributes Table" option will only enable Virtualization Based Protection of Code Integrity on devices with UEFI firmware support for the Memory Attributes Table. Devices without the UEFI Memory Attributes Table may have firmware that is incompatible with Virtualization Based Protection of Code Integrity which in some cases can lead to crashes or data loss or incompatibility with certain plug-in cards. If not setting this option the targeted devices should be tested to ensure compatibility.
-
-Warning: All drivers on the system must be compatible with this feature or the system may crash. Ensure that this policy setting is only deployed to computers which are known to be compatible.
-
-Credential Guard
-
-This setting lets users turn on Credential Guard with virtualization-based security to help protect credentials.
-
-For Windows 11 21H2 and earlier, the "Disabled" option turns off Credential Guard remotely if it was previously turned on with the "Enabled without lock" option. For later versions, the "Disabled" option turns off Credential Guard remotely if it was previously turned on with the "Enabled without lock" option or was "Not Configured".
-
-The "Enabled with UEFI lock" option ensures that Credential Guard cannot be disabled remotely. In order to disable the feature, you must set the Group Policy to "Disabled" as well as remove the security functionality from each computer, with a physically present user, in order to clear configuration persisted in UEFI.
-
-The "Enabled without lock" option allows Credential Guard to be disabled remotely by using Group Policy. The devices that use this setting must be running at least Windows 10 (Version 1511).
-
-For Windows 11 21H2 and earlier, the "Not Configured" option leaves the policy setting undefined. Group Policy does not write the policy setting to the registry, and so it has no impact on computers or users. If there is a current setting in the registry it will not be modified. For later versions, if there is no current setting in the registry, the "Not Configured" option will enable Credential Guard without UEFI lock.
-
-Secure Launch
-
-This setting sets the configuration of Secure Launch to secure the boot chain.
-
-The "Not Configured" setting is the default, and allows configuration of the feature by Administrative users.
-
-The "Enabled" option turns on Secure Launch on supported hardware.
-
-The "Disabled" option turns off Secure Launch, regardless of hardware support.
-
-Kernel-mode Hardware-enforced Stack Protection
-
-This setting enables Hardware-enforced Stack Protection for kernel-mode code. When this security feature is enabled, kernel-mode data stacks are hardened with hardware-based shadow stacks, which store intended return address targets to ensure that program control flow is not tampered.
-
-This security feature has the following prerequisites:
-1) The CPU hardware supports hardware-based shadow stacks.
-2) Virtualization Based Protection of Code Integrity is enabled.
-
-If either prerequisite is not met, this feature will not be enabled, even if an "Enabled" option is selected for this feature. Note that selecting an "Enabled" option for this feature will not automatically enable Virtualization Based Protection of Code Integrity, that needs to be done separately.
-
-Devices that enable this security feature must be running at least Windows 11 (Version 22H2).
-
-The "Disabled" option turns off kernel-mode Hardware-enforced Stack Protection.
-
-The "Enabled in audit mode" option enables kernel-mode Hardware-enforced Stack Protection in audit mode, where shadow stack violations are not fatal and will be logged to the system event log.
-
-The "Enabled in enforcement mode" option enables kernel-mode Hardware-enforced Stack Protection in enforcement mode, where shadow stack violations are fatal.
-
-The "Not Configured" option leaves the policy setting undefined. Group Policy does not write the policy setting to the registry, and so it has no impact on computers or users. If there is a current setting in the registry it will not be modified.
-
-Warning: All drivers on the system must be compatible with this security feature or the system may crash in enforcement mode. Audit mode can be used to discover incompatible drivers. For more information, refer to https://go.microsoft.com/fwlink/?LinkId=2162953.
-
- Secure Boot
- Secure Boot and DMA Protection
- Disabled
- Enabled
- Enabled without lock
- Enabled with UEFI lock
- Enabled in audit mode
- Enabled in enforcement mode
- Not Configured
- Deploy Windows Defender Application Control
- Deploy Windows Defender Application Control
-
-This policy setting lets you deploy a Code Integrity Policy to a machine to control what is allowed to run on that machine.
-
-If you deploy a Code Integrity Policy, Windows will restrict what can run in both kernel mode and on the Windows Desktop based on the policy. To enable this policy the machine must be rebooted.
-
-The file path must be either a UNC path (for example, \\ServerName\ShareName\SIPolicy.p7b), or a locally valid path (for example, C:\FolderName\SIPolicy.p7b). The local machine account (LOCAL SYSTEM) must have access permission to the policy file.
-
-If using a signed and protected policy then disabling this policy setting doesn't remove the feature from the computer. Instead, you must either:
-
- 1) first update the policy to a non-protected policy and then disable the setting, or
- 2) disable the setting and then remove the policy from each computer, with a physically present user.
-
-
-
-
- Select Platform Security Level:
- Virtualization Based Protection of Code Integrity:
- Require UEFI Memory Attributes Table
- Credential Guard Configuration:
- Secure Launch Configuration:
- Kernel-mode Hardware-enforced Stack Protection:
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/DeviceInstallation.adml b/policy_templates/en-US/DeviceInstallation.adml
deleted file mode 100644
index 8fd3ea0..0000000
--- a/policy_templates/en-US/DeviceInstallation.adml
+++ /dev/null
@@ -1,263 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow administrators to override Device Installation Restriction policies
- This policy setting allows you to determine whether members of the Administrators group can install and update the drivers for any device, regardless of other policy settings.
-
-If you enable this policy setting, members of the Administrators group can use the Add Hardware wizard or the Update Driver wizard to install and update the drivers for any device. If you enable this policy setting on a remote desktop server, the policy setting affects redirection of the specified devices from a remote desktop client to the remote desktop server.
-
-If you disable or do not configure this policy setting, members of the Administrators group are subject to all policy settings that restrict device installation.
- Prioritize all digitally signed drivers equally during the driver ranking and selection process
- This policy setting allows you to determine how drivers signed by a Microsoft Windows Publisher certificate are ranked with drivers signed by other valid Authenticode signatures during the driver selection and installation process. Regardless of this policy setting, a signed driver is still preferred over a driver that is not signed at all.
-
-If you enable or do not configure this policy setting, drivers that are signed by a Microsoft Windows Publisher certificate and drivers that are signed by other Authenticode certificates are prioritized equally during the driver selection process. Selection is based on other criteria, such as version number or when the driver was created.
-
-If you disable this policy setting, drivers that are signed by a Microsoft Windows Publisher certificate are selected for installation over drivers that are signed by other Authenticode certificates.
- Device Installation
- Allow installation of devices using drivers that match these device setup classes
- This policy setting allows you to specify a list of device setup class globally unique identifiers (GUIDs) for driver packages that Windows is allowed to install. This policy setting is intended to be used only when the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting is enabled, however it may also be used with the "Prevent installation of devices not described by other policy settings" policy setting for legacy policy definitions.
-
-When this policy setting is enabled together with the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting, Windows is allowed to install or update driver packages whose device setup class GUIDs appear in the list you create, unless another policy setting at the same or higher layer in the hierarchy specifically prevents that installation, such as the following policy settings:
-- Prevent installation of devices for these device classes
-- Prevent installation of devices that match these device IDs
-- Prevent installation of devices that match any of these device instance IDs
-If the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting is not enabled with this policy setting, then any other policy settings specifically preventing installation will take precedence.
-
-NOTE: The "Prevent installation of devices not described by other policy settings" policy setting has been replaced by the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting for supported target Windows 10 versions. It is recommended that you use the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting when possible.
-
-Alternatively, if this policy setting is enabled together with the "Prevent installation of devices not described by other policy settings" policy setting, Windows is allowed to install or update driver packages whose device setup class GUIDs appear in the list you create, unless another policy setting specifically prevents installation (for example, the "Prevent installation of devices that match these device IDs" policy setting, the "Prevent installation of devices for these device classes" policy setting, the "Prevent installation of devices that match any of these device instance IDs" policy setting, or the "Prevent installation of removable devices" policy setting).
-
-If you enable this policy setting on a remote desktop server, the policy setting affects redirection of the specified devices from a remote desktop client to the remote desktop server.
-
-If you disable or do not configure this policy setting, and no other policy setting describes the device, the "Prevent installation of devices not described by other policy settings" policy setting determines whether the device can be installed.
- Prevent installation of devices using drivers that match these device setup classes
- This policy setting allows you to specify a list of device setup class globally unique identifiers (GUIDs) for driver packages that Windows is prevented from installing. By default, this policy setting takes precedence over any other policy setting that allows Windows to install a device.
-
-NOTE: To enable the "Allow installation of devices that match any of these device IDs" and "Allow installation of devices that match any of these device instance IDs" policy settings to supersede this policy setting for applicable devices, enable the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting.
-
-If you enable this policy setting, Windows is prevented from installing or updating driver packages whose device setup class GUIDs appear in the list you create. If you enable this policy setting on a remote desktop server, the policy setting affects redirection of the specified devices from a remote desktop client to the remote desktop server.
-
-If you disable or do not configure this policy setting, Windows can install and update devices as allowed or prevented by other policy settings.
- Policy settings that control the installation of devices.
- Allow installation of devices that match any of these device IDs
- This policy setting allows you to specify a list of Plug and Play hardware IDs and compatible IDs for devices that Windows is allowed to install. This policy setting is intended to be used only when the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting is enabled, however it may also be used with the "Prevent installation of devices not described by other policy settings" policy setting for legacy policy definitions.
-
-When this policy setting is enabled together with the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting, Windows is allowed to install or update any device whose Plug and Play hardware ID or compatible ID appears in the list you create, unless another policy setting at the same or higher layer in the hierarchy specifically prevents that installation, such as the following policy settings:
-- Prevent installation of devices that match these device IDs
-- Prevent installation of devices that match any of these device instance IDs
-If the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting is not enabled with this policy setting, then any other policy settings specifically preventing installation will take precedence.
-
-NOTE: The "Prevent installation of devices not described by other policy settings" policy setting has been replaced by the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting for supported target Windows 10 versions. It is recommended that you use the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting when possible.
-
-Alternatively, if this policy setting is enabled together with the "Prevent installation of devices not described by other policy settings" policy setting, Windows is allowed to install or update any device whose Plug and Play hardware ID or compatible ID appears in the list you create, unless another policy setting specifically prevents that installation (for example, the "Prevent installation of devices that match any of these device IDs" policy setting, the "Prevent installation of devices for these device classes" policy setting, the "Prevent installation of devices that match any of these device instance IDs" policy setting, or the "Prevent installation of removable devices" policy setting).
-
-If you enable this policy setting on a remote desktop server, the policy setting affects redirection of the specified devices from a remote desktop client to the remote desktop server.
-
-If you disable or do not configure this policy setting, and no other policy setting describes the device, the "Prevent installation of devices not described by other policy settings" policy setting determines whether the device can be installed.
- Prevent installation of devices that match any of these device IDs
- This policy setting allows you to specify a list of Plug and Play hardware IDs and compatible IDs for devices that Windows is prevented from installing. By default, this policy setting takes precedence over any other policy setting that allows Windows to install a device.
-
-NOTE: To enable the "Allow installation of devices that match any of these device instance IDs" policy setting to supersede this policy setting for applicable devices, enable the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting.
-
-If you enable this policy setting, Windows is prevented from installing a device whose hardware ID or compatible ID appears in the list you create. If you enable this policy setting on a remote desktop server, the policy setting affects redirection of the specified devices from a remote desktop client to the remote desktop server.
-
-If you disable or do not configure this policy setting, devices can be installed and updated as allowed or prevented by other policy settings.
- Allow installation of devices that match any of these device instance IDs
- This policy setting allows you to specify a list of Plug and Play device instance IDs for devices that Windows is allowed to install. This policy setting is intended to be used only when the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting is enabled, however it may also be used with the "Prevent installation of devices not described by other policy settings" policy setting for legacy policy definitions.
-
-When this policy setting is enabled together with the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting, Windows is allowed to install or update any device whose Plug and Play device instance ID appears in the list you create, unless another policy setting at the same or higher layer in the hierarchy specifically prevents that installation, such as the following policy settings:
-- Prevent installation of devices that match any of these device instance IDs
-If the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting is not enabled with this policy setting, then any other policy settings specifically preventing installation will take precedence.
-
-NOTE: The "Prevent installation of devices not described by other policy settings" policy setting has been replaced by the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting for supported target Windows 10 versions. It is recommended that you use the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting when possible.
-
-Alternatively, if this policy setting is enabled together with the "Prevent installation of devices not described by other policy settings" policy setting, Windows is allowed to install or update any device whose Plug and Play device instance ID appears in the list you create, unless another policy setting specifically prevents that installation (for example, the "Prevent installation of devices that match any of these device IDs" policy setting, the "Prevent installation of devices for these device classes" policy setting, the "Prevent installation of devices that match any of these device instance IDs" policy setting, or the "Prevent installation of removable devices" policy setting).
-
-If you enable this policy setting on a remote desktop server, the policy setting affects redirection of the specified devices from a remote desktop client to the remote desktop server.
-
-If you disable or do not configure this policy setting, and no other policy setting describes the device, the "Prevent installation of devices not described by other policy settings" policy setting determines whether the device can be installed.
- Prevent installation of devices that match any of these device instance IDs
- This policy setting allows you to specify a list of Plug and Play device instance IDs for devices that Windows is prevented from installing. This policy setting takes precedence over any other policy setting that allows Windows to install a device.
-
-If you enable this policy setting, Windows is prevented from installing a device whose device instance ID appears in the list you create. If you enable this policy setting on a remote desktop server, the policy setting affects redirection of the specified devices from a remote desktop client to the remote desktop server.
-
-If you disable or do not configure this policy setting, devices can be installed and updated as allowed or prevented by other policy settings.
- Configure device installation time-out
- This policy setting allows you to configure the number of seconds Windows waits for a device installation task to complete.
-
-If you enable this policy setting, Windows waits for the number of seconds you specify before terminating the installation.
-
-If you disable or do not configure this policy setting, Windows waits 240 seconds for a device installation task to complete before terminating the installation.
- Prevent installation of removable devices
- This policy setting allows you to prevent Windows from installing removable devices. A device is considered removable when the driver for the device to which it is connected indicates that the device is removable. For example, a Universal Serial Bus (USB) device is reported to be removable by the drivers for the USB hub to which the device is connected. By default, this policy setting takes precedence over any other policy setting that allows Windows to install a device.
-
-NOTE: To enable the "Allow installation of devices using drivers that match these device setup classes", "Allow installation of devices that match any of these device IDs", and "Allow installation of devices that match any of these device instance IDs" policy settings to supersede this policy setting for applicable devices, enable the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting.
-
-If you enable this policy setting, Windows is prevented from installing removable devices and existing removable devices cannot have their drivers updated. If you enable this policy setting on a remote desktop server, the policy setting affects redirection of removable devices from a remote desktop client to the remote desktop server.
-
-If you disable or do not configure this policy setting, Windows can install and update driver packages for removable devices as allowed or prevented by other policy settings.
- Device Installation Restrictions
- Policy settings that describe which devices can or cannot be installed.
- Prevent creation of a system restore point during device activity that would normally prompt creation of a restore point
- This policy setting allows you to prevent Windows from creating a system restore point during device activity that would normally prompt Windows to create a system restore point. Windows normally creates restore points for certain driver activity, such as the installation of an unsigned driver. A system restore point enables you to more easily restore your system to its state before the activity.
-
-If you enable this policy setting, Windows does not create a system restore point when one would normally be created.
-
-If you disable or do not configure this policy setting, Windows creates a system restore point as it normally would.
- Allow remote access to the Plug and Play interface
- This policy setting allows you to allow or deny remote access to the Plug and Play interface.
-
-If you enable this policy setting, remote connections to the Plug and Play interface are allowed.
-
-If you disable or do not configure this policy setting, remote connections to the Plug and Play interface are not allowed.
- Prevent installation of devices not described by other policy settings
- This policy setting allows you to prevent the installation of devices that are not specifically described by any other policy setting.
-
-NOTE: This policy setting has been replaced by the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting to provide more granular control. It is recommended that you use the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting instead of this policy setting.
-
-If you enable this policy setting, Windows is prevented from installing or updating the driver package for any device that is not described by either the "Allow installation of devices that match any of these device IDs", the "Allow installation of devices for these device classes", or the "Allow installation of devices that match any of these device instance IDs" policy setting.
-
-If you disable or do not configure this policy setting, Windows is allowed to install or update the driver package for any device that is not described by the "Prevent installation of devices that match any of these device IDs", "Prevent installation of devices for these device classes" policy setting, "Prevent installation of devices that match any of these device instance IDs", or "Prevent installation of removable devices" policy setting.
- Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria
- This policy setting will change the evaluation order in which Allow and Prevent policy settings are applied when more than one install policy setting is applicable for a given device. Enable this policy setting to ensure that overlapping device match criteria is applied based on an established hierarchy where more specific match criteria supersedes less specific match criteria. The hierarchical order of evaluation for policy settings that specify device match criteria is as follows:
-
-Device instance IDs > Device IDs > Device setup class > Removable devices
-
-Device instance IDs
-1. Prevent installation of devices using drivers that match these device instance IDs
-2. Allow installation of devices using drivers that match these device instance IDs
-
-Device IDs
-3. Prevent installation of devices using drivers that match these device IDs
-4. Allow installation of devices using drivers that match these device IDs
-
-Device setup class
-5. Prevent installation of devices using drivers that match these device setup classes
-6. Allow installation of devices using drivers that match these device setup classes
-
-Removable devices
-7. Prevent installation of removable devices
-
-NOTE: This policy setting provides more granular control than the "Prevent installation of devices not described by other policy settings" policy setting. If these conflicting policy settings are enabled at the same time, the "Apply layered order of evaluation for Allow and Prevent device installation policies across all device match criteria" policy setting will be enabled and the other policy setting will be ignored.
-
-If you disable or do not configure this policy setting, the default evaluation is used. By default, all "Prevent installation..." policy settings have precedence over any other policy setting that allows Windows to install a device.
- Display a custom message title when device installation is prevented by a policy setting
- This policy setting allows you to display a custom message title in a notification when a device installation is attempted and a policy setting prevents the installation.
-
-If you enable this policy setting, Windows displays the text you type in the Main Text box as the title text of a notification when a policy setting prevents device installation.
-
-If you disable or do not configure this policy setting, Windows displays a default title in a notification when a policy setting prevents device installation.
- Display a custom message when installation is prevented by a policy setting
- This policy setting allows you to display a custom message to users in a notification when a device installation is attempted and a policy setting prevents the installation.
-
-If you enable this policy setting, Windows displays the text you type in the Detail Text box when a policy setting prevents device installation.
-
-If you disable or do not configure this policy setting, Windows displays a default message when a policy setting prevents device installation.
- Driver Installation
- Allow non-administrators to install drivers for these device setup classes
- This policy setting specifies a list of device setup class GUIDs describing driver packages that non-administrator members of the built-in Users group may install on the system.
-
-If you enable this policy setting, members of the Users group may install new drivers for the specified device setup classes. The drivers must be signed according to Windows Driver Signing Policy, or be signed by publishers already in the TrustedPublisher store.
-
-If you disable or do not configure this policy setting, only members of the Administrators group are allowed to install new driver packages on the system.
- Policy settings controlling the installation of driver packages on the system.
- Block
- Ignore
- Warn
- Code signing for driver packages
- Determines how the system responds when a user tries to install driver package files that are not digitally signed.
-
-This setting establishes the least secure response permitted on the systems of users in the group. Users can use System in Control Panel to select a more secure setting, but when this setting is enabled, the system does not implement any setting less secure than the one the setting established.
-
-When you enable this setting, use the drop-down box to specify the desired response.
-
--- "Ignore" directs the system to proceed with the installation even if it includes unsigned files.
-
--- "Warn" notifies the user that files are not digitally signed and lets the user decide whether to stop or to proceed with the installation and whether to permit unsigned files to be installed. "Warn" is the default.
-
--- "Block" directs the system to refuse to install unsigned files. As a result, the installation stops, and none of the files in the driver package are installed.
-
-To change driver file security without specifying a setting, use System in Control Panel. Right-click My Computer, click Properties, click the Hardware tab, and then click the Driver Signing button.
- Time (in seconds) to force reboot when required for policy changes to take effect
- This policy setting establishes the amount of time (in seconds) that the system will wait to reboot in order to enforce a change in device installation restriction policies.
-
-If you enable this policy setting, set the amount of seconds you want the system to wait until a reboot.
-
-If you disable or do not configure this policy setting, the system does not force a reboot.
-
-Note: If no reboot is forced, the device installation restriction right will not take effect until the system is restarted.
-
-
-
- Allow installation of devices using drivers for these device classes:
- To create a list of device classes, click Show. In the Show Contents dialog box, in the Value column,
- type a GUID that represents a device setup class
- (for example, {25DBCE51-6C8F-4A72-8A6D-B54C2B4FC835}).
-
-
- Prevent installation of devices using drivers for these device setup classes:
- To create a list of device classes, click Show. In the Show Contents dialog box, in the Value column,
- type a GUID that represents a device setup class
- (for example, {25DBCE51-6C8F-4A72-8A6D-B54C2B4FC835}).
- Also apply to matching devices that are already installed.
-
-
- Allow installation of devices that match any of these Device IDs:
- To create a list of devices, click Show. In the Show Contents dialog box, in the Value column,
- type a Plug and Play hardware ID or compatible ID
- (for example, gendisk, USB\COMPOSITE, USB\Class_ff).
-
-
- Prevent installation of devices that match any of these Device IDs:
- To create a list of devices, click Show. In the Show Contents dialog box, in the Value column,
- type a Plug and Play hardware ID or compatible ID
- (for example, gendisk, USB\COMPOSITE, USB\Class_ff).
- Also apply to matching devices that are already installed.
-
-
- Allow installation of devices that match any of these device instance IDs:
- To create a list of devices, click Show. In the Show Contents dialog box, in the Value column,
- type a Plug and Play device instance ID
- (for example, USB\VID_045E&&PID_0123\01234567890123456789).
-
-
- Prevent installation of devices that match any of these device instance IDs:
- To create a list of devices, click Show. In the Show Contents dialog box, in the Value column,
- type a Plug and Play device instance ID
- (for example, USB\VID_045E&&PID_0123\01234567890123456789).
- Also apply to matching devices that are already installed.
-
-
- Device Installation Timeout (in seconds)
-
-
- Reboot Timeout (in seconds)
-
-
- Enter the text you wish users to see (Max 63 chars)
-
-
-
-
-
- Enter the text you wish users to see (Max 128 chars)
-
-
-
-
-
- Allow Users to install driver packages for these classes:
- To create a list of device classes, click Show. In the Show Contents dialog box, in the Value column,
- type a GUID that represents a device setup class
- (for example, {25DBCE51-6C8F-4A72-8A6D-B54C2B4FC835}).
-
-
- When Windows detects a driver file without a digital signature:
-
-
-
-
diff --git a/policy_templates/en-US/DeviceSetup.adml b/policy_templates/en-US/DeviceSetup.adml
deleted file mode 100644
index 3ff966f..0000000
--- a/policy_templates/en-US/DeviceSetup.adml
+++ /dev/null
@@ -1,94 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off "Found New Hardware" balloons during device installation
- This policy setting allows you to turn off "Found New Hardware" balloons during device installation.
-
-If you enable this policy setting, "Found New Hardware" balloons do not appear while a device is being installed.
-
-If you disable or do not configure this policy setting, "Found New Hardware" balloons appear while a device is being installed, unless the driver for the device suppresses the balloons.
- Do not send a Windows error report when a generic driver is installed on a device
- Windows has a feature that sends "generic-driver-installed" reports through the Windows Error Reporting infrastructure. This policy allows you to disable the feature.
-
-If you enable this policy setting, an error report is not sent when a generic driver is installed.
-
-If you disable or do not configure this policy setting, an error report is sent when a generic driver is installed.
- Prevent Windows from sending an error report when a device driver requests additional software during installation
- Windows has a feature that allows a device driver to request additional software through the Windows Error Reporting infrastructure. This policy allows you to disable the feature.
-
-If you enable this policy setting, Windows will not send an error report to request additional software even if this is specified by the device driver.
-
-If you disable or do not configure this policy setting, Windows sends an error report when a device driver that requests additional software is installed.
- Configure driver search locations
- This setting configures the location that Windows searches for drivers when a new piece of hardware is found.
-
-By default, Windows searches the following places for drivers: local installation, floppy drives, CD-ROM drives, Windows Update.
-
-Using this setting, you may remove the floppy and CD-ROM drives from the search algorithm.
-
-If you enable this setting, you can remove the locations by selecting the associated check box beside the location name.
-
-If you disable or do not configure this setting, Windows searches the installation location, floppy drives, and CD-ROM drives.
-
-Note: To prevent searching Windows Update for drivers also see "Turn off Windows Update device driver searching" in Administrative Templates/System/Internet Communication Management/Internet Communication settings.
- Turn off Windows Update device driver search prompt
- Specifies whether the administrator will be prompted about going to Windows Update to search for device drivers using the Internet.
-
-Note: This setting only has effect if "Turn off Windows Update device driver searching" in "Administrative Templates/System/Internet Communication Management/Internet Communication settings" is disabled or not configured.
-
-If you enable this setting, administrators will not be prompted to search Windows Update.
-
-If you disable or do not configure this setting, and "Turn off Windows Update device driver searching" is disabled or not configured, the administrator will be prompted for consent before going to Windows Update to search for device drivers.
- Specify search order for device driver source locations
- This policy setting allows you to specify the order in which Windows searches source locations for device drivers.
-
-If you enable this policy setting, you can select whether Windows searches for drivers on Windows Update unconditionally, only if necessary, or not at all.
-
-Note that searching always implies that Windows will attempt to search Windows Update exactly one time. With this setting, Windows will not continually search for updates. This setting is used to ensure that the best software will be found for the device, even if the network is temporarily available.
-
-If the setting for searching only if needed is specified, then Windows will search for a driver only if a driver is not locally available on the system.
-
-If you disable or do not configure this policy setting, members of the Administrators group can determine the priority order in which Windows searches source locations for device drivers.
- Always search Windows Update
- Search Windows Update only if needed
- Do not search Windows Update
-
- Specify the search server for device driver updates
- This policy setting allows you to specify the search server that Windows uses to find updates for device drivers.
-
-If you enable this policy setting, you can select whether Windows searches Windows Update (WU), searches a Managed Server, or a combination of both.
-
-Note that if both are specified, then Windows will first search the Managed Server, such as a Windows Server Update Services (WSUS) server. Only if no update is found will Windows then also search Windows Update.
-
-If you disable or do not configure this policy setting, members of the Administrators group can determine the server used in the search for device drivers.
-
- Search Windows Update
- Search Managed Server
- Search Managed Server, then WU
-
- Prevent device metadata retrieval from the Internet
- This policy setting allows you to prevent Windows from retrieving device metadata from the Internet.
-
-If you enable this policy setting, Windows does not retrieve device metadata for installed devices from the Internet. This policy setting overrides the setting in the Device Installation Settings dialog box (Control Panel > System and Security > System > Advanced System Settings > Hardware tab).
-
-If you disable or do not configure this policy setting, the setting in the Device Installation Settings dialog box controls whether Windows retrieves device metadata from the Internet.
-
-
-
- Do not search floppy disk drives
- Do not search CD-ROM drives
- Do not search Windows Update
-
-
- Select search order:
-
-
- Select update server:
-
-
-
-
diff --git a/policy_templates/en-US/DigitalLocker.adml b/policy_templates/en-US/DigitalLocker.adml
deleted file mode 100644
index 4311869..0000000
--- a/policy_templates/en-US/DigitalLocker.adml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Do not allow Digital Locker to run
- Specifies whether Digital Locker can run.
-
-Digital Locker is a dedicated download manager associated with Windows Marketplace and a feature of Windows that can be used to manage and download products acquired and stored in the user's Windows Marketplace Digital Locker.
-
-If you enable this setting, Digital Locker will not run.
-
-If you disable or do not configure this setting, Digital Locker can be run.
- Digital Locker
-
-
-
diff --git a/policy_templates/en-US/DiskDiagnostic.adml b/policy_templates/en-US/DiskDiagnostic.adml
deleted file mode 100644
index 14e696d..0000000
--- a/policy_templates/en-US/DiskDiagnostic.adml
+++ /dev/null
@@ -1,56 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
-
-
- Windows Server 2008 with Desktop Experience installed or Windows Vista
-
-
- Disk Diagnostic: Configure custom alert text
- This policy setting substitutes custom alert text in the disk diagnostic message shown to users when a disk reports a S.M.A.R.T. fault.
-
-If you enable this policy setting, Windows displays custom alert text in the disk diagnostic message. The custom text may not exceed 512 characters.
-
-If you disable or do not configure this policy setting, Windows displays the default alert text in the disk diagnostic message.
-
-No reboots or service restarts are required for this policy setting to take effect: changes take effect immediately.
-
-This policy setting only takes effect if the Disk Diagnostic scenario policy setting is enabled or not configured and the Diagnostic Policy Service (DPS) is in the running state. When the service is stopped or disabled, diagnostic scenarios are not executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
-
-Note: For Windows Server systems, this policy setting applies only if the Desktop Experience optional component is installed and the Remote Desktop Services role is not installed.
-
- Disk Diagnostic
- Disk Diagnostic: Configure execution level
- This policy setting determines the execution level for S.M.A.R.T.-based disk diagnostics.
-
-Self-Monitoring And Reporting Technology (S.M.A.R.T.) is a standard mechanism for storage devices to report faults to Windows. A disk that reports a S.M.A.R.T. fault may need to be repaired or replaced. The Diagnostic Policy Service (DPS) detects and logs S.M.A.R.T. faults to the event log when they occur.
-
-If you enable this policy setting, the DPS also warns users of S.M.A.R.T. faults and guides them through backup and recovery to minimize potential data loss.
-
-If you disable this policy, S.M.A.R.T. faults are still detected and logged, but no corrective action is taken.
-
-If you do not configure this policy setting, the DPS enables S.M.A.R.T. fault resolution by default.
-
-This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
-
-No reboots or service restarts are required for this policy setting to take effect: changes take effect immediately.
-
-This policy setting takes effect only when the DPS is in the running state. When the service is stopped or disabled, diagnostic scenarios are not executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
-
-Note: For Windows Server systems, this policy setting applies only if the Desktop Experience optional component is installed and the Remote Desktop Services role is not installed.
-
-
-
-
-
-
- Enter custom alert text here
-
-
-
-
-
diff --git a/policy_templates/en-US/DiskNVCache.adml b/policy_templates/en-US/DiskNVCache.adml
deleted file mode 100644
index 49607f1..0000000
--- a/policy_templates/en-US/DiskNVCache.adml
+++ /dev/null
@@ -1,51 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off boot and resume optimizations
- This policy setting turns off the boot and resume optimizations for the hybrid hard disks in the system.
-
-If you enable this policy setting, the system does not use the non-volatile (NV) cache to optimize boot and resume.
-
-If you disable this policy setting, the system uses the NV cache to achieve faster boot and resume. The system determines the data that will be stored in the NV cache to optimize boot and resume. The required data is stored in the NV cache during shutdown and hibernate, respectively. This might cause a slight increase in the time taken for shutdown and hibernate.
-
-If you do not configure this policy setting, the default behavior is observed and the NV cache is used for boot and resume optimizations.
-
-Note: This policy setting is applicable only if the NV cache feature is on.
- Turn off cache power mode
- This policy setting turns off power save mode on the hybrid hard disks in the system.
-
-If you enable this policy setting, the hard disks are not put into NV cache power save mode and no power savings are achieved.
-
-If you disable this policy setting, the hard disks are put into an NV cache power saving mode. In this mode, the system tries to save power by aggressively spinning down the disk.
-
-If you do not configure this policy setting, the default behavior is to allow the hybrid hard disks to be in power save mode.
-
-Note: This policy setting is applicable only if the NV cache feature is on.
- Turn off non-volatile cache feature
- This policy setting turns off all support for the non-volatile (NV) cache on all hybrid hard disks in the system. To check if you have hybrid hard disks in the system, from Device Manager, right-click the disk drive and select Properties. The NV cache can be used to optimize boot and resume by reading data from the cache while the disks are spinning up. The NV cache can also be used to reduce the power consumption of the system by keeping the disks spun down while satisfying reads and writes from the cache.
-
-If you enable this policy setting, the system will not manage the NV cache and will not enable NV cache power saving mode.
-
-If you disable this policy setting, the system will manage the NV cache on the disks if the other policy settings for the NV cache are appropriately configured.
-
-Note: This policy setting will take effect on next boot.
-
-If you do not configure this policy setting, the default behavior is to turn on support for the NV cache.
- Disk NV Cache
- Turn off solid state mode
- This policy setting turns off the solid state mode for the hybrid hard disks.
-
-If you enable this policy setting, frequently written files such as the file system metadata and registry may not be stored in the NV cache.
-
-If you disable this policy setting, the system will store frequently written data into the non-volatile (NV) cache. This allows the system to exclusively run out of the NV cache and power down the disk for longer periods to save power. Note that this can cause increased wear of the NV cache.
-
-If you do not configure this policy setting, the default behavior of the system is observed and frequently written files will be stored in the NV cache.
-
-Note: This policy setting is applicable only if the NV cache feature is on.
-
-
-
diff --git a/policy_templates/en-US/DiskQuota.adml b/policy_templates/en-US/DiskQuota.adml
deleted file mode 100644
index b5450a6..0000000
--- a/policy_templates/en-US/DiskQuota.adml
+++ /dev/null
@@ -1,99 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Disk Quotas
- Enable disk quotas
- This policy setting turns on and turns off disk quota management on all NTFS volumes of the computer, and prevents users from changing the setting.
-
-If you enable this policy setting, disk quota management is turned on, and users cannot turn it off.
-
-If you disable the policy setting, disk quota management is turned off, and users cannot turn it on.
-
-If this policy setting is not configured, disk quota management is turned off by default, but administrators can turn it on.
-
-To prevent users from changing the setting while a setting is in effect, the system disables the "Enable quota management" option on the Quota tab of NTFS volumes.
-
-Note: This policy setting turns on disk quota management but does not establish or enforce a particular disk quota limit. To specify a disk quota limit, use the "Default quota limit and warning level" policy setting. Otherwise, the system uses the physical space on the volume as the quota limit.
-
-Note: To turn on or turn off disk quota management without specifying a setting, in My Computer, right-click the name of an NTFS volume, click Properties, click the Quota tab, and then click "Enable quota management."
- Enforce disk quota limit
- This policy setting determines whether disk quota limits are enforced and prevents users from changing the setting.
-
-If you enable this policy setting, disk quota limits are enforced. If you disable this policy setting, disk quota limits are not enforced. When you enable or disable this policy setting, the system disables the "Deny disk space to users exceeding quota limit" option on the Quota tab so administrators cannot make changes while the setting is in effect.
-
-If you do not configure this policy setting, the disk quota limit is not enforced by default, but administrators can change the setting.
-
-Enforcement is optional. When users reach an enforced disk quota limit, the system responds as though the physical space on the volume were exhausted. When users reach an unenforced limit, their status in the Quota Entries window changes, but they can continue to write to the volume as long as physical space is available.
-
-Note: This policy setting overrides user settings that enable or disable quota enforcement on their volumes.
-
-Note: To specify a disk quota limit, use the "Default quota limit and warning level" policy setting. Otherwise, the system uses the physical space on the volume as the quota limit.
- Specify default quota limit and warning level
- This policy setting specifies the default disk quota limit and warning level for new users of the volume.
-
-This policy setting determines how much disk space can be used by each user on each of the NTFS file system volumes on a computer. It also specifies the warning level, the point at which the user's status in the Quota Entries window changes to indicate that the user is approaching the disk quota limit.
-
-This setting overrides new users’ settings for the disk quota limit and warning level on their volumes, and it disables the corresponding options in the "Select the default quota limit for new users of this volume" section on the Quota tab.
-
-This policy setting applies to all new users as soon as they write to the volume. It does not affect disk quota limits for current users, or affect customized limits and warning levels set for particular users (on the Quota tab in Volume Properties).
-
-If you disable or do not configure this policy setting, the disk space available to users is not limited. The disk quota management feature uses the physical space on each volume as its quota limit and warning level.
-
-When you select a limit, remember that the same limit applies to all users on all volumes, regardless of actual volume size. Be sure to set the limit and warning level so that it is reasonable for the range of volumes in the group.
-
-This policy setting is effective only when disk quota management is enabled on the volume. Also, if disk quotas are not enforced, users can exceed the quota limit you set. When users reach the quota limit, their status in the Quota Entries window changes, but users can continue to write to the volume.
- Log event when quota limit is exceeded
- This policy setting determines whether the system records an event in the local Application log when users reach their disk quota limit on a volume, and prevents users from changing the logging setting.
-
-If you enable this policy setting, the system records an event when the user reaches their limit. If you disable this policy setting, no event is recorded. Also, when you enable or disable this policy setting, the system disables the "Log event when a user exceeds their quota limit" option on the Quota tab, so administrators cannot change the setting while a setting is in effect.
-
-If you do not configure this policy setting, no events are recorded, but administrators can use the Quota tab option to change the setting.
-
-This policy setting is independent of the enforcement policy settings for disk quotas. As a result, you can direct the system to log an event, regardless of whether or not you choose to enforce the disk quota limit.
-
-Also, this policy setting does not affect the Quota Entries window on the Quota tab. Even without the logged event, users can detect that they have reached their limit, because their status in the Quota Entries window changes.
-
-Note: To find the logging option, in My Computer, right-click the name of an NTFS file system volume, click Properties, and then click the Quota tab.
- Log event when quota warning level is exceeded
- This policy setting determines whether the system records an event in the Application log when users reach their disk quota warning level on a volume.
-
-If you enable this policy setting, the system records an event. If you disable this policy setting, no event is recorded. When you enable or disable this policy setting, the system disables the corresponding "Log event when a user exceeds their warning level" option on the Quota tab so that administrators cannot change logging while a policy setting is in effect.
-
-If you do not configure this policy setting, no event is recorded, but administrators can use the Quota tab option to change the logging setting.
-
-This policy setting does not affect the Quota Entries window on the Quota tab. Even without the logged event, users can detect that they have reached their warning level because their status in the Quota Entries window changes.
-
-Note: To find the logging option, in My Computer, right-click the name of an NTFS file system volume, click Properties, and then click the Quota tab.
- Apply policy to removable media
- This policy setting extends the disk quota policies in this folder to NTFS file system volumes on removable media.
-
-If you disable or do not configure this policy setting, the disk quota policies established in this folder apply to fixed-media NTFS volumes only. Note: When this policy setting is applied, the computer will apply the disk quota to both fixed and removable media.
- EB
- GB
- KB
- MB
- PB
- TB
-
-
-
- Specify a quota limit and warning level applied to users when
- they first write to a quota-enabled volume.
-
- Default quota limit:
-
- Value
- Units
-
- Default warning level:
-
- Value
- Units
-
-
-
-
diff --git a/policy_templates/en-US/Display.adml b/policy_templates/en-US/Display.adml
deleted file mode 100644
index 11777ed..0000000
--- a/policy_templates/en-US/Display.adml
+++ /dev/null
@@ -1,72 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Display
- GDI DPI Scaling enables applications that are not DPI aware to become per monitor DPI aware.
-
-This policy setting lets you specify legacy applications that have GDI DPI Scaling turned on.
-
-If you enable this policy setting, GDI DPI Scaling is turned on for all legacy applications in the list.
-
-If you disable or do not configure this policy setting, GDI DPI Scaling will not be enabled for an application except when an application is enabled by using ApplicationCompatibility database, ApplicationCompatibility UI System (Enhanced) setting, or an application manifest.
-
-If GDI DPI Scaling is configured to both turn off and turn on an application, the application will be turned off.
- GDI DPI Scaling enables applications that are not DPI aware to become per monitor DPI aware.
-
-This policy setting lets you specify legacy applications that have GDI DPI Scaling turned off.
-
-If you enable this policy setting, GDI DPI Scaling is turned off for all applications in the list, even if they are enabled by using ApplicationCompatibility database, ApplicationCompatibility UI System (Enhanced) setting, or an application manifest.
-
-If you disable or do not configure this policy setting, GDI DPI Scaling might still be turned on for legacy applications.
-
-If GDI DPI Scaling is configured to both turn off and turn on an application, the application will be turned off.
- Turn on GdiDPIScaling for applications
- Turn off GdiDPIScaling for applications
- Per Process System DPI is an application compatibility feature for desktop applications that do not render properly after a display-scale factor (DPI) change. When the display scale factor of the primary display changes (which can happen when you connect or disconnect a display that has a different display scale factor (DPI), connect remotely from a device with a different display scale factor, or manually change the display scale factor), many desktop applications can display blurry. Desktop applications that have not been updated to display properly in this scenario will be blurry until the user logs out and back in to Windows.
-
-When you enable this policy some blurry applications will be crisp after they are restarted, without requiring the user to log out and back in to Windows.
-
-Be aware of the following:
-
-Per Process System DPI will only improve the rendering of desktop applications that are positioned on the primary display. Some desktop applications can still be blurry on secondary displays that have different display scale factors.
-
-Per Process System DPI will not work for all applications as some older desktop applications will always be blurry on high DPI displays.
-
-In some cases, you may see some odd behavior in some desktop applications. If that happens, Per Process System DPI should be disabled.
-
-Enabling this setting lets you specify the system-wide default for desktop applications as well as per-application overrides. If you disable or do not configure this setting, Per Process System DPI will not apply to any processes on the system.
-
-
- Configure Per-Process System DPI settings
- Enable
- Disable
- Enable Per-Process System DPI for applications
- Disable Per-Process System DPI for applications
-
-
-
-
-
-
-
-
-
-
-
-
-
- Enable or disable Per-Process System DPI for all applications.
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/DistributedLinkTracking.adml b/policy_templates/en-US/DistributedLinkTracking.adml
deleted file mode 100644
index faca0e9..0000000
--- a/policy_templates/en-US/DistributedLinkTracking.adml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow Distributed Link Tracking clients to use domain resources
- Specifies that Distributed Link Tracking clients in this domain may use the Distributed Link Tracking (DLT) server, which runs on domain controllers. The DLT client enables programs to track linked files that are moved within an NTFS volume, to another NTFS volume on the same computer, or to an NTFS volume on another computer. The DLT client can more reliably track links when allowed to use the DLT server. This policy should not be set unless the DLT server is running on all domain controllers in the domain.
-
-
-
diff --git a/policy_templates/en-US/DmaGuard.adml b/policy_templates/en-US/DmaGuard.adml
deleted file mode 100644
index 2fcd9cf..0000000
--- a/policy_templates/en-US/DmaGuard.adml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- Kernel DMA Protection
- This file contains the configuration options for Kernel DMA Protection
-
-
-
- Kernel DMA Protection
- Policies for configuring Kernel DMA Protection
- Enumeration policy for external devices incompatible with Kernel DMA Protection
- Enumeration policy for external DMA-capable devices incompatible with DMA remapping. This policy only takes effect when Kernel DMA Protection is enabled and supported by the system. Note: this policy does not apply to 1394, PCMCIA or ExpressCard devices.
- Allow all
- Only while logged in (default)
- Block all
-
-
-
-
- Enumeration policy
-
-
-
-
-
diff --git a/policy_templates/en-US/DnsClient.adml b/policy_templates/en-US/DnsClient.adml
deleted file mode 100644
index 4d54616..0000000
--- a/policy_templates/en-US/DnsClient.adml
+++ /dev/null
@@ -1,342 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- DNS Client
- Connection-specific DNS suffix
- Specifies a connection-specific DNS suffix. This policy setting supersedes local connection-specific DNS suffixes, and those configured using DHCP.
-
-To use this policy setting, click Enabled, and then enter a string value representing the DNS suffix.
-
-If you enable this policy setting, the DNS suffix that you enter will be applied to all network connections used by computers that receive this policy setting.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers will use the local or DHCP supplied connection specific DNS suffix, if configured.
- DNS servers
- Defines the DNS servers to which a computer sends queries when it attempts to resolve names. This policy setting supersedes the list of DNS servers configured locally and those configured using DHCP.
-
-To use this policy setting, click Enabled, and then enter a space-delimited list of IP addresses in the available field. To use this policy setting, you must enter at least one IP address.
-
-If you enable this policy setting, the list of DNS servers is applied to all network connections used by computers that receive this policy setting.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers will use the local or DHCP supplied list of DNS servers, if configured.
- Primary DNS suffix
- Specifies the primary DNS suffix used by computers in DNS name registration and DNS name resolution.
-
-To use this policy setting, click Enabled and enter the entire primary DNS suffix you want to assign. For example: microsoft.com.
-
-Important: In order for changes to this policy setting to be applied on computers that receive it, you must restart Windows.
-
-If you enable this policy setting, it supersedes the primary DNS suffix configured in the DNS Suffix and NetBIOS Computer Name dialog box using the System control panel.
-
-You can use this policy setting to prevent users, including local administrators, from changing the primary DNS suffix.
-
-If you disable this policy setting, or if you do not configure this policy setting, each computer uses its local primary DNS suffix, which is usually the DNS name of Active Directory domain to which it is joined.
- Register DNS records with connection-specific DNS suffix
- Specifies if a computer performing dynamic DNS registration will register A and PTR resource records with a concatenation of its computer name and a connection-specific DNS suffix, in addition to registering these records with a concatenation of its computer name and the primary DNS suffix.
-
-By default, a DNS client performing dynamic DNS registration registers A and PTR resource records with a concatenation of its computer name and the primary DNS suffix. For example, a computer name of mycomputer and a primary DNS suffix of microsoft.com will be registered as: mycomputer.microsoft.com.
-
-If you enable this policy setting, a computer will register A and PTR resource records with its connection-specific DNS suffix, in addition to the primary DNS suffix. This applies to all network connections used by computers that receive this policy setting.
-
-For example, with a computer name of mycomputer, a primary DNS suffix of microsoft.com, and a connection specific DNS suffix of VPNconnection, a computer will register A and PTR resource records for mycomputer.VPNconnection and mycomputer.microsoft.com when this policy setting is enabled.
-
-Important: This policy setting is ignored on a DNS client computer if dynamic DNS registration is disabled.
-
-If you disable this policy setting, or if you do not configure this policy setting, a DNS client computer will not register any A and PTR resource records using a connection-specific DNS suffix.
- Register PTR records
- Do not register
- Specifies if DNS client computers will register PTR resource records.
-
-By default, DNS clients configured to perform dynamic DNS registration will attempt to register PTR resource record only if they successfully registered the corresponding A resource record.
-
-If you enable this policy setting, registration of PTR records will be determined by the option that you choose under Register PTR records.
-
-To use this policy setting, click Enabled, and then select one of the following options from the drop-down list:
-
-Do not register: Computers will not attempt to register PTR resource records.
-
-Register: Computers will attempt to register PTR resource records even if registration of the corresponding A records was not successful.
-
-Register only if A record registration succeeds: Computers will attempt to register PTR resource records only if registration of the corresponding A records was successful.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers will use locally configured settings.
- Register
- Register only if A record registration succeeds
- Dynamic update
- Specifies if DNS dynamic update is enabled. Computers configured for DNS dynamic update automatically register and update their DNS resource records with a DNS server.
-
-If you enable this policy setting, or you do not configure this policy setting, computers will attempt to use dynamic DNS registration on all network connections that have connection-specific dynamic DNS registration enabled. For a dynamic DNS registration to be enabled on a network connection, the connection-specific configuration must allow dynamic DNS registration, and this policy setting must not be disabled.
-
-If you disable this policy setting, computers may not use dynamic DNS registration for any of their network connections, regardless of the configuration for individual network connections.
- Replace addresses in conflicts
- Specifies whether dynamic updates should overwrite existing resource records that contain conflicting IP addresses.
-
-This policy setting is designed for computers that register address (A) resource records in DNS zones that do not use Secure Dynamic Updates. Secure Dynamic Update preserves ownership of resource records and does not allow a DNS client to overwrite records that are registered by other computers.
-
-During dynamic update of resource records in a zone that does not use Secure Dynamic Updates, an A resource record might exist that associates the client's host name with an IP address different than the one currently in use by the client. By default, the DNS client attempts to replace the existing A resource record with an A resource record that has the client's current IP address.
-
-If you enable this policy setting or if you do not configure this policy setting, DNS clients maintain their default behavior and will attempt to replace conflicting A resource records during dynamic update.
-
-If you disable this policy setting, existing A resource records that contain conflicting IP addresses will not be replaced during a dynamic update, and an error will be recorded in Event Viewer.
- Registration refresh interval
- Specifies the interval used by DNS clients to refresh registration of A and PTR resource. This policy setting only applies to computers performing dynamic DNS updates.
-
-Computers configured to perform dynamic DNS registration of A and PTR resource records periodically reregister their records with DNS servers, even if the record has not changed. This reregistration is required to indicate to DNS servers that records are current and should not be automatically removed (scavenged) when a DNS server is configured to delete stale records.
-
-Warning: If record scavenging is enabled on the zone, the value of this policy setting should never be longer than the value of the DNS zone refresh interval. Configuring the registration refresh interval to be longer than the refresh interval of the DNS zone might result in the undesired deletion of A and PTR resource records.
-
-To specify the registration refresh interval, click Enabled and then enter a value of 1800 or greater. The value that you specify is the number of seconds to use for the registration refresh interval. For example, 1800 seconds is 30 minutes.
-
-If you enable this policy setting, registration refresh interval that you specify will be applied to all network connections used by computers that receive this policy setting.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers will use the local or DHCP supplied setting. By default, client computers configured with a static IP address attempt to update their DNS resource records once every 24 hours and DHCP clients will attempt to update their DNS resource records when a DHCP lease is granted or renewed.
- TTL value for A and PTR records
-
-Specifies the value of the time to live (TTL) field in A and PTR resource records that are registered by computers to which this policy setting is applied.
-
-To specify the TTL, click Enabled and then enter a value in seconds (for example, 900 is 15 minutes).
-
-If you enable this policy setting, the TTL value that you specify will be applied to DNS resource records registered for all network connections used by computers that receive this policy setting.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers will use the TTL settings specified in DNS. By default, the TTL is 1200 seconds (20 minutes).
- DNS suffix search list
- Specifies the DNS suffixes to attach to an unqualified single-label name before submission of a DNS query for that name.
-
-An unqualified single-label name contains no dots. The name "example" is a single-label name. This is different from a fully qualified domain name such as "example.microsoft.com."
-
-Client computers that receive this policy setting will attach one or more suffixes to DNS queries for a single-label name. For example, a DNS query for the single-label name "example" will be modified to "example.microsoft.com" before sending the query to a DNS server if this policy setting is enabled with a suffix of "microsoft.com."
-
-To use this policy setting, click Enabled, and then enter a string value representing the DNS suffixes that should be appended to single-label names. You must specify at least one suffix. Use a comma-delimited string, such as "microsoft.com,serverua.microsoft.com,office.microsoft.com" to specify multiple suffixes.
-
-If you enable this policy setting, one DNS suffix is attached at a time for each query. If a query is unsuccessful, a new DNS suffix is added in place of the failed suffix, and this new query is submitted. The values are used in the order they appear in the string, starting with the leftmost value and proceeding to the right until a query is successful or all suffixes are tried.
-
-If you disable this policy setting, or if you do not configure this policy setting, the primary DNS suffix and network connection-specific DNS suffixes are appended to the unqualified queries.
- Update security level
- Specifies the security level for dynamic DNS updates.
-
-To use this policy setting, click Enabled and then select one of the following values:
-
-Unsecure followed by secure - computers send secure dynamic updates only when nonsecure dynamic updates are refused.
-
-Only unsecure - computers send only nonsecure dynamic updates.
-
-Only secure - computers send only secure dynamic updates.
-
-If you enable this policy setting, computers that attempt to send dynamic DNS updates will use the security level that you specify in this policy setting.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers will use local settings. By default, DNS clients attempt to use unsecured dynamic update first. If an unsecured update is refused, clients try to use secure update.
- Only secure
- Only unsecure
- Unsecure followed by secure
- Update top level domain zones
- Specifies if computers may send dynamic updates to zones with a single label name. These zones are also known as top-level domain zones, for example: "com."
-
-By default, a DNS client that is configured to perform dynamic DNS update will update the DNS zone that is authoritative for its DNS resource records unless the authoritative zone is a top-level domain or root zone.
-
-If you enable this policy setting, computers send dynamic updates to any zone that is authoritative for the resource records that the computer needs to update, except the root zone.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers do not send dynamic updates to the root zone or top-level domain zones that are authoritative for the resource records that the computer needs to update.
- Primary DNS suffix devolution
- Specifies if the DNS client performs primary DNS suffix devolution during the name resolution process.
-
-With devolution, a DNS client creates queries by appending a single-label, unqualified domain name with the parent suffix of the primary DNS suffix name, and the parent of that suffix, and so on, stopping if the name is successfully resolved or at a level determined by devolution settings. Devolution can be used when a user or application submits a query for a single-label domain name.
-
-The DNS client appends DNS suffixes to the single-label, unqualified domain name based on the state of the Append primary and connection specific DNS suffixes radio button and Append parent suffixes of the primary DNS suffix check box on the DNS tab in Advanced TCP/IP Settings for the Internet Protocol (TCP/IP) Properties dialog box.
-
-Devolution is not enabled if a global suffix search list is configured using Group Policy.
-
-If a global suffix search list is not configured, and the Append primary and connection specific DNS suffixes radio button is selected, the DNS client appends the following names to a single-label name when it sends DNS queries:
-
-The primary DNS suffix, as specified on the Computer Name tab of the System control panel.
-
-Each connection-specific DNS suffix, assigned either through DHCP or specified in the DNS suffix for this connection box on the DNS tab in the Advanced TCP/IP Settings dialog box for each connection.
-
-For example, when a user submits a query for a single-label name such as "example," the DNS client attaches a suffix such as "microsoft.com" resulting in the query "example.microsoft.com," before sending the query to a DNS server.
-
-If a DNS suffix search list is not specified, the DNS client attaches the primary DNS suffix to a single-label name. If this query fails, the connection-specific DNS suffix is attached for a new query. If none of these queries are resolved, the client devolves the primary DNS suffix of the computer (drops the leftmost label of the primary DNS suffix), attaches this devolved primary DNS suffix to the single-label name, and submits this new query to a DNS server.
-
-For example, if the primary DNS suffix ooo.aaa.microsoft.com is attached to the non-dot-terminated single-label name "example," and the DNS query for example.ooo.aaa.microsoft.com fails, the DNS client devolves the primary DNS suffix (drops the leftmost label) till the specified devolution level, and submits a query for example.aaa.microsoft.com. If this query fails, the primary DNS suffix is devolved further if it is under specified devolution level and the query example.microsoft.com is submitted. If this query fails, devolution continues if it is under specified devolution level and the query example.microsoft.com is submitted, corresponding to a devolution level of two. The primary DNS suffix cannot be devolved beyond a devolution level of two. The devolution level can be configured using the primary DNS suffix devolution level policy setting. The default devolution level is two.
-
-If you enable this policy setting, or if you do not configure this policy setting, DNS clients attempt to resolve single-label names using concatenations of the single-label name to be resolved and the devolved primary DNS suffix.
-
-If you disable this policy setting, DNS clients do not attempt to resolve names that are concatenations of the single-label name to be resolved and the devolved primary DNS suffix.
- Primary DNS suffix devolution level
- Specifies if the devolution level that DNS clients will use if they perform primary DNS suffix devolution during the name resolution process.
-
-With devolution, a DNS client creates queries by appending a single-label, unqualified domain name with the parent suffix of the primary DNS suffix name, and the parent of that suffix, and so on, stopping if the name is successfully resolved or at a level determined by devolution settings. Devolution can be used when a user or application submits a query for a single-label domain name.
-
-The DNS client appends DNS suffixes to the single-label, unqualified domain name based on the state of the Append primary and connection specific DNS suffixes radio button and Append parent suffixes of the primary DNS suffix check box on the DNS tab in Advanced TCP/IP Settings for the Internet Protocol (TCP/IP) Properties dialog box.
-
-Devolution is not enabled if a global suffix search list is configured using Group Policy.
-
-If a global suffix search list is not configured, and the Append primary and connection specific DNS suffixes radio button is selected, the DNS client appends the following names to a single-label name when it sends DNS queries:
-
-The primary DNS suffix, as specified on the Computer Name tab of the System control panel.
-
-Each connection-specific DNS suffix, assigned either through DHCP or specified in the DNS suffix for this connection box on the DNS tab in the Advanced TCP/IP Settings dialog box for each connection.
-
-For example, when a user submits a query for a single-label name such as "example," the DNS client attaches a suffix such as "microsoft.com" resulting in the query "example.microsoft.com," before sending the query to a DNS server.
-
-If a DNS suffix search list is not specified, the DNS client attaches the primary DNS suffix to a single-label name. If this query fails, the connection-specific DNS suffix is attached for a new query. If none of these queries are resolved, the client devolves the primary DNS suffix of the computer (drops the leftmost label of the primary DNS suffix), attaches this devolved primary DNS suffix to the single-label name, and submits this new query to a DNS server.
-
-For example, if the primary DNS suffix ooo.aaa.microsoft.com is attached to the non-dot-terminated single-label name "example," and the DNS query for example.ooo.aaa.microsoft.com fails, the DNS client devolves the primary DNS suffix (drops the leftmost label) till the specified devolution level, and submits a query for example.aaa.microsoft.com. If this query fails, the primary DNS suffix is devolved further if it is under specified devolution level and the query example.microsoft.com is submitted. If this query fails, devolution continues if it is under specified devolution level and the query example.microsoft.com is submitted, corresponding to a devolution level of two. The primary DNS suffix cannot be devolved beyond a devolution level of two. The devolution level can be configured using this policy setting. The default devolution level is two.
-
-If you enable this policy setting and DNS devolution is also enabled, DNS clients use the DNS devolution level that you specify.
-
-If this policy setting is disabled, or if this policy setting is not configured, DNS clients use the default devolution level of two provided that DNS devolution is enabled.
- Turn off multicast name resolution
- Specifies that link local multicast name resolution (LLMNR) is disabled on client computers.
-
-LLMNR is a secondary name resolution protocol. With LLMNR, queries are sent using multicast over a local network link on a single subnet from a client computer to another client computer on the same subnet that also has LLMNR enabled. LLMNR does not require a DNS server or DNS client configuration, and provides name resolution in scenarios in which conventional DNS name resolution is not possible.
-
-If you enable this policy setting, LLMNR will be disabled on all available network adapters on the client computer.
-
-If you disable this policy setting, or you do not configure this policy setting, LLMNR will be enabled on all available network adapters.
- Allow DNS suffix appending to unqualified multi-label name queries
- Specifies that computers may attach suffixes to an unqualified multi-label name before sending subsequent DNS queries if the original name query fails.
-
-A name containing dots, but not dot-terminated, is called an unqualified multi-label name, for example "server.corp" is an unqualified multi-label name. The name "server.corp.contoso.com." is an example of a fully qualified name because it contains a terminating dot.
-
-For example, if attaching suffixes is allowed, an unqualified multi-label name query for "server.corp" will be queried by the DNS client first. If the query succeeds, the response is returned to the client. If the query fails, the unqualified multi-label name is appended with DNS suffixes. These suffixes can be derived from a combination of the local DNS client's primary domain suffix, a connection-specific domain suffix, and a DNS suffix search list.
-
-If attaching suffixes is allowed, and a DNS client with a primary domain suffix of "contoso.com" performs a query for "server.corp" the DNS client will send a query for "server.corp" first, and then a query for "server.corp.contoso.com." second if the first query fails.
-
-If you enable this policy setting, suffixes are allowed to be appended to an unqualified multi-label name if the original name query fails.
-
-If you disable this policy setting, no suffixes are appended to unqualified multi-label name queries if the original name query fails.
-
-If you do not configure this policy setting, computers will use their local DNS client settings to determine the query behavior for unqualified multi-label names.
- Turn off smart multi-homed name resolution
- Specifies that a multi-homed DNS client should optimize name resolution across networks. The setting improves performance by issuing parallel DNS, link local multicast name resolution (LLMNR) and NetBIOS over TCP/IP (NetBT) queries across all networks. In the event that multiple positive responses are received, the network binding order is used to determine which response to accept.
-
-If you enable this policy setting, the DNS client will not perform any optimizations. DNS queries will be issued across all networks first. LLMNR queries will be issued if the DNS queries fail, followed by NetBT queries if LLMNR queries fail.
-
-If you disable this policy setting, or if you do not configure this policy setting, name resolution will be optimized when issuing DNS, LLMNR and NetBT queries.
- Turn off smart protocol reordering
- Specifies that the DNS client should prefer responses from link local name resolution protocols on non-domain networks over DNS responses when issuing queries for flat names. Examples of link local name resolution protocols include link local multicast name resolution (LLMNR) and NetBIOS over TCP/IP (NetBT).
-
-If you enable this policy setting, the DNS client will prefer DNS responses, followed by LLMNR, followed by NetBT for all networks.
-
-If you disable this policy setting, or if you do not configure this policy setting, the DNS client will prefer link local responses for flat name queries on non-domain networks.
-
-Note: This policy setting is applicable only if the turn off smart multi-homed name resolution policy setting is disabled or not configured.
- Allow NetBT queries for fully qualified domain names
- Specifies that NetBIOS over TCP/IP (NetBT) queries are issued for fully qualified domain names.
-
-If you enable this policy setting, NetBT queries will be issued for multi-label and fully qualified domain names such as "www.example.com" in addition to single-label names.
-
-If you disable this policy setting, or if you do not configure this policy setting, NetBT queries will only be issued for single-label names such as "example" and not for multi-label and fully qualified domain names.
- Prefer link local responses over DNS when received over a network with higher precedence
- Specifies that responses from link local name resolution protocols received over a network interface that is higher in the binding order are preferred over DNS responses from network interfaces lower in the binding order. Examples of link local name resolution protocols include link local multicast name resolution (LLMNR) and NetBIOS over TCP/IP (NetBT).
-
-If you enable this policy setting, responses from link local protocols will be preferred over DNS responses if the local responses are from a network with a higher binding order.
-
-If you disable this policy setting, or if you do not configure this policy setting, then DNS responses from networks lower in the binding order will be preferred over responses from link local protocols received from networks higher in the binding order.
-
-Note: This policy setting is applicable only if the turn off smart multi-homed name resolution policy setting is disabled or not configured.
- Turn off IDN encoding
- Specifies whether the DNS client should convert internationalized domain names (IDNs) to Punycode when the computer is on non-domain networks with no WINS servers configured.
-
-If this policy setting is enabled, IDNs are not converted to Punycode.
-
-If this policy setting is disabled, or if this policy setting is not configured, IDNs are converted to Punycode when the computer is on non-domain networks with no WINS servers configured.
- IDN mapping
- Specifies whether the DNS client should convert internationalized domain names (IDNs) to the Nameprep form, a canonical Unicode representation of the string.
-
-If this policy setting is enabled, IDNs are converted to the Nameprep form.
-
-If this policy setting is disabled, or if this policy setting is not configured, IDNs are not converted to the Nameprep form.
- Configure DNS over HTTPS (DoH) name resolution
- Prohibit DoH
- Allow DoH
- Require DoH
- Specifies if the DNS client will perform name resolution over DNS over HTTPS (DoH).
-
-By default, the DNS client will do classic DNS name resolution (over UDP or TCP). This setting can enhance the DNS client to use DoH protocol to resolve domain names.
-
-To use this policy setting, click Enabled, and then select one of the following options from the drop-down list:
-
-Prohibit DoH: No DoH name resolution will be performed.
-
-Allow DoH: Perform DoH queries if the configured DNS servers support it. If they don't support it, try classic name resolution.
-
-Require DoH: Allow only DoH name resolution. If there are no DoH capable DNS servers configured, name resolution will fail.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers will use locally configured settings. DDR (Discovery of Designated Resolvers) plaintext traffic is allowed as it is necessary for auto-discovering DoH settings.
- Configure NetBIOS settings
- Disable NetBIOS name resolution
- Allow NetBIOS name resolution
- Disable NetBIOS name resolution on public networks
- NetBIOS learning mode
- Specifies if the DNS client will perform name resolution over NetBIOS.
-
-By default, the DNS client will disable NetBIOS name resolution on public networks for security reasons.
-
-To use this policy setting, click Enabled, and then select one of the following options from the drop-down list:
-
-Disable NetBIOS name resolution: Never allow NetBIOS name resolution.
-
-Allow NetBIOS name resolution: Always allow NetBIOS name resolution.
-
-Disable NetBIOS name resolution on public networks: Only allow NetBIOS name resolution on network adapters which are not connected to public networks.
-
-NetBIOS learning mode: Always allow NetBIOS name resolution and use it as a fallback after mDNS/LLMNR queries fail.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers will use locally configured settings.
- Configure Discovery of Designated Resolvers (DDR) protocol
- Specifies if the DNS client would use the DDR protocol.
-
-The Discovery of Designated Resolvers (DDR) protocol allows Windows to move from unencrypted DNS to encrypted DNS when only the IP address of a resolver is known.
-
-If you enable this policy, the DNS client will use the DDR protocol.
-
-If you disable this policy setting, or if you do not configure this policy setting, computers will use locally configured settings.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Register PTR records:
-
-
- Seconds:
-
-
- Set the primary DNS suffix devolution level
-
-
- Seconds:
-
-
-
-
-
-
-
- Update security level:
-
-
- Configure DoH options:
-
-
- Configure NetBIOS options:
-
-
-
-
diff --git a/policy_templates/en-US/EAIME.adml b/policy_templates/en-US/EAIME.adml
deleted file mode 100644
index 5b15c7e..0000000
--- a/policy_templates/en-US/EAIME.adml
+++ /dev/null
@@ -1,180 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- IME
- Turn on misconversion logging for misconversion report
- This policy setting allows you to turn on logging of misconversion for the misconversion report.
-
-If you enable this policy setting, misconversion logging is turned on.
-
-If you disable or do not configure this policy setting, misconversion logging is turned off.
-
-This policy setting applies to Japanese Microsoft IME and Traditional Chinese IME.
- Turn off saving auto-tuning data to file
- This policy setting allows you to turn off saving the auto-tuning result to file.
-
-If you enable this policy setting, the auto-tuning data is not saved to file.
-
-If you disable or do not configure this policy setting, auto-tuning data is saved to file by default.
-
-This policy setting applies to Japanese Microsoft IME only.
- Turn off history-based predictive input
- This policy setting allows you to turn off history-based predictive input.
-
-If you enable this policy setting, history-based predictive input is turned off.
-
-If you disable or do not configure this policy setting, history-based predictive input is on by default.
-
-This policy setting applies to Japanese Microsoft IME only.
-
-Note: Changes to this setting will not take effect until the user logs off.
- Turn off Open Extended Dictionary
- This policy setting allows you to turn off Open Extended Dictionary.
-
-If you enable this policy setting, Open Extended Dictionary is turned off. You cannot add a new Open Extended Dictionary.
-
-For Japanese Microsoft IME, an Open Extended Dictionary that is added before enabling this policy setting is not used for conversion.
-
-If you disable or do not configure this policy setting, Open Extended Dictionary can be added and used by default.
-
-This policy setting is applied to Japanese Microsoft IME.
- Turn off Internet search integration
- This policy setting allows you to turn off Internet search integration.
-
-Search integration includes both using Search Provider (Japanese Microsoft IME) and performing bing search from predictive input for Japanese Microsoft IME.
-
-If you enable this policy setting, you cannot use search integration.
-
-If you disable or do not configure this policy setting, the search integration function can be used by default.
-
-This policy setting applies to Japanese Microsoft IME.
-
-Note: Changes to this setting will not take effect until the user logs off.
- Turn off custom dictionary
- This policy setting allows you to turn off the ability to use a custom dictionary.
-
-If you enable this policy setting, you cannot add, edit, and delete words in the custom dictionary either with GUI tools or APIs. A word registered in the custom dictionary before enabling this policy setting can continue to be used for conversion.
-
-If you disable or do not configure this policy setting, the custom dictionary can be used by default.
-
-[Clear auto-tuning information] removes self-tuned words from the custom dictionary, even if a group policy setting is turned on. To do this, select Settings > Time & Language > Japanese Options > Microsoft IME Options. If compatibility mode is turned on, select Advanced options > Dictionary/Auto-tuning > [Clear auto-tuning information].
-
-[Clear input history] removes self-tuned words from the custom dictionary, even if a group policy setting is turned on. To do this, select Settings > Time & Language > Japanese Options > Microsoft IME Options > Learning and Dictionary > [Clear input history].
-
-This policy setting is applied to Japanese Microsoft IME.
-
-Note: Changes to this setting will not take effect until the user logs off.
- Restrict character code range of conversion
- This policy setting allows you to restrict character code range of conversion by setting character filter.
-
-If you enable this policy setting, then only the character code ranges specified by this policy setting are used for conversion of IME. You can specify multiple ranges by setting a value combined with a bitwise OR of following values:
-
-0x0001 // JIS208 area
-0x0002 // NEC special char code
-0x0004 // NEC selected IBM extended code
-0x0008 // IBM extended code
-0x0010 // Half width katakana code
-0x0100 // EUDC(GAIJI)
-0x0200 // S-JIS unmapped area
-0x0400 // Unicode char
-0x0800 // surrogate char
-0x1000 // IVS char
-0xFFFF // no definition.
-
-If you disable or do not configure this policy setting, no range of characters are filtered by default.
-
-This policy setting applies to Japanese Microsoft IME only.
-
-Note: Changes to this setting will not take effect until the user logs off.
- Do not include Non-Publishing Standard Glyph in the candidate list
- This policy setting allows you to include the Non-Publishing Standard Glyph in the candidate list when Publishing Standard Glyph for the word exists.
-
-If you enable this policy setting, Non-Publishing Standard Glyph is not included in the candidate list when Publishing Standard Glyph for the word exists.
-
-If you disable or do not configure this policy setting, both Publishing Standard Glyph and Non-Publishing Standard Glyph are included in the candidate list.
-
-This policy setting applies to Japanese Microsoft IME only.
-
-Note: Changes to this setting will not take effect until the user logs off.
- Turn on cloud candidate
- This policy setting controls the cloud candidates feature, which uses an online service to provide input suggestions that don't exist in a PC's local dictionary.
-
-If you enable this policy setting, the functionality associated with this feature is turned on, the user's keyboard input is sent to Microsoft to generate the suggestions, and the user won't be able to turn it off.
-
-If you disable this policy setting, the functionality associated with this feature is turned off, and the user won't be able to turn it on.
-
-If you don't configure this policy setting, it will be turned off by default, and the user can turn on and turn off the cloud candidates feature.
-
-This Policy setting applies to Microsoft CHS Pinyin IME and JPN IME.
- Turn on cloud candidate for CHS
- This policy setting controls the cloud candidates feature, which uses an online service to provide input suggestions that don't exist in a PC's local dictionary.
-
-If you enable this policy setting, the functionality associated with this feature is turned on, the user's keyboard input is sent to Microsoft to generate the suggestions, and the user won't be able to turn it off.
-
-If you disable this policy setting, the functionality associated with this feature is turned off, and the user won't be able to turn it on.
-
-If you don't configure this policy setting, it will be turned off by default, and the user can turn on and turn off the cloud candidates feature.
-
-This Policy setting applies only to Microsoft CHS Pinyin IME.
- Configure Simplified Chinese IME version
- This policy setting controls the version of Microsoft IME.
-
-If you don’t configure this policy setting, user can control IME version to use. The new Microsoft IME is on by default.
-
-If you enable this, user is not allowed to control IME version to use. The previous version of Microsoft IME is always selected.
-
-If you disable this, user is not allowed to control IME version to use. The new Microsoft IME is always selected.
-
-This Policy setting applies only to Microsoft Simplified Chinese IME.
-
-Note: Changes to this setting will not take effect until the user logs off.
- Configure Traditional Chinese IME version
- This policy setting controls the version of Microsoft IME.
-
-If you don’t configure this policy setting, user can control IME version to use. The new Microsoft IME is on by default.
-
-If you enable this, user is not allowed to control IME version to use. The previous version of Microsoft IME is always selected.
-
-If you disable this, user is not allowed to control IME version to use. The new Microsoft IME is always selected.
-
-This Policy setting applies only to Microsoft Traditional Chinese IME.
-
-Note: Changes to this setting will not take effect until the user logs off.
- Configure Japanese IME version
- This policy setting controls the version of Microsoft IME.
-
-If you don’t configure this policy setting, user can control IME version to use. The new Microsoft IME is on by default.
-
-If you enable this, user is not allowed to control IME version to use. The previous version of Microsoft IME is always selected.
-
-If you disable this, user is not allowed to control IME version to use. The new Microsoft IME is always selected.
-
-This Policy setting applies only to Microsoft Japanese IME.
-
-Note: Changes to this setting will not take effect until the user logs off.
- Configure Korean IME version
- This policy setting controls the version of Microsoft IME.
-
-If you don’t configure this policy setting, user can control IME version to use. The new Microsoft IME is on by default.
-
-If you enable this, user is not allowed to control IME version to use. The previous version of Microsoft IME is always selected.
-
-If you disable this, user is not allowed to control IME version to use. The new Microsoft IME is always selected.
-
-This Policy setting applies only to Microsoft Korean IME.
-
-Note: Changes to this setting will not take effect until the user logs off.
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/EarlyLaunchAM.adml b/policy_templates/en-US/EarlyLaunchAM.adml
deleted file mode 100644
index 3685dd2..0000000
--- a/policy_templates/en-US/EarlyLaunchAM.adml
+++ /dev/null
@@ -1,31 +0,0 @@
-
- enter display name here
- enter description here
-
-
- Early Launch Antimalware
- Boot-Start Driver Initialization Policy
- This policy setting allows you to specify which boot-start drivers are initialized based on a classification determined by an Early Launch Antimalware boot-start driver. The Early Launch Antimalware boot-start driver can return the following classifications for each boot-start driver:
-- Good: The driver has been signed and has not been tampered with.
-- Bad: The driver has been identified as malware. It is recommended that you do not allow known bad drivers to be initialized.
-- Bad, but required for boot: The driver has been identified as malware, but the computer cannot successfully boot without loading this driver.
-- Unknown: This driver has not been attested to by your malware detection application and has not been classified by the Early Launch Antimalware boot-start driver.
-
-If you enable this policy setting you will be able to choose which boot-start drivers to initialize the next time the computer is started.
-
-If you disable or do not configure this policy setting, the boot start drivers determined to be Good, Unknown or Bad but Boot Critical are initialized and the initialization of drivers determined to be Bad is skipped.
-
-If your malware detection application does not include an Early Launch Antimalware boot-start driver or if your Early Launch Antimalware boot-start driver has been disabled, this setting has no effect and all boot-start drivers are initialized.
-
- Good only
- Good and unknown
- Good, unknown and bad but critical
- All
-
-
-
- Choose the boot-start drivers that can be initialized:
-
-
-
-
diff --git a/policy_templates/en-US/EdgeUI.adml b/policy_templates/en-US/EdgeUI.adml
deleted file mode 100644
index 8d1010f..0000000
--- a/policy_templates/en-US/EdgeUI.adml
+++ /dev/null
@@ -1,54 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Edge UI
- Contains settings related to system user interfaces attached to the screen edges.
- Turn off switching between recent apps
- If you enable this setting, users will not be allowed to switch between recent apps. The App Switching option in the PC settings app will be disabled as well.
-
-If you disable or do not configure this policy setting, users will be allowed to switch between recent apps.
- Turn off tracking of app usage
- This policy setting prevents Windows from keeping track of the apps that are used and searched most frequently. If you enable this policy setting, apps will be sorted alphabetically in:
- - search results
- - the Search and Share panes
- - the drop-down app list in the Picker
-
- If you disable or don't configure this policy setting, Windows will keep track of the apps that are used and searched most frequently. Most frequently used apps will appear at the top.
- Do not show recent apps when the mouse is pointing to the upper-left corner of the screen
- This policy setting allows you to prevent the last app and the list of recent apps from appearing when the mouse is pointing to the upper-left corner of the screen.
-
-If you enable this policy setting, the user will no longer be able to switch to recent apps using the mouse. The user will still be able to switch apps using touch gestures, keyboard shortcuts, and the Start screen.
-
-If you disable or don't configure this policy setting, the recent apps will be available by default, and the user can configure this setting.
- Search, Share, Start, Devices, and Settings don't appear when the mouse is pointing to the upper-right corner of the screen
- This policy setting allows you to prevent Search, Share, Start, Devices, and Settings from appearing when the mouse is pointing to the upper-right corner of the screen.
-
-If you enable this policy setting, Search, Share, Start, Devices, and Settings will no longer appear when the mouse is pointing to the upper-right corner. They'll still be available if the mouse is pointing to the lower-right corner.
-
-If you disable or don't configure this policy setting, Search, Share, Start, Devices, and Settings will be available by default, and the user can configure this setting.
- Prevent users from replacing the Command Prompt with Windows PowerShell in the menu they see when they right-click the lower-left corner or press the Windows logo key+X
- This policy setting allows you to prevent users from replacing the Command Prompt with Windows PowerShell in the menu they see when they right-click the lower-left corner or press the Windows logo key + X.
-
-If you enable this policy setting, the Command Prompt will always be listed in that menu, and users won't be able to replace it with Windows PowerShell. Users will still be able to access Windows PowerShell, but not from that menu.
-
-If you disable or don't configure this policy setting, Command Prompt will be listed in the menu by default, and users can configure this setting.
-
- Disable help tips
- Disables help tips that Windows shows to the user.
-
-By default, Windows will show the user help tips until the user has successfully completed the scenarios.
-
-If this setting is enabled, Windows will not show any help tips to the user.
-
- Allow edge swipe
- If you disable this policy setting, users will not be able to invoke any system UI by swiping in from any screen edge.
-
-If you enable or do not configure this policy setting, users will be able to invoke system UI by swiping in from the screen edges.
-
-
-
-
diff --git a/policy_templates/en-US/EncryptFilesonMove.adml b/policy_templates/en-US/EncryptFilesonMove.adml
deleted file mode 100644
index 8ed87e2..0000000
--- a/policy_templates/en-US/EncryptFilesonMove.adml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Do not automatically encrypt files moved to encrypted folders
- This policy setting prevents File Explorer from encrypting files that are moved to an encrypted folder.
-
-If you enable this policy setting, File Explorer will not automatically encrypt files that are moved to an encrypted folder.
-
-If you disable or do not configure this policy setting, File Explorer automatically encrypts files that are moved to an encrypted folder.
-
-This setting applies only to files moved within a volume. When files are moved to other volumes, or if you create a new file in an encrypted folder, File Explorer encrypts those files automatically.
-
-
-
diff --git a/policy_templates/en-US/EnhancedStorage.adml b/policy_templates/en-US/EnhancedStorage.adml
deleted file mode 100644
index 2a8adf0..0000000
--- a/policy_templates/en-US/EnhancedStorage.adml
+++ /dev/null
@@ -1,75 +0,0 @@
-
-
-
- Enhanced Storage Devices Group Policies
- Group Policies for managing Enhanced Storage devices
-
-
- Enhanced Storage Access
-
- Allow only USB root hub connected Enhanced Storage devices
- This policy setting configures whether or not only USB root hub connected Enhanced Storage devices are allowed. Allowing only root hub connected Enhanced Storage devices minimizes the risk of an unauthorized USB device reading data on an Enhanced Storage device.
-
-If you enable this policy setting, only USB root hub connected Enhanced Storage devices are allowed.
-
-If you disable or do not configure this policy setting, USB Enhanced Storage devices connected to both USB root hubs and non-root hubs will be allowed.
-
- Lock Enhanced Storage when the computer is locked
- This policy setting locks Enhanced Storage devices when the computer is locked.
-
-This policy setting is supported in Windows Server SKUs only.
-
-If you enable this policy setting, the Enhanced Storage device remains locked when the computer is locked.
-
-If you disable or do not configure this policy setting, the Enhanced Storage device state is not changed when the computer is locked.
-
- Do not allow non-Enhanced Storage removable devices
- This policy setting configures whether or not non-Enhanced Storage removable devices are allowed on your computer.
-
-If you enable this policy setting, non-Enhanced Storage removable devices are not allowed on your computer.
-
-If you disable or do not configure this policy setting, non-Enhanced Storage removable devices are allowed on your computer.
-
- Do not allow password authentication of Enhanced Storage devices
- This policy setting configures whether or not a password can be used to unlock an Enhanced Storage device.
-
-If you enable this policy setting, a password cannot be used to unlock an Enhanced Storage device.
-
-If you disable or do not configure this policy setting, a password can be used to unlock an Enhanced Storage device.
-
- Do not allow Windows to activate Enhanced Storage devices
- This policy setting configures whether or not Windows will activate an Enhanced Storage device.
-
-If you enable this policy setting, Windows will not activate unactivated Enhanced Storage devices.
-
-If you disable or do not configure this policy setting, Windows will activate unactivated Enhanced Storage devices.
-
- Configure list of Enhanced Storage devices usable on your computer
- This policy setting allows you to configure a list of Enhanced Storage devices by manufacturer and product ID that are usable on your computer.
-
-If you enable this policy setting, only Enhanced Storage devices that contain a manufacturer and product ID specified in this policy are usable on your computer.
-
-If you disable or do not configure this policy setting, all Enhanced Storage devices are usable on your computer.
-
-
- Configure list of IEEE 1667 silos usable on your computer
- This policy setting allows you to create a list of IEEE 1667 silos, compliant with the Institute of Electrical and Electronics Engineers, Inc. (IEEE) 1667 specification, that are usable on your computer.
-
-If you enable this policy setting, only IEEE 1667 silos that match a silo type identifier specified in this policy are usable on your computer.
-
-If you disable or do not configure this policy setting, all IEEE 1667 silos on Enhanced Storage devices are usable on your computer.
-
-
-
- Usable Enhanced Storage Devices:
- The device identifier should be entered in the form "Vendor ID-Product ID" where "Vendor ID" is the Institute of Electrical and Electronics Engineers, Inc. (IEEE) issued organizationally unique identifier (OUI) of the manufacturer and "Product ID" is a string assigned by the manufacturer.
- For more information on how to obtain the manufacturer and product ID from the device search for "Enhanced Storage Access" on Microsoft TechNet.
-
-
- Usable IEEE 1667 Silo Type Identifiers:
- Each silo type identifier must be a separate entry.
- For more information on how to set a silo type identifier for this policy search for "Enhanced Storage Access" on Microsoft TechNet.
-
-
-
-
diff --git a/policy_templates/en-US/ErrorReporting.adml b/policy_templates/en-US/ErrorReporting.adml
deleted file mode 100644
index 88cf2c2..0000000
--- a/policy_templates/en-US/ErrorReporting.adml
+++ /dev/null
@@ -1,295 +0,0 @@
-
-
-
- Windows Error Reporting
- Windows Error Reporting
-
-
- Windows Error Reporting
- Advanced Error Reporting Settings
- Consent
- Default application reporting settings
- Do not report any application errors
- This policy setting controls whether errors in general applications are included in reports when Windows Error Reporting is enabled.
-
-If you enable this policy setting, you can instruct Windows Error Reporting in the Default pull-down menu to report either all application errors (the default setting), or no application errors.
-
-If the Report all errors in Microsoft applications check box is filled, all errors in Microsoft applications are reported, regardless of the setting in the Default pull-down menu. When the Report all errors in Windows check box is filled, all errors in Windows applications are reported, regardless of the setting in the Default dropdown list. The Windows applications category is a subset of Microsoft applications.
-
-If you disable or do not configure this policy setting, users can enable or disable Windows Error Reporting in Control Panel. The default setting in Control Panel is Upload all applications.
-
-This policy setting is ignored if the Configure Error Reporting policy setting is disabled or not configured.
-
-For related information, see the Configure Error Reporting and Report Operating System Errors policy settings.
- Report all application errors
- List of applications to never report errors for
- This policy setting controls Windows Error Reporting behavior for errors in general applications when Windows Error Reporting is turned on.
-
-If you enable this policy setting, you can create a list of applications that are never included in error reports. To create a list of applications for which Windows Error Reporting never reports errors, click Show under the Exclude errors for applications on this list setting, and then add or remove applications from the list of application file names in the Show Contents dialog box (example: notepad.exe). File names must always include the .exe file name extension. Errors that are generated by applications in this list are not reported, even if the Default Application Reporting Settings policy setting is configured to report all application errors.
-
-If this policy setting is enabled, the Exclude errors for applications on this list setting takes precedence. If an application is listed both in the List of applications to always report errors for policy setting, and in the exclusion list in this policy setting, the application is excluded from error reporting. You can also use the exclusion list in this policy setting to exclude specific Microsoft applications or parts of Windows if the check boxes for these categories are filled in the Default application reporting settings policy setting.
-
-If you disable or do not configure this policy setting, the Default application reporting settings policy setting takes precedence.
- List of applications to always report errors for
- This policy setting specifies applications for which Windows Error Reporting should always report errors.
-
-To create a list of applications for which Windows Error Reporting never reports errors, click Show under the Exclude errors for applications on this list setting, and then add or remove applications from the list of application file names in the Show Contents dialog box (example: notepad.exe). Errors that are generated by applications in this list are not reported, even if the Default Application Reporting Settings policy setting is configured to report all application errors.
-
-If you enable this policy setting, you can create a list of applications that are always included in error reporting. To add applications to the list, click Show under the Report errors for applications on this list setting, and edit the list of application file names in the Show Contents dialog box. The file names must include the .exe file name extension (for example, notepad.exe). Errors that are generated by applications on this list are always reported, even if the Default dropdown in the Default application reporting policy setting is set to report no application errors.
-
-If the Report all errors in Microsoft applications or Report all errors in Windows components check boxes in the Default Application Reporting policy setting are filled, Windows Error Reporting reports errors as if all applications in these categories were added to the list in this policy setting. (Note: The Microsoft applications category includes the Windows components category.)
-
-If you disable this policy setting or do not configure it, the Default application reporting settings policy setting takes precedence.
-
-Also see the ""Default Application Reporting"" and ""Application Exclusion List"" policies.
-
-This setting will be ignored if the 'Configure Error Reporting' setting is disabled or not configured.
- Configure Error Reporting
- This policy setting configures how errors are reported to Microsoft, and what information is sent when Windows Error Reporting is enabled.
-
-This policy setting does not enable or disable Windows Error Reporting. To turn Windows Error Reporting on or off, see the Turn off Windows Error Reporting policy setting in Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings.
-
-Important: If the Turn off Windows Error Reporting policy setting is not configured, then Control Panel settings for Windows Error Reporting override this policy setting.
-
-If you enable this policy setting, the setting overrides any user changes made to Windows Error Reporting settings in Control Panel, and default values are applied for any Windows Error Reporting policy settings that are not configured (even if users have changed settings by using Control Panel). If you enable this policy setting, you can configure the following settings in the policy setting:
-
-- ""Do not display links to any Microsoft ‘More information’ websites"": Select this option if you do not want error dialog boxes to display links to Microsoft websites.
-
-- ""Do not collect additional files"": Select this option if you do not want additional files to be collected and included in error reports.
-
-- ""Do not collect additional computer data"": Select this if you do not want additional information about the computer to be collected and included in error reports.
-
-- ""Force queue mode for application errors"": Select this option if you do not want users to report errors. When this option is selected, errors are stored in a queue directory, and the next administrator to log on to the computer can send the error reports to Microsoft.
-
-- ""Corporate file path"": Type a UNC path to enable Corporate Error Reporting. All errors are stored at the specified location instead of being sent directly to Microsoft, and the next administrator to log onto the computer can send the error reports to Microsoft.
-
-- ""Replace instances of the word ‘Microsoft’ with"": You can specify text with which to customize your error report dialog boxes. The word ""Microsoft"" is replaced with the specified text.
-
-If you do not configure this policy setting, users can change Windows Error Reporting settings in Control Panel. By default, these settings are Enable Reporting on computers that are running Windows XP, and Report to Queue on computers that are running Windows Server 2003.
-
-If you disable this policy setting, configuration settings in the policy setting are left blank.
-
-See related policy settings Display Error Notification (same folder as this policy setting), and Turn off Windows Error Reporting in Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings.
- Report operating system errors
- This policy setting controls whether errors in the operating system are included Windows Error Reporting is enabled.
-
-If you enable this policy setting, Windows Error Reporting includes operating system errors.
-
-If you disable this policy setting, operating system errors are not included in error reports.
-
-If you do not configure this policy setting, users can change this setting in Control Panel. By default, Windows Error Reporting settings in Control Panel are set to upload operating system errors.
-
-See also the Configure Error Reporting policy setting.
- Display Error Notification
- This policy setting controls whether users are shown an error dialog box that lets them report an error.
-
-If you enable this policy setting, users are notified in a dialog box that an error has occurred, and can display more details about the error. If the Configure Error Reporting policy setting is also enabled, the user can also report the error.
-
-If you disable this policy setting, users are not notified that errors have occurred. If the Configure Error Reporting policy setting is also enabled, errors are reported, but users receive no notification. Disabling this policy setting is useful for servers that do not have interactive users.
-
-If you do not configure this policy setting, users can change this setting in Control Panel, which is set to enable notification by default on computers that are running Windows XP Personal Edition and Windows XP Professional Edition, and disable notification by default on computers that are running Windows Server.
-
-See also the Configure Error Reporting policy setting.
- Configure Report Archive
- Store all
- This policy setting controls the behavior of the Windows Error Reporting archive.
-
-If you enable this policy setting, you can configure Windows Error Reporting archiving behavior. If Archive behavior is set to Store all, all data collected for each error report is stored in the appropriate location. If Archive behavior is set to Store parameters only, only the minimum information required to check for an existing solution is stored. The Maximum number of reports to store setting determines how many reports are stored before older reports are automatically deleted.
-
-If you disable or do not configure this policy setting, no Windows Error Reporting information is stored.
- Store parameters only
- Configure Corporate Windows Error Reporting
- This policy setting specifies a corporate server to which Windows Error Reporting sends reports (if you do not want to send error reports to Microsoft).
-
-If you enable this policy setting, you can specify the name or IP address of an error report destination server on your organization’s network. You can also select Connect using SSL to transmit error reports over a Secure Sockets Layer (SSL) connection, and specify a port number on the destination server for transmission.
-
-If you disable or do not configure this policy setting, Windows Error Reporting sends error reports to Microsoft.
- Always ask before sending data
- Customize consent settings
- This policy setting determines the consent behavior of Windows Error Reporting for specific event types.
-
-If you enable this policy setting, you can add specific event types to a list by clicking Show, and typing event types in the Value Name column of the Show Contents dialog box. Event types are those for generic, non-fatal errors: crash, no response, and kernel fault errors. For each specified event type, you can set a consent level of 0, 1, 2, 3, or 4.
-
-- 0 (Disable): Windows Error Reporting sends no data to Microsoft for this event type.
-
-- 1 (Always ask before sending data): Windows prompts the user for consent to send reports.
-
-- 2 (Send parameters): Windows Error Reporting automatically sends the minimum data required to check for an existing solution, and Windows prompts the user for consent to send any additional data requested by Microsoft.
-
-- 3 (Send parameters and safe additional data): Windows Error Reporting automatically sends the minimum data required to check for an existing solution, as well as data which Windows has determined (within a high probability) does not contain personally identifiable data, and prompts the user for consent to send any additional data requested by Microsoft.
-
-- 4 (Send all data): Any data requested by Microsoft is sent automatically.
-
-If you disable or do not configure this policy setting, then the default consent settings that are applied are those specified by the user in Control Panel, or in the Configure Default Consent policy setting.
- Disable
- Send all data
- Ignore custom consent settings
- This policy setting determines the behavior of the Configure Default Consent setting in relation to custom consent settings.
-
-If you enable this policy setting, the default consent levels of Windows Error Reporting always override any other consent policy setting.
-
-If you disable or do not configure this policy setting, custom consent policy settings for error reporting determine the consent level for specified event types, and the default consent setting determines only the consent level of any other error reports.
- Send parameters and safe additional data
- Send parameters
- Configure Default consent
- This policy setting determines the default consent behavior of Windows Error Reporting.
-
-If you enable this policy setting, you can set the default consent handling for error reports. The following list describes the Consent level settings that are available in the pull-down menu in this policy setting:
-
-- Always ask before sending data: Windows prompts users for consent to send reports.
-
-- Send parameters: Only the minimum data that is required to check for an existing solution is sent automatically, and Windows prompts users for consent to send any additional data that is requested by Microsoft.
-
-- Send parameters and safe additional data: the minimum data that is required to check for an existing solution, along with data which Windows has determined (within a high probability) does not contain personally-identifiable information is sent automatically, and Windows prompts the user for consent to send any additional data that is requested by Microsoft.
-
-- Send all data: any error reporting data requested by Microsoft is sent automatically.
-
-If this policy setting is disabled or not configured, then the consent level defaults to the highest-privacy setting: Always ask before sending data.
- Disable Windows Error Reporting
- This policy setting turns off Windows Error Reporting, so that reports are not collected or sent to either Microsoft or internal servers within your organization when software unexpectedly stops working or fails.
-
-If you enable this policy setting, Windows Error Reporting does not send any problem information to Microsoft. Additionally, solution information is not available in Security and Maintenance in Control Panel.
-
-If you disable or do not configure this policy setting, the Turn off Windows Error Reporting policy setting in Computer Configuration/Administrative Templates/System/Internet Communication Management/Internet Communication settings takes precedence. If Turn off Windows Error Reporting is also either disabled or not configured, user settings in Control Panel for Windows Error Reporting are applied.
- Prevent display of the user interface for critical errors
- This policy setting prevents the display of the user interface for critical errors.
-
-If you enable or do not configure this policy setting, Windows Error Reporting does not display any GUI-based error messages or dialog boxes for critical errors.
-
-If you disable this policy setting, Windows Error Reporting displays the GUI-based error messages or dialog boxes for critical errors.
- List of applications to be excluded
- This policy setting limits Windows Error Reporting behavior for errors in general applications when Windows Error Reporting is turned on.
-
-If you enable this policy setting, you can create a list of applications that are never included in error reports. To create a list of applications for which Windows Error Reporting never reports errors, click Show, and then add or remove applications from the list of application file names in the Show Contents dialog box (example: notepad.exe). File names must always include the .exe file name extension. To remove an application from the list, click the name, and then press DELETE. If this policy setting is enabled, the Exclude errors for applications on this list setting takes precedence.
-
-If you disable or do not configure this policy setting, errors are reported on all Microsoft and Windows applications by default.
- Always queue for administrator
- Always queue
- Disable logging
- This policy setting controls whether Windows Error Reporting saves its own events and error messages to the system event log.
-
-If you enable this policy setting, Windows Error Reporting events are not recorded in the system event log.
-
-If you disable or do not configure this policy setting, Windows Error Reporting events and errors are logged to the system event log, as with other Windows-based programs.
- Do not send additional data
- This policy setting controls whether additional data in support of error reports can be sent to Microsoft automatically.
-
-If you enable this policy setting, any additional data requests from Microsoft in response to a Windows Error Reporting report are automatically declined, without notification to the user.
-
-If you disable or do not configure this policy setting, then consent policy settings in Computer Configuration/Administrative Templates/Windows Components/Windows Error Reporting/Consent take precedence.
- Configure Report Queue
- This policy setting determines the behavior of the Windows Error Reporting report queue.
-
-If you enable this policy setting, you can configure report queue behavior by using the controls in the policy setting. When the Queuing behavior pull-down list is set to Default, Windows determines, when a problem occurs, whether the report should be placed in the reporting queue, or the user should be prompted to send it immediately. When Queuing behavior is set to Always queue, all reports are added to the queue until the user is prompted to send the reports, or until the user sends problem reports by using the Solutions to Problems page in Control Panel. If Queuing behavior is set to Always queue for administrator, reports are queued until an administrator is prompted to send them, or until the administrator sends them by using the Solutions to Problems page in Control Panel.
-
-The Maximum number of reports to queue setting determines how many reports can be queued before older reports are automatically deleted. The setting for Number of days between solution check reminders determines the interval time between the display of system notifications that remind the user to check for solutions to problems. A value of 0 disables the reminder.
-
-If you disable or do not configure this policy setting, Windows Error Reporting reports are not queued, and users can only send reports at the time that a problem occurs.
- This policy setting determines the behavior of the Windows Error Reporting report queue.
-
-If you enable this policy setting, you can configure report queue behavior by using the controls in the policy setting. When the Queuing behavior pull-down list is set to Default, Windows determines, when a problem occurs, whether the report should be placed in the reporting queue, or the user should be prompted to send it immediately. When Queuing behavior is set to Always queue, all reports are added to the queue until the user is prompted to send the reports, or until the user sends problem reports by using the Solutions to Problems page in Control Panel.
-
-The Maximum number of reports to queue setting determines how many reports can be queued before older reports are automatically deleted. The setting for Number of days between solution check reminders determines the interval time between the display of system notifications that remind the user to check for solutions to problems. A value of 0 disables the reminder.
-
-If you disable or do not configure this policy setting, Windows Error Reporting reports are not queued, and users can only send reports at the time that a problem occurs.
- Default
- Do not throttle additional data
- This policy setting determines whether Windows Error Reporting (WER) sends additional, second-level report data even if a CAB file containing data about the same event types has already been uploaded to the server.
-
-If you enable this policy setting, WER does not throttle data; that is, WER uploads additional CAB files that can contain data about the same event types as an earlier uploaded report.
-
-If you disable or do not configure this policy setting, WER throttles data by default; that is, WER does not upload more than one CAB file for a report that contains data about the same event types.
- Send additional data when on battery power
- This policy setting determines whether Windows Error Reporting (WER) checks if the computer is running on battery power. By default, when a computer is running on battery power, WER only checks for solutions, but does not upload additional report data until the computer is connected to a more permanent power source.
-
-If you enable this policy setting, WER does not determine whether the computer is running on battery power, but checks for solutions and uploads report data normally.
-
-If you disable or do not configure this policy setting, WER checks for solutions while a computer is running on battery power, but does not upload report data until the computer is connected to a more permanent power source.
- Send data when on connected to a restricted/costed network
- This policy setting determines whether Windows Error Reporting (WER) checks for a network cost policy that restricts the amount of data that is sent over the network.
-
-If you enable this policy setting, WER does not check for network cost policy restrictions, and transmits data even if network cost is restricted.
-
-If you disable or do not configure this policy setting, WER does not send data, but will check the network cost policy again if the network profile is changed.
- Automatically send memory dumps for OS-generated error reports
- This policy setting controls whether memory dumps in support of OS-generated error reports can be sent to Microsoft automatically. This policy does not apply to error reports generated by 3rd-party products, or additional data other than memory dumps.
-
-If you enable or do not configure this policy setting, any memory dumps generated for error reports by Microsoft Windows are automatically uploaded, without notification to the user.
-
-If you disable this policy setting, then all memory dumps are uploaded according to the default consent and notification settings.
-
-
-
-
- Default:
- Report all errors in Microsoft applications.
- Report all errors in Windows components.
-
-
- Exclude errors for applications on this list:
-
-
- Report errors for applications on this list:
-
-
- Do not display links to any Microsoft provided 'more information' web sites.
- Do not collect additional files
- Do not collect additional machine data
- Force queue mode for application errors
-
-
-
-
-
-
-
-
- Archive behavior:
- Maximum number of reports to store:
-
-
- Archive behavior:
- Maximum number of reports to store:
-
-
-
-
-
- Connect using SSL
- Only upload on free networks
- Server port:
-
-
- Customize consent settings
-
-
- Customize consent settings
-
-
- Consent level
-
-
- Consent level
-
-
- List of applications to be excluded
-
-
- List of applications to be excluded
-
-
- Queuing behavior:
- Maximum number of reports to queue:
- Maximum size of the queue (MB):
- Number of days between solution check reminders:
-
-
- Queuing behavior:
- Maximum number of reports to queue:
- Maximum size of the queue (MB):
- Minimum free disk space (MB):
- Number of days between solution check reminders:
-
-
-
-
diff --git a/policy_templates/en-US/EventForwarding.adml b/policy_templates/en-US/EventForwarding.adml
deleted file mode 100644
index 4903ad5..0000000
--- a/policy_templates/en-US/EventForwarding.adml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
- Event Forwarding
-
- Policy Definitions For Event Forwarding
-
-
-
-
-
- Event Forwarding
-
- Configure forwarder resource usage
- This policy setting controls resource usage for the forwarder (source computer) by controlling the events/per second sent to the Event Collector.
-
-If you enable this policy setting, you can control the volume of events sent to the Event Collector by the source computer. This may be required in high volume environments.
-
-If you disable or do not configure this policy setting, forwarder resource usage is not specified.
-
-This setting applies across all subscriptions for the forwarder (source computer).
-
- Configure target Subscription Manager
-
- This policy setting allows you to configure the server address, refresh interval, and issuer certificate authority (CA) of a target Subscription Manager.
-
-If you enable this policy setting, you can configure the Source Computer to contact a specific FQDN (Fully Qualified Domain Name) or IP Address and request subscription specifics.
-
-Use the following syntax when using the HTTPS protocol:
-Server=https://<FQDN of the collector>:5986/wsman/SubscriptionManager/WEC,Refresh=<Refresh interval in seconds>,IssuerCA=<Thumb print of the client authentication certificate>. When using the HTTP protocol, use port 5985.
-
-If you disable or do not configure this policy setting, the Event Collector computer will not be specified.
-
- SubscriptionManagers
-
-
-
-
-
-
-
- SubscriptionManagers
-
-
-
-
-
- The maximum forwarding rate ( events/sec ) allowed for the forwarder:
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/EventLog.adml b/policy_templates/en-US/EventLog.adml
deleted file mode 100644
index 9acf96b..0000000
--- a/policy_templates/en-US/EventLog.adml
+++ /dev/null
@@ -1,173 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Back up log automatically when full
- This policy setting controls Event Log behavior when the log file reaches its maximum size and takes effect only if the "Retain old events" policy setting is enabled.
-
-If you enable this policy setting and the "Retain old events" policy setting is enabled, the Event Log file is automatically closed and renamed when it is full. A new file is then started.
-
-If you disable this policy setting and the "Retain old events" policy setting is enabled, new events are discarded and old events are retained.
-
-If you do not configure this policy setting and the "Retain old events" policy setting is enabled, new events are discarded and the old events are retained.
- Configure log access
- Configure log access (legacy)
- This policy setting specifies the security descriptor to use for the log using the Security Descriptor Definition Language (SDDL) string.
-
-If you enable this policy setting, only those users matching the security descriptor can access the log.
-
-If you disable or do not configure this policy setting, all authenticated users and system services can write, read, or clear this log.
-
-Note: If you enable this policy setting, some tools and APIs may ignore it. The same change should be made to the "Configure log access (legacy)" policy setting to enforce this change across all tools and APIs.
- This policy setting specifies the security descriptor to use for the log using the Security Descriptor Definition Language (SDDL) string. You must set both "configure log access" policy settings for this log in order to affect the both modern and legacy tools.
-
-If you enable this policy setting, only those users matching the security descriptor can access the log.
-
-If you disable this policy setting, all authenticated users and system services can write, read, or clear this log.
-
-If you do not configure this policy setting, the previous policy setting configuration remains in effect.
- This policy setting specifies the security descriptor to use for the log using the Security Descriptor Definition Language (SDDL) string. You cannot configure write permissions for this log. You must set both "configure log access" policy settings for this log in order to affect the both modern and legacy tools.
-
-If you enable this policy setting, only those users whose security descriptor matches the configured specified value can access the log.
-
-If you disable or do not configure this policy setting, only system software and administrators can read or clear this log.
-
-Note: If you enable this policy setting, some tools and APIs may ignore it. The same change should be made to the "Configure log access (legacy)" policy setting to enforce this change across all tools and APIs.
- This policy setting specifies the security descriptor to use for the log using the Security Descriptor Definition Language (SDDL) string. You cannot configure write permissions for this log.
-
-If you enable this policy setting, only those users whose security descriptor matches the configured specified value can access the log.
-
-If you disable this policy setting, only system software and administrators can read or clear this log.
-
-If you do not configure this policy setting, the previous policy setting configuration remains in effect.
- This policy setting specifies the security descriptor to use for the log using the Security Descriptor Definition Language (SDDL) string. You must set both "configure log access" policy settings for this log in order to affect the both modern and legacy tools.
-
-If you enable this policy setting, only users whose security descriptor matches the configured value can access the log.
-
-If you disable or do not configure this policy setting, only system software and administrators can write or clear this log, and any authenticated user can read events from it.
-
-Note: If you enable this policy setting, some tools and APIs may ignore it. The same change should be made to the "Configure log access (legacy)" policy setting to enforce this change across all tools and APIs.
- This policy setting specifies the security descriptor to use for the log using the Security Descriptor Definition Language (SDDL) string.
-
-If you enable this policy setting, only users whose security descriptor matches the configured value can access the log.
-
-If you disable this policy setting, only system software and administrators can write or clear this log, and any authenticated user can read events from it.
-
-If you do not configure this policy setting, the previous policy setting configuration remains in effect.
- Control Event Log behavior when the log file reaches its maximum size
- This policy setting controls Event Log behavior when the log file reaches its maximum size.
-
-If you enable this policy setting and a log file reaches its maximum size, new events are not written to the log and are lost.
-
-If you disable or do not configure this policy setting and a log file reaches its maximum size, new events overwrite old events.
-
-Note: Old events may or may not be retained according to the "Backup log automatically when full" policy setting.
- Turn on logging
- This policy setting turns on logging.
-
-If you enable or do not configure this policy setting, then events can be written to this log.
-
-If the policy setting is disabled, then no new events can be logged. Events can always be read from the log, regardless of this policy setting.
- Control the location of the log file
- This policy setting controls the location of the log file. The location of the file must be writable by the Event Log service and should only be accessible to administrators.
-
-If you enable this policy setting, the Event Log uses the path specified in this policy setting.
-
-If you disable or do not configure this policy setting, the Event Log uses the folder %SYSTEMROOT%\System32\winevt\Logs.
- Specify the maximum log file size (KB)
- This policy setting specifies the maximum size of the log file in kilobytes.
-
-If you enable this policy setting, you can configure the maximum log file size to be between 1 megabyte (1024 kilobytes) and 2 terabytes (2147483647 kilobytes), in kilobyte increments.
-
-If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog, and it defaults to 1 megabyte.
- This policy setting specifies the maximum size of the log file in kilobytes.
-
-If you enable this policy setting, you can configure the maximum log file size to be between 20 megabytes (20480 kilobytes) and 2 terabytes (2147483647 kilobytes), in kilobyte increments.
-
-If you disable or do not configure this policy setting, the maximum size of the log file will be set to the locally configured value. This value can be changed by the local administrator using the Log Properties dialog, and it defaults to 20 megabytes.
- Configuration Settings for log
- Application
- Security
- Setup
- System
- Event Log Service
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Maximum Log Size (KB)
-
-
- Maximum Log Size (KB)
-
-
- Maximum Log Size (KB)
-
-
- Maximum Log Size (KB)
-
-
-
-
diff --git a/policy_templates/en-US/EventLogging.adml b/policy_templates/en-US/EventLogging.adml
deleted file mode 100644
index c5eaec6..0000000
--- a/policy_templates/en-US/EventLogging.adml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
- Event Logging
- This file contains the configuration options for Windows Event Logging
-
-
- Event Logging
- Enable Protected Event Logging
-
-This policy setting lets you configure Protected Event Logging.
-
-If you enable this policy setting, components that support it will use the certificate you supply to encrypt potentially sensitive event log data before writing it to the event log. Data will be encrypted using the Cryptographic Message Syntax (CMS) standard and the public key you provide. You can use the Unprotect-CmsMessage PowerShell cmdlet to decrypt these encrypted messages, provided that you have access to the private key corresponding to the public key that they were encrypted with.
-
-If you disable or do not configure this policy setting, components will not encrypt event log messages before writing them to the event log.
-
-
-
-
-
-Provide an encryption certificate to be used by Protected Event Logging. You may provide either:
-
- - The content of a base-64 encoded X.509 certificate
- - The thumbprint of a certificate that can be found in the Local Machine certificate store (usually deployed by PKI infrastructure)
- - The full path to a certificate (can be local, or a remote share)
- - The path to a directory containing a certificate or certificates (can be local, or a remote share)
- - The subject name of a certificate that can be found in the Local Machine certificate store (usually deployed by PKI infrastructure)
-
-The resulting certificate must have 'Document Encryption' as an enhanced key usage (1.3.6.1.4.1.311.80.1), as well as either Data Encipherment or Key Encipherment key usages enabled.
-
-
-
-
-
-
diff --git a/policy_templates/en-US/EventViewer.adml b/policy_templates/en-US/EventViewer.adml
deleted file mode 100644
index 990fa8f..0000000
--- a/policy_templates/en-US/EventViewer.adml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Event Viewer
- Events.asp program
- This is the program that will be invoked when the user clicks the events.asp link.
- Events.asp program command line parameters
- This specifies the command line parameters that will be passed to the events.asp program
- Events.asp URL
- This is the URL that will be passed to the Description area in the Event Properties dialog box. Change this value if you want to use a different Web server to handle event information requests.
-
-
-
-
-
- %SystemRoot%\PCHealth\HelpCtr\Binaries\HelpCtr.exe
-
-
-
-
-
- -url hcp://services/centers/support?topic=%s
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/ExploitGuard.adml b/policy_templates/en-US/ExploitGuard.adml
deleted file mode 100644
index 3457374..0000000
--- a/policy_templates/en-US/ExploitGuard.adml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Microsoft Defender Exploit Guard
- Exploit Protection
- Use a common set of exploit protection settings
- Specify a common set of Microsoft Defender Exploit Guard system and application mitigation settings that can be applied to all endpoints that have this GP setting configured.
-
-There are some prerequisites before you can enable this setting:
-- Manually configure a device's system and application mitigation settings using the Set-ProcessMitigation PowerShell cmdlet, the ConvertTo-ProcessMitigationPolicy PowerShell cmdlet, or directly in Windows Security.
-- Generate an XML file with the settings from the device by running the Get-ProcessMitigation PowerShell cmdlet or using the Export button at the bottom of the Exploit Protection area in Windows Security.
-- Place the generated XML file in a shared or local path.
-
-Note: Endpoints that have this GP setting set to Enabled must be able to access the XML file, otherwise the settings will not be applied.
-
-Enabled
-Specify the location of the XML file in the Options section. You can use a local (or mapped) path, a UNC path, or a URL, such as the following:
-- C:\MitigationSettings\Config.XML
-- \\Server\Share\Config.xml
-- https://localhost:8080/Config.xml
-
-The settings in the XML file will be applied to the endpoint.
-
-Disabled
-Common settings will not be applied, and the locally configured settings will be used instead.
-
-Not configured
-Same as Disabled.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/Explorer.adml b/policy_templates/en-US/Explorer.adml
deleted file mode 100644
index 3e8e773..0000000
--- a/policy_templates/en-US/Explorer.adml
+++ /dev/null
@@ -1,52 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Display the menu bar in File Explorer
- This policy setting configures File Explorer to always display the menu bar.
-
-Note: By default, the menu bar is not displayed in File Explorer.
-
-If you enable this policy setting, the menu bar will be displayed in File Explorer.
-
-If you disable or do not configure this policy setting, the menu bar will not be displayed in File Explorer.
-
-Note: When the menu bar is not displayed, users can access the menu bar by pressing the 'ALT' key.
- Prevent users from adding files to the root of their Users Files folder.
- This policy setting allows administrators to prevent users from adding new items such as files or folders to the root of their Users Files folder in File Explorer.
-
-If you enable this policy setting, users will no longer be able to add new items such as files or folders to the root of their Users Files folder in File Explorer.
-
-If you disable or do not configure this policy setting, users will be able to add new items such as files or folders to the root of their Users Files folder in File Explorer.
-
-
-Note: Enabling this policy setting does not prevent the user from being able to add new items such as files and folders to their actual file system profile folder at %userprofile%.
- Turn off common control and window animations
- This policy is similar to settings directly available to computer users. Disabling animations can improve usability for users with some visual disabilities as well as improving performance and battery life in some scenarios.
- Turn off Data Execution Prevention for Explorer
- Disabling data execution prevention can allow certain legacy plug-in applications to function without terminating Explorer.
- Turn off heap termination on corruption
- Disabling heap termination on corruption can allow certain legacy plug-in applications to function without terminating Explorer immediately, although Explorer may still terminate unexpectedly later.
- Set a support web page link
- Sets the target of the More Information link that will be displayed when the user attempts to run a program that is blocked by policy.
- Information URL
- Do not reinitialize a pre-existing roamed user profile when it is loaded on a machine for the first time
- This policy setting allows administrators who have configured roaming profile in conjunction with Delete Cached Roaming Profile Group Policy setting to ensure that Explorer will not reinitialize default program associations and other settings to default values.
-
-If you enable this policy setting on a machine that does not contain all programs installed in the same manner as it was on the machine on which the user had last logged on, unexpected behavior could occur.
- Turn off files from Office.com in Quick access view
- Turning off files from Office.com will prevent File Explorer from requesting recent cloud file metadata and displaying it in the Quick access view.
-
-
-
-
-
- http://msdn.microsoft.com
-
-
-
-
-
diff --git a/policy_templates/en-US/ExternalBoot.adml b/policy_templates/en-US/ExternalBoot.adml
deleted file mode 100644
index 4253894..0000000
--- a/policy_templates/en-US/ExternalBoot.adml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- Portable Workspace
- This file contains Portable Workspace policy settings.
-
-
- Portable Operating System
- Windows To Go Default Startup Options
-
-
-This policy setting controls whether the PC will boot to Windows To Go if a USB device containing a Windows To Go workspace is connected, and controls whether users can make changes using the Windows To Go Startup Options Control Panel item.
-
-If you enable this setting, booting to Windows To Go when a USB device is connected will be enabled, and users will not be able to make changes using the Windows To Go Startup Options Control Panel item.
-
-If you disable this setting, booting to Windows To Go when a USB device is connected will not be enabled unless a user configures the option manually in the BIOS or other boot order configuration.
-
-If you do not configure this setting, users who are members of the Administrators group can make changes using the Windows To Go Startup Options Control Panel item.
- Allow hibernate (S4) when starting from a Windows To Go workspace
-
-
-Specifies whether the PC can use the hibernation sleep state (S4) when started from a Windows To Go workspace.
-
-If you enable this setting, Windows, when started from a Windows To Go workspace, can hibernate the PC.
-
-If you disable or don't configure this setting, Windows, when started from a Windows To Go workspace, can't hibernate the PC.
- Disallow standby sleep states (S1-S3) when starting from a Windows to Go workspace
-
-
-Specifies whether the PC can use standby sleep states (S1-S3) when starting from a Windows To Go workspace.
-
-If you enable this setting, Windows, when started from a Windows To Go workspace, can't use standby states to make the PC sleep.
-
-If you disable or don't configure this setting, Windows, when started from a Windows To Go workspace, can use standby states to make the PC sleep.
-
-
-
diff --git a/policy_templates/en-US/FeedbackNotifications.adml b/policy_templates/en-US/FeedbackNotifications.adml
deleted file mode 100644
index f1d8c3d..0000000
--- a/policy_templates/en-US/FeedbackNotifications.adml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Do not show feedback notifications
- This policy setting allows an organization to prevent its devices from showing feedback questions from Microsoft.
-
-If you enable this policy setting, users will no longer see feedback notifications through the Windows Feedback app.
-
-If you disable or do not configure this policy setting, users may see notifications through the Windows Feedback app asking users for feedback.
-
-Note: If you disable or do not configure this policy setting, users can control how often they receive feedback questions.
-
-
-
diff --git a/policy_templates/en-US/FileHistory.adml b/policy_templates/en-US/FileHistory.adml
deleted file mode 100644
index 4fcd9a7..0000000
--- a/policy_templates/en-US/FileHistory.adml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- File History
- File History
-
-
- File History
- Turn off File History
- This policy setting allows you to turn off File History.
-
-If you enable this policy setting, File History cannot be activated to create regular, automatic backups.
-
-If you disable or do not configure this policy setting, File History can be activated to create regular, automatic backups.
-
-
-
diff --git a/policy_templates/en-US/FileRecovery.adml b/policy_templates/en-US/FileRecovery.adml
deleted file mode 100644
index b8f99a0..0000000
--- a/policy_templates/en-US/FileRecovery.adml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Corrupted File Recovery
- Configure Corrupted File Recovery behavior
- This policy setting allows you to configure the recovery behavior for corrupted files to one of three states:
-
-Regular: Detection, troubleshooting, and recovery of corrupted files will automatically start with a minimal UI display. Windows will attempt to present you with a dialog box when a system restart is required. This is the default recovery behavior for corrupted files.
-
-Silent: Detection, troubleshooting, and recovery of corrupted files will automatically start with no UI. Windows will log an administrator event when a system restart is required. This behavior is recommended for headless operation.
-
-Troubleshooting Only: Detection and troubleshooting of corrupted files will automatically start with no UI. Recovery is not attempted automatically. Windows will log an administrator event with instructions if manual recovery is possible.
-
-If you enable this setting, the recovery behavior for corrupted files will be set to either the regular (default), silent, or troubleshooting only state.
-
-If you disable this setting, the recovery behavior for corrupted files will be disabled. No troubleshooting or resolution will be attempted.
-
-If you do not configure this setting, the recovery behavior for corrupted files will be set to the regular recovery behavior.
-
-No system or service restarts are required for changes to this policy to take immediate effect after a Group Policy refresh.
-
-Note: This policy setting will take effect only when the Diagnostic Policy Service (DPS) is in the running state. When the service is stopped or disabled, system file recovery will not be attempted. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
- Regular
- Silent
- Troubleshooting Only
-
-
-
- Scenario Execution Level
-
-
-
-
diff --git a/policy_templates/en-US/FileRevocation.adml b/policy_templates/en-US/FileRevocation.adml
deleted file mode 100644
index d48f6ec..0000000
--- a/policy_templates/en-US/FileRevocation.adml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
-
- File Revocation Policy Settings
- File Revocation Policy Settings
-
-
- File Revocation
- Allow Windows Runtime apps to revoke enterprise data
- Windows Runtime applications can protect content which has been associated with an enterprise identifier (EID), but can only revoke access to content it protected. To allow an application to revoke access to all content on the device that is protected by a particular enterprise, add an entry to the list on a new line that contains the enterprise identifier, separated by a comma, and the Package Family Name of the application. The EID must be an internet domain belonging to the enterprise in standard international domain name format.
-
-Example value:
-Contoso.com,ContosoIT.HumanResourcesApp_m5g0r7arhahqy
-
-If you enable this policy setting, the application identified by the Package Family Name will be permitted to revoke access to all content protected using the specified EID on the device.
-
-If you disable or do not configure this policy setting, the only Windows Runtime applications that can revoke access to all enterprise-protected content on the device are Windows Mail and the user-selected mailto protocol handler app. Any other Windows Runtime application will only be able to revoke access to content it protected.
-
-Note: File revocation applies to all content protected under the same second level domain as the provided enterprise identifier. So, revoking an enterprise ID of mail.contoso.com will revoke the user’s access to all content protected under the contoso.com hierarchy.
-
-
-
- Apps permitted to revoke all protected data from the device for the specified enterprise identifier:
-
-
-
-
-
diff --git a/policy_templates/en-US/FileServerVSSProvider.adml b/policy_templates/en-US/FileServerVSSProvider.adml
deleted file mode 100644
index 02844bb..0000000
--- a/policy_templates/en-US/FileServerVSSProvider.adml
+++ /dev/null
@@ -1,23 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
-
- File Share Shadow Copy Provider
-
-
- Allow or Disallow use of encryption to protect the RPC protocol messages between File Share Shadow Copy Provider running on application server and File Share Shadow Copy Agent running on the file servers.
- Determines whether the RPC protocol messagese used by VSS for SMB2 File Shares feature is enabled.
-
-VSS for SMB2 File Shares feature enables VSS aware backup applications to perform application consistent backup and restore of VSS aware applications storing data on SMB2 File Shares.
-
-By default, the RPC protocol message between File Server VSS provider and File Server VSS Agent is signed but not encrypted.
-
-Note: To make changes to this setting effective, you must restart Volume Shadow Copy (VSS) Service .
-
-
-
-
diff --git a/policy_templates/en-US/FileSys.adml b/policy_templates/en-US/FileSys.adml
deleted file mode 100644
index 9eb86e8..0000000
--- a/policy_templates/en-US/FileSys.adml
+++ /dev/null
@@ -1,120 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Filesystem
- NTFS
- Symbolic links can introduce vulnerabilities in certain applications. To mitigate this issue, you can selectively enable or disable the evaluation of these types of symbolic links:
-
-Local Link to a Local Target
-Local Link to a Remote Target
-Remote Link to Remote Target
-Remote Link to Local Target
-
-For further information please refer to the Windows Help section
-
-NOTE: If this policy is Disabled or Not Configured, local administrators may select the types of symbolic links to be evaluated.
- Selectively allow the evaluation of a symbolic link
-
- Do not allow compression on all NTFS volumes
- Compression can add to the processing overhead of filesystem operations. Enabling this setting will prevent access to and creation of compressed files.
-
-A reboot is required for this setting to take effect
-
- Do not allow encryption on all NTFS volumes
- Encryption can add to the processing overhead of filesystem operations. Enabling this setting will prevent access to and creation of encrypted files.
-
-A reboot is required for this setting to take effect
-
- Enable NTFS pagefile encryption
- Encrypting the page file prevents malicious users from reading data that has been paged to disk, but also adds processing overhead for filesystem operations. Enabling this setting will cause the page files to be encrypted.
-
- Enable Win32 long paths
- Enabling Win32 long paths will allow manifested win32 applications and Windows Store applications to access paths beyond the normal 260 character limit. Enabling this setting will cause the long paths to be accessible within the process.
-
- Short name creation options
- These settings provide control over whether or not short names are generated during file creation. Some applications require short names for compatibility, but short names have a negative performance impact on the system.
-
-If you enable short names on all volumes then short names will always be generated. If you disable them on all volumes then they will never be generated. If you set short name creation to be configurable on a per volume basis then an on-disk flag will determine whether or not short names are created on a given volume. If you disable short name creation on all data volumes then short names will only be generated for files created on the system volume.
- Enable on all volumes
- Disable on all volumes
- Enable / disable on a per volume basis
- Disable on all data volumes
-
- Disable delete notifications on all volumes
- Delete notification is a feature that notifies the underlying storage device of clusters that are freed due to a file delete operation.
-
-A value of 0, the default, will enable delete notifications for all volumes.
-A value of 1 will disable delete notifications for all volumes.
-
- Enable / disable TXF deprecated features
- TXF deprecated features included savepoints, secondary RM, miniversion and roll forward. Please enable it if you want to use these APIs.
-
- Enable NTFS non-paged pool usage
- By default NTFS allocates memory from both pageable and non-pageable memory as needed. Enabling this setting tells NTFS to use non-pageable memory for all allocations. NTFS also changes all of its code sections to be non-pageable.
-
-The benefit of enabling this feature is a reduction in page-faults and stack usage at the cost of additional memory consumption.
-
-A reboot is required for this setting to take effect
-
- NTFS parallel flush threshold
- When flushing modified file data from memory, NTFS chooses to use one or more threads based on how many files are currently open. This setting gives control over the open file threshold used to trigger parallel flush.
-
- NTFS parallel flush worker threads
- When flushing modified file data from memory, NTFS chooses to use one or more threads based on how many files are currently open. This setting gives control over how many threads will be used.
-
-Making this value larger may decrease the time it takes to flush a volume but the flush may have a larger impact on other concurrent IO operations.
-
-Values with special meaning:
- 0: Use the system calculated default
- 1: Disable parallel flush
-
-The default value and limit for this setting varies based on the number of available processors on a given system:
- - Default value calculation is: (([NumProcessors]/2) + 1)
- - Default max value calculation is: ([NumProcessors]*2)
-
- NTFS default tier
- For NTFS tiered volumes this controls the tier that new allocations go to by default.
-
-Client systems default to the Performance tier.
-Server systems default to the Capacity tier.
- Capacity tier
- Performance tier
-
-
-
-
-
- Local Link to Local Target
- Local Link to a Remote Target
- Remote Link to Remote Target
- Remote Link to Local Target
-
-
-
-
-
-
- Short name creation options
-
-
-
-
-
- Open File Threshold:
-
-
-
- Open File Threshold:
-
-
-
- NTFS default tier options
-
-
-
-
-
diff --git a/policy_templates/en-US/FindMy.adml b/policy_templates/en-US/FindMy.adml
deleted file mode 100644
index 11593ed..0000000
--- a/policy_templates/en-US/FindMy.adml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Find My Device
- Configuration for FindMyDevice
-
-
- Find My Device
- Turn On/Off Find My Device
- This policy turns on Find My Device.
-
-When Find My Device is on, the device and its location are registered in the cloud so that the device can be located when the user initiates a Find command from account.microsoft.com. On devices that are compatible with active digitizers, enabling Find My Device will also allow the user to view the last location of use of their active digitizer on their device; this location is stored locally on the user's device after each use of their active digitizer.
-
-When Find My Device is off, the device and its location are not registered and the Find My Device feature will not work.The user will also not be able to view the location of the last use of their active digitizer on their device.
-
-
-
-
diff --git a/policy_templates/en-US/FolderRedirection.adml b/policy_templates/en-US/FolderRedirection.adml
deleted file mode 100644
index 7a9a0d7..0000000
--- a/policy_templates/en-US/FolderRedirection.adml
+++ /dev/null
@@ -1,80 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Folder Redirection
- Use localized subfolder names when redirecting Start Menu and My Documents
- This policy setting allows the administrator to define whether Folder Redirection should use localized names for the All Programs, Startup, My Music, My Pictures, and My Videos subfolders when redirecting the parent Start Menu and legacy My Documents folder respectively.
-
-If you enable this policy setting, Windows Vista, Windows 7, Windows 8, and Windows Server 2012 will use localized folder names for these subfolders when redirecting the Start Menu or legacy My Documents folder.
-
-If you disable or not configure this policy setting, Windows Vista, Windows 7, Windows 8, and Windows Server 2012 will use the standard English names for these subfolders when redirecting the Start Menu or legacy My Documents folder.
-
-Note: This policy is valid only on Windows Vista, Windows 7, Windows 8, and Windows Server 2012 when it processes a legacy redirection policy already deployed for these folders in your existing localized environment.
-
- Do not automatically make specific redirected folders available offline
- This policy setting allows you to control whether individual redirected shell folders are available offline by default.
-
-For the folders affected by this setting, users must manually select the files they wish to make available offline.
-
-If you disable or do not configure this policy setting, all redirected shell folders are automatically made available offline. All subfolders within the redirected folders are also made available offline.
-
-Note: This policy setting does not prevent files from being automatically cached if the network share is configured for "Automatic Caching", nor does it affect the availability of the "Always available offline" menu option in the user interface.
-
-Note: The configuration of this policy for any folder will override the configured value of "Do not automatically make all redirected folders available offline".
-
- Do not automatically make all redirected folders available offline
- This policy setting allows you to control whether all redirected shell folders, such as Contacts, Documents, Desktop, Favorites, Music, Pictures, Videos, Start Menu, and AppData\Roaming, are available offline by default.
-
-If you enable this policy setting, users must manually select the files they wish to make available offline.
-
-If you disable or do not configure this policy setting, redirected shell folders are automatically made available offline. All subfolders within the redirected folders are also made available offline.
-
-Note: This policy setting does not prevent files from being automatically cached if the network share is configured for "Automatic Caching", nor does it affect the availability of the "Always available offline" menu option in the user interface.
-
-Note: Do not enable this policy setting if users will need access to their redirected files if the network or server holding the redirected files becomes unavailable.
-
-Note: If one or more valid folder GUIDs are specified in the policy setting "Do not automatically make specific redirected folders available offline", that setting will override the configured value of "Do not automatically make all redirected folders available offline".
-
- Enable optimized move of contents in Offline Files cache on Folder Redirection server path change
- This policy setting controls whether the contents of redirected folders is copied from the old location to the new location or simply renamed in the Offline Files cache when a folder is redirected to a new location.
-
-If you enable this policy setting, when the path to a redirected folder is changed from one network location to another and Folder Redirection is configured to move the content to the new location, instead of copying the content to the new location, the cached content is renamed in the local cache and not copied to the new location. To use this policy setting, you must move or restore the server content to the new network location using a method that preserves the state of the files, including their timestamps, before updating the Folder Redirection location.
-
-If you disable or do not configure this policy setting, when the path to a redirected folder is changed and Folder Redirection is configured to move the content to the new location, Windows copies the contents of the local cache to the new network location, then deleted the content from the old network location.
-
- Redirect folders on primary computers only
- This policy setting controls whether folders are redirected on a user's primary computers only. This policy setting is useful to improve logon performance and to increase security for user data on computers where the user might not want to download private data, such as on a meeting room computer or on a computer in a remote office.
-
-To designate a user's primary computers, an administrator must use management software or a script to add primary computer attributes to the user's account in Active Directory Domain Services (AD DS). This policy setting also requires the Windows Server 2012 version of the Active Directory schema to function.
-
-If you enable this policy setting and the user has redirected folders, such as the Documents and Pictures folders, the folders are redirected on the user's primary computer only.
-
-If you disable or do not configure this policy setting and the user has redirected folders, the folders are redirected on every computer that the user logs on to.
-
-Note: If you enable this policy setting in Computer Configuration and User Configuration, the Computer Configuration policy setting takes precedence.
-
-
-
-
- Set the checkbox for any redirected shell folder that should not automatically be made available offline.
- AppData(Roaming)
- Desktop
- Start Menu
- Documents
- Pictures
- Music
- Videos
- Favorites
- Contacts
- Downloads
- Links
- Searches
- Saved Games
-
-
-
-
diff --git a/policy_templates/en-US/FramePanes.adml b/policy_templates/en-US/FramePanes.adml
deleted file mode 100644
index 8be422d..0000000
--- a/policy_templates/en-US/FramePanes.adml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Explorer Frame Pane
- Turn on or off details pane
- Always show
- Always hide
- This policy setting shows or hides the Details Pane in File Explorer.
-
-If you enable this policy setting and configure it to hide the pane, the Details Pane in File Explorer is hidden and cannot be turned on by the user.
-
-If you enable this policy setting and configure it to show the pane, the Details Pane is always visible and cannot be hidden by the user. Note: This has a side effect of not being able to toggle to the Preview Pane since the two cannot be displayed at the same time.
-
-If you disable, or do not configure this policy setting, the Details Pane is hidden by default and can be displayed by the user. This is the default policy setting.
-
- Turn off Preview Pane
- Hides the Preview Pane in File Explorer.
-
-If you enable this policy setting, the Preview Pane in File Explorer is hidden and cannot be turned on by the user.
-
-If you disable, or do not configure this setting, the Preview Pane is hidden by default and can be displayed by the user.
-
-
-
-
- Configure details pane
-
-
-
-
diff --git a/policy_templates/en-US/GameDVR.adml b/policy_templates/en-US/GameDVR.adml
deleted file mode 100644
index 6d75581..0000000
--- a/policy_templates/en-US/GameDVR.adml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
- Windows Game Recording and Broadcasting
- Manages the Windows Game Recording and Broadcasting states
-
-
- Windows Game Recording and Broadcasting
- Manages the Windows Game Recording and Broadcasting states
- Enables or disables Windows Game Recording and Broadcasting
- Windows 10
-
- Windows Game Recording and Broadcasting.
-
-This setting enables or disables the Windows Game Recording and Broadcasting features. If you disable this setting, Windows Game Recording will not be allowed.
-If the setting is enabled or not configured, then Recording and Broadcasting (streaming) will be allowed.
-
-
-
-
diff --git a/policy_templates/en-US/Globalization.adml b/policy_templates/en-US/Globalization.adml
deleted file mode 100644
index cde6553..0000000
--- a/policy_templates/en-US/Globalization.adml
+++ /dev/null
@@ -1,330 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Disallow selection of Custom Locales
- This policy setting prevents a user from selecting a supplemental custom locale as their user locale. The user is restricted to the set of locales that are installed with the operating system.
-
-This does not affect the selection of replacement locales. To prevent the selection of replacement locales, adjust the permissions of the %windir%\Globalization directory to prevent the installation of locales by unauthorized users.
-
-The policy setting "Restrict user locales" can also be enabled to disallow selection of a custom locale, even if this policy setting is not configured.
-
-If you enable this policy setting, the user cannot select a custom locale as their user locale, but they can still select a replacement locale if one is installed.
-
-If you disable or do not configure this policy setting, the user can select a custom locale as their user locale.
-
-If this policy setting is enabled at the machine level, it cannot be disabled by a per-user policy setting. If this policy setting is disabled at the machine level, the per-user policy setting will be ignored. If this policy setting is not configured at the machine level, restrictions will be based on per-user policy settings.
-
-To set this policy setting on a per-user basis, make sure that you do not configure the per-machine policy setting.
-
-
- Hide Regional and Language Options administrative options
- This policy setting removes the Administrative options from the Region settings control panel. Administrative options include interfaces for setting system locale and copying settings to the default user. This policy setting does not, however, prevent an administrator or another application from changing these values programmatically.
-
-This policy setting is used only to simplify the Regional Options control panel.
-
-If you enable this policy setting, the user cannot see the Administrative options.
-
-If you disable or do not configure this policy setting, the user can see the Administrative options.
-
-Note: Even if a user can see the Administrative options, other policies may prevent them from modifying the values.
- Hide the geographic location option
- This policy setting removes the option to change the user's geographical location (GeoID) from the Region settings control panel.
-
-This policy setting is used only to simplify the Regional Options control panel.
-
-If you enable this policy setting, the user does not see the option to change the GeoID. This does not prevent the user or an application from changing the GeoID programmatically.
-
-If you disable or do not configure this policy setting, the user sees the option for changing the user location (GeoID).
-
-Note: Even if a user can see the GeoID option, the "Disallow changing of geographical location" option can prevent them from actually changing their current geographical location.
- Hide the select language group options
- This policy setting removes the option to change the user's menus and dialogs (UI) language from the Language and Regional Options control panel.
-
-This policy setting is used only to simplify the Regional Options control panel.
-
-If you enable this policy setting, the user does not see the option for changing the UI language. This does not prevent the user or an application from changing the UI language programmatically.
-
-If you disable or do not configure this policy setting, the user sees the option for changing the UI language.
-
-Note: Even if a user can see the option to change the UI language, other policy settings can prevent them from changing their UI language.
- Hide user locale selection and customization options
- This policy setting removes the regional formats interface from the Region settings control panel.
-
-This policy setting is used only to simplify the Regional and Language Options control panel.
-
-If you enable this policy setting, the user does not see the regional formats options. This does not prevent the user or an application from changing their user locale or user overrides programmatically.
-
-If you disable or do not configure this policy setting, the user sees the regional formats options for changing and customizing the user locale.
- Restrict system locales
- This policy setting restricts the permitted system locales to the specified list. If the list is empty, it locks the system locale to its current value. This policy setting does not change the existing system locale; however, the next time that an administrator attempts to change the computer's system locale, they will be restricted to the specified list.
-
-The locale list is specified using language names, separated by a semicolon (;). For example, en-US is English (United States). Specifying "en-US;en-CA" would restrict the system locale to English (United States) and English (Canada).
-
-If you enable this policy setting, administrators can select a system locale only from the specified system locale list.
-
-If you disable or do not configure this policy setting, administrators can select any system locale shipped with the operating system.
- Restrict user locales
- This policy setting restricts users on a computer to the specified list of user locales. If the list is empty, it locks all user locales to their current values. This policy setting does not change existing user locale settings; however, the next time a user attempts to change their user locale, their choices will be restricted to locales in this list.
-
-To set this policy setting on a per-user basis, make sure that you do not configure the per-computer policy setting.
-
-The locale list is specified using language tags, separated by a semicolon (;). For example, en-US is English (United States). Specifying "en-CA;fr-CA" would restrict the user locale to English (Canada) and French (Canada).
-
-If you enable this policy setting, only locales in the specified locale list can be selected by users.
-
-If you disable or do not configure this policy setting, users can select any locale installed on the computer, unless restricted by the "Disallow selection of Custom Locales" policy setting.
-
-If this policy setting is enabled at the computer level, it cannot be disabled by a per-user policy. If this policy setting is disabled at the computer level, the per-user policy is ignored. If this policy setting is not configured at the computer level, restrictions are based on per-user policies.
-
- Restricts the UI language Windows uses for all logged users
- This policy setting restricts the Windows UI language for all users.
-
-This is a policy setting for computers with more than one UI language installed.
-
-If you enable this policy setting, the UI language of Windows menus and dialogs for systems with more than one language will follow the language specified by the administrator as the system UI languages. The UI language selected by the user will be ignored if it is different than any of the system UI languages.
-
-If you disable or do not configure this policy setting, the user can specify which UI language is used.
- Restricts the UI languages Windows should use for the selected user
- This policy setting restricts the Windows UI language for specific users.
-
-This policy setting applies to computers with more than one UI language installed.
-
-If you enable this policy setting, the UI language of Windows menus and dialogs for systems with more than one language is restricted to a specified language for the selected user. If the specified language is not installed on the target computer or you disable this policy setting, the language selection defaults to the language selected by the user.
-
-If you disable or do not configure this policy setting, there is no restriction on which language users should use.
-
-To enable this policy setting in Windows Server 2003, Windows XP, or Windows 2000, to use the "Restrict selection of Windows menus and dialogs language" policy setting.
- Force selected system UI language to overwrite the user UI language
- This policy setting controls which UI language is used for computers with more than one UI language installed.
-
-If you enable this policy setting, the UI language of Windows menus and dialogs for systems with more than one language is restricted to a specified language. If the specified language is not installed on the target computer or you disable this policy setting, the language selection defaults to the language selected by the local administrator.
-
-If you disable or do not configure this policy setting, there is no restriction of a specific language used for the Windows menus and dialogs.
- Locale Services
- Disallow changing of geographic location
- This policy setting prevents users from changing their user geographical location (GeoID).
-
-If you enable this policy setting, users cannot change their GeoID.
-
-If you disable or do not configure this policy setting, users may select any GeoID.
-
-If you enable this policy setting at the computer level, it cannot be disabled by a per-user policy setting. If you disable this policy setting at the computer level, the per-user policy is ignored. If you do not configure this policy setting at the computer level, restrictions are based on per-user policy settings.
-
-To set this policy setting on a per-user basis, make sure that the per-computer policy setting is not configured.
- Disallow user override of locale settings
- This policy setting prevents the user from customizing their locale by changing their user overrides.
-
-Any existing overrides in place when this policy is enabled will be frozen. To remove existing user overrides, first reset the user(s) values to the defaults and then apply this policy.
-
-When this policy setting is enabled, users can still choose alternate locales installed on the system unless prevented by other policies, however, they will be unable to customize those choices. The user cannot customize their user locale with user overrides.
-
-If this policy setting is disabled or not configured, then the user can customize their user locale overrides.
-
-If this policy is set to Enabled at the computer level, then it cannot be disabled by a per-User policy. If this policy is set to Disabled at the computer level, then the per-User policy will be ignored. If this policy is set to Not Configured at the computer level, then restrictions will be based on per-User policies.
-
-To set this policy on a per-user basis, make sure that the per-computer policy is set to Not Configured.
- Regional and Language Options
- Restrict selection of Windows menus and dialogs language
- This policy setting restricts users to the specified language by disabling the menus and dialog box controls in the Region settings control panel. If the specified language is not installed on the target computer, the language selection defaults to English.
-
-If you enable this policy setting, the dialog box controls in the Regional and Language Options control panel are not accessible to the logged on user. This prevents users from specifying a language different than the one used.
-
-To enable this policy setting in Windows Vista, use the "Restricts the UI languages Windows should use for the selected user" policy setting.
-
-If you disable or do not configure this policy setting, the logged-on user can access the dialog box controls in the Regional and Language Options control panel to select any available UI language.
- English
- Swedish
- Dutch
- Portuguese (Brazil)
- Finnish
- Norwegian
- Danish
- Hungarian
- Polish
- Russian
- Czech
- Japanese
- Greek
- Portuguese (Portugal)
- Turkish
- Arabic
- Hebrew
- Slovak
- Slovenian
- Romanian
- Croatian
- Bulgarian
- Korean
- Estonian
- Lithuanian
- Latvian
- Thai
- German
- Simplified Chinese
- Traditional Chinese
- Traditional Chinese (Hong Kong)
- Traditional Chinese (Taiwan)
- French
- Spanish
- Italian
- Serbian (Latin)
- Ukrainian
- Century interpretation for Year 2000
- This policy setting determines how programs interpret two-digit years.
-
-This policy setting affects only the programs that use this Windows feature to interpret two-digit years. If a program does not interpret two-digit years correctly, consult the documentation or manufacturer of the program.
-
-If you enable this policy setting, the system specifies the largest two-digit year interpreted as being preceded by 20. All numbers less than or equal to the specified value are interpreted as being preceded by 20. All numbers greater than the specified value are interpreted as being preceded by 19.
-
-For example, the default value, 2029, specifies that all two-digit years less than or equal to 29 (00 to 29) are interpreted as being preceded by 20, that is 2000 to 2029. Conversely, all two-digit years greater than 29 (30 to 99) are interpreted as being preceded by 19, that is, 1930 to 1999.
-
-If you disable or do not configure this policy setting, Windows does not interpret two-digit year formats using this scheme for the program.
- Turn off offer text predictions as I type
-
- This policy turns off the offer text predictions as I type option. This does not, however, prevent the user or an application from changing the setting programmatically.
-
- The offer text predictions as I type option controls whether or not text prediction suggestions will be presented to the user on the on-screen keyboard.
-
- If the policy is Enabled, then the option will be locked to not offer text predictions.
-
- If the policy is Disabled or Not Configured, then the user will be free to change the setting according to their preference.
-
- Note that the availability and function of this setting is dependent on supported languages being enabled.
- Turn off insert a space after selecting a text prediction
-
- This policy turns off the insert a space after selecting a text prediction option. This does not, however, prevent the user or an application from changing the setting programmatically.
-
- The insert a space after selecting a text prediction option controls whether or not a space will be inserted after the user selects a text prediction candidate when using the on-screen keyboard.
-
- If the policy is Enabled, then the option will be locked to not insert a space after selecting a text prediction.
-
- If the policy is Disabled or Not Configured, then the user will be free to change the setting according to their preference.
-
- Note that the availability and function of this setting is dependent on supported languages being enabled.
- Turn off autocorrect misspelled words
-
- This policy turns off the autocorrect misspelled words option. This does not, however, prevent the user or an application from changing the setting programmatically.
-
- The autocorrect misspelled words option controls whether or not errors in typed text will be automatically corrected.
-
- If the policy is Enabled, then the option will be locked to not autocorrect misspelled words.
-
- If the policy is Disabled or Not Configured, then the user will be free to change the setting according to their preference.
-
- Note that the availability and function of this setting is dependent on supported languages being enabled.
- Turn off highlight misspelled words
-
- This policy turns off the highlight misspelled words option. This does not, however, prevent the user or an application from changing the setting programmatically.
-
- The highlight misspelled words option controls whether or next spelling errors in typed text will be highlighted.
-
- If the policy is Enabled, then the option will be locked to not highlight misspelled words.
-
- If the policy is Disabled or Not Configured, then the user will be free to change the setting according to their preference.
-
- Note that the availability and function of this setting is dependent on supported languages being enabled.
- Turn off automatic learning
-
- This policy setting turns off the automatic learning component of handwriting recognition personalization.
-
- Automatic learning enables the collection and storage of text and ink written by the user in order to help adapt handwriting recognition to the vocabulary and handwriting style of the user.
-
- Text that is collected includes all outgoing messages in Windows Mail, and MAPI enabled email clients, as well as URLs from the Internet Explorer browser history. The information that is stored includes word frequency and new words not already known to the handwriting recognition engines (for example, proper names and acronyms). Deleting email content or the browser history does not delete the stored personalization data. Ink entered through Input Panel is collected and stored.
-
- Note: Automatic learning of both text and ink might not be available for all languages, even when handwriting personalization is available. See Tablet PC Help for more information.
-
- If you enable this policy setting, automatic learning stops and any stored data is deleted. Users cannot configure this setting in Control Panel.
-
- If you disable this policy setting, automatic learning is turned on. Users cannot configure this policy setting in Control Panel. Collected data is only used for handwriting recognition, if handwriting personalization is turned on.
-
- If you do not configure this policy, users can choose to enable or disable automatic learning either from the Handwriting tab in the Tablet Settings in Control Panel or from the opt-in dialog.
-
- This policy setting is related to the "Turn off handwriting personalization" policy setting.
-
- Note: The amount of stored ink is limited to 50 MB and the amount of text information to approximately 5 MB. When these limits are reached and new data is collected, old data is deleted to make room for more recent data.
-
- Note: Handwriting personalization works only for Microsoft handwriting recognizers, and not with third-party recognizers.
- Handwriting personalization
- Disallow copying of user input methods to the system account for sign-in
-
- This policy prevents automatic copying of user input methods to the system account for use on the sign-in screen. The user is restricted to the set of input methods that are enabled in the system account.
-
- Note this does not affect the availability of user input methods on the lock screen or with the UAC prompt.
-
- If the policy is Enabled, then the user will get input methods enabled for the system account on the sign-in page.
-
- If the policy is Disabled or Not Configured, then the user will be able to use input methods enabled for their user account on the sign-in page.
- Block clean-up of unused language packs
-
- This policy setting controls whether the LPRemove task will run to clean up language packs installed on a machine but are not used by any users on that machine.
-
- If you enable this policy setting, language packs that are installed as part of the system image will remain installed even if they are not used by any user on that system.
-
- If you disable or do not configure this policy setting, language packs that are installed as part of the system image but are not used by any user on that system will be removed as part of a scheduled clean up task.
-
- Allow users to enable online speech recognition services
-
- This policy specifies whether users on the device have the option to enable online speech recognition services.
-
- If this policy is enabled or not configured, control is deferred to users, and users may choose whether to enable speech services via settings.
-
- If this policy is disabled, speech services will be disabled, and users cannot enable speech services via settings.
-
- Restrict Language Pack and Language Feature Installation
-
- This policy setting restricts all users from installing language packs and language features on demand packages. This policy does not restrict switching the Windows language, if you want to restrict the Windows language use the following policy: "Restricts the UI languages Windows uses for all logged users."
-
- If you enable this policy setting, the installation of language packs and language features is prevented for all users.
-
- If you disable or do not configure this policy setting, there is no language packs or feature installation restriction for any user.
-
-
- This policy setting restricts the user from installing language packs and language features on demand. This policy does not restrict switching the Windows language, if you want to restrict the Windows language use the following policy: "Restricts the UI languages Windows should use for the selected user."
-
- If you enable this policy setting, the installation of language packs and language features is prevented for the user.
-
- If you disable or do not configure this policy setting, there is no language packs or language features installation restriction for the user.
-
-
-
-
- These systems are restricted to the following locale(s)
- The expected form is en-US;fr-FR
-
-
-
-
-
- The user is restricted to using the following locale(s)
- The expected form is en-US;fr-FR
-
-
-
-
-
- The user is restricted to using the following locale(s)
- The expected form is en-US;fr-FR
-
-
-
-
-
- Restrict users to the following language:
-
-
- Restrict users to the following language:
-
-
- Restrict users to the following language:
-
-
- Specify the maximum year for which two-digit years are interpreted as being 21st century:
- Year
-
-
-
-
diff --git a/policy_templates/en-US/GroupPolicy.adml b/policy_templates/en-US/GroupPolicy.adml
deleted file mode 100644
index cd6281d..0000000
--- a/policy_templates/en-US/GroupPolicy.adml
+++ /dev/null
@@ -1,670 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Mitigation Options
- Untrusted Font Blocking
- This security feature provides a global setting to prevent programs from loading untrusted fonts. Untrusted fonts are any font installed outside of the %windir%\Fonts directory. This feature can be configured to be in 3 modes: On, Off, and Audit. By default, it is Off and no fonts are blocked. If you aren't quite ready to deploy this feature into your organization, you can run it in Audit mode to see if blocking untrusted fonts causes any usability or compatibility issues.
- Block untrusted fonts and log events
- Do not block untrusted fonts
- Log events without blocking untrusted fonts
-
- Process Mitigation Options
-
- This security feature provides a means to override individual process MitigationOptions settings. This can be used to enforce a number of security policies specific to applications. The application name is specified as the Value name, including extension. The Value is specified as a bit field with a series of flags in particular positions. Bits can be set to either 0 (setting is forced off), 1 (setting is forced on), or ? (setting retains its existing value prior to GPO evaluation). The recognized bit locations are:
-
- PROCESS_CREATION_MITIGATION_POLICY_DEP_ENABLE (0x00000001)
- Enables data execution prevention (DEP) for the child process
-
- PROCESS_CREATION_MITIGATION_POLICY_DEP_ATL_THUNK_ENABLE (0x00000002)
- Enables DEP-ATL thunk emulation for the child process. DEP-ATL thunk emulation causes the system to intercept NX faults that originate from the Active Template Library (ATL) thunk layer.
-
- PROCESS_CREATION_MITIGATION_POLICY_SEHOP_ENABLE (0x00000004)
- Enables structured exception handler overwrite protection (SEHOP) for the child process. SEHOP blocks exploits that use the structured exception handler (SEH) overwrite technique.
-
- PROCESS_CREATION_MITIGATION_POLICY_FORCE_RELOCATE_IMAGES_ALWAYS_ON (0x00000100)
- The force Address Space Layout Randomization (ASLR) policy forcibly rebases images that are not dynamic base compatible by acting as though an image base collision happened at load time. If relocations are required, images that do not have a base relocation section will not be loaded.
-
- PROCESS_CREATION_MITIGATION_POLICY_BOTTOM_UP_ASLR_ALWAYS_ON (0x00010000)
- PROCESS_CREATION_MITIGATION_POLICY_BOTTOM_UP_ASLR_ALWAYS_OFF (0x00020000)
- The bottom-up randomization policy, which includes stack randomization options, causes a random location to be used as the lowest user address.
-
- For instance, to enable PROCESS_CREATION_MITIGATION_POLICY_DEP_ENABLE and PROCESS_CREATION_MITIGATION_POLICY_FORCE_RELOCATE_IMAGES_ALWAYS_ON, disable PROCESS_CREATION_MITIGATION_POLICY_BOTTOM_UP_ASLR_ALWAYS_OFF, and to leave all other options at their default values, specify a value of:
- ???????????????0???????1???????1
-
- Setting flags not specified here to any value other than ? results in undefined behavior.
-
-
- Enable AD/DFS domain controller synchronization during policy refresh
- Enabling this setting will cause the Group Policy Client to connect to the same domain controller for DFS shares as is being used for Active Directory.
-
-
- Turn off Group Policy Client Service AOAC optimization
- This policy setting prevents the Group Policy Client Service from stopping when idle.
-
-
- Continue experiences on this device
-
-This policy setting determines whether the Windows device is allowed to participate in cross-device experiences (continue experiences).
-
-If you enable this policy setting, the Windows device is discoverable by other Windows devices that belong to the same user, and can participate in cross-device experiences.
-
-If you disable this policy setting, the Windows device is not discoverable by other devices, and cannot participate in cross-device experiences.
-
-If you do not configure this policy setting, the default behavior depends on the Windows edition. Changes to this policy take effect on reboot.
-
- Phone-PC linking on this device
-
-This policy allows IT admins to turn off the ability to Link a Phone with a PC to continue reading, emailing and other tasks that requires linking between Phone and PC.
-
-If you enable this policy setting, the Windows device will be able to enroll in Phone-PC linking functionality and participate in Continue on PC experiences.
-
-If you disable this policy setting, the Windows device is not allowed to be linked to Phones, will remove itself from the device list of any linked Phones, and cannot participate in Continue on PC experiences.
-
-If you do not configure this policy setting, the default behavior depends on the Windows edition. Changes to this policy take effect on reboot.
-
- Configure web-to-app linking with app URI handlers
-
-This policy setting determines whether Windows supports web-to-app linking with app URI handlers.
-
-Enabling this policy setting enables web-to-app linking so that apps can be launched with a http(s) URI.
-
-Disabling this policy disables web-to-app linking and http(s) URIs will be opened in the default browser instead of launching the associated app.
-
-If you do not configure this policy setting, the default behavior depends on the Windows edition. Changes to this policy take effect on reboot.
-
- Fonts
- Enable Font Providers
-
- This policy setting determines whether Windows is allowed to download fonts and font catalog data from an online font provider.
-
- If you enable this policy setting, Windows periodically queries an online font provider to determine whether a new font catalog is available. Windows may also download font data if needed to format or render text.
-
- If you disable this policy setting, Windows does not connect to an online font provider and only enumerates locally-installed fonts.
-
- If you do not configure this policy setting, the default behavior depends on the Windows edition. Changes to this policy take effect on reboot.
-
- Configure Group Policy Caching
-
- This policy setting allows you to configure Group Policy caching behavior.
-
- If you enable or do not configure this policy setting, Group Policy caches policy information after every background processing session. This cache saves applicable GPOs and the settings contained within them. When Group Policy runs in synchronous foreground mode, it refers to this cache, which enables it to run faster. When the cache is read, Group Policy attempts to contact a logon domain controller to determine the link speed. When Group Policy runs in background mode or asynchronous foreground mode, it continues to download the latest version of the policy information, and it uses a bandwidth estimate to determine slow link thresholds. (See the “Configure Group Policy Slow Link Detection” policy setting to configure asynchronous foreground behavior.)
-
- The slow link value that is defined in this policy setting determines how long Group Policy will wait for a response from the domain controller before reporting the link speed as slow. The default is 500 milliseconds.
-
- The timeout value that is defined in this policy setting determines how long Group Policy will wait for a response from the domain controller before determining that there is no network connectivity. This stops the current Group Policy processing. Group Policy will run in the background the next time a connection to a domain controller is established. Setting this value too high might result in longer waits for the user at boot or logon. The default is 5000 milliseconds.
-
- If you disable this policy setting, the Group Policy client will not cache applicable GPOs or settings that are contained within the GPOs. When Group Policy runs synchronously, it downloads the latest version of the policy from the network and uses bandwidth estimates to determine slow link thresholds. (See the “Configure Group Policy Slow Link Detection” policy setting to configure asynchronous foreground behavior.)
-
-
- Enable Group Policy Caching for Servers
-
- This policy setting allows you to configure Group Policy caching behavior on Windows Server machines.
- If you enable this policy setting, Group Policy caches policy information after every background processing session. This cache saves applicable GPOs and the settings contained within them. When Group Policy runs in synchronous foreground mode, it refers to this cache, which enables it to run faster. When the cache is read, Group Policy attempts to contact a logon domain controller to determine the link speed. When Group Policy runs in background mode or asynchronous foreground mode, it continues to download the latest version of the policy information, and it uses a bandwidth estimate to determine slow link thresholds. (See the “Configure Group Policy Slow Link Detection” policy setting to configure asynchronous foreground behavior.)
- The slow link value that is defined in this policy setting determines how long Group Policy will wait for a response from the domain controller before reporting the link speed as slow. The default is 500 milliseconds.
- The timeout value that is defined in this policy setting determines how long Group Policy will wait for a response from the domain controller before determining that there is no network connectivity. This stops the current Group Policy processing. Group Policy will run in the background the next time a connection to a domain controller is established. Setting this value too high might result in longer waits for the user at boot or logon. The default is 5000 milliseconds.
- If you disable or do not configure this policy setting, the Group Policy client will not cache applicable GPOs or settings that are contained within the GPOs. When Group Policy runs synchronously, it downloads the latest version of the policy from the network and uses bandwidth estimates to determine slow link thresholds. (See the “Configure Group Policy Slow Link Detection” policy setting to configure asynchronous foreground behavior.)
-
-
- Configure Logon Script Delay
-
- Enter “0” to disable Logon Script Delay.
-
- This policy setting allows you to configure how long the Group Policy client waits after logon before running scripts.
-
- By default, the Group Policy client waits five minutes before running logon scripts. This helps create a responsive desktop environment by preventing disk contention.
-
- If you enable this policy setting, Group Policy will wait for the specified amount of time before running logon scripts.
-
- If you disable this policy setting, Group Policy will run scripts immediately after logon.
-
- If you do not configure this policy setting, Group Policy will wait five minutes before running logon scripts.
-
-
- Configure Direct Access connections as a fast network connection
- This policy setting allows an administrator to define the Direct Access connection to be considered a fast network connection for the purposes of applying and updating Group Policy.
-
-When Group Policy detects the bandwidth speed of a Direct Access connection, the detection can sometimes fail to provide any bandwidth speed information. If Group Policy detects a bandwidth speed, Group Policy will follow the normal rules for evaluating if the Direct Access connection is a fast or slow network connection. If no bandwidth speed is detected, Group Policy will default to a slow network connection. This policy setting allows the administrator the option to override the default to slow network connection and instead default to using a fast network connection in the case that no network bandwidth speed is determined.
-
-Note: When Group Policy detects a slow network connection, Group Policy will only process those client side extensions configured for processing across a slow link (slow network connection).
-
-If you enable this policy, when Group Policy cannot determine the bandwidth speed across Direct Access, Group Policy will evaluate the network connection as a fast link and process all client side extensions.
-
-If you disable this setting or do not configure it, Group Policy will evaluate the network connection as a slow link and process only those client side extensions configured to process over a slow link.
-
-
- Change Group Policy processing to run asynchronously when a slow network connection is detected.
- This policy directs Group Policy processing to skip processing any client side extension that requires synchronous processing (that is, whether computers wait for the network to be fully initialized during computer startup and user logon) when a slow network connection is detected.
-
-If you enable this policy setting, when a slow network connection is detected, Group Policy processing will always run in an asynchronous manner.
-Client computers will not wait for the network to be fully initialized at startup and logon. Existing users will be logged on using cached credentials,
-which will result in shorter logon times. Group Policy will be applied in the background after the network becomes available.
-Note that because this is a background refresh, extensions requiring synchronous processing such as Software Installation, Folder Redirection
-and Drive Maps preference extension will not be applied.
-
-Note: There are two conditions that will cause Group Policy to be processed synchronously even if this policy setting is enabled:
-1 - At the first computer startup after the client computer has joined the domain.
-2 - If the policy setting "Always wait for the network at computer startup and logon" is enabled.
-
-If you disable or do not configure this policy setting, detecting a slow network connection will not affect whether Group Policy processing will be synchronous or asynchronous.
-
-
- Turn off Local Group Policy Objects processing
- This policy setting prevents Local Group Policy Objects (Local GPOs) from being applied.
-
-By default, the policy settings in Local GPOs are applied before any domain-based GPO policy settings. These policy settings can apply to both users and the local computer. You can disable the processing and application of all Local GPOs to ensure that only domain-based GPOs are applied.
-
-If you enable this policy setting, the system does not process and apply any Local GPOs.
-
-If you disable or do not configure this policy setting, Local GPOs continue to be applied.
-
-Note: For computers joined to a domain, it is strongly recommended that you only configure this policy setting in domain-based GPOs. This policy setting will be ignored on computers that are joined to a workgroup.
-
- Specify startup policy processing wait time
- This policy setting specifies how long Group Policy should wait for network availability notifications during startup policy processing. If the startup policy processing is synchronous, the computer is blocked until the network is available or the default wait time is reached. If the startup policy processing is asynchronous, the computer is not blocked and policy processing will occur in the background. In either case, configuring this policy setting overrides any system-computed wait times.
-
-If you enable this policy setting, Group Policy will use this administratively configured maximum wait time and override any default or system-computed wait time.
-
-If you disable or do not configure this policy setting, Group Policy will use the default wait time of 30 seconds on computers running Windows Vista operating system.
-
-
- Allow cross-forest user policy and roaming user profiles
- This policy setting allows user-based policy processing, roaming user profiles, and user object logon scripts for interactive logons across forests.
-
-This policy setting affects all user accounts that interactively log on to a computer in a different forest when a trust across forests or a two-way forest trust exists.
-
-If you do not configure this policy setting:
-- No user-based policy settings are applied from the user's forest.
-- Users do not receive their roaming profiles; they receive a local profile on the computer from the local forest. A warning message appears to the user, and an event log message (1529) is posted.
-- Loopback Group Policy processing is applied, using the Group Policy Objects (GPOs) that are scoped to the computer.
-- An event log message (1109) is posted, stating that loopback was invoked in Replace mode.
-
-If you enable this policy setting, the behavior is exactly the same as in Windows 2000: user policy is applied, and a roaming user profile is allowed from the trusted forest.
-
-If you disable this policy setting, the behavior is the same as if it is not configured.
- Configure software Installation policy processing
- This policy setting determines when software installation policies are updated.
-
-This policy setting affects all policy settings that use the software installation component of Group Policy, such as policy settings in Software Settings\Software Installation. You can set software installation policy only for Group Policy Objects stored in Active Directory, not for Group Policy Objects on the local computer.
-
-This policy setting overrides customized settings that the program implementing the software installation policy set when it was installed.
-
-If you enable this policy setting, you can use the check boxes provided to change the options. If you disable or do not configure this policy setting, it has no effect on the system.
-
-The "Allow processing across a slow network connection" option updates the policies even when the update is being transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy setting implementations specify that they are updated only when changed. However, you might want to update unchanged policy settings, such as reapplying a desired policies in case a user has changed it.
- Configure disk quota policy processing
- This policy setting determines when disk quota policies are updated.
-
-This policy setting affects all policies that use the disk quota component of Group Policy, such as those in Computer Configuration\Administrative Templates\System\Disk Quotas.
-
-This policy setting overrides customized settings that the program implementing the disk quota policy set when it was installed.
-
-If you enable this policy setting, you can use the check boxes provided to change the options. If you disable or do not configure this policy setting, it has no effect on the system.
-
-The "Allow processing across a slow network connection" option updates the policies even when the update is being transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired setting in case a user has changed it.
- Configure EFS recovery policy processing
- This policy setting determines when encryption policies are updated.
-
-This policy setting affects all policies that use the encryption component of Group Policy, such as policies related to encryption in Windows Settings\Security Settings.
-
-It overrides customized settings that the program implementing the encryption policy set when it was installed.
-
-If you enable this policy setting, you can use the check boxes provided to change the options. If you disable or do not configure this policy setting, it has no effect on the system.
-
-The "Allow processing across a slow network connection" option updates the policies even when the update is being transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired setting in case a user has changed it.
- Configure folder redirection policy processing
- This policy setting determines when folder redirection policies are updated.
-
-This policy setting affects all policies that use the folder redirection component of Group Policy, such as those in WindowsSettings\Folder Redirection. You can only set folder redirection policy for Group Policy objects, stored in Active Directory, not for Group Policy objects on the local computer.
-
-This policy setting overrides customized settings that the program implementing the folder redirection policy setting set when it was installed.
-
-If you enable this policy setting, you can use the check boxes provided to change the options. If you disable or do not configure this policy setting, it has no effect on the system.
-
-The "Allow processing across a slow network connection" option updates the policies even when the update is being transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired setting in case a user has changed it.
- Configure Internet Explorer Maintenance policy processing
- This policy setting determines when Internet Explorer Maintenance policies are updated.
-
-This policy setting affects all policies that use the Internet Explorer Maintenance component of Group Policy, such as those in Windows Settings\Internet Explorer Maintenance.
-
-This policy setting overrides customized settings that the program implementing the Internet Explorer Maintenance policy set when it was installed.
-
-If you enable this policy setting, you can use the check boxes provided to change the options. If you disable or do not configure this policy setting, it has no effect on the system.
-
-The "Allow processing across a slow network connection" option updates the policies even when the update is being transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired policy setting in case a user has changed it.
- Configure IP security policy processing
- This policy setting determines when IP security policies are updated.
-
-This policy setting affects all policies that use the IP security component of Group Policy, such as policies in Computer Configuration\Windows Settings\Security Settings\IP Security Policies on Local Machine.
-
-This policy setting overrides customized settings that the program implementing the IP security policy set when it was installed.
-
-If you enable this policy setting, you can use the check boxes provided to change the options. If you disable or do not configure this policy setting, it has no effect on the system.
-
-The "Allow processing across a slow network connection" option updates the policies even when the update is being transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired policy setting in case a user has changed it.
- Configure registry policy processing
- This policy setting determines when registry policies are updated.
-
-This policy setting affects all policies in the Administrative Templates folder and any other policies that store values in the registry. It overrides customized settings that the program implementing a registry policy set when it was installed.
-
-If you enable this policy setting, you can use the check boxes provided to change the options. If you disable or do not configure this policy setting, it has no effect on the system.
-
-The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired policy setting in case a user has changed it.
- Configure scripts policy processing
- This policy setting determines when policies that assign shared scripts are updated.
-
-This policy setting affects all policies that use the scripts component of Group Policy, such as those in WindowsSettings\Scripts. It overrides customized settings that the program implementing the scripts policy set when it was installed.
-
-If you enable this policy setting, you can use the check boxes provided to change the options. If you disable or do not configure this setting, it has no effect on the system.
-
-The "Allow processing across a slow network connection" option updates the policies even when the update is being transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired policy setting in case a user has changed it.
- Configure security policy processing
- This policy setting determines when security policies are updated.
-
-This policy setting affects all policies that use the security component of Group Policy, such as those in Windows Settings\Security Settings.
-
-This policy setting overrides customized settings that the program implementing the security policy set when it was installed.
-
-If you enable this policy setting, you can use the check boxes provided to change the options. If you disable or do not configure this policy setting, it has no effect on the system.
-
-The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they be updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired policy setting in case a user has changed it.
- Configure wireless policy processing
- This policy setting determines when policies that assign wireless network settings are updated.
-
-This policy setting affects all policies that use the wireless network component of Group Policy, such as those in WindowsSettings\Wireless Network Policies.
-
-It overrides customized settings that the program implementing the wireless network set when it was installed.
-
-If you enable this policy, you can use the check boxes provided to change the options.
-
-If you disable this setting or do not configure it, it has no effect on the system.
-
-The "Allow processing across a slow network connection" option updates the policies even when the update is being transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired setting in case a user has changed it.
- Configure wired policy processing
- This policy setting determines when policies that assign wired network settings are updated.
-
-This policy setting affects all policies that use the wired network component of Group Policy, such as those in Windows Settings\Wired Network Policies.
-
-It overrides customized settings that the program implementing the wired network set when it was installed.
-
-If you enable this policy, you can use the check boxes provided to change the options.
-
-If you disable this setting or do not configure it, it has no effect on the system.
-
-The "Allow processing across a slow network connection" option updates the policies even when the update is being transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-The "Do not apply during periodic background processing" option prevents the system from updating affected policies in the background while the computer is in use. When background updates are disabled, policy changes will not take effect until the next user logon or system restart.
-
-The "Process even if the Group Policy objects have not changed" option updates and reapplies the policies even if the policies have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged policies, such as reapplying a desired setting in case a user has changed it.
-
- Determine if interactive users can generate Resultant Set of Policy data
- This policy setting controls the ability of users to view their Resultant Set of Policy (RSoP) data.
-
-By default, interactively logged on users can view their own Resultant Set of Policy (RSoP) data.
-
-If you enable this policy setting, interactive users cannot generate RSoP data.
-
-If you disable or do not configure this policy setting, interactive users can generate RSoP.
-
-Note: This policy setting does not affect administrators. If you enable or disable this policy setting, by default administrators can view RSoP data.
-
-Note: To view RSoP data on a client computer, use the RSoP snap-in for the Microsoft Management Console. You can launch the RSoP snap-in from the command line by typing RSOP.msc
-
-Note: This policy setting exists as both a User Configuration and Computer Configuration setting.
-
-Also, see the "Turn off Resultant set of Policy logging" policy setting in Computer Configuration\Administrative Templates\System\GroupPolicy.
- Turn off automatic update of ADM files
- Prevents the system from updating the Administrative Templates source files automatically when you open the Group Policy Object Editor. Administrators might want to use this if they are concerned about the amount of space used on the system volume of a DC.
-
-By default, when you start the Group Policy Object Editor, a timestamp comparison is performed on the source files in the local %SYSTEMROOT%\inf directory and the source files stored in the GPO. If the local files are newer, they are copied into the GPO.
-
-Changing the status of this setting to Enabled will keep any source files from copying to the GPO.
-
-Changing the status of this setting to Disabled will enforce the default behavior. Files will always be copied to the GPO if they have a later timestamp.
-
-NOTE: If the Computer Configuration policy setting, "Always use local ADM files for the Group Policy Object Editor" is enabled, the state of this setting is ignored and always treated as Enabled.
- Turn off background refresh of Group Policy
- This policy setting prevents Group Policy from being updated while the computer is in use. This policy setting applies to Group Policy for computers, users, and domain controllers.
-
-If you enable this policy setting, the system waits until the current user logs off the system before updating the computer and user settings.
-
-If you disable or do not configure this policy setting, updates can be applied while users are working. The frequency of updates is determined by the "Set Group Policy refresh interval for computers" and "Set Group Policy refresh interval for users" policy settings.
-
-Note: If you make changes to this policy setting, you must restart your computer for it to take effect.
- Remove users' ability to invoke machine policy refresh
- This policy setting allows you to control a user's ability to invoke a computer policy refresh.
-
-If you enable this policy setting, users are not able to invoke a refresh of computer policy. Computer policy will still be applied at startup or when an official policy refresh occurs.
-
-If you disable or do not configure this policy setting, the default behavior applies. By default, computer policy is applied when the computer starts up. It also applies at a specified refresh interval or when manually invoked by the user.
-
-Note: This policy setting applies only to non-administrators. Administrators can still invoke a refresh of computer policy at any time, no matter how this policy setting is configured.
-
-Also, see the "Set Group Policy refresh interval for computers" policy setting to change the policy refresh interval.
-
-Note: If you make changes to this policy setting, you must restart your computer for it to take effect.
- Enforce Show Policies Only
- This policy setting prevents administrators from viewing or using Group Policy preferences.
-
-A Group Policy administration (.adm) file can contain both true settings and preferences. True settings, which are fully supported by Group Policy, must use registry entries in the Software\Policies or Software\Microsoft\Windows\CurrentVersion\Policies registry subkeys. Preferences, which are not fully supported, use registry entries in other subkeys.
-
-If you enable this policy setting, the "Show Policies Only" command is turned on, and administrators cannot turn it off. As a result, Group Policy Object Editor displays only true settings; preferences do not appear.
-
-If you disable or do not configure this policy setting, the "Show Policies Only" command is turned on by default, but administrators can view preferences by turning off the "Show Policies Only" command.
-
-Note: To find the "Show Policies Only" command, in Group Policy Object Editor, click the Administrative Templates folder (either one), right-click the same folder, and then point to "View."
-
-In Group Policy Object Editor, preferences have a red icon to distinguish them from true settings, which have a blue icon.
- Use any available domain controller
- Inherit from Active Directory Snap-ins
- Use the Primary Domain Controller
- Configure Group Policy domain controller selection
- This policy setting determines which domain controller the Group Policy Object Editor snap-in uses.
-
-If you enable this setting, you can which domain controller is used according to these options:
-
-"Use the Primary Domain Controller" indicates that the Group Policy Object Editor snap-in reads and writes changes to the domain controller designated as the PDC Operations Master for the domain.
-
-"Inherit from Active Directory Snap-ins" indicates that the Group Policy Object Editor snap-in reads and writes changes to the domain controller that Active Directory Users and Computers or Active Directory Sites and Services snap-ins use.
-
-"Use any available domain controller" indicates that the Group Policy Object Editor snap-in can read and write changes to any available domain controller.
-
-If you disable this setting or do not configure it, the Group Policy Object Editor snap-in uses the domain controller designated as the PDC Operations Master for the domain.
-
-Note: To change the PDC Operations Master for a domain, in Active Directory Users and Computers, right-click a domain, and then click "Operations Masters."
- Configure Group Policy slow link detection
- This policy setting defines a slow connection for purposes of applying and updating Group Policy.
-
-If the rate at which data is transferred from the domain controller providing a policy update to the computers in this group is slower than the rate specified by this setting, the system considers the connection to be slow.
-
-The system's response to a slow policy connection varies among policies. The program implementing the policy can specify the response to a slow link. Also, the policy processing settings in this folder lets you override the programs' specified responses to slow links.
-
-If you enable this setting, you can, in the "Connection speed" box, type a decimal number between 0 and 4,294,967,200, indicating a transfer rate in kilobits per second. Any connection slower than this rate is considered to be slow. If you type 0, all connections are considered to be fast.
-
-If you disable this setting or do not configure it, the system uses the default value of 500 kilobits per second.
-
-This setting appears in the Computer Configuration and User Configuration folders. The setting in Computer Configuration defines a slow link for policies in the Computer Configuration folder. The setting in User Configuration defines a slow link for settings in the User Configuration folder.
-
-Also, see the "Do not detect slow network connections" and related policies in Computer Configuration\Administrative Templates\System\User Profile. Note: If the profile server has IP connectivity, the connection speed setting is used. If the profile server does not have IP connectivity, the SMB timing is used.
- Set Group Policy refresh interval for computers
- This policy setting specifies how often Group Policy for computers is updated while the computer is in use (in the background). This setting specifies a background update rate only for Group Policies in the Computer Configuration folder.
-
-In addition to background updates, Group Policy for the computer is always updated when the system starts.
-
-By default, computer Group Policy is updated in the background every 90 minutes, with a random offset of 0 to 30 minutes.
-
-If you enable this setting, you can specify an update rate from 0 to 64,800 minutes (45 days). If you select 0 minutes, the computer tries to update Group Policy every 7 seconds. However, because updates might interfere with users' work and increase network traffic, very short update intervals are not appropriate for most installations.
-
-If you disable this setting, Group Policy is updated every 90 minutes (the default). To specify that Group Policy should never be updated while the computer is in use, select the "Turn off background refresh of Group Policy" policy.
-
-The Set Group Policy refresh interval for computers policy also lets you specify how much the actual update interval varies. To prevent clients with the same update interval from requesting updates simultaneously, the system varies the update interval for each client by a random number of minutes. The number you type in the random time box sets the upper limit for the range of variance. For example, if you type 30 minutes, the system selects a variance of 0 to 30 minutes. Typing a large number establishes a broad range and makes it less likely that client requests overlap. However, updates might be delayed significantly.
-
-This setting establishes the update rate for computer Group Policy. To set an update rate for user policies, use the "Set Group Policy refresh interval for users" setting (located in User Configuration\Administrative Templates\System\Group Policy).
-
-This setting is only used when the "Turn off background refresh of Group Policy" setting is not enabled.
-
-Note: Consider notifying users that their policy is updated periodically so that they recognize the signs of a policy update. When Group Policy is updated, the Windows desktop is refreshed; it flickers briefly and closes open menus. Also, restrictions imposed by Group Policies, such as those that limit the programs users can run, might interfere with tasks in progress.
- Set Group Policy refresh interval for domain controllers
- This policy setting specifies how often Group Policy is updated on domain controllers while they are running (in the background). The updates specified by this setting occur in addition to updates performed when the system starts.
-
-By default, Group Policy on the domain controllers is updated every five minutes.
-
-If you enable this setting, you can specify an update rate from 0 to 64,800 minutes (45 days). If you select 0 minutes, the domain controller tries to update Group Policy every 7 seconds. However, because updates might interfere with users' work and increase network traffic, very short update intervals are not appropriate for most installations.
-
-If you disable or do not configure this setting, the domain controller updates Group Policy every 5 minutes (the default). To specify that Group Policies for users should never be updated while the computer is in use, select the "Turn off background refresh of Group Policy" setting.
-
-This setting also lets you specify how much the actual update interval varies. To prevent domain controllers with the same update interval from requesting updates simultaneously, the system varies the update interval for each controller by a random number of minutes. The number you type in the random time box sets the upper limit for the range of variance. For example, if you type 30 minutes, the system selects a variance of 0 to 30 minutes. Typing a large number establishes a broad range and makes it less likely that update requests overlap. However, updates might be delayed significantly.
-
-Note: This setting is used only when you are establishing policy for a domain, site, organizational unit (OU), or customized group. If you are establishing policy for a local computer only, the system ignores this setting.
- Set Group Policy refresh interval for users
- This policy setting specifies how often Group Policy for users is updated while the computer is in use (in the background). This setting specifies a background update rate only for the Group Policies in the User Configuration folder.
-
-In addition to background updates, Group Policy for users is always updated when users log on.
-
-By default, user Group Policy is updated in the background every 90 minutes, with a random offset of 0 to 30 minutes.
-
-If you enable this setting, you can specify an update rate from 0 to 64,800 minutes (45 days). If you select 0 minutes, the computer tries to update user Group Policy every 7 seconds. However, because updates might interfere with users' work and increase network traffic, very short update intervals are not appropriate for most installations.
-
-If you disable this setting, user Group Policy is updated every 90 minutes (the default). To specify that Group Policy for users should never be updated while the computer is in use, select the "Turn off background refresh of Group Policy" setting.
-
-This setting also lets you specify how much the actual update interval varies. To prevent clients with the same update interval from requesting updates simultaneously, the system varies the update interval for each client by a random number of minutes. The number you type in the random time box sets the upper limit for the range of variance. For example, if you type 30 minutes, the system selects a variance of 0 to 30 minutes. Typing a large number establishes a broad range and makes it less likely that client requests overlap. However, updates might be delayed significantly.
-
-Important: If the "Turn off background refresh of Group Policy" setting is enabled, this setting is ignored.
-
-Note: This setting establishes the update rate for user Group Policies. To set an update rate for computer Group Policies, use the "Group Policy refresh interval for computers" setting (located in Computer Configuration\Administrative Templates\System\Group Policy).
-
-Tip: Consider notifying users that their policy is updated periodically so that they recognize the signs of a policy update. When Group Policy is updated, the Windows desktop is refreshed; it flickers briefly and closes open menus. Also, restrictions imposed by Group Policies, such as those that limit the programs a user can run, might interfere with tasks in progress.
- Set default name for new Group Policy objects
- This policy setting allows you to set the default display name for new Group Policy objects.
-
-This setting allows you to specify the default name for new Group Policy objects created from policy compliant Group Policy Management tools including the Group Policy tab in Active Directory tools and the GPO browser.
-
-The display name can contain environment variables and can be a maximum of 255 characters long.
-
-If this setting is Disabled or Not Configured, the default display name of New Group Policy object is used.
- Create new Group Policy Object links disabled by default
- This policy setting allows you to create new Group Policy object links in the disabled state.
-
-If you enable this setting, you can create all new Group Policy object links in the disabled state by default. After you configure and test the new object links by using a policy compliant Group Policy management tool such as Active Directory Users and Computers or Active Directory Sites and Services, you can enable the object links for use on the system.
-
-If you disable this setting or do not configure it, new Group Policy object links are created in the enabled state. If you do not want them to be effective until they are configured and tested, you must disable the object link.
- Always use local ADM files for Group Policy Object Editor
- This policy setting lets you always use local ADM files for the Group Policy snap-in.
-
-By default, when you edit a Group Policy Object (GPO) using the Group Policy Object Editor snap-in, the ADM files are loaded from that GPO into the Group Policy Object Editor snap-in. This allows you to use the same version of the ADM files that were used to create the GPO while editing this GPO.
-
-This leads to the following behavior:
-
-- If you originally created the GPO with, for example, an English system, the GPO contains English ADM files.
-
-- If you later edit the GPO from a different-language system, you get the English ADM files as they were in the GPO.
-
-You can change this behavior by using this setting.
-
-If you enable this setting, the Group Policy Object Editor snap-in always uses local ADM files in your %windir%\inf directory when editing GPOs.
-
-This leads to the following behavior:
-
-- If you had originally created the GPO with an English system, and then you edit the GPO with a Japanese system, the Group Policy Object Editor snap-in uses the local Japanese ADM files, and you see the text in Japanese under Administrative Templates.
-
-If you disable or do not configure this setting, the Group Policy Object Editor snap-in always loads all ADM files from the actual GPO.
-
-Note: If the ADMs that you require are not all available locally in your %windir%\inf directory, you might not be able to see all the settings that have been configured in the GPO that you are editing.
- Group Policy
- Turn off Resultant Set of Policy logging
- This setting allows you to enable or disable Resultant Set of Policy (RSoP) logging on a client computer.
-
-RSoP logs information on Group Policy settings that have been applied to the client. This information includes details such as which Group Policy Objects (GPO) were applied, where they came from, and the client-side extension settings that were included.
-
-If you enable this setting, RSoP logging is turned off.
-
-If you disable or do not configure this setting, RSoP logging is turned on. By default, RSoP logging is always on.
-
-Note: To view the RSoP information logged on a client computer, you can use the RSoP snap-in in the Microsoft Management Console (MMC).
- Configure user Group Policy loopback processing mode
- This policy setting directs the system to apply the set of Group Policy objects for the computer to any user who logs on to a computer affected by this setting. It is intended for special-use computers, such as those in public places, laboratories, and classrooms, where you must modify the user setting based on the computer that is being used.
-
-By default, the user's Group Policy Objects determine which user settings apply. If this setting is enabled, then, when a user logs on to this computer, the computer's Group Policy Objects determine which set of Group Policy Objects applies.
-
-If you enable this setting, you can select one of the following modes from the Mode box:
-
-"Replace" indicates that the user settings defined in the computer's Group Policy Objects replace the user settings normally applied to the user.
-
-"Merge" indicates that the user settings defined in the computer's Group Policy Objects and the user settings normally applied to the user are combined. If the settings conflict, the user settings in the computer's Group Policy Objects take precedence over the user's normal settings.
-
-If you disable this setting or do not configure it, the user's Group Policy Objects determines which user settings apply.
-
-Note: This setting is effective only when both the computer account and the user account are in at least Windows 2000 domains.
- Merge
- Replace
- Specify workplace connectivity wait time for policy processing
- This policy setting specifies how long Group Policy should wait for workplace connectivity notifications during startup policy processing. If the startup policy processing is synchronous, the computer is blocked until workplace connectivity is available or the wait time is reached. If the startup policy processing is asynchronous, the computer is not blocked and policy processing will occur in the background. In either case, configuring this policy setting overrides any system-computed wait times.
-
-If you enable this policy setting, Group Policy uses this administratively configured maximum wait time for workplace connectivity, and overrides any default or system-computed wait time.
-
-If you disable or do not configure this policy setting, Group Policy will use the default wait time of 60 seconds on computers running Windows operating systems greater than Windows 7 configured for workplace connectivity.
-
-
-
- Mitigation Options
-
-
- Process Mitigation Options
-
-
- The Windows Font Cache Service should be allowed to download fonts and font catalog data from online font providers.
-
-
- Slow link value:[number field] milliseconds
- Timeout value: [number field] milliseconds
-
-
- minute:
-
-
- Amount of time to wait (in seconds):
-
-
- Allow processing across a slow network connection
- Process even if the Group Policy objects have not changed
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
-
-
- Allow processing across a slow network connection
- Process even if the Group Policy objects have not changed
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
-
-
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
-
-
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
-
-
- When Group Policy Object Editor is selecting a domain controller to use, it should:
-
-
- Connection speed (Kbps):
-
- Enter 0 to disable slow link detection.
-
-
- Connection speed (Kbps):
-
- Enter 0 to disable slow link detection.
- Always treat WWAN connections as a slow link
-
-
- This setting allows you to customize how often Group Policy is applied
- to computers. The range is 0 to 44640 minutes (31 days).
- Minutes:
-
- This is a random time added to the refresh interval to prevent
- all clients from requesting Group Policy at the same time.
- The range is 0 to 1440 minutes (24 hours)
- Minutes:
-
-
- This setting allows you to customize how often Group Policy is applied
- to domain controllers. The range is 0 to 44640 minutes (31 days).
- Minutes:
-
- This is a random time added to the refresh interval to prevent
- all clients from requesting Group Policy at the same time.
- The range is 0 to 1440 minutes (24 hours)
- Minutes:
-
-
- This setting allows you to customize how often Group Policy is applied
- to users. The range is 0 to 44640 minutes (31 days).
- Minutes:
-
- This is a random time added to the refresh interval to prevent
- all clients from requesting Group Policy at the same time.
- The range is 0 to 1440 minutes (24 hours)
- Minutes:
-
-
-
-
-
-
-
- Mode:
-
-
- Amount of time to wait (in seconds):
-
-
-
-
diff --git a/policy_templates/en-US/Handwriting.adml b/policy_templates/en-US/Handwriting.adml
deleted file mode 100644
index 8df1f6a..0000000
--- a/policy_templates/en-US/Handwriting.adml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- Windows Ink Workspace
- Windows Ink Workspace
-
-
- Handwriting
- Handwriting Panel Default Mode Docked
- The handwriting panel has 2 modes - floats near the text box, or, attached to the bottom of the screen. Default is floating near text box. If you want the panel to be fixed, use this policy to fix it to the bottom.
-
-
-
diff --git a/policy_templates/en-US/Help.adml b/policy_templates/en-US/Help.adml
deleted file mode 100644
index 342cd7b..0000000
--- a/policy_templates/en-US/Help.adml
+++ /dev/null
@@ -1,71 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Restrict potentially unsafe HTML Help functions to specified folders
- This policy setting allows you to restrict certain HTML Help commands to function only in HTML Help (.chm) files within specified folders and their subfolders. Alternatively, you can disable these commands on the entire system. It is strongly recommended that only folders requiring administrative privileges be added to this policy setting.
-
- If you enable this policy setting, the commands function only for .chm files in the specified folders and their subfolders.
-
- To restrict the commands to one or more folders, enable the policy setting and enter the desired folders in the text box on the Settings tab of the Policy Properties dialog box. Use a semicolon to separate folders. For example, to restrict the commands to only .chm files in the %windir%\help folder and D:\somefolder, add the following string to the edit box: "%windir%\help;D:\somefolder".
-
- Note: An environment variable may be used, (for example, %windir%), as long as it is defined on the system. For example, %programfiles% is not defined on some early versions of Windows.
-
- The "Shortcut" command is used to add a link to a Help topic, and runs executables that are external to the Help file. The "WinHelp" command is used to add a link to a Help topic, and runs a WinHLP32.exe Help (.hlp) file.
-
- To disallow the "Shortcut" and "WinHelp" commands on the entire local system, enable the policy setting and leave the text box on the Settings tab of the Policy Properties dialog box blank.
-
- If you disable or do not configure this policy setting, these commands are fully functional for all Help files.
-
- Note: Only folders on the local computer can be specified in this policy setting. You cannot use this policy setting to enable the "Shortcut" and "WinHelp" commands for .chm files that are stored on mapped drives or accessed using UNC paths.
-
- For additional options, see the "Restrict these programs from being launched from Help" policy.
-
- Restrict these programs from being launched from Help
- Restrict these programs from being launched from Help
-
- This policy setting allows you to restrict programs from being run from online Help.
-
- If you enable this policy setting, you can prevent specified programs from being run from Help. When you enable this policy setting, enter the file names names of the programs you want to restrict, separated by commas.
-
- If you disable or do not configure this policy setting, users can run all applications from online Help.
-
- Note: You can also restrict users from running applications by using the Software Restriction Policy settings available in Computer Configuration\Security Settings.
-
- Note: This policy setting is available under Computer Configuration and User Configuration. If both are settings are used, any programs listed in either of these locations cannot launched from Help
-
- Turn off Data Execution Prevention for HTML Help Executible
- This policy setting allows you to exclude HTML Help Executable from being monitored by software-enforced Data Execution Prevention.
-
- Data Execution Prevention (DEP) is designed to block malicious code that takes advantage of exception-handling mechanisms in Windows by monitoring your programs to make sure that they use system memory safely.
-
- If you enable this policy setting, DEP for HTML Help Executable is turned off. This will allow certain legacy ActiveX controls to function without DEP shutting down HTML Help Executable.
-
- If you disable or do not configure this policy setting, DEP is turned on for HTML Help Executable. This provides an additional security benefit, but HTLM Help stops if DEP detects system memory abnormalities.
-
-
-
-
-
-
-
- Example: %windir%\Help;%windir%\pchealth;%programfiles%
-
-
-
-
-
- Example: calc.exe,paint.exe
-
-
-
-
-
- Example: calc.exe,paint.exe
-
-
-
-
diff --git a/policy_templates/en-US/HelpAndSupport.adml b/policy_templates/en-US/HelpAndSupport.adml
deleted file mode 100644
index 1c1416c..0000000
--- a/policy_templates/en-US/HelpAndSupport.adml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- Online Assistance
- Online Assistance
-
-
- Online Assistance
- Windows Components
- This policy setting specifies whether active content links in trusted assistance content are rendered. By default, the Help viewer renders trusted assistance content with active elements such as ShellExecute links and Guided Help links.
-
-If you enable this policy setting, active content links are not rendered. The text is displayed, but there are no clickable links for these elements.
-
-If you disable or do not configure this policy setting, the default behavior applies (Help viewer renders trusted assistance content with active elements).
- Turn off Active Help
- Turn off Help Ratings
- This policy setting specifies whether users can provide ratings for Help content.
-
-If you enable this policy setting, ratings controls are not added to Help content.
-
-If you disable or do not configure this policy setting, ratings controls are added to Help topics.
-
-Users can use the control to provide feedback on the quality and usefulness of the Help and Support content.
- Turn off Help Experience Improvement Program
- This policy setting specifies whether users can participate in the Help Experience Improvement program. The Help Experience Improvement program collects information about how customers use Windows Help so that Microsoft can improve it.
-
-If you enable this policy setting, users cannot participate in the Help Experience Improvement program.
-
-If you disable or do not configure this policy setting, users can turn on the Help Experience Improvement program feature from the Help and Support settings page.
- Turn off Windows Online
- This policy setting specifies whether users can search and view content from Windows Online in Help and Support. Windows Online provides the most up-to-date Help content for Windows.
-
-If you enable this policy setting, users are prevented from accessing online assistance content from Windows Online.
-
-If you disable or do not configure this policy setting, users can access online assistance if they have a connection to the Internet and have not disabled Windows Online from the Help and Support Options page.
-
-
-
diff --git a/policy_templates/en-US/ICM.adml b/policy_templates/en-US/ICM.adml
deleted file mode 100644
index 66c80c7..0000000
--- a/policy_templates/en-US/ICM.adml
+++ /dev/null
@@ -1,198 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off Automatic Root Certificates Update
- This policy setting specifies whether to automatically update root certificates using the Windows Update website.
-
-Typically, a certificate is used when you use a secure website or when you send and receive secure email. Anyone can issue certificates, but to have transactions that are as secure as possible, certificates must be issued by a trusted certificate authority (CA). Microsoft has included a list in Windows XP and other products of companies and organizations that it considers trusted authorities.
-
-If you enable this policy setting, when you are presented with a certificate issued by an untrusted root authority, your computer will not contact the Windows Update website to see if Microsoft has added the CA to its list of trusted authorities.
-
-If you disable or do not configure this policy setting, your computer will contact the Windows Update website.
- Turn off printing over HTTP
- This policy setting specifies whether to allow printing over HTTP from this client.
-
-Printing over HTTP allows a client to print to printers on the intranet as well as the Internet.
-
-Note: This policy setting affects the client side of Internet printing only. It does not prevent this computer from acting as an Internet Printing server and making its shared printers available via HTTP.
-
-If you enable this policy setting, it prevents this client from printing to Internet printers over HTTP.
-
-If you disable or do not configure this policy setting, users can choose to print to Internet printers over HTTP.
-
-Also, see the "Web-based printing" policy setting in Computer Configuration/Administrative Templates/Printers.
- Turn off downloading of print drivers over HTTP
- This policy setting specifies whether to allow this client to download print driver packages over HTTP.
-
-To set up HTTP printing, non-inbox drivers need to be downloaded over HTTP.
-
-Note: This policy setting does not prevent the client from printing to printers on the Intranet or the Internet over HTTP. It only prohibits downloading drivers that are not already installed locally.
-
-If you enable this policy setting, print drivers cannot be downloaded over HTTP.
-
-If you disable or do not configure this policy setting, users can download print drivers over HTTP.
- Turn off Windows Update device driver searching
- This policy setting specifies whether Windows searches Windows Update for device drivers when no local drivers for a device are present.
-
-If you enable this policy setting, Windows Update is not searched when a new device is installed.
-
-If you disable this policy setting, Windows Update is always searched for drivers when no local drivers are present.
-
-If you do not configure this policy setting, searching Windows Update is optional when installing a device.
-
-Also see "Turn off Windows Update device driver search prompt" in "Administrative Templates/System," which governs whether an administrator is prompted before searching Windows Update for device drivers if a driver is not found locally.
-
-Note: This policy setting is replaced by "Specify Driver Source Search Order" in "Administrative Templates/System/Device Installation" on newer versions of Windows.
- Turn off Event Viewer "Events.asp" links
- This policy setting specifies whether "Events.asp" hyperlinks are available for events within the Event Viewer application.
-
-The Event Viewer normally makes all HTTP(S) URLs into hyperlinks that activate the Internet browser when clicked. In addition, "More Information" is placed at the end of the description text if the event is created by a Microsoft component. This text contains a link (URL) that, if clicked, sends information about the event to Microsoft, and allows users to learn more about why that event occurred.
-
-If you enable this policy setting, event description hyperlinks are not activated and the text "More Information" is not displayed at the end of the description.
-
-If you disable or do not configure this policy setting, the user can click the hyperlink, which prompts the user and then sends information about the event over the Internet to Microsoft. Also, see "Events.asp URL", "Events.asp program", and "Events.asp Program Command Line Parameters" settings in "Administrative Templates/Windows Components/Event Viewer".
- Turn off Help and Support Center "Did you know?" content
- This policy setting specifies whether to show the "Did you know?" section of Help and Support Center.
-
-This content is dynamically updated when users who are connected to the Internet open Help and Support Center, and provides up-to-date information about Windows and the computer.
-
-If you enable this policy setting, the Help and Support Center no longer retrieves nor displays "Did you know?" content.
-
-If you disable or do not configure this policy setting, the Help and Support Center retrieves and displays "Did you know?" content.
-
-You might want to enable this policy setting for users who do not have Internet access, because the content in the "Did you know?" section will remain static indefinitely without an Internet connection.
- Turn off Help and Support Center Microsoft Knowledge Base search
- This policy setting specifies whether users can perform a Microsoft Knowledge Base search from the Help and Support Center.
-
-The Knowledge Base is an online source of technical support information and self-help tools for Microsoft products, and is searched as part of all Help and Support Center searches with the default search options.
-
-If you enable this policy setting, it removes the Knowledge Base section from the Help and Support Center "Set search options" page, and only Help content on the local computer is searched.
-
-If you disable or do not configure this policy setting, the Knowledge Base is searched if the user has a connection to the Internet and has not disabled the Knowledge Base search from the Search Options page.
- Restrict Internet communication
- This policy setting specifies whether Windows can access the Internet to accomplish tasks that require Internet resources.
-
-If you enable this setting, all of the the policy settings listed in the "Internet Communication settings" section are set such that their respective features cannot access the Internet.
-
-If you disable this policy setting, all of the the policy settings listed in the "Internet Communication settings" section are set such that their respective features can access the Internet.
-
-If you do not configure this policy setting, all of the the policy settings in the "Internet Communication settings" section are set to not configured.
- Turn off Internet Connection Wizard if URL connection is referring to Microsoft.com
- This policy setting specifies whether the Internet Connection Wizard can connect to Microsoft to download a list of Internet Service Providers (ISPs).
-
-If you enable this policy setting, the "Choose a list of Internet Service Providers" path in the Internet Connection Wizard causes the wizard to exit. This prevents users from retrieving the list of ISPs, which resides on Microsoft servers.
-
-If you disable or do not configure this policy setting, users can connect to Microsoft to download a list of ISPs for their area.
- Turn off Registration if URL connection is referring to Microsoft.com
- This policy setting specifies whether the Windows Registration Wizard connects to Microsoft.com for online registration.
-
-If you enable this policy setting, it blocks users from connecting to Microsoft.com for online registration and users cannot register their copy of Windows online.
-
-If you disable or do not configure this policy setting, users can connect to Microsoft.com to complete the online Windows Registration.
-
-Note that registration is optional and involves submitting some personal information to Microsoft. However, Windows Product Activation is required but does not involve submitting any personal information (except the country/region you live in).
- Turn off Windows Error Reporting
- This policy setting controls whether or not errors are reported to Microsoft.
-
-Error Reporting is used to report information about a system or application that has failed or has stopped responding and is used to improve the quality of the product.
-
-If you enable this policy setting, users are not given the option to report errors.
-
-If you disable or do not configure this policy setting, the errors may be reported to Microsoft via the Internet or to a corporate file share.
-
-This policy setting overrides any user setting made from the Control Panel for error reporting.
-
-Also see the "Configure Error Reporting", "Display Error Notification" and "Disable Windows Error Reporting" policy settings under Computer Configuration/Administrative Templates/Windows Components/Windows Error Reporting.
- Turn off access to all Windows Update features
- This policy setting allows you to remove access to Windows Update.
-
-If you enable this policy setting, all Windows Update features are removed. This includes blocking access to the Windows Update website at http://windowsupdate.microsoft.com, from the Windows Update hyperlink on the Start menu, and also on the Tools menu in Internet Explorer. Windows automatic updating is also disabled; you will neither be notified about nor will you receive critical updates from Windows Update. This policy setting also prevents Device Manager from automatically installing driver updates from the Windows Update website.
-
-If you disable or do not configure this policy setting, users can access the Windows Update website and enable automatic updating to receive notifications and critical updates from Windows Update.
-
-Note: This policy applies only when this PC is configured to connect to an intranet update service using the "Specify intranet Microsoft update service location" policy.
- Turn off Search Companion content file updates
- This policy setting specifies whether Search Companion should automatically download content updates during local and Internet searches.
-
-When users search the local computer or the Internet, Search Companion occasionally connects to Microsoft to download an updated privacy policy and additional content files used to format and display results.
-
-If you enable this policy setting, Search Companion does not download content updates during searches.
-
-If you disable or do not configure this policy setting, Search Companion downloads content updates unless the user is using Classic Search.
-
-Note: Internet searches still send the search text and information about the search to Microsoft and the chosen search provider. Choosing Classic Search turns off the Search Companion feature completely.
- Turn off Internet File Association service
- This policy setting specifies whether to use the Microsoft Web service for finding an application to open a file with an unhandled file association.
-
-When a user opens a file that has an extension that is not associated with any applications on the computer, the user is given the choice to select a local application or use the Web service to find an application.
-
-If you enable this policy setting, the link and the dialog for using the Web service to open an unhandled file association are removed.
-
-If you disable or do not configure this policy setting, the user is allowed to use the Web service.
- Turn off access to the Store
- This policy setting specifies whether to use the Store service for finding an application to open a file with an unhandled file type or protocol association.
-
-When a user opens a file type or protocol that is not associated with any applications on the computer, the user is given the choice to select a local application or use the Store service to find an application.
-
-If you enable this policy setting, the "Look for an app in the Store" item in the Open With dialog is removed.
-
-If you disable or do not configure this policy setting, the user is allowed to use the Store service and the Store item is available in the Open With dialog.
- Turn off Internet download for Web publishing and online ordering wizards
- This policy setting specifies whether Windows should download a list of providers for the web publishing and online ordering wizards.
-
-These wizards allow users to select from a list of companies that provide services such as online storage and photographic printing. By default, Windows displays providers downloaded from a Windows website in addition to providers specified in the registry.
-
-If you enable this policy setting, Windows does not download providers, and only the service providers that are cached in the local registry are displayed.
-
-If you disable or do not configure this policy setting, a list of providers are downloaded when the user uses the web publishing or online ordering wizards.
-
-See the documentation for the web publishing and online ordering wizards for more information, including details on specifying service providers in the registry.
- Turn off the "Order Prints" picture task
- This policy setting specifies whether the "Order Prints Online" task is available from Picture Tasks in Windows folders.
-
-The Order Prints Online Wizard is used to download a list of providers and allow users to order prints online.
-
-If you enable this policy setting, the task "Order Prints Online" is removed from Picture Tasks in File Explorer folders.
-
-If you disable or do not configure this policy setting, the task is displayed.
- Turn off the "Publish to Web" task for files and folders
- This policy setting specifies whether the tasks "Publish this file to the Web," "Publish this folder to the Web," and "Publish the selected items to the Web" are available from File and Folder Tasks in Windows folders.
-
-The Web Publishing Wizard is used to download a list of providers and allow users to publish content to the web.
-
-If you enable this policy setting, these tasks are removed from the File and Folder tasks in Windows folders.
-
-If you disable or do not configure this policy setting, the tasks are shown.
- Turn off the Windows Messenger Customer Experience Improvement Program
- This policy setting specifies whether Windows Messenger collects anonymous information about how Windows Messenger software and service is used.
-
-With the Customer Experience Improvement program, users can allow Microsoft to collect anonymous information about how the product is used. This information is used to improve the product in future releases.
-
-If you enable this policy setting, Windows Messenger does not collect usage information, and the user settings to enable the collection of usage information are not shown.
-
-If you disable this policy setting, Windows Messenger collects anonymous usage information, and the setting is not shown.
-
-If you do not configure this policy setting, users have the choice to opt in and allow information to be collected.
- Turn off Windows Customer Experience Improvement Program
- This policy setting turns off the Windows Customer Experience Improvement Program. The Windows Customer Experience Improvement Program collects information about your hardware configuration and how you use our software and services to identify trends and usage patterns. Microsoft will not collect your name, address, or any other personally identifiable information. There are no surveys to complete, no salesperson will call, and you can continue working without interruption. It is simple and user-friendly.
-
-If you enable this policy setting, all users are opted out of the Windows Customer Experience Improvement Program.
-
-If you disable this policy setting, all users are opted into the Windows Customer Experience Improvement Program.
-
-If you do not configure this policy setting, the administrator can use the Problem Reports and Solutions component in Control Panel to enable Windows Customer Experience Improvement Program for all users.
- Turn off Windows Network Connectivity Status Indicator active tests
- This policy setting turns off the active tests performed by the Windows Network Connectivity Status Indicator (NCSI) to determine whether your computer is connected to the Internet or to a more limited network.
-
-As part of determining the connectivity level, NCSI performs one of two active tests: downloading a page from a dedicated Web server or making a DNS request for a dedicated address.
-
-If you enable this policy setting, NCSI does not run either of the two active tests. This may reduce the ability of NCSI, and of other components that use NCSI, to determine Internet access.
-
-If you disable or do not configure this policy setting, NCSI runs one of the two active tests.
-
-
-
diff --git a/policy_templates/en-US/IIS.adml b/policy_templates/en-US/IIS.adml
deleted file mode 100644
index 8aed20a..0000000
--- a/policy_templates/en-US/IIS.adml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Internet Information Services
- Prevent IIS installation
- "This policy setting prevents installation of Internet Information Services (IIS) on this computer. If you enable this policy setting, Internet Information Services (IIS) cannot be installed, and you will not be able to install Windows components or applications that require IIS. Users installing Windows components or applications that require IIS might not receive a warning that IIS cannot be installed because of this Group Policy setting. Enabling this setting will not have any effect on IIS if IIS is already installed on the computer. If you disable or do not configure this policy setting, IIS can be installed, as well as all the programs and applications that require IIS to run."
-
-
-
diff --git a/policy_templates/en-US/InetRes.adml b/policy_templates/en-US/InetRes.adml
deleted file mode 100644
index c713579..0000000
--- a/policy_templates/en-US/InetRes.adml
+++ /dev/null
@@ -1,4914 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Accessibility
- International
- Security
- Connections Page
- Content Page
- Certificates
- Appearance
- Search
- Tabs
- Privacy Page
- Programs Page
- Add-on List
- Deny all add-ons unless specifically allowed in the Add-on List
- Turn off Crash Detection
- Do not allow users to enable or disable add-ons
- Add a specific list of search providers to the user's list of search providers
- Administrator Approved Controls
- Advanced settings
- Allow active content from CDs to run on user machines
- Check for server certificate revocation
- Turn off ClearType
- Do not allow resetting Internet Explorer settings
- Check for signatures on downloaded programs
- Allow third-party browser extensions
- This policy setting allows you to manage whether users receive a dialog requesting permission for active content on a CD to run.
-
-If you enable this policy setting, active content on a CD will run without a prompt.
-
-If you disable this policy setting, active content on a CD will always prompt before running.
-
-If you do not configure this policy, users can choose whether to be prompted before running active content on a CD.
- This policy setting allows you to manage whether Internet Explorer will check revocation status of servers' certificates. Certificates are revoked when they have been compromised or are no longer valid, and this option protects users from submitting confidential data to a site that may be fraudulent or not secure.
-
-If you enable this policy setting, Internet Explorer will check to see if server certificates have been revoked.
-
-If you disable this policy setting, Internet Explorer will not check server certificates to see if they have been revoked.
-
-If you do not configure this policy setting, Internet Explorer will not check server certificates to see if they have been revoked.
- This policy setting prevents the user from using the Reset Internet Explorer Settings feature. Reset Internet Explorer Settings allows the user to reset all settings changed since installation, delete browsing history, and disable add-ons that are not preapproved.
-
-If you enable this policy setting, the user cannot use Reset Internet Explorer Settings.
-
-If you disable or do not configure this policy setting, the user can use Reset Internet Explorer Settings.
- This policy setting allows you to manage whether Internet Explorer checks for digital signatures (which identifies the publisher of signed software and verifies it hasn't been modified or tampered with) on user computers before downloading executable programs.
-
-If you enable this policy setting, Internet Explorer will check the digital signatures of executable programs and display their identities before downloading them to user computers.
-
-If you disable this policy setting, Internet Explorer will not check the digital signatures of executable programs or display their identities before downloading them to user computers.
-
-If you do not configure this policy, Internet Explorer will not check the digital signatures of executable programs or display their identities before downloading them to user computers.
- This policy setting allows you to manage whether Internet Explorer will launch COM add-ons known as browser helper objects, such as toolbars. Browser helper objects may contain flaws such as buffer overruns which impact Internet Explorer's performance or stability.
-
-If you enable this policy setting, Internet Explorer automatically launches any browser helper objects that are installed on the user's computer.
-
-If you disable this policy setting, browser helper objects do not launch.
-
-If you do not configure this policy, Internet Explorer automatically launches any browser helper objects that are installed on the user's computer.
- This policy setting allows you to manage whether users can automatically download and install Web components (such as fonts) that can installed by Internet Explorer Active Setup. For example, if you open a Web page that requires Japanese-text display support, Internet Explorer could prompt the user to download the Japanese Language Pack component if it is not already installed.
-
-If you enable this policy setting, Web components such as fonts will be automatically installed as necessary.
-
-If you disable this policy setting, users will be prompted when Web Components such as fonts would be downloaded.
-
-If you do not configure this policy, users will be prompted when Web Components such as fonts would be downloaded.
- This policy setting allows you to manage whether users can download and install self-installing program files (non-Internet Explorer components) that are registered with Internet Explorer (such as Macromedia and Java) that are required in order to view web pages as intended.
-
-If you enable this policy setting, non-Internet Explorer components will be automatically installed as necessary.
-
-If you disable this policy setting, users will be prompted when non-Internet Explorer components would be installed.
-
-If you do not configure this policy setting, non-Internet Explorer components will be automatically installed as necessary.
- This policy setting allows you to manage whether Internet Explorer checks the Internet for newer versions. When Internet Explorer is set to do this, the checks occur approximately every 30 days, and users are prompted to install new versions as they become available.
-
-If you enable this policy setting, Internet Explorer checks the Internet for a new version approximately every 30 days and prompts the user to download new versions when they are available.
-
-If you disable this policy setting, Internet Explorer does not check the Internet for new versions of the browser, so does not prompt users to install them.
-
-If you do not configure this policy setting, Internet Explorer does not check the Internet for new versions of the browser, so does not prompt users to install them.
- This policy setting allows you to manage whether software, such as ActiveX controls and file downloads, can be installed or run by the user even though the signature is invalid. An invalid signature might indicate that someone has tampered with the file.
-
-If you enable this policy setting, users will be prompted to install or run files with an invalid signature.
-
-If you disable this policy setting, users cannot run or install files with an invalid signature.
-
-If you do not configure this policy, users can choose to run or install files with an invalid signature.
- This policy setting allows you to manage whether Internet Explorer will display animated pictures found in Web content. Generally only animated GIF files are affected by this setting; active Web content such as java applets are not.
-
-If you enable this policy setting, Internet Explorer will play animated pictures found in Web content.
-
-If you disable this policy setting, Internet Explorer will not play or download animated pictures, helping pages display more quickly.
-
-If you do not configure this policy setting, Internet Explorer will play animated pictures found in Web content.
- This policy setting allows you to manage whether Internet Explorer will play sounds found in web content. Generally only sound files such as MIDI files are affected by this setting; active Web content such as java applets are not.
-
-If you enable this policy setting, Internet Explorer will play sounds found in Web content.
-
-If you disable this policy setting, Internet Explorer will not play or download sounds in Web content, helping pages display more quickly.
-
-If you enable this policy setting, Internet Explorer will play sounds found in Web content.
- This policy setting allows you to manage whether Internet Explorer will display videos found in Web content. Generally only embedded video files are affected by this setting; active Web content such as java applets are not.
-
-If you enable this policy setting, Internet Explorer will play videos found in Web content.
-
-If you disable this policy setting, Internet Explorer will not play or download videos, helping pages display more quickly.
-
-If you do not configure this policy setting, Internet Explorer will play videos found in Web content.
- This policy setting specifies whether you will accept requests from Web sites for Profile Assistant information.
-
-If you enable this policy setting, Profile Assistant information will not be provided, and users will not be prompted to provide information.
-
-If you disable this policy setting, then when a Web site requests Profile Assistant information, users will be prompted to choose which information to share. At that time, users can also choose to allow this information to be shared with the Web site in the future without being prompted.
-
-If you do not configure this policy setting, a user will have the freedom to accept requests from Web sites for Profile Assistant information.
- This policy setting allows you to manage whether Internet Explorer will save encrypted pages that contain secure (HTTPS) information such as passwords and credit card numbers to the Internet Explorer cache, which may be insecure.
-
-If you enable this policy setting, Internet Explorer will not save encrypted pages containing secure (HTTPS) information to the cache.
-
-If you disable this policy setting, Internet Explorer will save encrypted pages containing secure (HTTPS) information to the cache.
-
-If you do not configure this policy, Internet Explorer will save encrypted pages containing secure (HTTPS) information to the cache.
- This policy setting allows you to manage whether Internet Explorer deletes the contents of the Temporary Internet Files folder after all browser windows are closed. This protects against storing dangerous files on the computer, or storing sensitive files that other users could see, in addition to managing total disk space usage.
-
-If you enable this policy setting, Internet Explorer will delete the contents of the user's Temporary Internet Files folder when all browser windows are closed.
-
-If you disable this policy setting, Internet Explorer will not delete the contents of the user's Temporary Internet Files folder when browser windows are closed.
-
-If you do not configure this policy, Internet Explorer will not delete the contents of the Temporary Internet Files folder when browser windows are closed.
- Allow Install On Demand (Internet Explorer)
- Allow Install On Demand (except Internet Explorer)
- Automatically check for Internet Explorer updates
- Allow software to run or install even if the signature is invalid
- Play animations in web pages
- Play sounds in web pages
- Play videos in web pages
- Turn off Profile Assistant
- Do not save encrypted pages to disk
- Empty Temporary Internet Files folder when browser is closed
- Advanced Page
- Allow Microsoft services to provide enhanced suggestions as the user types in the Address bar
- This policy setting allows Internet Explorer to provide enhanced suggestions as the user types in the Address bar. To provide enhanced suggestions, the user's keystrokes are sent to Microsoft through Microsoft services.
-
-If you enable this policy setting, users receive enhanced suggestions while typing in the Address bar. In addition, users won't be able to change the Suggestions setting on the Settings charm.
-
-If you disable this policy setting, users won't receive enhanced suggestions while typing in the Address bar. In addition, users won't be able to change the Suggestions setting on the Settings charm.
-
-If you don't configure this policy setting, users can change the Suggestions setting on the Settings charm.
- Always
- Turn on menu bar by default
- This policy setting prevents the user from specifying the color to which hyperlinks change when the mouse pointer pauses on them.
-
-If you enable this policy setting, the user cannot specify the hover color. You must specify the hover color (for example: 192,192,192).
-
-If you disable or do not configure this policy setting, the user can specify the hover color.
- Prevent specifying the hover color
- Audio/Video Player
- Turn on inline AutoComplete
- This policy setting allows you to turn on inline AutoComplete in Internet Explorer and File Explorer. The AutoComplete feature provides suggestions for what the user types by automatically completing the address or command with the closest match.
-
-If you enable this policy setting, inline AutoComplete is turned on. The user cannot turn it off.
-
-If you disable this policy setting, inline AutoComplete is turned off. The user cannot turn it on.
-
-If you do not configure this policy setting, the user can turn on or turn off inline AutoComplete.
-
-By default, inline AutoComplete is turned off for Windows Vista, Windows 7, Internet Explorer 7, and Internet Explorer 8. By default, inline AutoComplete is turned on for Internet Explorer 9.
- AutoComplete
- Turn off inline AutoComplete in File Explorer
- This policy setting let you turn off Inline AutoComplete in File Explorer. Inline AutoComplete provides suggestions for what you type by automatically completing the command inline with the closest match. By default, this functionality is turned on in File Explorer.
-
-If you enable this policy setting, Inline AutoComplete for File Explorer is turned off. The user cannot turn it on.
-
-If you disable this policy setting, Inline AutoComplete for File Explorer is turned on. The user cannot turn it off.
-
-If you do not configure this policy setting, a user will have the freedom to turn on or off Inline AutoComplete for File Explorer.
- Automatic
- Disable caching of Auto-Proxy scripts
- Do not search from the address bar
- Display the results in the main window
- Go to an intranet site for a one-word entry in the Address bar
- This policy allows the user to go directly to an intranet site for a one-word entry in the Address bar.
-
-If you enable this policy setting, Internet Explorer goes directly to an intranet site for a one-word entry in the Address bar, if it is available.
-
-If you disable or do not configure this policy setting, Internet Explorer does not go directly to an intranet site for a one-word entry in the Address bar.
- Background
- This policy setting prevents the user from specifying the background color in Internet Explorer.
-
-If you enable this policy setting, the user cannot specify the background color in Internet Explorer. You must specify the background color (for example: 192,192,192).
-
-If you disable or do not configure this policy setting, the user can specify the background color in Internet Explorer.
- Prevent specifying background color
- Turn on printing of background colors and images
- Disable external branding of Internet Explorer
- Browsing
- Carpoint
- Application Compatibility
- Offline Pages
- Code Download
- Prevent specifying the code download path for each computer
- This policy setting prevents the user from specifying the code download path for each computer. The Internet Component Download service exposes a function that is called by an application to download, verify, and install code for an Object Linking and Embedding (OLE) component.
-
-If you enable this policy setting, the user cannot specify the download path for the code. You must specify the download path.
-
-If you disable or do not configure this policy setting, the user can specify the download path for the code.
- Component Updates
- Disable changing Advanced page settings
- Disable the Advanced page
- Disable the Connections page
- Disable the Content page
- Disable the General page
- Disable the Privacy page
- Disable the Programs page
- Disable the Security page
- Send internationalized domain names
- Turn off sending UTF-8 query strings for URLs
- Use UTF-8 for mailto links
- Corporate Settings
- Customize user agent string
- DHTML Edit Control
- Use Automatic Detection for dial-up connections
- Turn off background synchronization for feeds and Web Slices
- Prevent downloading of enclosures
- Prevent subscribing to or deleting a feed or a Web Slice
- Prevent automatic discovery of feeds and Web Slices
- Prevent access to feed list
- Turn on Basic feed authentication over HTTP
- Prevent "Fix settings" functionality
- Prevent managing the phishing filter
- Turn off Managing SmartScreen Filter for Internet Explorer 8
- Prevent managing SmartScreen Filter
- Turn off the Security Settings Check feature
- Turn on script debugging
- This policy setting allows you to turn on your script debugger, if one is installed. Website developers use script debuggers to test programs and scripts on their webpages. You can use the script debugger to browse, edit, and debug .htm and .asp files that contain Microsoft Visual Basic Scripting Edition (VBScript) or Microsoft JScript.
-
-If you enable this policy setting, script debugging is turned on. The user cannot turn off script debugging.
-
-If you disable this policy setting, script debugging is turned off. The user cannot turn on script debugging.
-
-If you do not configure this policy setting, the user can turn on or turn off script debugging.
- Position the menu bar above the navigation bar
- Prevent changing pop-up filter level
- Turn off toolbar upgrade tool
- Display error message on proxy script download failure
- Display settings
- Turn on compatibility logging
- Internet Control Panel
- URL Encoding
- Enforce full-screen mode
- Open in existing Internet Explorer window
- This policy setting prevents the text on the screen from being rendered through the ClearType technology that enhances the readability of text on LCD displays.
-
-If you enable this policy setting, applications that host MSHTML do not render text by using the Microsoft ClearType rendering engine.
-
-If you disable or do not configure this policy setting, applications that host MSHTML render text by using the Microsoft ClearType rendering engine.
- Prevents users from running the Internet Explorer Tour from the Help menu in Internet Explorer.
-
-If you enable this policy, the Tour command is removed from the Help menu.
-
-If you disable this policy or do not configure it, users can run the tour from the Help menu.
- This policy setting allows you to specify a list of web sites that will be allowed to open pop-up windows regardless of the Internet Explorer process's Pop-Up Blocker settings.
-
-If you enable this policy setting, you can enter a list of sites which will be allowed to open pop-up windows regardless of user settings. Only the domain name is allowed, so www.contoso.com is valid, but not http://www.contoso.com. Wildcards are allowed, so *.contoso.com is also valid.
-
-If you disable this or do not configure this policy setting, you will not be able to provide a default Pop-up Blocker exception list.
-
-Note: You can disable users from adding or removing websites to the exception list by enabling "Turn off Managing Pop-up Allow list" policy.
- This policy setting allows you to bypass prompting when a script that is running in any process on the computer attempts to perform a Clipboard operation (delete, copy, or paste).
-
-If you enable this policy setting, the user is not prompted when a script that is running in any process on the computer performs a Clipboard operation. This means that if the zone behavior is currently set to prompt, it will be bypassed and enabled.
-
-If you disable this policy setting, the user is prompted when a script that is running in any process on the computer attempts to perform a Clipboard operation.
-
-If you do not configure this policy setting, current values of the URL action for the application or process on the computer prevail.
- This policy setting allows you to bypass prompting when a script that is running in the Internet Explorer process attempts to perform a Clipboard operation (delete, copy, or paste) and the URL action for the zone is set to prompt.
-
-If you enable this policy setting, the user is not prompted when a script that is running in the Internet Explorer process performs a Clipboard operation. In the Internet Explorer process, if the zone behavior is currently set to prompt, it will be bypassed and enabled.
-
-If you disable this policy setting, the user is prompted when a script that is running in the Internet Explorer process attempts to perform a Clipboard operation.
-
-If you do not configure this policy setting, current values of the URL action for the Internet Explorer process prevail.
- This policy setting allows you to define applications and processes that can access the Clipboard without prompting the user.
-
-Note: Do not enter the Internet Explorer processes in this list. To enable or disable Internet Explorer processes, use the "Bypass prompting for Clipboard access for scripts running in the Internet Explorer process" policy. If the "Bypass prompting for Clipboard access for scripts running in any process" policy setting is enabled, the processes configured in this policy setting take precedence over that policy setting.
-
-If you enable this policy setting and enter a value of 1, prompts are bypassed. If you enter a value of 0, prompts are not bypassed. Value Name is the name of the executable file. If Value Name is empty or the value is not 0 or 1, the policy setting is ignored.
-
-If you enable this policy setting for an application or process in the list, a script can perform a Clipboard operation without prompting the user. This means that if the zone behavior is currently set to prompt, it will be bypassed and enabled.
-
-If you disable this policy setting for an application or process in the list, a script that is running in the application or process cannot bypass the prompt for delete, copy, or paste operations from the Clipboard.
-
-If you do not configure this policy setting, current values of the URL action for an application or process in the list prevail.
- Disable Import/Export Settings wizard
- Turn off browser geolocation
- Turn off Adobe Flash in Internet Explorer and prevent applications from using Internet Explorer technology to instantiate Flash objects
- File menu: Disable closing the browser and Explorer windows
- File menu: Disable Save As... menu option
- File menu: Disable Save As Web Page Complete
- File menu: Disable New menu option
- File menu: Disable Open menu option
- Shockwave Flash
- Smallest
- Smaller
- Medium
- Larger
- Largest
- Prevent choosing default text size
- This policy setting prevents the user from choosing the default text size in Internet Explorer.
-
-If you enable this policy setting, the user cannot choose the default text size in Internet Explorer. You must specify the default text size:
- • Largest
- • Larger
- • Medium
- • Smaller
- • Smallest
-
-If you disable or do not configure this policy setting, the user can choose the default text size in Internet Explorer.
- Force pop-ups to open in a new tab
- Force pop-ups to open in a new window
- Foreground
- Turn off details in messages about Internet connection problems
- This policy setting specifies whether, when there is a problem connecting with an Internet server, to provide a detailed description with hints about how to correct the problem. If you clear this check box, the user sees only the error code and the name of the error.
-
-If you enable this policy setting, when there is a problem connecting with an Internet server, the user does not see a detailed description or hints about how to correct the problem. The user cannot change this policy setting.
-
-If you disable this policy setting, when there is a problem connecting with an Internet server, the user sees a detailed description with hints about how to correct the problem. The user cannot change this policy setting.
-
-If you do not configure this policy setting, the user can turn on or turn off details in these error messages.
- Turn off page-zooming functionality
- General Colors
- Help menu: Remove 'Send Feedback' menu option
- Help menu: Remove 'For Netscape Users' menu option
- Help menu: Remove 'Tip of the Day' menu option
- Help menu: Remove 'Tour' menu option
- Help Menu > About Internet Explorer
- Prevent specifying cipher strength update information URLs
- This policy setting prevents the user from specifying a URL that contains update information about cipher strength. When the user logs on to a secure page, the page cannot grant access unless the Internet browser connects with a prespecified encryption. To ensure that the browser meets this requirement, this policy setting allows you to specify the URL to update the browser security setting.
-
-If you enable this policy setting, the user cannot specify the cipher strength update information URL. You must specify the cipher strength update information URL.
-
-If you disable or do not configure this policy setting, the user can specify the cipher strength update information URL.
- Hover
- Start the Internet Connection Wizard automatically
- This policy setting determines whether the Internet Connection Wizard was completed. If the Internet Connection Wizard was not completed, this policy setting starts the wizard automatically.
-
-If you enable this policy setting, the Internet Connection Wizard starts automatically if it was not completed before. The user cannot prevent the wizard from starting.
-
-If you disable this policy setting, the Internet Connection Wizard does not start automatically. The user can start the wizard manually.
-
-If you do not configure this policy setting, the user can decide whether the Internet Connection Wizard should start automatically.
- Internet Connection Wizard Settings
- Identity Manager: Prevent users from using Identities
- Always convert to IDN format
- Convert Intranet addresses to IDN format
- Never convert to IDN format
- Convert non-Intranet addresses to IDN format
- This policy setting allows you to customize the Internet Explorer version string as reported to web servers in the HTTP User Agent header.
-
-If you enable this policy setting, Internet Explorer sends the specified custom string in the version portion of the User Agent header.
-
-If you disable or do not configure this policy setting, Internet Explorer sends the current Internet Explorer version in the User Agent header (for example, "MSIE 7.0").
- This policy setting controls whether to have background synchronization for feeds and Web Slices.
-
-If you enable this policy setting, the ability to synchronize feeds and Web Slices in the background is turned off.
-
-If you disable or do not configure this policy setting, the user can synchronize feeds and Web Slices in the background.
- This policy setting prevents the user from having enclosures (file attachments) downloaded from a feed to the user's computer.
-
-If you enable this policy setting, the user cannot set the Feed Sync Engine to download an enclosure through the Feed property page. A developer cannot change the download setting through the Feed APIs.
-
-If you disable or do not configure this policy setting, the user can set the Feed Sync Engine to download an enclosure through the Feed property page. A developer can change the download setting through the Feed APIs.
- This policy setting prevents the user from subscribing to or deleting a feed or a Web Slice.
-
-If you enable this policy setting, the menu command to subscribe to a feed and the menu command to delete a feed are disabled, and access to Web Slices is turned off. A developer cannot add a feed or Web Slice or delete a feed or Web Slice by using the Feed APIs. A developer also cannot create or delete folders.
-
-If you disable or do not configure this policy setting, the user can subscribe to a feed or Web Slice through the Subscribe button in Internet Explorer and delete a feed or Web Slice through the feed list control. A developer can add or delete a feed or Web Slice by using the Feed APIs.
- This policy setting prevents users from having Internet Explorer automatically discover whether a feed or Web Slice is available for an associated webpage.
-
-If you enable this policy setting, the user does not receive a notification on the toolbar that a feed or Web Slice is available.
-
-If you disable or do not configure this policy setting, the user receives a notification when a feed or Web Slice is available and can click the feed discovery button.
- This policy setting prevents the user from using Internet Explorer as a feed reader. This policy setting has no impact on the Windows RSS Platform.
-
-If you enable this policy setting, the user cannot access the feed list in the Favorites Center.
-
-If you disable or do not configure this policy setting, the user can access the feed list in the Favorites Center.
- This policy setting allows users to have their feeds authenticated through the Basic authentication scheme over an unencrypted HTTP connection.
-
-If you enable this policy setting, the Windows RSS Platform authenticates feeds to servers by using the Basic authentication scheme in combination with a less secure HTTP connection.
-
-If you disable or do not configure this policy setting, the Windows RSS Platform does not authenticate feeds to servers by using the Basic authentication scheme in combination with a less secure HTTP connection.
-
-A developer cannot change this policy setting through the Feed APIs.
- This policy setting prevents the user from using the "Fix settings" functionality related to Security Settings Check.
-
-If you enable this policy setting, the user cannot use the "Fix settings" functionality.
-
-If you disable or do not configure this policy setting, the user can use the "Fix settings" functionality.
-
-Note: When this policy setting is enabled, the "Fix settings" command on the Notification bar shortcut menu should be disabled.
- This policy setting positions the menu bar above the navigation bar. The navigation bar contains icons for a variety of features, including browsing web pages, searching the web by using a selection of search tools, accessing and managing favorites, viewing a history of visited pages, printing, and accessing email and newsgroups. The menu bar contains menus that open lists of commands. The commands include options for printing, customizing Internet Explorer, copying and pasting text, managing favorites, and accessing Help.
-
-If you enable this policy setting, the menu bar is above the navigation bar. The user cannot interchange the positions of the menu bar and the navigation bar.
-
-If you disable this policy setting, the menu bar is below the navigation bar. The user cannot interchange the positions of the menu bar and the navigation bar.
-
-If you do not configure this policy setting, the user can interchange the positions of the menu bar and the navigation bar.
- This policy setting prevents the user from managing a filter that warns the user if the website being visited is known for fraudulent attempts to gather personal information through "phishing."
-
-If you enable this policy setting, the user is not prompted to enable the phishing filter. You must specify which mode the phishing filter uses: manual, automatic, or off.
-
-If you select manual mode, the phishing filter performs only local analysis, and the user is prompted to permit any data to be sent to Microsoft. If the feature is fully enabled, all website addresses that are not on the filter's allow list are sent automatically to Microsoft without prompting the user.
-
-If you disable or do not configure this policy setting, the user is prompted to decide the mode of operation for the phishing filter.
- This policy setting allows the user to enable the SmartScreen Filter, which warns the user if the website being visited is known for fraudulent attempts to gather personal information through "phishing," or is known to host malware.
-
-If you enable this policy setting, the user is not prompted to turn on SmartScreen Filter. You must specify which mode the SmartScreen Filter uses: on, or off.All website addresses that are not on the filter's allow list are sent automatically to Microsoft without prompting the user.
-
-If you disable or do not configure this policy setting, the user is prompted to decide whether to turn on the SmartScreen Filter during the first-run experience.
- This policy setting prevents the user from managing SmartScreen Filter, which warns the user if the website being visited is known for fraudulent attempts to gather personal information through "phishing," or is known to host malware.
-
-If you enable this policy setting, the user is not prompted to turn on SmartScreen Filter. All website addresses that are not on the filter's allow list are sent automatically to Microsoft without prompting the user.
-
-If you disable or do not configure this policy setting, the user is prompted to decide whether to turn on SmartScreen Filter during the first-run experience.
- This policy setting turns off the Security Settings Check feature, which checks Internet Explorer security settings to determine when the settings put Internet Explorer at risk.
-
-If you enable this policy setting, the feature is turned off.
-
-If you disable or do not configure this policy setting, the feature is turned on.
- This policy setting logs information that is blocked by new features in Internet Explorer. The logged compatibility information is displayed in the Windows Event Viewer.
-
-If you enable this policy setting, the user can log information that is blocked by new Internet Explorer features. The user cannot turn off logging.
-
-If you disable this policy setting, the user cannot log information that is blocked by new Internet Explorer features. The user cannot turn on logging.
-
-If you do not configure this policy setting, the user can change the logging settings.
- This policy setting allows you to enforce full-screen mode, which disables the navigation bar, the menu bar, and the Command bar. Starting with Windows 8, this policy only applies to Internet Explorer on the desktop.
-
-The navigation bar includes features for browsing webpages, searching the web by using a selection of search tools, viewing a history of visited pages, printing, and accessing email and newsgroups. The menu bar contains menus that open lists of commands for printing, customizing Internet Explorer, copying and pasting text, managing favorites, and accessing Help. The Command bar enables the user to access and manage favorites, feeds, shortcuts to home page, and more. Full-screen mode disables not only these three bars, but also the shortcuts to these bars.
-
-If you enable this policy setting, the navigation bar, the menu bar, and the Command bar are not visible, and the user cannot access them.
-
-If you disable or do not configure this policy setting, the user can view and access the navigation bar, the menu bar, and the Command bar.
- This policy setting allows you to configure whether newly installed add-ons are automatically activated in the Internet Explorer 9 browser. Any add-ons that were activated in a previous version of Internet Explorer are considered to be the same as newly installed add-ons and are not activated when the user upgrades to Internet Explorer 9.
-
-In Internet Explorer 9, add-ons are defined as toolbars, Browser Helper Objects, or Explorer bars. ActiveX controls are referred to as plug-ins and are not part of this definition.
-
-If you enable this policy setting, newly installed add-ons are automatically activated in the browser.
-
-If you disable or do not configure this policy setting, newly installed add-ons are not automatically activated in the browser. Internet Explorer notifies the user when newly installed add-ons are ready for use. The user must choose to activate them by responding to the notification, using Manage Add-ons, or using other methods.
- This policy setting prevents Internet Explorer from displaying a notification when the average time to load all the user's enabled add-ons exceeds the threshold. The notification informs the user that add-ons are slowing his or her browsing and displays a button that opens the Disable Add-ons dialog box. The Disable Add-ons dialog box displays the load time for each group of add-ons enabled in the browser. It allows the user to disable add-ons and configure the threshold.
-
-If you enable this policy setting, users are not notified when the average time to load all the user's enabled add-ons exceeds the threshold.
-
-If you disable or do not configure this policy setting, users are notified when the average time to load all the user's enabled add-ons exceeds the threshold. This is the default.
- Designates the Microsoft Agent ActiveX control as administrator-approved.
-
-Microsoft Agent is a set of software services that supports the presentation of software agents as interactive personalities within the Microsoft Windows interface.
-
-If you enable this policy, this control can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, these controls will not be designated as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- This policy setting controls the ActiveX Filtering feature for websites that are running ActiveX controls. The user can choose to turn off ActiveX Filtering for specific websites so that ActiveX controls can run properly.
-
-If you enable this policy setting, ActiveX Filtering is enabled by default for the user. The user cannot turn off ActiveX Filtering, although they may add per-site exceptions.
-
-If you disable or do not configure this policy setting, ActiveX Filtering is not enabled by default for the user. The user can turn ActiveX Filtering on or off.
- This policy setting allows you to manage a list of add-ons to be allowed or denied by Internet Explorer. Add-ons in this case are controls like ActiveX Controls, Toolbars, and Browser Helper Objects (BHOs) which are specifically written to extend or enhance the functionality of the browser or web pages.
-
-This list can be used with the 'Deny all add-ons unless specifically allowed in the Add-on List' policy setting, which defines whether add-ons not listed here are assumed to be denied.
-
-If you enable this policy setting, you can enter a list of add-ons to be allowed or denied by Internet Explorer. For each entry that you add to the list, enter the following information:
-
-Name of the Value - the CLSID (class identifier) for the add-on you wish to add to the list. The CLSID should be in brackets for example, ‘{000000000-0000-0000-0000-0000000000000}'. The CLSID for an add-on can be obtained by reading the OBJECT tag from a Web page on which the add-on is referenced.
-
-Value - A number indicating whether Internet Explorer should deny or allow the add-on to be loaded. To specify that an add-on should be denied enter a 0 (zero) into this field. To specify that an add-on should be allowed, enter a 1 (one) into this field. To specify that an add-on should be allowed and also permit the user to manage the add-on through Add-on Manager, enter a 2 (two) into this field.
-
-If you disable this policy setting, the list is deleted. The 'Deny all add-ons unless specifically allowed in the Add-on List' policy setting will still determine whether add-ons not in this list are assumed to be denied.
- This policy setting allows you to ensure that any Internet Explorer add-ons not listed in the 'Add-on List' policy setting are denied. Add-ons in this case are controls like ActiveX Controls, Toolbars, and Browser Helper Objects (BHOs) which are specifically written to extend or enhance the functionality of the browser or web pages.
-
-By default, the 'Add-on List' policy setting defines a list of add-ons to be allowed or denied through Group Policy. However, users can still use the Add-on Manager within Internet Explorer to manage add-ons not listed within the 'Add-on List' policy setting. This policy setting effectively removes this option from users - all add-ons are assumed to be denied unless they are specifically allowed through the 'Add-on List' policy setting.
-
-If you enable this policy setting, Internet Explorer only allows add-ons that are specifically listed (and allowed) through the 'Add-on List' policy setting.
-
-If you disable or do not configure this policy setting, users may use Add-on Manager to allow or deny any add-ons that are not included in the 'Add-on List' policy setting.
-
-Note: If an add-on is listed in the 'Add-on List' policy setting, the user cannot change its state through Add-on Manager (unless its value has been set to allow user management - see the 'Add-on List' policy for more details).
- This policy setting allows you to manage the crash detection feature of add-on Management.
-
-If you enable this policy setting, a crash in Internet Explorer will exhibit behavior found in Windows XP Professional Service Pack 1 and earlier, namely to invoke Windows Error Reporting. All policy settings for Windows Error Reporting continue to apply.
-
-If you disable or do not configure this policy setting, the crash detection feature for add-on management will be functional.
- This policy setting allows you to manage whether users have the ability to allow or deny add-ons through Add-On Manager.
-
-If you enable this policy setting, users cannot enable or disable add-ons through Add-On Manager.
-
-If you disable or do not configure this policy setting, the appropriate controls in the Add-On Manager will be available to the user.
- This policy setting allows you to add a specific list of search providers to the user's default list of search providers. Normally, search providers can be added from third-party toolbars or in Setup. The user can also add a search provider from the provider's website.
-
-If you enable this policy setting, the user can add and remove search providers, but only from the set of search providers specified in the list of policy keys for search providers (found under [HKCU or HKLM\Software\policies\Microsoft\Internet Explorer\SearchScopes]). Note: This list can be created from a custom administrative template file. For information about creating this custom administrative template file, see the Internet Explorer documentation on search providers.
-
-If you disable or do not configure this policy setting, the user can configure their list of search providers unless another policy setting restricts such configuration.
- Contains settings to enable or disable ActiveX controls.
- This policy setting allows you to turn on or turn off the earlier menus (for example, File, Edit, and View) in Internet Explorer.
-
-If you enable this policy setting, the menu bar appears in Internet Explorer by default, and the user cannot turn it off.
-
-If you disable this policy setting, the menu bar appears in Internet Explorer by default, and the user cannot turn it on.
-
-If you do not configure this policy setting, the menu bar is turned off by default. The user can turn on or turn off the menu bar.
- Designates the Audio/Video Player ActiveX control as administrator-approved.
-
-This control is used for playing sounds, videos, and other media.
-
-If you enable this policy, this control can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, this control will not be designated as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- Prevents automatic proxy scripts, which interact with a server to automatically configure users' proxy settings, from being stored in the users' cache.
-
-If you enable this policy, automatic proxy scripts will not be stored temporarily on the users' computer.
-
-If you disable this policy or do not configure it, automatic proxy scripts can be stored in the users' cache.
- Prevents branding of Internet programs, such as customization of Internet Explorer and Outlook Express logos and title bars, by another party.
-
-If you enable this policy, it prevents customization of the browser by another party, such as an Internet service provider or Internet content provider.
-
-If you disable this policy or do not configure it, users could install customizations from another party-for example, when signing up for Internet services.
-
-This policy is intended for administrators who want to maintain a consistent browser across an organization.
- Designates the Microsoft Network (MSN) Carpoint automatic pricing control as administrator-approved.
-
-This control enables enhanced pricing functionality on the Carpoint Web site, where users can shop for and obtain information about vehicles.
-
-If you enable this policy, this control can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, this control will not be designated as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- Contains settings to configure Internet Explorer
- Contains settings for Offline pages and channels.
- Prevents users from changing settings on the Advanced tab in the Internet Options dialog box.
-
-If you enable this policy, users are prevented from changing advanced Internet settings, such as security, multimedia, and printing. Users cannot select or clear the check boxes on the Advanced tab.
-
-If you disable this policy or do not configure it, users can select or clear settings on the Advanced tab.
-
-If you set the "Disable the Advanced page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), you do not need to set this policy, because the "Disable the Advanced page" policy removes the Advanced tab from the interface.
- Removes the Advanced tab from the interface in the Internet Options dialog box.
-
-If you enable this policy, users are prevented from seeing and changing advanced Internet settings, such as security, multimedia, and printing.
-
-If you disable this policy or do not configure it, users can see and change these settings.
-
-When you set this policy, you do not need to set the "Disable changing Advanced page settings" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\), because this policy removes the Advanced tab from the interface.
- Removes the Connections tab from the interface in the Internet Options dialog box.
-
-If you enable this policy, users are prevented from seeing and changing connection and proxy settings.
-
-If you disable this policy or do not configure it, users can see and change these settings.
-
-When you set this policy, you do not need to set the following policies for the Content tab, because this policy removes the Connections tab from the interface:
-
-"Disable Internet Connection Wizard"
-
-"Disable changing connection settings"
-
-"Prevent changing proxy settings"
-
-"Disable changing Automatic Configuration settings"
- If you enable this policy setting, users are prevented from seeing and changing ratings, certificates, AutoComplete, Wallet, and Profile Assistant settings.
-
-If you disable this policy or do not configure it, users can see and change these settings.
- Removes the General tab from the interface in the Internet Options dialog box.
-
-If you enable this policy, users are unable to see and change settings for the home page, the cache, history, Web page appearance, and accessibility.
-
-If you disable this policy or do not configure it, users can see and change these settings.
-
-When you set this policy, you do not need to set the following Internet Explorer policies (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\), because this policy removes the General tab from the interface:
-
-"Disable changing home page settings"
-
-"Disable changing Temporary Internet files settings"
-
-"Disable changing history settings"
-
-"Disable changing color settings"
-
-"Disable changing link color settings"
-
-"Disable changing font settings"
-
-"Disable changing language settings"
-
-"Disable changing accessibility settings"
- Removes the Privacy tab from the interface in the Internet Options dialog box.
-
-If you enable this policy, users are prevented from seeing and changing default settings for privacy.
-
-If you disable this policy or do not configure it, users can see and change these settings.
- Removes the Programs tab from the interface in the Internet Options dialog box.
-
-If you enable this policy, users are prevented from seeing and changing default settings for Internet programs.
-
-If you disable this policy or do not configure it, users can see and change these settings.
-
-When you set this policy, you do not need to set the following policies for the Programs tab, because this policy removes the Programs tab from the interface:
-
-"Disable changing Messaging settings"
-
-"Disable changing Calendar and Contact settings"
-
-"Disable the Reset Web Settings feature"
-
-"Disable changing default browser check"
- Removes the Security tab from the interface in the Internet Options dialog box.
-
-If you enable this policy, it prevents users from seeing and changing settings for security zones, such as scripting, downloads, and user authentication.
-
-If you disable this policy or do not configure it, users can see and change these settings.
-
-When you set this policy, you do not need to set the following Internet Explorer policies, because this policy removes the Security tab from the interface:
-
-"Security zones: Do not allow users to change policies"
-
-"Security zones: Do not allow users to add/delete sites"
- This policy setting allows you to manage whether Internet Explorer converts Unicode domain names to internationalized domain name (IDN) format (Punycode) before sending them to Domain Name System (DNS) servers or to proxy servers.
-
-If you enable this policy setting, you must specify when IDN server names should be sent:
- 0) Unicode domain names are never converted to IDN format.
- 1) Unicode domain names are converted to IDN format only for addresses that are not in the Intranet zone.
- 2) Unicode domain names are converted to IDN format only for addresses that are in the Intranet zone.
- 3) Unicode domain names are always converted to IDN format.
-
-If you disable or do not configure this policy setting, the user can control this setting by using Advanced Options in Internet Control Panel. By default, domain names are converted to IDN format only for addresses that are not in the Intranet zone.
- This policy setting determines whether Internet Explorer uses 8-bit Unicode Transformation Format (UTF-8) to encode query strings in URLs before sending them to servers or to proxy servers.
-
-If you enable this policy setting, you must specify when to use UTF-8 to encode query strings:
- 0) Never encode query strings.
- 1) Only encode query strings for URLs that aren't in the Intranet zone.
- 2) Only encode query strings for URLs that are in the Intranet zone.
- 3) Always encode query strings.
-
-If you disable or don't configure this policy setting, users can turn this behavior on or off, using Internet Explorer Advanced Options settings. The default is to encode all query strings in UTF-8.
- This policy setting allows you to manage whether Internet Explorer uses 8-bit Unicode Transformation Format (UTF-8) for mailto links.
-
-If you enable this policy setting, Internet Explorer encodes mailto links in UTF-8.
-
-If you disable or do not configure this policy setting, Internet Explorer sends mailto links encoded through the user's code page. This behavior matches the behavior of Internet Explorer 6 and earlier. The user can change this behavior on the Internet Explorer Tools menu: Click Internet Options, click the Advanced tab, and then under International, select the "Use UTF-8 for mailto links" check box.
- This ActiveX control enables users to edit HTML text and see a faithful rendition of how the text would look in the browser. There are two versions of the control: a more powerful version that cannot be invoked by a web site because it includes file access and other features, and a "safe for scripting" version that has restricted functionality and is intended for use by web sites.
-
-If you enable this policy, this control will be available as an administrator approved control and can be run if the user specifies to run administrator-approved Active-X controls and plug-ins under security zones.
-
-If you disable this policy or do not configure it, this control will not be designated as administrator-approved.
- Specifies that Automatic Detection will be used to configure dial-up settings for users.
-
-Automatic Detection uses a DHCP (Dynamic Host Configuration Protocol) or DNS server to customize the browser the first time it is started.
-
-If you enable this policy, users' dial-up settings will be configured by Automatic Detection.
-
-If you disable this policy or do not configure it, dial-up settings will not be configured by Automatic Detection, unless specified by the user.
- This policy setting prevents the user from changing the level of pop-up filtering. The available levels are as follows:
- High: Block all pop-ups.
- Medium: Block most automatic pop-ups.
- Low: Allow pop-ups from secure sites.
-
-If you enable this policy setting, the user cannot change the filter level. You can specify the filter level by importing Privacy settings from your computer under Internet Explorer Maintenance.
-
-If you disable or do not configure this policy setting, the user can manage pop-ups by changing the filter level.
-
-You may also want to enable the "Prevent managing pop-up exception list" and "Turn off pop-up management" policy settings to prevent the user from configuring pop-up behavior.
- This policy setting allows you to turn off the toolbar upgrade tool. The toolbar upgrade tool determines whether incompatible toolbars or Browser Helper Objects are installed when Internet Explorer starts. If the tool detects an incompatible toolbar, the user is prompted to update or disable the toolbar. Specific toolbars or Browser Helper Objects that are enabled or disabled via policy settings do not undergo this check.
-
-If you enable this policy setting, the toolbar upgrade tool does not check for incompatible toolbars. The user is not prompted, and incompatible toolbars run unless previously disabled through policy settings or user choice.
-
-If you disable or do not configure this policy setting, the toolbar upgrade tool checks for incompatible toolbars. The user can enable or disable incompatible toolbars. Toolbars that are enabled or disabled via policy settings do not undergo these checks.
- Specifies that error messages will be displayed to users if problems occur with proxy scripts.
-
-If you enable this policy, error messages will be displayed when the browser does not download or run a script to set proxy settings.
-
-If you disable this policy or do not configure it, error messages will not be displayed when problems occur with proxy scripts.
- Contains settings that control features found in the Internet Options dialog.
- This policy settings disables the Import/Export Settings wizard. This wizard allows you to import settings from another browser, import settings from a file, or export settings to a file. Importing settings from another browser allows the user to import favorites and feeds from other browsers. Importing settings from a file allows the user to import favorites, feeds and cookies from a file. Exporting settings to a file allows the user to export favorites, feeds and cookies to a file.
-
-If you enable this policy setting, the user will not be able to use the Import/Export Settings wizard.
-
-If you disable or do not configure this policy setting, the user will be able to use the Import/Export Settings wizard.
- This policy setting allows you to disable browser geolocation support. This will prevent websites from requesting location data about the user.
-
-If you enable this policy setting, browser geolocation support is turned off.
-
-If you disable this policy setting, browser geolocation support is turned on.
-
-If you do not configure this policy setting, browser geolocation support can be turned on or off in Internet Options on the Privacy tab.
- This policy setting turns off Adobe Flash in Internet Explorer and prevents applications from using Internet Explorer technology to instantiate Flash objects.
-
-If you enable this policy setting, Flash is turned off for Internet Explorer, and applications cannot use Internet Explorer technology to instantiate Flash objects. In the Manage Add-ons dialog box, the Flash status will be 'Disabled', and users cannot enable Flash. If you enable this policy setting, Internet Explorer will ignore settings made for Adobe Flash through the "Add-on List" and "Deny all add-ons unless specifically allowed in the Add-on List" policy settings.
-
-If you disable, or do not configure this policy setting, Flash is turned on for Internet Explorer, and applications can use Internet Explorer technology to instantiate Flash objects. Users can enable or disable Flash in the Manage Add-ons dialog box.
-
-Note that Adobe Flash can still be disabled through the "Add-on List" and "Deny all add-ons unless specifically allowed in the Add-on List" policy settings, even if this policy setting is disabled, or not configured. However, if Adobe Flash is disabled through the "Add-on List" and "Deny all add-ons unless specifically allowed in the Add-on List" policy settings and not through this policy setting, all applications that use Internet Explorer technology to instantiate Flash object can still do so. For more information, see "Group Policy Settings in Internet Explorer 10" in the Internet Explorer TechNet library.
- Prevents users from closing Microsoft Internet Explorer and File Explorer.
-
-If you enable this policy, the Close command on the File menu will appear dimmed.
-
-If you disable this policy or do not configure it, users are not prevented from closing the browser or File Explorer.
-
-Note: The Close button in the top right corner of the program will not work; if users click the Close button, they will be informed that the command is not available.
- Prevents users from saving Web pages from the browser File menu to their hard disk or to a network share.
-
-If you enable this policy, the Save As command on the File menu will be removed.
-
-If you disable this policy or do not configure it, users can save Web pages for later viewing.
-
-This policy takes precedence over the "File Menu: Disable Save As Web Page Complete" policy, which prevents users from saving the entire contents that are displayed or run from a Web Page, such as graphics, scripts, and linked files, but does not prevent users from saving the text of a Web page.
-
-Caution: If you enable this policy, users are not prevented from saving Web content by pointing to a link on a Web page, clicking the right mouse button, and then clicking Save Target As.
- Prevents users from saving the complete contents that are displayed on or run from a Web page, including the graphics, scripts, linked files, and other elements. It does not prevent users from saving the text of a Web page.
-
-If you enable this policy, the Web Page, Complete file type option will be removed from the Save as Type box in the Save Web Page dialog box. Users can still save Web pages as hypertext markup language (HTML) files or as text files, but graphics, scripts, and other elements are not saved. To display the Save Web Page dialog box, users click the File menu, and then click the Save As command.
-
-If you disable this policy or do not configure it, users can save all elements on a Web page.
-
-The "File menu: Disable Save As... menu option" policy, which removes the Save As command, takes precedence over this policy. If it is enabled, this policy is ignored.
- Prevents users from opening a new browser window from the File menu.
-
-If this policy is enabled, users cannot open a new browser window by clicking the File menu, pointing to the New menu, and then clicking Window. The user interface is not changed, but a new window will not be opened, and users will be informed that the command is not available.
-
-If you disable this policy or do not configure it, users can open a new browser window from the File menu.
-
-Caution: This policy does not prevent users from opening a new browser window by right-clicking, and then clicking the Open in New Window command. To prevent users from using the shortcut menu to open new browser windows, you should also set the "Disable Open in New Window menu option" policy, which disables this command on the shortcut menu, or the "Turn off Shortcut Menu" policy, which disables the entire shortcut menu.
-
-Note: the user will still be able to open New Tabs.
- Prevents users from opening a file or Web page from the File menu in Internet Explorer.
-
-If you enable this policy, the Open dialog box will not appear when users click the Open command on the File menu. If users click the Open command, they will be notified that the command is not available.
-
-If you disable this policy or do not configure it, users can open a Web page from the browser File menu.
-
-Caution: This policy does not prevent users from right-clicking a link on a Web page, and then clicking the Open or Open in New Window command. To prevent users from opening Web pages by using the shortcut menu, set the "Disable Open in New Window menu option" policy, which disables this command on the shortcut menu, or the "Turn off Shortcut Menu" policy, which disables the entire shortcut menu.
- Designates Shockwave flash as an administrator approved control.
-
-If you enable this policy, this control can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, this control will not be designated as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- This policy setting prevents the user from zooming in to or out of a page to better see the content.
-
-If you enable this policy setting, applications that host MSHTML do not respond to user input that causes the content to be re-rendered at a scaled size.
-
-If you disable or do not configure this policy setting, applications that host MSHTML respond to user input that causes the content to be re-rendered at a scaled size.
- Prevents users from sending feedback to Microsoft by clicking the Send Feedback command on the Help menu.
-
-If you enable this policy, the Send Feedback command is removed from the Help menu.
-
-If you disable this policy or do not configure it, users can fill out an Internet form to provide feedback about Microsoft products.
- Prevents users from displaying tips for users who are switching from Netscape.
-
-If you enable this policy, the For Netscape Users command is removed from the Help menu.
-
-If you disable this policy or do not configure it, users can display content about switching from Netscape by clicking the For Netscape Users command on the Help menu.
-
-Caution: Enabling this policy does not remove the tips for Netscape users from the Microsoft Internet Explorer Help file.
- Prevents users from viewing or changing the Tip of the Day interface in Microsoft Internet Explorer.
-
-If you enable this policy, the Tip of the Day command is removed from the Help menu.
-
-If you disable this policy or do not configure it, users can enable or disable the Tip of the Day, which appears at the bottom of the browser.
- Prevents users from configuring unique identities by using Identity Manager.
-
-Identity Manager enables users to create multiple accounts, such as e-mail accounts, on the same computer. Each user has a unique identity, with a different password and different program preferences.
-
-If you enable this policy, users will not be able to create new identities, manage existing identities, or switch identities. The Switch Identity option will be removed from the File menu in Address Book.
-
-If you disable this policy or do not configure it, users can set up and change identities.
- Designates a set of Microsoft Network (MSN) Investor controls as administrator-approved.
-
-These controls enable users to view updated lists of stocks on their Web pages.
-
-If you enable this policy, these controls can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, these controls will not be designated as administrator-approved.
-
-Select the check boxes for the controls that you want to designate as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- Restricts the amount of information downloaded for offline viewing.
-
-If you enable this policy, you can set limits to the size and number of pages that users can download. If users attempt to exceed the number of subscriptions, a prompt will appear that states that they cannot set up more Web sites for offline viewing.
-
-If you disable this policy or do not configure it, then users can determine the amount of content that is searched for new information and downloaded.
-
-Caution: Although the Maximum Number of Offline Pages option determines how many levels of a Web site are searched for new information, it does not change the user interface in the Offline Favorites wizard.
-
-Note: The begin and end times for downloading are measured in minutes after midnight. The Maximum Offline Page Crawl Depth setting specifies how many levels of a Web site are searched for new information.
- Allows Administrators to enable and disable the Media Explorer Bar and set the auto-play default.
-
-The Media Explorer Bar plays music and video content from the Internet.
-
-If you disable the Media explorer bar, users cannot display the Media Explorer Bar. The auto-play feature is also disabled. When users click on a link within Internet Explorer, the content will be played by the default media client on their system.
-
-If you enable the Media Explorer Bar or do not configure it, users can show and hide the Media Explorer Bar.
-
-Administrators also have the ability to turn the auto-play feature on or off. This setting only applies if the Media Explorer Bar is enabled.
-
-If checked, the Media Explorer Bar will automatically display and play the media content when the user clicks on a media link.
-
-If unchecked, the content will be played by the default media client on their system.
- Designates a set of Microsoft ActiveX controls used to manipulate pop-up menus in the browser as administrator-approved.
-
-If you enable this policy, these controls can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, these controls will not be designated as administrator-approved.
-
-To specify a control as administrator-approved, click Enabled, and then select the check box for the control:
-
--- MCSiMenu - enables Web authors to control the placement and appearance of Windows pop-up menus on Web pages
--- Popup Menu Object - enables Web authors to add pop-up menus to Web pages
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- Contains settings for showing or hiding menus and menu options in Internet Explorer.
- Designates the Microsoft Chat ActiveX control as administrator-approved.
-
-This control is used by Web authors to build text-based and graphical-based Chat communities for real-time conversations on the Web.
-
-If you enable this policy, this control can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, this control will not be designated as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- Designates a set of MSNBC controls as administrator-approved.
-
-These controls enable enhanced browsing of news reports on the MSNBC Web site.
-
-If you enable this policy, these controls can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, these controls will not be designated as administrator-approved.
-
-Select the check boxes for the controls that you want to designate as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- Designates NetShow File Transfer Control as an administrator approved control.
-
-If you enable this policy, this control can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, this control will not be designated as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- Prevents users from adding channels to Internet Explorer.
-
-Channels are Web sites that are updated automatically on your computer, according to a schedule specified by the channel provider.
-
-If you enable this policy, the Add Active Channel button, which appears on a channel that users haven't yet subscribed to, will be disabled. Users also cannot add content that is based on a channel, such as some of the Active Desktop items from Microsoft's Active Desktop Gallery, to their desktop.
-
-If you disable this policy or do not configure it, users can add channels to the Channel bar or to their desktop.
-
-Note: Most channel providers use the words Add Active Channel for this option; however, a few use different words, such as Subscribe.
- Prevents users from specifying that Web pages can be downloaded for viewing offline. When users make Web pages available for offline viewing, they can view the content when their computer is not connected to the Internet.
-
-If you enable this policy, users cannot add new schedules for downloading offline content. The Make Available Offline check box will be dimmed in the Add Favorite dialog box.
-
-If you disable this policy or do not configure it, users can add new offline content schedules.
-
-This policy is intended for organizations that are concerned about server load for downloading content.
-
-The "Hide Favorites menu" policy (located in User Configuration\Administrative Templates\Windows Components\Internet Explorer) takes precedence over this policy. If it is enabled, this policy is ignored.
- Prevents users from determining which toolbars are displayed in Microsoft Internet Explorer and File Explorer.
-
-If you enable this policy, the list of toolbars, which users can display by clicking the View menu and then pointing to the Toolbars command, will appear dimmed.
-
-If you disable this policy or do not configure it, users can determine which toolbars are displayed in File Explorer and Internet Explorer.
-
-This policy can be used in coordination with the "Disable customizing browser toolbar buttons" policy, which prevents users from adding or removing toolbars from Internet Explorer.
- This policy setting prevents the shortcut menu from appearing when a user right-clicks a webpage while using Internet Explorer. Starting with Windows 8, this policy setting only applies to Internet Explorer on the desktop.
-
-If you enable this policy setting, the shortcut menu will not appear when a user right-clicks a webpage.
-
-If you disable or do not configure this policy setting, users can use the shortcut menu.
- This policy setting prevents the user from ignoring Secure Sockets Layer/Transport Layer Security (SSL/TLS) certificate errors that interrupt browsing (such as "expired", "revoked", or "name mismatch" errors) in Internet Explorer.
-
-If you enable this policy setting, the user cannot continue browsing.
-
-If you disable or do not configure this policy setting, the user can choose to ignore certificate errors and continue browsing.
- Prevents channel providers from recording information about when their channel pages are viewed by users who are working offline.
-
-If you enable this policy, it disables any channel logging settings set by channel providers in the channel definition format (.cdf) file. The .cdf file determines the schedule and other settings for downloading Web content.
-
-If you disable this policy or do not configure it, channel providers can record information about when their channel pages are viewed by users who are working offline.
- Prevents users from viewing the Channel bar interface. Channels are Web sites that are automatically updated on their computer according to a schedule specified by the channel provider.
-
-If you enable this policy, the Channel bar interface will be disabled, and users cannot select the Internet Explorer Channel Bar check box on the Web tab in the Display Properties dialog box.
-
-If you disable this policy or do not configure it, users can view and subscribe to channels from the Channel bar interface.
- This policy setting prevents the user from performing actions which will delete browsing history. For more information on browsing history Group Policy settings, see "Group Policies Settings in Internet Explorer 10" in the TechNet technical library.
-
-If you enable this policy setting, the user cannot access the Delete Browsing History dialog box. Starting with Windows 8, users cannot click the Delete Browsing History button on the Settings charm.
-
-If you disable or do not configure this policy setting, the user can access the Delete Browsing History dialog box. Starting with Windows 8, users can click the Delete Browsing History button on the Settings charm.
- This policy setting prevents the user from deleting form data. This feature is available in the Delete Browsing History dialog box.
-
-If you enable this policy setting, form data is preserved when the user clicks Delete.
-
-If you disable this policy setting, form data is deleted when the user clicks Delete.
-
-If you do not configure this policy setting, the user can choose whether to delete or preserve form data when he or she clicks Delete.
-
-If the "Prevent access to Delete Browsing History" policy setting is enabled, this policy setting is enabled by default.
- This policy setting prevents users from deleting passwords. This feature is available in the Delete Browsing History dialog box.
-
-If you enable this policy setting, passwords are preserved when the user clicks Delete.
-
-If you disable this policy setting, passwords are deleted when the user clicks Delete.
-
-If you do not configure this policy setting, the user can choose whether to delete or preserve passwords when he or she clicks Delete.
-
-If the "Prevent access to Delete Browsing History" policy setting is enabled, this policy setting is enabled by default.
- Prevents users from adding, editing, or removing schedules for offline viewing of Web pages and groups of Web pages that users have subscribed to.
-
-A subscription group is a favorite Web page plus the Web pages it links to.
-
-If you enable this policy, the Add, Remove, and Edit buttons on the Schedule tab in the Web page Properties dialog box are dimmed. To display this tab, users click the Tools menu, click Synchronize, select a Web page, click the Properties button, and then click the Schedule tab.
-
-If you disable this policy or do not configure it, users can add, remove, and edit schedules for Web sites and groups of Web sites.
-
-The "Disable editing schedules for offline pages" policy and the "Hide Favorites menu" policy (located in User Configuration\Administrative Templates\Windows Components\Internet Explorer) take precedence over this policy. If either policy is enabled, this policy is ignored.
- Prevents users from editing an existing schedule for downloading Web pages for offline viewing.
-
-When users make Web pages available for offline viewing, they can view content when their computer is not connected to the Internet.
-
-If you enable this policy, users cannot display the schedule properties of pages that have been set up for offline viewing. If users click the Tools menu, click Synchronize, select a Web page, and then click the Properties button, no properties are displayed. Users do not receive an alert stating that the command is unavailable.
-
-If you disable this policy or do not configure it, users can edit an existing schedule for downloading Web content for offline viewing.
-
-This policy is intended for organizations that are concerned about server load for downloading content.
-
-The "Hide Favorites menu" policy (located in User Configuration\Administrative Templates\Windows Components\Internet Explorer) takes precedence over this policy. If it is enabled, this policy is ignored.
- Prevents users from adding, removing, editing or viewing the list of Favorite links.
-
-The Favorites list is a way to store popular links for future use.
-
-If you enable this policy, the Favorites menu is removed from the interface, and the Favorites button on the browser toolbar appears dimmed. The Add to Favorites command on the shortcut menu is disabled; when users click it, they are informed that the command is unavailable.
-
-If you disable this policy or do not configure it, users can manage their Favorites list.
-
-Note: If you enable this policy, users also cannot click Synchronize on the Tools menu (in Internet Explorer 6) to manage their favorite links that are set up for offline viewing.
- This policy setting prevents Internet Explorer from running the First Run wizard the first time a user starts the browser after installing Internet Explorer or Windows.
-
-If you enable this policy setting, you must make one of the following choices:
- • Skip the First Run wizard, and go directly to the user's home page.
- • Skip the First Run wizard, and go directly to the "Welcome to Internet Explorer" webpage.
-
-Starting with Windows 8, the "Welcome to Internet Explorer" webpage is not available. The user's home page will display regardless of which option is chosen.
-
-If you disable or do not configure this policy setting, Internet Explorer may run the First Run wizard the first time the browser is started after installation.
- This policy setting prevents the user from accessing Help in Internet Explorer.
-
-If you enable this policy setting, the following occur:
- • The Help menu on the menu bar is not functional.
- • Help is removed from the Command bar.
- • The shortcut key F1 does not make Help appear.
- • Help cannot be accessed from the Settings charm (starting with Internet Explorer 10 on Windows 8).
-
-If you disable or do not configure this policy setting, the Internet Explorer Help menu is available to the user. The user can also use the Command bar and F1 to access Help.
- This policy setting prevents the Search box from appearing in Internet Explorer. When the Search box is available, it includes all installed search providers and a link to search settings.
-
-If you enable this policy setting, the Search box does not appear in the Internet Explorer frame.
-
-If you disable or do not configure this policy setting, the Search box appears by default in the Internet Explorer frame.
-
-Note: If you enable this policy setting, Internet Explorer does not enumerate search providers for the Accelerators infrastructure. If Accelerators are turned on, users can install search providers as Accelerators to include them on the Accelerator menu.
- Prevents Internet Explorer from automatically installing components.
-
-If you enable this policy, it prevents Internet Explorer from downloading a component when users browse to a Web site that needs that component.
-
-If you disable this policy or do not configure it, users will be prompted to download and install a component when visiting a Web site that uses that component.
-
-This policy is intended to help the administrator control which components the user installs.
- Prevents using the shortcut menu to open a link in a new browser window.
-
-If you enable this policy, users cannot point to a link, click the right mouse button, and then click the Open in New Window command.
-
-If you disable this policy or do not configure it, users can open a Web page in a new browser window by using the shortcut menu.
-
-This policy can be used in coordination with the "File menu: Disable New menu option" policy, which prevents users from opening the browser in a new window by clicking the File menu, pointing to New, and then clicking Window.
-
-Note: When users click the Open in New Window command, the link will not open in a new window and they will be informed that the command is not available.
- This policy setting allows you to turn off the Quick Tabs functionality in Internet Explorer.
-
-If you enable this policy setting, the entry points to Quick Tabs are removed from the Internet Explorer user interface.
-
-If you disable or do not configure this policy setting, Quick Tabs is turned on.
- Prevents users from disabling channel synchronization in Microsoft Internet Explorer.
-
-Channels are Web sites that are automatically updated on your computer according to a schedule specified by the channel provider.
-
-If you enable this policy, users cannot prevent channels from being synchronized.
-
-If you disable this policy or do not configure it, users can disable the synchronization of channels.
-
-This policy is intended to help administrators ensure that users' computers are being updated uniformly across their organization.
-
-Note: This policy does not prevent users from removing active content from the desktop interface.
- Prevents users from clearing the preconfigured settings for Web pages to be downloaded for offline viewing.
-
-When users make Web pages available for offline viewing, they can view content when their computer is not connected to the Internet.
-
-If you enable this policy, the Make Available Offline check box in the Organize Favorites Favorite dialog box and the Make This Page Available Offline check box will be selected but dimmed. To display the Make This Page Available Offline check box, users click the Tools menu, click Synchronize, and then click the Properties button.
-
-If you disable this policy or do not configure it, users can remove the preconfigured settings for pages to be downloaded for offline viewing.
-
-This policy is intended for organizations that are concerned about server load for downloading content.
-
-The "Hide Favorites menu" policy (located in User Configuration\Administrative Templates\Windows Components\Internet Explorer) takes precedence over this policy. If it is enabled, this policy is ignored.
- Disables existing schedules for downloading Web pages for offline viewing.
-
-When users make Web pages available for offline viewing, they can view content when their computer is not connected to the Internet.
-
-If you enable this policy, the check boxes for schedules on the Schedule tab of the Web page properties are cleared and users cannot select them. To display this tab, users click the Tools menu, click Synchronize, select a Web page, click the Properties button, and then click the Schedule tab.
-
-If you disable this policy, then Web pages can be updated on the schedules specified on the Schedule tab.
-
-This policy is intended for organizations that are concerned about server load for downloading content.
-
-The "Hide Favorites menu" policy (located in User Configuration\Administrative Templates\Windows Components\Internet Explorer) takes precedence over this policy. If it is enabled, this policy is ignored.
- Makes the Customize button in the Search Assistant appear dimmed.
-
-The Search Assistant is a tool that appears in the Search bar to help users search the Internet.
-
-If you enable this policy, users cannot change their Search Assistant settings, such as setting default search engines for specific tasks.
-
-If you disable this policy or do not configure it, users can change their settings for the Search Assistant.
-
-This policy is designed to help administrators maintain consistent settings for searching across an organization.
- This policy setting prevents the user from changing the default search provider for the Address bar and the toolbar Search box.
-
-If you enable this policy setting, the user cannot change the default search provider.
-
-If you disable or do not configure this policy setting, the user can change the default search provider.
- Prevents users from saving a program or file that Microsoft Internet Explorer has downloaded to the hard disk.
-
-If you enable this policy, users cannot save a program to disk by clicking the Save This Program to Disk command while attempting to download a file. The file will not be downloaded and users will be informed that the command is not available.
-
-If you disable this policy or do not configure it, users can download programs from their browsers.
- Prevents the Internet Explorer splash screen from appearing when users start the browser.
-
-If you enable this policy, the splash screen, which displays the program name, licensing, and copyright information, is not displayed.
-
-If you disable this policy or do not configure it, the splash screen will be displayed when users start their browsers.
- Prevents content from being downloaded from Web sites that users have subscribed to.
-
-When users make Web pages available for offline viewing, they can view content when their computer is not connected to the Internet.
-
-If you enable this policy, content will not be downloaded from Web sites that users have subscribed to. However, synchronization with the Web pages will still occur to determine if any content has been updated since the last time the user synchronized with or visited the page.
-
-If you disable this policy or do not configure it, content will not be prevented from being downloaded.
-
-The "Disable downloading of site subscription content" policy and the "Hide Favorites menu" policy (located in User Configuration\Administrative Templates\Windows Components\Internet Explorer) take precedence over this policy. If either policy is enabled, this policy is ignored.
- This policy setting allows you to turn off tabbed browsing and related entry points from the Internet Explorer user interface. Starting with Windows 8, this policy only applies to Internet Explorer on the desktop.
-
-If you enable this policy setting, tabbed browsing and related entry points are turned off for Internet Explorer, and the user cannot turn them on.
-
-If you disable this policy setting, tabbed browsing and related entry points appear on the user interface for Internet Explorer, and the user cannot turn them off.
-
-If you do not configure this policy setting, the user can turn on or turn off tabbed browsing.
- This policy setting allows you to define the user experience related to how pop-up windows appear in tabbed browsing in Internet Explorer.
-
-If you enable this policy setting, the user cannot configure pop-up windows in tabbed browsing. You must specify one of the following values:
- 0: Let Internet Explorer decide.
- 1: Force pop-up windows to open in new windows.
- 2: Force pop-up windows to open on new tabs.
-
-If you disable or do not configure this policy setting, Internet Explorer uses the user's setting for pop-up windows in tabbed browsing.
- Prevents users from determining which buttons appear on the Microsoft Internet Explorer and File Explorer standard toolbars. The buttons appearing on the toolbar can be customized by the "Customize" option. This is present under the Toolbars submenu of the View menu in Internet Explorer 6 and under the Toolbars submenu of the Tools menu in the Command bar in subsequent versions of Internet Explorer.
-
-If you enable this policy, the Customize option will be removed from the menu.
-
-If you disable this policy or do not configure it, users can customize which buttons appear on the Internet Explorer and File Explorer toolbars.
-
-This policy can be used in coordination with the "Disable customizing browser toolbars" policy, which prevents users from determining which toolbars are displayed in Internet Explorer and File Explorer.
- Prevents Internet Explorer from checking whether a new version of the browser is available.
-
-If you enable this policy, it prevents Internet Explorer from checking to see whether it is the latest available browser version and notifying users if a new version is available.
-
-If you disable this policy or do not configure it, Internet Explorer checks every 30 days by default, and then notifies users if a new version is available.
-
-This policy is intended to help the administrator maintain version control for Internet Explorer by preventing users from being notified about new versions of the browser.
- This policy setting allows you to configure how windows open in Internet Explorer when the user clicks links from other applications.
-
-If you enable this policy setting, the user cannot configure how windows open in Internet Explorer when he or she clicks links from other applications. You must specify one of the following:
- • Open in an existing Internet Explorer window. If tabbed browsing is enabled, a new tab is created in this scenario.
- • Open a new Internet Explorer window.
-
-If you disable or do not configure this policy setting, the user can configure how windows open when he or she clicks links from other applications.
- Allows Administrators to enable and disable the ability for Outlook Express users to save or open attachments that can potentially contain a virus.
-
-If you check the block attachments setting, users will be unable to open or save attachments that could potentially contain a virus. Users will not be able to disable the blocking of attachments in options.
-
-If the block attachments setting is not checked, the user can specify to enable or disable the blocking of attachments in options.
- Limits the amount of storage that a page or site using the DHTML Persistence behavior can use for the Local Computer security zone.
-
-If you enable this policy, you can specify the persistence storage amount per domain or per document for this security zone.
-
-If you disable this policy or do not configure it, you cannot set this limit.
-
-Note: This setting does not appear in the user interface.
- Limits the amount of storage that a page or site using the DHTML Persistence behavior can use for the Local Intranet security zone.
-
-If you enable this policy, you can specify the persistence storage amount per domain or per document for this security zone.
-
-If you disable this policy or do not configure it, you cannot set this limit.
-
-Note: This setting does not appear in the user interface.
- Limits the amount of storage that a page or site using the DHTML Persistence behavior can use for the Trusted Sites security zone.
-
-If you enable this policy, you can specify the persistence storage amount per domain or per document for this security zone.
-
-If you disable this policy or do not configure it, you cannot set this limit.
-
-Note: This setting does not appear in the user interface.
- Limits the amount of storage that a page or site using the DHTML Persistence behavior can use for the Internet security zone.
-
-If you enable this policy, you can specify the persistence storage amount per domain or per document for this security zone.
-
-If you disable this policy or do not configure it, you cannot set this limit.
-
-Note: This setting does not appear in the user interface.
- Limits the amount of storage that a page or site using the DHTML Persistence behavior can use for the Restricted Sites security zone.
-
-If you enable this policy, you can specify the persistence storage amount per domain or per document for this security zone.
-
-If you disable this policy or do not configure it, you cannot set this limit.
-
-Note: This setting does not appear in the user interface.
- Contains settings for file size limits in internet security zones.
- If you enable this policy, the user cannot modify the Accessibility options. All options in the "Accessibility" window on the General Tab in the Internet Options dialog box appear dimmed.
-
-If you disable this policy or do not configure it, users can change accessibility settings, such as overriding fonts and colors on Web pages.
-
-If you set the "Disable the General page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), you do not need to set this policy, because the "Disable the General page" policy removes the General tab from the interface.
- This setting specifies to automatically detect the proxy server settings used to connect to the Internet and customize Internet Explorer. This setting specifies that Internet explorer use the configuration settings provided in a file by the system administrator.
-
-If you enable this policy setting, the user will not be able to do automatic configuration. You can import your current connection settings from your machine using Internet Explorer Maintenance under Admin Templates using group policy editor.
-
-If you disable or do no configure this policy setting, the user will have the freedom to automatically configure these settings.
- Prevents users from changing the browser cache settings, such as the location and amount of disk space to use for the Temporary Internet Files folder.
-
-If you enable this policy, the browser cache settings appear dimmed. These settings are found in the dialog box that appears when users click the General tab and then click the Settings button in the Internet Options dialog box.
-
-If you disable this policy or do not configure it, users can change their cache settings.
-
-If you set the "Disable the General page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), you do not need to set this policy, because the "Disable the General page" policy removes the General tab from the interface.
- Prevents users from changing the default programs for managing schedules and contacts.
-
-If you enable this policy, the Calendar and Contact combo boxes appear dimmed in the Internet Programs area. To display these options, users open the Internet Options dialog box, and then click the Programs tab.
-
-If you disable this policy or do not configure it, users can determine which programs to use for managing schedules and contacts, if programs that perform these tasks are installed.
-
-This "Disable the Programs Page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel) takes precedence over this policy. If it is enabled, this policy is ignored.
- Prevents users from changing certificate settings in Internet Explorer. Certificates are used to verify the identity of software publishers.
-
-If you enable this policy, the settings in the Certificates area on the Content tab in the Internet Options dialog box appear dimmed.
-
-If you disable this policy or do not configure it, users can import new certificates, remove approved publishers, and change settings for certificates that have already been accepted.
-
-The "Disable the Content page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), which removes the Content tab from Internet Explorer in Control Panel, takes precedence over this policy. If it is enabled, this policy is ignored.
-
-Caution: If you enable this policy, users can still run the Certificate Manager Import Wizard by double-clicking a software publishing certificate (.spc) file. This wizard enables users to import and configure settings for certificates from software publishers that haven't already been configured for Internet Explorer.
- Prevents Microsoft Internet Explorer from checking to see whether it is the default browser.
-
-If you enable this policy, the Internet Explorer Should Check to See Whether It Is the Default Browser check box on the Programs tab in the Internet Options dialog box appears dimmed.
-
-If you disable this policy or do not configure it, users can determine whether Internet Explorer will check to see if it is the default browser. When Internet Explorer performs this check, it prompts the user to specify which browser to use as the default.
-
-This policy is intended for organizations that do not want users to determine which browser should be their default.
-
-The "Disable the Programs page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), which removes the Programs tab from Internet Explorer in Control Panel, takes precedence over this policy. If it is enabled, this policy is ignored.
- This policy setting allows you to choose whether users will be notified if Internet Explorer is not the default web browser.
-
-If you enable this policy setting, users will be notified if Internet Explorer is not the default web browser. Users cannot change the setting.
-
-If you disable this policy setting, users will not be notified if Internet Explorer is not the default web browser. Users cannot change the setting.
-
-If you do not configure this policy setting, users can choose whether to be notified that Internet Explorer is not the default web browser through the Tell me if Internet Explorer is not the default web browser check box on the Programs tab in the Internet Options dialog box. Note that starting with Internet Explorer 10 on Windows 8, the check box is located on the Advanced tab in the Internet Options dialog box. For more information, see "Group Policy Settings in Internet Explorer 10" in the Internet Explorer TechNet library.
- Prevents users from changing the default Web page colors.
-
-If you enable this policy, the color settings for Web pages appear dimmed. The settings are located in the Colors area in the dialog box that appears when the user clicks the General tab and then clicks the Colors button in the Internet Options dialog box.
-
-If you disable this policy or do not configure it, users can change the default background and text color of Web pages.
-
-If you set the "Disable the General page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), you do not need to set this policy, because the "Disable the General page" policy removes the General tab from the interface.
-
-Note: The default Web page colors are ignored on Web pages in which the author has specified the background and text colors.
- Prevents users from changing dial-up settings.
-
-If you enable this policy, the Settings button on the Connections tab in the Internet Options dialog box appears dimmed.
-
-If you disable this policy or do not configure it, users can change their settings for dial-up connections.
-
-If you set the "Disable the Connections page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), you do not need to set this policy, because the "Disable the Connections page" policy removes the Connections tab from the interface.
- Prevents users from running the Internet Connection Wizard.
-
-If you enable this policy, the Setup button on the Connections tab in the Internet Options dialog box appears dimmed.
-
-Users will also be prevented from running the wizard by clicking the Connect to the Internet icon on the desktop or by clicking Start, pointing to Programs, pointing to Accessories, pointing to Communications, and then clicking Internet Connection Wizard.
-
-If you disable this policy or do not configure it, users can change their connection settings by running the Internet Connection Wizard.
-
-Note: This policy overlaps with the "Disable the Connections page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), which removes the Connections tab from the interface. Removing the Connections tab from the interface, however, does not prevent users from running the Internet Connection Wizard from the desktop or the Start menu.
- Prevents users from changing font settings.
-
-If you enable this policy, users will not be able to change font settings for viewing Web pages. All font settings visible after pressing the "Fonts" button on the General Tab in the Internet Options dialog box will be disabled.
-
-If you disable this policy or do not configure it, users can change the default fonts for viewing Web pages.
-
-If you set the "Disable the General page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), you do not need to set this policy, because the "Disable the General page" policy removes the General tab from the interface.
-
-Note: The default font settings colors are ignored in cases in which the Web page author has specified the font attributes.
- This AutoComplete feature suggests possible matches when users are filling up forms.
-
-If you enable this setting, the user is not suggested matches when filling forms. The user cannot change it.
-
-If you disable this setting, the user is suggested possible matches when filling forms. The user cannot change it.
-
-If you do not configure this setting, the user has the freedom to turn on the auto-complete feature for forms.
-
-To display this option, the users open the Internet Options dialog box, click the Contents Tab and click the Settings button.
- This AutoComplete feature can remember and suggest User names and passwords on Forms.
-
-If you enable this setting, the user cannot change "User name and passwords on forms" or "prompt me to save passwords". The Auto Complete feature for User names and passwords on Forms will be turned on. You have to decide whether to select "prompt me to save passwords".
-
-If you disable this setting the user cannot change "User name and passwords on forms" or "prompt me to save passwords". The Auto Complete feature for User names and passwords on Forms is turned off. The user also cannot opt to be prompted to save passwords.
-
-If you do not configure this setting, the user has the freedom of turning on Auto complete for User name and passwords on forms and the option of prompting to save passwords. To display this option, the users open the Internet Options dialog box, click the Contents Tab and click the Settings button.
- This setting specifies the number of days that Internet Explorer tracks views of pages in the History List. To access the Temporary Internet Files and History Settings dialog box, from the Menu bar, on the Tools menu, click Internet Options, click the General tab, and then click Settings under Browsing history.
-
-If you enable this policy setting, a user cannot set the number of days that Internet Explorer tracks views of the pages in the History List. You must specify the number of days that Internet Explorer tracks views of pages in the History List. Users can not delete browsing history.
-
-If you disable or do not configure this policy setting, a user can set the number of days that Internet Explorer tracks views of pages in the History list. Users can delete browsing history.
- The Home page specified on the General tab of the Internet Options dialog box is the default Web page that Internet Explorer loads whenever it is run.
-
-If you enable this policy setting, a user cannot set a custom default home page. You must specify which default home page should load on the user machine. For machines with at least Internet Explorer 7, the home page can be set within this policy to override other home page policies.
-
-If you disable or do not configure this policy setting, the Home page box is enabled and users can choose their own home page.
- Prevents users from changing language preference settings.
-
-If you enable this policy, users will not be able to set language preferences to read websites. Language preference settings visible after pressing the "Languages" button on the General Tab in the Internet Options dialog box will be disabled.
-
-If you disable this policy or do not configure it, users can change the language preference settings for viewing Web sites for languages in which the character set has been installed.
-
-If you set the "Disable the General page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), you do not need to set this policy, because the "Disable the General page" policy removes the General tab from the interface.
- Prevents users from changing the colors of links on Web pages.
-
-If you enable this policy, the color settings for links appear dimmed. The settings are located in the Links area of the dialog box that appears when users click the General tab and then click the Colors button in the Internet Options dialog box.
-
-If you disable this policy or do not configure it, users can change the default color of links on Web pages.
-
-If you set the "Disable the General page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), you do not need to set this policy, because the "Disable the General page" policy removes the General tab from the interface.
-
-Note: The default link colors are ignored on Web pages on which the author has specified link colors.
- Prevents users from changing the default programs for messaging tasks.
-
-If you enable this policy, the E-mail, Newsgroups, and Internet Call options in the Internet Programs area appear dimmed. To display these options, users open the Internet Options dialog box, and then click the Programs tab.
-
-If you disable this policy or do not configure it, users can determine which programs to use for sending mail, viewing newsgroups, and placing Internet calls, if programs that perform these tasks are installed.
-
-The "Disable the Programs page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), which removes the Programs tab from Internet Explorer in Control Panel, takes precedence over this policy. If it is enabled, this policy is ignored.
- You can allow pop-ups from specific websites by adding the sites to the exception list.
-
-If you enable this policy setting, the user cannot add websites to or remove websites from the exception list.
-
-If you disable or do not configure this policy setting, the user can add websites to or remove websites from the exception list.
-
-Note: You can allow a default list of sites that can open pop-up windows regardless of the Internet Explorer process's Pop-Up Blocker settings by enabling the "Specify pop-up allow list" policy setting.
- This policy setting allows you to manage pop-up management functionality in Internet Explorer.
-
-If you enable this policy setting, the Control Panel information relating to pop-up management will be unavailable (grayed out) and all other pop-up manager controls, notifications, and dialog boxes will not appear. Pop-up windows will continue to function as they did in Windows XP Service Pack 1 or earlier, although windows launched off screen will continue to be re-positioned onscreen.
-
-If you disable or do not configure this policy setting, the popup management feature will be functional.
- Prevents users from changing Profile Assistant settings.
-
-If you enable this policy, the My Profile button appears dimmed in the Personal Information area on the Content tab in the Internet Options dialog box.
-
-If you disable this policy or do not configure it, users can change their profile information, such as their street and e-mail addresses.
-
-The "Disable the Content page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), which removes the Content tab from Internet Explorer in Control Panel, takes precedence over this policy. If it is enabled, this policy is ignored.
- This policy setting specifies if a user can change proxy settings.
-
-If you enable this policy setting, the user will not be able to configure proxy settings.
-
-If you disable or do not configure this policy setting, the user can configure proxy settings.
- Prevents users from changing ratings that help control the type of Internet content that can be viewed.
-
-If you enable this policy, the settings in the Content Advisor area on the Content tab in the Internet Options dialog box appear dimmed.
-
-If you disable this policy or do not configure it, users can change their ratings settings.
-
-The "Disable the Ratings page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), which removes the Ratings tab from Internet Explorer in Control Panel, takes precedence over this policy. If it is enabled, this policy is ignored.
- Prevents users from restoring default settings for home and search pages.
-
-If you enable this policy, the Reset Web Settings button on the Programs tab in the Internet Options dialog box appears dimmed.
-
-If you disable this policy or do not configure it, users can restore the default settings for home and search pages.
-
-The "Disable the Programs page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), which removes the Programs tab from Internet Explorer in Control Panel, takes precedence over this policy. If it is enabled, this policy is ignored.
- This policy setting is used to manage temporary Internet files and cookies associated with your Internet browsing history, available by clicking Tools, Internet Options, and then Delete Browsing History in Internet Explorer.
-
-If you enable this policy setting, users will not be able to delete temporary Internet files and cookies.
-
-If you disable or do not configure this policy setting, users will be able to delete temporary Internet files and cookies.
- This AutoComplete feature suggests possible matches when users are entering Web addresses in the browser address bar.
-
-If you enable this policy setting, user will not be suggested matches when entering Web addresses. The user cannot change the auto-complete for web-address setting.
-
-If you disable this policy setting, user will be suggested matches when entering Web addresses. The user cannot change the auto-complete for web-address setting.
-
-If you do not configure this policy setting, a user will have the freedom to choose to turn the auto-complete setting for web-addresses on or off.
- This policy setting allows you to prevent Windows Search AutoComplete from providing results in the Internet Explorer Address bar.
-
-Windows Search AutoComplete suggests possible matches when a user is entering a web address in the browser Address bar. This feature provides more relevant results in the browser Address bar.
-
-If you enable this policy setting, Internet Explorer does not use Windows Search AutoComplete for providing relevant results in the Address bar. The user cannot change this setting.
-
-If you disable this policy setting, Internet Explorer uses Windows Search AutoComplete to provide relevant results in the Address bar. The user cannot change this setting.
-
-If you do not configure this policy setting, the user can choose to turn the Use Windows Search setting on or off.
-
-Note: If you enable this policy setting, feeds do not appear in the Address bar. This does not affect subscribing to feeds and interacting with them through the Favorites Center.
- This policy setting turns off URL Suggestions. URL Suggestions allow users to autocomplete URLs in the address bar based on common URLs. The list of common URLs is stored locally and is updated once a month. No user data is sent over the internet by this feature.
-
-If you enable this policy setting, URL Suggestions will be turned off. Users will not be able to turn on URL Suggestions.
-
-If you disable this policy setting, URL Suggestions will be turned on. Users will not be able to turn off URL Suggestions.
-
-If you do not configure this policy setting, URL Suggestions will be turned on. Users will be able to turn on or turn off URL Suggestions in the Internet Options dialog. By default, URL Suggestions are turned on.
- Designates Microsoft Scriptlet Component as an administrator approved control. It is an Active X control which is used to render HTML pages.
-
-If you enable this policy, this control can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, this control will not be designated as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- Disables using the F3 key to search in Internet Explorer and File Explorer.
-
-If you enable this policy, the search functionality of the F3 key is disabled. Users cannot press F3 to search the Internet (from Internet Explorer) or to search the hard disk (from File Explorer). If the user presses F3, a prompt appears that informs the user that this feature has been disabled.
-
-If you disable this policy or do not configure it, users can press F3 to search the Internet (from Internet Explorer) or the hard disk (from File Explorer).
-
-This policy is intended for situations in which administrators do not want users to explore the Internet or the hard disk.
-
-This policy can be used in coordination with the "File Menu: Disable Open menu option" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Browser Menus), which prevents users from opening files by using the browser.
- Applies security zone information to all users of the same computer. A security zone is a group of Web sites with the same security level.
-
-If you enable this policy, changes that the user makes to a security zone will apply to all users of that computer.
-
-If you disable this policy or do not configure it, users of the same computer can establish their own security zone settings.
-
-This policy is intended to ensure that security zone settings apply uniformly to the same computer and do not vary from user to user.
-
-Also, see the "Security zones: Do not allow users to change policies" policy.
- Prevents users from changing security zone settings. A security zone is a group of Web sites with the same security level.
-
-If you enable this policy, the Custom Level button and security-level slider on the Security tab in the Internet Options dialog box are disabled.
-
-If you disable this policy or do not configure it, users can change the settings for security zones.
-
-This policy prevents users from changing security zone settings established by the administrator.
-
-Note: The "Disable the Security page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), which removes the Security tab from Internet Explorer in Control Panel, takes precedence over this policy. If it is enabled, this policy is ignored.
-
-Also, see the "Security zones: Use only machine settings" policy.
- Prevents users from adding or removing sites from security zones. A security zone is a group of Web sites with the same security level.
-
-If you enable this policy, the site management settings for security zones are disabled. (To see the site management settings for security zones, in the Internet Options dialog box, click the Security tab, and then click the Sites button.)
-
-If you disable this policy or do not configure it, users can add Web sites to or remove sites from the Trusted Sites and Restricted Sites zones, and alter settings for the Local Intranet zone.
-
-This policy prevents users from changing site management settings for security zones established by the administrator.
-
-Note: The "Disable the Security page" policy (located in \User Configuration\Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel), which removes the Security tab from the interface, takes precedence over this policy. If it is enabled, this policy is ignored.
-
-Also, see the "Security zones: Use only machine settings" policy.
- This policy setting enables intranet mapping rules to be applied automatically if the computer belongs to a domain.
-
-If you enable this policy setting, automatic detection of the intranet is turned on, and intranet mapping rules are applied automatically if the computer belongs to a domain.
-
-If you disable this policy setting, automatic detection of the intranet is turned off, and intranet mapping rules are applied however they are configured.
-
-If this policy setting is not configured, the user can choose whether or not to automatically detect the intranet through the intranet settings dialog in Control Panel.
- This policy setting causes a Notification bar notification to appear when intranet content is loaded and the intranet mapping rules have not been configured. The Notification bar allows the user to enable intranet mappings, if they require them.
-
-If you enable this policy setting, a Notification bar notification appears whenever the user browses to a page that loads content from an intranet site.
-
-If you disable this policy setting, a Notification bar notification does not appear when the user loads content from an intranet site that is being treated as though it is in the Internet zone.
-
-If this policy setting is not configured, a Notification bar notification appears for intranet content loaded on a browser on a computer that is not a domain member, until the user turns off the Notification bar.
- Specifies that programs using the Microsoft Software Distribution Channel will not notify users when they install new components. The Software Distribution Channel is a means of updating software dynamically on users' computers by using Open Software Distribution (.osd) technologies.
-
-If you enable this policy, users will not be notified if their programs are updated using Software Distribution Channels.
-
-If you disable this policy or do not configure it, users will be notified before their programs are updated.
-
-This policy is intended for administrators who want to use Software Distribution Channels to update their users' programs without user intervention.
- This policy setting allows you to restrict the search providers that appear in the Search box in Internet Explorer to those defined in the list of policy keys for search providers (found under [HKCU or HKLM\Software\policies\Microsoft\Internet Explorer\SearchScopes]). Normally, search providers can be added from third-party toolbars or in Setup, but the user can also add them from a search provider's website.
-
-If you enable this policy setting, the user cannot configure the list of search providers on his or her computer, and any default providers installed do not appear (including providers installed from other applications). The only providers that appear are those in the list of policy keys for search providers. Note: This list can be created through a custom administrative template file. For information about creating this custom administrative template file, see the Internet Explorer documentation on search providers.
-
-If you disable or do not configure this policy setting, the user can configure his or her list of search providers.
- This policy setting prevents the user from participating in the Customer Experience Improvement Program (CEIP).
-
-If you enable this policy setting, the user cannot participate in the CEIP, and the Customer Feedback Options command does not appear on the Help menu.
-
-If you disable this policy setting, the user must participate in the CEIP, and the Customer Feedback Options command does not appear on the Help menu.
-
-If you do not configure this policy setting, the user can choose to participate in the CEIP.
- Designates Microsoft Survey Control as an administrator approved control.
-
-If you enable this policy, this control can be run in security zones in which you specify that administrator-approved controls can be run.
-
-If you disable this policy or do not configure it, this control will not be designated as administrator-approved.
-
-To specify how administrator-approved controls are handled for each security zone, carry out the following steps:
-1. In Group Policy, click User Configuration, click Internet Explorer Maintenance, and then click Security.
-2. Double-click Security Zones and Content Ratings, click Import the Current Security Zones Settings, and then click Modify Settings.
-3. Select the content zone in which you want to manage ActiveX controls, and then click Custom Level.
-4. In the Run ActiveX Controls and Plug-ins area, click Administrator Approved.
- This policy setting allows you to configure how new tabs are created by default in Internet Explorer.
-
-If you enable this policy setting, the user cannot configure how new tabs are created by default. You must specify whether tabs should open in the foreground or in the background. The user cannot open the tabs in the background by pressing Ctrl+Shift+Select or open the tabs in the foreground by pressing Ctrl+Shift+Select.
-
-If you disable or do not configure this policy setting, the user can configure how new tabs are created by default.
- Specifies which buttons will be displayed on the standard toolbar in Microsoft Internet Explorer.
-
-If you enable this policy, you can specify whether or not each button will be displayed by selecting or clearing the check boxes for each button.
-
-If you disable this policy or do not configure it, the standard toolbar will be displayed with its default settings, unless users customize it.
- Contains settings to allow and restrict users from editing the toolbars in Internet Explorer. Administrators can also set the default toolbar buttons.
- Prevents users from opening the Internet Options dialog box from the Tools menu in Microsoft Internet Explorer.
-
-If you enable this policy, users cannot change their Internet options, such as default home page, cache size, and connection and proxy settings, from the browser Tools menu. When users click the Internet Options command on the Tools menu, they are informed that the command is unavailable.
-
-If you disable this policy or do not configure it, users can change their Internet settings from the browser Tools menu.
-
-Caution: This policy does not prevent users from viewing and changing Internet settings by clicking the Internet Options icon in Windows Control Panel.
-
-Also, see policies for Internet options in the \Administrative Templates\Windows Components\Internet Explorer and in \Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel folders.
- This policy setting allows you to manage whether users can launch the report site problems dialog using a menu option.
-
-If you enable this policy setting, a menu option won’t be available in Internet Explorer settings, or in the tools menu in the desktop. Users won’t be able to use it to launch the report site problems dialog box.
-
-If you disable or do not configure this policy setting, the menu options will be available.
- Applies proxy settings to all users of the same computer.
-
-If you enable this policy, users cannot set user-specific proxy settings. They must use the zones created for all users of the computer.
-
-If you disable this policy or do not configure it, users of the same computer can establish their own proxy settings.
-
-This policy is intended to ensure that proxy settings apply uniformly to the same computer and do not vary from user to user.
- Prevents users from displaying the browser in full-screen (kiosk) mode, without the standard toolbar.
-
-If you enable this policy, the Full Screen command on the View menu will appear dimmed, and pressing F11 will not display the browser in a full screen.
-
-If you disable this policy or do not configure it, users can display the browser in a full screen.
-
-This policy is intended to prevent users from displaying the browser without toolbars, which might be confusing for some beginning users.
- Prevents users from viewing the HTML source of Web pages by clicking the Source command on the View menu.
-
-If you enable this policy, the Source command on the View menu will appear dimmed.
-
-If you disable this policy or do not configure it, then users can view the HTML source of Web pages from the browser View menu.
-
-Caution: This policy does not prevent users from viewing the HTML source of a Web page by right-clicking a Web page to open the shortcut menu, and then clicking View Source. To prevent users from viewing the HTML source of a Web page from the shortcut menu, set the "Turn off Shortcut Menu" policy, which disables the entire shortcut menu.
- Let Internet Explorer decide
- Add-on Management
- This policy setting allows you to manage whether processes respect add-on management user preferences (as reflected by Add-on Manager) or policy settings. By default, any process other than the Internet Explorer processes or those listed in the 'Process List' policy setting ignore add-on management user preferences and policy settings.
-
-If you enable this policy setting, all processes will respect add-on management user preferences and policy settings.
-
-If you disable or do not configure this policy setting, all processes will not respect add-on management user preferences or policy settings.
- This policy setting allows you to manage whether the listed processes respect add-on management user preferences (as entered into Add-on Manager) or policy settings. By default, only Internet Explorer processes use the add-on management user preferences and policy settings. This policy setting allows you to extend support for these user preferences and policy settings to specific processes listed in the process list.
-
-If you enable this policy setting and enter a Value of 1, the process entered will respect the add-on management user preferences and policy settings. If you enter a Value of 0, the add-on management user preferences and policy settings are ignored by the specified process. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter Internet Explorer processes in this list because these processes always respect add-on management user preferences and policy settings. If the All Processes policy setting is enabled, the processes configured in this policy setting take precedence over that setting.
-
-If you do not configure this policy, processes other than the Internet Explorer processes will not be affected by add-on management user preferences or policy settings (unless "All Processes" is enabled).
- AJAX
- Binary Behavior Security Restriction
- Consistent Mime Handling
- Notification bar
- Local Machine Zone Lockdown Security
- Mime Sniffing Safety Feature
- MK Protocol Security Restriction
- Network Protocol Lockdown
- Object Caching Protection
- Protection From Zone Elevation
- Restrict ActiveX Install
- Restrict File Download
- Scripted Window Security Restrictions
- Allow native XMLHTTP support
- Technologies that enable communications between clients and server and/or cross domain communications.
- For each zone, the Binary and Scripted Behavior security restrictions may be configured to allow only a list of admin-approved behaviors. This list may be configured here, and applies to all processes which have opted in to the behavior, and to all zones. (Behaviors are components that encapsulate specific functionality or behavior on a page.)
-
-If you enable this policy setting, this sets the list of behaviors permitted in each zone for which Script and Binary Behaviors is set to 'admin-approved'. Behaviors must be entered in #package#behavior notation, e.g., #default#vml.
-
-If you disable this policy setting, no behaviors will be allowed in zones set to 'admin-approved', just as if those zones were set to 'disable'.
-
-If you do not configure this policy setting, only VML will be allowed in zones set to 'admin-approved'.
-
-Note. If this policy is set in both Computer Configuration and User Configuration, both lists of behaviors will be allowed as appropriate.
- Internet Explorer allows users and administrators to decide which add-ons are permitted to load. Applications hosting the Web Browser Control can be configured to respect the same settings as Internet Explorer.
- Internet Explorer contains dynamic binary behaviors: components that encapsulate specific functionality for the HTML elements to which they are attached. This policy setting controls whether the Binary Behavior Security Restriction setting is prevented or allowed.
-
-If you enable this policy setting, binary behaviors are prevented for all processes. Any use of binary behaviors for HTML rendering is blocked.
-
-If you disable or do not configure this policy setting, binary behaviors are allowed for all processes.
- Internet Explorer contains dynamic binary behaviors: components that encapsulate specific functionality for the HTML elements to which they are attached. This policy setting controls whether the Binary Behavior Security Restriction setting is prevented or allowed.
-
-If you enable this policy setting, binary behaviors are prevented for the File Explorer and Internet Explorer processes.
-
-If you disable this policy setting, binary behaviors are allowed for the File Explorer and Internet Explorer processes.
-
-If you do not configure this policy setting, binary behaviors are prevented for the File Explorer and Internet Explorer processes.
- Internet Explorer contains dynamic binary behaviors: components that encapsulate specific functionality for the HTML elements to which they are attached. This policy setting controls whether the Binary Behavior Security Restriction setting is prevented or allowed.
-
-This policy setting allows administrators to define applications for which they want this security feature to be prevented or allowed.
-
-If you enable this policy setting and enter a Value of 1 binary behaviors are prevented. If you enter a Value of 0 binary behaviors are allowed. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- Internet Explorer contains dynamic binary behaviors: components that encapsulate specific functionality for HTML elements to which they were attached. These binary behaviors are not controlled by any pages in zones such as Restricted Sites. In Windows XP Service Pack 2, there is a new Internet Explorer security setting for binary behaviors. This new binary behaviors security setting provides a general mitigation to vulnerabilities in Internet Explorer binary behaviors, and disables any binary behaviors for HTML rendering from the Restricted Sites zone by default.
- Internet Explorer uses Multipurpose Internet Mail Extensions (MIME) data to determine file handling procedures for files received through a Web server.
-
-This policy setting determines whether Internet Explorer requires that all file-type information provided by Web servers be consistent. For example, if the MIME type of a file is text/plain but the MIME sniff indicates that the file is really an executable file, Internet Explorer renames the file by saving it in the Internet Explorer cache and changing its extension.
-
-If you enable this policy setting, Consistent Mime Handling is enabled for all processes.
-
-If you disable or do not configure this policy setting, Consistent Mime Handling is prevented for all processes.
- Internet Explorer uses Multipurpose Internet Mail Extensions (MIME) data to determine file handling procedures for files received through a Web server.
-
-This policy setting determines whether Internet Explorer requires that all file-type information provided by Web servers be consistent. For example, if the MIME type of a file is text/plain but the MIME sniff indicates that the file is really an executable file, Internet Explorer renames the file by saving it in the Internet Explorer cache and changing its extension.
-
-If you enable this policy setting, Internet Explorer requires consistent MIME data for all received files.
-
-If you disable this policy setting, Internet Explorer will not require consistent MIME data for all received files.
-
-If you do not configure this policy setting, Internet Explorer requires consistent MIME data for all received files.
- Internet Explorer uses Multipurpose Internet Mail Extensions (MIME) data to determine file handling procedures for files received through a Web server.
-
-This policy setting determines whether Internet Explorer requires that all file-type information provided by Web servers be consistent. For example, if the MIME type of a file is text/plain but the MIME sniff indicates that the file is really an executable file, Internet Explorer renames the file by saving it in the Internet Explorer cache and changing its extension.
-
-This policy setting allows administrators to define applications for which they want this security feature to be prevented or allowed.
-
-If you enable this policy setting and enter a Value of 1, MIME handling is in effect. If you enter a Value of 0 file-type information is allowed to be inconsistent. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- Internet Explorer uses Multipurpose Internet Mail Extensions (MIME) type information to decide how to handle files that have been sent by a Web server. For example, when there is a Hypertext Transfer Protocol (HTTP) request for .jpg files, on receipt are generally displayed to the user in an Internet Explorer window. If Internet Explorer receives an executable file, Internet Explorer generally prompted the user for how to handle the file.
-
-In Windows XP Service Pack 2, Internet Explorer follows stricter rules that are designed to reduce the attack surface for spoofing the Internet Explorer MIME-handling logic.
-
-When files are served to the client, Internet Explorer uses the following pieces of information to decide how to handle the file:
-
-- File name extension
-- Content-Type from the HTTP header (MIME type)
-- Content-Disposition from the HTTP header
-- Results of the MIME sniff
-
-In Windows XP Service Pack 2, Internet Explorer requires that all file-type information that is provided by Web servers is consistent. For example, if the MIME type of a file is "text/plain" but the MIME sniff indicates that the file is really an executable file, Internet Explorer renames the file by saving the file in the Internet Explorer cache and changes its extension. (In a MIME sniff, Internet Explorer examines, or sniffs, a file to recognize the bit signatures of certain types of files.)
- This policy setting allows the user to run natively implemented, scriptable XMLHTTP.
-
-If you enable this policy setting, the user can run natively implemented, scriptable XMLHTTP.
-
-If you disable this policy setting, the user cannot run natively implemented, scriptable XMLHTTP.
-
-If you do not configure this policy setting, the user can choose to run natively implemented, scriptable XMLHTTP.
- This policy setting allows you to manage whether the Notification bar is displayed for processes other than the Internet Explorer processes when file or code installs are restricted. By default, the Notification bar is not displayed for any process when file or code installs are restricted (except for the Internet Explorer Processes, for which the Notification bar is displayed by default).
-
- If you enable this policy setting, the Notification bar will be displayed for all processes.
-
-If you disable or do not configure this policy setting, the Notification bar will not be displayed for all processes other than Internet Explorer or those listed in the Process List.
- This policy setting allows you to manage whether the Notification bar is displayed for Internet Explorer processes when file or code installs are restricted. By default, the Notification bar is displayed for Internet Explorer processes.
-
-If you enable this policy setting, the Notification bar will be displayed for Internet Explorer Processes.
-
-If you disable this policy setting, the Notification bar will not be displayed for Internet Explorer processes.
-
-If you do not configure this policy setting, the Notification bar will be displayed for Internet Explorer Processes.
- This policy setting allows you to manage whether the Notification bar is displayed for specific processes when file or code installs are restricted. By default, the Notification bar is not displayed for any process when file or code installs are restricted (except for the Internet Explorer Processes, for which the Notification bar is displayed by default).
-
-If you enable this policy setting and enter a Value of 1, the Notification bar is displayed. If you enter a Value of 0 the Notification bar is not displayed. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable for IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
- If you disable or do not configure this policy setting, the Notification bar is not displayed for the specified processes.
- Enables applications hosting the Web Browser Control to automatically show the Notification bar when file downloads or code installs are restricted.
- Internet Explorer places zone restrictions on each Web page it opens, which are dependent upon the location of the Web page (Internet, Intranet, Local Machine zone, etc.). Web pages on the local computer have the fewest security restrictions and reside in the Local Machine zone.
-
-Local Machine zone security applies to all local files and content. This feature helps to mitigate attacks where the Local Machine zone is used as an attack vector to load malicious HTML code.
-
-If you enable this policy setting, the Local Machine zone security applies to all local files and content processed by any process other than Internet Explorer or those defined in a process list.
-
-If you disable or do not configure this policy setting, Local Machine zone security is not applied to local files or content processed by any process other than Internet Explorer or those defined in a process list.
- Internet Explorer places zone restrictions on each Web page it opens, which are dependent upon the location of the Web page (Internet, Intranet, Local Machine zone, etc.). Web pages on the local computer have the fewest security restrictions and reside in the Local Machine zone.
-
-Local Machine zone security applies to all local files and content processed by Internet Explorer. This feature helps to mitigate attacks where the Local Machine zone is used as an attack vector to load malicious HTML code.
-
-If you enable this policy setting, the Local Machine zone security applies to all local files and content processed by Internet Explorer.
-
-If you disable this policy setting, Local Machine zone security is not applied to local files or content processed by Internet Explorer.
-
-If you do not configure this policy setting, the Local Machine zone security applies to all local files and content processed by Internet Explorer.
- Internet Explorer places zone restrictions on each Web page it opens, which are dependent upon the location of the Web page (Internet, Intranet, Local Machine zone, and so on). Web pages on the local computer have the fewest security restrictions and reside in the Local Machine zone.
-
-Local Machine zone security applies to all local files and content. This feature helps to mitigate attacks where the Local Machine zone is used as an attack vector to load malicious HTML code.
-
-If you enable this policy setting and enter a value of 1, Local Machine Zone security applies. If you enter a value of 0, Local Machine Zone security does not apply. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- When Internet Explorer opens a Web page, it places restrictions on what the page can do, based on the location of the Web page. For example, Web pages that are located on the Internet might not be able to perform some operations, such as accessing information from the local hard drive.
-
-On the other hand, Web pages on the local computer are in the Local Machine zone, where they have the fewest security restrictions. The Local Machine zone is an Internet Explorer security zone, but is not displayed in the settings for Internet Explorer. The Local Machine zone allows Web content to run with fewer restrictions. Unfortunately, attackers also try to take advantage of the Local Machine zone to elevate their privileges and compromise a computer.
-
-In Windows XP Service Pack 2, all local files and content that is processed by Internet Explorer has the security of the Local Machine zone applied to it. This differs from previous versions, where local content was considered to be secure and had no zone-based security was placed on it.
-
-This feature dramatically restricts HTML in the Local Machine zone and controls running in the Local Machine Zone. This helps to mitigate attacks where the Local Machine zone is used as an attack vector to load malicious code.
- This policy setting determines whether Internet Explorer MIME sniffing will prevent promotion of a file of one type to a more dangerous file type.
-
-If you enable this policy setting, the Mime Sniffing Safety Feature is enabled for all processes.
-
-If you disable or do not configure this policy setting, the Mime Sniffing Safety Feature is disabled for all processes.
- This policy setting determines whether Internet Explorer MIME sniffing will prevent promotion of a file of one type to a more dangerous file type.
-
-If you enable this policy setting, MIME sniffing will never promote a file of one type to a more dangerous file type.
-
-If you disable this policy setting, Internet Explorer processes will allow a MIME sniff promoting a file of one type to a more dangerous file type.
-
-If you do not configure this policy setting, MIME sniffing will never promote a file of one type to a more dangerous file type.
- This policy setting determines whether Internet Explorer MIME sniffing will prevent promotion of a file of one type to a more dangerous file type.
-
-This policy setting allows administrators to define applications for which they want this security feature to be prevented or allowed.
-
-If you enable this policy setting and enter a Value of 1, this protection will be in effect. If you enter a Value of 0, any file may be promoted to more dangerous file types. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- One of the backup criteria for determining a file type is the result of the MIME sniff. By examining (or sniffing) a file, Internet Explorer can recognize the bit signatures of certain types of files. In Windows XP Service Pack 2, Internet Explorer MIME sniffing will never promote a file of one type to a more dangerous file type. For example, files that are received as plain text but that include HTML code will not be promoted to the HTML type, which could contain malicious code.
-
-In the absence of other file type information, the MIME sniff might be the only information that determines how to handle a given file download. If, for instance, Internet Explorer upgrades a text file to an HTML file, the file might execute code from the browser and possibly elevate the file's security privilege.
-
-Settings note: this feature can be turned off by zone in IE security zones settings.
- The MK Protocol Security Restriction policy setting reduces attack surface area by preventing the MK protocol. Resources hosted on the MK protocol will fail.
-
-If you enable this policy setting, the MK Protocol is disabled for all processes. Any use of the MK Protocol is blocked.
-
-If you disable or do not configure this policy setting, the MK Protocol is enabled.
- The MK Protocol Security Restriction policy setting reduces attack surface area by preventing the MK protocol. Resources hosted on the MK protocol will fail.
-
-If you enable this policy setting, the MK Protocol is prevented for File Explorer and Internet Explorer, and resources hosted on the MK protocol will fail.
-
-If you disable this policy setting, applications can use the MK protocol API. Resources hosted on the MK protocol will work for the File Explorer and Internet Explorer processes.
-
-If you do not configure this policy setting, the MK Protocol is prevented for File Explorer and Internet Explorer, and resources hosted on the MK protocol will fail.
- The MK Protocol Security Restriction policy setting reduces attack surface area by preventing the MK protocol. Resources hosted on the MK protocol will fail.
-
-This policy setting allows administrators to define applications for which they want this security feature to be prevented or allowed.
-
-If you enable this policy setting and enter a Value of 1, use of the MK protocol is prevented. If you enter a Value of 0, use of the MK protocol is allowed. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the policy setting is ignored.
- In a reduction of attack surface, retired protocols are no longer supported. This feature disables the MK protocol. Resources hosted on the MK protocol will fail. Some legacy middleware apps may use this API, and this registry key can be set to allow them to continue to use it.
- Internet Explorer may be configured to prevent active content obtained through restricted protocols from running in an unsafe manner. This policy setting controls whether restricting content obtained through restricted protocols is prevented or allowed.
-
-If you enable this policy setting, restricting content obtained through restricted protocols is allowed for all processes other than File Explorer or Internet Explorer.
-
-If you disable this policy setting, restricting content obtained through restricted protocols is prevented for all processes other than File Explorer or Internet Explorer.
-
-If you do not configure this policy setting, no policy is enforced for processes other than File Explorer and Internet Explorer.
- File Explorer and Internet Explorer may be configured to prevent active content obtained through restricted protocols from running in an unsafe manner. This policy setting controls whether restricting content obtained through restricted protocols is prevented or allowed.
-
-If you enable this policy setting, restricting content obtained through restricted protocols is allowed for File Explorer and Internet Explorer processes. For example, you can restrict active content from pages served over the http and https protocols by adding the value names http and https.
-
-If you disable this policy setting, restricting content obtained through restricted protocols is prevented for File Explorer and Internet Explorer processes.
-
-If you do not configure this policy setting, the policy setting is ignored.
- Internet Explorer may be configured to prevent active content obtained through restricted protocols from running in an unsafe manner. This policy setting controls whether restricting content obtained through restricted protocols is prevented or allowed.
-
-This policy setting allows administrators to define applications for which they want restricting content obtained through restricted protocols to be prevented or allowed.
-
-If you enable this policy setting and enter a Value of 1, restricting content obtained through restricted protocols is allowed. If you enter a Value of 0, restricting content obtained through restricted protocols is blocked. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the File Explorer or Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable these processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- In File Explorer, Internet Explorer, or any other process which opts into the security restriction, Network Protocol Lockdown may be implemented in any security zone in order to prevent active content obtained through restricted protocols from running in an unsafe manner, if the target URL is in that zone. Each zone may be set to either prompt the user when such content attempts to run, or to simply disallow the content in that zone.
- This policy setting defines whether a reference to an object is accessible when the user navigates within the same domain or to a new domain.
-
-If you enable this policy setting, object reference is no longer accessible when navigating within or across domains for all processes.
-
-If you disable or do not configure this policy setting, object reference is retained when navigating within or across domains in the Restricted Zone sites.
- This policy setting defines whether a reference to an object is accessible when the user navigates within the same domain or to a new domain.
-
-If you enable this policy setting, an object reference is no longer accessible when navigating within or across domains for Internet Explorer processes.
-
-If you disable this policy setting, an object reference is retained when navigating within or across domains for Internet Explorer processes.
-
-If you do not configure this policy setting, an object reference is no longer accessible when navigating within or across domains for Internet Explorer processes.
- This policy setting defines whether a reference to an object is accessible when the user navigates within the same domain or to a new domain.
-
-This policy setting allows administrators to define applications for which they want this security feature to be prevented or allowed.
-
-If you enable this policy setting and enter a Value of 1, references to objects are inaccessible after navigation. If you enter a Value of 0, references to objects are still accessible after navigation. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- In previous versions of Windows with Internet Explorer, some Web pages could access objects cached from another Web site. In Windows XP Service Pack 2, a reference to an object is no longer accessible when the user navigates to a new domain.
-
-For Windows XP Service Pack 2, there is now a new security context on all scriptable objects so that access to all cached objects is blocked. In addition to blocking access when navigating across domains, access is also blocked when navigating within the same domain. (In this context, a domain is defined as a fully qualified domain name (FQDN)). A reference to an object is no longer accessible after the context has changed due to navigation.
- Internet Explorer places restrictions on each Web page it opens. The restrictions are dependent upon the location of the Web page (Internet, Intranet, Local Machine zone, and so on). For example, Web pages on the local computer have the fewest security restrictions and reside in the Local Machine zone, making the Local Machine security zone a prime target for malicious users.
-
-If you enable this policy setting, any zone can be protected from zone elevation for all processes.
-
-If you disable or do not configure this policy setting, processes other than Internet Explorer or those listed in the Process List receive no such protection.
- Internet Explorer places restrictions on each Web page it opens. The restrictions are dependent upon the location of the Web page (Internet, Intranet, Local Machine zone, etc.). Web pages on the local computer have the fewest security restrictions and reside in the Local Machine zone, making the Local Machine security zone a prime target for malicious users. Zone Elevation also disables JavaScript navigation if there is no security context.
-
-If you enable this policy setting, any zone can be protected from zone elevation by Internet Explorer processes.
-
-If you disable this policy setting, no zone receives such protection for Internet Explorer processes.
-
-If you do not configure this policy setting, any zone can be protected from zone elevation by Internet Explorer processes.
- Internet Explorer places restrictions on each Web page it opens. The restrictions are dependent upon the location of the Web page (Internet, Intranet, Local Machine zone, and so on). Web pages on the local computer have the fewest security restrictions and reside in the Local Machine zone, making the Local Machine security zone a prime target for malicious users. Zone Elevation also disables JavaScript navigation if there is no security context.
-
-This policy setting allows administrators to define applications for which they want this security feature to be prevented or allowed.
-
-If you enable this policy setting and enter a Value of 1, elevation to more privileged zones can be prevented. If you enter a Value of 0, elevation to any zone is allowed. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- When a Web page is opened in Internet Explorer, Internet Explorer puts restrictions on what the page can do, based on where that Web page came from: the Internet, a local intranet server, a trusted site, and so on. For example, pages on the Internet have stricter security restrictions than pages on a user's local intranet. Web pages on a user's computer are in the Local Machine security zone, where they have the fewest security restrictions. This makes the Local Machine security zone a prime target for malicious users. Zone Elevation Blocks makes it harder to get code to run in this zone. (As a separate feature, Local Machine Zone Lockdown makes the zone less vulnerable to malicious users by changing its security settings.)
-
-Internet Explorer prevents the overall security context for any link on a page from being higher than the security context of the root URL. This means, for example, that a page in the Internet zone cannot navigate to a page in the Local Intranet zone, except as the result of a user-initiated action. A script, for example, could not cause this navigation. For the purpose of this mitigation, the security context ranking of the zones, from highest security context to lowest, is: Restricted Sites zone, Internet zone, Local Intranet zone, Trusted Sites zone, and Local Machine zone.
-
-Zone Elevation also disables JavaScript navigation if there is no security context.
-
-Settings note: this feature can be turned off or set to prompt by zone in IE security zones settings.
- This policy setting enables applications hosting the Web Browser Control to block automatic prompting of ActiveX control installation.
-
-If you enable this policy setting, the Web Browser Control will block automatic prompting of ActiveX control installation for all processes.
-
-If you disable or do not configure this policy setting, the Web Browser Control will not block automatic prompting of ActiveX control installation for all processes.
- This policy setting enables blocking of ActiveX control installation prompts for Internet Explorer processes.
-
-If you enable this policy setting, prompting for ActiveX control installations will be blocked for Internet Explorer processes.
-
-If you disable this policy setting, prompting for ActiveX control installations will not be blocked for Internet Explorer processes.
-
-If you do not configure this policy setting, the user's preference will be used to determine whether to block ActiveX control installations for Internet Explorer processes.
- This policy setting enables applications hosting the Web Browser Control to block automatic prompting of ActiveX control installation.
-
-If you enable this policy setting and enter a Value of 1, automatic prompting of ActiveX control installation is blocked. If you enter a Value of 0, automatic prompting of ActiveX control installation is allowed. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- Enables applications hosting the Web Browser Control to block automatic prompting of ActiveX control installation. If a policy setting blocks prompting for an ActiveX control installation, the Notification bar appears instead.
- This policy setting enables applications hosting the Web Browser Control to block automatic prompting of file downloads that are not user initiated.
-
-If you enable this policy setting, the Web Browser Control will block automatic prompting of file downloads that are not user initiated for all processes.
-
-If you disable this policy setting, the Web Browser Control will not block automatic prompting of file downloads that are not user initiated for all processes.
- This policy setting enables blocking of file download prompts that are not user initiated.
-
-If you enable this policy setting, file download prompts that are not user initiated will be blocked for Internet Explorer processes.
-
-If you disable this policy setting, prompting will occur for file downloads that are not user initiated for Internet Explorer processes.
-
-If you do not configure this policy setting, the user's preference determines whether to prompt for file downloads that are not user initiated for Internet Explorer processes.
- This policy setting enables applications hosting the Web Browser Control to block automatic prompting of file downloads that are not user initiated.
-
-If you enable this policy setting and enter a Value of 1, automatic prompting of non-initiated file downloads is blocked. If you enter a Value of 0, automatic prompting of non-initiated file downloads is allowed. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- Enables applications hosting the Web Browser Control to block automatic prompting of file downloads that were not user initiated. If a policy setting blocks prompting for a file download, the Notification bar appears instead.
- Internet Explorer allows scripts to programmatically open, resize, and reposition windows of various types. The Window Restrictions security feature restricts popup windows and prohibits scripts from displaying windows in which the title and status bars are not visible to the user or obfuscate other Windows' title and status bars.
-
-If you enable this policy setting, scripted windows are restricted for all processes.
-
-If you disable or do not configure this policy setting, scripted windows are not restricted.
- Internet Explorer allows scripts to programmatically open, resize, and reposition windows of various types. The Window Restrictions security feature restricts popup windows and prohibits scripts from displaying windows in which the title and status bars are not visible to the user or obfuscate other Windows' title and status bars.
-
-If you enable this policy setting, popup windows and other restrictions apply for File Explorer and Internet Explorer processes.
-
-If you disable this policy setting, scripts can continue to create popup windows and windows that obfuscate other windows.
-
-If you do not configure this policy setting, popup windows and other restrictions apply for File Explorer and Internet Explorer processes.
- Internet Explorer allows scripts to programmatically open, resize, and reposition windows of various types. The Window Restrictions security feature restricts popup windows and prohibits scripts from displaying windows in which the title and status bars are not visible to the user or obfuscate other Windows' title and status bars.
-
-This policy setting allows administrators to define applications for which they want this security feature to be prevented or allowed.
-
-If you enable this policy setting and enter a Value of 1, such windows may not be opened. If you enter a Value of 0, windows have none of these restrictions. The Value Name is the name of the executable. If a Value Name is empty or the Value is not 0 or 1, the policy setting is ignored.
-
-Do not enter the Internet Explorer processes in this list: use the related Internet Explorer Processes policy to enable or disable IE processes. If the All Processes policy setting is enabled, the processes configured in this box take precedence over that setting.
-
-If you disable or do not configure this policy setting, the security feature is allowed.
- Internet Explorer provides the capability for scripts to programmatically open additional windows of various types, and to resize and reposition existing windows. The Window Restrictions security feature restricts two types of script-initiated windows that have been used by malicious persons to deceive users: popup windows (which do not have components such as the address bar, title bar, status bar, and toolbars) and windows that include the title bar and status bar.
-
-Script-initiated windows with the title bar and status bar are constrained in scripted movement to ensure that these important and informative bars remain visible after the operation completes.
-
-- Scripts cannot position windows so that the title bar or address bar are above the visible top of the display.
-- Scripts cannot position windows such that the status bar is below the visible bottom of the display.
-- Script-initiated windows that include a title bar and status bar are constrained in scripted sizing to ensure that the title bar and status bar remain visible after the operation completes.
-- Scripts cannot resize windows such that the title bar, address bar, or status bar cannot be seen.
-- When creating a window, the definition of the fullscreen=yes specification is changed to mean "show the window as maximized," which will keep the title bar, address bar, and status bar visible.
-
-Internet Explorer has been modified to not turn off the status bar for any windows. The status bar is always visible for all Internet Explorer windows.
-
-Script-initiated popup windows are now constrained so that they:
-
-- Do not extend above the top or below the bottom of the parent Internet Explorer Web Object Control (WebOC) window.
-- Are smaller in height than the parent WebOC window.
-- Overlap the parent window horizontally.
-- Stay with the parent window if the parent window moves.
-- Appear above its parent so other windows (such as a dialog box) cannot be hidden.
- Contains settings to enable or disable security features for Internet Explorer, File Explorer and other applications.
- Restricted Protocols Per Security Zone
- The list of restricted protocols governed by Network Protocol Lockdown varies per security zone. Use these policies to set the restricted protocol list for each zone.
-
-If policy is set in both Computer Configuration and User Configuration, the two lists are combined.
- Internet Zone Restricted Protocols
- Intranet Zone Restricted Protocols
- Local Machine Zone Restricted Protocols
- Restricted Sites Zone Restricted Protocols
- Trusted Sites Zone Restricted Protocols
- For each zone, the Network Protocol Lockdown security restriction may be configured to prevent active content obtained through restricted protocols from running in an unsafe manner, either by prompting the user, or simply disabling the content. For each zone, this list of protocols may be configured here, and applies to all processes which have opted in to the security restriction.
-
-If you enable this policy setting for a zone, this sets the list of protocols to be restricted if that zone is set to Prompt or Disable for "Allow active content over restricted protocols to access my computer."
-
-If you disable or do not configure this policy setting for a zone, no protocols are restricted for that zone, regardless of the setting for "Allow active content over restricted protocols to access my computer."
-
-Note. If policy for a zone is set in both Computer Configuration and User Configuration, both lists of protocols will be restricted for that zone.
- Admin-approved behaviors
- All Processes
- Internet Explorer Processes
- Process List
- Bypass prompting for Clipboard access for scripts running in any process
- Bypass prompting for Clipboard access for scripts running in the Internet Explorer process
- Define applications and processes that can access the Clipboard without prompting
- Automatically activate newly installed add-ons
- Turn off add-on performance notifications
- Internet Explorer
- Internet Settings
- Investor
- This policy setting controls whether local sites which are not explicitly mapped into any Security Zone are forced into the local Intranet security zone.
-
-If you enable this policy setting, local sites which are not explicitly mapped into a zone are considered to be in the Intranet Zone.
-
-If you disable this policy setting, local sites which are not explicitly mapped into a zone will not be considered to be in the Intranet Zone (so would typically be in the Internet Zone).
-
-If you do not configure this policy setting, users choose whether to force local sites into the Intranet Zone.
- Install binaries signed by MD2 and MD4 signing technologies
- This policy setting allows you to manage whether Internet Explorer 9 can install ActiveX controls and other binaries signed with MD2 and MD4 signing technologies. Internet Explorer 9 does not support MD2 and MD4 signing technologies by default, because they are not as secure as other technologies.
-
-If you enable this policy setting, Internet Explorer 9 installs binaries signed by MD2 and MD4 signing technologies.
-
-If you disable or do not configure this policy setting, Internet Explorer 9 does not install binaries signed by MD2 and MD4 signing technologies.
- This policy setting controls whether sites which bypass the proxy server are mapped into the local Intranet security zone.
-
-If you enable this policy setting, sites which bypass the proxy server are mapped into the Intranet Zone.
-
-If you disable this policy setting, sites which bypass the proxy server aren't necessarily mapped into the Intranet Zone (other rules might map one there).
-
-If you do not configure this policy setting, users choose whether sites which bypass the proxy server are mapped into the Intranet Zone.
- This policy setting controls whether URLs representing UNCs are mapped into the local Intranet security zone.
-
-If you enable this policy setting, all network paths are mapped into the Intranet Zone.
-
-If you disable this policy setting, network paths are not necessarily mapped into the Intranet Zone (other rules might map one there).
-
-If you do not configure this policy setting, users choose whether network paths are mapped into the Intranet Zone.
- This policy setting allows you to manage a list of sites that you want to associate with a particular security zone. These zone numbers have associated security settings that apply to all of the sites in the zone.
-
-Internet Explorer has 4 security zones, numbered 1-4, and these are used by this policy setting to associate sites to zones. They are: (1) Intranet zone, (2) Trusted Sites zone, (3) Internet zone, and (4) Restricted Sites zone. Security settings can be set for each of these zones through other policy settings, and their default settings are: Trusted Sites zone (Low template), Intranet zone (Medium-Low template), Internet zone (Medium template), and Restricted Sites zone (High template). (The Local Machine zone and its locked down equivalent have special security settings that protect your local computer.)
-
-If you enable this policy setting, you can enter a list of sites and their related zone numbers. The association of a site with a zone will ensure that the security settings for the specified zone are applied to the site. For each entry that you add to the list, enter the following information:
-
-Valuename – A host for an intranet site, or a fully qualified domain name for other sites. The valuename may also include a specific protocol. For example, if you enter http://www.contoso.com as the valuename, other protocols are not affected. If you enter just www.contoso.com, then all protocols are affected for that site, including http, https, ftp, and so on. The site may also be expressed as an IP address (e.g., 127.0.0.1) or range (e.g., 127.0.0.1-10). To avoid creating conflicting policies, do not include additional characters after the domain such as trailing slashes or URL path. For example, policy settings for www.contoso.com and www.contoso.com/mail would be treated as the same policy setting by Internet Explorer, and would therefore be in conflict.
-
-Value - A number indicating the zone with which this site should be associated for security settings. The Internet Explorer zones described above are 1-4.
-
-If you disable or do not configure this policy, users may choose their own site-to-zone assignments.
- This template policy setting allows you to configure policy settings in this zone consistent with a selected security level, for example, Low, Medium Low, Medium, or High.
-
-If you enable this template policy setting and select a security level, all values for individual settings in the zone will be overwritten by the standard template defaults.
-
-If you disable this template policy setting, no security level is configured.
-
-If you do not configure this template policy setting, no security level is configured.
-
-Note. Local Machine Zone Lockdown Security and Network Protocol Lockdown operate by comparing the settings in the active URL's zone against those in the Locked-Down equivalent zone. If you select a security level for any zone (including selecting no security), the same change should be made to the Locked-Down equivalent.
-
-Note. It is recommended to configure template policy settings in one Group Policy object (GPO) and configure any related individual policy settings in a separate GPO. You can then use Group Policy management features (for example, precedence, inheritance, or enforce) to apply individual settings to specific targets.
- Intranet Sites: Include all local (intranet) sites not listed in other zones
- Internet Zone
- Locked-Down Internet Zone
- The settings in this zone apply only if the Internet Zone is in 'lockdown' mode, such as when the Network Protocol Lockdown security feature is in effect. If the zone is locked down, these URL action settings do not override the standard Internet Zone settings, but are compared against them. If the settings for that URL action in the two zones are the same, then that setting is used. Otherwise, the user is presented with a Notification bar, and may allow the zone to operate with the standard (non-lockdown) zone's setting.
- Intranet Zone
- Locked-Down Intranet Zone
- The settings in this zone apply only if the Intranet Zone is in 'lockdown' mode, such as when the Network Protocol Lockdown security feature is in effect. If the zone is locked down, these URL action settings do not override the standard Intranet Zone settings, but are compared against them. If the settings for that URL action in the two zones are the same, then that setting is used. Otherwise, the user is presented with a Notification bar, and may allow the zone to operate with the standard (non-lockdown) zone's setting.
- Administrator approved
- Anonymous logon
- Automatic logon with current username and password
- Automatic logon only in Intranet zone
- Custom
- Disable
- Disable Java
- Enable
- High
- High safety
- Low
- Low safety
- Medium
- Medium High
- Medium Low
- Medium safety
- Prompt
- Prompt for user name and password
- Local Machine Zone
- Locked-Down Local Machine Zone
- The settings in this zone apply only if the Local Machine Zone is in 'lockdown' mode, such as when the Local Machine Zone Lockdown security feature is in effect. If the zone is locked down, these URL action settings do not override the standard Local Machine Zone settings, but are compared against them. If the settings for that URL action in the two zones are the same, then that setting is used. Otherwise, the user is presented with a Notification bar, and may allow the zone to operate with the standard (non-lockdown) zone's setting.
- Allow websites to open windows without status bar or Address bar
- This policy setting controls whether websites can open new Internet Explorer windows that have no status bar or Address bar.
-
-If you enable this policy setting, websites can open new Internet Explorer windows that have no status bar or Address bar.
-
-If you disable this policy setting, websites cannot open new Internet Explorer windows that have no status bar or Address bar.
-
-If you do not configure this policy setting, the user can choose whether websites can open new Internet Explorer Windows that have no status bar or Address bar.
- Allow only approved domains to use ActiveX controls without prompt
- This policy setting controls whether or not the user is prompted to allow ActiveX controls to run on websites other than the website that installed the ActiveX control.
-
-If you enable this policy setting, the user is prompted before ActiveX controls can run from websites in this zone. The user can choose to allow the control to run from the current site or from all sites.
-
-If you disable this policy setting, the user does not see the per-site ActiveX prompt, and ActiveX controls can run from all sites in this zone.
-Allow only approved domains to use the TDC ActiveX control
- This policy setting controls whether or not the user is allowed to run the TDC ActiveX control on websites.
-
-If you enable this policy setting, the TDC ActiveX control will not run from websites in this zone.
-
-If you disable this policy setting, the TDC Active X control will run from all sites in this zone.
- Allow video and animation on a webpage that uses an older media player
- This policy setting allows the playing of video and animation through older media players in specified zones. Video and animation playback through the object tag may still be allowed, because this involves external controls or media players.
-
-The dynsrc attribute on the img tag specifies an older media player. Also, as of Internet Explorer 8, this policy setting controls HTML+TIME media elements that refer to audio and video files.
-
-If you enable this policy setting, video and animation can be played through older media players in specified zones.
-
-If you disable this policy setting, video and animation cannot be played through older media players.
-
-If you do not configure this policy setting, video and animation can be played through older media players in specified zones.
- Allow scriptlets
- This policy setting allows you to manage whether the user can run scriptlets.
-
-If you enable this policy setting, the user can run scriptlets.
-
-If you disable this policy setting, the user cannot run scriptlets.
-
-If you do not configure this policy setting, the user can enable or disable scriptlets.
- Turn off first-run prompt
- Turn off first-run prompt
- This policy setting controls the first-run response that the user sees on a zone-by-zone basis. When the user encounters a new control that has not previously run in Internet Explorer, he or she may be prompted to approve the control. This policy setting determines whether the user is prompted.
-
-If you enable this policy setting, the first-run prompt is turned off in the corresponding zone.
-
-If you disable this policy setting, the first-run prompt is turned on in the corresponding zone.
-
-If you do not configure this policy setting, the first-run prompt is turned off by default.
- This policy setting controls the first-run response that the user sees on a zone-by-zone basis. When the user encounters a new control that has not previously run in Internet Explorer, he or she may be prompted to approve the control. This policy setting determines whether the user is prompted.
-
-If you enable this policy setting, the first-run prompt is turned off in the corresponding zone.
-
-If you disable this policy setting, the first-run prompt is turned on in the corresponding zone.
-
-If you do not configure this policy setting, the first-run prompt is turned on by default.
- Include local path when user is uploading files to a server
- This policy setting controls whether or not local path information is sent when the user is uploading a file via an HTML form. If the local path information is sent, some information may be unintentionally revealed to the server. For instance, files sent from the user's desktop may contain the user name as a part of the path.
-
-If you enable this policy setting, path information is sent when the user is uploading a file via an HTML form.
-
-If you disable this policy setting, path information is removed when the user is uploading a file via an HTML form.
-
-If you do not configure this policy setting, the user can choose whether path information is sent when he or she is uploading a file via an HTML form. By default, path information is sent.
- Turn on SmartScreen Filter scan
- This policy setting controls whether SmartScreen Filter scans pages in this zone for malicious content.
-
-If you enable this policy setting, SmartScreen Filter scans pages in this zone for malicious content.
-
-If you disable this policy setting, SmartScreen Filter does not scan pages in this zone for malicious content.
-
-If you do not configure this policy setting, the user can choose whether SmartScreen Filter scans pages in this zone for malicious content.
-
-Note: In Internet Explorer 7, this policy setting controls whether Phishing Filter scans pages in this zone for malicious content.
- Allow websites to prompt for information by using scripted windows
- This policy setting determines whether scripted windows are automatically displayed.
-
-If you enable this policy setting, scripted windows are displayed.
-
-If you disable this policy setting, the user must choose to display any scripted windows by using the Notification bar.
-
-If you do not configure this policy setting, the user can enable or disable the Notification bar behavior.
- Allow updates to status bar via script
- Allow updates to status bar via script
- This policy setting allows you to manage whether script is allowed to update the status bar within the zone.
-
-If you enable this policy setting, script is allowed to update the status bar.
-
-If you disable or do not configure this policy setting, script is not allowed to update the status bar.
- This policy setting allows you to manage whether script is allowed to update the status bar within the zone.
-
-If you enable this policy setting, script is allowed to update the status bar.
-
-If you disable or do not configure this policy setting, script is allowed to update the status bar.
- Turn on Protected Mode
- This policy setting allows you to turn on Protected Mode. Protected Mode helps protect Internet Explorer from exploited vulnerabilities by reducing the locations that Internet Explorer can write to in the registry and the file system.
-
-If you enable this policy setting, Protected Mode is turned on. The user cannot turn off Protected Mode.
-
-If you disable this policy setting, Protected Mode is turned off. The user cannot turn on Protected Mode.
-
-If you do not configure this policy setting, the user can turn on or turn off Protected Mode.
- Turn on Cross-Site Scripting Filter
- This policy controls whether or not the Cross-Site Scripting (XSS) Filter will detect and prevent cross-site script injections into websites in this zone.
-
-If you enable this policy setting, the XSS Filter is turned on for sites in this zone, and the XSS Filter attempts to block cross-site script injections.
-
-If you disable this policy setting, the XSS Filter is turned off for sites in this zone, and Internet Explorer permits cross-site script injections.
- Show security warning for potentially unsafe files
- This policy setting controls whether or not the "Open File - Security Warning" message appears when the user tries to open executable files or other potentially unsafe files (from an intranet file share by using File Explorer, for example).
-
-If you enable this policy setting and set the drop-down box to Enable, these files open without a security warning. If you set the drop-down box to Prompt, a security warning appears before the files open.
-
-If you disable this policy setting, these files do not open.
-
-If you do not configure this policy setting, the user can configure how the computer handles these files. By default, these files are blocked in the Restricted zone, enabled in the Intranet and Local Computer zones, and set to prompt in the Internet and Trusted zones.
- Allow loading of XAML Browser Applications
- This policy setting allows you to manage the loading of XAML Browser Applications (XBAPs). These are browser-hosted, ClickOnce-deployed applications built via WinFX. These applications run in a security sandbox and take advantage of the Windows Presentation Foundation platform for the web.
-
-If you enable this policy setting and set the drop-down box to Enable, XBAPs are automatically loaded inside Internet Explorer. The user cannot change this behavior. If you set the drop-down box to Prompt, the user is prompted for loading XBAPs.
-
-If you disable this policy setting, XBAPs are not loaded inside Internet Explorer. The user cannot change this behavior.
-
-If you do not configure this policy setting, the user can decide whether to load XBAPs inside Internet Explorer.
- Allow scripting of Internet Explorer WebBrowser controls
- This policy setting determines whether a page can control embedded WebBrowser controls via script.
-
-If you enable this policy setting, script access to the WebBrowser control is allowed.
-
-If you disable this policy setting, script access to the WebBrowser control is not allowed.
-
-If you do not configure this policy setting, the user can enable or disable script access to the WebBrowser control. By default, script access to the WebBrowser control is allowed only in the Local Machine and Intranet zones.
- Turn off .NET Framework Setup
- This policy setting prevents the user's computer from starting Microsoft .NET Framework Setup when the user is browsing to .NET Framework content in Internet Explorer. The .NET Framework is the next-generation platform for Windows. It uses the common language runtime and incorporates support from multiple developer tools. It includes the new managed code APIs for Windows.
-
-If you enable this policy setting, .NET Framework Setup is turned off. The user cannot change this behavior.
-
-If you disable this policy setting, .NET Framework Setup is turned on. The user cannot change this behavior.
-
-If you do not configure this policy setting, .NET Framework Setup is turned on by default. The user can change this behavior.
- Allow loading of XAML files
- This policy setting allows you to manage the loading of Extensible Application Markup Language (XAML) files. XAML is an XML-based declarative markup language commonly used for creating rich user interfaces and graphics that take advantage of the Windows Presentation Foundation.
-
-If you enable this policy setting and set the drop-down box to Enable, XAML files are automatically loaded inside Internet Explorer. The user cannot change this behavior. If you set the drop-down box to Prompt, the user is prompted for loading XAML files.
-
-If you disable this policy setting, XAML files are not loaded inside Internet Explorer. The user cannot change this behavior.
-
-If you do not configure this policy setting, the user can decide whether to load XAML files inside Internet Explorer.
- Allow loading of XPS files
- This policy setting allows you to manage the loading of XPS files. These files contain a fixed-layout representation of paginated content and are portable across platforms, devices, and applications.
-
-If you enable this policy setting and set the drop-down box to Enable, XPS files are automatically loaded inside Internet Explorer. The user cannot change this behavior. If you set the drop-down box to Prompt, the user is prompted for loading XPS files.
-
-If you disable this policy setting, XPS files are not loaded inside Internet Explorer. The user cannot change this behavior.
-
-If you do not configure this policy setting, the user can decide whether to load XPS files inside Internet Explorer.
- Access data sources across domains
- This policy setting allows you to manage whether Internet Explorer can access data from another security zone using the Microsoft XML Parser (MSXML) or ActiveX Data Objects (ADO).
-
-If you enable this policy setting, users can load a page in the zone that uses MSXML or ADO to access data from another site in the zone. If you select Prompt in the drop-down box, users are queried to choose whether to allow a page to be loaded in the zone that uses MSXML or ADO to access data from another site in the zone.
-
-If you disable this policy setting, users cannot load a page in the zone that uses MSXML or ADO to access data from another site in the zone.
-
-If you do not configure this policy setting, users cannot load a page in the zone that uses MSXML or ADO to access data from another site in the zone.
- This policy setting allows you to manage whether Internet Explorer can access data from another security zone using the Microsoft XML Parser (MSXML) or ActiveX Data Objects (ADO).
-
-If you enable this policy setting, users can load a page in the zone that uses MSXML or ADO to access data from another site in the zone. If you select Prompt in the drop-down box, users are queried to choose whether to allow a page to be loaded in the zone that uses MSXML or ADO to access data from another site in the zone.
-
-If you disable this policy setting, users cannot load a page in the zone that uses MSXML or ADO to access data from another site in the zone.
-
-If you do not configure this policy setting, users can load a page in the zone that uses MSXML or ADO to access data from another site in the zone.
- This policy setting allows you to manage whether Internet Explorer can access data from another security zone using the Microsoft XML Parser (MSXML) or ActiveX Data Objects (ADO).
-
-If you enable this policy setting, users can load a page in the zone that uses MSXML or ADO to access data from another site in the zone. If you select Prompt in the drop-down box, users are queried to choose whether to allow a page to be loaded in the zone that uses MSXML or ADO to access data from another site in the zone.
-
-If you disable this policy setting, users cannot load a page in the zone that uses MSXML or ADO to access data from another site in the zone.
-
-If you do not configure this policy setting, users are queried to choose whether to allow a page to be loaded in the zone that uses MSXML or ADO to access data from another site in the zone.
- Allow active scripting
- This policy setting allows you to manage whether script code on pages in the zone is run.
-
-If you enable this policy setting, script code on pages in the zone can run automatically. If you select Prompt in the drop-down box, users are queried to choose whether to allow script code on pages in the zone to run.
-
-If you disable this policy setting, script code on pages in the zone is prevented from running.
-
-If you do not configure this policy setting, script code on pages in the zone is prevented from running.
- This policy setting allows you to manage whether script code on pages in the zone is run.
-
-If you enable this policy setting, script code on pages in the zone can run automatically. If you select Prompt in the drop-down box, users are queried to choose whether to allow script code on pages in the zone to run.
-
-If you disable this policy setting, script code on pages in the zone is prevented from running.
-
-If you do not configure this policy setting, script code on pages in the zone can run automatically.
- This policy setting allows you to manage whether script code on pages in the zone is run.
-
-If you enable this policy setting, script code on pages in the zone can run automatically. If you select Prompt in the drop-down box, users are queried to choose whether to allow script code on pages in the zone to run.
-
-If you disable this policy setting, script code on pages in the zone is prevented from running.
-
-If you do not configure this policy setting, users are queried to choose whether to allow script code on pages in the Local Machine zone to run.
- Allow META REFRESH
- This policy setting allows you to manage whether a user's browser can be redirected to another Web page if the author of the Web page uses the Meta Refresh setting (tag) to redirect browsers to another Web page.
-
-If you enable this policy setting, a user's browser that loads a page containing an active Meta Refresh setting can be redirected to another Web page.
-
-If you disable this policy setting, a user's browser that loads a page containing an active Meta Refresh setting cannot be redirected to another Web page.
-
-If you do not configure this policy setting, a user's browser that loads a page containing an active Meta Refresh setting cannot be redirected to another Web page.
- This policy setting allows you to manage whether a user's browser can be redirected to another Web page if the author of the Web page uses the Meta Refresh setting (tag) to redirect browsers to another Web page.
-
-If you enable this policy setting, a user's browser that loads a page containing an active Meta Refresh setting can be redirected to another Web page.
-
-If you disable this policy setting, a user's browser that loads a page containing an active Meta Refresh setting cannot be redirected to another Web page.
-
-If you do not configure this policy setting, a user's browser that loads a page containing an active Meta Refresh setting can be redirected to another Web page.
- Allow cut, copy or paste operations from the clipboard via script
- This policy setting allows you to manage whether scripts can perform a clipboard operation (for example, cut, copy, and paste) in a specified region.
-
-If you enable this policy setting, a script can perform a clipboard operation.
-
-If you select Prompt in the drop-down box, users are queried as to whether to perform clipboard operations.
-
-If you disable this policy setting, a script cannot perform a clipboard operation.
-
-If you do not configure this policy setting, a script cannot perform a clipboard operation.
- This policy setting allows you to manage whether scripts can perform a clipboard operation (for example, cut, copy, and paste) in a specified region.
-
-If you enable this policy setting, a script can perform a clipboard operation.
-
-If you select Prompt in the drop-down box, users are queried as to whether to perform clipboard operations.
-
-If you disable this policy setting, a script cannot perform a clipboard operation.
-
-If you do not configure this policy setting, a script can perform a clipboard operation.
- Allow binary and script behaviors
- This policy setting allows you to manage dynamic binary and script behaviors: components that encapsulate specific functionality for HTML elements to which they were attached.
-
-If you enable this policy setting, binary and script behaviors are available. If you select Administrator approved in the drop-down box, only behaviors listed in the Admin-approved Behaviors under Binary Behaviors Security Restriction policy are available.
-
-If you disable this policy setting, binary and script behaviors are not available unless applications have implemented a custom security manager.
-
-If you do not configure this policy setting, only behaviors listed in the Admin-approved Behaviors under Binary Behaviors Security Restriction policy are available.
- This policy setting allows you to manage dynamic binary and script behaviors: components that encapsulate specific functionality for HTML elements to which they were attached.
-
-If you enable this policy setting, binary and script behaviors are available. If you select Administrator approved in the drop-down box, only behaviors listed in the Admin-approved Behaviors under Binary Behaviors Security Restriction policy are available.
-
-If you disable this policy setting, binary and script behaviors are not available unless applications have implemented a custom security manager.
-
-If you do not configure this policy setting, binary and script behaviors are not available unless applications have implemented a custom security manager.
- This policy setting allows you to manage dynamic binary and script behaviors: components that encapsulate specific functionality for HTML elements to which they were attached.
-
-If you enable this policy setting, binary and script behaviors are available. If you select Administrator approved in the drop-down box, only behaviors listed in the Admin-approved Behaviors under Binary Behaviors Security Restriction policy are available.
-
-If you disable this policy setting, binary and script behaviors are not available unless applications have implemented a custom security manager.
-
-If you do not configure this policy setting, binary and script behaviors are available.
- Use Pop-up Blocker
- This policy setting allows you to manage whether unwanted pop-up windows appear. Pop-up windows that are opened when the end user clicks a link are not blocked.
-
-If you enable this policy setting, most unwanted pop-up windows are prevented from appearing.
-
-If you disable this policy setting, pop-up windows are not prevented from appearing.
-
-If you do not configure this policy setting, pop-up windows are not prevented from appearing.
- This policy setting allows you to manage whether unwanted pop-up windows appear. Pop-up windows that are opened when the end user clicks a link are not blocked.
-
-If you enable this policy setting, most unwanted pop-up windows are prevented from appearing.
-
-If you disable this policy setting, pop-up windows are not prevented from appearing.
-
-If you do not configure this policy setting, most unwanted pop-up windows are prevented from appearing.
- Display mixed content
- This policy setting allows you to manage whether users can display nonsecure items and manage whether users receive a security information message to display pages containing both secure and nonsecure items.
-
-If you enable this policy setting, and the drop-down box is set to Enable, the user does not receive a security information message (This page contains both secure and nonsecure items. Do you want to display the nonsecure items?) and nonsecure content can be displayed.
-
-If the drop-down box is set to Prompt, the user will receive the security information message on the Web pages that contain both secure (https://) and nonsecure (http://) content.
-
-If you disable this policy setting, users cannot receive the security information message and nonsecure content cannot be displayed.
-
-If you do not configure this policy setting, the user will receive the security information message on the Web pages that contain both secure (https://) and nonsecure (http://) content.
- Download signed ActiveX controls
- This policy setting allows you to manage whether users may download signed ActiveX controls from a page in the zone.
-
-If you enable this policy, users can download signed controls without user intervention. If you select Prompt in the drop-down box, users are queried whether to download controls signed by publishers who aren't trusted. Code signed by trusted publishers is silently downloaded.
-
-If you disable the policy setting, signed controls cannot be downloaded.
-
-If you do not configure this policy setting, signed controls cannot be downloaded.
- This policy setting allows you to manage whether users may download signed ActiveX controls from a page in the zone.
-
-If you enable this policy, users can download signed controls without user intervention. If you select Prompt in the drop-down box, users are queried whether to download controls signed by publishers who aren't trusted. Code signed by trusted publishers is silently downloaded.
-
-If you disable the policy setting, signed controls cannot be downloaded.
-
-If you do not configure this policy setting, users can download signed controls without user intervention.
- This policy setting allows you to manage whether users may download signed ActiveX controls from a page in the zone.
-
-If you enable this policy, users can download signed controls without user intervention. If you select Prompt in the drop-down box, users are queried whether to download controls signed by publishers who aren't trusted. Code signed by trusted publishers is silently downloaded.
-
-If you disable the policy setting, signed controls cannot be downloaded.
-
-If you do not configure this policy setting, users are queried whether to download controls signed by publishers who aren't trusted. Code signed by trusted publishers is silently downloaded.
- Download unsigned ActiveX controls
- This policy setting allows you to manage whether users may download unsigned ActiveX controls from the zone. Such code is potentially harmful, especially when coming from an untrusted zone.
-
-If you enable this policy setting, users can run unsigned controls without user intervention. If you select Prompt in the drop-down box, users are queried to choose whether to allow the unsigned control to run.
-
-If you disable this policy setting, users cannot run unsigned controls.
-
-If you do not configure this policy setting, users cannot run unsigned controls.
- This policy setting allows you to manage whether users may download unsigned ActiveX controls from the zone. Such code is potentially harmful, especially when coming from an untrusted zone.
-
-If you enable this policy setting, users can run unsigned controls without user intervention. If you select Prompt in the drop-down box, users are queried to choose whether to allow the unsigned control to run.
-
-If you disable this policy setting, users cannot run unsigned controls.
-
-If you do not configure this policy setting, users can run unsigned controls without user intervention.
- This policy setting allows you to manage whether users may download unsigned ActiveX controls from the zone. Such code is potentially harmful, especially when coming from an untrusted zone.
-
-If you enable this policy setting, users can run unsigned controls without user intervention. If you select Prompt in the drop-down box, users are queried to choose whether to allow the unsigned control to run.
-
-If you disable this policy setting, users cannot run unsigned controls.
-
-If you do not configure this policy setting, users are queried to choose whether to allow the unsigned control to run.
- Allow drag and drop or copy and paste files
- This policy setting allows you to manage whether users can drag files or copy and paste files from a source within the zone.
-
-If you enable this policy setting, users can drag files or copy and paste files from this zone automatically. If you select Prompt in the drop-down box, users are queried to choose whether to drag or copy files from this zone.
-
-If you disable this policy setting, users are prevented from dragging files or copying and pasting files from this zone.
-
-If you do not configure this policy setting, users can drag files or copy and paste files from this zone automatically.
- This policy setting allows you to manage whether users can drag files or copy and paste files from a source within the zone.
-
-If you enable this policy setting, users can drag files or copy and paste files from this zone automatically. If you select Prompt in the drop-down box, users are queried to choose whether to drag or copy files from this zone.
-
-If you disable this policy setting, users are prevented from dragging files or copying and pasting files from this zone.
-
-If you do not configure this policy setting, users are queried to choose whether to drag or copy files from this zone.
-
- Render legacy filters
- This policy setting specifies whether Internet Explorer renders legacy visual filters in this zone.
-
-If you enable this policy setting, you can control whether or not Internet Explorer renders legacy filters by selecting Enable, or Disable, under Options in Group Policy Editor.
-
-If you disable, or do not configure this policy setting, users can choose whether or not to render filters in this zone. Users can change this setting on the Security tab of the Internet Options dialog box. Filters are not rendered by default in this zone.
-
- This policy setting specifies whether Internet Explorer renders legacy visual filters in this zone.
-
-If you enable this policy setting, you can control whether or not Internet Explorer renders legacy filters by selecting Enable, or Disable, under Options in Group Policy Editor.
-
-If you disable, or do not configure this policy setting, users can choose whether or not to render filters in this zone. Users can change this setting on the Security tab of the Internet Options dialog box. Filters are rendered by default in this zone.
-
- Allow file downloads
- This policy setting allows you to manage whether file downloads are permitted from the zone. This option is determined by the zone of the page with the link causing the download, not the zone from which the file is delivered.
-
-If you enable this policy setting, files can be downloaded from the zone.
-
-If you disable this policy setting, files are prevented from being downloaded from the zone.
-
- If you do not configure this policy setting, files are prevented from being downloaded from the zone.
- This policy setting allows you to manage whether file downloads are permitted from the zone. This option is determined by the zone of the page with the link causing the download, not the zone from which the file is delivered.
-
-If you enable this policy setting, files can be downloaded from the zone.
-
-If you disable this policy setting, files are prevented from being downloaded from the zone.
-
- If you do not configure this policy setting, files can be downloaded from the zone.
- Allow font downloads
- This policy setting allows you to manage whether pages of the zone may download HTML fonts.
-
-If you enable this policy setting, HTML fonts can be downloaded automatically. If you enable this policy setting and Prompt is selected in the drop-down box, users are queried whether to allow HTML fonts to download.
-
-If you disable this policy setting, HTML fonts are prevented from downloading.
-
-If you do not configure this policy setting, HTML fonts can be downloaded automatically.
- This policy setting allows you to manage whether pages of the zone may download HTML fonts.
-
-If you enable this policy setting, HTML fonts can be downloaded automatically. If you enable this policy setting and Prompt is selected in the drop-down box, users are queried whether to allow HTML fonts to download.
-
-If you disable this policy setting, HTML fonts are prevented from downloading.
-
-If you do not configure this policy setting, users are queried whether to allow HTML fonts to download.
- Allow installation of desktop items
- This policy setting allows you to manage whether users can install Active Desktop items from this zone. The settings for this option are: If you enable this policy setting, users can install desktop items from this zone automatically.
-
-If you select Prompt in the drop-down box, users are queried to choose whether to install desktop items from this zone.
-
-If you disable this policy setting, users are prevented from installing desktop items from this zone.
-
-If you do not configure this policy setting, users are prevented from installing desktop items from this zone.
- This policy setting allows you to manage whether users can install Active Desktop items from this zone. The settings for this option are: If you enable this policy setting, users can install desktop items from this zone automatically.
-
-If you select Prompt in the drop-down box, users are queried to choose whether to install desktop items from this zone.
-
-If you disable this policy setting, users are prevented from installing desktop items from this zone.
-
-If you do not configure this policy setting, users can install desktop items from this zone automatically.
- This policy setting allows you to manage whether users can install Active Desktop items from this zone. The settings for this option are: If you enable this policy setting, users can install desktop items from this zone automatically.
-
-If you select Prompt in the drop-down box, users are queried to choose whether to install desktop items from this zone.
-
-If you disable this policy setting, users are prevented from installing desktop items from this zone.
-
-If you do not configure this policy setting, users are queried to choose whether to install desktop items from this zone.
- Locked-Down Internet Zone Template
- Internet Zone Template
- Locked-Down Intranet Zone Template
- Intranet Zone Template
- Java permissions
- This policy setting allows you to manage permissions for Java applets.
-
-If you enable this policy setting, you can choose options from the drop-down box. Custom, to control permissions settings individually.
-
-Low Safety enables applets to perform all operations.
-
-Medium Safety enables applets to run in their sandbox (an area in memory outside of which the program cannot make calls), plus capabilities like scratch space (a safe and secure storage area on the client computer) and user-controlled file I/O.
-
-High Safety enables applets to run in their sandbox. Disable Java to prevent any applets from running.
-
-If you disable this policy setting, Java applets cannot run.
-
-If you do not configure this policy setting, Java applets are disabled.
- This policy setting allows you to manage permissions for Java applets.
-
-If you enable this policy setting, you can choose options from the drop-down box. Custom, to control permissions settings individually.
-
-Low Safety enables applets to perform all operations.
-
-Medium Safety enables applets to run in their sandbox (an area in memory outside of which the program cannot make calls), plus capabilities like scratch space (a safe and secure storage area on the client computer) and user-controlled file I/O.
-
-High Safety enables applets to run in their sandbox. Disable Java to prevent any applets from running.
-
-If you disable this policy setting, Java applets cannot run.
-
-If you do not configure this policy setting, the permission is set to High Safety.
- This policy setting allows you to manage permissions for Java applets.
-
-If you enable this policy setting, you can choose options from the drop-down box. Custom, to control permissions settings individually.
-
-Low Safety enables applets to perform all operations.
-
-Medium Safety enables applets to run in their sandbox (an area in memory outside of which the program cannot make calls), plus capabilities like scratch space (a safe and secure storage area on the client computer) and user-controlled file I/O.
-
-High Safety enables applets to run in their sandbox. Disable Java to prevent any applets from running.
-
-If you disable this policy setting, Java applets cannot run.
-
-If you do not configure this policy setting, the permission is set to Low Safety.
- This policy setting allows you to manage permissions for Java applets.
-
-If you enable this policy setting, you can choose options from the drop-down box. Custom, to control permissions settings individually.
-
-Low Safety enables applets to perform all operations.
-
-Medium Safety enables applets to run in their sandbox (an area in memory outside of which the program cannot make calls), plus capabilities like scratch space (a safe and secure storage area on the client computer) and user-controlled file I/O.
-
-High Safety enables applets to run in their sandbox. Disable Java to prevent any applets from running.
-
-If you disable this policy setting, Java applets cannot run.
-
-If you do not configure this policy setting, the permission is set to Medium Safety.
- Launching applications and files in an IFRAME
- This policy setting allows you to manage whether applications may be run and files may be downloaded from an IFRAME reference in the HTML of the pages in this zone.
-
-If you enable this policy setting, users can run applications and download files from IFRAMEs on the pages in this zone without user intervention. If you select Prompt in the drop-down box, users are queried to choose whether to run applications and download files from IFRAMEs on the pages in this zone.
-
-If you disable this policy setting, users are prevented from running applications and downloading files from IFRAMEs on the pages in this zone.
-
-If you do not configure this policy setting, users are prevented from running applications and downloading files from IFRAMEs on the pages in this zone.
- This policy setting allows you to manage whether applications may be run and files may be downloaded from an IFRAME reference in the HTML of the pages in this zone.
-
-If you enable this policy setting, users can run applications and download files from IFRAMEs on the pages in this zone without user intervention. If you select Prompt in the drop-down box, users are queried to choose whether to run applications and download files from IFRAMEs on the pages in this zone.
-
-If you disable this policy setting, users are prevented from running applications and downloading files from IFRAMEs on the pages in this zone.
-
-If you do not configure this policy setting, users can run applications and download files from IFRAMEs on the pages in this zone without user intervention.
- This policy setting allows you to manage whether applications may be run and files may be downloaded from an IFRAME reference in the HTML of the pages in this zone.
-
-If you enable this policy setting, users can run applications and download files from IFRAMEs on the pages in this zone without user intervention. If you select Prompt in the drop-down box, users are queried to choose whether to run applications and download files from IFRAMEs on the pages in this zone.
-
-If you disable this policy setting, users are prevented from running applications and downloading files from IFRAMEs on the pages in this zone.
-
-If you do not configure this policy setting, users are queried to choose whether to run applications and download files from IFRAMEs on the pages in this zone.
- Locked-Down Local Machine Zone Template
- Local Machine Zone Template
- Logon options
- This policy setting allows you to manage settings for logon options.
-
-If you enable this policy setting, you can choose from the following logon options.
-
-Anonymous logon to disable HTTP authentication and use the guest account only for the Common Internet File System (CIFS) protocol.
-
-Prompt for user name and password to query users for user IDs and passwords. After a user is queried, these values can be used silently for the remainder of the session.
-
-Automatic logon only in Intranet zone to query users for user IDs and passwords in other zones. After a user is queried, these values can be used silently for the remainder of the session.
-
-Automatic logon with current user name and password to attempt logon using Windows NT Challenge Response (also known as NTLM authentication). If Windows NT Challenge Response is supported by the server, the logon uses the user's network user name and password for logon. If Windows NT Challenge Response is not supported by the server, the user is queried to provide the user name and password.
-
-If you disable this policy setting, logon is set to Automatic logon only in Intranet zone.
-
-If you do not configure this policy setting, logon is set to Automatic logon with current username and password.
- This policy setting allows you to manage settings for logon options.
-
-If you enable this policy setting, you can choose from the following logon options.
-
-Anonymous logon to disable HTTP authentication and use the guest account only for the Common Internet File System (CIFS) protocol.
-
-Prompt for user name and password to query users for user IDs and passwords. After a user is queried, these values can be used silently for the remainder of the session.
-
-Automatic logon only in Intranet zone to query users for user IDs and passwords in other zones. After a user is queried, these values can be used silently for the remainder of the session.
-
-Automatic logon with current user name and password to attempt logon using Windows NT Challenge Response (also known as NTLM authentication). If Windows NT Challenge Response is supported by the server, the logon uses the user's network user name and password for logon. If Windows NT Challenge Response is not supported by the server, the user is queried to provide the user name and password.
-
-If you disable this policy setting, logon is set to Automatic logon only in Intranet zone.
-
-If you do not configure this policy setting, logon is set to Automatic logon only in Intranet zone.
- This policy setting allows you to manage settings for logon options.
-
-If you enable this policy setting, you can choose from the following logon options.
-
-Anonymous logon to disable HTTP authentication and use the guest account only for the Common Internet File System (CIFS) protocol.
-
-Prompt for user name and password to query users for user IDs and passwords. After a user is queried, these values can be used silently for the remainder of the session.
-
-Automatic logon only in Intranet zone to query users for user IDs and passwords in other zones. After a user is queried, these values can be used silently for the remainder of the session.
-
-Automatic logon with current user name and password to attempt logon using Windows NT Challenge Response (also known as NTLM authentication). If Windows NT Challenge Response is supported by the server, the logon uses the user's network user name and password for logon. If Windows NT Challenge Response is not supported by the server, the user is queried to provide the user name and password.
-
-If you disable this policy setting, logon is set to Automatic logon only in Intranet zone.
-
-If you do not configure this policy setting, logon is set to Prompt for username and password.
- Enable MIME Sniffing
- This policy setting allows you to manage MIME sniffing for file promotion from one type to another based on a MIME sniff. A MIME sniff is the recognition by Internet Explorer of the file type based on a bit signature.
-
-If you enable this policy setting, the MIME Sniffing Safety Feature will not apply in this zone. The security zone will run without the added layer of security provided by this feature.
-
-If you disable this policy setting, the actions that may be harmful cannot run; this Internet Explorer security feature will be turned on in this zone, as dictated by the feature control setting for the process.
-
-If you do not configure this policy setting, the actions that may be harmful cannot run; this Internet Explorer security feature will be turned on in this zone, as dictated by the feature control setting for the process.
- This policy setting allows you to manage MIME sniffing for file promotion from one type to another based on a MIME sniff. A MIME sniff is the recognition by Internet Explorer of the file type based on a bit signature.
-
-If you enable this policy setting, the MIME Sniffing Safety Feature will not apply in this zone. The security zone will run without the added layer of security provided by this feature.
-
-If you disable this policy setting, the actions that may be harmful cannot run; this Internet Explorer security feature will be turned on in this zone, as dictated by the feature control setting for the process.
-
-If you do not configure this policy setting, the MIME Sniffing Safety Feature will not apply in this zone.
- Enable dragging of content from different domains within a window
- This policy setting allows you to set options for dragging content from one domain to a different domain when the source and destination are in the same window.
-
-If you enable this policy setting and click Enable, users can drag content from one domain to a different domain when the source and destination are in the same window. Users cannot change this setting.
-
-If you enable this policy setting and click Disable, users cannot drag content from one domain to a different domain when the source and destination are in the same window. Users cannot change this setting in the Internet Options dialog.
-
-In Internet Explorer 10, if you disable this policy setting or do not configure it, users cannot drag content from one domain to a different domain when the source and destination are in the same window. Users can change this setting in the Internet Options dialog.
-
-In Internet Explorer 9 and earlier versions, if you disable this policy setting or do not configure it, users can drag content from one domain to a different domain when the source and destination are in the same window. Users cannot change this setting in the Internet Options dialog.
- Enable dragging of content from different domains across windows
- This policy setting allows you to set options for dragging content from one domain to a different domain when the source and destination are in different windows.
-
-If you enable this policy setting and click Enable, users can drag content from one domain to a different domain when the source and destination are in different windows. Users cannot change this setting.
-
-If you enable this policy setting and click Disable, users cannot drag content from one domain to a different domain when both the source and destination are in different windows. Users cannot change this setting.
-
-In Internet Explorer 10, if you disable this policy setting or do not configure it, users cannot drag content from one domain to a different domain when the source and destination are in different windows. Users can change this setting in the Internet Options dialog.
-
-In Internet Explorer 9 and earlier versions, if you disable this policy or do not configure it, users can drag content from one domain to a different domain when the source and destination are in different windows. Users cannot change this setting.
- Navigate windows and frames across different domains
- This policy setting allows you to manage the opening of windows and frames and access of applications across different domains.
-
-If you enable this policy setting, users can open additional windows and frames from other domains and access applications from other domains. If you select Prompt in the drop-down box, users are queried whether to allow additional windows and frames to access applications from other domains.
-
-If you disable this policy setting, users cannot open other windows and frames from other domains or access applications from different domains.
-
-If you do not configure this policy setting, users cannot open other windows and frames from different domains or access applications from different domains.
- This policy setting allows you to manage the opening of windows and frames and access of applications across different domains.
-
-If you enable this policy setting, users can open windows and frames from othe domains and access applications from other domains. If you select Prompt in the drop-down box, users are queried whether to allow windows and frames to access applications from other domains.
-
-If you disable this policy setting, users cannot open windows and frames to access applications from different domains.
-
-If you do not configure this policy setting, users can open windows and frames from othe domains and access applications from other domains.
- Allow active content over restricted protocols to access my computer
- This policy setting allows you to manage whether a resource hosted on an admin-restricted protocol in the Trusted Sites Zone can run active content such as script, ActiveX, Java and Binary Behaviors. The list of restricted protocols may be set in the Trusted Sites Zone Restricted Protocols section under Network Protocol Lockdown policy.
-
-If you enable this policy setting, no Trusted Sites Zone content accessed is affected, even for protocols on the restricted list. If you select Prompt from the drop-down box, the Notification bar will appear to allow control over questionable content accessed over any restricted protocols; content over other protocols is unaffected.
-
-If you disable this policy setting, all attempts to access such content over the restricted protocols is blocked.
-
-If you do not configure this policy setting, all attempts to access such content over the restricted protocols is blocked when the Network Protocol Lockdown security feature is enabled.
- This policy setting allows you to manage whether a resource hosted on an admin-restricted protocol in the Intranet Zone can run active content such as script, ActiveX, Java and Binary Behaviors. The list of restricted protocols may be set in the Intranet Zone Restricted Protocols section under Network Protocol Lockdown policy.
-
-If you enable this policy setting, no Intranet Zone content accessed is affected, even for protocols on the restricted list. If you select Prompt from the drop-down box, the Notification bar will appear to allow control over questionable content accessed over any restricted protocols; content over other protocols is unaffected.
-
-If you disable this policy setting, all attempts to access such content over the restricted protocols is blocked.
-
-If you do not configure this policy setting, the Notification bar will appear to allow control over questionable content accessed over any restricted protocols when the Network Protocol Lockdown security feature is enabled.
- Do not prompt for client certificate selection when no certificates or only one certificate exists.
- This policy setting allows you to manage whether users are prompted to select a certificate when no certificate or only one certificate exists.
-
-If you enable this policy setting, Internet Explorer does not prompt users with a "Client Authentication" message when they connect to a Web site that has no certificate or only one certificate.
-
-If you disable this policy setting, Internet Explorer prompts users with a "Client Authentication" message when they connect to a Web site that has no certificate or only one certificate.
-
-If you do not configure this policy setting, Internet Explorer prompts users with a Client Authentication message when they connect to a Web site that has no certificate or only one certificate.
- This policy setting allows you to manage whether users are prompted to select a certificate when no certificate or only one certificate exists.
-
-If you enable this policy setting, Internet Explorer does not prompt users with a "Client Authentication" message when they connect to a Web site that has no certificate or only one certificate.
-
-If you disable this policy setting, Internet Explorer prompts users with a "Client Authentication" message when they connect to a Web site that has no certificate or only one certificate.
-
-If you do not configure this policy setting, Internet Explorer does not prompt users with a "Client Authentication" message when they connect to a Web site that has no certificate or only one certificate.
- Automatic prompting for ActiveX controls
- This policy setting manages whether users will be automatically prompted for ActiveX control installations.
-
-If you enable this policy setting, users will receive a prompt when a site instantiates an ActiveX control they do not have installed.
-
-If you disable this policy setting, ActiveX control installations will be blocked using the Notification bar. Users can click on the Notification bar to allow the ActiveX control prompt.
-
-If you do not configure this policy setting, ActiveX control installations will be blocked using the Notification bar. Users can click on the Notification bar to allow the ActiveX control prompt.
- This policy setting manages whether users will be automatically prompted for ActiveX control installations.
-
-If you enable this policy setting, users will receive a prompt when a site instantiates an ActiveX control they do not have installed.
-
-If you disable this policy setting, ActiveX control installations will be blocked using the Notification bar. Users can click on the Notification bar to allow the ActiveX control prompt.
-
-If you do not configure this policy setting, users will receive a prompt when a site instantiates an ActiveX control they do not have installed.
- Automatic prompting for file downloads
- This policy setting determines whether users will be prompted for non user-initiated file downloads. Regardless of this setting, users will receive file download dialogs for user-initiated downloads.
-
-If you enable this setting, users will receive a file download dialog for automatic download attempts.
-
-If you disable or do not configure this setting, file downloads that are not user-initiated will be blocked, and users will see the Notification bar instead of the file download dialog. Users can then click the Notification bar to allow the file download prompt.
- This policy setting determines whether users will be prompted for non user-initiated file downloads. Regardless of this setting, users will receive file download dialogs for user-initiated downloads.
-
-If you enable this setting, users will receive a file download dialog for automatic download attempts.
-
-If you disable or do not configure this setting, users will receive a file download dialog for automatic download attempts.
- Locked-Down Restricted Sites Zone Template
- Restricted Sites Zone Template
- Run ActiveX controls and plugins
- This policy setting allows you to manage whether ActiveX controls and plug-ins can be run on pages from the specified zone.
-
-If you enable this policy setting, controls and plug-ins can run without user intervention.
-
-If you selected Prompt in the drop-down box, users are asked to choose whether to allow the controls or plug-in to run.
-
-If you disable this policy setting, controls and plug-ins are prevented from running.
-
-If you do not configure this policy setting, controls and plug-ins are prevented from running.
- This policy setting allows you to manage whether ActiveX controls and plug-ins can be run on pages from the specified zone.
-
-If you enable this policy setting, controls and plug-ins can run without user intervention.
-
-If you selected Prompt in the drop-down box, users are asked to choose whether to allow the controls or plug-in to run.
-
-If you disable this policy setting, controls and plug-ins are prevented from running.
-
-If you do not configure this policy setting, controls and plug-ins can run without user intervention.
- Script ActiveX controls marked safe for scripting
- This policy setting allows you to manage whether an ActiveX control marked safe for scripting can interact with a script.
-
-If you enable this policy setting, script interaction can occur automatically without user intervention.
-
-If you select Prompt in the drop-down box, users are queried to choose whether to allow script interaction.
-
-If you disable this policy setting, script interaction is prevented from occurring.
-
-If you do not configure this policy setting, script interaction is prevented from occurring.
- This policy setting allows you to manage whether an ActiveX control marked safe for scripting can interact with a script.
-
-If you enable this policy setting, script interaction can occur automatically without user intervention.
-
-If you select Prompt in the drop-down box, users are queried to choose whether to allow script interaction.
-
-If you disable this policy setting, script interaction is prevented from occurring.
-
-If you do not configure this policy setting, script interaction can occur automatically without user intervention.
- Don't run antimalware programs against ActiveX controls
- This policy setting determines whether Internet Explorer runs antimalware programs against ActiveX controls, to check if they're safe to load on pages.
-
-If you enable this policy setting, Internet Explorer won't check with your antimalware program to see if it's safe to create an instance of the ActiveX control.
-
-If you disable this policy setting, Internet Explorer always checks with your antimalware program to see if it's safe to create an instance of the ActiveX control.
-
-If you don't configure this policy setting, Internet Explorer always checks with your antimalware program to see if it's safe to create an instance of the ActiveX control. Users can turn this behavior on or off, using Internet Explorer Security settings.
- This policy setting determines whether Internet Explorer runs antimalware programs against ActiveX controls, to check if they're safe to load on pages.
-
-If you enable this policy setting, Internet Explorer won't check with your antimalware program to see if it's safe to create an instance of the ActiveX control.
-
-If you disable this policy setting, Internet Explorer always checks with your antimalware program to see if it's safe to create an instance of the ActiveX control.
-
-If you don't configure this policy setting, Internet Explorer won't check with your antimalware program to see if it's safe to create an instance of the ActiveX control. Users can turn this behavior on or off, using Internet Explorer Security settings.
- Initialize and script ActiveX controls not marked as safe
- This policy setting allows you to manage ActiveX controls not marked as safe.
-
-If you enable this policy setting, ActiveX controls are run, loaded with parameters, and scripted without setting object safety for untrusted data or scripts. This setting is not recommended, except for secure and administered zones. This setting causes both unsafe and safe controls to be initialized and scripted, ignoring the Script ActiveX controls marked safe for scripting option.
-
-If you enable this policy setting and select Prompt in the drop-down box, users are queried whether to allow the control to be loaded with parameters or scripted.
-
-If you disable this policy setting, ActiveX controls that cannot be made safe are not loaded with parameters or scripted.
-
-If you do not configure this policy setting, ActiveX controls that cannot be made safe are not loaded with parameters or scripted.
- This policy setting allows you to manage ActiveX controls not marked as safe.
-
-If you enable this policy setting, ActiveX controls are run, loaded with parameters, and scripted without setting object safety for untrusted data or scripts. This setting is not recommended, except for secure and administered zones. This setting causes both unsafe and safe controls to be initialized and scripted, ignoring the Script ActiveX controls marked safe for scripting option.
-
-If you enable this policy setting and select Prompt in the drop-down box, users are queried whether to allow the control to be loaded with parameters or scripted.
-
-If you disable this policy setting, ActiveX controls that cannot be made safe are not loaded with parameters or scripted.
-
-If you do not configure this policy setting, users are queried whether to allow the control to be loaded with parameters or scripted.
- Scripting of Java applets
- This policy setting allows you to manage whether applets are exposed to scripts within the zone.
-
-If you enable this policy setting, scripts can access applets automatically without user intervention.
-
-If you select Prompt in the drop-down box, users are queried to choose whether to allow scripts to access applets.
-
-If you disable this policy setting, scripts are prevented from accessing applets.
-
-If you do not configure this policy setting, scripts are prevented from accessing applets.
- This policy setting allows you to manage whether applets are exposed to scripts within the zone.
-
-If you enable this policy setting, scripts can access applets automatically without user intervention.
-
-If you select Prompt in the drop-down box, users are queried to choose whether to allow scripts to access applets.
-
-If you disable this policy setting, scripts are prevented from accessing applets.
-
-If you do not configure this policy setting, scripts can access applets automatically without user intervention.
- Run .NET Framework-reliant components signed with Authenticode
- This policy setting allows you to manage whether .NET Framework components that are signed with Authenticode can be executed from Internet Explorer. These components include managed controls referenced from an object tag and managed executables referenced from a link.
-
-If you enable this policy setting, Internet Explorer will execute signed managed components. If you select Prompt in the drop-down box, Internet Explorer will prompt the user to determine whether to execute signed managed components.
-
-If you disable this policy setting, Internet Explorer will not execute signed managed components.
-
-If you do not configure this policy setting, Internet Explorer will not execute signed managed components.
- This policy setting allows you to manage whether .NET Framework components that are signed with Authenticode can be executed from Internet Explorer. These components include managed controls referenced from an object tag and managed executables referenced from a link.
-
-If you enable this policy setting, Internet Explorer will execute signed managed components. If you select Prompt in the drop-down box, Internet Explorer will prompt the user to determine whether to execute signed managed components.
-
-If you disable this policy setting, Internet Explorer will not execute signed managed components.
-
-If you do not configure this policy setting, Internet Explorer will execute signed managed components.
- Software channel permissions
- This policy setting allows you to manage software channel permissions.
-
-If you enable this policy setting, you can choose the following options from the drop-down box.
-
-Low safety to allow users to be notified of software updates by e-mail, software packages to be automatically downloaded to users' computers, and software packages to be automatically installed on users' computers.
-
-Medium safety to allow users to be notified of software updates by e-mail and software packages to be automatically downloaded to (but not installed on) users' computers.
-
-High safety to prevent users from being notified of software updates by e-mail, software packages from being automatically downloaded to users' computers, and software packages from being automatically installed on users' computers.
-
-If you disable this policy setting, permissions are set to high safety.
-
-If you do not configure this policy setting, permissions are set to High safety.
- This policy setting allows you to manage software channel permissions.
-
-If you enable this policy setting, you can choose the following options from the drop-down box.
-
-Low safety to allow users to be notified of software updates by e-mail, software packages to be automatically downloaded to users' computers, and software packages to be automatically installed on users' computers.
-
-Medium safety to allow users to be notified of software updates by e-mail and software packages to be automatically downloaded to (but not installed on) users' computers.
-
-High safety to prevent users from being notified of software updates by e-mail, software packages from being automatically downloaded to users' computers, and software packages from being automatically installed on users' computers.
-
-If you disable this policy setting, permissions are set to high safety.
-
-If you do not configure this policy setting, permissions are set to Low safety.
- This policy setting allows you to manage software channel permissions.
-
-If you enable this policy setting, you can choose the following options from the drop-down box.
-
-Low safety to allow users to be notified of software updates by e-mail, software packages to be automatically downloaded to users' computers, and software packages to be automatically installed on users' computers.
-
-Medium safety to allow users to be notified of software updates by e-mail and software packages to be automatically downloaded to (but not installed on) users' computers.
-
-High safety to prevent users from being notified of software updates by e-mail, software packages from being automatically downloaded to users' computers, and software packages from being automatically installed on users' computers.
-
-If you disable this policy setting, permissions are set to high safety.
-
-If you do not configure this policy setting, permissions are set to Medium safety.
- Submit non-encrypted form data
- This policy setting allows you to manage whether data on HTML forms on pages in the zone may be submitted. Forms sent with SSL (Secure Sockets Layer) encryption are always allowed; this setting only affects non-SSL form data submission.
-
-If you enable this policy setting, information using HTML forms on pages in this zone can be submitted automatically. If you select Prompt in the drop-down box, users are queried to choose whether to allow information using HTML forms on pages in this zone to be submitted.
-
-If you disable this policy setting, information using HTML forms on pages in this zone is prevented from being submitted.
-
-If you do not configure this policy setting, information using HTML forms on pages in this zone can be submitted automatically.
- This policy setting allows you to manage whether data on HTML forms on pages in the zone may be submitted. Forms sent with SSL (Secure Sockets Layer) encryption are always allowed; this setting only affects non-SSL form data submission.
-
-If you enable this policy setting, information using HTML forms on pages in this zone can be submitted automatically. If you select Prompt in the drop-down box, users are queried to choose whether to allow information using HTML forms on pages in this zone to be submitted.
-
-If you disable this policy setting, information using HTML forms on pages in this zone is prevented from being submitted.
-
-If you do not configure this policy setting, users are queried to choose whether to allow information using HTML forms on pages in this zone to be submitted.
- Locked-Down Trusted Sites Zone Template
- Trusted Sites Zone Template
- Run .NET Framework-reliant components not signed with Authenticode
- This policy setting allows you to manage whether .NET Framework components that are not signed with Authenticode can be executed from Internet Explorer. These components include managed controls referenced from an object tag and managed executables referenced from a link.
-
-If you enable this policy setting, Internet Explorer will execute unsigned managed components. If you select Prompt in the drop-down box, Internet Explorer will prompt the user to determine whether to execute unsigned managed components.
-
-If you disable this policy setting, Internet Explorer will not execute unsigned managed components.
-
-If you do not configure this policy setting, Internet Explorer will not execute unsigned managed components.
- This policy setting allows you to manage whether .NET Framework components that are not signed with Authenticode can be executed from Internet Explorer. These components include managed controls referenced from an object tag and managed executables referenced from a link.
-
-If you enable this policy setting, Internet Explorer will execute unsigned managed components. If you select Prompt in the drop-down box, Internet Explorer will prompt the user to determine whether to execute unsigned managed components.
-
-If you disable this policy setting, Internet Explorer will not execute unsigned managed components.
-
-If you do not configure this policy setting, Internet Explorer will execute unsigned managed components.
- Userdata persistence
- This policy setting allows you to manage the preservation of information in the browser's history, in favorites, in an XML store, or directly within a Web page saved to disk. When a user returns to a persisted page, the state of the page can be restored if this policy setting is appropriately configured.
-
-If you enable this policy setting, users can preserve information in the browser's history, in favorites, in an XML store, or directly within a Web page saved to disk.
-
-If you disable this policy setting, users cannot preserve information in the browser's history, in favorites, in an XML store, or directly within a Web page saved to disk.
-
-If you do not configure this policy setting, users cannot preserve information in the browser's history, in favorites, in an XML store, or directly within a Web page saved to disk.
- This policy setting allows you to manage the preservation of information in the browser's history, in favorites, in an XML store, or directly within a Web page saved to disk. When a user returns to a persisted page, the state of the page can be restored if this policy setting is appropriately configured.
-
-If you enable this policy setting, users can preserve information in the browser's history, in favorites, in an XML store, or directly within a Web page saved to disk.
-
-If you disable this policy setting, users cannot preserve information in the browser's history, in favorites, in an XML store, or directly within a Web page saved to disk.
-
-If you do not configure this policy setting, users can preserve information in the browser's history, in favorites, in an XML store, or directly within a Web page saved to disk.
- Allow script-initiated windows without size or position constraints
- This policy setting allows you to manage restrictions on script-initiated pop-up windows and windows that include the title and status bars.
-
-If you enable this policy setting, Windows Restrictions security will not apply in this zone. The security zone runs without the added layer of security provided by this feature.
-
-If you disable this policy setting, the possible harmful actions contained in script-initiated pop-up windows and windows that include the title and status bars cannot be run. This Internet Explorer security feature will be on in this zone as dictated by the Scripted Windows Security Restrictions feature control setting for the process.
-
-If you do not configure this policy setting, the possible harmful actions contained in script-initiated pop-up windows and windows that include the title and status bars cannot be run. This Internet Explorer security feature will be on in this zone as dictated by the Scripted Windows Security Restrictions feature control setting for the process.
- This policy setting allows you to manage restrictions on script-initiated pop-up windows and windows that include the title and status bars.
-
-If you enable this policy setting, Windows Restrictions security will not apply in this zone. The security zone runs without the added layer of security provided by this feature.
-
-If you disable this policy setting, the possible harmful actions contained in script-initiated pop-up windows and windows that include the title and status bars cannot be run. This Internet Explorer security feature will be on in this zone as dictated by the Scripted Windows Security Restrictions feature control setting for the process.
-
-If you do not configure this policy setting, Windows Restrictions security will not apply in this zone. The security zone runs without the added layer of security provided by this feature.
- Web sites in less privileged Web content zones can navigate into this zone
- This policy setting allows you to manage whether Web sites from less privileged zones, such as Internet sites, can navigate into this zone.
-
-If you enable this policy setting, Web sites from less privileged zones can open new windows in, or navigate into, this zone. The security zone will run without the added layer of security that is provided by the Protection from Zone Elevation security feature. If you select Prompt in the drop-down box, a warning is issued to the user that potentially risky navigation is about to occur.
-
-If you disable this policy setting, the possibly harmful navigations are prevented. The Internet Explorer security feature will be on in this zone as set by Protection from Zone Elevation feature control.
-
-If you do not configure this policy setting, the possibly harmful navigations are prevented. The Internet Explorer security feature will be on in this zone as set by Protection from Zone Elevation feature control.
- This policy setting allows you to manage whether Web sites from less privileged zones, such as Restricted Sites, can navigate into this zone.
-
-If you enable this policy setting, Web sites from less privileged zones can open new windows in, or navigate into, this zone. The security zone will run without the added layer of security that is provided by the Protection from Zone Elevation security feature. If you select Prompt in the drop-down box, a warning is issued to the user that potentially risky navigation is about to occur.
-
-If you disable this policy setting, the possibly harmful navigations are prevented. The Internet Explorer security feature will be on in this zone as set by Protection from Zone Elevation feature control.
-
-If you do not configure this policy setting, Web sites from less privileged zones can open new windows in, or navigate into, this zone.
- This policy setting allows you to manage whether Web sites from less privileged zones, such as Restricted Sites, can navigate into this zone.
-
-If you enable this policy setting, Web sites from less privileged zones can open new windows in, or navigate into, this zone. The security zone will run without the added layer of security that is provided by the Protection from Zone Elevation security feature. If you select Prompt in the drop-down box, a warning is issued to the user that potentially risky navigation is about to occur.
-
-If you disable this policy setting, the possibly harmful navigations are prevented. The Internet Explorer security feature will be on in this zone as set by Protection from Zone Elevation feature control.
-
-If you do not configure this policy setting, a warning is issued to the user that potentially risky navigation is about to occur.
- Allow VBScript to run in Internet Explorer
- This policy setting allows you to manage whether VBScript can be run on pages from the specified zone in Internet Explorer.
-
-If you selected Enable in the drop-down box, VBScript can run without user intervention.
-
-If you selected Prompt in the drop-down box, users are asked to choose whether to allow VBScript to run.
-
-If you selected Disable in the drop-down box, VBScript is prevented from running.
-
-If you do not configure or disable this policy setting, VBScript is prevented from running.
- This policy setting allows you to manage whether VBScript can be run on pages from the specified zone in Internet Explorer.
-
-If you selected Enable in the drop-down box, VBScript can run without user intervention.
-
-If you selected Prompt in the drop-down box, users are asked to choose whether to allow VBScript to run.
-
-If you selected Disable in the drop-down box, VBScript is prevented from running.
-
-If you do not configure or disable this policy setting, VBScript will run without user intervention.
- This policy setting allows you to manage whether VBScript can be run on pages from the specified zone in Internet Explorer.
-
-If you selected Enable in the drop-down box, VBScript can run without user intervention.
-
-If you selected Prompt in the drop-down box, users are asked to choose whether to allow VBScript to run.
-
-If you selected Disable in the drop-down box, VBScript is prevented from running.
-
-If you do not configure or disable this policy setting, users are asked to choose whether to allow VBScript to run.
- Intranet Sites: Include all sites that bypass the proxy server
- Restricted Sites Zone
- Locked-Down Restricted Sites Zone
- The settings in this zone apply only if the Restricted Zone is in 'lockdown' mode, such as when the Network Protocol Lockdown security feature is in effect. If the zone is locked down, these URL action settings do not override the standard Restricted Zone settings, but are compared against them. If the settings for that URL action in the two zones are the same, then that setting is used. Otherwise, the relevant behavior is strictly blocked, preventing the zone from operating with the standard (non-lockdown) zone's setting.
- Security Page
- If you enable any policies for the security page, it is strongly recommended that you also configure policy to disable the security page from being presented in the UI to prevent users from believing that they can change their security settings.
-
-You can disable the security page using the policy located at Administrative Templates\Windows Components\Internet Explorer\Internet Control Panel\.
- Trusted Sites Zone
- Locked-Down Trusted Sites Zone
- The settings in this zone apply only if the Trusted Zone is in 'lockdown' mode, such as when the Network Protocol Lockdown security feature is in effect. If the zone is locked down, these URL action settings do not override the standard Trusted Zone settings, but are compared against them. If the settings for that URL action in the two zones are the same, then that setting is used. Otherwise, the user is presented with a Notification bar, and may allow the zone to operate with the standard (non-lockdown) zone's setting.
- Intranet Sites: Include all network paths (UNCs)
- Site to Zone Assignment List
- This policy setting prevents the user from specifying the color of webpage links that he or she has not yet clicked. Appropriate color choices can make links easier to see for some users, especially those who use high-contrast color schemes.
-
-If you enable this policy setting, the user cannot specify the color of links not yet clicked in Internet Explorer. You must specify the link color (for example: 192,192,192).
-
-If you disable or do not configure this policy setting, the user can specify the color of links not yet clicked.
- Prevent specifying the color of links that have not yet been clicked
- Link Colors
- This policy setting prevents the user from specifying the color of webpage links that he or she has already clicked. Appropriate color choices can make links easier to see for some users, especially those who use high-contrast color schemes.
-
-If you enable this policy setting, the user cannot specify the color of links already clicked in Internet Explorer. You must specify the link color (for example: 192,192,192).
-
-If you disable or do not configure this policy setting, the user can specify the color of links already clicked.
- Prevent specifying the color of links that have already been clicked
- Manual
- Subscription Limits
- 0
- 1
- 2
- 3
- Configure Media Explorer Bar
- Menu Controls
- Browser menus
- Microsoft Agent
- Microsoft Chat
- MSNBC
- Multimedia
- NetShow File Transfer Control
- Never
- Open in a new Internet Explorer window
- Disable adding channels
- Disable adding schedules for offline pages
- Turn on automatic signup
- This policy setting allows Internet Explorer to be started automatically to complete the signup process after the branding is complete for Internet service providers (ISPs) through the Internet Explorer Administration Kit (IEAK).
-
-If you enable this policy setting, Internet Explorer is started automatically to complete the signup process after the branding is complete for ISPs (IEAK). The user cannot change this behavior.
-
-If you disable this policy setting, Internet Explorer is not started automatically to complete the signup process after the branding is complete for ISPs (IEAK). The user cannot change this behavior.
-
-If you do not configure this policy setting, the user can decide whether to start Internet Explorer automatically to complete the signup process after the branding is complete for ISPs (IEAK).
- Disable customizing browser toolbars
- Turn off Shortcut Menu
- Prevent ignoring certificate errors
- Disable offline page hit logging
- Disable channel user interface completely
- Prevent access to Delete Browsing History
- Prevent deleting form data
- Prevent deleting passwords
- Disable editing and creating of schedule groups
- Disable editing schedules for offline pages
- Hide Favorites menu
- Prevent running First Run wizard
- Prevent access to Internet Explorer Help
- Prevent Internet Explorer Search box from appearing
- Disable Automatic Install of Internet Explorer components
- Disable Open in New Window menu option
- Turn off Quick Tabs functionality
- Disable removing channels
- Disable removing schedules for offline pages
- Disable all scheduled offline pages
- Prevent changing the default search provider
- Disable Save this program to disk option
- Disable showing the splash screen
- Disable downloading of site subscription content
- Turn off tabbed browsing
- Turn off configuration of pop-up windows in tabbed browsing
- Disable customizing browser toolbar buttons
- Disable Periodic Check for Internet Explorer software updates
- Prevent configuration of how windows open
- Configure Outlook Express
- Turn off page transitions
- This policy setting specifies if, as you move from one Web page to another, Internet Explorer fades out of the page you are leaving and fades into the page to which you are going.
-
-If you enable this policy setting, page transitions will be turned off. The user cannot change this behavior.
-
-If you disable this policy setting, page transitions will be turned on. The user cannot change this behavior.
-
-If you do not configure this policy setting, the user can turn on or off page transitions.
-
-This feature only applies to versions of Internet Explorer up to and including Internet Explorer 8.
- Persistence Behavior
- File size limits for Local Machine zone
- File size limits for Intranet zone
- File size limits for Trusted Sites zone
- File size limits for Internet zone
- File size limits for Restricted Sites zone
- Off
- On
- Pop-up allow list
- Printing
- This policy setting specifies whether Internet Explorer prints background colors and images when the user prints a webpage. Including background colors and images might reduce the speed at which a page is printed and the quality of the printing, depending on the capabilities of the printer.
-
-If you enable this policy setting, the printing of background colors and images is turned on. The user cannot turn it off.
-
-If you disable this policy setting, the printing of background colors and images is turned off. The user cannot turn it on.
-
-If you do not configure this policy setting, the user can turn on or turn off the printing of background colors and images.
- Disable changing accessibility settings
- Disable changing Automatic Configuration settings
- Turn off automatic image resizing
- This policy setting specifies that you want Internet Explorer to automatically resize large images so that they fit in the browser window.
-
-If you enable this policy setting, automatic image resizing is turned off. The user cannot change this setting.
-
-If you disable this policy setting, automatic image resizing is turned on. The user cannot change this setting.
-
-If you do not configure this policy setting, the user can turn on or off automatic image resizing.
- Disable changing Temporary Internet files settings
- Disable changing Calendar and Contact settings
- Disable changing certificate settings
- Disable changing default browser check
- Notify users if Internet Explorer is not the default web browser
- Disable changing color settings
- Disable changing connection settings
- Disable Internet Connection wizard
- Disable changing font settings
- Disable AutoComplete for forms
- Turn on the auto-complete feature for user names and passwords on forms
- Disable "Configuring History"
- Disable changing home page settings
- Disable changing language settings
- Disable changing link color settings
- Disable changing Messaging settings
- Prevent managing pop-up exception list
- Turn off pop-up management
- Disable changing Profile Assistant settings
- Prevent changing proxy settings
- Disable changing ratings settings
- Disable the Reset Web Settings feature
- Prevent the deletion of temporary Internet files and cookies
- Turn off the auto-complete feature for web addresses
- Turn off Windows Search AutoComplete
- Turn off URL Suggestions
- RSS Feeds
- Turn on the display of script errors
- This policy setting specifies whether to display script errors when a page does not appear properly because of problems with its scripting. This feature is off by default, but it is useful to developers when they are testing webpages.
-
-If you enable this policy setting, the user is shown script errors when a page does not appear properly because of problems with its scripting. The user cannot change this policy setting.
-
-If you disable this policy setting, the user is not shown script errors when a page does not appear properly because of problems with its scripting. The user cannot change this policy setting.
-
-If you do not configure this policy setting, the user can turn on or turn off the display of script errors.
- Microsoft Scriptlet Component
- Clipboard access
- Search: Disable Find Files via F3 within the browser
- Search: Disable Search Customization
- Searching
- Security Zones: Use only machine settings
- Security Zones: Do not allow users to change policies
- Security Zones: Do not allow users to add/delete sites
- Security Features
- Turn on automatic detection of intranet
- Turn on Notification bar notification for intranet content
- Disable software update shell notifications on program launch
- Turn off image display
- This policy setting specifies whether graphical images are included when pages are displayed.
-
-Sometimes, pages that contain several graphical images are displayed very slowly. If you want to display pages more quickly, you can turn off image display.
-
-If you enable this policy setting, images do not appear. The user cannot turn on image display. However, the user can still display an individual image by right-clicking the icon that represents the image and then clicking Show Picture. The "Allow the display of image download placeholders" policy setting must be disabled if this policy setting is enabled.
-
-If you disable this policy setting, images appear. The user cannot turn off image display.
-
-If you do not configure this policy setting, the user can turn on or turn off image display.
- Allow the display of image download placeholders
- This policy setting specifies whether placeholders appear for graphical images while the images are downloading. This allows items on the page to be positioned where they will appear when the images are completely downloaded. This option is ignored if the Show Pictures check box is cleared.
-
-If you enable this policy setting, placeholders appear for graphical images while the images are downloading. The user cannot change this policy setting. The "Turn off image display" policy setting must be disabled if this policy setting is enabled.
-
-If you disable this policy setting, placeholders will not appear for graphical images while the images are downloading. The user cannot change this policy setting.
-
-If you do not configure this policy setting, the user can allow or prevent the display of placeholders for graphical images while the images are downloading.
- Allow Internet Explorer to play media files that use alternative codecs
- This policy setting specifies whether Internet Explorer plays media files that use alternative codecs and that require additional software.
-
-If you enable this policy setting, Internet Explorer plays these files, if the appropriate software is installed.
-
-If you disable this policy setting, Internet Explorer does not play these files.
-
-If you do not configure this policy setting, the user can change the "Enable alternative codecs in HTML5 media elements" setting on the Advanced tab in the Internet Options dialog box.
- Signup Settings
- Turn off smart image dithering
- This policy setting specifies whether you want Internet Explorer to smooth images so that they appear less jagged when displayed.
-
-If you enable this policy setting, smart image dithering is turned off. The user cannot turn it on.
-
-If you disable this policy setting, smart image dithering is turned on. The user cannot turn it off.
-
-If you do not configure this policy setting, the user can turn on or turn off smart image dithering.
- Turn off smooth scrolling
- This policy setting specifies whether smooth scrolling is used to display content at a predefined speed.
-
-If you enable this policy setting, smooth scrolling is turned off. The user cannot turn on smooth scrolling.
-
-If you disable this policy setting, smooth scrolling is turned on. The user cannot turn off smooth scrolling.
-
-If you do not configure this policy setting, the user can hide or show the button to open Microsoft Edge from Internet Explorer.
- Hide the button (next to the New Tab button) that opens Microsoft Edge
- This policy setting allows you to manage if users can see the button (next to the New Tab button) that opens Microsoft Edge.
-
-If you enable this policy setting, the button to open Microsoft Edge from Internet Explorer will be hidden.
-
-If you disable this policy setting, the button to open Microsoft Edge from Internet Explorer will be shown.
-
-If you do not configure this policy setting, the button to open Microsoft Edge from Internet Explorer can be configured by the user.
- Restrict search providers to a specific list
- Prevent participation in the Customer Experience Improvement Program
- Only Internet Explorer 4.0
- At least Internet Explorer 5.0
- Only Internet Explorer 5.0 and Internet Explorer 6.0
- Only Internet Explorer 5.0 through Internet Explorer 7.0
- Only Internet Explorer 5.0 through Internet Explorer 8.0
- Only Internet Explorer 5.0 through Internet Explorer 9.0
- At least Internet Explorer 5.0. Not supported on Windows 8
- At least Internet Explorer 5.0. Not supported on Windows Vista
- Only Internet Explorer 5.0
- Only Internet Explorer 6.0
- At least Internet Explorer 6.0 in Windows XP with Service Pack 2 or Windows Server 2003 with Service Pack 1
- Only Internet Explorer 6.0 in Windows XP Service Pack 2 or Windows Server 2003 Service Pack 1 through IE7 inclusive
- Only Internet Explorer 6.0 in Windows XP Service Pack 2 or Windows Server 2003 Service Pack 1 through IE8 inclusive
- At least Internet Explorer 6.0 in Windows 2003 Service Pack 1
- At least Internet Explorer 6.0 in Windows 2003 Service Pack 1. Not supported on Windows Vista
- Only Internet Explorer 6.0 in Windows 2003 Service Pack 1
- At least Internet Explorer 7.0
- Only Internet Explorer 7.0
- Only Internet Explorer 7.0 and Internet Explorer 8.0
- Internet Explorer 7.0 to Internet Explorer 9.0
- Internet Explorer 7.0 to Internet Explorer 10.0
- Internet Explorer 8.0 to Internet Explorer 10.0
- At least Internet Explorer 8.0
- Only Internet Explorer 8.0
- At least Internet Explorer 9.0
- Only Internet Explorer 9.0 through 11.0. Not supported on Windows 10
- At least Internet Explorer 10.0
- At least Internet Explorer 10.0 on Windows 8
- At least Internet Explorer 11.0 on Windows 8.1
- Only Internet Explorer 11.0 on Windows 8.1
- At least Internet Explorer 11.0 on Windows 10
- At least Internet Explorer 11.0 on Windows 10, vertion 1607 or later
- At least Internet Explorer 11.0 on Windows 10, version 1703 or later
- At least Internet Explorer 11.0
- At least Internet Explorer 7.0. Not supported on Windows Vista
- At least Internet Explorer 7.0 in Windows Vista
- Microsoft Survey Control
- Prevent configuration of new tab creation
- This policy setting prevents the user from specifying the text color in Internet Explorer.
-
-If you enable this policy setting, the user cannot specify the text color in Internet Explorer. You must specify the text color (for example: 192,192,192).
-
-If you disable or do not configure this policy setting, the user can specify the text color in Internet Explorer.
- Prevent specifying text color
- Configure Toolbar Buttons
- Toolbars
- Tools menu: Disable Internet Options... menu option
- Turn off the ability to launch report site problems using a menu option
- Turn on ActiveX Filtering
- Turn off configuring underline links
- This policy setting specifies how you want links on webpages to be underlined.
-
-If you enable this policy setting, a user cannot choose when to underline links. You must specify when to underline links:
- • Always
- • Never
- • Hover (when the mouse pointer pauses on a link)
-
-If you disable or do not configure this policy setting, the user can choose when to underline links.
- Periodic check for updates to Internet Explorer and Internet Tools
- Prevent specifying the update check interval (in days)
- This policy setting prevents the user from specifying the update check interval. The default value is 30 days.
-
-If you enable this policy setting, the user cannot specify the update check interval. You must specify the update check interval.
-
-If you disable or do not configure this policy setting, the user can specify the update check interval.
- Prevent changing the URL for checking updates to Internet Explorer and Internet Tools
- This policy setting prevents the user from changing the default URL for checking updates to Internet Explorer and Internet Tools.
-
-If you enable this policy setting, the user cannot change the URL that is displayed for checking updates to Internet Explorer and Internet Tools. You must specify this URL.
-
-If you disable or do not configure this policy setting, the user can change the URL that is displayed for checking updates to Internet Explorer and Internet Tools.
- Prevent configuration of search on Address bar
- This policy setting specifies whether the user can conduct a search on the Address bar.
-
-If you enable this policy setting, you must specify which of the following actions applies to searches on the Address bar. The user cannot change the specified action.
-
- • Do not search from the Address bar: The user cannot use the Address bar for searches. The user can still perform searches on the Search bar by clicking the Search button.
- • Display the results in the main window: When the user searches on the Address bar, the list of search results is displayed in the main window.
-
-If you disable or do not configure this policy setting, the user can specify what action applies to searches on the Address bar.
- Always encode query strings in UTF-8
- Encode query strings in UTF-8 only in Intranet URLs
- Never encode query strings in UTF-8
- Encode query strings in UTF-8 only in non-Intranet URLs
- Disable top result search
- Enable top result search
- Prevent configuration of top-result search on Address bar
- This policy setting allows you to specify whether a user can browse to the website of a top result when search is enabled on the Address bar. The possible options are:
- • Disable top result search: When a user performs a search in the Address bar, a list of search results from the selected search provider is displayed in the main window.
- • Enable top result search: When a user performs a search in the Address bar, the user is directed to an external top result website determined by the search provider, if available.
-
-If you enable this policy setting, you can choose where to direct the user after a search on the Address bar: a top-result website or a search-results webpage in the main window.
-
-If you disable or do not configure this policy setting, the user can select their preference for this behavior. Browsing to the top-result website is the default.
- Go directly to home page
- Turn on the hover color option
- This policy setting makes hyperlinks change color when the mouse pointer pauses on them.
-
-If you enable this policy setting, the hover color option is turned on. The user cannot turn it off.
-
-If you disable this policy setting, the hover color option is turned off. The user cannot turn it on.
-
-If you do not configure this policy setting, the user can turn on or turn off the hover color option.
- Make proxy settings per-machine (rather than per-user)
- Go directly to "Welcome To IE" page
- Prevent the use of Windows colors
- This policy setting prevents the user from using Windows colors as a part of the display settings.
-
-If you enable this policy setting, Windows colors are turned off. The user cannot turn them on.
-
-If you disable this policy setting, Windows colors are turned on. The user cannot turn them off.
-
-If you do not configure this policy setting, the user can turn on or turn off Windows colors for display.
- Turn off sending URL path as UTF-8
- This policy setting specifies whether to use 8-bit Unicode Transformation Format (UTF-8), a standard that defines characters so they are readable in any language. By using UTF-8, you can exchange Internet addresses (URLs) that contain characters from any language.
-
-If you enable this policy setting, Internet Explorer does not allow sending the path portion of URLs as UTF-8. The user cannot change this policy setting.
-
-If you disable this policy setting, Internet Explorer allows sending the path portion of URLs as UTF-8. The user cannot change this policy setting.
-
-If you do not configure this policy setting, the user can allow or prevent the sending of the path portion of URLs as UTF-8.
- View menu: Disable Full Screen menu option
- View menu: Disable Source menu option
- Turn off Developer Tools
- Turn off Favorites bar
- Turn off Tab Grouping
- Turn off Data URI support
- Turn off Data Execution Prevention
- This policy setting allows you to manage whether the user can access Developer Tools in Internet Explorer.
-
-If you enable this policy setting, the user cannot access Developer Tools.
-
-If you disable or do not configure this policy setting, the user can access Developer Tools.
- Do not display the reveal password button
- This policy setting allows you to hide the reveal password button when Internet Explorer prompts users for a password. The reveal password button is displayed during password entry. When the user clicks the button, the current password value is visible until the mouse button is released (or until the tap ends).
-
-If you enable this policy setting, the reveal password button will be hidden for all password fields. Users and developers will not be able to depend on the reveal password button being displayed in any web form or web application.
-
-If you disable or do not configure this policy setting, the reveal password button can be shown by the application as a user types in a password. The reveal password button is visible by default.
-
-On at least Windows 8, if the "Do not display the reveal password button" policy setting located in Computer Configuration\Administrative Templates\Windows Components\Credential User Interface is enabled for the system, it will override this policy setting.
- This policy setting allows you to manage whether a user has access to the Favorites bar in Internet Explorer.
-
-If you enable this policy setting, the Favorites bar is turned off.
-
-If you disable this policy setting, the Favorites bar is turned on.
-
-If you do not configure this policy setting, the user can turn on or turn off the Favorites bar.
- This policy setting allows you to manage whether the user has access to Tab Grouping in Internet Explorer.
-
-If you enable this policy setting, Tab Grouping is turned off.
-
-If you disable this policy setting, Tab Grouping is turned on.
-
-If you do not configure this policy setting, the user can turn on or turn off Tab Grouping.
- This policy setting allows you to turn off the Data Execution Prevention feature for Internet Explorer on Windows Server 2008, Windows Vista with SP1, and Windows XP with SP3.
-
-If you enable this policy setting, Internet Explorer does not turn on Data Execution Prevention on platforms that support the SetProcessDEPPolicy function.
-
-If you disable or do not configure this policy setting, Internet Explorer uses the SetProcessDEPPolicy function to turn on Data Execution Prevention on platforms that support the function.
-
-This policy setting has no effect if Windows has been configured to enable Data Execution Prevention.
- This policy setting allows you to turn on or turn off Data URI support. A Data URI allows web developers to encapsulate images and .css files within the body of the URL and optionally encode them by using base 64 encoding. Malware filters or other network-based filters may not properly filter encapsulated data.
-
-If you enable this policy setting, Data URI support is turned off. Without Data URI support, a Data URI will be interpreted as a failed URL.
-
-If you disable this policy setting, Data URI support is turned on.
-
-If you do not configure this policy setting, Data URI support can be turned on or off through the registry.
- Prevent deleting cookies
- Prevent deleting websites that the user has visited
- Prevent deleting download history
- Prevent deleting temporary Internet files
- Prevent deleting InPrivate Filtering data
- Prevent deleting ActiveX Filtering, Tracking Protection, and Do Not Track data
- Prevent deleting favorites site data
- Allow deleting browsing history on exit
- Delete Browsing History
- Turn off Automatic Crash Recovery
- Change the maximum number of connections per host (HTTP 1.1)
- Maximum number of connections per server (HTTP 1.0)
- Turn off cross-document messaging
- Turn off the XDomainRequest object
- Turn off the WebSocket Object
- Set the maximum number of WebSocket connections per server
- The WebSocket object allows websites to request data across domains from your browser by using the WebSocket protocol. This policy setting allows administrators to enable or disable the WebSocket object. This policy setting does not prevent client-side communication across domains via other features in Internet Explorer 10. Also, this policy setting does not prevent a site from requesting cross-domain data through a server.
-
-If you enable this policy setting, websites cannot request data across domains by using the WebSocket object.
-
-If you disable or do not configure this policy setting, websites can request data across domains by using the WebSocket object. By default, the WebSocket object is enabled.
- This policy setting allows you to change the default limit of WebSocket connections per server. The default limit is 6; you can select a value from 2 through 128.
-
-If you enable this policy setting, Internet Explorer uses the WebSocket connection limit that you set with this policy setting.
-
-If you disable or do not configure this policy setting, Internet Explorer uses the default limit of 6 WebSocket connections per server.
- Prevent bypassing SmartScreen Filter warnings
- Prevent bypassing SmartScreen Filter warnings about files that are not commonly downloaded from the Internet
- This policy setting prevents the user from deleting cookies. This feature is available in the Delete Browsing History dialog box.
-
-If you enable this policy setting, cookies are preserved when the user clicks Delete.
-
-If you disable this policy setting, cookies are deleted when the user clicks Delete.
-
-If you do not configure this policy setting, the user can choose whether to delete or preserve cookies when he or she clicks Delete.
-
-If the "Prevent access to Delete Browsing History" policy setting is enabled, this policy setting is enabled by default.
- This policy setting prevents the user from deleting the history of websites that he or she has visited. This feature is available in the Delete Browsing History dialog box.
-
-If you enable this policy setting, websites that the user has visited are preserved when he or she clicks Delete.
-
-If you disable this policy setting, websites that the user has visited are deleted when he or she clicks Delete.
-
-If you do not configure this policy setting, the user can choose whether to delete or preserve visited websites when he or she clicks Delete.
-
-If the "Prevent access to Delete Browsing History" policy setting is enabled, this policy setting is enabled by default.
- This policy setting prevents the user from deleting temporary Internet files. This feature is available in the Delete Browsing History dialog box.
-
-If you enable this policy setting, temporary Internet files are preserved when the user clicks Delete.
-
-If you disable this policy setting, temporary Internet files are deleted when the user clicks Delete.
-
-If you do not configure this policy setting, the user can choose whether to delete or preserve temporary Internet files when he or she clicks Delete.
-
-If the "Prevent access to Delete Browsing History" policy setting is enabled, this policy setting is enabled by default.
- This policy setting prevents the user from deleting InPrivate Filtering data. Internet Explorer collects InPrivate Filtering data during browser sessions other than InPrivate Browsing sessions to determine which third-party items should be blocked when InPrivate Filtering is enabled. This feature is available in the Delete Browsing History dialog box.
-
-If you enable this policy setting, InPrivate Filtering data is preserved when the user clicks Delete.
-
-If you disable this policy setting, InPrivate Filtering data is deleted when the user clicks Delete.
-
-If you do not configure this policy setting, the user can choose whether to delete or preserve InPrivate Filtering data when he or she clicks Delete.
- In Internet Explorer 9 and Internet Explorer 10:
-This policy setting prevents users from deleting ActiveX Filtering and Tracking Protection data, which includes the list of websites for which the user has chosen to disable ActiveX Filtering or Tracking Protection. In addition, Tracking Protection data is also collected if users turn on the Personalized Tracking Protection List, which blocks third-party items while the user is browsing.
-
-With at least Internet Explorer 11:
-This policy setting prevents users from deleting ActiveX Filtering data, Tracking Protection data, and Do Not Track exceptions stored for visited websites.
-
-This feature is available in the Delete Browsing History dialog box.
-
-If you enable this policy setting, ActiveX Filtering, Tracking Protection and Do Not Track data is preserved when the user clicks Delete.
-
-If you disable this policy setting, ActiveX Filtering, Tracking Protection and Do Not Track data is deleted when the user clicks Delete.
-
-If you don't configure this policy setting, users can turn this feature on and off, determining whether to delete ActiveX Filtering, Tracking Protection, and Do Not Track data when clicking Delete.
- This policy setting prevents the user from deleting favorites site data. This feature is available in the Delete Browsing History dialog box.
-
-If you enable this policy setting, favorites site data is preserved when the user clicks Delete.
-
-If you disable this policy setting, favorites site data is deleted when the user clicks Delete.
-
-If you do not configure this policy setting, the user can choose whether to delete or preserve favorites site data when he or she clicks Delete.
-
-If the "Prevent access to Delete Browsing History" policy setting is enabled, this policy setting has no effect.
- This policy setting prevents the user from deleting his or her download history. This feature is available in the Delete Browsing History dialog box.
-
-If you enable this policy setting, download history is preserved when the user clicks Delete.
-
-If you disable this policy setting, download history is deleted when the user clicks Delete.
-
-If you do not configure this policy setting, the user can choose whether to delete or preserve download history when he or she clicks Delete.
-
-If the "Prevent access to Delete Browsing History" policy setting is enabled, this policy setting is enabled by default.
- This policy setting allows the automatic deletion of specified items when the last browser window closes. The preferences selected in the Delete Browsing History dialog box (such as deleting temporary Internet files, cookies, history, form data, and passwords) are applied, and those items are deleted.
-
-If you enable this policy setting, deleting browsing history on exit is turned on.
-
-If you disable this policy setting, deleting browsing history on exit is turned off.
-
-If you do not configure this policy setting, it can be configured on the General tab in Internet Options.
-
-If the "Prevent access to Delete Browsing History" policy setting is enabled, this policy setting has no effect.
- This policy setting turns off Automatic Crash Recovery.
-
-If you enable this policy setting, Automatic Crash Recovery does not prompt the user to recover his or her data after a program stops responding.
-
-If you disable or do not configure this policy setting, Automatic Crash Recovery prompts the user to recover his or her data after a program stops responding.
- This policy setting allows you to change the default connection limit for HTTP 1.1 from 6 connections per host to a limit of your choice (from 2 through 128).
-
-If you enable this policy setting, Internet Explorer uses the connection limit of your choice for HTTP 1.1.
-
-If you disable or do not configure this policy setting, Internet Explorer uses the default connection limit for HTTP 1.1 (6 connections per host).
-
-In versions of Internet Explorer before Internet Explorer 8, the default connection limit for HTTP 1.1 was 2.
- This policy setting allows you to change the default connection limit for HTTP 1.0 from 6 connections per host to a limit of your choice (from 2 through 128).
-
-If you disable or do not configure this policy setting, Internet Explorer will use the default connection limit for HTTP 1.0 (6 connections per host).
-
-In versions of Internet Explorer prior to Internet Explorer 8, the default connection limit for HTTP 1.0 was 4.
- This policy setting allows you to manage whether documents can request data across third-party domains embedded in the page.
-
-If you enable this policy setting, documents cannot request data across third-party domains embedded in the page.
-
-If you disable or do not configure this policy setting, documents can request data across third-party domains embedded in the page.
- This policy setting allows you to choose whether websites can request data across domains by using the XDomainRequest object. Note that this policy setting does not block client-side communication across domains through other features in Internet Explorer 8, and it does not prevent a site from requesting cross-domain data through a server.
-
-If you enable this policy setting, websites cannot request data across domains by using the XDomainRequest object.
-
-If you disable or do not configure this policy setting, websites can request data across domains by using the XDomainRequest object.
- This policy setting determines whether the user can bypass warnings from SmartScreen Filter. SmartScreen Filter prevents the user from browsing to or downloading from sites that are known to host malicious content. SmartScreen Filter also prevents the execution of files that are known to be malicious.
-
-If you enable this policy setting, SmartScreen Filter warnings block the user.
-
-If you disable or do not configure this policy setting, the user can bypass SmartScreen Filter warnings.
- This policy setting determines whether the user can bypass warnings from SmartScreen Filter. SmartScreen Filter warns the user about executable files that Internet Explorer users do not commonly download from the Internet.
-
-If you enable this policy setting, SmartScreen Filter warnings block the user.
-
-If you disable or do not configure this policy setting, the user can bypass SmartScreen Filter warnings.
- Turn on Caret Browsing support
- Turn on Enhanced Protected Mode
- Turn on 64-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows
- Do not allow ActiveX controls to run in Protected Mode when Enhanced Protected Mode is enabled
- Use HTTP 1.1
- Use HTTP 1.1 through proxy connections
- Allow fallback to SSL 3.0 (Internet Explorer)
- Non-Protected Mode Sites
- All Sites
- No Sites
- Allow Internet Explorer to use the SPDY/3 network protocol
- Allow Internet Explorer to use the HTTP2 network protocol
- Turn off encryption support
- Turn off Print Menu
- Turn off the flip ahead with page prediction feature
- Turn off loading websites and content in the background to optimize performance
- Always send Do Not Track header
- Show Content Advisor on Internet Options
- This policy setting allows you to turn Caret Browsing on or off. Caret Browsing allows users to browse to a webpage by using the keyboard to move the cursor. Caret Browsing supports standard text-editor functionality, such as using the Shift key to select text and copying a selection to the clipboard. This policy setting is particularly useful to users who do not use a mouse.
-
-If you enable this policy setting, Caret Browsing is turned on.
-
-If you disable this policy setting, Caret Browsing is turned off.
-
-If you do not configure this policy setting, Caret Browsing support can be turned on or off through the registry.
- Enhanced Protected Mode provides additional protection against malicious websites by using 64-bit processes on 64-bit versions of Windows. For computers running at least Windows 8, Enhanced Protected Mode also limits the locations Internet Explorer can read from in the registry and the file system.
-
-If you enable this policy setting, Enhanced Protected Mode will be turned on. Any zone that has Protected Mode enabled will use Enhanced Protected Mode. Users will not be able to disable Enhanced Protected Mode.
-
-If you disable this policy setting, Enhanced Protected Mode will be turned off. Any zone that has Protected Mode enabled will use the version of Protected Mode introduced in Internet Explorer 7 for Windows Vista.
-
-If you do not configure this policy, users will be able to turn on or turn off Enhanced Protected Mode on the Advanced tab of the Internet Options dialog.
- This policy setting determines whether Internet Explorer 11 uses 64-bit processes (for greater security) or 32-bit processes (for greater compatibility) when running in Enhanced Protected Mode on 64-bit versions of Windows.
-
-Important: Some ActiveX controls and toolbars may not be available when 64-bit processes are used.
-
-If you enable this policy setting, Internet Explorer 11 will use 64-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows.
-
-If you disable this policy setting, Internet Explorer 11 will use 32-bit tab processes when running in Enhanced Protected Mode on 64-bit versions of Windows.
-
-If you don't configure this policy setting, users can turn this feature on or off using Internet Explorer settings. This feature is turned off by default.
- This policy setting prevents ActiveX controls from running in Protected Mode when Enhanced Protected Mode is enabled. When a user has an ActiveX control installed that is not compatible with Enhanced Protected Mode and a website attempts to load the control, Internet Explorer notifies the user and gives the option to run the website in regular Protected Mode. This policy setting disables this notification and forces all websites to run in Enhanced Protected Mode.
-
-Enhanced Protected Mode provides additional protection against malicious websites by using 64-bit processes on 64-bit versions of Windows. For computers running at least Windows 8, Enhanced Protected Mode also limits the locations Internet Explorer can read from in the registry and the file system.
-
-When Enhanced Protected Mode is enabled, and a user encounters a website that attempts to load an ActiveX control that is not compatible with Enhanced Protected Mode, Internet Explorer notifies the user and gives the option to disable Enhanced Protected Mode for that particular website.
-
-If you enable this policy setting, Internet Explorer will not give the user the option to disable Enhanced Protected Mode. All Protected Mode websites will run in Enhanced Protected Mode.
-
-If you disable or do not configure this policy setting, Internet Explorer notifies users and provides an option to run websites with incompatible ActiveX controls in regular Protected Mode. This is the default behavior.
- This policy setting allows you to manage whether Internet Explorer uses HTTP 1.1.
-
-If you enable this policy setting, Internet Explorer uses HTTP 1.1.
-
-If you disable this policy setting, Internet Explorer does not use HTTP 1.1.
-
-If you do not configure this policy setting, users can configure Internet Explorer to use or not use HTTP 1.1.
- This policy setting allows you to manage whether Internet Explorer uses HTTP 1.1 through proxy connections.
-
-If you enable this policy setting, Internet Explorer uses HTTP 1.1 through proxy connections.
-
-If you disable this policy setting, Internet Explorer does not use HTTP 1.1 through proxy connections.
-
-If you do not configure this policy setting, users can configure Internet Explorer to use or not use HTTP 1.1 through proxy connections.
- This policy setting determines whether Internet Explorer uses the SPDY/3 network protocol. SPDY/3 works with HTTP requests to optimize the latency of network requests through compression, multiplexing and prioritization.
-
-If you enable this policy setting, Internet Explorer uses the SPDY/3 network protocol.
-
-If you disable this policy setting, Internet Explorer won't use the SPDY/3 network protocol.
-
-If you don't configure this policy setting, users can turn this behavior on or off, using Internet Explorer Advanced Internet Options settings. The default is on.
- This policy setting determines whether Internet Explorer uses the HTTP2 network protocol. HTTP2 requests help optimize the latency of network requests through compression, multiplexing, and prioritization.
-
-If you enable this policy setting, Internet Explorer uses the HTTP2 network protocol.
-
-If you disable this policy setting, Internet Explorer won't use the HTTP2 network protocol.
-
-If you don't configure this policy setting, users can turn this behavior on or off, using Internet Explorer Advanced Internet Options settings. The default is on.
- This policy setting allows you to block an insecure fallback to SSL 3.0. When this policy is enabled, Internet Explorer will attempt to connect to sites using SSL 3.0 or below when TLS 1.0 or greater fails.
-
-We recommend that you do not allow insecure fallback in order to prevent a man-in-the-middle attack.
-
-This policy does not affect which security protocols are enabled.
-
-If you disable this policy, system defaults will be used.
-
- This policy setting allows you to turn off support for Transport Layer Security (TLS) 1.0, TLS 1.1, TLS 1.2, Secure Sockets Layer (SSL) 2.0, or SSL 3.0 in the browser. TLS and SSL are protocols that help protect communication between the browser and the target server. When the browser attempts to set up a protected communication with the target server, the browser and server negotiate which protocol and version to use. The browser and server attempt to match each other’s list of supported protocols and versions, and they select the most preferred match.
-
-If you enable this policy setting, the browser negotiates or does not negotiate an encryption tunnel by using the encryption methods that you select from the drop-down list.
-
-If you disable or do not configure this policy setting, the user can select which encryption method the browser supports.
-
-Note: SSL 2.0 is off by default and is no longer supported starting with Windows 10 Version 1607. SSL 2.0 is an outdated security protocol, and enabling SSL 2.0 impairs the performance and functionality of TLS 1.0.
- This policy setting allows you to manage whether users can access the Print menu. Starting with Windows 8, this policy setting also allows you to manage whether users can access the Print flyout for Internet Explorer and any printers under the Devices charm.
-
-If you enable this policy setting, the Print menu in Internet Explorer will not be available. Starting with Windows 8, the Print flyout for Internet Explorer will not be available, and users will not see printers under the Devices charm.
-
-If you disable or do not configure this policy setting, the Print menu in Internet Explorer will be available. Starting with Windows 8, the Print flyout for Internet Explorer will be available, and users will see installed printers under the Devices charm.
- This policy setting determines whether a user can swipe across a screen or click Forward to go to the next pre-loaded page of a website.
-
-Microsoft collects your browsing history to improve how flip ahead with page prediction works. This feature isn't available for Internet Explorer for the desktop.
-
-If you enable this policy setting, flip ahead with page prediction is turned off and the next webpage isn't loaded into the background.
-
-If you disable this policy setting, flip ahead with page prediction is turned on and the next webpage is loaded into the background.
-
-If you don't configure this setting, users can turn this behavior on or off, using the Settings charm.
- This policy setting determines whether Internet Explorer preemptively loads websites and content in the background, speeding up performance such that when the user clicks a hyperlink, the background page seamlessly switches into view.
-
-If you enable this policy setting, Internet Explorer doesn't load any websites or content in the background.
-
-If you disable this policy setting, Internet Explorer preemptively loads websites and content in the background.
-
-If you don't configure this policy setting, users can turn this behavior on or off, using Internet Explorer settings. This feature is turned on by default
- This policy setting allows you to configure how Internet Explorer sends the Do Not Track (DNT) header.
-
-If you enable this policy setting, Internet Explorer sends a DNT:1 header with all HTTP and HTTPS requests. The DNT:1 header signals to the servers not to track the user.
-
-For Internet Explorer 9 and 10:
-If you disable this policy setting, Internet Explorer only sends the Do Not Track header if a Tracking Protection List is enabled or inPrivate Browsing mode is used.
-
-For at least Internet Explorer 11:
-If you disable this policy setting, Internet Explorer only sends the Do Not Track header if inPrivate Browsing mode is used.
-
-If you don't configure the policy setting, users can select the Always send Do Not Track header option, in Internet Explorer settings. By selecting this option, Internet Explorer sends a DNT:1 header with all HTTP and HTTPS requests; unless the user grants a site-specific exception. Internet Explorer sends a DNT:0 header to any sites granted an exception. By default, this option is turned on.
- This policy setting shows the Content Advisor setting on the Content tab of the Internet Options dialog box.
-
-If you enable this policy setting, Internet Explorer displays the Content Advisor setting on the Content tab of the Internet Options dialog box. Users can change Content Advisor settings.
-
-If you disable or do not configure this policy setting, Internet Explorer does not display the Content Advisor setting on the Content tab of the Internet Options dialog box.
-
-Note: This policy is no longer supported starting with Windows 10 Version 1607.
- Use no secure protocols
- Only use SSL 2.0
- Only use SSL 3.0
- Use SSL 2.0 and SSL 3.0
- Only use TLS 1.0
- Use SSL 2.0 and TLS 1.0
- Use SSL 3.0 and TLS 1.0
- Use SSL 2.0, SSL 3.0, and TLS 1.0
- Only use TLS 1.1
- Use SSL 2.0 and TLS 1.1
- Use SSL 3.0 and TLS 1.1
- Use SSL 2.0, SSL 3.0, and TLS 1.1
- Use TLS 1.0 and TLS 1.1
- Use SSL 2.0, TLS 1.0, and TLS 1.1
- Use SSL 3.0, TLS 1.0, and TLS 1.1
- Use SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.1
- Only use TLS 1.2
- Use SSL 2.0 and TLS 1.2
- Use SSL 3.0 and TLS 1.2
- Use SSL 2.0, SSL 3.0, and TLS 1.2
- Use TLS 1.0 and TLS 1.2
- Use SSL 2.0, TLS 1.0, and TLS 1.2
- Use SSL 3.0, TLS 1.0, and TLS 1.2
- Use SSL 2.0, SSL 3.0, TLS 1.0, and TLS 1.2
- Use TLS 1.1 and TLS 1.2
- Use SSL 2.0, TLS 1.1, and TLS 1.2
- Use SSL 3.0, TLS 1.1, and TLS 1.2
- Use SSL 2.0, SSL 3.0, TLS 1.1, and TLS 1.2
- Use TLS 1.0, TLS 1.1, and TLS 1.2
- Use SSL 2.0, TLS 1.0, TLS 1.1, and TLS 1.2
- Use SSL 3.0, TLS 1.0, TLS 1.1, and TLS 1.2
- Use SSL 2.0, SSL 3.0, TLS 1.0, TLS 1.1, and TLS 1.2
- Only use TLS 1.3
- Use TLS 1.2 and TLS 1.3
- Use TLS 1.1, TLS 1.2, and TLS 1.3
- Use TLS 1.0, TLS 1.1, TLS 1.2, and TLS 1.3
- Use SSL 3.0, TLS 1.0, TLS 1.1, TLS 1.2, and TLS 1.3
- Lock all toolbars
- Lock location of Stop and Refresh buttons
- about:blank
- New tab page
- Home page
- New tab page with my news feed
- Specify default behavior for a new tab
- Disable changing secondary home page settings
- Customize command labels
- Set tab process growth
- Allow Internet Explorer 8 shutdown behavior
- Use large icons for command buttons
- Display tabs on a separate row
- Show only icons
- Show selective text
- Show all text labels
- Hide the Command bar
- Hide the status bar
- This policy setting allows you to show or hide the Command bar.
-
-If you enable this policy setting, the Command bar is hidden and the user cannot choose to show it.
-
-If you disable this policy setting, the Command bar is shown and the user cannot choose to hide it.
-
-If you do not configure this policy setting, the Command bar is shown by default, and the user can choose to hide it.
- This policy setting allows you to show or hide the status bar.
-
-If you enable this policy setting, the status bar is hidden and the user cannot choose to show it.
-
-If you disable this policy setting, the status bar is shown and the user cannot choose to hide it.
-
-If you do not configure this policy setting, the status bar is shown by default, and the user can choose to hide it.
- This policy setting allows you to lock or unlock the toolbars on the user interface.
-
-If you enable this policy setting, the toolbars are locked and the user cannot move them.
-
-If you disable this policy setting, the toolbars are unlocked and the user can move them.
-
-If you do not configure this policy setting, the toolbars are locked by default, but the user can unlock them through the shortcut menu of the Command bar.
- This policy setting allows you to lock the Stop and Refresh buttons next to the Back and Forward buttons.
-
-If you enable this policy setting, the Stop and Refresh buttons are next to the Forward and Back buttons, and the user cannot move them.
-
-If you disable this policy setting, the Stop and Refresh buttons are next to the Address bar, and the user cannot move them.
-
-If you do not configure this policy setting, the Stop and Refresh buttons are next to the Address bar by default, and the user can choose to move them.
- This policy setting allows you to specify what is displayed when the user opens a new tab.
-
-If you enable this policy setting, you can choose which page to display when the user opens a new tab: blank page (about:blank), the first home page, the new tab page or the new tab page with my news feed.
-
-If you disable or do not configure this policy setting, the user can select his or her preference for this behavior.
- Secondary home pages are the default Web pages that Internet Explorer loads in separate tabs from the home page whenever the browser is run. This policy setting allows you to set default secondary home pages.
-
-If you enable this policy setting, you can specify which default home pages should load as secondary home pages. The user cannot set custom default secondary home pages.
-
-If you disable or do not configure this policy setting, the user can add secondary home pages.
-
-Note: If the “Disable Changing Home Page Settings” policy is enabled, the user cannot add secondary home pages.
- This policy setting allows you to choose among three different labels for command buttons: show all text labels, show selective text, or show only icons.
-
-If you enable this policy setting, command buttons are displayed according to which one of the following options you choose, and the user cannot change how command buttons are displayed:
-
-Show all text labels: All command buttons have only text.
-
-Show selective text: Some command buttons have only text; some have icons and text.
-
-Show only icons: All command buttons have only icons.
-
-If you disable or do not configure this policy setting, the command buttons show selective text by default, and the user can change this.
- This policy setting allows you to set the rate at which Internet Explorer creates new tab processes. There are two algorithms that Internet Explorer uses.
-
-The default algorithm has four settings: low, medium, high, or default. Low creates very few tab processes; medium creates a moderate amount of tab processes; and high allows the tab process to grow very quickly and is intended only for computers that have ample physical memory. The default setting creates the optimal number of tab processes based on the operating system and amount of physical memory. We recommend the default setting.
-
-The second algorithm must be explicitly enabled through the creation of an integer setting. In this case, each Internet Explorer isolation setting will quickly grow to use the specified integer number of tab processes, regardless of the physical memory on the computer or how many Internet Explorer isolation settings are running.
-
-If you enable this policy setting, you set the rate at which Internet Explorer creates new tab processes to low, medium, or high, or to an integer.
-
-If you disable or do not configure this policy setting, the tab process growth is set to the default. The user can change this value by using the registry key. Note: On Terminal Server, the default value is the integer “1”.
- This policy setting allows you to revert to the Internet Explorer 8 behavior of allowing OnUnLoad script handlers to display UI during shutdown. This policy setting may be needed to fix compatibility problems with particular web applications.
-
-If you enable this policy setting, OnUnLoad script handlers display UI during shutdown.
-
-If you disable or do not configure this policy setting, OnUnLoad script handlers do not display UI during shutdown (default behavior in Internet Explorer 9).
- This policy setting allows you increase the size of icons for command buttons.
-
-If you enable this policy setting, icons for command buttons are 20 x 20 pixels and cannot be made smaller (16 x 16 pixels).
-
-If you disable this policy setting, icons for command buttons are 16 x 16 pixels (the default) and cannot be made bigger (20 x 20 pixels).
-
-If you do not configure this policy setting, icons for command buttons are 16 x 16 pixels, and the user can make them bigger (20 x 20 pixels).
- This policy setting allows you to manage where tabs are displayed.
-
-If you enable this policy setting, tabs are displayed on a separate row.
-
-If you disable this policy setting, tabs are not displayed on a separate row.
-
-If you do not configure this policy setting, the user can change where tabs are displayed.
- Turn off suggestions for all user-installed providers
- Turn off the quick pick menu
- This policy setting allows you to turn off suggestions for all user-installed search providers.
-
-If you enable this policy setting, the user cannot view suggestions for user-installed search providers.
-
-If you disable or do not configure this policy setting, the user can choose to view suggestions for all user-installed search providers that offer suggestions.
- This policy setting allows you to prevent the quick pick menu from appearing when a user clicks in the Search box.
-
-If you enable this policy setting, when a user clicks in the Search box, the quick pick menu does not appear until the user starts typing.
-
-If you disable or do not configure this policy setting, when a user clicks in the Search box, the quick pick menu appears.
- Turn off ActiveX Opt-In prompt
- Prevent per-user installation of ActiveX controls
- Specify use of ActiveX Installer Service for installation of ActiveX controls
- Turn on Suggested Sites
- This policy setting allows you to turn off the ActiveX Opt-In prompt. ActiveX Opt-In prevents websites from loading any ActiveX control without prior approval. If a website attempts to load an ActiveX control that Internet Explorer has not used before, a Notification bar will appear, asking the user for approval.
-
-If you enable this policy setting, the ActiveX Opt-In prompt does not appear. Internet Explorer does not ask the user for permission to load an ActiveX control, and Internet Explorer loads the control if it passes all other internal security checks.
-
-If you disable or do not configure this policy setting, the ActiveX Opt-In prompt appears.
- This policy setting allows you to prevent the installation of ActiveX controls on a per-user basis.
-
-If you enable this policy setting, ActiveX controls cannot be installed on a per-user basis.
-
-If you disable or do not configure this policy setting, ActiveX controls can be installed on a per-user basis.
- This policy setting allows you to specify how ActiveX controls are installed.
-
-If you enable this policy setting, ActiveX controls are installed only if the ActiveX Installer Service is present and has been configured to allow the installation of ActiveX controls.
-
-If you disable or do not configure this policy setting, ActiveX controls, including per-user controls, are installed through the standard installation process.
- This policy setting controls the Suggested Sites feature, which recommends websites based on the user’s browsing activity. Suggested Sites reports a user’s browsing history to Microsoft to suggest sites that the user might want to visit.
-
-If you enable this policy setting, the user is not prompted to enable Suggested Sites. The user’s browsing history is sent to Microsoft to produce suggestions.
-
-If you disable this policy setting, the entry points and functionality associated with this feature are turned off.
-
-If you do not configure this policy setting, the user can turn on and turn off the Suggested Sites feature.
- Privacy
- Turn off InPrivate Browsing
- This policy setting allows you to turn off the InPrivate Browsing feature.
-
-InPrivate Browsing prevents Internet Explorer from storing data about a user's browsing session. This includes cookies, temporary Internet files, history, and other data.
-
-If you enable this policy setting, InPrivate Browsing is turned off.
-
-If you disable this policy setting, InPrivate Browsing is available for use.
-
-If you do not configure this policy setting, InPrivate Browsing can be turned on or off through the registry.
- Prevent the computer from loading toolbars and Browser Helper Objects when InPrivate Browsing starts
- This policy setting allows you to choose whether or not toolbars and Browser Helper Objects (BHOs) are loaded by default during an InPrivate Browsing session.
-
-Toolbars and BHOs may store data about a user's browsing session. By default, the computer does not load them when InPrivate Browsing starts.
-
-If you enable this policy setting, toolbars and BHOs are not loaded by default during an InPrivate Browsing session.
-
-If you disable this policy setting, toolbars and BHOs are loaded by default during an InPrivate Browsing session.
-
-If you do not configure this policy setting, it can be configured on the Privacy tab in Internet Options.
- Turn off collection of InPrivate Filtering data
- This policy setting allows you to turn off the collection of data used by the InPrivate Filtering Automatic mode.
-
-The data consists of the URLs of third-party content, along with data about the first-party websites that referenced it. It is collected during non-InPrivate (normal) browsing sessions.
-
-If you enable this policy setting, InPrivate Filtering data collection is turned off.
-
-If you disable this policy setting, InPrivate Filtering collection is turned on.
-
-If you do not configure this policy setting, InPrivate Filtering data collection can be turned on or off on the Privacy tab in Internet Options.
- Establish InPrivate Filtering threshold
- This policy setting allows you to establish the threshold for InPrivate Filtering Automatic mode.
-
-The threshold sets the number of first-party sites that a particular third-party item can be referenced from before it is blocked. Setting this value lower can help prevent more third-party sites from obtaining details about a user's browsing. However, doing so may cause compatibility issues on some websites. The allowed value range is 3 through 30.
-
-If you enable this policy setting, the selected value is enforced.
-
-If you disable or do not configure this policy setting, the user can establish the InPrivate Filtering threshold by clicking the Safety button and then clicking InPrivate Filtering.
- Establish Tracking Protection threshold
- This policy setting allows you to establish the threshold for Tracking Protection Automatic mode.
-
-The threshold sets the number of first-party sites that a particular third-party item can be referenced from before it is blocked. Setting this value lower can help prevent more third-party sites from obtaining details about a user's browsing. However, doing so may cause compatibility issues on some websites. The allowed value range is 3 through 30.
-
-If you enable this policy setting, the selected value is enforced.
-
-If you disable or do not configure this policy setting, the user can establish the Tracking Protection threshold by clicking the Safety button and then clicking Tracking Protection.
- Turn off InPrivate Filtering
- This policy setting allows you to turn off InPrivate Filtering.
-
-InPrivate Filtering helps users control whether third parties can automatically collect information about their browsing based on the sites that they visit. InPrivate Filtering does this by identifying third-party content that is used by multiple websites that users have visited.
-
-If you enable this policy setting, InPrivate Filtering is turned off in all browsing sessions, and InPrivate Filtering data is not collected.
-
-If you disable this policy setting, InPrivate Filtering is available for use.
-
-If you do not configure this policy setting, it can be configured through the registry.
- Turn off Tracking Protection
- This policy setting allows you to turn off Tracking Protection.
-
-Tracking Protection helps users control whether third parties can automatically collect information about their browsing based on the sites that they visit. Tracking Protection does this by identifying third-party content that is used by multiple websites that users have visited.
-
-If you enable this policy setting, Tracking Protection is disabled in all browsing sessions, and Tracking Protection data is not collected.
-
-If you disable this policy setting, Tracking Protection is available for use.
-
-If you do not configure this policy setting, it can be configured through the registry.
- Accelerators
- Add non-default Accelerators
- Add default Accelerators
- This policy setting allows you to add non-default Accelerators.
-
-If you enable this policy setting, the specified Accelerators are added to the user's browser. The user can append other Accelerators to this list, but the user cannot remove or change the Accelerators that this policy setting has added. Default and non-default Accelerators should not overlap.
-
-If you disable or do not configure this policy setting, the user has Accelerators that are provided through first use of the browser.
- This policy setting allows you to add default Accelerators.
-
-If you enable this policy setting, the specified Accelerators are added to the user's browser. The user can append other Accelerators to this list, but the user cannot remove or change the Accelerators that this policy setting has added. Default and non-default Accelerators should not overlap.
-
-If you disable or do not configure this policy setting, the user has Accelerators that are provided through first use of the browser.
- This policy setting allows you to manage whether users can access Accelerators.
-
-If you enable this policy setting, users cannot access Accelerators.
-
-If you disable or do not configure this policy setting, users can access Accelerators and install new Accelerators.
- This policy setting restricts the list of Accelerators that the user can access to only the set deployed through Group Policy.
-
-If you enable this policy setting, the user can access only Accelerators that are deployed through Group Policy. The user cannot add or delete Accelerators.
-
-If you disable or do not configure this policy setting, the user can access any Accelerators that he or she has installed.
- Turn off Accelerators
- Restrict Accelerators to those deployed through Group Policy
- Compatibility View
- Turn on Internet Explorer 7 Standards Mode
- Turn off Compatibility View
- Turn on Internet Explorer Standards Mode for local intranet
- Turn off Compatibility View button
- Use Policy List of Internet Explorer 7 sites
- Use Policy List of Quirks Mode sites
- Include updated website lists from Microsoft
- This policy setting allows you to turn on Internet Explorer 7 Standards Mode. Compatibility View determines how Internet Explorer identifies itself to a web server and determines whether content is rendered in Internet Explorer 7 Standards Mode or the Standards Mode available in the latest version of Internet Explorer.
-
-If you enable this policy setting, Internet Explorer uses an Internet Explorer 7 user agent string (with an additional string appended). Additionally, all Standards Mode webpages appear in Internet Explorer 7 Standards Mode. This option results in the greatest compatibility with existing webpages, but newer content written to common Internet standards may be displayed incorrectly.
-
-If you disable this policy setting, Internet Explorer uses a current user agent string. Additionally, all Standards Mode webpages appear in the Standards Mode available in the latest version of Internet Explorer. This option matches the default behavior of Internet Explorer.
-
-If you do not configure this policy setting, the user can turn on and turn off Internet Explorer 7 Standards Mode.
- This policy setting controls the Compatibility View feature, which allows the user to fix website display problems that he or she may encounter while browsing.
-
-If you enable this policy setting, the user cannot use the Compatibility View button or manage the Compatibility View sites list.
-
-If you disable or do not configure this policy setting, the user can use the Compatibility View button and manage the Compatibility View sites list.
- This policy setting controls how Internet Explorer displays local intranet content. Intranet content is defined as any webpage that belongs to the local intranet security zone.
-
-If you enable this policy setting, Internet Explorer uses the current user agent string for local intranet content. Additionally, all local intranet Standards Mode pages appear in the Standards Mode available with the latest version of Internet Explorer. The user cannot change this behavior through the Compatibility View Settings dialog box.
-
-If you disable this policy setting, Internet Explorer uses an Internet Explorer 7 user agent string (with an additional string appended) for local intranet content. Additionally, all local intranet Standards Mode pages appear in Internet Explorer 7 Standards Mode. The user cannot change this behavior through the Compatibility View Settings dialog box.
-
-If you do not configure this policy setting, Internet Explorer uses an Internet Explorer 7 user agent string (with an additional string appended) for local intranet content. Additionally, all local intranet Standards Mode pages appear in Internet Explorer 7 Standards Mode. This option results in the greatest compatibility with existing webpages, but newer content written to common Internet standards may be displayed incorrectly. This option matches the default behavior of Internet Explorer.
- This policy setting controls the Compatibility View button that appears on the Command bar. This button allows the user to fix website display problems that he or she may encounter while browsing.
-
-If you enable this policy setting, the user cannot use the Compatibility View button.
-
-If you disable or do not configure this policy setting, the user can use the Compatibility View button.
- This policy setting allows you to add specific sites that must be viewed in Internet Explorer 7 Compatibility View.
-
-If you enable this policy setting, the user can add and remove sites from the list, but the user cannot remove the entries that you specify.
-
-If you disable or do not configure this policy setting, the user can add and remove sites from the list.
- Compatibility View determines how Internet Explorer identifies itself to a web server and determines whether content is rendered in Quirks Mode or the Standards Mode available in the latest version of Internet Explorer.
-
-If you enable this policy setting, Internet Explorer uses an Internet Explorer 7 user agent string (with an additional string appended). Additionally, webpages included in this list appear in Quirks Mode.
- Turn on certificate address mismatch warning
- This policy setting allows you to turn on the certificate address mismatch security warning. When this policy setting is turned on, the user is warned when visiting Secure HTTP (HTTPS) websites that present certificates issued for a different website address. This warning helps prevent spoofing attacks.
-
-If you enable this policy setting, the certificate address mismatch warning always appears.
-
-If you disable or do not configure this policy setting, the user can choose whether the certificate address mismatch warning appears (by using the Advanced page in the Internet Control panel).
- This policy controls the website compatibility lists that Microsoft provides. The updated website lists are available on Windows Update.
-
-If you enable this policy setting, the Microsoft-provided website lists are used during browser navigation. If a user visits a site on the compatibility lists, the pages are automatically displayed in Compatibility View.
-
-If you disable this policy setting, the Microsoft-provided website lists are not used. Additionally, the user cannot activate the feature by using the Compatibility View Settings dialog box.
-
-If you do not configure this policy setting, the Microsoft-provided website lists are not active. The user can activate the feature by using the Compatibility View Settings dialog box.
- Turn off Reopen Last Browsing Session
- This policy setting allows you to manage whether a user has access to the Reopen Last Browsing Session feature in Internet Explorer.
-
-If you enable this policy setting, the user cannot use the Reopen Last Browsing Session feature.
-
-If you disable or do not configure this policy setting, the user can use the Reopen Last Browsing Session feature.
- Turn off ability to pin sites in Internet Explorer on the desktop
- This policy setting allows you to manage whether users can pin sites to locations where pinning is allowed, such as the taskbar, the desktop, or File Explorer.
-
-If you enable this policy setting, users cannot pin sites.
-
-If you disable or do not configure this policy setting, users can pin sites.
- Let users turn on and use Enterprise Mode from the Tools menu
- This policy setting lets you decide whether users can turn on Enterprise Mode for websites with compatibility issues. Optionally, this policy also lets you specify where to get reports (through post messages) about the websites for which users turn on Enterprise Mode using the Tools menu.
-
-If you turn this setting on, users can see and use the Enterprise Mode option from the Tools menu. If you turn this setting on, but don't specify a report location, Enterprise Mode will still be available to your users, but you won't get any reports.
-
-If you disable or don't configure this policy setting, the menu option won't appear and users won't be able to run websites in Enterprise Mode.
- Send all sites not included in the Enterprise Mode Site List to Microsoft Edge
- This setting lets you decide whether to open all sites not included in the Enterprise Mode Site List in Microsoft Edge. If you use this setting, you must also turn on the Administrative Templates\Windows Components\Internet Explorer\Use the Enterprise Mode IE website list policy setting and you must include at least one site in the Enterprise Mode Site List.
-
-Enabling this setting automatically opens all sites not included in the Enterprise Mode Site List in Microsoft Edge.
-
-Disabling, or not configuring this setting, opens all sites based on the currently active browser.
-
-Note: If you've also enabled the Administrative Templates\Windows Components\Microsoft Edge\Send all intranet sites to Internet Explorer 11 policy setting, then all intranet sites will continue to open in Internet Explorer 11.
- Show message when opening sites in Microsoft Edge using Enterprise Mode
- This policy setting lets you decide whether employees see an additional page in Internet Explorer 11, stating that a site has been opened using Microsoft Edge with Enterprise Mode.
-
-If you enable this setting, employees see an additional page in Internet Explorer 11, stating that a site has been opened using Microsoft Edge with Enterprise Mode.
-
-If you disable or don't configure this setting, the default app behavior occurs and no additional page appears.
- Configure which channel of Microsoft Edge to use for opening redirected sites
- Enables you to configure up to three versions of Microsoft Edge to open a redirected site (in order of preference). Use this policy if your environment is configured to redirect sites from Internet Explorer 11 to Microsoft Edge. If any of the chosen versions are not installed on the device, that preference will be bypassed.
-
-If both the Windows Update for the next version of Microsoft Edge* and Microsoft Edge Stable channel are installed, the following behaviors occur:
-- If you disable or don't configure this policy, Microsoft Edge Stable channel is used. This is the default behavior.
-- If you enable this policy, you can configure redirected sites to open in up to three of the following channels where:
- 1 = Microsoft Edge Stable
- 2 = Microsoft Edge Beta version 77 or later
- 3 = Microsoft Edge Dev version 77 or later
- 4 = Microsoft Edge Canary version 77 or later
-
-If the Windows Update for the next version of Microsoft Edge* or Microsoft Edge Stable channel are not installed, the following behaviors occur:
-- If you disable or don't configure this policy, Microsoft Edge version 45 or earlier is automatically used. This is the default behavior.
-- If you enable this policy, you can configure redirected sites to open in up to three of the following channels where:
- 0 = Microsoft Edge version 45 or earlier
- 1 = Microsoft Edge Stable
- 2 = Microsoft Edge Beta version 77 or later
- 3 = Microsoft Edge Dev version 77 or later
- 4 = Microsoft Edge Canary version 77 or later
-
-*For more information about the Windows update for the next version of Microsoft Edge including how to disable it, see https://go.microsoft.com/fwlink/?linkid=2102115. This update applies only to Windows 10 version 1709 and higher.
-
- Microsoft Edge Stable
- Microsoft Edge Beta version 77 or later
- Microsoft Edge Dev version 77 or later
- Microsoft Edge Canary version 77 or later
- Microsoft Edge version 45 or earlier
- Keep all intranet sites in Internet Explorer
- Prevents intranet sites from being opened in any browser except Internet Explorer. But note that If the ‘Send all sites not included in the Enterprise Mode Site List to Microsoft Edge’ (‘RestrictIE’) policy isn’t enabled, this policy has no effect.
-
-If you enable this policy, all intranet sites are opened in Internet Explorer 11. The only exceptions are sites listed in your Enterprise Mode Site List.
-
-If you disable or don’t configure this policy, all intranet sites are automatically opened in Microsoft Edge.
-
-We strongly recommend keeping this policy in sync with the ‘Send all intranet sites to Internet Explorer’ (‘SendIntranetToInternetExplorer’) policy. Additionally, it’s best to enable this policy only if your intranet sites have known compatibility problems with Microsoft Edge.
-
-Related policies:
-- Send all intranet sites to Internet Explorer (‘SendIntranetToInternetExplorer’)
-- Send all sites not included in the Enterprise Mode Site List to Microsoft Edge (‘RestrictIE’)
-
-For more info about how to use this policy together with other related policies to create the optimal configuration for your organization, see https://go.microsoft.com/fwlink/?linkid=2094210.
- Allow "Save Target As" in Internet Explorer mode
- This policy setting allows admins to enable "Save Target As" context menu in Internet Explorer mode.
-
-If you enable this policy, "Save Target As" will show up in the Internet Explorer mode context menu and work the same as Internet Explorer.
-
-If you disable or do not configure this policy setting, "Save Target As" will not show up in the Internet Explorer mode context menu.
-
-For more information, see https://go.microsoft.com/fwlink/?linkid=2102115
- Enable global window list in Internet Explorer mode
- This setting allows Internet Explorer mode to use the global window list that enables sharing state with other applications.
-The setting will take effect only when Internet Explorer 11 is disabled as a standalone browser.
-
-If you enable this policy, Internet Explorer mode will use the global window list.
-
-If you disable or don’t configure this policy, Internet Explorer mode will continue to maintain a separate window list.
-
-To learn more about Internet Explorer mode, see https://go.microsoft.com/fwlink/?linkid=2102921
-To learn more about disabling Internet Explorer 11 as a standalone browser, see https://go.microsoft.com/fwlink/?linkid=2168340
- Enable extended hot keys in Internet Explorer mode
- This policy setting lets admins enable extended Microsoft Edge Internet Explorer mode hotkeys, such as "Ctrl+S" to have "Save as" functionality.
-
-If you enable this policy, extended hotkey functionality is enabled in Internet Explorer mode and work the same as Internet Explorer.
-
-If you disable, or don't configure this policy, extended hotkeys will not work in Internet Explorer mode.
-
-For more information, see https://go.microsoft.com/fwlink/?linkid=2102115
- Reset zoom to default for HTML dialogs in Internet Explorer mode
- This policy setting lets admins reset zoom to default for HTML dialogs in Internet Explorer mode.
-
-If you enable this policy, the zoom of an HTML dialog in Internet Explorer mode will not get propagated from its parent page.
-
-If you disable, or don't configure this policy, the zoom of an HTML dialog in Internet Explorer mode will be set based on the zoom of it's parent page.
-
-For more information, see https://go.microsoft.com/fwlink/?linkid=2102115
- Disable Internet Explorer 11 as a standalone browser
- This policy lets you restrict launching of Internet Explorer as a standalone browser.
-
-If you enable this policy, it:
-- Prevents Internet Explorer 11 from launching as a standalone browser.
-- Restricts Internet Explorer's usage to Microsoft Edge's native 'Internet Explorer mode'.
-- Redirects all attempts at launching Internet Explorer 11 to Microsoft Edge Stable Channel browser.
-- Overrides any other policies that redirect to Internet Explorer 11.
-
-If you disable, or don’t configure this policy, all sites are opened using the current active browser settings. Note: Microsoft Edge Stable Channel must be installed for this policy to take effect.
- Hide Internet Explorer 11 retirement notification
- This policy setting allows you to manage whether the notification bar reminder that Internet Explorer is being retired is displayed. By default, the Notification bar is displayed in Internet Explorer 11.
-
-If you enable this policy setting, the Notification bar will not be displayed in Internet Explorer 11.
-
-If you disable, or do not configure, this policy setting, the Notification bar will be displayed in Internet Explorer 11.
- Never
- Always
- Once per user
- Replace JScript by loading JScript9Legacy in place of JScript via MSHTML/WebOC.
- This policy setting specifies whether JScript or JScript9Legacy is loaded for MSHTML/WebOC/MSXML/Cscript based invocations.
-
-If you enable this policy setting, JScript9Legacy will be loaded in situations where JScript is instantiated.
-
-If you disable this policy, then JScript will be utilized.
-
-If this policy is left unconfigured, then MSHTML will use JScript9Legacy and MSXML/Cscript will use JScript.
- Turn off blocking of outdated ActiveX controls for Internet Explorer
- This policy setting determines whether Internet Explorer blocks specific outdated ActiveX controls. Outdated ActiveX controls are never blocked in the Intranet Zone.
-
-If you enable this policy setting, Internet Explorer stops blocking outdated ActiveX controls.
-
-If you disable or don't configure this policy setting, Internet Explorer continues to block specific outdated ActiveX controls.
-
-For more information, see "Outdated ActiveX Controls" in the Internet Explorer TechNet library.
- Turn on ActiveX control logging in Internet Explorer
- This policy setting determines whether Internet Explorer saves log information for ActiveX controls.
-
-If you enable this policy setting, Internet Explorer logs ActiveX control information (including the source URI that loaded the control and whether it was blocked) to a local file.
-
-If you disable or don't configure this policy setting, Internet Explorer won't log ActiveX control information.
-
-Note that you can turn this policy setting on or off regardless of the "Turn off blocking of outdated ActiveX controls for Internet Explorer" or "Turn off blocking of outdated ActiveX controls for Internet Explorer on specific domains" policy settings.
-
-For more information, see "Outdated ActiveX Controls" in the Internet Explorer TechNet library.
- Turn off blocking of outdated ActiveX controls for Internet Explorer on specific domains
- This policy setting allows you to manage a list of domains on which Internet Explorer will stop blocking outdated ActiveX controls. Outdated ActiveX controls are never blocked in the Intranet Zone.
-
-If you enable this policy setting, you can enter a custom list of domains for which outdated ActiveX controls won't be blocked in Internet Explorer. Each domain entry must be formatted like one of the following:
-
-1. "domain.name.TLD". For example, if you want to include *.contoso.com/*, use "contoso.com"
-2. "hostname". For example, if you want to include http://example, use "example"
-3. "file:///path/filename.htm". For example, use "file:///C:/Users/contoso/Desktop/index.htm"
-
-If you disable or don't configure this policy setting, the list is deleted and Internet Explorer continues to block specific outdated ActiveX controls on all domains in the Internet Zone.
-
-For more information, see "Outdated ActiveX Controls" in the Internet Explorer TechNet library.
- Remove "Run this time" button for outdated ActiveX controls in Internet Explorer
- This policy setting allows you to stop users from seeing the "Run this time" button and from running specific outdated ActiveX controls in Internet Explorer.
-
-If you enable this policy setting, users won't see the "Run this time" button on the warning message that appears when Internet Explorer blocks an outdated ActiveX control.
-
-If you disable or don't configure this policy setting, users will see the "Run this time" button on the warning message that appears when Internet Explorer blocks an outdated ActiveX control. Clicking this button lets the user run the outdated ActiveX control once.
-
-For more information, see "Outdated ActiveX Controls" in the Internet Explorer TechNet library.
- Use the Enterprise Mode IE website list
- This policy setting lets you specify where to find the list of websites you want opened using Enterprise Mode IE, instead of Standard mode, because of compatibility issues. Users can't edit this list.
-
-If you enable this policy setting, Internet Explorer downloads the website list from your location (HKCU or HKLM\Software\policies\Microsoft\Internet Explorer\Main\EnterpriseMode), opening all listed websites using Enterprise Mode IE.
-
-If you disable or don't configure this policy setting, Internet Explorer opens all websites using Standards mode.
- General Page
- Browsing History
- Set default storage limits for websites
- This policy setting sets data storage limits for indexed database and application caches for individual websites. When you set this policy setting, you provide the cache limit, in MB.
-
-If you enable this policy setting, Internet Explorer displays a notification when a website exceeds the configured storage limit.
-
-If you disable or do not configure this policy setting, users can set default data storage limits for indexed databases and application caches.
- Allow websites to store indexed databases on client computers
- This policy setting allows websites to store indexed database cache information on client computers.
-
-If you enable this policy setting, websites will be able to store an indexed database on client computers. Allow website database and caches on Website Data Settings will be unavailable to users.
-
-If you disable this policy setting, websites will not be able to store an indexed database on client computers. Allow website database and caches on Website Data Settings will be unavailable to users.
-
-If you do not configure this policy setting, websites will be able to store an indexed database on client computers. Allow website database and caches on Website Data Settings will be available to users. Users can choose whether or not to allow websites to store data on their computers.
- Set indexed database storage limits for individual domains
- This policy setting sets data storage limits for indexed databases of websites that have been allowed to exceed their storage limit. The “Set default storage limits for websites” policy setting sets the data storage limits for indexed databases. If a domain exceeds the indexed database storage limit for an individual domain, Internet Explorer sends an error to the website. No notification is sent to the user. This group policy sets the maximum data storage limit for domains that are trusted by users. When you set this policy setting, you provide the cache limit, in MB. The default is 500 MB.
-
-If you enable this policy setting, Internet Explorer will allow trusted domains to store additional data in indexed databases, up to the limit set in this group policy.
-
-If you disable or do not configure this policy setting, Internet Explorer will use the default maximum storage limit for all indexed databases. The default is 500 MB.
- Set maximum indexed database storage limit for all domains
- This policy setting sets the data storage limit for all combined indexed databases for a user. When you set this policy setting, you provide the storage limit in MB. When the limit is reached, Internet Explorer notifies the user, and the user must delete indexed databases before an updated database can be saved on their computer. The default maximum storage limit for all indexed databases is 4 GB.
-
-If you enable this policy setting, you can set the maximum storage limit for all indexed databases. The default is 4 GB.
-
-If you disable or do not configure this policy setting, Internet Explorer will use the default maximum storage limit for all indexed databases. The default is 4 GB.
- Allow websites to store application caches on client computers
- This policy setting allows websites to store file resources in application caches on client computers.
-
-If you enable this policy setting, websites will be able to store application caches on client computers. Allow website database and caches on Website Data Settings will be unavailable to users.
-
-If you disable this policy setting, websites will not be able to store application caches on client computers. Allow website database and caches on Website Data Settings will be unavailable to users.
-
-If you do not configure this policy setting, websites will be able to store application caches on client computers. Allow website database and caches on Website Data Settings will be available to users. Users can choose whether or not to allow websites to store data on their computers.
- Set application cache storage limits for individual domains
- This policy setting sets file storage limits for application caches of websites that have been allowed to exceed their storage limit. The “Set default storage limits for websites” policy setting sets the data storage limits for application caches. If a domain exceeds the application cache storage limit for an individual domain, Internet Explorer sends an error to the website. No notification will be displayed to the user. This group policy sets the maximum file storage limit for domains that are trusted by users. When you set this policy setting, you provide the cache limit, in MB. The default is 50 MB.
-
-If you enable this policy setting, Internet Explorer will allow trusted domains to store additional files in application caches, up to the limit set in this policy setting.
-
-If you disable or do not configure this policy setting, Internet Explorer will use the default maximum storage limit for all application caches. The default is 50 MB.
- Set maximum application caches storage limit for all domains
- This policy setting sets the file storage limit for all combined application caches for a user. When you set this policy setting, you provide the storage limit in MB. When the limit is reached, Internet Explorer notifies the user, and the user must delete application caches before an updated one can be saved on their computer. The default maximum storage limit for all application caches is 1 GB.
-
-If you enable this policy setting, you can set the maximum storage limit for all application caches. The default is 1 GB.
-
-If you disable or do not configure this policy setting, Internet Explorer will use the default maximum storage limit for all application caches. The default is 1 GB.
- Set application caches expiration time limit for individual domains
- This policy setting sets the number of days an inactive application cache will exist before it is removed. If the application cache is used before the expiration time limit, it will not be automatically removed. When you set this policy setting, you provide the expiration time limit in days.
-
-If you enable this policy setting, Internet Explorer will remove application caches that haven't been used within the timeframe set in this policy setting.
-
-If you disable or do not configure this policy setting, Internet Explorer will use the default application cache expiration time limit for all application caches. The default is 30 days.
- Set maximum application cache resource list size
- This policy setting sets the maximum number of resource entries that can be specified in a manifest file associated with an application cache. If the manifest associated with an application cache exceeds the number of resources allowed, including the page that referenced the manifest, Internet Explorer sends an error to the website. No notification will be displayed to the user. When you set this policy setting, you provide the resource limit as a number. The default is 1000 resources.
-
-If you enable this policy setting, Internet Explorer will allow the creation of application caches whose manifest file contains the number of resources, including the page that referenced the manifest, that are less than or equal to the limit set in this policy setting.
-
-If you disable or do not configure this policy setting, Internet Explorer will use the default maximum application cache resource list size for all application caches. The default is 1000 resources.
- Set maximum application cache individual resource size
- This policy setting sets the maximum size for an individual resource file contained in a manifest file. The manifest file is used to create the application cache. If any file in the manifest exceeds the allowed size, Internet Explorer sends an error to the website. No notification will be displayed to the user. When you set this policy setting, you provide the resource size limit, in MB. The default is 50 MB.
-
-If you enable this policy setting, Internet Explorer will allow the creation of application caches whose individual manifest file entries are less than or equal to the size set in this policy setting.
-
-If you disable or do not configure this policy setting, Internet Explorer will use the default application cache individual resource size for all application caches resources. The default is 50 MB.
- Start Internet Explorer with tabs from last browsing session
- This policy setting configures what Internet Explorer displays when a new browsing session is started. By default, Internet Explorer displays the home page. In Internet Explorer 10, Internet Explorer can start a new browsing session with the tabs from the last browsing session.
-
-If you enable this policy setting, Internet Explorer starts a new browsing session with the tabs from the last browsing session. Users cannot change this option to start with the home page.
-
-If you disable this policy setting, Internet Explorer starts a new browsing session with the home page. Users cannot change this option to start with the tabs from the last browsing session.
-
-If you do not configure this policy setting, Internet Explorer starts with the home page. Users can change this option to start with the tabs from the last session.
- Open Internet Explorer tiles on the desktop
- This policy setting configures Internet Explorer to open Internet Explorer tiles on the desktop.
-
-If you enable this policy setting, Internet Explorer opens tiles only on the desktop.
-
-If you disable this policy setting, Internet Explorer does not open tiles on the desktop.
-
-If you do not configure this policy, users can choose how Internet Explorer tiles are opened.
- Set how links are opened in Internet Explorer
- This policy setting allows you to choose how links are opened in Internet Explorer: Let Internet Explorer decide, always in Internet Explorer, or always in Internet Explorer on the desktop.
-
-If you enable this policy setting, Internet Explorer enforces your choice. Users cannot change the setting.
-
-If you disable or do not configure this policy setting, users can choose how links are opened in Internet Explorer.
- Always in Internet Explorer on the desktop
- Always in Internet Explorer
- Let Internet Explorer decide
- Install new versions of Internet Explorer automatically
- This policy setting configures Internet Explorer to automatically install new versions of Internet Explorer when they are available.
-
-If you enable this policy setting, automatic upgrade of Internet Explorer will be turned on.
-
-If you disable this policy setting, automatic upgrade of Internet Explorer will be turned off.
-
-If you do not configure this policy, users can turn on or turn off automatic updates from the About Internet Explorer dialog.
-
-Note: This policy is deprecated starting with Windows 10 version 1703.
- Turn off phone number detection
- This policy setting determines whether phone numbers are recognized and turned into hyperlinks, which can be used to invoke the default phone application on the system.
-
-If you enable this policy setting, phone number detection is turned off. Users won't be able to modify this setting.
-
-If you disable this policy setting, phone number detection is turned on. Users won't be able to modify this setting.
-
-If you don't configure this policy setting, users can turn this behavior on or off, using Internet Explorer settings. The default is on.
- Turn on Site Discovery XML output
- Turn on Site Discovery WMI output
- Limit Site Discovery output by Domain
- Limit Site Discovery output by Zone
- This policy setting allows you to manage the XML output functionality of the Internet Explorer Site discovery Toolkit(SDTK). When enabled the feature will write data collected to an XML file at a location specified when setting this policy. When disabled, no data will be written to the XML file. Enabling or disabling this setting will not impact other output methods available for the SDTK.
- This policy setting allows you to manage the WMI output functionality of the Internet Explorer Site discovery Toolkit(SDTK). When enabled the feature will write data collected to a WMI class which can then be aggregated using a client management solution(SCCM) or other means. When disabled, no data will be written to the WMI class. Enabling or disabling this setting will not impact other output methods available for the SDTK.
- This policy setting allows you to control which Domains are included in the discovery functionality of the Internet Explorer Site discovery Toolkit(SDTK). When enabled the feature will collect data from sites that are part of the domains configured in the policy. When disabled, or not configured, all domains will be included in site discovery. This policy can be used in conjunction with other policies controlling sites included in Site Discovery.
-
-To configure the domain(s) included in data collection for the IE Site Discovery Toolkit, Add one domain per line to the text box. For example:
-
-microsoft.sharepoint.com
-outlook.com
-onedrive.com
-timecard.contoso.com
-LOBApp.contoso.com
- This policy setting allows you to control which site zones are included in the discovery functionality of the Internet Explorer Site discovery Toolkit(SDTK). When enabled the feature will collect data from sites that are part of the zones configured in the policy. When disabled or not configured all Zones will be included in site discovery. This policy can be used in conjunction with other policies controlling sites included in Site Discovery.
-
-To configure zone(s) included in site discovery, a binary number is formed based on the selected zones. The decimal representation of this number is used to represent this number in policy. For example:
-
-• 2 - Intranet site zone only
- Binary Representation - 00010
- • 0 - Restricted Sites Zone
- • 0 - Internet Zone
- • 0 - Trusted Sites Zone
- • 1 - Local Intranet Zone
- • 0 - Local Machine Zone
-• 6 - Intranet and Trusted site zones only
- Binary Representation - 00110
- • 0 - Restricted Sites Zone
- • 0 - Internet Zone
- • 1 - Trusted Sites Zone
- • 1 - Local Intranet Zone
- • 0 - Local Machine Zone
-• 22 - Trusted, Intranet, and Restricted site zones only
- Binary Representation - 10110
- • 1 - Restricted Sites Zone
- • 0 - Internet Zone
- • 1 - Trusted Sites Zone
- • 1 - Local Intranet Zone
- • 0 - Local Machine Zone
- Turn off automatic download of the ActiveX VersionList
- This setting determines whether IE automatically downloads updated versions of Microsoft’s VersionList.XML. IE uses this file to determine whether an ActiveX control should be stopped from loading.
-
-If you enable this setting, IE stops downloading updated versions of VersionList.XML. Turning off this automatic download breaks the out-of-date ActiveX control blocking feature by not letting the version list update with newly outdated controls, potentially compromising the security of your computer.
-
-If you disable or don't configure this setting, IE continues to download updated versions of VersionList.XML.
-
-For more information, see "Out-of-date ActiveX control blocking" in the Internet Explorer TechNet library.
- Disable HTML Application
- This policy setting specifies if running the HTML Application (HTA file) is blocked or allowed.
-
-If you enable this policy setting, running the HTML Application (HTA file) will be blocked.
-
-If you disable or do not configure this policy setting, running the HTML Application (HTA file) is allowed.
-
-
-
- Domain allow list
-
-
- Add-on List
-
-
-
-
- 255,0,0
-
-
-
- ActiveMovie Control
- Media Control
-
-
-
-
- 192,192,192
-
-
-
- CarPoint AutoPricer Control
-
-
-
-
- CODEBASE
-
-
-
- Select the desired behavior
-
-
- Select the desired behavior
-
-
-
-
-
-
-
- DHTML Edit Control
-
-
- Select phishing filter mode
-
-
- Select SmartScreen Filter mode for Internet Explorer 8
-
-
- Select SmartScreen Filter mode
-
-
-
-
-
-
-
-
-
-
-
-
- Shockwave Flash
-
-
- Default Size
-
-
-
-
- http://www.microsoft.com/isapi/redir.dll?prd=ie&ar=128bit
-
-
-
- Enter restricted protocols for this zone.
-
-
- Enter the allowed behaviors here.
-
-
- Process List:
-
-
- MSN Investor Chart Control
- MS Investor Ticker
-
-
- Open windows without address or status bars
-
-
- Only allow approved domains to use ActiveX controls without prompt
-
-
- Only allow approved domains to use ActiveX controls without prompt
-
-
- Only allow approved domains to use the TDC ActiveX control
-
-
- Only allow approved domains to use the TDC ActiveX control
-
-
- Allow video and animation on a Web page that uses a legacy media player
-
-
- Scriptlets
-
-
- First-Run Opt-In
-
-
- Include local directory path when uploading files to a server
-
-
- Use SmartScreen Filter
-
-
- Prompt for information using scripted windows
-
-
- Status bar updates via script
-
-
- Protected Mode
-
-
- Turn on Cross-Site Scripting (XSS) Filter
-
-
- Turn on Cross-Site Scripting (XSS) Filter
-
-
- Launching programs and unsafe files
-
-
- XAML browser applications
-
-
- Internet Explorer web browser control
-
-
- .NET Framework Setup
-
-
- XAML Files
-
-
- XPS documents
-
-
- Access data sources across domains
-
-
- Access data sources across domains
-
-
- Access data sources across domains
-
-
- Allow active scripting
-
-
- Allow active scripting
-
-
- Allow active scripting
-
-
- Allow META REFRESH
-
-
- Allow META REFRESH
-
-
- Allow paste operations via script
-
-
- Allow paste operations via script
-
-
- Allow Binary and Script Behaviors
-
-
- Allow Binary and Script Behaviors
-
-
- Allow Binary and Script Behaviors
-
-
- Use Pop-up Blocker
-
-
- Use Pop-up Blocker
-
-
- Display mixed content
-
-
- Download signed ActiveX controls
-
-
- Download signed ActiveX controls
-
-
- Download signed ActiveX controls
-
-
- Download unsigned ActiveX controls
-
-
- Download unsigned ActiveX controls
-
-
- Download unsigned ActiveX controls
-
-
- Allow drag and drop or copy and paste files
-
-
- Allow drag and drop or copy and paste files
-
-
- Render legacy filters
-
-
- Render legacy filters
-
-
- Allow file downloads
-
-
- Allow file downloads
-
-
- Allow font downloads
-
-
- Allow font downloads
-
-
- Allow installation of desktop items
-
-
- Allow installation of desktop items
-
-
- Allow installation of desktop items
-
-
- Locked-Down Internet
-
-
- Internet
-
-
- Locked-Down Intranet
-
-
- Intranet
-
-
- Java permissions
-
-
- Java permissions
-
-
- Java permissions
-
-
- Java permissions
-
-
- Launching applications and files in an IFRAME
-
-
- Launching applications and files in an IFRAME
-
-
- Launching applications and files in an IFRAME
-
-
- Locked-Down Local Machine Zone
-
-
- Local Machine Zone
-
-
- Logon options
-
-
- Logon options
-
-
- Logon options
-
-
- Enable MIME Sniffing
-
-
- Enable MIME Sniffing
-
-
- Enable dragging of content from different domains within a window
-
-
- Enable dragging of content from different domains across windows
-
-
- Navigate windows and frames across different domains
-
-
- Navigate windows and frames across different domains
-
-
- Allow active content over restricted protocols to access my computer
-
-
- Allow active content over restricted protocols to access my computer
-
-
- Do not prompt for client certificate selection when no certificates or only one certificate exists.
-
-
- Do not prompt for client certificate selection when no certificates or only one certificate exists.
-
-
- Automatic prompting for ActiveX controls
-
-
- Automatic prompting for ActiveX controls
-
-
- Automatic prompting for file downloads
-
-
- Automatic prompting for file downloads
-
-
- Locked-Down Restricted Sites
-
-
- Restricted Sites
-
-
- Run ActiveX controls and plugins
-
-
- Run ActiveX controls and plugins
-
-
- Script ActiveX controls marked safe for scripting
-
-
- Script ActiveX controls marked safe for scripting
-
-
- Don't run antimalware programs against ActiveX controls
-
-
- Don't run antimalware programs against ActiveX controls
-
-
- Initialize and script ActiveX controls not marked as safe
-
-
- Initialize and script ActiveX controls not marked as safe
-
-
- Scripting of Java applets
-
-
- Scripting of Java applets
-
-
- Run .NET Framework-reliant components signed with Authenticode
-
-
- Run .NET Framework-reliant components signed with Authenticode
-
-
- Software channel permissions
-
-
- Software channel permissions
-
-
- Software channel permissions
-
-
- Submit non-encrypted form data
-
-
- Submit non-encrypted form data
-
-
- Locked-Down Trusted Sites
-
-
- Trusted Sites
-
-
- Run .NET Framework-reliant components not signed with Authenticode
-
-
- Run .NET Framework-reliant components not signed with Authenticode
-
-
- Userdata persistence
-
-
- Userdata persistence
-
-
- Allow script-initiated windows without size or position constraints
-
-
- Allow script-initiated windows without size or position constraints
-
-
- Web sites in less privileged Web content zones can navigate into this zone
-
-
- Web sites in less privileged Web content zones can navigate into this zone
-
-
- Web sites in less privileged Web content zones can navigate into this zone
-
-
- Allow VBScript to run in Internet Explorer
-
-
- Allow VBScript to run in Internet Explorer
-
-
- Allow VBScript to run in Internet Explorer
-
-
- Enter the zone assignments here.
-
-
-
-
- 0,0,255
-
-
-
-
-
- 96,100,32
-
-
-
- Maximum size of subscriptions in kilobytes:
- Maximum number of offline pages:
- Minimum number of minutes between scheduled updates:
- Time to begin preventing scheduled updates:
- Time to end preventing scheduled updates:
- Maximum offline page crawl depth:
-
-
- Disable the Media Explorer Bar and auto-play feature
- Auto-Play Media files in the Media bar when enabled
-
-
- MCSiMenu
- Popup Menu Object
- Ikonic Menu Control
-
-
- Microsoft Agent Control
-
-
- MSChat Control
-
-
- MSNBC News Control
-
-
- NetShow File Transfer Control
-
-
- Select your choice
-
-
- Select tabbed browsing pop-up behavior
-
-
- Select where to open links
-
-
- Block attachments that could contain a virus
-
-
- Per domain(in kilobytes)
- Per document (in kilobytes)
-
-
- Per domain (in kilobytes)
- Per document (in kilobytes)
-
-
- Per domain (in kilobytes)
- Per document (in kilobytes)
-
-
- Per domain (in kilobytes)
- Per document (in kilobytes)
-
-
- Per domain (in kilobytes)
- Per document (in kilobytes)
-
-
- Enter the list of sites here.
-
-
- Prompt me to save passwords
-
-
- Days to keep pages in History
-
-
-
-
-
-
-
- Microsoft Scriptlet Component
-
-
- Microsoft Survey Control
-
-
- Select tab opening position
-
-
-
-
- 0,0,0
-
-
-
- Show Back button
- Show Forward button
- Show Stop button
- Show Refresh button
- Show Home button
- Show Search button
- Show Favorites button
- Show History button
- Show Folders button
- Show Fullscreen button
- Show Tools button
- Show Mail button
- Show Font size button
- Show Print button
- Show Edit button
- Show Discussions button
- Show Cut button
- Show Copy button
- Show Paste button
- Show Encoding button
-
-
- When searching from the Address bar:
-
-
- Underline links
-
-
- Update check interval (in days):
-
-
-
-
- http://www.microsoft.com/isapi/redir.dll?Prd=ie&Pver=5.0&Ar=ie5update
-
-
-
- When searching from the address bar:
-
-
- Maximum number of connections:
-
-
- Maximum number of connections:
-
-
-
- Secure Protocol combinations
-
-
- Allow insecure fallback for:
-
-
- New tab behavior
-
-
- Secondary home pages
-
-
- Command Labeling
-
-
-
-
-
-
-
- Threshold (3-30):
-
-
- Threshold (3-30):
-
-
- List of non-default Accelerators to install
-
-
- List of default Accelerators to install
-
-
- List of sites
-
-
- List of sites
-
-
- Set default storage limits for websites
-
-
- Set indexed database storage limits for individual domains
-
-
- Set maximum indexed database storage limit for all domains
-
-
- Domain Storage Limit
-
-
- Total Storage Limit
-
-
- Number of days
-
-
- Number of resources
-
-
- Maximum resource size
-
-
- Default browser launch behavior for links
-
-
-
-
-
-
-
- Zone mask
-
-
- Domain list
-
-
- First choice
- Second choice
- Third choice
-
-
- Notify that Internet Explorer 11 browser is disabled
-
-
-
-
diff --git a/policy_templates/en-US/KDC.adml b/policy_templates/en-US/KDC.adml
deleted file mode 100644
index 60a6ec8..0000000
--- a/policy_templates/en-US/KDC.adml
+++ /dev/null
@@ -1,151 +0,0 @@
-
-
-
- KDC Settings
- Configuration settings for the Kerberos Key Distribution Center.
-
-
- KDC
- Use forest search order
- This policy setting defines the list of trusting forests that the Key Distribution Center (KDC) searches when attempting to resolve two-part service principal names (SPNs).
-
-If you enable this policy setting, the KDC will search the forests in this list if it is unable to resolve a two-part SPN in the local forest. The forest search is performed by using a global catalog or name suffix hints. If a match is found, the KDC will return a referral ticket to the client for the appropriate domain.
-
-If you disable or do not configure this policy setting, the KDC will not search the listed forests to resolve the SPN. If the KDC is unable to resolve the SPN because the name is not found, NTLM authentication might be used.
-
-To ensure consistent behavior, this policy setting must be supported and set identically on all domain controllers in the domain.
- Provide information about previous logons to client computers
- This policy setting controls whether the domain controller provides information about previous logons to client computers.
-
-If you enable this policy setting, the domain controller provides the information message about previous logons.
-
-For Windows Logon to leverage this feature, the "Display information about previous logons during user logon" policy setting located in the Windows Logon Options node under Windows Components also needs to be enabled.
-
-If you disable or do not configure this policy setting, the domain controller does not provide information about previous logons unless the "Display information about previous logons during user logon" policy setting is enabled.
-
-Note: Information about previous logons is provided only if the domain functional level is Windows Server 2008. In domains with a domain functional level of Windows Server 2003, Windows 2000 native, or Windows 2000 mixed, domain controllers cannot provide information about previous logons, and enabling this policy setting does not affect anything.
-
- KDC support for claims, compound authentication and Kerberos armoring
- This policy setting allows you to configure a domain controller to support claims and compound authentication for Dynamic Access Control and Kerberos armoring using Kerberos authentication.
-
-If you enable this policy setting, client computers that support claims and compound authentication for Dynamic Access Control and are Kerberos armor-aware will use this feature for Kerberos authentication messages. This policy should be applied to all domain controllers to ensure consistent application of this policy in the domain.
-
-If you disable or do not configure this policy setting, the domain controller does not support claims, compound authentication or armoring.
-
-If you configure the "Not supported" option, the domain controller does not support claims, compound authentication or armoring which is the default behavior for domain controllers running Windows Server 2008 R2 or earlier operating systems.
-
-Note: For the following options of this KDC policy to be effective, the Kerberos Group Policy "Kerberos client support for claims, compound authentication and Kerberos armoring" must be enabled on supported systems. If the Kerberos policy setting is not enabled, Kerberos authentication messages will not use these features.
-
-If you configure "Supported", the domain controller supports claims, compound authentication and Kerberos armoring. The domain controller advertises to Kerberos client computers that the domain is capable of claims and compound authentication for Dynamic Access Control and Kerberos armoring.
-
-Domain functional level requirements
-For the options "Always provide claims" and "Fail unarmored authentication requests", when the domain functional level is set to Windows Server 2008 R2 or earlier then domain controllers behave as if the "Supported" option is selected.
-
-When the domain functional level is set to Windows Server 2012 then the domain controller advertises to Kerberos client computers that the domain is capable of claims and compound authentication for Dynamic Access Control and Kerberos armoring, and:
- - If you set the "Always provide claims" option, always returns claims for accounts and supports the RFC behavior for advertising the flexible authentication secure tunneling (FAST).
- - If you set the "Fail unarmored authentication requests" option, rejects unarmored Kerberos messages.
-
-Warning: When "Fail unarmored authentication requests" is set, then client computers which do not support Kerberos armoring will fail to authenticate to the domain controller.
-
-To ensure this feature is effective, deploy enough domain controllers that support claims and compound authentication for Dynamic Access Control and are Kerberos armor-aware to handle the authentication requests. Insufficient number of domain controllers that support this policy result in authentication failures whenever Dynamic Access Control or Kerberos armoring is required (that is, the "Supported" option is enabled).
-
-Impact on domain controller performance when this policy setting is enabled:
- - Secure Kerberos domain capability discovery is required resulting in additional message exchanges.
- - Claims and compound authentication for Dynamic Access Control increases the size and complexity of the data in the message which results in more processing time and greater Kerberos service ticket size.
- - Kerberos armoring fully encrypts Kerberos messages and signs Kerberos errors which results in increased processing time, but does not change the service ticket size.
-
- Not supported
- Supported
- Always provide claims
- Fail unarmored authentication requests
- Warning for large Kerberos tickets
- This policy setting allows you to configure at what size Kerberos tickets will trigger the warning event issued during Kerberos authentication. The ticket size warnings are logged in the System log.
-
-If you enable this policy setting, you can set the threshold limit for Kerberos ticket which trigger the warning events. If set too high, then authentication failures might be occurring even though warning events are not being logged. If set too low, then there will be too many ticket warnings in the log to be useful for analysis. This value should be set to the same value as the Kerberos policy "Set maximum Kerberos SSPI context token buffer size" or the smallest MaxTokenSize used in your environment if you are not configuring using Group Policy.
-
-If you disable or do not configure this policy setting, the threshold value defaults to 12,000 bytes, which is the default Kerberos MaxTokenSize for Windows 7, Windows Server 2008 R2 and prior versions.
-
- Request compound authentication
- This policy setting allows you to configure a domain controller to request compound authentication.
-
-Note: For a domain controller to request compound authentication, the policy "KDC support for claims, compound authentication, and Kerberos armoring" must be configured and enabled.
-
-If you enable this policy setting, domain controllers will request compound authentication. The returned service ticket will contain compound authentication only when the account is explicitly configured. This policy should be applied to all domain controllers to ensure consistent application of this policy in the domain.
-
-If you disable or do not configure this policy setting, domain controllers will return service tickets that contain compound authentication any time the client sends a compound authentication request regardless of the account configuration.
-
- KDC support for PKInit Freshness Extension
- Support for PKInit Freshness Extension requires Windows Server 2016 domain functional level (DFL). If the domain controller’s domain is not at Windows Server 2016 DFL or higher this policy will not be applied.
-
-This policy setting allows you to configure a domain controller (DC) to support the PKInit Freshness Extension.
-
-If you enable this policy setting, the following options are supported:
-
-Supported: PKInit Freshness Extension is supported on request. Kerberos clients successfully authenticating with the PKInit Freshness Extension will get the fresh public key identity SID.
-
-Required: PKInit Freshness Extension is required for successful authentication. Kerberos clients which do not support the PKInit Freshness Extension will always fail when using public key credentials.
-
-If you disable or not configure this policy setting, then the DC will never offer the PKInit Freshness Extension and accept valid authentication requests without checking for freshness. Users will never receive the fresh public key identity SID.
-
- Disabled
- Supported
- Required
- Configure hash algorithms for certificate logon
- This policy setting controls hash or checksum algorithms used by the Kerberos client when performing certificate authentication.
-
-If you enable this policy, you will be able to configure one of four states for each algorithm:
-
-- “Default” sets the algorithm to the recommended state.
-
-- “Supported” enables usage of the algorithm. Enabling algorithms that have been disabled by default may reduce your security.
-
-- “Audited” enables usage of the algorithm and reports an event (ID 309) every time it is used. This state is intended to verify that the algorithm is not being used and can be safely disabled.
-
-- “Not Supported” disables usage of the algorithm. This state is intended for algorithms that are deemed to be insecure.
-
-If you disable or do not configure this policy, each algorithm will assume the “Default” state.
-More information about the hash and checksum algorithms supported by the Windows Kerberos client and their default states can be found at https://go.microsoft.com/fwlink/?linkid=2169037.
-
-Events generated by this configuration: 309, 310.
-
- Default
- Supported
- Audited
- Not Supported
-
-
-
- Mode:
-
-
-
-
-
- Syntax:
- Enter the list of forests to be searched when this policy is enabled.
- Use the Fully Qualified Domain Name (FQDN) naming format.
- Separate multiple search entries with a semi-colon ";".
- Details:
- The current forest need not be listed because Forest Search Order uses the global catalog first then searches in the order listed.
- You do not need to separately list all the domains in the forest.
- If a trusting forest is listed, all the domains in that forest will be searched.
- For best performance, list the forests in probability of success order.
-
-
- Claims, compound authentication for Dynamic Access Control and Kerberos armoring options:
-
-
- Ticket Size Threshold
-
-
- PKInit Freshness Extension options:
-
-
- SHA-1
- SHA-256
- SHA-384
- SHA-512
-
-
-
-
diff --git a/policy_templates/en-US/Kerberos.adml b/policy_templates/en-US/Kerberos.adml
deleted file mode 100644
index 7b33c7e..0000000
--- a/policy_templates/en-US/Kerberos.adml
+++ /dev/null
@@ -1,265 +0,0 @@
-
-
-
- Kerberos Settings
- Configuration settings for the Kerberos authentication protocol.
-
-
- Kerberos
- Use forest search order
- This policy setting defines the list of trusting forests that the Kerberos client searches when attempting to resolve two-part service principal names (SPNs).
-
-If you enable this policy setting, the Kerberos client searches the forests in this list, if it is unable to resolve a two-part SPN. If a match is found, the Kerberos client requests a referral ticket to the appropriate domain.
-
-If you disable or do not configure this policy setting, the Kerberos client does not search the listed forests to resolve the SPN. If the Kerberos client is unable to resolve the SPN because the name is not found, NTLM authentication might be used.
- Define host name-to-Kerberos realm mappings
- This policy setting allows you to specify which DNS host names and which DNS suffixes are mapped to a Kerberos realm.
-
-If you enable this policy setting, you can view and change the list of DNS host names and DNS suffixes mapped to a Kerberos realm as defined by Group Policy. To view the list of mappings, enable the policy setting and then click the Show button. To add a mapping, enable the policy setting, note the syntax, and then click Show. In the Show Contents dialog box in the Value Name column, type a realm name. In the Value column, type the list of DNS host names and DNS suffixes using the appropriate syntax format. To remove a mapping from the list, click the mapping entry to be removed, and then press the DELETE key. To edit a mapping, remove the current entry from the list and add a new one with different parameters.
-
-If you disable this policy setting, the host name-to-Kerberos realm mappings list defined by Group Policy is deleted.
-
-If you do not configure this policy setting, the system uses the host name-to-Kerberos realm mappings that are defined in the local registry, if they exist.
- Define interoperable Kerberos V5 realm settings
- This policy setting configures the Kerberos client so that it can authenticate with interoperable Kerberos V5 realms, as defined by this policy setting.
-
-If you enable this policy setting, you can view and change the list of interoperable Kerberos V5 realms and their settings. To view the list of interoperable Kerberos V5 realms, enable the policy setting and then click the Show button. To add an interoperable Kerberos V5 realm, enable the policy setting, note the syntax, and then click Show. In the Show Contents dialog box in the Value Name column, type the interoperable Kerberos V5 realm name. In the Value column, type the realm flags and host names of the host KDCs using the appropriate syntax format. To remove an interoperable Kerberos V5 realm Value Name or Value entry from the list, click the entry, and then press the DELETE key. To edit a mapping, remove the current entry from the list and add a new one with different parameters.
-
-If you disable this policy setting, the interoperable Kerberos V5 realm settings defined by Group Policy are deleted.
-
-If you do not configure this policy setting, the system uses the interoperable Kerberos V5 realm settings that are defined in the local registry, if they exist.
- Require strict KDC validation
- This policy setting controls the Kerberos client's behavior in validating the KDC certificate for smart card and system certificate logon.
-
-If you enable this policy setting, the Kerberos client requires that the KDC's X.509 certificate contains the KDC key purpose object identifier in the Extended Key Usage (EKU) extensions, and that the KDC's X.509 certificate contains a dNSName subjectAltName (SAN) extension that matches the DNS name of the domain. If the computer is joined to a domain, the Kerberos client requires that the KDC's X.509 certificate must be signed by a Certificate Authority (CA) in the NTAuth store. If the computer is not joined to a domain, the Kerberos client allows the root CA certificate on the smart card to be used in the path validation of the KDC's X.509 certificate.
-
-If you disable or do not configure this policy setting, the Kerberos client requires only that the KDC certificate contain the Server Authentication purpose object identifier in the EKU extensions which can be issued to any server.
-
- Require strict target SPN match on remote procedure calls
- This policy setting allows you to configure this server so that Kerberos can decrypt a ticket that contains this system-generated SPN. When an application attempts to make a remote procedure call (RPC) to this server with a NULL value for the service principal name (SPN), computers running Windows 7 or later attempt to use Kerberos by generating an SPN.
-
-If you enable this policy setting, only services running as LocalSystem or NetworkService are allowed to accept these connections. Services running as identities different from LocalSystem or NetworkService might fail to authenticate.
-
-If you disable or do not configure this policy setting, any service is allowed to accept incoming connections by using this system-generated SPN.
- Specify KDC proxy servers for Kerberos clients
- This policy setting configures the Kerberos client's mapping to KDC proxy servers for domains based on their DNS suffix names.
-
-If you enable this policy setting, the Kerberos client will use the KDC proxy server for a domain when a domain controller cannot be located based on the configured mappings. To map a KDC proxy server to a domain, enable the policy setting, click Show, and then map the KDC proxy server name(s) to the DNS name for the domain using the syntax described in the options pane. In the Show Contents dialog box in the Value Name column, type a DNS suffix name. In the Value column, type the list of proxy servers using the appropriate syntax format. To view the list of mappings, enable the policy setting and then click the Show button. To remove a mapping from the list, click the mapping entry to be removed, and then press the DELETE key. To edit a mapping, remove the current entry from the list and add a new one with different parameters.
-
-If you disable or do not configure this policy setting, the Kerberos client does not have KDC proxy servers settings defined by Group Policy.
-
- Disable revocation checking for the SSL certificate of KDC proxy servers
- This policy setting allows you to disable revocation check for the SSL certificate of the targeted KDC proxy server.
-
-If you enable this policy setting, revocation check for the SSL certificate of the KDC proxy server is ignored by the Kerberos client. This policy setting should only be used in troubleshooting KDC proxy connections.
-Warning: When revocation check is ignored, the server represented by the certificate is not guaranteed valid.
-
-If you disable or do not configure this policy setting, the Kerberos client enforces the revocation check for the SSL certificate. The connection to the KDC proxy server is not established if the revocation check fails.
-
- Fail authentication requests when Kerberos armoring is not available
- This policy setting controls whether a computer requires that Kerberos message exchanges be armored when communicating with a domain controller.
-
-Warning: When a domain does not support Kerberos armoring by enabling "Support Dynamic Access Control and Kerberos armoring", then all authentication for all its users will fail from computers with this policy setting enabled.
-
-If you enable this policy setting, the client computers in the domain enforce the use of Kerberos armoring in only authentication service (AS) and ticket-granting service (TGS) message exchanges with the domain controllers.
-
-Note: The Kerberos Group Policy "Kerberos client support for claims, compound authentication and Kerberos armoring" must also be enabled to support Kerberos armoring.
-
-If you disable or do not configure this policy setting, the client computers in the domain enforce the use of Kerberos armoring when possible as supported by the target domain.
-
- Support compound authentication
- This policy setting controls configuring the device's Active Directory account for compound authentication.
-
-Support for providing compound authentication which is used for access control will require enough domain controllers in the resource account domains to support the requests. The Domain Administrator must configure the policy "Support Dynamic Access Control and Kerberos armoring" on all the domain controllers to support this policy.
-
-If you enable this policy setting, the device's Active Directory account will be configured for compound authentication by the following options:
-
-Never: Compound authentication is never provided for this computer account.
-
-Automatic: Compound authentication is provided for this computer account when one or more applications are configured for Dynamic Access Control.
-
-Always: Compound authentication is always provided for this computer account.
-
-If you disable this policy setting, Never will be used.
-If you do not configure this policy setting, Automatic will be used.
-
- Never
- Automatic
- Always
-
- Set maximum Kerberos SSPI context token buffer size
- This policy setting allows you to set the value returned to applications which request the maximum size of the SSPI context token buffer size.
-
-The size of the context token buffer determines the maximum size of SSPI context tokens an application expects and allocates. Depending upon authentication request processing and group memberships, the buffer might be smaller than the actual size of the SSPI context token.
-
-If you enable this policy setting, the Kerberos client or server uses the configured value, or the locally allowed maximum value, whichever is smaller.
-
-If you disable or do not configure this policy setting, the Kerberos client or server uses the locally configured value or the default value.
-
-Note: This policy setting configures the existing MaxTokenSize registry value in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\Kerberos\Parameters, which was added in Windows XP and Windows Server 2003, with a default value of 12,000 bytes. Beginning with Windows 8 the default is 48,000 bytes. Due to HTTP's base64 encoding of authentication context tokens, it is not advised to set this value more than 48,000 bytes.
-
-
- Kerberos client support for claims, compound authentication and Kerberos armoring
- This policy setting controls whether a device will request claims and compound authentication for Dynamic Access Control and Kerberos armoring using Kerberos authentication with domains that support these features.
-If you enable this policy setting, the client computers will request claims, provide information required to create compounded authentication and armor Kerberos messages in domains which support claims and compound authentication for Dynamic Access Control and Kerberos armoring.
-
-If you disable or do not configure this policy setting, the client devices will not request claims, provide information required to create compounded authentication and armor Kerberos messages. Services hosted on the device will not be able to retrieve claims for clients using Kerberos protocol transition.
-
- Always send compound authentication first
- This policy setting controls whether a device always sends a compound authentication request when the resource domain requests compound identity.
-
-Note: For a domain controller to request compound authentication, the policies "KDC support for claims, compound authentication, and Kerberos armoring" and "Request compound authentication" must be configured and enabled in the resource account domain.
-
-If you enable this policy setting and the resource domain requests compound authentication, devices that support compound authentication always send a compound authentication request.
-
-If you disable or do not configure this policy setting and the resource domain requests compound authentication, devices will send a non-compounded authentication request first then a compound authentication request when the service requests compound authentication.
-
- Support device authentication using certificate
- Support for device authentication using certificate will require connectivity to a DC in the device account domain which supports certificate authentication for computer accounts.
-
-This policy setting allows you to set support for Kerberos to attempt authentication using the certificate for the device to the domain.
-
-If you enable this policy setting, the devices credentials will be selected based on the following options:
-
-Automatic: Device will attempt to authenticate using its certificate. If the DC does not support computer account authentication using certificates then authentication with password will be attempted.
-
-Force: Device will always authenticate using its certificate. If a DC cannot be found which support computer account authentication using certificates then authentication will fail.
-
-If you disable this policy setting, certificates will never be used.
-If you do not configure this policy setting, Automatic will be used.
-
- Automatic
- Force
- Allow retrieving the Azure AD Kerberos Ticket Granting Ticket during logon
- This policy setting allows retrieving the Azure AD Kerberos Ticket Granting Ticket during logon.
-
-If you disable or do not configure this policy setting, the Azure AD Kerberos Ticket Granting Ticket is not retrieved during logon.
-
-If you enable this policy setting, the Azure AD Kerberos Ticket Granting Ticket is retrieved during logon.
- Configure hash algorithms for certificate logon
- This policy setting controls hash or checksum algorithms used by the Kerberos client when performing certificate authentication.
-
-If you enable this policy, you will be able to configure one of four states for each algorithm:
-
-- “Default” sets the algorithm to the recommended state.
-
-- “Supported” enables usage of the algorithm. Enabling algorithms that have been disabled by default may reduce your security.
-
-- “Audited” enables usage of the algorithm and reports an event (ID 206) every time it is used. This state is intended to verify that the algorithm is not being used and can be safely disabled.
-
-- “Not Supported” disables usage of the algorithm. This state is intended for algorithms that are deemed to be insecure.
-
-If you disable or do not configure this policy, each algorithm will assume the “Default” state.
-More information about the hash and checksum algorithms supported by the Windows Kerberos client and their default states can be found at https://go.microsoft.com/fwlink/?linkid=2169037.
-
-Events generated by this configuration: 205, 206, 207, 208.
-
- Default
- Supported
- Audited
- Not Supported
-
-
-
- Define host name-to-realm mappings:
-
- Syntax:
- Enter the Kerberos realm name as the Value Name.
- Enter the host names and DNS suffixes, that you want to
- map to the Kerberos realm, as the Value. To add multiple
- names, separate entries with ";".
-
- Note: To specify a DNS suffix prepend the entry with a '.' period.
- For a host name entry do not specify a leading '.' period.
-
- Example:
- Value Name: MICROSOFT.COM
- Value: .microsoft.com; .ms.com; computer1.fabrikam.com;
-
- In the example above. All principals with either the DNS suffix
- of *.microsoft.com or *.ms.com will be mapped to the
- MICROSOFT.COM Kerberos realm. In addition the host name
- computer1.fabrikam.com will also be mapped to the
- MICROSOFT.COM Kerberos realm.
-
-
- Define interoperable Kerberos V5 realm settings:
-
- Syntax:
- Enter the interoperable Kerberos V5 realm name as the Value Name.
- Enter the realm flags and the host names of the KDCs as
- the Value. Enclose the realm flags with the following
- tags <f> </f>. Enclose the list of KDCs with the tags <k> </k>
- To add multiple KDC names, separate entries with
- a semi-colon ";".
-
- Example:
- Value Name: TEST.COM
- Value: <f>0x00000004</f><k>kdc1.test.com; kdc2.test.com</k>
-
- Another Example:
- Value Name: REALM.FABRIKAM.COM
- Value: <f>0x0000000E</f>
-
-
- Mode:
-
-
-
-
-
- Syntax:
- Enter the list of forests to be searched when this policy is enabled.
- Use the Fully Qualified Domain Name (FQDN) naming format.
- Separate multiple search entries with a semi-colon ";".
- Details:
- The current forest need not be listed because Forest Search Order uses the global catalog first then searches in the order listed.
- You do not need to separately list all the domains in the forest.
- If a trusting forest is listed, all the domains in that forest will be searched.
- For best performance, list the forests in probability of success order.
-
-
- Define KDC proxy servers settings:
-
- Syntax:
-
- Enter the DNS suffix name as the Value Name.
- DNS suffix name allows three formats with decreasing preference order:
- Full Match: host.contoso.com
- Suffix Match: .contoso.com
- Default Match: *
-
- Enter the proxy server names as the Value.
- The proxy server names must be enclosed with tags <https />
- To add multiple proxy server names, separate entries with a space or comma ","
-
- Example:
- Value Name: .contoso.com
- Value: <https proxy1.contoso.com proxy2.contoso.com />
-
- Another Example:
- Value Name: *
- Value: <https proxy.contoso.com />
-
-
-
-
- Support authorization with client device information:
-
-
- Maximum size
-
-
-
-
- Device authentication behavior using certificate:
-
-
- SHA-1
- SHA-256
- SHA-384
- SHA-512
-
-
-
-
diff --git a/policy_templates/en-US/LAPS.adml b/policy_templates/en-US/LAPS.adml
deleted file mode 100644
index 65cf191..0000000
--- a/policy_templates/en-US/LAPS.adml
+++ /dev/null
@@ -1,188 +0,0 @@
-
-
-
-
-
-
-
- LAPS
- Configure password backup directory
- Use this setting to configure which directory the local admin account password is backed up to.
-
-The allowable settings are:
-
-0=Disabled (password will not be backed up)
-
-1=Backup the password to Azure Active Directory
-
-2=Backup the password to Active Directory
-
-If not specified, this setting will default to 0 (Disabled).
-
-If this setting is configured to 1, and the managed device is not joined to Azure Active Directory, the local administrator password will not be managed.
-
-If this setting is configured to 2, and the managed device is not joined to Active Directory, the local administrator password will not be managed.
-
-If this setting is disabled or not configured, the local administrator password is not managed.
-
-See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.
-
- Disabled
- Azure Active Directory
- Active Directory
- Password Settings
- Configures password parameters
-
-Password complexity: which characters are used when generating a new password
- Default: Large letters + small letters + numbers + special characters
-
-Password length
- Minimum: 8 characters
- Maximum: 64 characters
- Default: 14 characters
-
-Password age in days
- Minimum: 1 day (7 days when backup directory is configured to be Azure AD)
- Maximum: 365 days
- Default: 30 days
-
-See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.
-
- Large letters
- Large letters + small letters
- Large letters + small letters + numbers
- Large letters + small letters + numbers + specials
- Name of administrator account to manage
- This policy setting specifies a custom Administrator account name to manage the password for.
-
-If this policy setting is enabled, LAPS will manage the password for a local account with this name.
-
-If this policy setting is disabled or not configured, LAPS will manage the password for the well known Administrator account.
-
-DO NOT enable this policy setting to manage the built-in administrator account. The built-in administrator account is auto-detected by well-known SID and does not depend on the account name.
-
-See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.
-
- Do not allow password expiration time longer than required by policy
- If this setting is enabled or not configured, planned password expiration longer than the password age dictated by the "Password Settings" policy is NOT allowed. When such expiration is detected, the password is changed immediately and password expiration is set according to policy.
-
-If this setting is disabled, password expiration time may be longer than required by "Password Settings" policy.
-
-See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.
-
- Enable password encryption
- When you enable this setting, the managed password is encrypted before being sent to Active Directory.
-
-Enabling this setting has no effect unless 1) the password has been configured to be backed up to Active Directory and 2) the Active Directory domain functional level is at Windows Server 2016 or above.
-
-If this setting is enabled, and the domain functional level is at or above Windows Server 2016, the managed account password is encrypted.
-
-If this setting is enabled, and the domain functional level is less than Windows Server 2016, the managed account password is not backed up to the directory.
-
-If this setting is disabled, the managed account password is not encrypted.
-
-This setting will default to enabled if not configured.
-
-See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.
-
- Configure authorized password decryptors
- Configure this setting to control the specific user or group who is authorized to decrypt encrypted passwords.
-
-Configuring this setting has no effect unless password encryption has been enabled.
-
-If this setting is enabled, encrypted passwords will be decryptable by the specified group.
-
-If this setting is disabled or not configured, encrypted passwords will be decryptable by the Domain Admins group.
-
-This setting must be configured with either a SID in string format ("S-1-5-21-2127521184-1604012920-1887927527-35197") or the name of a group or user in "domain\(group or user)" format. The specified user or group must be resolvable by the managed device, otherwise passwords will not be backed up.
-
-See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.
-
- Configure size of encrypted password history
- Use this setting to configure how many previous encrypted passwords will be stored in Active Directory.
-
-Configuring this setting has no effect unless 1) the password has been configured to be backed up to Active Directory and 2) password encryption has been enabled.
-
-If this setting is enabled, the specified number of older passwords will be stored in Active Directory.
-
-If this setting is disabled or not configured, zero older passwords will be stored in Active Directory.
-
-This setting has a minimum allowed value of 0 passwords.
-
-This setting has a maximum allowed value of 12 passwords.
-
-See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.
-
- Enable password backup for DSRM accounts
- When you enable this setting, the DSRM administrator account password will be managed and backed up to Active Directory.
-
-Enabling this setting has no effect unless the managed device is a domain controller and password encryption is also enabled.
-
-If this setting is enabled, the password for the DSRM administrator account on the domain controller will be backed up to Active Directory.
-
-If this setting is disabled or not configured, the password for the DSRM administrator account on the domain controller will not be backed up to Active Directory.
-
-See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.
-
- Post-authentication actions
- This policy configures post-authentication actions which will be executed after detecting an authentication by the managed account.
-
-Grace period: specifies the amount of time (in hours) to wait after an authentication before executing the specified post-authentication actions.
-
-If this setting is enabled and greater than zero, the specified post-authentication actions will be executed upon expiry of the grace period.
-
-If this setting is disabled or not configured, the specified post-authentication actions will be executed after a default 24 hour grace period.
-
-If this setting is equal to zero, no post-authentication actions will be executed.
-
-Actions: specifies the actions to take upon expiry of the grace period.
-
-Reset password: upon expiry of the grace period, the managed account password will be reset.
-
-Reset the password and logoff the managed account: upon expiry of the grace period, the managed account password will be reset and any interactive logon sessions using the managed account will terminated.
-
-(NOTE: after any interactive logon sessions are terminated there may still be other authenticated sessions in use by the managed account. The only robust way to ensure that the previous password is longer in use is to reboot the device.)
-
-Reset the password and reboot: upon expiry of the grace period, the managed account password will be reset and the managed device will be immediately rebooted.
-
-If this setting is disabled or not configured, post-authentication actions will default to "Reset the password and logoff the managed account".
-
-Note: the DSRM account on domain controllers cannot be configured for post-authentication actions. This policy has no effect on domain controllers and will be ignored even if configured for a DC.
-
-See https://go.microsoft.com/fwlink/?linkid=2188435 for more information.
-
- Disabled - take no actions
- Reset the password
- Reset the password and logoff the managed account
- Reset the password and reboot the device
- At least Microsoft Windows 10 or later
-
-
-
- Backup directory
-
-
- Password Complexity
- Password Length
- Password Age (Days)
-
-
-
-
-
-
-
-
-
-
-
-
- Encrypted password history size
-
-
- Grace period (hours):
- Actions:
-
-
-
-
diff --git a/policy_templates/en-US/LanmanServer.adml b/policy_templates/en-US/LanmanServer.adml
deleted file mode 100644
index a112160..0000000
--- a/policy_templates/en-US/LanmanServer.adml
+++ /dev/null
@@ -1,142 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Lanman Server
- Allow hash publication only for shared folders on which BranchCache is enabled
- Disallow hash publication on all shared folders
- Allow hash publication for all shared folders
- Hash Publication for BranchCache
- This policy setting specifies whether a hash generation service generates hashes, also called content information, for data that is stored in shared folders. This policy setting must be applied to server computers that have the File Services role and both the File Server and the BranchCache for Network Files role services installed.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, hash publication settings are not applied to file servers. In the circumstance where file servers are domain members but you do not want to enable BranchCache on all file servers, you can specify Not Configured for this domain Group Policy setting, and then configure local machine policy to enable BranchCache on individual file servers. Because the domain Group Policy setting is not configured, it will not over-write the enabled setting that you use on individual servers where you want to enable BranchCache.
-
-- Enabled. With this selection, hash publication is turned on for all file servers where Group Policy is applied. For example, if Hash Publication for BranchCache is enabled in domain Group Policy, hash publication is turned on for all domain member file servers to which the policy is applied. The file servers are then able to create content information for all content that is stored in BranchCache-enabled file shares.
-
-- Disabled. With this selection, hash publication is turned off for all file servers where Group Policy is applied.
-
-In circumstances where this policy setting is enabled, you can also select the following configuration options:
-
-- Allow hash publication for all shared folders. With this option, BranchCache generates content information for all content in all shares on the file server.
-
-- Allow hash publication only for shared folders on which BranchCache is enabled. With this option, content information is generated only for shared folders on which BranchCache is enabled. If you use this setting, you must enable BranchCache for individual shares in Share and Storage Management on the file server.
-
-- Disallow hash publication on all shared folders. With this option, BranchCache does not generate content information for any shares on the computer and does not send content information to client computers that request content.
-
- Supports V1 hash version only
- Supports V2 hash version only
- Supports V1 as well as V2 versions
- Hash Version support for BranchCache
- This policy setting specifies whether the BranchCache hash generation service supports version 1 (V1) hashes, version 2 (V2) hashes, or both V1 and V2 hashes. Hashes, also called content information, are created based on the data in shared folders where BranchCache is enabled.
-
-If you specify only one version that is supported, content information for that version is the only type that is generated by BranchCache, and it is the only type of content information that can be retrieved by client computers. For example, if you enable support for V1 hashes, BranchCache generates only V1 hashes and client computers can retrieve only V1 hashes.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, BranchCache settings are not applied to client computers by this policy setting. In this circumstance, which is the default, both V1 and V2 hash generation and retrieval are supported.
-
-- Enabled. With this selection, the policy setting is applied and the hash version(s) that are specified in "Hash version supported" are generated and retrieved.
-
-- Disabled. With this selection, both V1 and V2 hash generation and retrieval are supported.
-
-In circumstances where this setting is enabled, you can also select and configure the following option:
-
-Hash version supported:
-
-- To support V1 content information only, configure "Hash version supported" with the value of 1.
-
-- To support V2 content information only, configure "Hash version supported" with the value of 2.
-
-- To support both V1 and V2 content information, configure "Hash version supported" with the value of 3.
- Cipher suite order
- This policy setting determines the cipher suites used by the SMB server.
-
-If you enable this policy setting, cipher suites are prioritized in the order specified.
-
-If you enable this policy setting and do not specify at least one supported cipher suite, or if you disable or do not configure this policy setting, the default cipher suite order is used.
-
-SMB 3.11 cipher suites:
-
-AES_128_GCM
-AES_128_CCM
-AES_256_GCM
-AES_256_CCM
-
-SMB 3.0 and 3.02 cipher suites:
-
-AES_128_CCM
-
-How to modify this setting:
-
-Arrange the desired cipher suites in the edit box, one cipher suite per line, in order from most to least preferred, with the most preferred cipher suite at the top. Remove any cipher suites you don't want to use.
-
-Note: When configuring this security setting, changes will not take effect until you restart Windows.
- Honor cipher suite order
- This policy setting determines how the SMB server selects a cipher suite when negotiating a new connection with an SMB client.
-
-If you enable this policy setting, the SMB server will select the cipher suite it most prefers from the SMB client's cipher suites, ignoring the client's cipher suite preferences.
-
-If you disable or do not configure this policy setting, the SMB server will select the cipher suite the SMB client most prefers from the server's cipher suites.
-
-Note: When configuring this security setting, changes will not take effect until you restart Windows.
- Honor cipher suite order
- This policy setting determines how the SMB server selects a cipher suite when negotiating a new connection with an SMB client.
-
-If you enable this policy setting, the SMB server will select the cipher suite it most prefers from the list of client-supported cipher suites, ignoring the client's preferences.
-
-If you disable or do not configure this policy setting, the SMB server will select the cipher suite the client most prefers from the list of server-supported cipher suites.
-
-Note: When configuring this security setting, changes will not take effect until you restart Windows.
- At least Windows Server 2022, Windows 11
- Request traffic compression for all shares
- This policy controls whether the SMB server requests SMB client to use traffic compression for all SMB shares.
-
-If you enable this policy setting, the SMB server will by default request the SMB client to compress traffic when SMB compression is enabled. See notes below.
-
-If you disable or do not configure this policy setting, the SMB server will not by default request the SMB client to compress traffic. However traffic compression may be requested by other means. See notes below.
-
-Note: If this policy is disabled, traffic compression may be requested by server-side per-share properties or by the SMB Client. If this is undesired, and one wishes to completely disable compression, configure the accompanying 'Disable SMB compression' policy instead.
-
-Note: Traffic compression can only be used when both the SMB client and SMB server support and enable traffic compression.
-
- Disable SMB compression
- This policy controls whether the SMB server will disable (completely prevent) traffic compression.
-
-If you enable this policy setting, the SMB server will never compress data, irrespective of other policies (such as the 'Use SMB compression by default' policy or per-share property).
-
-If you disable or do not configure this policy setting, the SMB server may compress traffic (depending on a combination of other policies and conditions).
-
-
-
-
- Values:
- 0 = Allow hash publication only for shared folders on which BranchCache is enabled
- 1 = Disallow hash publication on all shared folders
- 2 = Allow hash publication for all shared folders
- Hash publication actions:
-
-
-
- Values:
- 1 = Support V1 hashes
- 2 = Support V2 hashes
- 3 = Support V1 and V2 hashes
- Hash version supported:
-
-
-
- Cipher suites:
-
-
-
-
-
diff --git a/policy_templates/en-US/LanmanWorkstation.adml b/policy_templates/en-US/LanmanWorkstation.adml
deleted file mode 100644
index 3a18803..0000000
--- a/policy_templates/en-US/LanmanWorkstation.adml
+++ /dev/null
@@ -1,88 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Lanman Workstation
- Cipher suite order
- This policy setting determines the cipher suites used by the SMB client.
-
-If you enable this policy setting, cipher suites are prioritized in the order specified.
-
-If you enable this policy setting and do not specify at least one supported cipher suite, or if you disable or do not configure this policy setting, the default cipher suite order is used.
-
-SMB 3.11 cipher suites:
-
-AES_128_GCM
-AES_128_CCM
-AES_256_GCM
-AES_256_CCM
-
-SMB 3.0 and 3.02 cipher suites:
-
-AES_128_CCM
-
-How to modify this setting:
-
-Arrange the desired cipher suites in the edit box, one cipher suite per line, in order from most to least preferred, with the most preferred cipher suite at the top. Remove any cipher suites you don't want to use.
-
-Note: When configuring this security setting, changes will not take effect until you restart Windows.
- Enable insecure guest logons
- This policy setting determines if the SMB client will allow insecure guest logons to an SMB server.
-
-If you enable this policy setting or if you do not configure this policy setting, the SMB client will allow insecure guest logons.
-
-If you disable this policy setting, the SMB client will reject insecure guest logons.
-
-Insecure guest logons are used by file servers to allow unauthenticated access to shared folders. While uncommon in an enterprise environment, insecure guest logons are frequently used by consumer Network Attached Storage (NAS) appliances acting as file servers. Windows file servers require authentication and do not use insecure guest logons by default. Since insecure guest logons are unauthenticated, important security features such as SMB Signing and SMB Encryption are disabled. As a result, clients that allow insecure guest logons are vulnerable to a variety of man-in-the-middle attacks that can result in data loss, data corruption, and exposure to malware. Additionally, any data written to a file server using an insecure guest logon is potentially accessible to anyone on the network. Microsoft recommends disabling insecure guest logons and configuring file servers to require authenticated access."
-
-
- Offline Files Availability on Continuous Availability Shares
-
- This policy setting determines the behavior of Offline Files on clients connecting to an SMB share where the Continuous Availability (CA) flag is enabled.
-
- If you enable this policy setting, the "Always Available offline" option will appear in the File Explorer menu on a Windows computer when connecting to a CA-enabled share. Pinning of files on CA-enabled shares using client-side caching will also be possible.
-
- If you disable or do not configure this policy setting, Windows will prevent use of Offline Files with CA-enabled shares.
-
- Note: Microsoft does not recommend enabling this group policy. Use of CA with Offline Files will lead to very long transition times between the online and offline states.
-
-
- Handle Caching on Continuous Availability Shares
-
- This policy setting determines the behavior of SMB handle caching for clients connecting to an SMB share where the Continuous Availability (CA) flag is enabled.
-
- If you enable this policy setting, the SMB client will allow cached handles to files on CA shares. This may lead to better performance when repeatedly accessing a large number of unstructured data files on CA shares running in Microsoft Azure Files.
-
- If you disable or do not configure this policy setting, Windows will prevent use of cached handles to files opened through CA shares.
-
- Note: This policy has no effect when connecting Scale-out File Server shares provided by a Windows Server. Microsoft does not recommend enabling this policy for clients that routinely connect to files hosted on a Windows Failover Cluster with the File Server for General Use role, as it can lead to adverse failover times and increased memory and CPU usage.
-
- At least Windows Server 2022, Windows 11
- Use SMB compression by default
- This policy controls whether the SMB client uses traffic compression by default.
-
-If you enable this policy setting, the SMB client will attempt to compress traffic by default when SMB compression is enabled.
-
-If you disable or do not configure this policy setting, the SMB client will not by default attempt to compress traffic. However traffic compression may be requested by other means. See notes below.
-
-Note: This policy is combined with per-share and per-file handle properties, through which traffic compression may be requested. As well, the SMB server must support and enable compression. For example, should this policy be disabled (or not configured), the SMB client may still perform compression if an SMB server share has compression requested. If this is undesired, and one wishes to completely disable compression, configure the accompanying 'Disable SMB compression' policy instead.
-
- Disable SMB compression
- This policy controls whether the SMB client will disable (completely prevent) traffic compression.
-
-If you enable this policy setting, the SMB client will never compress data, irrespective of other policies (such as the 'Use SMB compression by default' policy or per-share property).
-
-If you disable or do not configure this policy setting, the SMB client may compress traffic (depending on a combination of other policies and conditions).
-
-
-
-
- Cipher suites:
-
-
-
-
-
diff --git a/policy_templates/en-US/LeakDiagnostic.adml b/policy_templates/en-US/LeakDiagnostic.adml
deleted file mode 100644
index 1f07f2e..0000000
--- a/policy_templates/en-US/LeakDiagnostic.adml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Windows Memory Leak Diagnosis
- Configure Scenario Execution Level
- This policy setting determines whether Diagnostic Policy Service (DPS) diagnoses memory leak problems.
-
-If you enable or do not configure this policy setting, the DPS enables Windows Memory Leak Diagnosis by default.
-
-If you disable this policy setting, the DPS is not able to diagnose memory leak problems.
-
-This policy setting takes effect only under the following conditions:
--- If the diagnostics-wide scenario execution policy is not configured.
--- When the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios are not executed.
-
-Note: The DPS can be configured with the Services snap-in to the Microsoft Management Console.
-
-No operating system restart or service restart is required for this policy to take effect. Changes take effect immediately.
-
-
-
diff --git a/policy_templates/en-US/LinkLayerTopologyDiscovery.adml b/policy_templates/en-US/LinkLayerTopologyDiscovery.adml
deleted file mode 100644
index 2aa1e25..0000000
--- a/policy_templates/en-US/LinkLayerTopologyDiscovery.adml
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Link-Layer Topology Discovery
- Configures all Link-Layer Topology Discovery components.
- Turn on Mapper I/O (LLTDIO) driver
- This policy setting changes the operational behavior of the Mapper I/O network protocol driver.
-
-LLTDIO allows a computer to discover the topology of a network it's connected to. It also allows a computer to initiate Quality-of-Service requests such as bandwidth estimation and network health analysis.
-
-If you enable this policy setting, additional options are available to fine-tune your selection. You may choose the "Allow operation while in domain" option to allow LLTDIO to operate on a network interface that's connected to a managed network. On the other hand, if a network interface is connected to an unmanaged network, you may choose the "Allow operation while in public network" and "Prohibit operation while in private network" options instead.
-
-If you disable or do not configure this policy setting, the default behavior of LLTDIO will apply.
- Turn on Responder (RSPNDR) driver
- This policy setting changes the operational behavior of the Responder network protocol driver.
-
-The Responder allows a computer to participate in Link Layer Topology Discovery requests so that it can be discovered and located on the network. It also allows a computer to participate in Quality-of-Service activities such as bandwidth estimation and network health analysis.
-
-If you enable this policy setting, additional options are available to fine-tune your selection. You may choose the "Allow operation while in domain" option to allow the Responder to operate on a network interface that's connected to a managed network. On the other hand, if a network interface is connected to an unmanaged network, you may choose the "Allow operation while in public network" and "Prohibit operation while in private network" options instead.
-
-If you disable or do not configure this policy setting, the default behavior for the Responder will apply.
-
-
-
- Allow operation while in domain
- Allow operation while in public network
- Prohibit operation while in private network
-
-
- Allow operation while in domain
- Allow operation while in public network
- Prohibit operation while in private network
-
-
-
-
diff --git a/policy_templates/en-US/LocalSecurityAuthority.adml b/policy_templates/en-US/LocalSecurityAuthority.adml
deleted file mode 100644
index 3e3899b..0000000
--- a/policy_templates/en-US/LocalSecurityAuthority.adml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- Local Security Authority Settings
- Settings for the Local Security Authority
-
-
- Local Security Authority
-
- Allow Custom SSPs and APs to be loaded into LSASS
- This policy controls the configuration under which LSASS loads custom SSPs and APs.
-
-If you enable this setting or do not configure it, LSA allows custom SSPs and APs to be loaded.
-
-If you disable this setting, LSA does not load custom SSPs and APs.
-
- Configures LSASS to run as a protected process
- This policy controls the configuration under which LSASS is run.
-
-If you do not configure this policy and there is no current setting in the registry, LSA will run as protected process for clean installed, HVCI capable, client SKUs that are domain or cloud domain joined devices. This configuration is not UEFI locked. This can be overridden if the policy is configured.
-
-If you configure and set this policy setting to "Disabled", LSA will not run as a protected process.
-
-If you configure and set this policy setting to "EnabledWithUEFILock," LSA will run as a protected process and this configuration is UEFI locked.
-
-If you configure and set this policy setting to "EnabledWithoutUEFILock", LSA will run as a protected process and this configuration is not UEFI locked.
-
- Disabled
- Enabled with UEFI Lock
- Enabled without UEFI Lock
-
-
-
-
- Configure LSA to run as a protected process
-
-
-
-
diff --git a/policy_templates/en-US/LocationProviderAdm.adml b/policy_templates/en-US/LocationProviderAdm.adml
deleted file mode 100644
index d04fcd2..0000000
--- a/policy_templates/en-US/LocationProviderAdm.adml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off Windows Location Provider
-
- This policy setting turns off the Windows Location Provider feature for this computer.
-
- If you enable this policy setting, the Windows Location Provider feature will be turned off, and all programs on this computer will not be able to use the Windows Location Provider feature.
-
- If you disable or do not configure this policy setting, all programs on this computer can use the Windows Location Provider feature.
- Windows Location Provider
-
-
-
diff --git a/policy_templates/en-US/Logon.adml b/policy_templates/en-US/Logon.adml
deleted file mode 100644
index 7216b08..0000000
--- a/policy_templates/en-US/Logon.adml
+++ /dev/null
@@ -1,180 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Always use custom logon background
- This policy setting ignores Windows Logon Background.
-
-This policy setting may be used to make Windows give preference to a custom logon background.
-
-If you enable this policy setting, the logon screen always attempts to load a custom background instead of the Windows-branded logon background.
-
-If you disable or do not configure this policy setting, Windows uses the default Windows logon background or custom background.
- Do not process the legacy run list
- This policy setting ignores the customized run list.
-
-You can create a customized list of additional programs and documents that the system starts automatically when it runs on Windows Vista, Windows XP Professional, and Windows 2000 Professional. These programs are added to the standard run list of programs and services that the system starts.
-
-If you enable this policy setting, the system ignores the run list for Windows Vista, Windows XP Professional, and Windows 2000 Professional.
-
-If you disable or do not configure this policy setting, Windows Vista adds any customized run list configured to its run list.
-
-This policy setting appears in the Computer Configuration and User Configuration folders. If both policy settings are configured, the policy setting in Computer Configuration takes precedence over the policy setting in User Configuration.
-
-Note: To create a customized run list by using a policy setting, use the ""Run these applications at startup"" policy setting.
-
-Also, see the ""Do not process the run once list"" policy setting.
-
- Do not display network selection UI
- This policy setting allows you to control whether anyone can interact with available networks UI on the logon screen.
-
-If you enable this policy setting, the PC's network connectivity state cannot be changed without signing into Windows.
-
-If you disable or don't configure this policy setting, any user can disconnect the PC from the network or can connect the PC to other available networks without signing into Windows.
-
- Do not process the run once list
- This policy setting ignores customized run-once lists.
-
-You can create a customized list of additional programs and documents that are started automatically the next time the system starts (but not thereafter). These programs are added to the standard list of programs and services that the system starts.
-
-If you enable this policy setting, the system ignores the run-once list.
-
-If you disable or do not configure this policy setting, the system runs the programs in the run-once list.
-
-This policy setting appears in the Computer Configuration and User Configuration folders. If both policy settings are configured, the policy setting in Computer Configuration takes precedence over the policy setting in User Configuration.
-
-Note: Customized run-once lists are stored in the registry in HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce.
-
-Also, see the ""Do not process the legacy run list"" policy setting.
- Remove Boot / Shutdown / Logon / Logoff status messages
- This policy setting suppresses system status messages.
-
-If you enable this setting, the system does not display a message reminding users to wait while their system starts or shuts down, or while users log on or off.
-
-If you disable or do not configure this policy setting, the system displays the message reminding users to wait while their system starts or shuts down, or while users log on or off.
- Logon
- Always use classic logon
- This policy is not available in this version of Windows.
- Do not display the Getting Started welcome screen at logon
- This policy setting hides the welcome screen that is displayed on Windows 2000 Professional each time the user logs on.
-
-If you enable this policy setting, the welcome screen is hidden from the user logging on to a computer where this policy is applied.
-
-Users can still display the welcome screen by selecting it on the Start menu or by typing ""Welcome"" in the Run dialog box.
-
-If you disable or do not configure this policy, the welcome screen is displayed each time a user logs on to the computer.
-
-This setting applies only to Windows 2000 Professional. It does not affect the ""Configure Your Server on a Windows 2000 Server"" screen on Windows 2000 Server.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Tip: To display the welcome screen, click Start, point to Programs, point to Accessories, point to System Tools, and then click ""Getting Started."" To suppress the welcome screen without specifying a setting, clear the ""Show this screen at startup"" check box on the welcome screen.
- Run these programs at user logon
- This policy setting specifies additional programs or documents that Windows starts automatically when a user logs on to the system.
-
-If you enable this policy setting, you can specify which programs can run at the time the user logs on to this computer that has this policy applied.
-
-To specify values for this policy setting, click Show. In the Show Contents dialog box in the Value column, type the name of the executable program (.exe) file or document file. To specify another name, press ENTER, and type the name. Unless the file is located in the %Systemroot% directory, you must specify the fully qualified path to the file.
-
-If you disable or do not configure this policy setting, the user will have to start the appropriate programs after logon.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the system starts the programs specified in the Computer Configuration setting just before it starts the programs specified in the User Configuration setting.
-
-Also, see the ""Do not process the legacy run list"" and the ""Do not process the run once list"" settings.
- Always wait for the network at computer startup and logon
- This policy setting determines whether Group Policy processing is synchronous (that is, whether computers wait for the network to be fully initialized during computer startup and user logon). By default, on client computers, Group Policy processing is not synchronous; client computers typically do not wait for the network to be fully initialized at startup and logon. Existing users are logged on using cached credentials, which results in shorter logon times. Group Policy is applied in the background after the network becomes available.
-
-Note that because this is a background refresh, extensions such as Software Installation and Folder Redirection take two logons to apply changes. To be able to operate safely, these extensions require that no users be logged on. Therefore, they must be processed in the foreground before users are actively using the computer. In addition, changes that are made to the user object, such as adding a roaming profile path, home directory, or user object logon script, may take up to two logons to be detected.
-
-If a user with a roaming profile, home directory, or user object logon script logs on to a computer, computers always wait for the network to be initialized before logging the user on. If a user has never logged on to this computer before, computers always wait for the network to be initialized.
-
-If you enable this policy setting, computers wait for the network to be fully initialized before users are logged on. Group Policy is applied in the foreground, synchronously.
-
-On servers running Windows Server 2008 or later, this policy setting is ignored during Group Policy processing at computer startup and Group Policy processing will be synchronous (these servers wait for the network to be initialized during computer startup).
-
-If the server is configured as follows, this policy setting takes effect during Group Policy processing at user logon:
-• The server is configured as a terminal server (that is, the Terminal Server role service is installed and configured on the server); and
-• The “Allow asynchronous user Group Policy processing when logging on through Terminal Services” policy setting is enabled. This policy setting is located under Computer Configuration\Policies\Administrative templates\System\Group Policy\.
-
-If this configuration is not implemented on the server, this policy setting is ignored. In this case, Group Policy processing at user logon is synchronous (these servers wait for the network to be initialized during user logon).
-
-If you disable or do not configure this policy setting and users log on to a client computer or a server running Windows Server 2008 or later and that is configured as described earlier, the computer typically does not wait for the network to be fully initialized. In this case, users are logged on with cached credentials. Group Policy is applied asynchronously in the background.
-
-Notes:
--If you want to guarantee the application of Folder Redirection, Software Installation, or roaming user profile settings in just one logon, enable this policy setting to ensure that Windows waits for the network to be available before applying policy.
--If Folder Redirection policy will apply during the next logon, security policies will be applied asynchronously during the next update cycle, if network connectivity is available.
- Display highly detailed status messages
- This policy setting directs the system to display highly detailed status messages.
-
-This policy setting is designed for advanced users who require this information.
-
-If you enable this policy setting, the system displays status messages that reflect each step in the process of starting, shutting down, logging on, or logging off the system.
-
-If you disable or do not configure this policy setting, only the default status messages are displayed to the user during these processes.
-
-Note: This policy setting is ignored if the ""Remove Boot/Shutdown/Logon/Logoff status messages"" policy setting is enabled.
- Hide entry points for Fast User Switching
- This policy setting allows you to hide the Switch User interface in the Logon UI, the Start menu and the Task Manager.
-
-If you enable this policy setting, the Switch User interface is hidden from the user who is attempting to log on or is logged on to the computer that has this policy applied.
-
-The locations that Switch User interface appear are in the Logon UI, the Start menu and the Task Manager.
-
-If you disable or do not configure this policy setting, the Switch User interface is accessible to the user in the three locations.
- Turn off Windows Startup sound
- This policy is not available in this version of Windows.
- Show first sign-in animation
- This policy setting allows you to control whether users see the first sign-in animation when signing in to the computer for the first time. This applies to both the first user of the computer who completes the initial setup and users who are added to the computer later. It also controls if Microsoft account users will be offered the opt-in prompt for services during their first sign-in.
-
-If you enable this policy setting, Microsoft account users will see the opt-in prompt for services, and users with other accounts will see the sign-in animation.
-
-If you disable this policy setting, users will not see the animation and Microsoft account users will not see the opt-in prompt for services.
-
-If you do not configure this policy setting, the user who completes the initial Windows setup will see the animation during their first sign-in. If the first user had already completed the initial setup and this policy setting is not configured, users new to this computer will not see the animation.
-
- Note: The first sign-in animation will not be shown on Server, so this policy will have no effect.
-
- Do not enumerate connected users on domain-joined computers
- This policy setting prevents connected users from being enumerated on domain-joined computers.
-
-If you enable this policy setting, the Logon UI will not enumerate any connected users on domain-joined computers.
-
-If you disable or do not configure this policy setting, connected users will be enumerated on domain-joined computers.
- Enumerate local users on domain-joined computers
- This policy setting allows local users to be enumerated on domain-joined computers.
-
-If you enable this policy setting, Logon UI will enumerate all local users on domain-joined computers.
-
-If you disable or do not configure this policy setting, the Logon UI will not enumerate local users on domain-joined computers.
- Block user from showing account details on sign-in
- This policy prevents the user from showing account details (email address or user name) on the sign-in screen.
-
-If you enable this policy setting, the user cannot choose to show account details on the sign-in screen.
-
-If you disable or do not configure this policy setting, the user may choose to show account details on the sign-in screen.
- Turn off app notifications on the lock screen
- This policy setting allows you to prevent app notifications from appearing on the lock screen.
-
-If you enable this policy setting, no app notifications are displayed on the lock screen.
-
-If you disable or do not configure this policy setting, users can choose which apps display notifications on the lock screen.
- Show clear logon background
- This policy setting disables the acrylic blur effect on logon background image.
-
- If you enable this policy, the logon background image shows without blur.
- If you disable or do not configure this policy, the logon background image adopts the acrylic blur effect.
-
-
-
-
- Items to run at logon
-
-
- Items to run at logon
-
-
-
-
diff --git a/policy_templates/en-US/MDM.adml b/policy_templates/en-US/MDM.adml
deleted file mode 100644
index bc4183b..0000000
--- a/policy_templates/en-US/MDM.adml
+++ /dev/null
@@ -1,44 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- MDM
- Disable MDM Enrollment
- This policy setting specifies whether Mobile Device Management (MDM) Enrollment is allowed. When MDM is enabled, it allows the user to have the computer remotely managed by a MDM Server.
-
-If you do not configure this policy setting, MDM Enrollment will be enabled.
-
-If you enable this policy setting, MDM Enrollment will be disabled for all users. It will not unenroll existing MDM enrollments.
-
-If you disable this policy setting, MDM Enrollment will be enabled for all users.
-
- Enable automatic MDM enrollment using default Azure AD credentials
-
- This policy setting specifies whether to automatically enroll the device to the Mobile Device Management (MDM) service configured in Azure Active Directory (Azure AD). If the enrollment is successful, the device will remotely managed by the MDM service.
-
- Important: The device must be registered in Azure AD for enrollment to succeed.
-
- If you do not configure this policy setting, automatic MDM enrollment will not be initiated.
-
- If you enable this policy setting, a task is created to initiate enrollment of the device to MDM service specified in the Azure AD.
-
- If you disable this policy setting, MDM will be unenrolled.
-
- User Credential
- Device Credential
-
-
-
- Select Credential Type to Use:
-
-
-
- MDM Application ID represents the ID of your MDM application that is configured in Azure AD. This is optional and only required for automatic MDM enrollment using device credentials when multiple MDM applications are configured in Azure AD.
-
-
-
-
-
diff --git a/policy_templates/en-US/MMC.adml b/policy_templates/en-US/MMC.adml
deleted file mode 100644
index 5329124..0000000
--- a/policy_templates/en-US/MMC.adml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Microsoft Management Console
- ActiveX Control
- Extended View (Web View)
- Extension snap-ins
- Link to Web Address
- Restricted/Permitted snap-ins
- Restrict the user from entering author mode
- Prevents users from entering author mode.
-
-This setting prevents users from opening the Microsoft Management Console (MMC) in author mode, explicitly opening console files in author mode, and opening any console files that open in author mode by default.
-
-As a result, users cannot create console files or add or remove snap-ins. Also, because they cannot open author-mode console files, they cannot use the tools that the files contain.
-
-This setting permits users to open MMC user-mode console files, such as those on the Administrative Tools menu in Windows 2000 Server family or Windows Server 2003 family. However, users cannot open a blank MMC console window on the Start menu. (To open the MMC, click Start, click Run, and type mmc.) Users also cannot open a blank MMC console window from a command prompt.
-
-If you disable this setting or do not configure it, users can enter author mode and open author-mode console files.
- Permits or prohibits use of this snap-in.
-
-If you enable this setting, the snap-in is permitted. If you disable the setting, the snap-in is prohibited.
-
-If this setting is not configured, the setting of the "Restrict users to the explicitly permitted list of snap-ins" setting determines whether this snap-in is permitted or prohibited.
-
--- If "Restrict users to the explicitly permitted list of snap-ins" is enabled, users cannot use any snap-in except those explicitly permitted.
-
- To explicitly permit use of this snap-in, enable this setting. If this setting is not configured (or disabled), this snap-in is prohibited.
-
--- If "Restrict users to the explicitly permitted list of snap-ins" is disabled or not configured, users can use any snap-in except those explicitly prohibited.
-
- To explicitly prohibit use of this snap-in, disable this setting. If this setting is not configured (or enabled), the snap-in is permitted.
-
-When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in window in MMC. Also, when a user opens a console file that includes a prohibited snap-in, the console file opens, but the prohibited snap-in does not appear.
- Restrict users to the explicitly permitted list of snap-ins
- Lets you selectively permit or prohibit the use of Microsoft Management Console (MMC) snap-ins.
-
--- If you enable this setting, all snap-ins are prohibited, except those that you explicitly permit. Use this setting if you plan to prohibit use of most snap-ins.
-
- To explicitly permit a snap-in, open the Restricted/Permitted snap-ins setting folder and enable the settings representing the snap-in you want to permit. If a snap-in setting in the folder is disabled or not configured, the snap-in is prohibited.
-
--- If you disable this setting or do not configure it, all snap-ins are permitted, except those that you explicitly prohibit. Use this setting if you plan to permit use of most snap-ins.
-
- To explicitly prohibit a snap-in, open the Restricted/Permitted snap-ins setting folder and then disable the settings representing the snap-ins you want to prohibit. If a snap-in setting in the folder is enabled or not configured, the snap-in is permitted.
-
-When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in window in MMC. Also, when a user opens a console file that includes a prohibited snap-in, the console file opens, but the prohibited snap-in does not appear.
-
-Note: If you enable this setting, and you do not enable any settings in the Restricted/Permitted snap-ins folder, users cannot use any MMC snap-ins.
-
-
-
diff --git a/policy_templates/en-US/MMCSnapins.adml b/policy_templates/en-US/MMCSnapins.adml
deleted file mode 100644
index 88276ef..0000000
--- a/policy_templates/en-US/MMCSnapins.adml
+++ /dev/null
@@ -1,131 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Active Directory Domains and Trusts
- Active Directory Sites and Services
- Active Directory Users and Computers
- Administrative Templates (Computers)
- Administrative Templates (Users)
- ADSI Edit
- AppleTalk Routing
- Authorization Manager
- Certification Authority
- Certification Authority Policy Settings
- Certificates
- Certificate Templates
- Component Services
- Computer Management
- Connection Sharing (NAT)
- DCOM Configuration Extension
- Device Manager
- Distributed File System
- DHCP Relay Management
- Disk Defragmenter
- Disk Management
- Enterprise PKI
- Event Viewer
- Event Viewer (Windows Vista)
- Failover Clusters Manager
- FAX Service
- Folder Redirection
- FrontPage Server Extensions
- Group Policy
- Group Policy snap-in extensions
- Allows you to permit and prohibit the use of the Group Policy Object Editor snap-in and its extensions.
- Resultant Set of Policy snap-in extensions
- Group Policy Management
- Group Policy Object Editor
- Group Policy tab for Active Directory Tools
- Permits or prohibits use of the Group Policy tab in property sheets for the Active Directory Users and Computers and Active Directory Sites and Services snap-ins.
-
-If you enable this setting, the Group Policy tab is displayed in the property sheet for a site, domain, or organizational unit displayed by the Active Directory Users and Computers and Active Directory Sites and Services snap-ins. If you disable the setting, the Group Policy tab is not displayed in those snap-ins.
-
-If this setting is not configured, the setting of the "Restrict users to the explicitly permitted list of snap-ins" setting determines whether this tab is displayed.
-
--- If "Restrict users to the explicitly permitted list of snap-ins" is enabled, users will not have access to the Group Policy tab.
-
- To explicitly permit use of the Group Policy tab, enable this setting. If this setting is not configured (or disabled), the Group Policy tab is inaccessible.
-
--- If "Restrict users to the explicitly permitted list of snap-ins" is disabled or not configured, users will have access to the Group Policy tab.
-
- To explicitly prohibit use of the Group Policy tab, disable this setting. If this setting is not configured (or enabled), the Group Policy tab is accessible.
-
-When the Group Policy tab is inaccessible, it does not appear in the site, domain, or organizational unit property sheets.
- Health Registration Authority (HRA)
- Internet Authentication Service (IAS)
- IAS Logging
- Internet Explorer Maintenance
- IGMP Routing
- Internet Information Services
- Indexing Service
- IP Routing
- IP Security Policy Management
- IP Security Monitor
- IPX RIP Routing
- IPX Routing
- IPX SAP Routing
- Local Users and Groups
- Logical and Mapped Drives
- NAP Client Configuration
- Network Policy Server (NPS)
- .Net Framework Configuration
- Online Responder
- OSPF Routing
- Performance Logs and Alerts
- Public Key Policies
- QoS Admission Control
- RAS Dialin - User Node
- Remote Access
- Remote Desktops
- Removable Storage
- This policy setting permits or prohibits the use of this snap-in.
-
-If you enable this policy setting, the snap-in is permitted and can be added into the Microsoft Management Console or run from the command line as a standalone console.
-
-If you disable this policy setting, the snap-in is prohibited and cannot be added into the Microsoft Management Console or run from the command line as a standalone console. An error message is displayed stating that policy is prohibiting the use of this snap-in.
-
-If this policy setting is not configured, the setting of the "Restrict users to the explicitly permitted list of snap-ins" setting determines whether this snap-in is permitted or prohibited.
-
--- If the policy setting "Restrict users to the explicitly permitted list of snap-ins" is enabled, users cannot use any snap-in except those explicitly permitted. To explicitly permit use of this snap-in, enable this policy setting. If this policy setting is not configured or disabled, this snap-in is prohibited.
-
--- If the policy setting "Restrict users to the explicitly permitted list of snap-ins" is disabled or not configured, users can use any snap-in except those explicitly prohibited. To explicitly prohibit use of this snap-in, disable this policy setting. If this policy setting is not configured or enabled, the snap-in is permitted.
-
-When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in window in MMC. Also, when a user opens a console file that includes a prohibited snap-in, the console file opens, but the prohibited snap-in does not appear.
- Resultant Set of Policy snap-in
- RIP Routing
- Remote Installation Services
- Routing
- Routing and Remote Access
- Removable Storage Management
- Security Configuration and Analysis
- Scripts (Startup/Shutdown)
- Scripts (Logon/Logoff)
- Security Settings
- Security Templates
- Send Console Message
- Server Manager
- Service Dependencies
- Services
- Shared Folders
- Shared Folders Ext
- SMTP Protocol
- SNMP
- Software Installation (Computers)
- Software Installation (Users)
- System Information
- System Properties
- Telephony
- Remote Desktop Services Configuration
- TPM Management
- Windows Firewall with Advanced Security
- Wireless Monitor
- Wireless Network (IEEE 802.11) Policies
- Wired Network (IEEE 802.3) Policies
- WMI Control
-
-
-
diff --git a/policy_templates/en-US/MSAPolicy.adml b/policy_templates/en-US/MSAPolicy.adml
deleted file mode 100644
index 4a83df7..0000000
--- a/policy_templates/en-US/MSAPolicy.adml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- Microsoft account
- Configuration for Microsoft account
-
-
- Microsoft account
- Block all consumer Microsoft account user authentication
- This setting controls whether users can provide Microsoft accounts for authentication for applications or services. If this setting is enabled, all applications and services on the device are prevented from using Microsoft accounts for authentication.
-This applies both to existing users of a device and new users who may be added. However, any application or service that has already authenticated a user will not be affected by enabling this setting until the authentication cache expires.
-It is recommended to enable this setting before any user signs in to a device to prevent cached tokens from being present. If this setting is disabled or not configured, applications and services can use Microsoft accounts for authentication.
-By default, this setting is Disabled. This setting does not affect whether users can sign in to devices by using Microsoft accounts, or the ability for users to provide Microsoft accounts via the browser for authentication with web-based applications.
-
- Only allow device authentication for the Microsoft Account Sign-In Assistant
- This setting determines whether to only allow enterprise device authentication for the Microsoft Account Sign-in Assistant service (wlidsvc). By default, this setting is disabled and allows both user and device authentication. When the value is set to 1, only allow device authentication, and block user authentication.
-
-
-
diff --git a/policy_templates/en-US/MSDT.adml b/policy_templates/en-US/MSDT.adml
deleted file mode 100644
index 633c9cd..0000000
--- a/policy_templates/en-US/MSDT.adml
+++ /dev/null
@@ -1,99 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Microsoft Support Diagnostic Tool
- Microsoft Support Diagnostic Tool: Configure execution level
- This policy setting determines the execution level for Microsoft Support Diagnostic Tool.
-
-Microsoft Support Diagnostic Tool (MSDT) gathers diagnostic data for analysis by support professionals.
-
-If you enable this policy setting, administrators can use MSDT to collect and send diagnostic data to a support professional to resolve a problem.
-
-If you disable this policy setting, MSDT cannot gather diagnostic data.
-
-If you do not configure this policy setting, MSDT is turned on by default.
-
-This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
-
-No reboots or service restarts are required for this policy setting to take effect. Changes take effect immediately.
-
-This policy setting will only take effect when the Diagnostic Policy Service (DPS) is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
-
- Microsoft Support Diagnostic Tool: Restrict tool download
- This policy setting restricts the tool download policy for Microsoft Support Diagnostic Tool.
-
-Microsoft Support Diagnostic Tool (MSDT) gathers diagnostic data for analysis by support professionals. For some problems, MSDT may prompt the user to download additional tools for troubleshooting.
-
-These tools are required to completely troubleshoot the problem. If tool download is restricted, it may not be possible to find the root cause of the problem.
-
-If you enable this policy setting for remote troubleshooting, MSDT prompts the user to download additional tools to diagnose problems on remote computers only. If you enable this policy setting for local and remote troubleshooting, MSDT always prompts for additional tool downloading.
-
-If you disable this policy setting, MSDT never downloads tools, and is unable to diagnose problems on remote computers.
-
-If you do not configure this policy setting, MSDT prompts the user before downloading any additional tools.
-
-No reboots or service restarts are required for this policy setting to take effect. Changes take effect immediately.
-
-This policy setting will take effect only when MSDT is enabled.
-
-This policy setting will only take effect when the Diagnostic Policy Service (DPS) is in the running state. When the service is stopped or disabled, diagnostic scenarios are not executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
- Remote troubleshooting only
- Local and remote troubleshooting
- Microsoft Support Diagnostic Tool: Turn on MSDT interactive communication with support provider
- This policy setting configures Microsoft Support Diagnostic Tool (MSDT) interactive communication with the support provider. MSDT gathers diagnostic data for analysis by support professionals.
-
-If you enable this policy setting, users can use MSDT to collect and send diagnostic data to a support professional to resolve a problem.
-
-By default, the support provider is set to Microsoft Corporation.
-
-If you disable this policy setting, MSDT cannot run in support mode, and no data can be collected or sent to the support provider.
-
-If you do not configure this policy setting, MSDT support mode is enabled by default.
-
-No reboots or service restarts are required for this policy setting to take effect. Changes take effect immediately.
-
-
-Troubleshooting: Allow users to access recommended troubleshooting for known problems
-This policy setting configures how troubleshooting for known problems can be applied on the device and lets administrators configure how it's applied to their domains/IT environments.
-
-Not configuring this policy setting will allow the user to configure how troubleshooting is applied.
-
-Enabling this policy allows you to configure how troubleshooting is applied on the user's device. You can select from one of the following values:
-0 = Do not allow users, system features, or Microsoft to apply troubleshooting.
-1 = Only automatically apply troubleshooting for critical problems by system features and Microsoft.
-2 = Automatically apply troubleshooting for critical problems by system features and Microsoft. Notify users when troubleshooting for other problems is available and allow users to choose to apply or ignore.
-3 = Automatically apply troubleshooting for critical and other problems by system features and Microsoft. Notify users when troubleshooting has solved a problem.
-4 = Automatically apply troubleshooting for critical and other problems by system features and Microsoft. Do not notify users when troubleshooting has solved a problem.
-5 = Allow the user to choose their own troubleshooting settings.
-
-After setting this policy, you can use the following instructions to check devices in your domain for available troubleshooting from Microsoft:
-1. Create a bat script with the following contents:
-rem The following batch script triggers Recommended Troubleshooting
-schtasks /run /TN "\Microsoft\Windows\Diagnosis\RecommendedTroubleshootingScanner"
-
-2. To create a new immediate task, navigate to the Group Policy Management Editor > Computer Configuration > Preferences and select Control Panel Settings.
-3. Under Control Panel settings, right-click on Scheduled Tasks and select New. Select Immediate Task (At least Windows 7).
-4. Provide name and description as appropriate, then under Security Options set the user account to System and select the Run with highest privileges checkbox.
-5. In the Actions tab, create a new action, select Start a Program as its type, then enter the file created in step 1.
-6. Configure the task to deploy to your domain.
-Do not allow users, system features, or Microsoft to apply troubleshooting.
-Only automatically apply troubleshooting for critical problems by system features and Microsoft.
-Automatically apply troubleshooting for critical problems by system features and Microsoft. Notify users when troubleshooting for other problems is available and allow users to choose to apply or ignore.
-Automatically apply troubleshooting for critical and other problems by system features and Microsoft. Notify users when troubleshooting has solved a problem.
-Automatically apply troubleshooting for critical and other problems by system features and Microsoft. Do not notify users when troubleshooting has solved a problem.
-Allow the user to choose their own troubleshooting settings.
-
-
-
- Tool downloads allowed
-
-
- Allow recommended troubleshooting from Microsoft for known problems
-
-
-
-
diff --git a/policy_templates/en-US/MSI.adml b/policy_templates/en-US/MSI.adml
deleted file mode 100644
index 997c008..0000000
--- a/policy_templates/en-US/MSI.adml
+++ /dev/null
@@ -1,330 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow users to browse for source while elevated
- This policy setting allows users to search for installation files during privileged installations.
-
-If you enable this policy setting, the Browse button in the "Use feature from" dialog box is enabled. As a result, users can search for installation files even when the installation program is running with elevated system privileges.
-
-Because the installation is running with elevated system privileges, users can browse through directories that their own permissions would not allow.
-
-This policy setting does not affect installations that run in the user's security context. Also, see the "Remove browse dialog box for new source" policy setting.
-
-If you disable or do not configure this policy setting, by default, only system administrators can browse during installations with elevated privileges, such as installations offered on the desktop or displayed in Add or Remove Programs.
- Allow users to use media source while elevated
- This policy setting allows users to install programs from removable media during privileged installations.
-
-If you enable this policy setting, all users are permitted to install programs from removable media, such as floppy disks and CD-ROMs, even when the installation program is running with elevated system privileges.
-
-This policy setting does not affect installations that run in the user's security context. By default, users can install from removable media when the installation runs in their own security context.
-
-If you disable or do not configure this policy setting, by default, users can install programs from removable media only when the installation runs in the user's security context. During privileged installations, such as those offered on the desktop or displayed in Add or Remove Programs, only system administrators can install from removable media.
-
-Also, see the "Prevent removable media source for any install" policy setting.
- Allow users to patch elevated products
- This policy setting allows users to patch elevated products.
-
-If you enable this policy setting, all users are permitted to install patches, even when the installation program is running with elevated system privileges. Patches are updates or upgrades that replace only those program files that have changed. Because patches can easily be vehicles for malicious programs, some installations prohibit their use.
-
-If you disable or do not configure this policy setting, by default, only system administrators can apply patches during installations with elevated privileges, such as installations offered on the desktop or displayed in Add or Remove Programs.
-
-This policy setting does not affect installations that run in the user's security context. By default, users can install patches to programs that run in their own security context. Also, see the "Prohibit patching" policy setting.
- Always install with elevated privileges
- This policy setting directs Windows Installer to use elevated permissions when it installs any program on the system.
-
-If you enable this policy setting, privileges are extended to all programs. These privileges are usually reserved for programs that have been assigned to the user (offered on the desktop), assigned to the computer (installed automatically), or made available in Add or Remove Programs in Control Panel. This profile setting lets users install programs that require access to directories that the user might not have permission to view or change, including directories on highly restricted computers.
-
-If you disable or do not configure this policy setting, the system applies the current user's permissions when it installs programs that a system administrator does not distribute or offer.
-
-Note: This policy setting appears both in the Computer Configuration and User Configuration folders. To make this policy setting effective, you must enable it in both folders.
-
-Caution: Skilled users can take advantage of the permissions this policy setting grants to change their privileges and gain permanent access to restricted files and folders. Note that the User Configuration version of this policy setting is not guaranteed to be secure.
- Restart Manager On
- Restart Manager Off
- Restart Manager Off for Legacy App Setup
- Always
- Prohibit use of Restart Manager
- This policy setting controls Windows Installer's interaction with the Restart Manager. The Restart Manager API can eliminate or reduce the number of system restarts that are required to complete an installation or update.
-
-If you enable this policy setting, you can use the options in the Prohibit Use of Restart Manager box to control file in use detection behavior.
-
--- The "Restart Manager On" option instructs Windows Installer to use Restart Manager to detect files in use and mitigate a system restart, when possible.
-
--- The "Restart Manager Off" option turns off Restart Manager for file in use detection and the legacy file in use behavior is used.
-
--- The "Restart Manager Off for Legacy App Setup" option applies to packages that were created for Windows Installer versions lesser than 4.0. This option lets those packages display the legacy files in use UI while still using Restart Manager for detection.
-
-If you disable or do not configure this policy setting, Windows Installer will use Restart Manager to detect files in use and mitigate a system restart, when possible.
- Remove browse dialog box for new source
-
- This policy setting prevents users from searching for installation files when they add features or components to an installed program.
-
- If you enable this policy setting, the Browse button beside the "Use feature from" list in the Windows Installer dialog box is disabled. As a result, users must select an installation file source from the "Use features from" list that the system administrator configures.
-
- This policy setting applies even when the installation is running in the user's security context.
-
- If you disable or do not configure this policy setting, the Browse button is enabled when an installation is running in the user's security context. But only system administrators can browse when an installation is running with elevated system privileges, such as installations offered on the desktop or in Add or Remove Programs.
-
- This policy setting affects Windows Installer only. It does not prevent users from selecting other browsers, such as File Explorer or Network Locations, to search for installation files.
-
- Also, see the "Enable user to browse for source while elevated" policy setting.
- Prohibit flyweight patching
- This policy setting controls the ability to turn off all patch optimizations.
-
-If you enable this policy setting, all Patch Optimization options are turned off during the installation.
-
-If you disable or do not configure this policy setting, it enables faster application of patches by removing execution of unnecessary actions. The flyweight patching mode is primarily designed for patches that just update a few files or registry values. The Installer will analyze the patch for specific changes to determine if optimization is possible. If so, the patch will be applied using a minimal set of processing.
- Disable logging via package settings off
- Disable logging via package settings on
- Turn off logging via package settings
- This policy setting controls Windows Installer's processing of the MsiLogging property. The MsiLogging property in an installation package can be used to enable automatic logging of all install operations for the package.
-
-If you enable this policy setting, you can use the options in the Disable logging via package settings box to control automatic logging via package settings behavior.
-
--- The "Logging via package settings on" option instructs Windows Installer to automatically generate log files for packages that include the MsiLogging property.
-
--- The "Logging via package settings off" option turns off the automatic logging behavior when specified via the MsiLogging policy. Log files can still be generated using the logging command line switch or the Logging policy.
-
-If you disable or do not configure this policy setting, Windows Installer will automatically generate log files for those packages that include the MsiLogging property.
- Prevent removable media source for any installation
- This policy setting prevents users from installing any programs from removable media.
-
-If you enable this policy setting, if a user tries to install a program from removable media, such as CD-ROMs, floppy disks, and DVDs, a message appears stating that the feature cannot be found.
-
-This policy setting applies even when the installation is running in the user's security context.
-
-If you disable or do not configure this policy setting, users can install from removable media when the installation is running in their own security context, but only system administrators can use removable media when an installation is running with elevated system privileges, such as installations offered on the desktop or in Add or Remove Programs.
-
-Also, see the "Enable user to use media source while elevated" and "Hide the 'Add a program from CD-ROM or floppy disk' option" policy settings.
- Turn off Windows Installer
- This policy setting restricts the use of Windows Installer.
-
-If you enable this policy setting, you can prevent users from installing software on their systems or permit users to install only those programs offered by a system administrator. You can use the options in the Disable Windows Installer box to establish an installation setting.
-
--- The "Never" option indicates Windows Installer is fully enabled. Users can install and upgrade software. This is the default behavior for Windows Installer on Windows 2000 Professional, Windows XP Professional and Windows Vista when the policy is not configured.
-
--- The "For non-managed applications only" option permits users to install only those programs that a system administrator assigns (offers on the desktop) or publishes (adds them to Add or Remove Programs). This is the default behavior of Windows Installer on Windows Server 2003 family when the policy is not configured.
-
--- The "Always" option indicates that Windows Installer is disabled.
-
-This policy setting affects Windows Installer only. It does not prevent users from using other methods to install and upgrade programs.
- Never
- For non-managed applications only
- Prevent users from using Windows Installer to install updates and upgrades
- This policy setting prevents users from using Windows Installer to install patches.
-
-If you enable this policy setting, users are prevented from using Windows Installer to install patches. Patches are updates or upgrades that replace only those program files that have changed. Because patches can be easy vehicles for malicious programs, some installations prohibit their use.
-
-Note: This policy setting applies only to installations that run in the user's security context.
-
-If you disable or do not configure this policy setting, by default, users who are not system administrators cannot apply patches to installations that run with elevated system privileges, such as those offered on the desktop or in Add or Remove Programs.
-
-Also, see the "Enable user to patch elevated products" policy setting.
- Prohibit rollback
- This policy setting prohibits Windows Installer from generating and saving the files it needs to reverse an interrupted or unsuccessful installation.
-
-If you enable this policy setting, Windows Installer is prevented from recording the original state of the system and sequence of changes it makes during installation. It also prevents Windows Installer from retaining files it intends to delete later. As a result, Windows Installer cannot restore the computer to its original state if the installation does not complete.
-
-This policy setting is designed to reduce the amount of temporary disk space required to install programs. Also, it prevents malicious users from interrupting an installation to gather data about the internal state of the computer or to search secure system files. However, because an incomplete installation can render the system or a program inoperable, do not use this policy setting unless it is essential.
-
-This policy setting appears in the Computer Configuration and User Configuration folders. If the policy setting is enabled in either folder, it is considered be enabled, even if it is explicitly disabled in the other folder.
- Allow user control over installs
- This policy setting permits users to change installation options that typically are available only to system administrators.
-
-If you enable this policy setting, some of the security features of Windows Installer are bypassed. It permits installations to complete that otherwise would be halted due to a security violation.
-
-If you disable or do not configure this policy setting, the security features of Windows Installer prevent users from changing installation options typically reserved for system administrators, such as specifying the directory to which files are installed.
-
-If Windows Installer detects that an installation package has permitted the user to change a protected option, it stops the installation and displays a message. These security features operate only when the installation program is running in a privileged security context in which it has access to directories denied to the user.
-
-This policy setting is designed for less restrictive environments. It can be used to circumvent errors in an installation program that prevents software from being installed.
- Windows Installer
- Allow User Installs
- Prohibit non-administrators from applying vendor signed updates
- This policy setting controls the ability of non-administrators to install updates that have been digitally signed by the application vendor.
-
-Non-administrator updates provide a mechanism for the author of an application to create digitally signed updates that can be applied by non-privileged users.
-
-If you enable this policy setting, only administrators or users with administrative privileges can apply updates to Windows Installer based applications.
-
-If you disable or do not configure this policy setting, users without administrative privileges can install non-administrator updates.
- Prohibit removal of updates
- This policy setting controls the ability for users or administrators to remove Windows Installer based updates.
-
-This policy setting should be used if you need to maintain a tight control over updates. One example is a lockdown environment where you want to ensure that updates once installed cannot be removed by users or administrators.
-
-If you enable this policy setting, updates cannot be removed from the computer by a user or an administrator. The Windows Installer can still remove an update that is no longer applicable to the product.
-
-If you disable or do not configure this policy setting, a user can remove an update from the computer only if the user has been granted privileges to remove the update. This can depend on whether the user is an administrator, whether "Disable Windows Installer" and "Always install with elevated privileges" policy settings are set, and whether the update was installed in a per-user managed, per-user unmanaged, or per-machine context."
- Turn off creation of System Restore checkpoints
- This policy setting prevents Windows Installer from creating a System Restore checkpoint each time an application is installed. System Restore enables users, in the event of a problem, to restore their computers to a previous state without losing personal data files.
-
-If you enable this policy setting, the Windows Installer does not generate System Restore checkpoints when installing applications.
-
-If you disable or do not configure this policy setting, by default, the Windows Installer automatically creates a System Restore checkpoint each time an application is installed, so that users can restore their computer to the state it was in before installing the application.
- Prohibit User Installs
- This policy setting allows you to configure user installs. To configure this policy setting, set it to enabled and use the drop-down list to select the behavior you want.
-
-If you do not configure this policy setting, or if the policy setting is enabled and "Allow User Installs" is selected, the installer allows and makes use of products that are installed per user, and products that are installed per computer. If the installer finds a per-user install of an application, this hides a per-computer installation of that same product.
-
-If you enable this policy setting and "Hide User Installs" is selected, the installer ignores per-user applications. This causes a per-computer installed application to be visible to users, even if those users have a per-user install of the product registered in their user profile.
- Enforce upgrade component rules
- This policy setting causes the Windows Installer to enforce strict rules for component upgrades.
-
-If you enable this policy setting, strict upgrade rules will be enforced by the Windows Installer which may cause some upgrades to fail. Upgrades can fail if they attempt to do one of the following:
-
-(1) Remove a component from a feature.
-This can also occur if you change the GUID of a component. The component identified by the original GUID appears to be removed and the component as identified by the new GUID appears as a new component.
-
-(2) Add a new feature to the top or middle of an existing feature tree.
-The new feature must be added as a new leaf feature to an existing feature tree.
-
-If you disable or do not configure this policy setting, the Windows Installer will use less restrictive rules for component upgrades.
- Hide User Installs
- Control maximum size of baseline file cache
-
- This policy controls the percentage of disk space available to the Windows Installer baseline file cache.
-
- The Windows Installer uses the baseline file cache to save baseline files modified by binary delta difference updates. The cache is used to retrieve the baseline file for future updates. The cache eliminates user prompts for source media when new updates are applied.
-
- If you enable this policy setting you can modify the maximum size of the Windows Installer baseline file cache.
-
- If you set the baseline cache size to 0, the Windows Installer will stop populating the baseline cache for new updates. The existing cached files will remain on disk and will be deleted when the product is removed.
-
- If you set the baseline cache to 100, the Windows Installer will use available free space for the baseline file cache.
-
- If you disable or do not configure this policy setting, the Windows Installer will uses a default value of 10 percent for the baseline file cache maximum size.
- Specify the types of events Windows Installer records in its transaction log
-
- Specifies the types of events that Windows Installer records in its transaction log for each installation. The log, Msi.log, appears in the Temp directory of the system volume.
-
- When you enable this policy setting, you can specify the types of events you want Windows Installer to record. To indicate that an event type is recorded, type the letter representing the event type. You can type the letters in any order and list as many or as few event types as you want.
-
- To disable logging, delete all of the letters from the box.
-
- If you disable or do not configure this policy setting, Windows Installer logs the default event types, represented by the letters "iweap."
- Patch Optimization Off
- Patch Optimization On
- Prevent Internet Explorer security prompt for Windows Installer scripts
- This policy setting allows Web-based programs to install software on the computer without notifying the user.
-
-If you disable or do not configure this policy setting, by default, when a script hosted by an Internet browser tries to install a program on the system, the system warns users and allows them to select or refuse the installation.
-
-If you enable this policy setting, the warning is suppressed and allows the installation to proceed.
-
-This policy setting is designed for enterprises that use Web-based tools to distribute programs to their employees. However, because this policy setting can pose a security risk, it should be applied cautiously.
- Specify the order in which Windows Installer searches for installation files
- This policy setting specifies the order in which Windows Installer searches for installation files.
-
-If you disable or do not configure this policy setting, by default, the Windows Installer searches the network first, then removable media (floppy drive, CD-ROM, or DVD), and finally, the Internet (URL).
-
-If you enable this policy setting, you can change the search order by specifying the letters representing each file source in the order that you want Windows Installer to search:
-
--- "n" represents the network;
-
--- "m" represents media;
-
--- "u" represents URL, or the Internet.
-
-To exclude a file source, omit or delete the letter representing that source type.
- Microsoft Windows XP or Windows 2000 with Windows Installer v2.0
- Windows Installer v3.0
- Windows Installer v4.0
- Windows Installer v4.5
- Save copies of transform files in a secure location on workstation
- This policy setting saves copies of transform files in a secure location on the local computer.
-
-Transform files consist of instructions to modify or customize a program during installation.
-
-If you enable this policy setting, the transform file is saved in a secure location on the user's computer.
-
-If you do not configure this policy setting on Windows Server 2003, Windows Installer requires the transform file in order to repeat an installation in which the transform file was used, therefore, the user must be using the same computer or be connected to the original or identical media to reinstall, remove, or repair the installation.
-
-This policy setting is designed for enterprises to prevent unauthorized or malicious editing of transform files.
-
-If you disable this policy setting, Windows Installer stores transform files in the Application Data directory in the user's profile.
-
-If you do not configure this policy setting on Windows 2000 Professional, Windows XP Professional and Windows Vista, when a user reinstalls, removes, or repairs an installation, the transform file is available, even if the user is on a different computer or is not connected to the network.
- Turn off shared components
- This policy setting controls the ability to turn off shared components.
-
-If you enable this policy setting, no packages on the system get the shared component functionality enabled by the msidbComponentAttributesShared attribute in the Component Table.
-
-If you disable or do not configure this policy setting, by default, the shared component functionality is allowed.
- Prevent embedded UI
- This policy setting controls the ability to prevent embedded UI.
-
-If you enable this policy setting, no packages on the system can run embedded UI.
-
-If you disable or do not configure this policy setting, embedded UI is allowed to run.
-
-
-
-
- This policy setting must be set for the machine and the user to be enforced.
-
-
-
- This policy setting must be set for the machine and the user to be enforced.
-
-
- Prohibit Usage of Restart Manager
-
-
- Prohibit Flyweight Patching
-
-
- Disable logging via package settings
-
-
- Disable Windows Installer
-
-
-
- This policy setting may be set for the machine or for the user.
-
-
-
- This policy setting may be set for the machine or for the user.
-
-
- User Install Behavior:
-
-
- Baseline file cache maximum size
-
-
-
-
- iweap
-
- To activate logging, enter one or more of the modes below.
- "iwearucmpvox" will log everything but adds time to the install.
- i - Status messages
- w - Non-fatal warnings
- e - All error messages
- a - Start up of actions
- r - Action-specific records
- u - User requests
- c - Initial UI parameters
- m - Out-of-memory
- p - Terminal properties
- v - Verbose output
- o - Out of disk space messages
- x - Extra debugging information
-
-
-
-
- nmu
-
- n = network, m = media (CD), u = URL
- A few valid examples: nmu, n, nu, mn
-
-
-
-
diff --git a/policy_templates/en-US/Messaging.adml b/policy_templates/en-US/Messaging.adml
deleted file mode 100644
index 1723d1a..0000000
--- a/policy_templates/en-US/Messaging.adml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- Messaging Service Group Policy Settings
- Messaging Service Group Policy Settings
-
-
- Messaging
- Allow Message Service Cloud Sync
- This policy setting allows backup and restore of cellular text messages to Microsoft's cloud services.
-
-
-
diff --git a/policy_templates/en-US/MicrosoftEdge.adml b/policy_templates/en-US/MicrosoftEdge.adml
deleted file mode 100644
index aad7b17..0000000
--- a/policy_templates/en-US/MicrosoftEdge.adml
+++ /dev/null
@@ -1,627 +0,0 @@
-
-
-
- Microsoft Edge Group Policies
- Policies defined to manage Microsoft Edge settings via Group Policy Management services.
-
-
-
- Only Microsoft Edge 1.0
- Microsoft Edge on Windows 10 or later
- Microsoft Edge on Windows 10, Version 1511 or later
- Microsoft Edge on Windows 10, Version 1607 or later
- Microsoft Edge on Windows 10, Version 1703 or later
- Microsoft Edge on Windows 10, Version 1709 or later
- Microsoft Edge on Windows 10, Version 1708 or later
- Microsoft Edge on Windows 10, Version 1803 or later
- Microsoft Edge on Windows 10, Version 1809 or later
- Microsoft Edge
- Microsoft Edge Category
-
-
-
-
-
- Configure Start pages
- When you enable the Configure Open Microsoft Edge With policy, you can configure one or more Start pages. When you enable this policy, users are not allowed to make changes to their Start pages.
-
-If enabled, you must include URLs to the pages, separating multiple pages using angle brackets in the following format:
-
- <support.contoso.com><support.microsoft.com>
-
-If disabled or not configured, the webpages specified in App settings loads as the default Start pages.
-
-Version 1703 or later:
-If you do not want to send traffic to Microsoft, enable this policy and use the <about:blank> value, which honors domain- and non-domain-joined devices, when it is the only configured URL.
-
-Version 1809:
-If enabled, and you select either Start page, New Tab page, or previous page in the Configure Open Microsoft Edge With policy, Microsoft Edge ignores the Configure Start Pages policy. If not configured or you set the Configure Open Microsoft Edge With policy to a specific page or pages, Microsoft Edge uses the Configure Start Pages policy.
-
-Supported devices: Domain-joined or MDM-enrolled
-Related policy:
-- Configure Open Microsoft Edge With
-- Disable Lockdown of Start Pages
- Disable lockdown of Start pages
- You can configure Microsoft Edge to disable the lockdown of Start pages allowing users to change or customize their start pages. To do this, you must also enable the Configure Start Pages or Configure Open Microsoft With policy. When enabled, all configured start pages are editable. Any Start page configured using the Configure Start pages policy is not locked down allowing users to edit their Start pages.
-
-If disabled or not configured, the Start pages configured in the Configure Start Pages policy cannot be changed and remain locked down.
-
-Supported devices: Domain-joined or MDM-enrolled
-Related policy:
-- Configure Start Pages
-- Configure Open Microsoft Edge With
- Prevent changes to Favorites on Microsoft Edge
- This policy setting lets you decide whether employees can add, import, sort, or edit the Favorites list on Microsoft Edge.
-
-If you enable this setting, employees won't be able to add, import, or change anything in the Favorites list. Also as part of this, Save a Favorite, Import settings, and the context menu items (such as, Create a new folder) are all turned off.
-
-Important
-Don't enable both this setting and the Keep favorites in sync between Internet Explorer and Microsoft Edge setting. Enabling both settings stops employees from syncing their favorites between Internet Explorer and Microsoft Edge.
-
-If you disable or don't configure this setting (default), employees can add, import and make changes to the Favorites list.
- Prevent certificate error overrides
- Web security certificates are used to ensure a site your users go to is legitimate, and in some circumstances encrypts the data. With this policy, you can specify whether to prevent users from bypassing the security warning to sites that have SSL errors.
-
-If enabled, overriding certificate errors are not allowed.
-
-If disabled or not configured, overriding certificate errors are allowed.
- Allow Address bar drop-down list suggestions
- This policy setting lets you decide whether the Address bar drop-down functionality is available in Microsoft Edge. We recommend disabling this setting if you want to minimize network connections from Microsoft Edge to Microsoft services.
-
- Note: Disabling this setting turns off the Address bar drop-down functionality. Therefore, because search suggestions are shown in the drop-down, this setting takes precedence over the "Configure search suggestions in Address bar" setting.
-
- If you enable or don't configure this setting, employees can see the Address bar drop-down functionality in Microsoft Edge.
-
- If you disable this setting, employees won't see the Address bar drop-down functionality in Microsoft Edge. This setting also disables the user-defined setting, "Show search and site suggestions as I type".
- Configure Autofill
- This policy setting lets you decide whether employees can use Autofill to automatically fill in form fields while using Microsoft Edge. By default, employees can choose whether to use Autofill.
-
-If you enable this setting, employees can use Autofill to automatically fill in forms while using Microsoft Edge.
-
-If you disable this setting, employees can't use Autofill to automatically fill in forms while using Microsoft Edge.
-
-If you don't configure this setting, employees can choose whether to use Autofill to automatically fill in forms while using Microsoft Edge.
- Allow Developer Tools
- This policy setting lets you decide whether F12 Developer Tools are available on Microsoft Edge.
-
-If you enable or don't configure this setting, the F12 Developer Tools are available in Microsoft Edge.
-
-If you disable this setting, the F12 Developer Tools aren't available in Microsoft Edge.
- Configure Do Not Track
- This policy setting lets you decide whether employees can send Do Not Track requests to websites that ask for tracking info. By default, Do Not Track requests aren't sent, but employees can choose to turn on and send requests.
-
-If you enable this setting, Do Not Tracker requests are always sent to websites asking for tracking info.
-
-If you disable this setting, Do Not Track requests are never sent to websites asking for tracking info.
-
-If you don't configure this setting, employees can choose whether to send Do Not Track requests to websites asking for tracking info.
- Allow FullScreen Mode
- With this policy, you can specify whether to allow full-screen mode, which shows only the web content and hides the Microsoft Edge UI.
-
-If enabled or not configured, full-screen mode is available for use in Microsoft Edge. Your users and extensions must have the proper permissions.
-
-If disabled, full-screen mode is unavailable for use in Microsoft Edge.
- Allow InPrivate browsing
- This policy setting lets you decide whether employees can browse using InPrivate website browsing.
-
-If you enable or don't configure this setting, employees can use InPrivate website browsing.
-
-If you disable this setting, employees can't use InPrivate website browsing.
- Configure Password Manager
- This policy setting lets you decide whether employees can save their passwords locally, using Password Manager. By default, Password Manager is turned on.
-
-If you enable this setting, employees can use Password Manager to save their passwords locally.
-
-If you disable this setting, employees can't use Password Manager to save their passwords locally.
-
-If you don't configure this setting, employees can choose whether to use Password Manager to save their passwords locally.
- Configure Pop-up Blocker
- This policy setting lets you decide whether to turn on Pop-up Blocker. By default, Pop-up Blocker is turned on..
-
-If you enable this setting, Pop-up Blocker is turned on, stopping pop-up windows from appearing.
-
-If you disable this setting, Pop-up Blocker is turned off, letting pop-ups windows appear.
-
-If you don't configure this setting, employees can choose whether to use Pop-up Blocker.
- Allow printing
- With this policy, you can restrict whether printing web content in Microsoft Edge is allowed.
-
-If enabled, printing is allowed.
-
-If disabled, printing is not allowed.
- For PDF files that have both landscape and portrait pages, print each in its own orientation.
- With this policy, you can print PDF files based on per page orientation in Microsoft Edge.
-
-If enabled, mixed mode printing is allowed.
-
-If disabled, mixed mode printing is not allowed.
- Allow Saving History
- Microsoft Edge saves your user's browsing history, which is made up of info about the websites they visit, on their devices.
-
-If enabled or not configured, the browsing history is saved and visible in the History pane.
-
-If disabled, the browsing history stops saving and is not visible in the History pane. If browsing history exists before this policy was disabled, the previous browsing history remains visible in the History pane. This policy, when disabled, does not stop roaming of existing history or history coming from other roamed devices.
- Allow search engine customization
- This policy setting lets you decide whether users can change their search engine. If you disable this setting, users can't add new search engines or change the default used in the address bar.
-
-Important
-This setting can only be used with domain-joined or MDM-enrolled devices. For more info, see the Microsoft browser extension policy (aka.ms/browserpolicy).
-
-If you enable or don't configure this policy, users can add new search engines and change the default used in the address bar from within Microsoft Edge Settings.
-
-If you disable this setting, users can't add search engines or change the default used in the address bar.
- Configure search suggestions in Address bar
- This policy setting lets you decide whether search suggestions appear in the Address bar of Microsoft Edge. By default, employees can choose whether search suggestions appear in the Address bar of Microsoft Edge.
-
-If you enable this setting, employees can see search suggestions in the Address bar of Microsoft Edge.
-
-If you disable this setting, employees can't see search suggestions in the Address bar of Microsoft Edge.
-
-If you don't configure this setting, employees can choose whether search suggestions appear in the Address bar of Microsoft Edge.
- Allow Sideloading of extension
- Sideloading installs and runs unverified extensions in Microsoft Edge. With this policy, you can specify whether unverified extensions can be sideloaded in Microsoft Edge.
-
-If enabled or not configured, sideloading of unverified extensions in Microsoft Edge is allowed.
-
-If disabled, sideloading of unverified extensions in Microsoft Edge is not allowed. Extensions can be installed only through Microsoft store (including a store for business), enterprise storefront (such as Company Portal) or PowerShell (using Add-AppxPackage). When disabled, this policy does not prevent sideloading of extensions using Add-AppxPackage via PowerShell. To prevent this, in Group Policy Editor, enable Allows development of Windows Store apps and installing them from an integrated development environment (IDE), which is located at:
-
-Computer Configuration > Administrative Templates > Windows Components > App Package Deployment
-
-Supported versions: Microsoft Edge on Windows 10, version 1809
-Default setting: Disabled or not configured
-Related policies:
-- Allows development of Windows Store apps and installing them from an integrated development environment (IDE)
-- Allow all trusted apps to install
- Configure Windows Defender SmartScreen
- This policy setting lets you configure whether to turn on Windows Defender SmartScreen. Windows Defender SmartScreen provides warning messages to help protect your employees from potential phishing scams and malicious software. By default, Windows Defender SmartScreen is turned on.
-
-If you enable this setting, Windows Defender SmartScreen is turned on and employees can't turn it off.
-
-If you disable this setting, Windows Defender SmartScreen is turned off and employees can't turn it on.
-
-If you don't configure this setting, employees can choose whether to use Windows Defender SmartScreen.
- Allow web content on New Tab page
- This policy setting lets you configure what appears when Microsoft Edge opens a new tab. By default, Microsoft Edge opens the New Tab page.
-
-If you enable this setting, Microsoft Edge opens a new tab with the New Tab page.
-
-If you disable this setting, Microsoft Edge opens a new tab with a blank page. If you use this setting, employees can't change it.
-
-If you don't configure this setting, employees can choose how new tabs appears.
- Provision Favorites
- This policy setting allows you to configure a default set of favorites, which will appear for employees. Employees cannot modify, sort, move, export or delete these provisioned favorites.
-
-If you enable this setting, you can set favorite URL's and favorite folders to appear on top of users' favorites list (either in the Hub or Favorites Bar). The user favorites will appear after these provisioned favorites.
-
-Important
-Don't enable both this setting and the Keep favorites in sync between Internet Explorer and Microsoft Edge setting. Enabling both settings stops employees from syncing their favorites between Internet Explorer and Microsoft Edge.
-
-If you disable or don't configure this setting, employees will see the favorites they set in the Hub and Favorites Bar.
- Configure Favorites Bar
- The favorites bar shows your user's links to sites they have added to it. With this policy, you can specify whether to set the favorites bar to always be visible or hidden on any page.
-
-If enabled, favorites bar is always visible on any page, and the favorites bar toggle in Settings sets to On, but disabled preventing your users from making changes. An error message also shows at the top of the Settings pane indicating that your organization manages some settings. The show bar/hide bar option is hidden from the context menu.
-
-If disabled, the favorites bar is hidden, and the favorites bar toggle resets to Off, but disabled preventing your users from making changes. An error message also shows at the top of the Settings pane indicating that your organization manages some settings.
-
-If not configured, the favorites bar is hidden but is visible on the Start and New Tab pages, and the favorites bar toggle in Settings sets to Off but is enabled allowing the user to make changes.
- Configure Home Button
- The Home button loads either the default Start page, the New tab page, or a URL defined in the Set Home Button URL policy.
-
-By default, this policy is disabled or not configured and clicking the home button loads the default Start page.
-
-When enabled, the home button is locked down preventing your users from making changes in Microsoft Edge's UI settings. To let your users change the Microsoft Edge UI settings, enable the Unlock Home Button policy.
-
-If Enabled AND:
-- Show home button & set to Start page is selected, clicking the home button loads the Start page.
-- Show home button & set to New tab page is selected, clicking the home button loads a New tab page.
-- Show home button & set a specific page is selected, clicking the home button loads the URL specified in the Set Home Button URL policy.
-- Hide home button is selected, the home button is hidden in Microsoft Edge.
-
-Default setting: Disabled or not configured
-Related policies:
-- Set Home Button URL
-- Unlock Home Button
- Show home button & set to Start page
- Show home button & set to New tab page
- Show home button & set a specific page
- Hide home button
- Configure Open Microsoft Edge With
- You can configure Microsoft Edge to lock down the Start page, preventing users from changing or customizing it.
-
-If enabled, you can choose one of the following options:
-- Start page: the Start page loads ignoring the Configure Start Pages policy.
-- New tab page: the New tab page loads ignoring the Configure Start Pages policy.
-- Previous pages: all tabs the user had open when Microsoft Edge last closed loads ignoring the Configure Start Pages policy.
-- A specific page or pages: the URL(s) specified with Configure Start Pages policy load(s). If selected, you must specify at least one URL in Configure Start Pages; otherwise, this policy is ignored.
-
-When enabled, and you want to make changes, you must first set the Disable Lockdown of Start Pages to not configured, make the changes to the Configure Open Microsoft Edge With policy, and then enable the Disable Lockdown of Start Pages policy.
-
-If disabled or not configured, and you enable the Disable Lockdown of Start Pages policy, your users can change or customize the Start page.
-
-Default setting: A specific page or pages (default)
-Related policies:
--Disable Lockdown of Start Pages
--Configure Start Pages
- Start page
- New tab page
- Previous pages
- A specific page or pages (default)
- Always show the Books Library in Microsoft Edge
- This policy setting helps you to decide whether to make the Books tab visible, regardless of a device's country or region setting, as configured in the Country or region area of Windows settings.
-
-If you enable this setting, Microsoft Edge shows the Books Library, regardless of the device's country or region.
-
-If you disable or don't configure this setting, Microsoft Edge shows the Books Library only in countries or regions where it's supported.
- Allow extended telemetry for the Books tab
- This policy setting lets you decide how much data to send to Microsoft about the book you're reading from the Books tab in Microsoft Edge.
-
-If you enable this setting, Microsoft Edge sends additional telemetry data, on top of the basic telemetry data, from the Books tab.
-
-If you disable or don't configure this setting, Microsoft Edge only sends basic telemetry data, depending on your device configuration.
- Allow a shared Books folder
- This policy setting lets you decide whether Microsoft Edge stores books from the Books tab to a default, shared folder for Windows.
-
-If you enable this setting, Microsoft Edge automatically downloads book files to a common, shared folder and prevents students and teachers from removing the book from the Books tab. For this to work properly, your students and teachers must be signed in using a school account.
-
-If you disable or don't configure this setting, Microsoft Edge downloads book files to a per-user folder for each student or teacher.
- Allow configuration updates for the Books Library
- This policy setting lets you decide whether Microsoft Edge can automatically update the configuration data for the Books Library.
-
-If you enable (default) or don't configure this setting, Microsoft Edge automatically updates the configuration data for the Books Library.
-
-If you disable this setting, Microsoft Edge won't automatically download updated configuration data for the Books Library.
- Configure cookies
- This setting lets you configure how to work with cookies.
-
-If you enable this setting, you must also decide whether to:
- Allow all cookies (default): Allows all cookies from all websites.
- Block all cookies: Blocks all cookies from all websites.
- Block only 3rd-party cookies: Blocks only cookies from 3rd-party websites.
-
-If you disable or don't configure this setting, all cookies are allowed from all sites.
- Allow all cookies (default)
- Block only 3rd-party cookies
- Block all cookies
- Configure the Enterprise Mode Site List
- This policy setting lets you configure whether to use Enterprise Mode and the Enterprise Mode Site List to address common compatibility problems with legacy apps.
-
-If you enable this setting, Microsoft Edge looks for the Enterprise Mode Site List XML file. This file includes the sites and domains that need to be viewed using Internet Explorer 11 and Enterprise Mode.
-
-If you disable or don't configure this setting, Microsoft Edge won't use the Enterprise Mode Site List XML file. In this case, employees might experience compatibility problems while using legacy apps.
- Allow Extensions
- This setting lets you decide whether employees can load extensions in Microsoft Edge.
-
-If you enable or don't configure this setting, employees can use Microsoft Edge Extensions.
-
-If you disable this setting, employees can't use Microsoft Edge Extensions.
- Prevent turning off required extensions
- You can define a list of extensions in Microsoft Edge that users cannot turn off. You must deploy extensions through any available enterprise deployment channel, such as Microsoft Intune. When you enable this policy, users cannot uninstall extensions from their computer, but they can configure options for extensions defined in this policy, such as allow for InPrivate browsing. Any additional permissions requested by future updates of the extension gets granted automatically.
-
-When you enable this policy, you must provide a semi-colon delimited list of extension package family names (PFNs). For example, adding Microsoft.OneNoteWebClipper_8wekyb3d8bbwe;Microsoft.OfficeOnline_8wekyb3d8bbwe prevents a user from turning off the OneNote Web Clipper and Office Online extension.
-
-When enabled, removing extensions from the list does not uninstall the extension from the user’s computer automatically. To uninstall the extension, use any available enterprise deployment channel.
-
-If you enable the Allow Developer Tools policy, then this policy does not prevent users from debugging and altering the logic on an extension.
-
-If disabled or not configured, extensions defined as part of this policy get ignored.
-
-Default setting: Disabled or not configured
-Related policies: Allow Developer Tools
-Related Documents:
-- Find a package family name (PFN) for per-app VPN (https://docs.microsoft.com/en-us/sccm/protect/deploy-use/find-a-pfn-for-per-app-vpn)
-- How to manage apps you purchased from the Microsoft Store for Business with Microsoft Intune (https://docs.microsoft.com/en-us/intune/windows-store-for-business)
-- How to assign apps to groups with Microsoft Intune (https://docs.microsoft.com/en-us/intune/apps-deploy)
-- Manage apps from the Microsoft Store for Business with System Center Configuration Manager (https://docs.microsoft.com/en-us/sccm/apps/deploy-use/manage-apps-from-the-windows-store-for-business)
-- How to add Windows line-of-business (LOB) apps to Microsoft Intune (https://docs.microsoft.com/en-us/intune/lob-apps-windows)
- Prevent using Localhost IP address for WebRTC
- This policy setting lets you decide whether an employee's LocalHost IP address shows while making calls using the WebRTC protocol.
-
-If you enable this setting, LocalHost IP addresses are hidden while making calls using the WebRTC protocol.
-
-If you disable or don't configure this setting, LocalHost IP addresses are shown while making calls using the WebRTC protocol.
- Disable
- Enable
- Prevent bypassing Windows Defender SmartScreen prompts for sites
- This policy setting lets you decide whether employees can override the Windows Defender SmartScreen warnings about potentially malicious websites.
-
-If you enable this setting, employees can't ignore Windows Defender SmartScreen warnings and they are blocked from continuing to the site.
-
-If you disable or don't configure this setting, employees can ignore Windows Defender SmartScreen warnings and continue to the site.
- Prevent bypassing Windows Defender SmartScreen prompts for files
- This policy setting lets you decide whether employees can override the Windows Defender SmartScreen warnings about downloading unverified files.
-
-If you enable this setting, employees can't ignore Windows Defender SmartScreen warnings and they are blocked from downloading the unverified files.
-
-If you disable or don't configure this setting, employees can ignore Windows Defender SmartScreen warnings and continue the download process.
- Set default search engine
- This policy setting lets you configure the default search engine for your employees. Your employees can change the default search engine at any time.
-
-Important
-This setting can only be used with domain-joined or MDM-enrolled devices. For more info, see the Microsoft browser extension policy (aka.ms/browserpolicy).
-
-If you enable this setting, you can choose a default search engine for your employees. If this setting is enabled, you must also add the default engine to the “Set default search engine” setting, by adding a link to your OpenSearch XML file, including at least the short name and https: URL of the search engine. For more info about creating the OpenSearch XML file, see the Understanding OpenSearch Standards (https://msdn.microsoft.com/en-us/library/dd163546.aspx) topic. Use this format to specify the link you wish to add: <https://fabrikam.com/opensearch.xml>
-
-Note
-If you'd like your employees to use the default Microsoft Edge settings for each market, you can set the string to EDGEDEFAULT. If you'd like your employees to use Microsoft Bing as the default search engine, you can set the string to EDGEBING.
-
-Employees can change the default search engine at any time, unless you disable the "Allow search engine customization" setting, which restricts any changes.
-
-If you disable this setting, the policy-set default search engine is removed. If this is also the current in-use default, the engine changes to the Microsoft Edge specified engine for the market.
-
-If you don't configure this setting, the default search engine is set to the one specified in App settings.
- Configure additional search engines
- This policy setting lets you add up to 5 additional search engines, which can't be removed by your employees, but can be made a personal default engine. This setting doesn't set the default search engine. For that, you must use the "Set default search engine" setting.
-
-Important
-This setting can only be used with domain-joined or MDM-enrolled devices. For more info, see the Microsoft browser extension policy (aka.ms/browserpolicy).
-
-If you enable this setting, you can add up to 5 additional search engines. For each additional engine, you must also add a link to your OpenSearch XML file, including at least the short name and https: URL of the search engine. For more info about creating the OpenSearch XML file, see the Understanding OpenSearch Standards (https://msdn.microsoft.com/en-us/library/dd163546.aspx) topic. Use this format to specify the link(s) you wish to add: <https://fabrikam.com/opensearch.xml><https://www.contoso.com/opensearch.xml>
-
-If you disable this setting, any added search engines are removed from your employee's devices.
-
-If you don't configure this setting, the search engine list is set to what is specified in App settings.
- Configure Favorites
- This policy setting lets you configure the default list of Favorites that appear for your employees. Employees can change their favorites by adding or removing items at any time.
-
-If you enable this setting, you can configure what default Favorites appear for your employees. If this setting is enabled, you must also provide a list of Favorites in the Options section. This list is imported after your policy is deployed.
-
-If you disable or don't configure this setting, employees will see the Favorites that they set in the Favorites hub.
- Set Home Button URL
- The home button can be configured to load a custom URL when your user clicks the home button.
-
-If enabled, or configured, and the Configure Home Button policy is enabled, and the Show home button & set a specific page is selected, a custom URL loads when your user clicks the home button.
-
-Default setting: Blank or not configured
-Related policy: Configure Home Button
- Send all intranet sites to Internet Explorer 11
- This policy setting lets you decide whether your intranet sites should all open using Internet Explorer 11. This setting should only be used if there are known compatibility problems with Microsoft Edge.
-
-If you enable this setting, all intranet sites are automatically opened using Internet Explorer 11.
-
-If you disable or don't configure this setting, all intranet sites are automatically opened using Microsoft Edge.
- Set New Tab page URL
- You can set the default New Tab page URL in Microsoft Edge. Enabling this policy prevents your users from changing the New tab page setting. When enabled and the Allow web content on New Tab page policy is disabled, Microsoft Edge ignores the URL specified in this policy and opens about:blank.
-
-If enabled, you can set the default New Tab page URL.
-
-If disabled or not configured, the default Microsoft Edge new tab page is used.
-
-Default setting: Disabled or not configured
-Related policy: Allow web content on New Tab page
- Show Keep going in Microsoft Edge link
- Hide Keep going in Microsoft Edge link
- Show message when opening sites in Internet Explorer
- You can configure Microsoft Edge to open a site automatically in Internet Explorer 11 and choose to display a notification before the site opens. If you want to display a notification, you must enable Configure the Enterprise Mode Site List or Send all intranets sites to Internet Explorer 11 or both.
-
-If enabled, the notification appears on a new page. If you want users to continue in Microsoft Edge, select the Show Keep going in Microsoft Edge option from the drop-down list under Options.
-
-If disabled or not configured, the default app behavior occurs and no additional page displays.
-
-Default setting: Disabled or not configured
-Related policies:
--Configure the Enterprise Mode Site List
--Send all intranet sites to Internet Explorer 11
- Prevent access to the about:flags page in Microsoft Edge
- This policy settings lets you decide whether employees can access the about:flags page, which is used to change developer settings and to enable experimental features.
-
-If you enable this policy setting, employees can't access the about:flags page.
-
-If you disable or don't configure this setting, employees can access the about:flags page.
- Prevent Microsoft Edge from gathering Live Tile information when pinning a site to Start
- This policy lets you decide whether Microsoft Edge can gather Live Tile metadata from the ieonline.microsoft.com service to provide a better experience while pinning a Live Tile to the Start menu.
-
-If you enable this setting, Microsoft Edge won't gather the Live Tile metadata, providing a minimal experience when a user pins a Live Tile to the Start menu.
-
-If you disable or don't configure this setting, Microsoft Edge gathers the Live Tile metadata, providing a fuller and more complete experience when a user pins a Live Tile to the Start menu.
- Prevent the First Run webpage from opening on Microsoft Edge
-
-This policy setting lets you decide whether employees see Microsoft's First Run webpage when opening Microsoft Edge for the first time.
-
-If you enable this setting, employees won't see the First Run page when opening Microsoft Edge for the first time.
-
-If you disable or don't configure this setting, employees will see the First Run page when opening Microsoft Edge for the first time.
- Keep favorites in sync between Internet Explorer and Microsoft Edge
- This setting lets you decide whether people can sync their favorites between Internet Explorer and Microsoft Edge.
-
-If you enable this setting, employees can sync their favorites between Internet Explorer and Microsoft Edge.
-
-If you disable or don't configure this setting, employees can’t sync their favorites between Internet Explorer and Microsoft Edge.
-
- Unlock Home Button
- By default, when enabling Configure Home Button or Set Home Button URL, the home button is locked down to prevent your users from changing what page loads when clicking the home button. Use this policy to let users change the home button even when Configure Home Button or Set Home Button URL are enabled.
-
-If enabled, the UI settings for the home button are enabled allowing your users to make changes, including hiding and showing the home button as well as configuring a custom URL.
-
-If disabled or not configured, the UI settings for the home button are disabled preventing your users from making changes.
-
-Default setting: Disabled or not configured
-Related policy:
--Configure Home Button
--Set Home Button URL
- Configure the Adobe Flash Click-to-Run setting
-
- If you enable or don’t configure the Adobe Flash Click-to-Run setting, Microsoft Edge will require a user to click the Click-to-Run button, to click the content, or for the site to appear on the auto-allowed list, before loading and running the content.
-
-Sites get onto the auto-allowed list based on user feedback, specifically by how often the content is allowed to load and run.
-
-
- Allow clearing browsing data on exit
- This policy setting allows the automatic clearing of browsing data when Microsoft Edge closes.
-
-If you enable this policy setting, clearing browsing history on exit is turned on.
-
-If you disable or don't configure this policy setting, it can be turned on and configured by the employee in the Clear browsing data options under Settings.
-
-
- Allow Adobe Flash
- This setting lets you decide whether employees can run Adobe Flash in Microsoft Edge.
-
-If you enable or don't configure this setting, employees can use Adobe Flash.
-
-If you disable this setting, employees can't use Adobe Flash.
-
-
-
- Allow Microsoft Compatibility List
- This policy setting lets you decide whether to use the Microsoft Compatibility List (a Microsoft-provided list that helps sites with known compatibility issues to display properly) in Microsoft Edge. By default, the Microsoft Compatibility List is enabled and can be viewed by visiting about:compat.
-
-If you enable or don’t configure this setting, Microsoft Edge periodically downloads the latest version of the list from Microsoft, applying the updates during browser navigation. Visiting any site on the Microsoft Compatibility List prompts the employee to use Internet Explorer 11, where the site is automatically rendered as though it’s in whatever version of IE is necessary for it to appear properly.
-
-If you disable this setting, the Microsoft Compatibility List isn’t used during browser navigation.
-
- Allow Microsoft Edge to start and load the Start and New Tab page at Windows startup and each time Microsoft Edge is closed
- This policy setting lets you decide whether Microsoft Edge can load the Start and New Tab page during Windows sign in and each time Microsoft Edge is closed. By default this setting is to allow preloading.
-
-If you allow preloading, disable, or don’t configure this policy setting, Microsoft Edge loads the Start and New Tab page during Windows sign in and each time Microsoft Edge is closed; minimizing the amount of time required to start up Microsoft Edge and to start a new tab.
-
-If you prevent preloading, Microsoft Edge won’t load the Start or New Tab page during Windows sign in and each time Microsoft Edge is closed.
- Allow tab preloading
- Prevent tab preloading
- Configure collection of browsing data for Desktop Analytics
- You can configure Microsoft Edge to send intranet history only, internet history only, or both to Desktop Analytics for enterprise devices with a configured Commercial ID. If disabled or not configured, Microsoft Edge does not send browsing history data to Desktop Analytics.
-
-Supported versions: Microsoft Edge on Windows 10, version 1809
-Default setting: Disabled or not configured (no data collected or sent)
- Allow sending intranet history only
- Allow sending internet history only
- Allow sending both intranet and internet history
- Do not allow sending intranet or internet history
-
- Allow Microsoft Edge to pre-launch at Windows startup, when the system is idle, and each time Microsoft Edge is closed
- This policy setting lets you decide whether Microsoft Edge can pre-launch during Windows sign in, when the system is idle, and each time Microsoft Edge is closed. By default this setting is to allow pre-launch.
-
-If you allow pre-launch, disable, or don’t configure this policy setting, Microsoft Edge pre-launches during Windows sign in, when the system is idle, and each time Microsoft Edge is closed; minimizing the amount of time required to start up Microsoft Edge.
-
-If you prevent pre-launch, Microsoft Edge won’t pre-launch during Windows sign in, when the system is idle, or each time Microsoft Edge is closed.
- Allow pre-launching
- Prevent pre-launching
-
- Configure kiosk mode
- Configure how Microsoft Edge behaves when it’s running in kiosk mode with assigned access, either as a single app or as one of multiple apps running on the kiosk device. You can control whether Microsoft Edge runs InPrivate full screen, InPrivate multi-tab with limited functionality, or normal Microsoft Edge.
-
-You need to configure Microsoft Edge in assigned access for this policy to take effect; otherwise, these settings are ignored. To learn more about assigned access and kiosk configuration, see “Configure kiosk and shared devices running Windows desktop editions” (https://aka.ms/E489vw).
-
-If enabled and set to 0 (Default or not configured):
-- If it’s a single app, it runs InPrivate full screen for digital signage or interactive displays.
-- If it’s one of many apps, Microsoft Edge runs as normal.
-If enabled and set to 1:
-- If it’s a single app, it runs a limited multi-tab version of InPrivate and is the only app available for public browsing. Users can’t minimize, close, or open windows or customize Microsoft Edge, but can clear browsing data and downloads and restart by clicking “End session.” You can configure Microsoft Edge to restart after a period of inactivity by using the “Configure kiosk reset after idle timeout” policy.
-- If it’s one of many apps, it runs in a limited multi-tab version of InPrivate for public browsing with other apps. Users can minimize, close, and open multiple InPrivate windows, but they can’t customize Microsoft Edge.
- Configure kiosk reset after idle timeout
- You can configure Microsoft Edge to reset to the configured start experience after a specified amount of idle time. The reset timer begins after the last user interaction. Resetting to the configured start experience deletes the current user’s browsing data.
-
-If enabled, you can set the idle time in minutes (0-1440). You must set the Configure kiosk mode policy to 1 and configure Microsoft Edge in assigned access as a single app for this policy to work. Once the idle time meets the time specified, a confirmation message prompts the user to continue, and if no user action, Microsoft Edge resets after 30 seconds.
-
-If you set this policy to 0, Microsoft Edge does not use an idle timer.
-
-If disabled or not configured, the default value is 5 minutes.
-
-If you do not configure Microsoft Edge in assigned access, then this policy does not take effect.
- Suppress the display of Edge Deprecation Notification
- You can configure Microsoft Edge to suppress the display of the notification that informs users that support of this version of Microsoft Edge ended on March 9th, 2021. If enabled, the notification will not show.
-
-If disabled or not configured, the notification will show every time Edge is launched.
-
-
-
-
-
-
-
-
-
-
-
- Configure Open Microsoft Edge With
-
-
- Configure the Home Button
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Enter the name of the favorite in the first column and the URL of the favorite in the other column like Contoso http://www.contoso.com/
-
-
-
-
-
-
-
- Configure Cookies
-
-
- Configure tab preloading
-
-
- Configure pre-launch
-
-
- Configure telemetry collection
-
-
- Configure how Microsoft Edge behaves in kiosk mode.
-
-For single app assigned access:
- - 0 = Full-screen digital signage and interactive display
- - 1 = InPrivate public browsing (limited features)
-
-For multi-app assigned access:
- - 0 = Normal Microsoft Edge running in assigned access
- - 1 = InPrivate public browsing
-
-
-
-
- Specify the time in minutes from the last user activity before Microsoft Edge kiosk resets, you can choose:
- - 0 to disable the idle timer
- - 1-1440 minutes of inactivity since the last user interaction
-
-
-
-
- Show Keep going in Microsoft Edge link
-
-
-
-
diff --git a/policy_templates/en-US/MobilePCMobilityCenter.adml b/policy_templates/en-US/MobilePCMobilityCenter.adml
deleted file mode 100644
index e0a0597..0000000
--- a/policy_templates/en-US/MobilePCMobilityCenter.adml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Windows Mobility Center
- Turn off Windows Mobility Center
- This policy setting turns off Windows Mobility Center.
-
-If you enable this policy setting, the user is unable to invoke Windows Mobility Center. The Windows Mobility Center UI is removed from all shell entry points and the .exe file does not launch it.
-
-If you disable this policy setting, the user is able to invoke Windows Mobility Center and the .exe file launches it.
-
-If you do not configure this policy setting, Windows Mobility Center is on by default.
-
-
-
diff --git a/policy_templates/en-US/MobilePCPresentationSettings.adml b/policy_templates/en-US/MobilePCPresentationSettings.adml
deleted file mode 100644
index 862456e..0000000
--- a/policy_templates/en-US/MobilePCPresentationSettings.adml
+++ /dev/null
@@ -1,21 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Presentation Settings
- Turn off Windows presentation settings
- This policy setting turns off Windows presentation settings.
-
-If you enable this policy setting, Windows presentation settings cannot be invoked.
-
-If you disable this policy setting, Windows presentation settings can be invoked. The presentation settings icon will be displayed in the notification area. This will give users a quick and easy way to configure their system settings before a presentation to block system notifications and screen blanking, adjust speaker volume, and apply a custom background image.
-
-Note: Users will be able to customize their system settings for presentations in Windows Mobility Center.
-
-If you do not configure this policy setting, Windows presentation settings can be invoked.
-
-
-
diff --git a/policy_templates/en-US/Msi-FileRecovery.adml b/policy_templates/en-US/Msi-FileRecovery.adml
deleted file mode 100644
index 6c85cba..0000000
--- a/policy_templates/en-US/Msi-FileRecovery.adml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- MSI Corrupted File Recovery
- Configure MSI Corrupted File Recovery behavior
- This policy setting allows you to configure the recovery behavior for corrupted MSI files to one of three states:
-
-Prompt for Resolution: Detection, troubleshooting, and recovery of corrupted MSI applications will be turned on. Windows will prompt the user with a dialog box when application reinstallation is required. This is the default recovery behavior on Windows client.
-
-Silent: Detection, troubleshooting, and notification of MSI application to reinstall will occur with no UI. Windows will log an event when corruption is determined and will suggest the application that should be re-installed. This behavior is recommended for headless operation and is the default recovery behavior on Windows server.
-
-Troubleshooting Only: Detection and verification of file corruption will be performed without UI. Recovery is not attempted.
-
-If you enable this policy setting, the recovery behavior for corrupted files is set to either the Prompt For Resolution (default on Windows client), Silent (default on Windows server), or Troubleshooting Only.
-
-If you disable this policy setting, the troubleshooting and recovery behavior for corrupted files will be disabled. No troubleshooting or resolution will be attempted.
-
-If you do not configure this policy setting, the recovery behavior for corrupted files will be set to the default recovery behavior.
-
-No system or service restarts are required for changes to this policy setting to take immediate effect after a Group Policy refresh.
-
-Note: This policy setting will take effect only when the Diagnostic Policy Service (DPS) is in the running state. When the service is stopped or disabled, system file recovery will not be attempted. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
- Prompt for Resolution
- Silent
- Troubleshooting Only
-
-
-
- Scenario Execution Level
-
-
-
-
diff --git a/policy_templates/en-US/Multitasking.adml b/policy_templates/en-US/Multitasking.adml
deleted file mode 100644
index f3dd500..0000000
--- a/policy_templates/en-US/Multitasking.adml
+++ /dev/null
@@ -1,27 +0,0 @@
-
-
- Multitasking
- Manages the Windows Multitasking options
-
-
- Multitasking
- Manages the Windows Multitasking options
- Configure the inclusion of app tabs into Alt-Tab
- This setting controls the inclusion of app tabs into Alt+Tab.
-
-This can be set to show the most recent 3, 5 or 20 tabs, or no tabs from apps.
-
-If this is set to show "Open windows only", the whole feature will be disabled.
-
- Open windows and 20 most recent tabs in apps
- Open windows and 5 most recent tabs in apps
- Open windows and 3 most recent tabs in apps
- Open windows only
-
-
-
- Pressing Alt + Tab shows
-
-
-
-
diff --git a/policy_templates/en-US/NCSI.adml b/policy_templates/en-US/NCSI.adml
deleted file mode 100644
index c567b57..0000000
--- a/policy_templates/en-US/NCSI.adml
+++ /dev/null
@@ -1,84 +0,0 @@
-
-
-
- Network Connectivity Status Indicator Group Policy Settings
- Network Connectivity Status Indicator Group Policy Settings
-
-
- Network Connectivity Status Indicator
- Specify corporate Website probe URL
- This policy setting enables you to specify the URL of the corporate website, against which an active probe is performed.
- Specify corporate DNS probe host name
- This policy setting enables you to specify the host name of a computer known to be on the corporate network. Successful resolution of this host name to the expected address indicates corporate connectivity.
- Specify corporate DNS probe host address
- This policy setting enables you to specify the expected address of the host name used for the DNS probe. Successful resolution of the host name to this address indicates corporate connectivity.
- Specify corporate site prefix list
- This policy setting enables you to specify the list of IPv6 corporate site prefixes to monitor for corporate connectivity. Reachability of addresses with any of these prefixes indicates corporate connectivity.
- Specify domain location determination URL
- This policy setting enables you to specify the HTTPS URL of the corporate website that clients use to determine the current domain location (i.e. whether the computer is inside or outside the corporate network). Reachability of the URL destination indicates that the client location is inside corporate network; otherwise it is outside the network.
- Specify passive polling
- This Policy setting enables you to specify passive polling behavior. NCSI polls various measurements throughout the network stack on a frequent interval to determine if network connectivity has been lost. Use the options to control the passive polling behavior.
- Specify global DNS
- This policy setting enables you to specify DNS binding behavior. NCSI by default will restrict DNS lookups to the interface it is currently probing on. If you enable this setting, NCSI will allow the DNS lookups to happen on any interface.
-
-
-
-
-
-
- Specify the URL of the corporate website to
- use to probe for corporate connectivity.
- Example:
- http://ncsi.corp.microsoft.com/
-
-
-
-
-
- Specify a corporate host name to resolve
- to probe for corporate connectivity.
- Example:
- ncsi.corp.microsoft.com
-
-
-
-
-
- Specify the expected DNS address for the
- corporate host name to probe.
- Example:
- 2001:4898:28:3:38a1:c31:7b3d:bf0
-
-
-
-
-
- Specify the list of corporate IPv6 site prefixes
- to check for reachability to detect corporate
- connectivity.
- Syntax:
- The list should be comma-separated with no
- extra whitespace.
- Example:
- fe80::/9,fe81::/9
-
-
-
-
-
- Specify the HTTPS URL of the corporate website to
- use to determine inside or outside domain location.
- Example:
- https://nid.corp.microsoft.com/
-
-
- The following checkbox disables the passive polling mechanism in NCSI. This can improve CPU workload on servers or other machines whose network connectivity is static.
- Disable passive polling
-
-
- The following checkbox disables interface binding when doing DNS lookups in NCSI. This can enable NCSI to work better with special network configurations, like a DNS server running on localhost.
- Use global DNS
-
-
-
-
diff --git a/policy_templates/en-US/Netlogon.adml b/policy_templates/en-US/Netlogon.adml
deleted file mode 100644
index d359cfb..0000000
--- a/policy_templates/en-US/Netlogon.adml
+++ /dev/null
@@ -1,436 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Net Logon
- Use DNS name resolution with a single-label domain name instead of NetBIOS name resolution to locate the DC
- This policy setting specifies whether the computers to which this setting is applied attempt DNS name resolution of a single-label domain names.
-
-By default, the behavior specified in the AllowDnsSuffixSearch is used. If the AllowDnsSuffixSearch policy is disabled, then NetBIOS name resolution is used exclusively, to locate a domain controller hosting an Active Directory domain specified with a single-label name.
-
-If you enable this policy setting, computers to which this policy is applied will attempt to locate a domain controller hosting an Active Directory domain specified with a single-label name using DNS name resolution.
-
-If you disable this policy setting, computers to which this setting is applied will use the AllowDnsSuffixSearch policy, if it is not disabled or perform NetBIOS name resolution otherwise, to attempt to locate a domain controller that hosts an Active Directory domain specified with a single-label name. the computers will not the DNS name resolution in this case, unless the computer is searching for a domain with a single label DNS name that exists in the Active Directory forest to which this computer is joined.
-
-If you do not configure this policy setting, it is not applied to any computers, and computers use their local configuration.
- Use DNS name resolution when a single-label domain name is used, by appending different registered DNS suffixes, if the AllowSingleLabelDnsDomain setting is not enabled.
- This policy setting specifies whether the computers to which this setting is applied attemps DNS name resolution of single-lablel domain names, by appending different registered DNS suffixes, and uses NetBIOS name resolution only if DNS name resolution fails. This policy, including the specified default behavior, is not used if the AllowSingleLabelDnsDomain policy setting is enabled.
-
-By default, when no setting is specified for this policy, the behavior is the same as explicitly enabling this policy, unless the AllowSingleLabelDnsDomain policy setting is enabled.
-
-If you enable this policy setting, when the AllowSingleLabelDnsDomain policy is not enabled, computers to which this policy is applied, will locate a domain controller hosting an Active Directory domain specified with a single-label name, by appending different registered DNS suffixes to perform DNS name resolution. The single-label name is not used without appending DNS suffixes unless the computer is joined to a domain that has a single-label DNS name in the Active Directory forest. NetBIOS name resolution is performed on the single-label name only, in the event that DNS resolution fails.
-
-If you disable this policy setting, when the AllowSingleLabelDnsDomain policy is not enabled, computers to which this policy is applied, will only use NetBIOS name resolution to attempt to locate a domain controller hosting an Active Directory domain specified with a single-label name. The computers will not attempt DNS name resolution in this case, unless the computer is searching for a domain with a single label DNS name to which this computer is joined, in the Active Directory forest.
-
- Use automated site coverage by the DC Locator DNS SRV Records
- This policy setting determines whether domain controllers (DC) will dynamically register DC Locator site-specific SRV records for the closest sites where no DC for the same domain exists (or no Global Catalog for the same forest exists). These DNS records are dynamically registered by the Net Logon service, and they are used to locate the DC.
-
-If you enable this policy setting, the DCs to which this setting is applied dynamically register DC Locator site-specific DNS SRV records for the closest sites where no DC for the same domain, or no Global Catalog for the same forest, exists.
-
-If you disable this policy setting, the DCs will not register site-specific DC Locator DNS SRV records for any other sites but their own.
-
-If you do not configure this policy setting, it is not applied to any DCs, and DCs use their local configuration.
- Contact PDC on logon failure
- This policy setting defines whether a domain controller (DC) should attempt to verify the password provided by a client with the PDC emulator if the DC failed to validate the password.
-
-Contacting the PDC emulator is useful in case the client’s password was recently changed and did not propagate to the DC yet. Users may want to disable this feature if the PDC emulator is located over a slow WAN connection.
-
-If you enable this policy setting, the DCs to which this policy setting applies will attempt to verify a password with the PDC emulator if the DC fails to validate the password.
-
-If you disable this policy setting, the DCs will not attempt to verify any passwords with the PDC emulator.
-
-If you do not configure this policy setting, it is not applied to any DCs.
- Use initial DC discovery retry setting for background callers
- This policy setting determines the amount of time (in seconds) to wait before the first retry for applications that perform periodic searches for domain controllers (DC) that are unable to find a DC.
-
-The default value for this setting is 10 minutes (10*60). The maximum value for this setting is 49 days (0x49*24*60*60=4233600). The minimum value for this setting is 0.
-
-This setting is relevant only to those callers of DsGetDcName that have specified the DS_BACKGROUND_ONLY flag.
-
-If the value of this setting is less than the value specified in the NegativeCachePeriod subkey, the value in the NegativeCachePeriod subkey is used.
-
-Warning: If the value for this setting is too large, a client will not attempt to find any DCs that were initially unavailable. If the value set in this setting is very small and the DC is not available, the traffic caused by periodic DC discoveries may be excessive.
- Use maximum DC discovery retry interval setting for background callers
- This policy setting determines the maximum retry interval allowed when applications performing periodic searches for Domain Controllers (DCs) are unable to find a DC.
-
-For example, the retry intervals may be set at 10 minutes, then 20 minutes and then 40 minutes, but when the interval reaches the value set in this setting, that value becomes the retry interval for all subsequent retries until the value set in Final DC Discovery Retry Setting is reached.
-
-The default value for this setting is 60 minutes (60*60). The maximum value for this setting is 49 days (0x49*24*60*60=4233600). The minimum value for this setting is 0.
-
-If the value for this setting is smaller than the value specified for the Initial DC Discovery Retry Setting, the Initial DC Discovery Retry Setting is used.
-
-Warning: If the value for this setting is too large, a client may take very long periods to try to find a DC.
-
-If the value for this setting is too small and the DC is not available, the frequent retries may produce excessive network traffic.
- Use final DC discovery retry setting for background callers
- This policy setting determines when retries are no longer allowed for applications that perform periodic searches for domain controllers (DC) are unable to find a DC. For example, retires may be set to occur according to the Use maximum DC discovery retry interval policy setting, but when the value set in this policy setting is reached, no more retries occur. If a value for this policy setting is smaller than the value in the Use maximum DC discovery retry interval policy setting, the value for Use maximum DC discovery retry interval policy setting is used.
-
-The default value for this setting is to not quit retrying (0). The maximum value for this setting is 49 days (0x49*24*60*60=4233600). The minimum value for this setting is 0.
-
-Warning: If the value for this setting is too small, a client will stop trying to find a DC too soon.
- Use positive periodic DC cache refresh for background callers
- This policy setting determines when a successful DC cache entry is refreshed. This policy setting is applied to caller programs that periodically attempt to locate DCs, and it is applied before returning the DC information to the caller program. The default value for this setting is infinite (4294967200). The maximum value for this setting is (4294967200), while the maximum that is not treated as infinity is 49 days (49*24*60*60=4233600). Any larger value is treated as infinity. The minimum value for this setting is to always refresh (0).
- DC Locator DNS Records
- Specify log file debug output level
- This policy setting specifies the level of debug output for the Net Logon service.
-
-The Net Logon service outputs debug information to the log file netlogon.log in the directory %windir%\debug. By default, no debug information is logged.
-
-If you enable this policy setting and specify a non-zero value, debug information will be logged to the file. Higher values result in more verbose logging; the value of 536936447 is commonly used as an optimal setting.
-
-If you specify zero for this policy setting, the default behavior occurs as described above.
-
-If you disable this policy setting or do not configure it, the default behavior occurs as described above.
- Specify DC Locator DNS records not registered by the DCs
- This policy setting determines which DC Locator DNS records are not registered by the Net Logon service.
-
-If you enable this policy setting, select Enabled and specify a list of space-delimited mnemonics (instructions) for the DC Locator DNS records that will not be registered by the DCs to which this setting is applied.
-
-Select the mnemonics from the following list:
-
-Mnemonic Type DNS Record
-
-LdapIpAddress A <DnsDomainName>
-Ldap SRV _ldap._tcp.<DnsDomainName>
-LdapAtSite SRV _ldap._tcp.<SiteName>._sites.<DnsDomainName>
-Pdc SRV _ldap._tcp.pdc._msdcs.<DnsDomainName>
-Gc SRV _ldap._tcp.gc._msdcs.<DnsForestName>
-GcAtSite SRV _ldap._tcp.<SiteName>._sites.gc._msdcs.<DnsForestName>
-DcByGuid SRV _ldap._tcp.<DomainGuid>.domains._msdcs.<DnsForestName>
-GcIpAddress A gc._msdcs.<DnsForestName>
-DsaCname CNAME <DsaGuid>._msdcs.<DnsForestName>
-Kdc SRV _kerberos._tcp.dc._msdcs.<DnsDomainName>
-KdcAtSite SRV _kerberos._tcp.<SiteName>._sites.dc._msdcs.<DnsDomainName>
-Dc SRV _ldap._tcp.dc._msdcs.<DnsDomainName>
-DcAtSite SRV _ldap._tcp.<SiteName>._sites.dc._msdcs.<DnsDomainName>
-Rfc1510Kdc SRV _kerberos._tcp.<DnsDomainName>
-Rfc1510KdcAtSite SRV _kerberos._tcp.<SiteName>._sites.<DnsDomainName>
-GenericGc SRV _gc._tcp.<DnsForestName>
-GenericGcAtSite SRV _gc._tcp.<SiteName>._sites.<DnsForestName>
-Rfc1510UdpKdc SRV _kerberos._udp.<DnsDomainName>
-Rfc1510Kpwd SRV _kpasswd._tcp.<DnsDomainName>
-Rfc1510UdpKpwd SRV _kpasswd._udp.<DnsDomainName>
-
-If you disable this policy setting, DCs configured to perform dynamic registration of DC Locator DNS records register all DC Locator DNS resource records.
-
-If you do not configure this policy setting, DCs use their local configuration.
- Specify Refresh Interval of the DC Locator DNS records
- This policy setting specifies the Refresh Interval of the DC Locator DNS resource records for DCs to which this setting is applied. These DNS records are dynamically registered by the Net Logon service and are used by the DC Locator algorithm to locate the DC. This setting may be applied only to DCs using dynamic update.
-
-DCs configured to perform dynamic registration of the DC Locator DNS resource records periodically reregister their records with DNS servers, even if their records’ data has not changed. If authoritative DNS servers are configured to perform scavenging of the stale records, this reregistration is required to instruct the DNS servers configured to automatically remove (scavenge) stale records that these records are current and should be preserved in the database.
-
-Warning: If the DNS resource records are registered in zones with scavenging enabled, the value of this setting should never be longer than the Refresh Interval configured for these zones. Setting the Refresh Interval of the DC Locator DNS records to longer than the Refresh Interval of the DNS zones may result in the undesired deletion of DNS resource records.
-
-To specify the Refresh Interval of the DC records, click Enabled, and then enter a value larger than 1800. This value specifies the Refresh Interval of the DC records in seconds (for example, the value 3600 is 60 minutes).
-
-If you do not configure this policy setting, it is not applied to any DCs, and DCs use their local configuration.
- Set TTL in the DC Locator DNS Records
- This policy setting specifies the value for the Time-To-Live (TTL) field in SRV resource records that are registered by the Net Logon service. These DNS records are dynamically registered, and they are used to locate the domain controller (DC).
-
-To specify the TTL for DC Locator DNS records, click Enabled, and then enter a value in seconds (for example, the value "900" is 15 minutes).
-
-If you do not configure this policy setting, it is not applied to any DCs, and DCs use their local configuration.
- Specify expected dial-up delay on logon
- This policy setting specifies the additional time for the computer to wait for the domain controller’s (DC) response when logging on to the network.
-
-To specify the expected dial-up delay at logon, click Enabled, and then enter the desired value in seconds (for example, the value "60" is 1 minute).
-
-If you do not configure this policy setting, it is not applied to any computers, and computers use their local configuration.
- Specify sites covered by the GC Locator DNS SRV Records
- This policy setting specifies the sites for which the global catalogs (GC) should register site-specific GC locator DNS SRV resource records. These records are registered in addition to the site-specific SRV records registered for the site where the GC resides, and records registered by a GC configured to register GC Locator DNS SRV records for those sites without a GC that are closest to it.
-
-The GC Locator DNS records and the site-specific SRV records are dynamically registered by the Net Logon service, and they are used to locate the GC. An Active Directory site is one or more well-connected TCP/IP subnets that allow administrators to configure Active Directory access and replication. A GC is a domain controller that contains a partial replica of every domain in Active Directory.
-
-To specify the sites covered by the GC Locator DNS SRV records, click Enabled, and enter the sites' names in a space-delimited format.
-
-If you do not configure this policy setting, it is not applied to any GCs, and GCs use their local configuration.
- Set Priority in the DC Locator DNS SRV records
- This policy setting specifies the Priority field in the SRV resource records registered by domain controllers (DC) to which this setting is applied. These DNS records are dynamically registered by the Net Logon service and are used to locate the DC.
-
-The Priority field in the SRV record sets the preference for target hosts (specified in the SRV record’s Target field). DNS clients that query for SRV resource records attempt to contact the first reachable host with the lowest priority number listed.
-
-To specify the Priority in the DC Locator DNS SRV resource records, click Enabled, and then enter a value. The range of values is from 0 to 65535.
-
-If you do not configure this policy setting, it is not applied to any DCs, and DCs use their local configuration.
- Set Weight in the DC Locator DNS SRV records
- This policy setting specifies the Weight field in the SRV resource records registered by the domain controllers (DC) to which this setting is applied. These DNS records are dynamically registered by the Net Logon service, and they are used to locate the DC.
-
-The Weight field in the SRV record can be used in addition to the Priority value to provide a load-balancing mechanism where multiple servers are specified in the SRV records Target field and are all set to the same priority. The probability with which the DNS client randomly selects the target host to be contacted is proportional to the Weight field value in the SRV record.
-
-To specify the Weight in the DC Locator DNS SRV records, click Enabled, and then enter a value. The range of values is from 0 to 65535.
-
-If you do not configure this policy setting, it is not applied to any DCs, and DCs use their local configuration.
- Specify maximum log file size
- This policy setting specifies the maximum size in bytes of the log file netlogon.log in the directory %windir%\debug when logging is enabled.
-
-By default, the maximum size of the log file is 20MB. If you enable this policy setting, the maximum size of the log file is set to the specified size. Once this size is reached the log file is saved to netlogon.bak and netlogon.log is truncated. A reasonable value based on available storage should be specified.
-
-If you disable or do not configure this policy setting, the default behavior occurs as indicated above.
- Specify sites covered by the application directory partition DC Locator DNS SRV records
- This policy setting specifies the sites for which the domain controllers (DC) that host the application directory partition should register the site-specific, application directory partition-specific DC Locator DNS SRV resource records. These records are registered in addition to the site-specific SRV records registered for the site where the DC resides, and records registered by a DC configured to register DC Locator DNS SRV records for those sites without a DC that are closest to it.
-
-The application directory partition DC Locator DNS records and the site-specific SRV records are dynamically registered by the Net Logon service, and they are used to locate the application directory partition-specific DC. An Active Directory site is one or more well-connected TCP/IP subnets that allow administrators to configure Active Directory access and replication.
-
-To specify the sites covered by the DC Locator application directory partition-specific DNS SRV records, click Enabled, and then enter the site names in a space-delimited format.
-
-If you do not configure this policy setting, it is not applied to any DCs, and DCs use their local configuration.
- Specify negative DC Discovery cache setting
- This policy setting specifies the amount of time (in seconds) the DC locator remembers that a domain controller (DC) could not be found in a domain. When a subsequent attempt to locate the DC occurs within the time set in this setting, DC Discovery immediately fails, without attempting to find the DC.
-
-The default value for this setting is 45 seconds. The maximum value for this setting is 7 days (7*24*60*60). The minimum value for this setting is 0.
-
-Warning: If the value for this setting is too large, a client will not attempt to find any DCs that were initially unavailable. If the value for this setting is too small, clients will attempt to find DCs even when none are available.
- Set Netlogon share compatibility
- This policy setting controls whether or not the Netlogon share created by the Net Logon service on a domain controller (DC) should support compatibility in file sharing semantics with earlier applications.
-
-If you enable this policy setting, the Netlogon share will honor file sharing semantics that grant requests for exclusive read access to files on the share even when the caller has only read permission.
-
-If you disable or do not configure this policy setting, the Netlogon share will grant shared read access to files on the share when exclusive access is requested and the caller has only read permission.
-
-By default, the Netlogon share will grant shared read access to files on the share when exclusive access is requested.
-
-Note: The Netlogon share is a share created by the Net Logon service for use by client machines in the domain. The default behavior of the Netlogon share ensures that no application with only read permission to files on the Netlogon share can lock the files by requesting exclusive read access, which might prevent Group Policy settings from being updated on clients in the domain. When this setting is enabled, an application that relies on the ability to lock files on the Netlogon share with only read permission will be able to deny Group Policy clients from reading the files, and in general the availability of the Netlogon share on the domain will be decreased.
-
-If you enable this policy setting, domain administrators should ensure that the only applications using the exclusive read capability in the domain are those approved by the administrator.
- Specify positive periodic DC Cache refresh for non-background callers
- This policy setting determines when a successful DC cache entry is refreshed. This policy setting is applied to caller programs that do not periodically attempt to locate DCs, and it is applied before the returning the DC information to the caller program. This policy setting is relevant to only those callers of DsGetDcName that have not specified the DS_BACKGROUND_ONLY flag.
-
-The default value for this setting is 30 minutes (1800). The maximum value for this setting is (4294967200), while the maximum that is not treated as infinity is 49 days (49*24*60*60=4233600). Any larger value will be treated as infinity. The minimum value for this setting is to always refresh (0).
- Set scavenge interval
- This policy setting determines the interval at which Netlogon performs the following scavenging operations:
-
-- Checks if a password on a secure channel needs to be modified, and modifies it if necessary.
-
-- On the domain controllers (DC), discovers a DC that has not been discovered.
-
-- On the PDC, attempts to add the <DomainName>[1B] NetBIOS name if it hasn’t already been successfully added.
-
-None of these operations are critical. 15 minutes is optimal in all but extreme cases. For instance, if a DC is separated from a trusted domain by an expensive (e.g., ISDN) line, this parameter might be adjusted upward to avoid frequent automatic discovery of DCs in a trusted domain.
-
-To enable the setting, click Enabled, and then specify the interval in seconds.
- Specify sites covered by the DC Locator DNS SRV records
- This policy setting specifies the sites for which the domain controllers (DC) register the site-specific DC Locator DNS SRV resource records. These records are registered in addition to the site-specific SRV records registered for the site where the DC resides, and records registered by a DC configured to register DC Locator DNS SRV records for those sites without a DC that are closest to it.
-
-The DC Locator DNS records are dynamically registered by the Net Logon service, and they are used to locate the DC. An Active Directory site is one or more well-connected TCP/IP subnets that allow administrators to configure Active Directory access and replication.
-
-To specify the sites covered by the DC Locator DNS SRV records, click Enabled, and then enter the sites names in a space-delimited format.
-
-If you do not configure this policy setting, it is not applied to any DCs, and DCs use their local configuration.
- Specify site name
- This policy setting specifies the Active Directory site to which computers belong.
-
-An Active Directory site is one or more well-connected TCP/IP subnets that allow administrators to configure Active Directory access and replication.
-
-To specify the site name for this setting, click Enabled, and then enter the site name. When the site to which a computer belongs is not specified, the computer automatically discovers its site from Active Directory.
-
-If you do not configure this policy setting, it is not applied to any computers, and computers use their local configuration.
- Set SYSVOL share compatibility
- This policy setting controls whether or not the SYSVOL share created by the Net Logon service on a domain controller (DC) should support compatibility in file sharing semantics with earlier applications.
-
-When this setting is enabled, the SYSVOL share will honor file sharing semantics that grant requests for exclusive read access to files on the share even when the caller has only read permission.
-
-When this setting is disabled or not configured, the SYSVOL share will grant shared read access to files on the share when exclusive access is requested and the caller has only read permission.
-
-By default, the SYSVOL share will grant shared read access to files on the share when exclusive access is requested.
-
-Note: The SYSVOL share is a share created by the Net Logon service for use by Group Policy clients in the domain. The default behavior of the SYSVOL share ensures that no application with only read permission to files on the sysvol share can lock the files by requesting exclusive read access, which might prevent Group Policy settings from being updated on clients in the domain. When this setting is enabled, an application that relies on the ability to lock files on the SYSVOL share with only read permission will be able to deny Group Policy clients from reading the files, and in general the availability of the SYSVOL share on the domain will be decreased.
-
-If you enable this policy setting, domain administrators should ensure that the only applications using the exclusive read capability in the domain are those approved by the administrator.
- Specify dynamic registration of the DC Locator DNS Records
- This policy setting determines if dynamic registration of the domain controller (DC) locator DNS resource records is enabled. These DNS records are dynamically registered by the Net Logon service and are used by the Locator algorithm to locate the DC.
-
-If you enable this policy setting, DCs to which this setting is applied dynamically register DC Locator DNS resource records through dynamic DNS update-enabled network connections.
-
-If you disable this policy setting, DCs will not register DC Locator DNS resource records.
-
-If you do not configure this policy setting, it is not applied to any DCs, and DCs use their local configuration.
- Try Next Closest Site
- This policy setting enables DC Locator to attempt to locate a DC in the nearest site based on the site link cost if a DC in same the site is not found. In scenarios with multiple sites, failing over to the try next closest site during DC Location streamlines network traffic more effectively.
-
-The DC Locator service is used by clients to find domain controllers for their Active Directory domain. The default behavior for DC Locator is to find a DC in the same site. If none are found in the same site, a DC in another site, which might be several site-hops away, could be returned by DC Locator. Site proximity between two sites is determined by the total site-link cost between them. A site is closer if it has a lower site link cost than another site with a higher site link cost.
-
-If you enable this policy setting, Try Next Closest Site DC Location will be turned on for the computer.
-
-If you disable this policy setting, Try Next Closest Site DC Location will not be used by default for the computer. However, if a DC Locator call is made using the DS_TRY_NEXTCLOSEST_SITE flag explicitly, the Try Next Closest Site behavior is honored.
-
-If you do not configure this policy setting, Try Next Closest Site DC Location will not be used by default for the machine. If the DS_TRY_NEXTCLOSEST_SITE flag is used explicitly, the Next Closest Site behavior will be used.
- Force Rediscovery Interval
- This policy setting determines the interval for when a Force Rediscovery is carried out by DC Locator.
-
-The Domain Controller Locator (DC Locator) service is used by clients to find domain controllers for their Active Directory domain. When DC Locator finds a domain controller, it caches domain controllers to improve the efficiency of the location algorithm. As long as the cached domain controller meets the requirements and is running, DC Locator will continue to return it. If a new domain controller is introduced, existing clients will only discover it when a Force Rediscovery is carried out by DC Locator. To adapt to changes in network conditions DC Locator will by default carry out a Force Rediscovery according to a specific time interval and maintain efficient load-balancing of clients across all available domain controllers in all domains or forests. The default time interval for Force Rediscovery by DC Locator is 12 hours. Force Rediscovery can also be triggered if a call to DC Locator uses the DS_FORCE_REDISCOVERY flag. Rediscovery resets the timer on the cached domain controller entries.
-
-If you enable this policy setting, DC Locator on the machine will carry out Force Rediscovery periodically according to the configured time interval. The minimum time interval is 3600 seconds (1 hour) to avoid excessive network traffic from rediscovery. The maximum allowed time interval is 4294967200 seconds, while any value greater than 4294967 seconds (~49 days) will be treated as infinity.
-
-If you disable this policy setting, Force Rediscovery will be used by default for the machine at every 12 hour interval.
-
-If you do not configure this policy setting, Force Rediscovery will be used by default for the machine at every 12 hour interval, unless the local machine setting in the registry is a different value.
- Return domain controller address type
- This policy setting detremines the type of IP address that is returned for a domain controller. The DC Locator APIs return the IP address of the DC with the other parts of information. Before the support of IPv6, the returned DC IP address was IPv4. But with the support of IPv6, the DC Locator APIs can return IPv6 DC address. The returned IPv6 DC address may not be correctly handled by some of the existing applications. So this policy is provided to support such scenarios.
-
-By default, DC Locator APIs can return IPv4/IPv6 DC address. But if some applications are broken due to the returned IPv6 DC address, this policy can be used to disable the default behavior and enforce to return only IPv4 DC address. Once applications are fixed, this policy can be used to enable the default behavior.
-
-If you enable this policy setting, DC Locator APIs can return IPv4/IPv6 DC address. This is the default behavior of the DC Locator.
-
-If you disable this policy setting, DC Locator APIs will ONLY return IPv4 DC address if any. So if the domain controller supports both IPv4 and IPv6 addresses, DC Locator APIs will return IPv4 address. But if the domain controller supports only IPv6 address, then DC Locator APIs will fail.
-
-If you do not configure this policy setting, DC Locator APIs can return IPv4/IPv6 DC address. This is the default behavior of the DC Locator.
- Allow cryptography algorithms compatible with Windows NT 4.0
- This policy setting controls whether the Net Logon service will allow the use of older cryptography algorithms that are used in Windows NT 4.0. The cryptography algorithms used in Windows NT 4.0 and earlier are not as secure as newer algorithms used in Windows 2000 or later, including this version of Windows.
-
-By default, Net Logon will not allow the older cryptography algorithms to be used and will not include them in the negotiation of cryptography algorithms. Therefore, computers running Windows NT 4.0 will not be able to establish a connection to this domain controller.
-
-If you enable this policy setting, Net Logon will allow the negotiation and use of older cryptography algorithms compatible with Windows NT 4.0. However, using the older algorithms represents a potential security risk.
-
-If you disable this policy setting, Net Logon will not allow the negotiation and use of older cryptography algorithms.
-
-If you do not configure this policy setting, Net Logon will not allow the negotiation and use of older cryptography algorithms.
- Do not process incoming mailslot messages used for domain controller location based on NetBIOS domain names
- This policy setting allows you to control the processing of incoming mailslot messages by a local domain controller (DC).
-
-Note: To locate a remote DC based on its NetBIOS (single-label) domain name, DC Locator first gets the list of DCs from a WINS server that is configured in its local client settings. DC Locator then sends a mailslot message to each remote DC to get more information. DC location succeeds only if a remote DC responds to the mailslot message.
-
-This policy setting is recommended to reduce the attack surface on a DC, and can be used in an environment without WINS, in an IPv6-only environment, and whenever DC location based on a NetBIOS domain name is not required. This policy setting does not affect DC location based on DNS names.
-
-If you enable this policy setting, this DC does not process incoming mailslot messages that are used for NetBIOS domain name based DC location.
-
-If you disable or do not configure this policy setting, this DC processes incoming mailslot messages. This is the default behavior of DC Locator.
- Do not use NetBIOS-based discovery for domain controller location when DNS-based discovery fails
- This policy setting allows you to control the domain controller (DC) location algorithm. By default, the DC location algorithm prefers DNS-based discovery if the DNS domain name is known. If DNS-based discovery fails and the NetBIOS domain name is known, the algorithm then uses NetBIOS-based discovery as a fallback mechanism.
-
-NetBIOS-based discovery uses a WINS server and mailslot messages but does not use site information. Hence it does not ensure that clients will discover the closest DC. It also allows a hub-site client to discover a branch-site DC even if the branch-site DC only registers site-specific DNS records (as recommended). For these reasons, NetBIOS-based discovery is not recommended.
-
-Note that this policy setting does not affect NetBIOS-based discovery for DC location if only the NetBIOS domain name is known.
-
-If you enable or do not configure this policy setting, the DC location algorithm does not use NetBIOS-based discovery as a fallback mechanism when DNS-based discovery fails. This is the default behavior.
-
-If you disable this policy setting, the DC location algorithm can use NetBIOS-based discovery as a fallback mechanism when DNS based discovery fails.
-
- Specify address lookup behavior for DC locator ping
- This policy setting configures how a domain controller (DC) behaves when responding to a client whose IP address does not map to any configured site.
-
-Domain controllers use the client IP address during a DC locator ping request to compute which Active Directory site the client belongs to. If no site mapping can be computed, the DC may do an address lookup on the client network name to discover other IP addresses which may then be used to compute a matching site for the client.
-
-The allowable values for this setting result in the following behaviors:
-
-0 - DCs will never perform address lookups.
-1 - DCs will perform an exhaustive address lookup to discover additional client IP addresses.
-2 - DCs will perform a fast, DNS-only address lookup to discover additional client IP addresses.
-
-To specify this behavior in the DC Locator DNS SRV records, click Enabled, and then enter a value. The range of values is from 0 to 2.
-
-If you do not configure this policy setting, it is not applied to any DCs, and DCs use their local configuration.
-
- Use urgent mode when pinging domain controllers
- This policy setting configures whether the computers to which this setting is applied are more aggressive when trying to locate a domain controller (DC).
-
-When an environment has a large number of DCs running both old and new operating systems, the default DC locator discovery behavior may be insufficient to find DCs running a newer operating system. This policy setting can be enabled to configure DC locator to be more aggressive about trying to locate a DC in such an environment, by pinging DCs at a higher frequency. Enabling this setting may result in additional network traffic and increased load on DCs. You should disable this setting once all DCs are running the same OS version.
-
-The allowable values for this setting result in the following behaviors:
-
-1 - Computers will ping DCs at the normal frequency.
-2 - Computers will ping DCs at the higher frequency.
-
-To specify this behavior, click Enabled and then enter a value. The range of values is from 1 to 2.
-
-If you do not configure this policy setting, it is not applied to any computers, and computers use their local configuration.
-
- Use lowercase DNS host names when registering domain controller SRV records
- This policy setting configures whether the domain controllers to which this setting is applied will lowercase their DNS host name when registering SRV records.
-
-If enabled, domain controllers will lowercase their DNS host name when registering domain controller SRV records. A best-effort attempt will be made to delete any previously registered SRV records that contain mixed-case DNS host names. For more information and potential manual cleanup procedures, see the link below.
-
-If disabled, domain controllers will use their configured DNS host name as-is when registering domain controller SRV records.
-
-If not configured, domain controllers will default to using their local configuration.
-
-The default local configuration is enabled.
-
-A reboot is not required for changes to this setting to take effect.
-
-More information is available at https://aka.ms/lowercasehostnamesrvrecord
-
-
-
-
-
- Seconds:
-
-
- Seconds:
-
-
- Seconds:
-
-
- Seconds:
-
-
- Level:
-
-
-
-
-
-
-
- Seconds:
-
-
- Seconds:
-
-
- Seconds:
-
-
-
-
-
-
-
- Priority:
-
-
- Weight:
-
-
- Bytes:
-
-
-
-
-
-
-
- Seconds:
-
-
- Seconds:
-
-
- Seconds:
-
-
-
-
-
-
-
-
-
-
-
-
- Seconds:
-
-
- Address lookup behavior:
-
-
- Ping urgency mode:
-
-
-
-
diff --git a/policy_templates/en-US/NetworkConnections.adml b/policy_templates/en-US/NetworkConnections.adml
deleted file mode 100644
index d4ef58d..0000000
--- a/policy_templates/en-US/NetworkConnections.adml
+++ /dev/null
@@ -1,383 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Prohibit adding and removing components for a LAN or remote access connection
- Determines whether administrators can add and remove network components for a LAN or remote access connection. This setting has no effect on nonadministrators.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Install and Uninstall buttons for components of connections are disabled, and administrators are not permitted to access network components in the Windows Components Wizard.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the Install and Uninstall buttons for components of connections in the Network Connections folder are enabled. Also, administrators can gain access to network components in the Windows Components Wizard.
-
-The Install button opens the dialog boxes used to add network components. Clicking the Uninstall button removes the selected component in the components list (above the button).
-
-The Install and Uninstall buttons appear in the properties dialog box for connections. These buttons are on the General tab for LAN connections and on the Networking tab for remote access connections.
-
-Note: When the "Prohibit access to properties of a LAN connection", "Ability to change properties of an all user remote access connection", or "Prohibit changing properties of a private remote access connection" settings are set to deny access to the connection properties dialog box, the Install and Uninstall buttons for connections are blocked.
-
-Note: Nonadministrators are already prohibited from adding and removing connection components, regardless of this setting.
- Prohibit access to the Advanced Settings item on the Advanced menu
- Determines whether the Advanced Settings item on the Advanced menu in Network Connections is enabled for administrators.
-
-The Advanced Settings item lets users view and change bindings and view and change the order in which the computer accesses connections, network providers, and print providers.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Advanced Settings item is disabled for administrators.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the Advanced Settings item is enabled for administrators.
-
-Note: Nonadministrators are already prohibited from accessing the Advanced Settings dialog box, regardless of this setting.
- Prohibit TCP/IP advanced configuration
- Determines whether users can configure advanced TCP/IP settings.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Advanced button on the Internet Protocol (TCP/IP) Properties dialog box is disabled for all users (including administrators). As a result, users cannot open the Advanced TCP/IP Settings Properties page and modify IP settings, such as DNS and WINS server information.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting, the Advanced button is enabled, and all users can open the Advanced TCP/IP Setting dialog box.
-
-Note: This setting is superseded by settings that prohibit access to properties of connections or connection components. When these policies are set to deny access to the connection properties dialog box or Properties button for connection components, users cannot gain access to the Advanced button for TCP/IP configuration.
-
-Note: Nonadministrators (excluding Network Configuration Operators) do not have permission to access TCP/IP advanced configuration for a LAN connection, regardless of this setting.
-
-Tip: To open the Advanced TCP/IP Setting dialog box, in the Network Connections folder, right-click a connection icon, and click Properties. For remote access connections, click the Networking tab. In the "Components checked are used by this connection" box, click Internet Protocol (TCP/IP), click the Properties button, and then click the Advanced button.
-
-Note: Changing this setting from Enabled to Not Configured does not enable the Advanced button until the user logs off.
- Prohibit installation and configuration of Network Bridge on your DNS domain network
- Determines whether a user can install and configure the Network Bridge.
-
-Important: This settings is location aware. It only applies when a computer is connected to the same DNS domain network it was connected to when the setting was refreshed on that computer. If a computer is connected to a DNS domain network other than the one it was connected to when the setting was refreshed, this setting does not apply.
-
-The Network Bridge allows users to create a layer 2 MAC bridge, enabling them to connect two or more network segements together. This connection appears in the Network Connections folder.
-
-If you disable this setting or do not configure it, the user will be able to create and modify the configuration of a Network Bridge. Enabling this setting does not remove an existing Network Bridge from the user's computer.
- Prohibit Enabling/Disabling components of a LAN connection
- Determines whether administrators can enable and disable the components used by LAN connections.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the check boxes for enabling and disabling components are disabled. As a result, administrators cannot enable or disable the components that a connection uses.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the Properties dialog box for a connection includes a check box beside the name of each component that the connection uses. Selecting the check box enables the component, and clearing the check box disables the component.
-
-Note: When the "Prohibit access to properties of a LAN connection" setting is enabled, users are blocked from accessing the check boxes for enabling and disabling the components of a LAN connection.
-
-Note: Nonadministrators are already prohibited from enabling or disabling components for a LAN connection, regardless of this setting.
- Ability to delete all user remote access connections
- Determines whether users can delete all user remote access connections.
-
-To create an all-user remote access connection, on the Connection Availability page in the New Connection Wizard, click the "For all users" option.
-
-If you enable this setting, all users can delete shared remote access connections. In addition, if your file system is NTFS, users need to have Write access to Documents and Settings\All Users\Application Data\Microsoft\Network\Connections\Pbk to delete a shared remote access connection.
-
-If you disable this setting (and enable the "Enable Network Connections settings for Administrators" setting), users (including administrators) cannot delete all-user remote access connections. (By default, users can still delete their private connections, but you can change the default by using the "Prohibit deletion of remote access connections" setting.)
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you do not configure this setting, only Administrators and Network Configuration Operators can delete all user remote access connections.
-
-Important: When enabled, the "Prohibit deletion of remote access connections" setting takes precedence over this setting. Users (including administrators) cannot delete any remote access connections, and this setting is ignored.
-
-Note: LAN connections are created and deleted automatically by the system when a LAN adapter is installed or removed. You cannot use the Network Connections folder to create or delete a LAN connection.
-
-Note: This setting does not prevent users from using other programs, such as Internet Explorer, to bypass this setting.
- Prohibit deletion of remote access connections
- Determines whether users can delete remote access connections.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), users (including administrators) cannot delete any remote access connections. This setting also disables the Delete option on the context menu for a remote access connection and on the File menu in the Network Connections folder.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, all users can delete their private remote access connections. Private connections are those that are available only to one user. (By default, only Administrators and Network Configuration Operators can delete connections available to all users, but you can change the default by using the "Ability to delete all user remote access connections" setting.)
-
-Important: When enabled, this setting takes precedence over the "Ability to delete all user remote access connections" setting. Users cannot delete any remote access connections, and the "Ability to delete all user remote access connections" setting is ignored.
-
-Note: LAN connections are created and deleted automatically when a LAN adapter is installed or removed. You cannot use the Network Connections folder to create or delete a LAN connection.
-
-Note: This setting does not prevent users from using other programs, such as Internet Explorer, to bypass this setting.
- Prohibit access to the Remote Access Preferences item on the Advanced menu
- Determines whether the Remote Acccess Preferences item on the Advanced menu in Network Connections folder is enabled.
-
-The Remote Access Preferences item lets users create and change connections before logon and configure automatic dialing and callback features.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Remote Access Preferences item is disabled for all users (including administrators).
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the Remote Access Preferences item is enabled for all users.
- Enable Windows 2000 Network Connections settings for Administrators
- Determines whether settings that existed in Windows 2000 Server family will apply to Administrators.
-
-The set of Network Connections group settings that existed in Windows 2000 Professional also exists in Windows XP Professional. In Windows 2000 Professional, all of these settings had the ability to prohibit the use of certain features from Administrators.
-
-By default, Network Connections group settings in Windows XP Professional do not have the ability to prohibit the use of features from Administrators.
-
-If you enable this setting, the Windows XP settings that existed in Windows 2000 Professional will have the ability to prohibit Administrators from using certain features. These settings are "Ability to rename LAN connections or remote access connections available to all users", "Prohibit access to properties of components of a LAN connection", "Prohibit access to properties of components of a remote access connection", "Ability to access TCP/IP advanced configuration", "Prohibit access to the Advanced Settings Item on the Advanced Menu", "Prohibit adding and removing components for a LAN or remote access connection", "Prohibit access to properties of a LAN connection", "Prohibit Enabling/Disabling components of a LAN connection", "Ability to change properties of an all user remote access connection", "Prohibit changing properties of a private remote access connection", "Prohibit deletion of remote access connections", "Ability to delete all user remote access connections", "Prohibit connecting and disconnecting a remote access connection", "Ability to Enable/Disable a LAN connection", "Prohibit access to the New Connection Wizard", "Prohibit renaming private remote access connections", "Prohibit access to the Remote Access Preferences item on the Advanced menu", "Prohibit viewing of status for an active connection". When this setting is enabled, settings that exist in both Windows 2000 Professional and Windows XP Professional behave the same for administrators.
-
-If you disable this setting or do not configure it, Windows XP settings that existed in Windows 2000 will not apply to administrators.
-
-Note: This setting is intended to be used in a situation in which the Group Policy object that these settings are being applied to contains both Windows 2000 Professional and Windows XP Professional computers, and identical Network Connections policy behavior is required between all Windows 2000 Professional and Windows XP Professional computers.
- Turn off notifications when a connection has only limited or no connectivity
- This policy setting allows you to manage whether notifications are shown to the user when a DHCP-configured connection is unable to retrieve an IP address from a DHCP server. This is often signified by the assignment of an automatic private IP address"(i.e. an IP address in the range 169.254.*.*). This indicates that a DHCP server could not be reached or the DHCP server was reached but unable to respond to the request with a valid IP address. By default, a notification is displayed providing the user with information on how the problem can be resolved.
-
-If you enable this policy setting, this condition will not be reported as an error to the user.
-
-If you disable or do not configure this policy setting, a DHCP-configured connection that has not been assigned an IP address will be reported via a notification, providing the user with information as to how the problem can be resolved.
- Prohibit access to properties of components of a LAN connection
- Determines whether Administrators and Network Configuration Operators can change the properties of components used by a LAN connection.
-
-This setting determines whether the Properties button for components of a LAN connection is enabled.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Properties button is disabled for Administrators. Network Configuration Operators are prohibited from accessing connection components, regardless of the "Enable Network Connections settings for Administrators" setting.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting does not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the Properties button is enabled for administrators and Network Configuration Operators.
-
-The Local Area Connection Properties dialog box includes a list of the network components that the connection uses. To view or change the properties of a component, click the name of the component, and then click the Properties button beneath the component list.
-
-Note: Not all network components have configurable properties. For components that are not configurable, the Properties button is always disabled.
-
-Note: When the "Prohibit access to properties of a LAN connection" setting is enabled, users are blocked from accessing the Properties button for LAN connection components.
-
-Note: Network Configuration Operators only have permission to change TCP/IP properties. Properties for all other components are unavailable to these users.
-
-Note: Nonadministrators are already prohibited from accessing properties of components for a LAN connection, regardless of this setting.
- Ability to Enable/Disable a LAN connection
- Determines whether users can enable/disable LAN connections.
-
-If you enable this setting, the Enable and Disable options for LAN connections are available to users (including nonadministrators). Users can enable/disable a LAN connection by double-clicking the icon representing the connection, by right-clicking it, or by using the File menu.
-
-If you disable this setting (and enable the "Enable Network Connections settings for Administrators" setting), double-clicking the icon has no effect, and the Enable and Disable menu items are disabled for all users (including administrators).
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you do not configure this setting, only Administrators and Network Configuration Operators can enable/disable LAN connections.
-
-Note: Administrators can still enable/disable LAN connections from Device Manager when this setting is disabled.
- Prohibit access to properties of a LAN connection
- Determines whether users can change the properties of a LAN connection.
-
-This setting determines whether the Properties menu item is enabled, and thus, whether the Local Area Connection Properties dialog box is available to users.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Properties menu items are disabled for all users, and users cannot open the Local Area Connection Properties dialog box.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, a Properties menu item appears when users right-click the icon representing a LAN connection. Also, when users select the connection, Properties is enabled on the File menu.
-
-Note: This setting takes precedence over settings that manipulate the availability of features inside the Local Area Connection Properties dialog box. If this setting is enabled, nothing within the properties dialog box for a LAN connection is available to users.
-
-Note: Nonadministrators have the right to view the properties dialog box for a connection but not to make changes, regardless of this setting.
- Prohibit access to the New Connection Wizard
- Determines whether users can use the New Connection Wizard, which creates new network connections.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Make New Connection icon does not appear in the Start Menu on in the Network Connections folder. As a result, users (including administrators) cannot start the New Connection Wizard.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the Make New Connection icon appears in the Start menu and in the Network Connections folder for all users. Clicking the Make New Connection icon starts the New Connection Wizard.
-
-Note: Changing this setting from Enabled to Not Configured does not restore the Make New Connection icon until the user logs off or on. When other changes to this setting are applied, the icon does not appear or disappear in the Network Connections folder until the folder is refreshed.
-
-Note: This setting does not prevent users from using other programs, such as Internet Explorer, to bypass this setting.
- Prohibit use of Internet Connection Firewall on your DNS domain network
- Prohibits use of Internet Connection Firewall on your DNS domain network.
-
-Determines whether users can enable the Internet Connection Firewall feature on a connection, and if the Internet Connection Firewall service can run on a computer.
-
-Important: This setting is location aware. It only applies when a computer is connected to the same DNS domain network it was connected to when the setting was refreshed on that computer. If a computer is connected to a DNS domain network other than the one it was connected to when the setting was refreshed, this setting does not apply.
-
-The Internet Connection Firewall is a stateful packet filter for home and small office users to protect them from Internet network security threats.
-
-If you enable this setting, Internet Connection Firewall cannot be enabled or configured by users (including administrators), and the Internet Connection Firewall service cannot run on the computer. The option to enable the Internet Connection Firewall through the Advanced tab is removed. In addition, the Internet Connection Firewall is not enabled for remote access connections created through the Make New Connection Wizard. The Network Setup Wizard is disabled.
-
-Note: If you enable the "Windows Firewall: Protect all network connections" policy setting, the "Prohibit use of Internet Connection Firewall on your DNS domain network" policy setting has no effect on computers that are running Windows Firewall, which replaces Internet Connection Firewall when you install Windows XP Service Pack 2.
-
-If you disable this setting or do not configure it, the Internet Connection Firewall is disabled when a LAN Connection or VPN connection is created, but users can use the Advanced tab in the connection properties to enable it. The Internet Connection Firewall is enabled by default on the connection for which Internet Connection Sharing is enabled. In addition, remote access connections created through the Make New Connection Wizard have the Internet Connection Firewall enabled.
- Ability to change properties of an all user remote access connection
- Determines whether a user can view and change the properties of remote access connections that are available to all users of the computer.
-
-To create an all-user remote access connection, on the Connection Availability page in the New Connection Wizard, click the "For all users" option.
-
-This setting determines whether the Properties menu item is enabled, and thus, whether the Remote Access Connection Properties dialog box is available to users.
-
-If you enable this setting, a Properties menu item appears when any user right-clicks the icon for a remote access connection. Also, when any user selects the connection, Properties appears on the File menu.
-
-If you disable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Properties menu items are disabled, and users (including administrators) cannot open the remote access connection properties dialog box.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you do not configure this setting, only Administrators and Network Configuration Operators can change properties of all-user remote access connections.
-
-Note: This setting takes precedence over settings that manipulate the availability of features inside the Remote Access Connection Properties dialog box. If this setting is disabled, nothing within the properties dialog box for a remote access connection will be available to users.
-
-Note: This setting does not prevent users from using other programs, such as Internet Explorer, to bypass this setting.
- Prohibit access to properties of components of a remote access connection
- Determines whether users can view and change the properties of components used by a private or all-user remote access connection.
-
-This setting determines whether the Properties button for components used by a private or all-user remote access connection is enabled.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Properties button is disabled for all users (including administrators).
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting does not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the Properties button is enabled for all users.
-
-The Networking tab of the Remote Access Connection Properties dialog box includes a list of the network components that the connection uses. To view or change the properties of a component, click the name of the component, and then click the Properties button beneath the component list.
-
-Note: Not all network components have configurable properties. For components that are not configurable, the Properties button is always disabled.
-
-Note: When the "Ability to change properties of an all user remote access connection" or "Prohibit changing properties of a private remote access connection" settings are set to deny access to the Remote Access Connection Properties dialog box, the Properties button for remote access connection components is blocked.
-
-Note: This setting does not prevent users from using other programs, such as Internet Explorer, to bypass this setting.
- Prohibit connecting and disconnecting a remote access connection
- Determines whether users can connect and disconnect remote access connections.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), double-clicking the icon has no effect, and the Connect and Disconnect menu items are disabled for all users (including administrators).
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the Connect and Disconnect options for remote access connections are available to all users. Users can connect or disconnect a remote access connection by double-clicking the icon representing the connection, by right-clicking it, or by using the File menu.
- Prohibit changing properties of a private remote access connection
- Determines whether users can view and change the properties of their private remote access connections.
-
-Private connections are those that are available only to one user. To create a private connection, on the Connection Availability page in the New Connection Wizard, click the "Only for myself" option.
-
-This setting determines whether the Properties menu item is enabled, and thus, whether the Remote Access Connection Properties dialog box for a private connection is available to users.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Properties menu items are disabled, and no users (including administrators) can open the Remote Access Connection Properties dialog box for a private connection.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, a Properties menu item appears when any user right-clicks the icon representing a private remote access connection. Also, when any user selects the connection, Properties appears on the File menu.
-
-Note: This setting takes precedence over settings that manipulate the availability of features in the Remote Access Connection Properties dialog box. If this setting is enabled, nothing within the properties dialog box for a remote access connection will be available to users.
-
-Note: This setting does not prevent users from using other programs, such as Internet Explorer, to bypass this setting.
- Ability to rename all user remote access connections
- Determines whether nonadministrators can rename all-user remote access connections.
-
-To create an all-user connection, on the Connection Availability page in the New Connection Wizard, click the "For all users" option.
-
-If you enable this setting, the Rename option is enabled for all-user remote access connections. Any user can rename all-user connections by clicking an icon representing the connection or by using the File menu.
-
-If you disable this setting, the Rename option is disabled for nonadministrators only.
-
-If you do not configure the setting, only Administrators and Network Configuration Operators can rename all-user remote access connections.
-
-Note: This setting does not apply to Administrators
-
-Note: When the "Ability to rename LAN connections or remote access connections available to all users" setting is configured (set to either Enabled or Disabled), this setting does not apply.
-
-Note: This setting does not prevent users from using other programs, such as Internet Explorer, to bypass this setting.
- Ability to rename LAN connections or remote access connections available to all users
- Determines whether users can rename LAN or all user remote access connections.
-
-If you enable this setting, the Rename option is enabled for all users. Users can rename connections by clicking the icon representing a connection or by using the File menu.
-
-If you disable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Rename option for LAN and all user remote access connections is disabled for all users (including Administrators and Network Configuration Operators).
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If this setting is not configured, only Administrators and Network Configuration Operators have the right to rename LAN or all user remote access connections.
-
-Note: When configured, this setting always takes precedence over the "Ability to rename LAN connections" and "Ability to rename all user remote access connections" settings.
-
-Note: This setting does not prevent users from using other programs, such as Internet Explorer, to rename remote access connections.
- Ability to rename LAN connections
- Determines whether nonadministrators can rename a LAN connection.
-
-If you enable this setting, the Rename option is enabled for LAN connections. Nonadministrators can rename LAN connections by clicking an icon representing the connection or by using the File menu.
-
-If you disable this setting, the Rename option is disabled for nonadministrators only.
-
-If you do not configure this setting, only Administrators and Network Configuration Operators can rename LAN connections
-
-Note: This setting does not apply to Administrators.
-
-Note: When the "Ability to rename LAN connections or remote access connections available to all users" setting is configured (set to either enabled or disabled), this setting does not apply.
- Prohibit renaming private remote access connections
- Determines whether users can rename their private remote access connections.
-
-Private connections are those that are available only to one user. To create a private connection, on the Connection Availability page in the New Connection Wizard, click the "Only for myself" option.
-
-If you enable this setting (and enable the "Enable Network Connections settings for Administrators" setting), the Rename option is disabled for all users (including administrators).
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the Rename option is enabled for all users' private remote access connections. Users can rename their private connection by clicking an icon representing the connection or by using the File menu.
-
-Note: This setting does not prevent users from using other programs, such as Internet Explorer, to bypass this setting.
- Prohibit use of Internet Connection Sharing on your DNS domain network
- Determines whether administrators can enable and configure the Internet Connection Sharing (ICS) feature of an Internet connection and if the ICS service can run on the computer.
-
-ICS lets administrators configure their system as an Internet gateway for a small network and provides network services, such as name resolution and addressing through DHCP, to the local private network.
-
-If you enable this setting, ICS cannot be enabled or configured by administrators, and the ICS service cannot run on the computer. The Advanced tab in the Properties dialog box for a LAN or remote access connection is removed. The Internet Connection Sharing page is removed from the New Connection Wizard. The Network Setup Wizard is disabled.
-
-If you disable this setting or do not configure it and have two or more connections, administrators can enable ICS. The Advanced tab in the properties dialog box for a LAN or remote access connection is available. In addition, the user is presented with the option to enable Internet Connection Sharing in the Network Setup Wizard and Make New Connection Wizard. (The Network Setup Wizard is available only in Windows XP Professional.)
-
-By default, ICS is disabled when you create a remote access connection, but administrators can use the Advanced tab to enable it. When running the New Connection Wizard or Network Setup Wizard, administrators can choose to enable ICS.
-
-Note: Internet Connection Sharing is only available when two or more network connections are present.
-
-Note: When the "Prohibit access to properties of a LAN connection," "Ability to change properties of an all user remote access connection," or "Prohibit changing properties of a private remote access connection" settings are set to deny access to the Connection Properties dialog box, the Advanced tab for the connection is blocked.
-
-Note: Nonadministrators are already prohibited from configuring Internet Connection Sharing, regardless of this setting.
-
-Note: Disabling this setting does not prevent Wireless Hosted Networking from using the ICS service for DHCP services. To prevent the ICS service from running, on the Network Permissions tab in the network's policy properties, select the "Don't use hosted networks" check box.
- Prohibit viewing of status for an active connection
- Determines whether users can view the status for an active connection.
-
-Connection status is available from the connection status taskbar icon or from the Status dialog box. The Status dialog box displays information about the connection and its activity. It also provides buttons to disconnect and to configure the properties of the connection.
-
-If you enable this setting, the connection status taskbar icon and Status dialog box are not available to users (including administrators). The Status option is disabled in the context menu for the connection and on the File menu in the Network Connections folder. Users cannot choose to show the connection icon in the taskbar from the Connection Properties dialog box.
-
-Important: If the "Enable Network Connections settings for Administrators" is disabled or not configured, this setting will not apply to administrators on post-Windows 2000 computers.
-
-If you disable this setting or do not configure it, the connection status taskbar icon and Status dialog box are available to all users.
- Require domain users to elevate when setting a network's location
- This policy setting determines whether to require domain users to elevate when setting a network's location.
-
-If you enable this policy setting, domain users must elevate when setting a network's location.
-
-If you disable or do not configure this policy setting, domain users can set a network's location without elevating.
- Do not show the "local access only" network icon
- Specifies whether or not the "local access only" network icon will be shown.
-
-When enabled, the icon for Internet access will be shown in the system tray even when a user is connected to a network with local access only.
-
-If you disable this setting or do not configure it, the "local access only" icon will be used when a user is connected to a network with local access only.
- Network Connections
- Microsoft Windows Server 2003, Windows XP, and Windows 2000 Service Pack 1 operating systems only
- Microsoft Windows XP Professional with SP2 and Windows Server 2003 family only
-
- Enabled State
- Disabled State
-
- Route all traffic through the internal network
- This policy setting determines whether a remote client computer routes Internet traffic through the internal network or whether the client accesses the Internet directly.
-
-When a remote client computer connects to an internal network using DirectAccess, it can access the Internet in two ways: through the secure tunnel that DirectAccess establishes between the computer and the internal network, or directly through the local default gateway.
-
-If you enable this policy setting, all traffic between a remote client computer running DirectAccess and the Internet is routed through the internal network.
-
-If you disable this policy setting, traffic between remote client computers running DirectAccess and the Internet is not routed through the internal network.
-
-If you do not configure this policy setting, traffic between remote client computers running DirectAccess and the Internet is not routed through the internal network.
-
-
-
-
- Select from the following states:
-
-
-
-
diff --git a/policy_templates/en-US/NetworkIsolation.adml b/policy_templates/en-US/NetworkIsolation.adml
deleted file mode 100644
index cc6c741..0000000
--- a/policy_templates/en-US/NetworkIsolation.adml
+++ /dev/null
@@ -1,157 +0,0 @@
-
-
- Network Isolation
- Configures Network Isolation Options for apps
-
-
- Network Isolation
-
-
-
- Internet proxy servers for apps
- This setting does not apply to desktop apps.
-
-A semicolon-separated list of Internet proxy server IP addresses. These addresses are categorized as Internet by Windows Network Isolation and are accessible to apps that have the Internet Client or Internet Client/Server capabilities.
-
-If you enable this policy setting, apps on proxied networks can access the Internet without relying on the Private Network capability. However, in most situations Windows Network Isolation will be able to correctly discover proxies. By default, any proxies configured with this setting are merged with proxies that are auto-discovered. To make this policy configuration the sole list of allowed proxies, enable the "Proxy definitions are authoritative" setting.
-
-If you disable or do not configure this policy setting, apps will use the Internet proxies auto-discovered by Windows Network Isolation.
-
-Example: [3efe:3022::1000];18.0.0.1;18.0.0.2
-
-For more information see: http://go.microsoft.com/fwlink/p/?LinkId=234043
-
-
-
- Intranet proxy servers for apps
- This setting does not apply to desktop apps.
-
-A semicolon-separated list of intranet proxy server IP addresses. These addresses are categorized as private by Windows Network Isolation and are accessible to apps that have the Home/Work Networking capability.
-
-If you enable this policy setting, it allows an administrator to configure a set of proxies that provide access to intranet resources.
-
-If you disable or do not configure this policy setting, Windows Network Isolation attempts to discover proxies and configures them as Internet nodes.
-
-This setting should NOT be used to configure Internet proxies.
-
-Example: [3efe:3022::1000]; 18.0.0.1; 18.0.0.2
-
-For more information see: http://go.microsoft.com/fwlink/p/?LinkId=234043
-
-
-
- Private network ranges for apps
- This setting does not apply to desktop apps.
-
-A comma-separated list of IP address ranges that are in your corporate network.
-
-If you enable this policy setting, it ensures that apps with the Home/Work Networking capability have appropriate access to your corporate network. These addresses are only accessible to apps if and only if the app has declared the Home/Work Networking capability.
-
-Windows Network Isolation attempts to automatically discover private network hosts. By default, the addresses configured with this policy setting are merged with the hosts that are declared as private through automatic discovery.
-
-To ensure that these addresses are the only addresses ever classified as private, enable the "Subnet definitions are authoritative" policy setting.
-
-If you disable or do not configure this policy setting, Windows Network Isolation attempts to automatically discover your private network hosts.
-
-Example: 3efe:1092::/96,18.1.1.1/10
-
-For more information see: http://go.microsoft.com/fwlink/p/?LinkId=234043
-
-
-
- Proxy definitions are authoritative
- This setting does not apply to desktop apps.
-
-Turns off Windows Network Isolation's automatic proxy discovery in the domain corporate environment.
-
-If you enable this policy setting, it turns off Windows Network Isolation's automatic proxy discovery in the domain corporate environment. Only proxies configured with Group Policy are authoritative. This applies to both Internet and intranet proxies.
-
-If you disable or do not configure this policy setting, Windows Network Isolation attempts to automatically discover your proxy server addresses.
-
-For more information see: http://go.microsoft.com/fwlink/p/?LinkId=234043
-
-
-
- Subnet definitions are authoritative
- This setting does not apply to desktop apps.
-
-Turns off Windows Network Isolation's automatic discovery of private network hosts in the domain corporate environment.
-
-If you enable this policy setting, it turns off Windows Network Isolation's automatic discovery of private network hosts in the domain corporate environment. Only network hosts within the address ranges configured via Group Policy will be classified as private.
-
-If you disable or do not configure this policy setting, Windows Network Isolation attempts to automatically discover your private network hosts in the domain corporate environment.
-
-For more information see: http://go.microsoft.com/fwlink/p/?LinkId=234043
-
-
-
-
- Enterprise resource domains hosted in the cloud
- This setting does not apply to desktop apps.
-
-A pipe-separated list of domain cloud resources. Each cloud resource can also be paired optionally with an internal proxy server by using a trailing comma followed by the proxy address.
-
-Contains a list of Enterprise resource domains hosted in the cloud. Connections to these resources are considered connections to enterprise networks.
-
-If a proxy is paired with a cloud resource, traffic to the cloud resource will be routed through the enterprise network via the denoted proxy server (on Port 80). A proxy server used for this purpose must also be configured using the Intranet proxy servers for apps policy.
-
-Example: [cloudresource]|[cloudresource]|[cloudresource],[proxy]|[cloudresource]|[cloudresource],[proxy]|
-
-For more information see: http://go.microsoft.com/fwlink/p/?LinkId=234043
-
-
-
- Domains categorized as both work and personal
- This setting does not apply to desktop apps.
-
-A comma-separated list of domain names that can be used as both work or personal resource.
-
-For more information see: http://go.microsoft.com/fwlink/p/?LinkId=234043
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/NetworkProvider.adml b/policy_templates/en-US/NetworkProvider.adml
deleted file mode 100644
index 4aa9595..0000000
--- a/policy_templates/en-US/NetworkProvider.adml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- NetworkProvider
- Policy Definitions for the Multiple UNC Provider
-
-
- Network Provider
- Hardened UNC Paths
- This policy setting configures secure access to UNC paths.
-
-If you enable this policy, Windows only allows access to the specified UNC paths after fulfilling additional security requirements.
-
-
-
-
- Specify hardened network paths.
-In the name field, type a fully-qualified UNC path for each network resource.
-To secure all access to a share with a particular name, regardless of the server name, specify a server name of '*' (asterisk). For example, "\\*\NETLOGON".
-To secure all access to all shares hosted on a server, the share name portion of the UNC path may be omitted. For example, "\\SERVER".
-
-In the value field, specify one or more of the following options, separated by commas:
- 'RequireMutualAuthentication=1': Mutual authentication between the client and server is required to ensure the client connects to the correct server.
- 'RequireIntegrity=1': Communication between the client and server must employ an integrity mechanism to prevent data tampering.
- 'RequirePrivacy=1': Communication between the client and the server must be encrypted to prevent third parties from observing sensitive data.
- Hardened UNC Paths:
-
- You should require both Integrity and Mutual Authentication for any UNC paths that host executable programs, script files, or files that control security policies.
-
-Consider hosting files that do not require Integrity or Privacy on separate shares from those that absolutely need such security for optimal performance.
-
-For additional details on configuring Windows computers to require additional security when accessing specific UNC paths, visit http://support.microsoft.com/kb/3000483.
-
-
-
-
diff --git a/policy_templates/en-US/NewsAndInterests.adml b/policy_templates/en-US/NewsAndInterests.adml
deleted file mode 100644
index d80ca83..0000000
--- a/policy_templates/en-US/NewsAndInterests.adml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Widgets
- Allow widgets
- This policy specifies whether the widgets feature is allowed on the device.
-Widgets will be turned on by default unless you change this in your settings.
-If you turned this feature on before, it will stay on automatically unless you turn it off.
-
-
-
diff --git a/policy_templates/en-US/OOBE.adml b/policy_templates/en-US/OOBE.adml
deleted file mode 100644
index 11d82b6..0000000
--- a/policy_templates/en-US/OOBE.adml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- OOBE Group Policies
- Policies defined to manage OOBE settings via Group Policy Management services.
-
-
- OOBE
- Configure certain OOBE-related settings
-
- Don't launch privacy settings experience on user logon
- When logging into a new user account for the first time or after an upgrade in some scenarios, that user may be presented with a screen or series of screens that prompts the user to choose privacy settings for their account. Enable this policy to prevent this experience from launching.
-
-If this policy is enabled, the privacy experience will not launch for newly-created user accounts or for accounts that would have been prompted to choose their privacy settings after an upgrade.
-
-If this policy is disabled or not configured, then the privacy experience may launch for newly-created user accounts or for accounts that should be prompted to choose their privacy settings after an upgrade.
-
-
-
diff --git a/policy_templates/en-US/OSPolicy.adml b/policy_templates/en-US/OSPolicy.adml
deleted file mode 100644
index 0a55ae2..0000000
--- a/policy_templates/en-US/OSPolicy.adml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
- Operating System privacy policies
- Contains machine wide privacy policies
-
-
- OS Policies
- Enables Activity Feed
-
- This policy setting determines whether ActivityFeed is enabled.
- If you enable this policy setting, all activity types (as applicable) are allowed to be published and ActivityFeed shall roam these activities across device graph of the user.
- If you disable this policy setting, activities can't be published and ActivityFeed shall disable cloud sync.
- Policy change takes effect immediately.
-
- Allow publishing of User Activities
-
- This policy setting determines whether User Activities can be published.
- If you enable this policy setting, activities of type User Activity are allowed to be published.
- If you disable this policy setting, activities of type User Activity are not allowed to be published.
- Policy change takes effect immediately.
-
- Allow upload of User Activities
-
- This policy setting determines whether published User Activities can be uploaded.
- If you enable this policy setting, activities of type User Activity are allowed to be uploaded.
- If you disable this policy setting, activities of type User Activity are not allowed to be uploaded.
- Deletion of activities of type User Activity are independent of this setting.
- Policy change takes effect immediately.
-
- Allow Clipboard synchronization across devices
-
- This policy setting determines whether Clipboard contents can be synchronized across devices.
- If you enable this policy setting, Clipboard contents are allowed to be synchronized across devices logged in under the same Microsoft account or Azure AD account.
- If you disable this policy setting, Clipboard contents cannot be shared to other devices.
- Policy change takes effect immediately.
-
- Allow Clipboard History
-
- This policy setting determines whether history of Clipboard contents can be stored in memory.
- If you enable this policy setting, history of Clipboard contents are allowed to be stored.
- If you disable this policy setting, history of Clipboard contents are not allowed to be stored.
- Policy change takes effect immediately.
-
-
-
-
diff --git a/policy_templates/en-US/OfflineFiles.adml b/policy_templates/en-US/OfflineFiles.adml
deleted file mode 100644
index afc5330..0000000
--- a/policy_templates/en-US/OfflineFiles.adml
+++ /dev/null
@@ -1,564 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Offline Files
- Never go offline
- Full
- Quick
- Work offline
- Subfolders always available offline
- Makes subfolders available offline whenever their parent folder is made available offline.
-
-This setting automatically extends the "make available offline" setting to all new and existing subfolders of a folder. Users do not have the option of excluding subfolders.
-
-If you enable this setting, when you make a folder available offline, all folders within that folder are also made available offline. Also, new folders that you create within a folder that is available offline are made available offline when the parent folder is synchronized.
-
-If you disable this setting or do not configure it, the system asks users whether they want subfolders to be made available offline when they make a parent folder available offline.
- Specify administratively assigned Offline Files
- This policy setting lists network files and folders that are always available for offline use. This ensures that the specified files and folders are available offline to users of the computer.
-
-If you enable this policy setting, the files you enter are always available offline to users of the computer. To specify a file or folder, click Show. In the Show Contents dialog box in the Value Name column, type the fully qualified UNC path to the file or folder. Leave the Value column field blank.
-
-If you disable this policy setting, the list of files or folders made always available offline (including those inherited from lower precedence GPOs) is deleted and no files or folders are made available for offline use by Group Policy (though users can still specify their own files and folders for offline use).
-
-If you do not configure this policy setting, no files or folders are made available for offline use by Group Policy.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both policy settings are configured, the policy settings will be combined and all specified files will be available for offline use.
-
- Non-default server disconnect actions
- Determines how computers respond when they are disconnected from particular offline file servers. This setting overrides the default response, a user-specified response, and the response specified in the "Action on server disconnect" setting.
-
-To use this setting, click Show. In the Show Contents dialog box in the Value Name column box, type the server's computer name. Then, in the Value column box, type "0" if users can work offline when they are disconnected from this server, or type "1" if they cannot.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured for a particular server, the setting in Computer Configuration takes precedence over the setting in User Configuration. Both Computer and User configuration take precedence over a user's setting. This setting does not prevent users from setting custom actions through the Offline Files tab. However, users are unable to change any custom actions established via this setting.
-
-Tip: To configure this setting without establishing a setting, in Windows Explorer, on the Tools menu, click Folder Options, click the Offline Files tab, and then click Advanced. This setting corresponds to the settings in the "Exception list" section.
- Default cache size
- Limits the percentage of the computer's disk space that can be used to store automatically cached offline files.
-
-This setting also disables the "Amount of disk space to use for temporary offline files" option on the Offline Files tab. This prevents users from trying to change the option while a setting controls it.
-
-Automatic caching can be set on any network share. When a user opens a file on the share, the system automatically stores a copy of the file on the user's computer.
-
-This setting does not limit the disk space available for files that user's make available offline manually.
-
-If you enable this setting, you can specify an automatic-cache disk space limit.
-
-If you disable this setting, the system limits the space that automatically cached files occupy to 10 percent of the space on the system drive.
-
-If you do not configure this setting, disk space for automatically cached files is limited to 10 percent of the system drive by default, but users can change it.
-
-Tip: To change the amount of disk space used for automatic caching without specifying a setting, in Windows Explorer, on the Tools menu, click Folder Options, click the Offline Files tab, and then use the slider bar associated with the "Amount of disk space to use for temporary offline files" option.
-
- Allow or Disallow use of the Offline Files feature
- This policy setting determines whether the Offline Files feature is enabled. Offline Files saves a copy of network files on the user's computer for use when the computer is not connected to the network.
-
-If you enable this policy setting, Offline Files is enabled and users cannot disable it.
-
-If you disable this policy setting, Offline Files is disabled and users cannot enable it.
-
-If you do not configure this policy setting, Offline Files is enabled on Windows client computers, and disabled on computers running Windows Server, unless changed by the user.
-
-Note: Changes to this policy setting do not take effect until the affected computer is restarted.
-
- Encrypt the Offline Files cache
- This policy setting determines whether offline files are encrypted.
-
-Offline files are locally cached copies of files from a network share. Encrypting this cache reduces the likelihood that a user could access files from the Offline Files cache without proper permissions.
-
-If you enable this policy setting, all files in the Offline Files cache are encrypted. This includes existing files as well as files added later. The cached copy on the local computer is affected, but the associated network copy is not. The user cannot unencrypt Offline Files through the user interface.
-
-If you disable this policy setting, all files in the Offline Files cache are unencrypted. This includes existing files as well as files added later, even if the files were stored using NTFS encryption or BitLocker Drive Encryption while on the server. The cached copy on the local computer is affected, but the associated network copy is not. The user cannot encrypt Offline Files through the user interface.
-
-If you do not configure this policy setting, encryption of the Offline Files cache is controlled by the user through the user interface. The current cache state is retained, and if the cache is only partially encrypted, the operation completes so that it is fully encrypted. The cache does not return to the unencrypted state. The user must be an administrator on the local computer to encrypt or decrypt the Offline Files cache.
-
-Note: By default, this cache is protected on NTFS partitions by ACLs.
-
-This setting is applied at user logon. If this setting is changed after user logon then user logoff and logon is required for this setting to take effect.
-
- Event logging level
- Determines which events the Offline Files feature records in the event log.
-
-Offline Files records events in the Application log in Event Viewer when it detects errors. By default, Offline Files records an event only when the offline files storage cache is corrupted. However, you can use this setting to specify additional events you want Offline Files to record.
-
-To use this setting, in the "Enter" box, select the number corresponding to the events you want the system to log. The levels are cumulative; that is, each level includes the events in all preceding levels.
-
-"0" records an error when the offline storage cache is corrupted.
-
-"1" also records an event when the server hosting the offline file is disconnected from the network.
-
-"2" also records events when the local computer is connected and disconnected from the network.
-
-"3" also records an event when the server hosting the offline file is reconnected to the network.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
- Files not cached
- Lists types of files that cannot be used offline.
-
-This setting lets you exclude certain types of files from automatic and manual caching for offline use. The system does not cache files of the type specified in this setting even when they reside on a network share configured for automatic caching. Also, if users try to make a file of this type available offline, the operation will fail and the following message will be displayed in the Synchronization Manager progress dialog box: "Files of this type cannot be made available offline."
-
-This setting is designed to protect files that cannot be separated, such as database components.
-
-To use this setting, type the file name extension in the "Extensions" box. To type more than one extension, separate the extensions with a semicolon (;).
-
-Note: To make changes to this setting effective, you must log off and log on again.
- Action on server disconnect
- Determines whether network files remain available if the computer is suddenly disconnected from the server hosting the files.
-
-This setting also disables the "When a network connection is lost" option on the Offline Files tab. This prevents users from trying to change the option while a setting controls it.
-
-If you enable this setting, you can use the "Action" box to specify how computers in the group respond.
-
--- "Work offline" indicates that the computer can use local copies of network files while the server is inaccessible.
-
--- "Never go offline" indicates that network files are not available while the server is inaccessible.
-
-If you disable this setting or select the "Work offline" option, users can work offline if disconnected.
-
-If you do not configure this setting, users can work offline by default, but they can change this option.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Tip: To configure this setting without establishing a setting, in Windows Explorer, on the Tools menu, click Folder Options, click the Offline Files tab, click Advanced, and then select an option in the "When a network connection is lost" section.
-
-Also, see the "Non-default server disconnect actions" setting.
- Prevent use of Offline Files folder
- Disables the Offline Files folder.
-
-This setting disables the "View Files" button on the Offline Files tab. As a result, users cannot use the Offline Files folder to view or open copies of network files stored on their computer. Also, they cannot use the folder to view characteristics of offline files, such as their server status, type, or location.
-
-This setting does not prevent users from working offline or from saving local copies of files available offline. Also, it does not prevent them from using other programs, such as Windows Explorer, to view their offline files.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Tip: To view the Offline Files Folder, in Windows Explorer, on the Tools menu, click Folder Options, click the Offline Files tab, and then click "View Files."
- Prohibit user configuration of Offline Files
- Prevents users from enabling, disabling, or changing the configuration of Offline Files.
-
-This setting removes the Offline Files tab from the Folder Options dialog box. It also removes the Settings item from the Offline Files context menu and disables the Settings button on the Offline Files Status dialog box. As a result, users cannot view or change the options on the Offline Files tab or Offline Files dialog box.
-
-This is a comprehensive setting that locks down the configuration you establish by using other settings in this folder.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Tip: This setting provides a quick method for locking down the default settings for Offline Files. To accept the defaults, just enable this setting. You do not have to disable any other settings in this folder.
- Remove "Make Available Offline" command
- This policy setting prevents users from making network files and folders available offline.
-
-If you enable this policy setting, users cannot designate files to be saved on their computer for offline use. However, Windows will still cache local copies of files that reside on network shares designated for automatic caching.
-
-If you disable or do not configure this policy setting, users can manually specify files and folders that they want to make available offline.
-
-Notes:
-
-This policy setting appears in the Computer Configuration and User Configuration folders. If both policy settings are configured, the policy setting in Computer Configuration takes precedence.
-
-The "Make Available Offline" command is called "Always available offline" on computers running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows 8, Windows 7, or Windows Vista.
-
- Remove "Make Available Offline" for these files and folders
- This policy setting allows you to manage a list of files and folders for which you want to block the "Make Available Offline" command.
-
-If you enable this policy setting, the "Make Available Offline" command is not available for the files and folders that you list. To specify these files and folders, click Show. In the Show Contents dialog box, in the Value Name column box, type the fully qualified UNC path to the file or folder. Leave the Value column field blank.
-
-If you disable this policy setting, the list of files and folders is deleted, including any lists inherited from lower precedence GPOs, and the "Make Available Offline" command is displayed for all files and folders.
-
-If you do not configure this policy setting, the "Make Available Offline" command is available for all files and folders.
-
-Notes:
-
-This policy setting appears in the Computer Configuration and User Configuration folders. If both policy settings are configured, the policy settings are combined, and the "Make Available Offline" command is unavailable for all specified files and folders.
-
-The "Make Available Offline" command is called "Always available offline" on computers running Windows Server 2012, Windows Server 2008 R2, Windows Server 2008, Windows 8, Windows 7, or Windows Vista.
-
-This policy setting does not prevent files from being automatically cached if the network share is configured for "Automatic Caching." It only affects the display of the "Make Available Offline" command in File Explorer.
-
-If the "Remove 'Make Available Offline' command" policy setting is enabled, this setting has no effect.
-
- Turn off reminder balloons
- Hides or displays reminder balloons, and prevents users from changing the setting.
-
-Reminder balloons appear above the Offline Files icon in the notification area to notify users when they have lost the connection to a networked file and are working on a local copy of the file. Users can then decide how to proceed.
-
-If you enable this setting, the system hides the reminder balloons, and prevents users from displaying them.
-
-If you disable the setting, the system displays the reminder balloons and prevents users from hiding them.
-
-If this setting is not configured, reminder balloons are displayed by default when you enable offline files, but users can change the setting.
-
-To prevent users from changing the setting while a setting is in effect, the system disables the "Enable reminders" option on the Offline Files tab
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Tip: To display or hide reminder balloons without establishing a setting, in Windows Explorer, on the Tools menu, click Folder Options, and then click the Offline Files tab. This setting corresponds to the "Enable reminders" check box.
- At logoff, delete local copy of user’s offline files
- Deletes local copies of the user's offline files when the user logs off.
-
-This setting specifies that automatically and manually cached offline files are retained only while the user is logged on to the computer. When the user logs off, the system deletes all local copies of offline files.
-
-If you disable this setting or do not configure it, automatically and manually cached copies are retained on the user's computer for later offline use.
-
-Caution: Files are not synchronized before they are deleted. Any changes to local files since the last synchronization are lost.
- Reminder balloon frequency
- Determines how often reminder balloon updates appear.
-
-If you enable this setting, you can select how often reminder balloons updates appear and also prevent users from changing this setting.
-
-Reminder balloons appear when the user's connection to a network file is lost or reconnected, and they are updated periodically. By default, the first reminder for an event is displayed for 30 seconds. Then, updates appear every 60 minutes and are displayed for 15 seconds. You can use this setting to change the update interval.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Tip: To set reminder balloon frequency without establishing a setting, in Windows Explorer, on the Tools menu, click Folder Options, and then click the Offline Files tab. This setting corresponds to the "Display reminder balloons every ... minutes" option.
- Initial reminder balloon lifetime
- Determines how long the first reminder balloon for a network status change is displayed.
-
-Reminder balloons appear when the user's connection to a network file is lost or reconnected, and they are updated periodically. By default, the first reminder for an event is displayed for 30 seconds. Then, updates appear every 60 minutes and are displayed for 15 seconds. You can use this setting to change the duration of the first reminder.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
- Reminder balloon lifetime
- Determines how long updated reminder balloons are displayed.
-
-Reminder balloons appear when the user's connection to a network file is lost or reconnected, and they are updated periodically. By default, the first reminder for an event is displayed for 30 seconds. Then, updates appear every 60 minutes and are displayed for 15 seconds. You can use this setting to change the duration of the update reminder.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
- Configure Slow link speed
- Configures the threshold value at which Offline Files considers a network connection to be "slow". Any network speed below this value is considered to be slow.
-
-When a connection is considered slow, Offline Files automatically adjust its behavior to avoid excessive synchronization traffic and will not automatically reconnect to a server when the presence of a server is detected.
-
-If you enable this setting, you can configure the threshold value that will be used to determine a slow network connection.
-
-If this setting is disabled or not configured, the default threshold value of 64,000 bps is used to determine if a network connection is considered to be slow.
-
-Note: Use the following formula when entering the slow link value: [ bps / 100]. For example, if you want to set a threshold value of 128,000 bps, enter a value of 1280.
- Synchronize all offline files before logging off
- Determines whether offline files are fully synchronized when users log off.
-
-This setting also disables the "Synchronize all offline files before logging off" option on the Offline Files tab. This prevents users from trying to change the option while a setting controls it.
-
-If you enable this setting, offline files are fully synchronized. Full synchronization ensures that offline files are complete and current.
-
-If you disable this setting, the system only performs a quick synchronization. Quick synchronization ensures that files are complete, but does not ensure that they are current.
-
-If you do not configure this setting, the system performs a quick synchronization by default, but users can change this option.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Tip: To change the synchronization method without changing a setting, in Windows Explorer, on the Tools menu, click Folder Options, click the Offline Files tab, and then select the "Synchronize all offline files before logging off" option.
- Synchronize all offline files when logging on
- Determines whether offline files are fully synchronized when users log on.
-
-This setting also disables the "Synchronize all offline files before logging on" option on the Offline Files tab. This prevents users from trying to change the option while a setting controls it.
-
-If you enable this setting, offline files are fully synchronized at logon. Full synchronization ensures that offline files are complete and current. Enabling this setting automatically enables logon synchronization in Synchronization Manager.
-
-If this setting is disabled and Synchronization Manager is configured for logon synchronization, the system performs only a quick synchronization. Quick synchronization ensures that files are complete but does not ensure that they are current.
-
-If you do not configure this setting and Synchronization Manager is configured for logon synchronization, the system performs a quick synchronization by default, but users can change this option.
-
-This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Tip: To change the synchronization method without setting a setting, in Windows Explorer, on the Tools menu, click Folder Options, click the Offline Files tab, and then select the "Synchronize all offline files before logging on" option.
- Synchronize offline files before suspend
- Determines whether offline files are synchonized before a computer is suspended.
-
-If you enable this setting, offline files are synchronized whenever the computer is suspended. Setting the synchronization action to "Quick" ensures only that all files in the cache are complete. Setting the synchronization action to "Full" ensures that all cached files and folders are up-to-date with the most current version.
-
-If you disable or do not configuring this setting, files are not synchronized when the computer is suspended.
-
-Note: If the computer is suspended by closing the display on a portable computer, files are not synchronized. If multiple users are logged on to the computer at the time the computer is suspended, a synchronization is not performed.
-
- Turn on economical application of administratively assigned Offline Files
- This policy setting allows you to turn on economical application of administratively assigned Offline Files.
-
-If you enable or do not configure this policy setting, only new files and folders in administratively assigned folders are synchronized at logon. Files and folders that are already available offline are skipped and are synchronized later.
-
-If you disable this policy setting, all administratively assigned folders are synchronized at logon.
-
- Remove "Work offline" command
- This policy setting removes the "Work offline" command from Explorer, preventing users from manually changing whether Offline Files is in online mode or offline mode.
-
-If you enable this policy setting, the "Work offline" command is not displayed in File Explorer.
-
-If you disable or do not configure this policy setting, the "Work offline" command is displayed in File Explorer.
-
- Configure slow-link mode
- This policy setting controls the network latency and throughput thresholds that will cause a client computers to transition files and folders that are already available offline to the slow-link mode so that the user's access to this data is not degraded due to network slowness. When Offline Files is operating in the slow-link mode, all network file requests are satisfied from the Offline Files cache. This is similar to a user working offline.
-
-If you enable this policy setting, Offline Files uses the slow-link mode if the network throughput between the client and the server is below (slower than) the Throughput threshold parameter, or if the round-trip network latency is above (slower than) the Latency threshold parameter.
-
-You can configure the slow-link mode by specifying threshold values for Throughput (in bits per second) and/or Latency (in milliseconds) for specific UNC paths. We recommend that you always specify a value for Latency, since the round-trip network latency detection is faster. You can use wildcard characters (*) for specifying UNC paths. If you do not specify a Latency or Throughput value, computers running Windows Vista or Windows Server 2008 will not use the slow-link mode.
-
-If you do not configure this policy setting, computers running Windows Vista or Windows Server 2008 will not transition a shared folder to the slow-link mode. Computers running Windows 7 or Windows Server 2008 R2 will use the default latency value of 80 milliseconds when transitioning a folder to the slow-link mode. Computers running Windows 8 or Windows Server 2012 will use the default latency value of 35 milliseconds when transitioning a folder to the slow-link mode. To avoid extra charges on cell phone or broadband plans, it may be necessary to configure the latency threshold to be lower than the round-trip network latency.
-
-In Windows Vista or Windows Server 2008, once transitioned to slow-link mode, users will continue to operate in slow-link mode until the user clicks the Work Online button on the toolbar in Windows Explorer. Data will only be synchronized to the server if the user manually initiates synchronization by using Sync Center.
-
-In Windows 7, Windows Server 2008 R2, Windows 8 or Windows Server 2012, when operating in slow-link mode Offline Files synchronizes the user's files in the background at regular intervals, or as configured by the "Configure Background Sync" policy. While in slow-link mode, Windows periodically checks the connection to the folder and brings the folder back online if network speeds improve.
-
-In Windows 8 or Windows Server 2012, set the Latency threshold to 1ms to keep users always working offline in slow-link mode.
-
-If you disable this policy setting, computers will not use the slow-link mode.
-
- Limit disk space used by Offline Files
- This policy setting limits the amount of disk space that can be used to store offline files. This includes the space used by automatically cached files and files that are specifically made available offline. Files can be automatically cached if the user accesses a file on an automatic caching network share.
-
-This setting also disables the ability to adjust, through the Offline Files control panel applet, the disk space limits on the Offline Files cache. This prevents users from trying to change the option while a policy setting controls it.
-
-If you enable this policy setting, you can specify the disk space limit (in megabytes) for offline files and also specify how much of that disk space can be used by automatically cached files.
-
-If you disable this policy setting, the system limits the space that offline files occupy to 25 percent of the total space on the drive where the Offline Files cache is located. The limit for automatically cached files is 100 percent of the total disk space limit.
-
-If you do not configure this policy setting, the system limits the space that offline files occupy to 25 percent of the total space on the drive where the Offline Files cache is located. The limit for automatically cached files is 100 percent of the total disk space limit. However, the users can change these values using the Offline Files control applet.
-
-If you enable this setting and specify a total size limit greater than the size of the drive hosting the Offline Files cache, and that drive is the system drive, the total size limit is automatically adjusted downward to 75 percent of the size of the drive. If the cache is located on a drive other than the system drive, the limit is automatically adjusted downward to 100 percent of the size of the drive.
-
-If you enable this setting and specify a total size limit less than the amount of space currently used by the Offline Files cache, the total size limit is automatically adjusted upward to the amount of space currently used by offline files. The cache is then considered full.
-
-If you enable this setting and specify an auto-cached space limit greater than the total size limit, the auto-cached limit is automatically adjusted downward to equal the total size limit.
-
-This setting replaces the Default Cache Size setting used by pre-Windows Vista systems.
- Configure Background Sync
- This policy setting controls when background synchronization occurs while operating in slow-link mode, and applies to any user who logs onto the specified machine while this policy is in effect. To control slow-link mode, use the "Configure slow-link mode" policy setting.
-
-If you enable this policy setting, you can control when Windows synchronizes in the background while operating in slow-link mode. Use the 'Sync Interval' and 'Sync Variance' values to override the default sync interval and variance settings. Use 'Blockout Start Time' and 'Blockout Duration' to set a period of time where background sync is disabled. Use the 'Maximum Allowed Time Without A Sync' value to ensure that all network folders on the machine are synchronized with the server on a regular basis.
-
-You can also configure Background Sync for network shares that are in user selected Work Offline mode. This mode is in effect when a user selects the Work Offline button for a specific share. When selected, all configured settings will apply to shares in user selected Work Offline mode as well.
-
-If you disable or do not configure this policy setting, Windows performs a background sync of offline folders in the slow-link mode at a default interval with the start of the sync varying between 0 and 60 additional minutes. In Windows 7 and Windows Server 2008 R2, the default sync interval is 360 minutes. In Windows 8 and Windows Server 2012, the default sync interval is 120 minutes.
- Enable Transparent Caching
- This policy setting controls whether files read from file shares over a slow network are transparently cached in the Offline Files cache for future reads. When a user tries to access a file that has been transparently cached, Windows reads from the cached copy after verifying its integrity. This improves end-user response times and decreases bandwidth consumption over WAN links.
-
-The cached files are temporary and are not available to the user when offline. The cached files are not kept in sync with the version on the server, and the most current version from the server is always available for subsequent reads.
-
-This policy setting is triggered by the configured round trip network latency value. We recommend using this policy setting when the network connection to the server is slow. For example, you can configure a value of 60 ms as the round trip latency of the network above which files should be transparently cached in the Offline Files cache. If the round trip latency of the network is less than 60ms, reads to remote files will not be cached.
-
-If you enable this policy setting, transparent caching is enabled and configurable.
-
-If you disable or do not configure this policy setting, remote files will be not be transparently cached on client computers.
- Enable file screens
- This policy setting enables administrators to block certain file types from being created in the folders that have been made available offline.
-
-If you enable this policy setting, a user will be unable to create files with the specified file extensions in any of the folders that have been made available offline.
-
-If you disable or do not configure this policy setting, a user can create a file of any type in the folders that have been made available offline.
- Enable file synchronization on costed networks
- This policy setting determines whether offline files are synchronized in the background when it could result in extra charges on cell phone or broadband plans.
-
-If you enable this setting, synchronization can occur in the background when the user's network is roaming, near, or over the plan's data limit. This may result in extra charges on cell phone or broadband plans.
-
-If this setting is disabled or not configured, synchronization will not run in the background on network folders when the user's network is roaming, near, or over the plan's data limit. The network folder must also be in "slow-link" mode, as specified by the "Configure slow-link mode" policy to avoid network usage.
-
-
-
- Ensures all subfolders are available offline when a folder is made
- available for offline use.
-
-
- Specify network files and folders that are always available offline.
- In the name field, type a fully-qualified UNC path for each file or folder.
- Do not enter a value for the item.
-
- Files and Folders:
-
-
- Specify network files and folders that are always available offline.
- In the name field, type a fully-qualified UNC path for each file or folder.
- Do not enter a value for the item.
-
- Files and Folders:
-
-
- Specify non-default actions for servers that become unavailable.
- Enter a server name paired with an action value listed below.
-
- Customize actions:
- Values:
- 0 = Work offline. Server's files are available to local computer
- 1 = Never go offline. Server's files are unavailable to local computer
-
-
- Specify non-default actions for servers that become unavailable.
- Enter a server name paired with an action value listed below.
-
- Customize actions:
- Values:
- 0 = Work offline. Server's files are available to local computer
- 1 = Never go offline. Server's files are unavailable to local computer
-
-
- Value entered is [ percent disk used * 10,000 ].
- For example, to indicate 12.53%, enter 1253.
-
- Default cache size:
-
-
-
- Enter [0-3]:
-
- 0 = Cache data corrupted
- 1 = Log 'server offline'
- 2 = Level 1 + log 'net stopped' and 'net started'
- 3 = Level 2 + log 'server available for reconnection'
-
-
-
- Enter [0-3]:
-
- 0 = Cache data corrupted
- 1 = Log 'server offline'
- 2 = Level 1 + log 'net stopped' and 'net started'
- 3 = Level 2 + log 'server available for reconnection'
-
-
- Files may be excluded from caching on auto-cache shared folders based
- on their extension. Enter a list of extensions to be excluded. Extensions
- must be preceded by an asterisk and period. e.g. "*.dbf;*.ndx;*.lnk"
-
-
-
-
-
-
- Specify how the system is to respond when a network server
- becomes unavailable.
-
- Action:
-
- Never go offline = Server's files are unavailable to local computer
- Work offline = Server's files are available to local computer
-
-
- Specify how the system is to respond when a network server
- becomes unavailable.
-
- Action:
-
- Never go offline = Server's files are unavailable to local computer
- Work offline = Server's files are available to local computer
-
-
- Prevents users from changing any cache configuration settings.
-
-
- Prevents users from changing any cache configuration settings.
-
-
- Click Show and enter a UNC path for each file or folder
-
- Files and Folders:
-
-
- Click Show and enter a UNC path for each file or folder
-
- Files and Folders:
-
-
- Causes the local copy of any offline file accessed by the user
- to be deleted when the user logs off of the computer.
-
- Delete only the temporary offline files.
-
-
- Number of minutes between reminder balloons
-
- Minutes:
-
-
- Number of minutes between reminder balloons
-
- Minutes:
-
-
- Sets the lifetime of the initial notification balloon displayed
- when an Offline Files event occurs.
-
- Seconds:
-
-
- Sets the lifetime of the initial notification balloon displayed
- when an Offline Files event occurs.
-
- Seconds:
-
-
- Sets the lifetime of the balloon displayed periodically reminding
- users of the current condition of Offline Files.
-
- Seconds:
-
-
- Sets the lifetime of the balloon displayed periodically reminding
- users of the current condition of Offline Files.
-
- Seconds:
-
-
- Value entered is [ bps / 100 ] --> Example: 128,000bps, enter 1280
- Value:
-
-
- Type of synchronization to perform when suspending:
-
- Action:
-
-
- Type of synchronization to perform when suspending:
-
- Action:
-
-
- Enables efficient processing of administratively assigned
- offline files.
-
-
- Allows the administrator to configure when the automatic slow-link transition should happen for the specified UNC paths.
- The UNC path should be specified in the Value Name colume. The thresholds for throughput (in bits per second) and/or latency (in milliseconds) should be specified in the Value column.
- Examples:
- To enable the slow-link mode to apply when network throughput is less than 10000 bits per second and network latency is greater than 50 milliseconds:
- Value Name="*" Value="Throughput=10000, Latency=50"
- To enable the slow-link mode to apply to all shares on a server named "server" when network latency is greater than 50 milliseconds:
- Value Name="\\server\*" Value="Latency=50"
- To enable the slow-link mode to apply to the share named "\\server\share" when network throughput is less than 10000 bits per second:
- Value Name="\\server\share\*" Value="Throughput=10000"
- UNC Paths:
-
-
-
- Value entered is in Megabytes.
-
- Total size of offline files:
- Size of auto-cached files:
-
-
- Configure background sync:
-
- Sync Interval (minutes)
- Sync Variance (minutes)
- Maximum Allowed Time Without A Sync (minutes)
- Blockout Start Time (HHMM)
- HHMM is a value where
- HH must be between 0 and 24, and
- MM must be between 0 and 59.
- Blockout Duration (minutes)
- Enable Background Sync for shares in user selected "Work Offline" mode
-
-
- Enter the network latency value above which network files will be temporarily cached on the client.
-
- Enter network latency value in milliseconds
-
-
-
- Enter semi-colon separated file extensions that you want to be excluded from being made available offline by Offline Files.
- Extensions must be preceded by an asterisk and period. e.g. "*.dbf;*.jpg"
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/P2P-pnrp.adml b/policy_templates/en-US/P2P-pnrp.adml
deleted file mode 100644
index 95a9f11..0000000
--- a/policy_templates/en-US/P2P-pnrp.adml
+++ /dev/null
@@ -1,166 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off Microsoft Peer-to-Peer Networking Services
- This setting turns off Microsoft Peer-to-Peer Networking Services in its entirety, and will cause all dependent applications to stop working.
-
-Peer-to-Peer protocols allow for applications in the areas of RTC, collaboration, content distribution and distributed processing.
-
-If you enable this setting, peer-to-peer protocols will be turned off.
-
-If you disable this setting or do not configure it, the peer-to-peer protocols will be turned on.
- Microsoft Peer-to-Peer Networking Services
- Turn off Multicast Bootstrap
- This setting disables PNRP protocol from advertising the computer or from searching other computers on the local subnet in the global cloud.
-
-The Peer Name Resolution Protocol (PNRP) allows for distributed resolution of a name to an IPV6 address and port number. One of the ways in which PNRP bootstraps itself is by using multicast on the same subnet. That is, PNRP publishes itself on the local subnet, so that other computers can find it when needed.
-
-If you enable this setting, PNRP will not use multicast for bootstrapping. Specifying this registry key will break scenarios where there is no seed server for bootstrap (such as ad hoc networking scenarios).
-
-If you disable this setting, PNRP will use multicast for bootstrapping on the same subnet.
-
-If this setting is not configured, the protocol will revert to using a public registry key to determine whether it will publish the computer or will use multicast to search for other computers on the local subnet.
-
-The multicast protocol used for bootstrapping is SSDP (Simple Service Discovery Protocol). The SSDP service must be enabled (which it is by default) for this policy to have effect.
- Turn off PNRP cloud creation
- Set PNRP cloud to resolve only
- This policy setting enables or disables PNRP cloud creation.
-
-PNRP is a distributed name resolution protocol allowing Internet hosts to publish peer names with a corresponding Internet Protocol version 6 (IPv6) address. Other hosts can then resolve the name, retrieve the corresponding address, and establish peer-to-peer (P2P) connections. The PNRP cloud is a group of connected PNRP nodes, in which connections exist between peers so that a node in the PNRP cloud can resolve names published by other nodes.
-
-PNRP creates a global cloud if the computer has a global IPv6 address, but creates a site-local cloud if the computer has a site-local address.
-
-If you enable this policy setting, PNRP does not create a cloud, and applications cannot use this cloud to publish or resolve names regardless of whether the computer has an IPv6 address that matches the cloud scope.
-
-If you disable or do not configure this policy setting, all PNRP clouds are turned on by default, and PNRP creates a cloud if the computer has an IPv6 address compatible with the cloud’s scope.
-
- This policy setting limits a node to resolving, but not publishing, names in a specific Peer Name Resolution Protocol (PNRP) cloud.
-
-This policy setting forces computers to act as clients in peer-to-peer (P2P) scenarios. For example, a client computer can detect other computers to initiate chat sessions, but other computers cannot detect that client and initiate sessions with it.
-
-If you enable this policy setting, this computer cannot register PNRP names, and cannot help other computers perform PNRP lookups.
-
-If you disable or do not configure this policy setting, this computer can publish PNRP names and help other computers perform PNRP lookups.
-
- This setting disables PNRP protocol from advertising the computer or from searching other computers on the local subnet in the link local cloud.
-
-The Peer Name Resolution Protocol (PNRP) allows for distributed resolution of a name to an IPV6 address and port number. One of the ways in which PNRP bootstraps itself is by using multicast on the same subnet. That is, PNRP publishes itself on the local subnet, so that other computers can find it when needed.
-
-If you enable this setting, PNRP will not use multicast for bootstrapping. Specifying this registry key will break scenarios where there is no seed server for bootstrap (such as ad hoc networking scenarios).
-
-If you disable this setting, PNRP will use multicast for bootstrapping on the same subnet.
-
-If this setting is not configured, the protocol will revert to using a public registry key to determine whether it will publish the computer or will use multicast to search for other computers on the local subnet.
-
-The multicast protocol used for bootstrapping is SSDP (Simple Service Discovery Protocol). The SSDP service must enabled (which it is by default) for this policy to have effect.
- This policy setting enables or disables PNRP cloud creation.
-
-PNRP is a distributed name resolution protocol allowing Internet hosts to publish peer names with a corresponding Internet Protocol version 6 (IPv6) address. Other hosts can then resolve the name, retrieve the corresponding address, and establish peer-to-peer (P2P) connections. The PNRP cloud is a group of connected PNRP nodes, in which connections exist between peers so that a node in the PNRP cloud can resolve names published by other nodes.
-
-PNRP creates a global cloud if the computer has a global IPv6 address, but creates a site-local cloud if the computer has a site-local address.
-
-If you enable this policy setting, PNRP does not create a cloud, and applications cannot use this cloud to publish or resolve names regardless of whether the computer has an IPv6 address that matches the cloud scope.
-
-If you disable or do not configure this policy setting, all PNRP clouds are turned on by default, and PNRP creates a cloud if the computer has an IPv6 address compatible with the cloud’s scope.
-
- This policy setting limits a node to resolving, but not publishing, names in a specific Peer Name Resolution Protocol (PNRP) cloud.
-
-This policy setting forces computers to act as clients in peer-to-peer (P2P) scenarios. For example, a client computer can detect other computers to initiate chat sessions, but other computers cannot detect that client and initiate sessions with it.
-
-If you enable this policy setting, this computer cannot register PNRP names, and cannot help other computers perform PNRP lookups.
-
-If you disable or do not configure this policy setting, this computer can publish PNRP names and help other computers perform PNRP lookups.
-
- This setting disables PNRP protocol from advertising the computer or from searching other computers on the local subnet in the site local cloud.
-
-The Peer Name Resolution Protocol (PNRP) allows for distributed resolution of a name to an IPV6 address and port number. One of the ways in which PNRP bootstraps itself is by using multicast on the same subnet. That is, PNRP publishes itself on the local subnet, so that other computers can find it when needed.
-
-If you enable this setting, PNRP will not use multicast for bootstrapping. Specifying this registry key will break scenarios where there is no seed server for bootstrap (such as ad hoc networking scenarios).
-
-If you disable this setting, PNRP will use multicast for bootstrapping on the same subnet.
-
-If this setting is not configured, the protocol will revert to using a public registry key to determine whether it will publish the computer or will use multicast to search for other computers on the local subnet.
-
-The multicast protocol used for bootstrapping is SSDP (Simple Service Discovery Protocol). The SSDP service must be enabled (which it is by default) for this policy to have effect.
- This policy setting enables or disables PNRP cloud creation.
-
-PNRP is a distributed name resolution protocol allowing Internet hosts to publish peer names with a corresponding Internet Protocol version 6 (IPv6) address. Other hosts can then resolve the name, retrieve the corresponding address, and establish peer-to-peer (P2P) connections. The PNRP cloud is a group of connected PNRP nodes, in which connections exist between peers so that a node in the PNRP cloud can resolve names published by other nodes.
-
-PNRP creates a global cloud if the computer has a global IPv6 address, but creates a site-local cloud if the computer has a site-local address.
-
-If you enable this policy setting, PNRP does not create a cloud, and applications cannot use this cloud to publish or resolve names regardless of whether the computer has an IPv6 address that matches the cloud scope.
-
-If you disable or do not configure this policy setting, all PNRP clouds are turned on by default, and PNRP creates a cloud if the computer has an IPv6 address compatible with the cloud’s scope.
-
- This policy setting limits a node to resolving, but not publishing, names in a specific Peer Name Resolution Protocol (PNRP) cloud.
-
-This policy setting forces computers to act as clients in peer-to-peer (P2P) scenarios. For example, a client computer can detect other computers to initiate chat sessions, but other computers cannot detect that client and initiate sessions with it.
-
-If you enable this policy setting, this computer cannot register PNRP names, and cannot help other computers perform PNRP lookups.
-
-If you disable or do not configure this policy setting, this computer can publish PNRP names and help other computers perform PNRP lookups.
-
- Global Clouds
- Link-Local Clouds
- Peer Name Resolution Protocol
- Set the Seed Server
- This setting sets the seed server for the global cloud to a specified node in the enterprise. The Peer Name Resolution Protocol (PNRP) allows for distributed resolution of a name to an IPv6 address and port number. The protocol, in some cases, requires a seed server from which to get bootstrapped.
-
-Any node running peer to peer can be used as a seed server. No configuration is needed for the seed server itself.
-
-This setting provides the added flexibility of allowing your users to use their peer-to-peer applications at home as well. Here are the four ways in which you can use this setting to control the seed server used in your corporation.
-
-1. In order to use the global, well known seed server on the Internet only; enable the setting, leave the seed server list empty, leave the checkbox unchecked.
-
-2. In order to use a corporate seed server only, enable the setting; insert the fully qualified domain name or IPv6 address of the corporate seed server; and check the checkbox. Using the corporate seed server only will prevent your mobile users from being able to use their peer to peer applications at home.
-
-3. In order to use a corporate seed server and the global seed server, enable the setting; insert the fully qualified domain name or IPv6 address of the corporate seed server, leave the checkbox unchecked. This is the setting which will allow your mobile users to use peer to peer applications at both work and home seamlessly.
-
-4. In order to not use any seed server, enable the setting; do not insert a seed server name; and check the check box.
-
-If this setting is disabled or not configured, the protocol will revert to using a public registry key to determine the seed server to bootstrap from.
- This setting sets the seed server for the link local cloud to a specified node in the enterprise.
-
-The Peer Name Resolution Protocol (PNRP) allows for distributed resolution of a name to an IPV6 address and port number. The protocol, in some cases, requires a seed server from which to get bootstrapped. This setting allows for setting the seed server to a specified node in an enterprise.
-
-To use this setting, click Enable, and then enter a semicolon-delimited list of IPV6 addresses in the available field. If you enable this setting and you don’t enter any address, no seed server will be used.
-
-If this setting is not configured, the protocol will revert to using a public registry key to determine the seed server to bootstrap from.
- This setting sets the seed server for the site local cloud to a specified node in the enterprise.
-
-The Peer Name Resolution Protocol (PNRP) allows for distributed resolution of a name to an IPV6 address and port number. The protocol, in some cases, requires a seed server from which to get bootstrapped. This setting allows for setting the seed server to a specified node in an enterprise.
-
-To use this setting, click Enable, and then enter a semicolon-delimited list of DNS names or IPV6 addresses in the available field. If you enable this setting and you don’t enter any address, no seed server will be used.
-
-If this setting is not configured, the protocol will revert to using a public registry key to determine the seed server to bootstrap from.
- Site-Local Clouds
- Disable password strength validation for Peer Grouping
- By default, when a Peer Group is created that allows for password-authentication (or the password for such a Group is changed), Peer Grouping validates that the password meets the password complexity requirements for the local system. Thus, it will not allow any passwords to be used for a Peer Group that are weaker than what would be allowed for a login password.
-
-This setting controls this validation behavior. If set to 1, then this validation will not be performed and any password will be allowed. If set to 0, the validation will be performed.
-
-
-
-
-
-
-
- Do not use the Microsoft global PNRP seed server
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/Passport.adml b/policy_templates/en-US/Passport.adml
deleted file mode 100644
index d8363e1..0000000
--- a/policy_templates/en-US/Passport.adml
+++ /dev/null
@@ -1,263 +0,0 @@
-
-
-
- Windows Hello for Business
- Configuration for Windows Hello for Business
-
-
- Windows Hello for Business
- PIN Complexity
- Use Windows Hello for Business
-
- Use certificate for on-premises authentication
-
- Use cloud trust for on-premises authentication
-
- Windows Hello for Business is an alternative method for signing into Windows using your Active Directory or Azure Active Directory account that can replace passwords, Smart Cards, and Virtual Smart Cards.
-
-If you enable this policy, the device provisions Windows Hello for Business using keys or certificates for all users.
-
-If you disable this policy setting, the device does not provision Windows Hello for Business for any user.
-
-If you do not configure this policy setting, users can provision Windows Hello for Business as a convenience credential that encrypts their domain password.
-
-Select "Do not start Windows Hello provisioning after sign-in" when you use a third-party solution to provision Windows Hello for Business.
-
-If you select "Do not start Windows Hello provisioning after sign-in", Windows Hello for Business does not automatically start provisioning after the user has signed in.
-
-If you do not select "Do not start Windows Hello provisioning after sign-in", Windows Hello for Business automatically starts provisioning after the user has signed in.
-
-
- Use a hardware security device
- A Trusted Platform Module (TPM) provides additional security benefits over software because data protected by it cannot be used on other devices.
-
-If you enable this policy setting, Windows Hello for Business provisioning only occurs on devices with usable 1.2 or 2.0 TPMs. You can optionally exclude security devices, which prevents Windows Hello for Business provisioning from using those devices.
-
-If you disable or do not configure this policy setting, the TPM is still preferred, but all devices may provision Windows Hello for Business using software if the TPM is non-functional or unavailable.
-
- Minimum PIN length
- Minimum PIN length configures the minimum number of characters required for the PIN. The lowest number you can configure for this policy setting is 4. The largest number you can configure must be less than the number configured in the Maximum PIN length policy setting or the number 127, whichever is the lowest.
-
-If you configure this policy setting, the PIN length must be greater than or equal to this number.
-
-If you disable or do not configure this policy setting, the PIN length must be greater than or equal to 6.
-
-NOTE: If the above specified conditions for the minimum PIN length are not met, default values will be used for both the maximum and minimum PIN lengths.
-
- Maximum PIN length
- Maximum PIN length configures the maximum number of characters allowed for the PIN. The largest number you can configure for this policy setting is 127. The lowest number you can configure must be larger than the number configured in the Minimum PIN length policy setting or the number 4, whichever is greater.
-
-If you configure this policy setting, the PIN length must be less than or equal to this number.
-
-If you disable or do not configure this policy setting, the PIN length must be less than or equal to 127.
-
-NOTE: If the above specified conditions for the maximum PIN length are not met, default values will be used for both the maximum and minimum PIN lengths.
-
- Require uppercase letters
- Use this policy setting to configure the use of uppercase letters in the PIN.
-
-If you enable this policy setting, Windows requires the user to include at least one uppercase letter in their PIN.
-
-If you disable this policy setting, Windows does not allow the user to include uppercase letters in their PIN.
-
-If you do not configure this policy setting, Windows allows, but does not require, uppercase letters in the PIN.
-
- Require lowercase letters
- Use this policy setting to configure the use of lowercase letters in the PIN.
-
-If you enable this policy setting, Windows requires the user to include at least one lowercase letter in their PIN.
-
-If you disable this policy setting, Windows does not allow the user to include lowercase letters in their PIN.
-
-If you do not configure this policy setting, Windows allows, but does not require, lowercase letters in the PIN.
-
- Require special characters
- ? @ [ \ ] ^ _ ` { | } ~ .
-
-If you enable this policy setting, Windows requires the user to include at least one special character in their PIN.
-
-If you disable this policy setting, Windows does not allow the user to include special characters in their PIN.
-
-If you do not configure this policy setting, Windows allows, but does not require, special characters in the PIN.]]>
-
- Require digits
- Use this policy setting to configure the use of digits in the PIN.
-
-If you enable this policy setting, Windows requires the user to include at least one digit in their PIN.
-
-If you disable this policy setting, Windows does not allow the user to include digits in their PINs.
-
-If you do not configure this policy setting, Windows allows, but does not require, digits in the PIN.
-
- History
- This setting specifies the number of past PINs that can be associated to a user account that can’t be reused. This policy enables administrators to enhance security by ensuring that old PINs are not reused continually. PIN history is not preserved through PIN reset.
-
-The value must be between 0 to 50 PINs. If this policy is set to 0, then storage of previous PINs is not required.
-
-Default: 0.
-
- Expiration
- This setting specifies the period of time (in days) that a PIN can be used before the system requires the user to change it. The PIN can be set to expire after any number of days between 1 and 730, or PINs can be set to never expire if the policy is set to 0.
-
-Default: 0.
-
- Use biometrics
- Windows Hello for Business enables users to use biometric gestures, such as face and fingerprints, as an alternative to the PIN gesture. However users must still configure a PIN to use in case of failures.
-
-If you enable or do not configure this policy setting, Windows Hello for Business allows the use biometric gestures.
-
-If you disable this policy setting, Windows Hello for Business prevents the use of biometric gestures.
-
-NOTE: Disabling this policy prevents the user of biometric gestures on the device for all account types.
-
- Enable ESS with Supported Peripherals
- Enhanced Sign-in Security (ESS) isolates Windows Hello biometric (face and fingerprint) template data and matching operations to trusted hardware or specified memory regions, meaning the rest of the operating system cannot access or tamper with them. Because the channel of communication between the sensors and the algorithm is also secured, it is impossible for malware to inject or replay data in order to simulate a user signing in or to lock a user out of their machine.
-If you enable this policy then it can have following possible values:
-
-0 - Enhanced Sign-in Security Enabled with peripheral and built-in non-ESS sensors
-Enhanced sign-in security will be enabled on systems with capable software and hardware, following the existing default behavior in Windows. Authentication operations of peripheral Windows Hello capable devices will be allowed, subject to current feature limitations. In addition, with this setting, ESS will be enabled on devices with a mixture of biometric devices, such as an ESS capable FPR and a non-ESS capable camera.
-
-1 - Enhanced Sign-in Security Enabled without peripheral or built-in non-ESS sensors (default and recommended for highest security)
-Enhanced sign-in security will be enabled on systems with capable software and hardware, following the existing default behavior in Windows. Authentication operations of any peripheral biometric device will be blocked and not available for Windows Hello.
-
-If you disable or not configure this policy then non-ESS sensors will be blocked on the ESS device.
-
- Use PIN Recovery
- PIN recovery enables a user to change a forgotten PIN using the Windows Hello for Business PIN recovery service, without losing any associated credentials or certificates, including any keys associated with the user's personal accounts on the device. To achieve this, the Azure-based PIN recovery service encrypts a recovery secret, which is stored on the device, and requires both the PIN recovery service and the device to decrypt. PIN recovery requires the user to perform multi-factor authentication to Azure Active Directory.
-
-If you enable this policy setting, Windows Hello for Business uses the PIN recovery service.
-
-If you disable or do not configure this policy setting, Windows does not create or store the PIN recovery secret. If the user forgets their PIN, they must delete their existing PIN and create a new one, and they will have to to re-register with any services to which the old PIN provided access.
-
-NOTE: This policy is only applicable to devices which are registered with Azure Active Directory.
-
-
- Use this policy setting to configure Windows Hello for Business to enroll a sign-in certificate used for on-premises authentication.
-
-If you enable this policy setting, Windows Hello for Business enrolls a sign-in certificate that is used for on-premises authentication.
-
-If you disable or do not configure this policy setting, Windows Hello for Business will use a key or a Kerberos ticket (depending on other policy settings) for on-premises authentication.
-
-NOTE: Disabling or not configuring this policy setting and enabling the "Use Windows Hello for Business" policy setting requires the environment to have one or more Windows Server 2016 domain controllers to prevent Windows Hello for Business authentication from failing.
-
-
- Use this policy setting to configure Windows Hello for Business to use Azure AD Kerberos for on-premises authentication.
-
-If you enable this policy setting, Windows Hello for Business will use a Kerberos ticket retrieved from authenticating to Azure for on-premises authentication.
-
-If you disable or do not configure this policy setting, Windows Hello for Business will use a key or certificate (depending on other policy settings) for on-premises authentication.
-
-NOTE: An environment that enables both this policy setting, and the "Use Windows Hello for Business" policy setting requires one or more Windows Server 2016 domain controllers. Otherwise, Windows Hello for Business authentication will fail.
-
-
- Configure device unlock factors
- Configure a comma separated list of credential provider GUIDs, such as face and fingerprint provider GUIDs, to be used as the first and second unlock factors. If the trusted signal provider is specified as one of the unlock factors, you should also configure a comma separated list of signal rules in the form of xml for each signal type to be verified.
-
-If you enable this policy setting, the user will have to use one factor from each list to successfully unlock.
-
-If you disable or do not configure this policy setting, users can continue to unlock with existing unlock options.
-
-For more information see: https://go.microsoft.com/fwlink/?linkid=849684
-
-
- Configure dynamic lock factors
- Configure a comma separated list of signal rules in the form of xml for each signal type.
-
-If you enable this policy setting, these signal rules will be evaluated to detect user absence and automatically lock the device.
-
-If you disable or do not configure this policy setting, users can continue to lock with existing locking options.
-
-For more information see: https://go.microsoft.com/fwlink/?linkid=849684
-
-
- Turn off smart card emulation
- Windows Hello for Business automatically provides smart card emulation for compatibility with smart card enabled applications.
-
-If you enable this policy setting, Windows Hello for Business provisions Windows Hello for Business credentials that are not compatible with smart card applications.
-
-If you disable or do not configure this policy setting, Windows Hello for Business provisions Windows Hello for Business credentials compatible with smart card applications.
-
-NOTE: This policy affects Windows Hello for Business credentials at the time of creation. Credentials created before the application of this policy continue to provide smart card emulation. To change an existing credential, enable this policy setting and select "I forgot my PIN" from Settings.
-
- Allow enumeration of emulated smart card for all users
- Windows prevents users on the same computer from enumerating provisioned Windows Hello for Business credentials for other users.
-
-If you enable this policy setting, Windows allows all users of the computer to enumerate all Windows Hello for Business credentials, but still require each user to provide their own factors for authentication.
-
-If you disable or do not configure this policy setting, Windows does not allow the enumeration of provisioned Windows Hello for Business credentials for other users on the same device.
-
-This policy setting is designed for a single user who has enrolled privileged and non-privileged on a single device. The user owns both credentials, which enables them to sign-in using non-privileged credentials, but can performed elevated tasks without signing-out.
-
-This policy setting is incompatible with Windows Hello for Business credentials provisioned when the "Turn off smart card emulation" is enabled.
-
-Windows requires a reboot after you apply this setting to a computer.
-
-
- Use Windows Hello for Business certificates as smart card certificates
- If you enable this policy setting, applications use Windows Hello for Business certificates as smart card certificates. Biometric factors are unavailable when a user is asked to authorize the use of the certificate's private key. This policy setting is designed to allow compatibility with applications that rely exclusively on smart card certificates.
-
-If you disable or do not configure this policy setting, applications do not use Windows Hello for Business certificates as smart card certificates, and biometric factors are available when a user is asked to authorize the use of the certificate's private key.
-
-This policy setting is incompatible with Windows Hello for Business credentials provisioned when the "Turn off smart card emulation" is enabled.
-
-Windows requires a user to lock and unlock their session after changing this setting if the user is currently signed in.
-
-
-
-
- Enable ESS with Supported Peripherals
-
-
- Minimum PIN length
-
-
- Maximum PIN length
-
-
- Uppercase letters:
-
-
- Lowercase letters:
-
-
- Special characters:
-
-
- digits:
-
-
- PIN History
-
-
- PIN Expiration
-
-
- Do not use the following security devices:
- TPM 1.2
-
-
- Do not start Windows Hello provisioning after sign-in
-
-
-
-
- {D6886603-9D2F-4EB2-B667-1971041FA96B},{8AF662BF-65A0-4D0A-A540-A338A999D36F},{BEC09223-B018-416D-A0AC-523971B639F5}
-
-
-
- {27FBDB57-B613-4AF2-9D7E-4FA7A66C21AD},{D6886603-9D2F-4EB2-B667-1971041FA96B}
-
-
-
- ]]>
-
-
-
-
-
- ]]>
-
-
-
-
-
diff --git a/policy_templates/en-US/PeerToPeerCaching.adml b/policy_templates/en-US/PeerToPeerCaching.adml
deleted file mode 100644
index 739dc47..0000000
--- a/policy_templates/en-US/PeerToPeerCaching.adml
+++ /dev/null
@@ -1,283 +0,0 @@
-
-
-
- BranchCache
- BranchCache enables clients to securely retrieve content from within the branch office instead of having to retrieve it from the server hosting the content. Depending on the deployment mode, the content can be retrieved from other clients in the branch office or from a hosted cache server in the branch. A client can only retrieve content from within the branch if it is authorized by the server to do so. The use of BranchCache reduces costs on the wide area network (WAN) link that connects your branch offices to the data center or headquarters and increases download speeds for content that has already been downloaded into the branch office.
-
-
-
-
-
- At least Windows 7 or Windows Server 2008 R2*
-
-
- BranchCache
-
- Turn on BranchCache
-
- This policy setting specifies whether BranchCache is enabled on client computers to which this policy is applied. In addition to this policy setting, you must specify whether the client computers are hosted cache mode or distributed cache mode clients. To do so, configure one of the following the policy settings:
-
-- Set BranchCache Distributed Cache mode
-
-- Set BranchCache Hosted Cache mode
-
-- Configure Hosted Cache Servers
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, BranchCache settings are not applied to client computers by this policy. In the circumstance where client computers are domain members but you do not want to enable BranchCache on all client computers, you can specify Not Configured for this domain Group Policy setting, and then configure local computer policy to enable BranchCache on individual client computers. Because the domain Group Policy setting is not configured, it will not over-write the enabled setting that you use on individual client computers where you want to enable BranchCache.
-
-- Enabled. With this selection, BranchCache is turned on for all client computers where the policy is applied. For example, if this policy is enabled in domain Group Policy, BranchCache is turned on for all domain member client computers to which the policy is applied.
-
-- Disabled. With this selection, BranchCache is turned off for all client computers where the policy is applied.
-
-* This policy setting is supported on computers that are running Windows Vista Business, Enterprise, and Ultimate editions with Background Intelligent Transfer Service (BITS) 4.0 installed.
-
-
- Set percentage of disk space used for client computer cache
-
- This policy setting specifies the default percentage of total disk space that is allocated for the BranchCache disk cache on client computers.
-
-If you enable this policy setting, you can configure the percentage of total disk space to allocate for the cache.
-
-If you disable or do not configure this policy setting, the cache is set to 5 percent of the total disk space on the client computer.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, BranchCache client computer cache settings are not applied to client computers by this policy. In the circumstance where client computers are domain members but you do not want to configure a BranchCache client computer cache setting on all client computers, you can specify Not Configured for this domain Group Policy setting, and then configure local computer policy to enable BranchCache client computer cache settings on individual client computers. Because the domain Group Policy setting is not configured, it will not over-write the client computer cache setting that you use on individual client computers.
-
-- Enabled. With this selection, the BranchCache client computer cache setting is enabled for all client computers where the policy is applied. For example, if Set percentage of disk space used for client computer cache is enabled in domain Group Policy, the BranchCache client computer cache setting that you specify in the policy is turned on for all domain member client computers to which the policy is applied.
-
-- Disabled. With this selection, BranchCache client computers use the default client computer cache setting of five percent of the total disk space on the client computer.
-
-In circumstances where this setting is enabled, you can also select and configure the following option:
-
-- Specify the percentage of total disk space allocated for the cache. Specifies an integer that is the percentage of total client computer disk space to use for the BranchCache client computer cache.
-
-* This policy setting is supported on computers that are running Windows Vista Business, Enterprise, and Ultimate editions with Background Intelligent Transfer Service (BITS) 4.0 installed.
-
-
- Set BranchCache Hosted Cache mode
-
- This policy setting specifies whether BranchCache hosted cache mode is enabled on client computers to which this policy is applied. In addition to this policy, you must use the policy "Turn on BranchCache" to enable BranchCache on client computers.
-
-When a client computer is configured as a hosted cache mode client, it is able to download cached content from a hosted cache server that is located at the branch office. In addition, when the hosted cache client obtains content from a content server, the client can upload the content to the hosted cache server for access by other hosted cache clients at the branch office.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, BranchCache settings are not applied to client computers by this policy. In the circumstance where client computers are domain members but you do not want to enable BranchCache on all client computers, you can specify Not Configured for this domain Group Policy setting, and then configure local computer policy to enable BranchCache on individual client computers. Because the domain Group Policy setting is not configured, it will not over-write the enabled setting that you use on individual client computers where you want to enable BranchCache.
-
-- Enabled. With this selection, BranchCache hosted cache mode is enabled for all client computers where the policy is applied. For example, if this policy is enabled in domain Group Policy, BranchCache hosted cache mode is turned on for all domain member client computers to which the policy is applied.
-
-- Disabled. With this selection, BranchCache hosted cache mode is turned off for all client computers where the policy is applied.
-
-In circumstances where this setting is enabled, you can also select and configure the following option:
-
-- Type the name of the hosted cache server. Specifies the computer name of the hosted cache server. Because the hosted cache server name is also specified in the certificate enrolled to the hosted cache server, the name that you enter here must match the name of the hosted cache server that is specified in the server certificate.
-
-Hosted cache clients must trust the server certificate that is issued to the hosted cache server. Ensure that the issuing CA certificate is installed in the Trusted Root Certification Authorities certificate store on all hosted cache client computers.
-
-* This policy setting is supported on computers that are running Windows Vista Business, Enterprise, and Ultimate editions with Background Intelligent Transfer Service (BITS) 4.0 installed.
-
-
- Set BranchCache Distributed Cache mode
-
- This policy setting specifies whether BranchCache distributed cache mode is enabled on client computers to which this policy is applied. In addition to this policy, you must use the policy "Turn on BranchCache" to enable BranchCache on client computers.
-
-In distributed cache mode, client computers download content from BranchCache-enabled main office content servers, cache the content locally, and serve the content to other BranchCache distributed cache mode clients in the branch office.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, BranchCache settings are not applied to client computers by this policy. In the circumstance where client computers are domain members but you do not want to enable BranchCache on all client computers, you can specify Not Configured for this domain Group Policy setting, and then configure local computer policy to enable BranchCache on individual client computers. Because the domain Group Policy setting is not configured, it will not over-write the enabled setting that you use on individual client computers where you want to enable BranchCache.
-
-- Enabled. With this selection, BranchCache distributed cache mode is enabled for all client computers where the policy is applied. For example, if this policy is enabled in domain Group Policy, BranchCache distributed cache mode is turned on for all domain member client computers to which the policy is applied.
-
-- Disabled. With this selection, BranchCache distributed cache mode is turned off for all client computers where the policy is applied.
-
-* This policy setting is supported on computers that are running Windows Vista Business, Enterprise, and Ultimate editions with Background Intelligent Transfer Service (BITS) 4.0 installed.
-
-
- Configure BranchCache for network files
-
- This policy setting is used only when you have deployed one or more BranchCache-enabled file servers at your main office. This policy setting specifies when client computers in branch offices start caching content from file servers based on the network latency - or delay - that occurs when the clients download content from the main office over a Wide Area Network (WAN) link. When you configure a value for this setting, which is the maximum round trip network latency allowed before caching begins, clients do not cache content until the network latency reaches the specified value; when network latency is greater than the value, clients begin caching content after they receive it from the file servers.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, BranchCache latency settings are not applied to client computers by this policy. In the circumstance where client computers are domain members but you do not want to configure a BranchCache latency setting on all client computers, you can specify Not Configured for this domain Group Policy setting, and then configure local computer policy to enable BranchCache latency settings on individual client computers. Because the domain Group Policy setting is not configured, it will not over-write the latency setting that you use on individual client computers.
-
-- Enabled. With this selection, the BranchCache maximum round trip latency setting is enabled for all client computers where the policy is applied. For example, if Configure BranchCache for network files is enabled in domain Group Policy, the BranchCache latency setting that you specify in the policy is turned on for all domain member client computers to which the policy is applied.
-
-- Disabled. With this selection, BranchCache client computers use the default latency setting of 80 milliseconds.
-
-In circumstances where this policy setting is enabled, you can also select and configure the following option:
-
-- Type the maximum round trip network latency (milliseconds) after which caching begins. Specifies the amount of time, in milliseconds, after which BranchCache client computers begin to cache content locally.
-
-
- Enable Automatic Hosted Cache Discovery by Service Connection Point
-
- This policy setting specifies whether client computers should attempt the automatic configuration of hosted cache mode by searching for hosted cache servers publishing service connection points that are associated with the client's current Active Directory site. If you enable this policy setting, client computers to which the policy setting is applied search for hosted cache servers using Active Directory, and will prefer both these servers and hosted cache mode rather than manual BranchCache configuration or BranchCache configuration by other group policies.
-
-If you enable this policy setting in addition to the "Turn on BranchCache" policy setting, BranchCache clients attempt to discover hosted cache servers in the local branch office. If client computers detect hosted cache servers, hosted cache mode is turned on. If they do not detect hosted cache servers, hosted cache mode is not turned on, and the client uses any other configuration that is specified manually or by Group Policy.
-
-When this policy setting is applied, the client computer performs or does not perform automatic hosted cache server discovery under the following circumstances:
-
-If no other BranchCache mode-based policy settings are applied, the client computer performs automatic hosted cache server discovery. If one or more hosted cache servers is found, the client computer self-configures for hosted cache mode.
-
-If the policy setting "Set BranchCache Distributed Cache Mode" is applied in addition to this policy, the client computer performs automatic hosted cache server discovery. If one or more hosted cache servers are found, the client computer self-configures for hosted cache mode only.
-
-If the policy setting "Set BranchCache Hosted Cache Mode" is applied, the client computer does not perform automatic hosted cache discovery. This is also true in cases where the policy setting "Configure Hosted Cache Servers" is applied.
-
-This policy setting can only be applied to client computers that are running at least Windows 8. This policy has no effect on computers that are running Windows 7 or Windows Vista.
-
-If you disable, or do not configure this setting, a client will not attempt to discover hosted cache servers by service connection point.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, BranchCache settings are not applied to client computers by this policy setting, and client computers do not perform hosted cache server discovery.
-
-- Enabled. With this selection, the policy setting is applied to client computers, which perform automatic hosted cache server discovery and which are configured as hosted cache mode clients.
-
-- Disabled. With this selection, this policy is not applied to client computers.
-
-
- Configure Hosted Cache Servers
-
- This policy setting specifies whether client computers are configured to use hosted cache mode and provides the computer name of the hosted cache servers that are available to the client computers. Hosted cache mode enables client computers in branch offices to retrieve content from one or more hosted cache servers that are installed in the same office location. You can use this setting to automatically configure client computers that are configured for hosted cache mode with the computer names of the hosted cache servers in the branch office.
-
-If you enable this policy setting and specify valid computer names of hosted cache servers, hosted cache mode is enabled for all client computers to which the policy setting is applied. For this policy setting to take effect, you must also enable the "Turn on BranchCache" policy setting.
-
-This policy setting can only be applied to client computers that are running at least Windows 8. This policy has no effect on computers that are running Windows 7 or Windows Vista. Client computers to which this policy setting is applied, in addition to the "Set BranchCache Hosted Cache mode" policy setting, use the hosted cache servers that are specified in this policy setting and do not use the hosted cache server that is configured in the policy setting "Set BranchCache Hosted Cache Mode."
-
-If you do not configure this policy setting, or if you disable this policy setting, client computers that are configured with hosted cache mode still function correctly.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, BranchCache settings are not applied to client computers by this policy setting.
-
-- Enabled. With this selection, the policy setting is applied to client computers, which are configured as hosted cache mode clients that use the hosted cache servers that you specify in "Hosted cache servers."
-
-- Disabled. With this selection, this policy is not applied to client computers.
-
-In circumstances where this setting is enabled, you can also select and configure the following option:
-
-- Hosted cache servers. To add hosted cache server computer names to this policy setting, click Enabled, and then click Show. The Show Contents dialog box opens. Click Value, and then type the computer names of the hosted cache servers.
-
-
- Configure Client BranchCache Version Support
-
- This policy setting specifies whether BranchCache-capable client computers operate in a downgraded mode in order to maintain compatibility with previous versions of BranchCache. If client computers do not use the same BranchCache version, cache efficiency might be reduced because client computers that are using different versions of BranchCache might store cache data in incompatible formats.
-
-If you enable this policy setting, all clients use the version of BranchCache that you specify in "Select from the following versions."
-
-If you do not configure this setting, all clients will use the version of BranchCache that matches their operating system.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, this policy setting is not applied to client computers, and the clients run the version of BranchCache that is included with their operating system.
-
-- Enabled. With this selection, this policy setting is applied to client computers based on the value of the option setting "Select from the following versions" that you specify.
-
-- Disabled. With this selection, this policy setting is not applied to client computers, and the clients run the version of BranchCache that is included with their operating system.
-
-In circumstances where this setting is enabled, you can also select and configure the following option:
-
-Select from the following versions
-
-- Windows Vista with BITS 4.0 installed, Windows 7, or Windows Server 2008 R2. If you select this version, later versions of Windows run the version of BranchCache that is included in these operating systems rather than later versions of BranchCache.
-
-- Windows 8. If you select this version, Windows 8 will run the version of BranchCache that is included in the operating system.
-
-
- Windows Vista with BITS 4.0 installed, Windows 7, or Windows Server 2008 R2
- Windows 8
-
- Set age for segments in the data cache
-
- This policy setting specifies the default age in days for which segments are valid in the BranchCache data cache on client computers.
-
-If you enable this policy setting, you can configure the age for segments in the data cache.
-
-If you disable or do not configure this policy setting, the age is set to 28 days.
-
-Policy configuration
-
-Select one of the following:
-
-- Not Configured. With this selection, BranchCache client computer cache age settings are not applied to client computers by this policy. In the circumstance where client computers are domain members but you do not want to configure a BranchCache client computer cache age setting on all client computers, you can specify Not Configured for this domain Group Policy setting, and then configure local computer policy to enable BranchCache client computer cache age settings on individual client computers. Because the domain Group Policy setting is not configured, it will not over-write the client computer cache age setting that you use on individual client computers.
-
-- Enabled. With this selection, the BranchCache client computer cache age setting is enabled for all client computers where the policy is applied. For example, if this policy setting is enabled in domain Group Policy, the BranchCache client computer cache age that you specify in the policy is turned on for all domain member client computers to which the policy is applied.
-
-- Disabled. With this selection, BranchCache client computers use the default client computer cache age setting of 28 days on the client computer.
-
-In circumstances where this setting is enabled, you can also select and configure the following option:
-
-- Specify the age in days for which segments in the data cache are valid.
-
-
-
-
-
-
-
-
-
-
-
- Specify the percentage of total disk space allocated for the cache
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Type the maximum round trip network latency (milliseconds) after which caching begins
-
-
-
-
-
- Hosted cache servers
-
-
-
-
- Select from the following versions:
-
-
-
- Specify the age in days for which segments in the data cache are valid
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/PenTraining.adml b/policy_templates/en-US/PenTraining.adml
deleted file mode 100644
index e189829..0000000
--- a/policy_templates/en-US/PenTraining.adml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Tablet PC Pen Training
- Turn off Tablet PC Pen Training
- Turns off Tablet PC Pen Training.
-
-If you enable this policy setting, users cannot open Tablet PC Pen Training.
-
-If you disable or do not configure this policy setting, users can open Tablet PC Pen Training.
- Turns off Tablet PC Pen Training.
-
-If you enable this policy setting, users cannot open Tablet PC Pen Training.
-
-If you disable or do not configure this policy setting, users can open Tablet PC Pen Training.
-
-
-
diff --git a/policy_templates/en-US/PerformanceDiagnostics.adml b/policy_templates/en-US/PerformanceDiagnostics.adml
deleted file mode 100644
index ea28356..0000000
--- a/policy_templates/en-US/PerformanceDiagnostics.adml
+++ /dev/null
@@ -1,83 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Windows Boot Performance Diagnostics
- Determines the execution level for Windows Boot Performance Diagnostics.
-
-If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Boot Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will detect Windows Boot Performance problems and indicate to the user that assisted resolution is available.
-
-If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve any Windows Boot Performance problems that are handled by the DPS.
-
-If you do not configure this policy setting, the DPS will enable Windows Boot Performance for resolution by default.
-
-This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
-
-No system restart or service restart is required for this policy to take effect: changes take effect immediately.
-
-This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
- Windows Standby/Resume Performance Diagnostics
- Determines the execution level for Windows Standby/Resume Performance Diagnostics.
-
-If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Standby/Resume Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will detect Windows Standby/Resume Performance problems and indicate to the user that assisted resolution is available.
-
-If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve any Windows Standby/Resume Performance problems that are handled by the DPS.
-
-If you do not configure this policy setting, the DPS will enable Windows Standby/Resume Performance for resolution by default.
-
-This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
-
-No system restart or service restart is required for this policy to take effect: changes take effect immediately.
-
-This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
- Windows System Responsiveness Performance Diagnostics
- Determines the execution level for Windows System Responsiveness Diagnostics.
-
-If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows System Responsiveness problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will detect Windows System Responsiveness problems and indicate to the user that assisted resolution is available.
-
-If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve any Windows System Responsiveness problems that are handled by the DPS.
-
-If you do not configure this policy setting, the DPS will enable Windows System Responsiveness for resolution by default.
-
-This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
-
-No system restart or service restart is required for this policy to take effect: changes take effect immediately.
-
-This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
- Windows Shutdown Performance Diagnostics
- Determines the execution level for Windows Shutdown Performance Diagnostics.
-
-If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Shutdown Performance problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will detect Windows Shutdown Performance problems and indicate to the user that assisted resolution is available.
-
-If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve any Windows Shutdown Performance problems that are handled by the DPS.
-
-If you do not configure this policy setting, the DPS will enable Windows Shutdown Performance for resolution by default.
-
-This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
-
-No system restart or service restart is required for this policy to take effect: changes take effect immediately.
-
-This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
- Configure Scenario Execution Level
- Detection, Troubleshooting and Resolution
- Detection and Troubleshooting Only
-
-
-
- Scenario Execution Level
-
-
- Scenario Execution Level
-
-
- Scenario Execution Level
-
-
- Scenario Execution Level
-
-
-
-
diff --git a/policy_templates/en-US/Power.adml b/policy_templates/en-US/Power.adml
deleted file mode 100644
index ae0e49d..0000000
--- a/policy_templates/en-US/Power.adml
+++ /dev/null
@@ -1,454 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn on the ability for applications to prevent sleep transitions (plugged in)
- Specify the system hibernate timeout (plugged in)
- Select the Power button action (plugged in)
- Require a password when a computer wakes (plugged in)
- Select the Sleep button action (plugged in)
- Select the Start menu Power button action (plugged in)
- Specify the system sleep timeout (plugged in)
- Turn off hybrid sleep (plugged in)
- Select the lid switch action (plugged in)
- Allow network connectivity during connected-standby (plugged in)
- This policy setting specifies the action that Windows takes when battery capacity reaches the critical battery notification level.
-
-If you enable this policy setting, select one of the following actions:
--Take no action
--Sleep
--Hibernate
--Shut down
-
-If you disable or do not configure this policy setting, users control this setting.
- This policy setting specifies the action that Windows takes when battery capacity reaches the low battery notification level.
-
-If you enable this policy setting, select one of the following actions:
--Take no action
--Sleep
--Hibernate
--Shut down
-
-If you disable or do not configure this policy setting, users control this setting.
- This policy setting specifies the percentage of battery capacity remaining that triggers the critical battery notification action.
-
-If you enable this policy setting, you must enter a numeric value (percentage) to set the battery level that triggers the critical notification.
-
-To set the action that is triggered, see the "Critical Battery Notification Action" policy setting.
-
-If you disable this policy setting or do not configure it, users control this setting.
- This policy setting specifies the percentage of battery capacity remaining that triggers the low battery notification action.
-
-If you enable this policy setting, you must enter a numeric value (percentage) to set the battery level that triggers the low notification.
-
-To set the action that is triggered, see the "Low Battery Notification Action" policy setting.
-
-If you disable this policy setting or do not configure it, users control this setting.
- This policy setting turns off the user notification when the battery capacity remaining equals the low battery notification level.
-
-If you enable this policy setting, Windows shows a notification when the battery capacity remaining equals the low battery notification level. To configure the low battery notification level, see the "Low Battery Notification Level" policy setting.
-
-The notification will only be shown if the "Low Battery Notification Action" policy setting is configured to "No Action".
-
-If you disable or do not configure this policy setting, users can control this setting.
- Hibernate
- Take no action
- Shut down
- Sleep
- This policy setting allows you to turn on the ability for applications and services to prevent the system from sleeping.
-
-If you enable this policy setting, an application or service may prevent the system from sleeping (Hybrid Sleep, Stand By, or Hibernate).
-
-If you disable or do not configure this policy setting, users control this setting.
- Specify a custom active power plan
- This policy setting specifies the active power plan from a specified power plan’s GUID. The GUID for a custom power plan GUID can be retrieved by using powercfg, the power configuration command line tool.
-
-If you enable this policy setting, you must specify a power plan, specified as a GUID using the following format: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX (For example, 103eea6e-9fcd-4544-a713-c282d8e50083), indicating the power plan to be active.
-
-If you disable or do not configure this policy setting, users can see and change this setting.
- Critical battery notification action
- Low battery notification action
- Critical battery notification level
- Low battery notification level
- Turn off low battery user notification
- Turn on the ability for applications to prevent sleep transitions (on battery)
- Specify the system hibernate timeout (on battery)
- Select the Power button action (on battery)
- Require a password when a computer wakes (on battery)
- Select the Sleep button action (on battery)
- Select the Start menu Power button action (on battery)
- Specify the system sleep timeout (on battery)
- Turn off hybrid sleep (on battery)
- Select the lid switch action (on battery)
- Allow network connectivity during connected-standby (on battery)
- Turn Off the hard disk (plugged in)
- Turn Off the hard disk (on battery)
- This policy setting specifies the period of inactivity before Windows turns off the hard disk.
-
-If you enable this policy setting, you must provide a value, in seconds, indicating how much idle time should elapse before Windows turns off the hard disk.
-
-If you disable or do not configure this policy setting, users can see and change this setting.
- Do not turn off system power after a Windows system shutdown has occurred.
- This policy setting allows you to configure whether power is automatically turned off when Windows shutdown completes. This setting does not affect Windows shutdown behavior when shutdown is manually selected using the Start menu or Task Manager user interfaces. Applications such as UPS software may rely on Windows shutdown behavior.
-
-This setting is only applicable when Windows shutdown is initiated by software programs invoking the Windows programming interfaces ExitWindowsEx() or InitiateSystemShutdown().
-
-If you enable this policy setting, the computer system safely shuts down and remains in a powered state, ready for power to be safely removed.
-
-If you disable or do not configure this policy setting, the computer system safely shuts down to a fully powered-off state.
- This policy setting allows you to specify the period of inactivity before Windows transitions the system to hibernate.
-
-If you enable this policy setting, you must provide a value, in seconds, indicating how much idle time should elapse before Windows transitions to hibernate.
-
-If you disable or do not configure this policy setting, users control this setting.
-
-If the user has configured a slide show to run on the lock screen when the machine is locked, this can prevent the sleep transition from occuring. The "Prevent enabling lock screen slide show" policy setting can be used to disable the slide show feature.
- Select an active power plan
- This policy setting specifies the active power plan from a list of default Windows power plans. To specify a custom power plan, use the Custom Active Power Plan setting.
-
-If you enable this policy setting, specify a power plan from the Active Power Plan list.
-
-If you disable or do not configure this policy setting, users control this setting.
- Power Saver
- High Performance
- Automatic (recommended)
- Notification Settings
- This policy setting specifies the action that Windows takes when a user presses the power button.
-
-Possible actions include:
--Take no action
--Sleep
--Hibernate
--Shut down
-
-If you enable this policy setting, you must select the desired action.
-
-If you disable this policy setting or do not configure it, users can see and change this setting.
- Button Settings
- Hard Disk Settings
- Power Management
- Sleep Settings
- Video and Display Settings
- This policy setting specifies whether or not the user is prompted for a password when the system resumes from sleep.
-
-If you enable or do not configure this policy setting, the user is prompted for a password when the system resumes from sleep.
-
-If you disable this policy setting, the user is not prompted for a password when the system resumes from sleep.
- Prompt for password on resume from hibernate/suspend
- This policy setting allows you to configure client computers to lock and prompt for a password when resuming from a hibernate or suspend state.
-
-If you enable this policy setting, the client computer is locked and prompted for a password when it is resumed from a suspend or hibernate state.
-
-If you disable or do not configure this policy setting, users control if their computer is automatically locked or not after performing a resume operation.
- This policy setting specifies the action that Windows takes when a user presses the sleep button.
-
-Possible actions include:
--Take no action
--Sleep
--Hibernate
--Shut down
-
-If you enable this policy setting, you must select the desired action.
-
-If you disable this policy setting or do not configure it, users can see and change this setting.
- This policy setting specifies the action that Windows takes when a user presses the Start menu Power button.
-
-If you enable this policy setting, select one of the following actions:
--Sleep
--Hibernate
--Shut down
-
-If you disable this policy or do not configure this policy setting, users control this setting.
- This policy setting allows you to specify the period of inactivity before Windows transitions the system to sleep.
-
-If you enable this policy setting, you must provide a value, in seconds, indicating how much idle time should elapse before Windows transitions to sleep.
-
-If you disable or do not configure this policy setting, users control this setting.
-
-If the user has configured a slide show to run on the lock screen when the machine is locked, this can prevent the sleep transition from occuring. The "Prevent enabling lock screen slide show" policy setting can be used to disable the slide show feature.
- This policy setting allows you to turn off hybrid sleep.
-
-If you enable this policy setting, a hiberfile is not generated when the system transitions to sleep (Stand By).
-
-If you disable or do not configure this policy setting, users control this setting.
- This policy setting specifies the action that Windows takes when a user closes the lid on a mobile PC.
-
-Possible actions include:
--Take no action
--Sleep
--Hibernate
--Shut down
-
-If you enable this policy setting, you must select the desired action.
-
-If you disable this policy setting or do not configure it, users can see and change this setting.
- Turn off adaptive display timeout (plugged in)
- Turn off adaptive display timeout (on battery)
- This policy setting allows you to manage how long a computer must be inactive before Windows turns off the computer’s display.
-
-If you enable this policy setting, Windows automatically adjusts the setting based on what users do with their keyboard or mouse to keep the display on.
-
-If you disable this policy setting, Windows uses the same setting regardless of users’ keyboard or mouse behavior.
-
-If you do not configure this policy setting, users control this setting.
- Turn off the display (plugged in)
- Turn off the display (on battery)
- This policy setting allows you to specify the period of inactivity before Windows turns off the display.
-
-If you enable this policy setting, you must provide a value, in seconds, indicating how much idle time should elapse before Windows turns off the display.
-
-If you disable or do not configure this policy setting, users control this setting.
-
-If the user has configured a slide show to run on the lock screen when the machine is locked, this can prevent the display from turning off. The "Prevent enabling lock screen slide show" policy setting can be used to disable the slide show feature.
- Allow standby states (S1-S3) when sleeping (plugged in)
- Allow standby states (S1-S3) when sleeping (on battery)
- This policy setting manages whether or not Windows is allowed to use standby states when putting the computer in a sleep state.
-
-If you enable or do not configure this policy setting, Windows uses standby states to put the computer in a sleep state.
-
-If you disable this policy setting, standby states (S1-S3) are not allowed.
-
- Allow automatic sleep with Open Network Files (plugged in)
- Allow automatic sleep with Open Network Files (on battery)
- This policy setting allows you to manage automatic sleep with open network files.
-
-If you enable this policy setting, the computer automatically sleeps when network files are open.
-
-If you disable or do not configure this policy setting, the computer does not automatically sleep when network files are open.
-
- Reduce display brightness (plugged in)
- Reduce display brightness (on battery)
- This policy setting allows you to specify the period of inactivity before Windows automatically reduces brightness of the display.
-
-If you enable this policy setting, you must provide a value, in seconds, indicating how much idle time should elapse before Windows automatically reduces the brightness of the display.
-
-Windows will only reduce the brightness of the primary display integrated into the computer.
-
-If you disable or do not configure this policy setting, users control this setting.
-
- Specify the display dim brightness (plugged in)
- Specify the display dim brightness (on battery)
- This policy setting allows you to specify the brightness of the display when Windows automatically reduces brightness of the display.
-
-If you enable this policy setting, you must provide a value, in percentage, indicating the display brightness when Windows automatically reduces brightness of the display.
-
-If you disable or do not configure this policy setting, users control this setting.
-
- Turn on desktop background slideshow (plugged in)
- Turn on desktop background slideshow (on battery)
- This policy setting allows you to specify if Windows should enable the desktop background slideshow.
-
-If you enable this policy setting, desktop background slideshow is enabled.
-
-If you disable this policy setting, the desktop background slideshow is disabled.
-
-If you disable or do not configure this policy setting, users control this setting.
-
- Specify the unattended sleep timeout (plugged in)
- Specify the unattended sleep timeout (on battery)
- This policy setting allows you to specify the period of inactivity before Windows transitions to sleep automatically when a user is not present at the computer.
-
-If you enable this policy setting, you must provide a value, in seconds, indicating how much idle time should elapse before Windows automatically transitions to sleep when left unattended. If you specify 0 seconds, Windows does not automatically transition to sleep.
-
-If you disable or do not configure this policy setting, users control this setting.
-
-If the user has configured a slide show to run on the lock screen when the machine is locked, this can prevent the sleep transition from occuring. The "Prevent enabling lock screen slide show" policy setting can be used to disable the slide show feature.
-
- Allow applications to prevent automatic sleep (plugged in)
- Allow applications to prevent automatic sleep (on battery)
- This policy setting allows applications and services to prevent automatic sleep.
-
-If you enable this policy setting, any application, service, or device driver prevents Windows from automatically transitioning to sleep after a period of user inactivity.
-
-If you disable or do not configure this policy setting, applications, services, or drivers do not prevent Windows from automatically transitioning to sleep. Only user input is used to determine if Windows should automatically sleep.
-
- Reserve battery notification level
- This policy setting specifies the percentage of battery capacity remaining that triggers the reserve power mode.
-
-If you enable this policy setting, you must enter a numeric value (percentage) to set the battery level that triggers the reserve power notification.
-
-If you disable or do not configure this policy setting, users can see and change this setting.
-
- Energy Saver Settings
- Energy Saver Battery Threshold (plugged in)
- Energy Saver Battery Threshold (on battery)
- This policy setting allows you to specify battery charge level at which Energy Saver is turned on.
-
-If you enable this policy setting, you must provide a percent value, indicating the battery charge level. Energy Saver will be automatically turned on at (and below) the specified level.
-
-If you disable or do not configure this policy setting, users control this setting.
-
- This policy setting allows you to control the network connectivity state in standby on modern standby-capable systems.
-
-If you enable this policy setting, network connectivity will be maintained in standby.
-
-If you disable this policy setting, network connectivity in standby is not guaranteed. This connectivity restriction currently applies to WLAN networks only, and is subject to change.
-
-If you do not configure this policy setting, users control this setting.
-
- Power Throttling Settings
- Turn off Power Throttling
- This policy setting allows you to turn off Power Throttling.
-
-If you enable this policy setting, Power Throttling will be turned off.
-
-If you disable or do not configure this policy setting, users control this setting.
-
-
-
- System Hibernate Timeout (seconds):
-
-
- System Hibernate Timeout (seconds):
-
-
- Power Button Action
-
-
- Power Button Action
-
-
- Sleep Button Action
-
-
- Sleep Button Action
-
-
- User Interface Sleep Button Action
-
-
- User Interface Sleep Button Action
-
-
- System Sleep Timeout (seconds):
-
-
- System Sleep Timeout (seconds):
-
-
- Lid Switch Action
-
-
- Lid Switch Action
-
-
-
-
-
-
-
-
-
-
-
-
- Critical Battery Notification Action
-
-
- Critical Battery Notification Action
-
-
- Low Battery Notification Action
-
-
- Low Battery Notification Action
-
-
- Critical Battery Notification Level
-
-
- Critical Battery Notification Level
-
-
- Low Battery Notification Level
-
-
- Low Battery Notification Level
-
-
- System Hibernate Timeout (seconds):
-
-
- System Hibernate Timeout (seconds):
-
-
- Power Button Action
-
-
- Power Button Action
-
-
- Sleep Button Action
-
-
- Sleep Button Action
-
-
- User Interface Sleep Button Action
-
-
- User Interface Sleep Button Action
-
-
- System Sleep Timeout (seconds):
-
-
- System Sleep Timeout (seconds):
-
-
- Lid Switch Action
-
-
- Lid Switch Action
-
-
- Turn Off the Hard Disk (seconds):
-
-
- Turn Off the Hard Disk (seconds):
-
-
- Turn Off the Hard Disk (seconds):
-
-
- Turn Off the Hard Disk (seconds):
-
-
- Active Power Plan:
-
-
- Active Power Plan:
-
-
- Turn Off the Display (seconds):
-
-
- Turn Off the Display (seconds):
-
-
- Turn Off the Display (seconds):
-
-
- Turn Off the Display (seconds):
-
-
- Reduce Display Brightness (seconds):
-
-
- Display Dim Brightness (percent):
-
-
- Unattended Sleep Timeout (seconds):
-
-
- Reserve Battery Notification Level (percent):
-
-
- Energy Saver Battery Threshold (percent):
-
-
-
-
diff --git a/policy_templates/en-US/PowerShellExecutionPolicy.adml b/policy_templates/en-US/PowerShellExecutionPolicy.adml
deleted file mode 100644
index b30da39..0000000
--- a/policy_templates/en-US/PowerShellExecutionPolicy.adml
+++ /dev/null
@@ -1,112 +0,0 @@
-
-
- Windows PowerShell
- This file contains the configuration options for Windows PowerShell
-
-
- Allow all scripts
- Allow only signed scripts
- Turn on Script Execution
- This policy setting lets you configure the script execution policy, controlling which scripts are allowed to run.
-
-If you enable this policy setting, the scripts selected in the drop-down list are allowed to run.
-
-The "Allow only signed scripts" policy setting allows scripts to execute only if they are signed by a trusted publisher.
-
-The "Allow local scripts and remote signed scripts" policy setting allows any local scrips to run; scripts that originate from the Internet must be signed by a trusted publisher.
-
-The "Allow all scripts" policy setting allows all scripts to run.
-
-If you disable this policy setting, no scripts are allowed to run.
-
-Note: This policy setting exists under both "Computer Configuration" and "User Configuration" in the Local Group Policy Editor. The "Computer Configuration" has precedence over "User Configuration."
-
-If you disable or do not configure this policy setting, it reverts to a per-machine preference setting; the default if that is not configured is "No scripts allowed."
- Windows PowerShell
- Allow local scripts and remote signed scripts
- At least Microsoft Windows 7 or Windows Server 2008 family
-
- Turn on Module Logging
-
- This policy setting allows you to turn on logging for Windows PowerShell modules.
-
- If you enable this policy setting, pipeline execution events for members of the specified modules are recorded in the Windows PowerShell log in Event Viewer. Enabling this policy setting for a module is equivalent to setting the LogPipelineExecutionDetails property of the module to True.
-
- If you disable this policy setting, logging of execution events is disabled for all Windows PowerShell modules. Disabling this policy setting for a module is equivalent to setting the LogPipelineExecutionDetails property of the module to False.
-
- If this policy setting is not configured, the LogPipelineExecutionDetails property of a module or snap-in determines whether the execution events of a module or snap-in are logged. By default, the LogPipelineExecutionDetails property of all modules and snap-ins is set to False.
-
- To add modules and snap-ins to the policy setting list, click Show, and then type the module names in the list. The modules and snap-ins in the list must be installed on the computer.
-
- Note: This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting.
-
-
- Turn on PowerShell Transcription
-
- This policy setting lets you capture the input and output of Windows PowerShell commands into text-based transcripts.
-
- If you enable this policy setting, Windows PowerShell will enable transcripting for Windows PowerShell, the Windows PowerShell ISE, and any other
- applications that leverage the Windows PowerShell engine. By default, Windows PowerShell will record transcript output to each users' My Documents
- directory, with a file name that includes 'PowerShell_transcript', along with the computer name and time started. Enabling this policy is equivalent
- to calling the Start-Transcript cmdlet on each Windows PowerShell session.
-
- If you disable this policy setting, transcripting of PowerShell-based applications is disabled by default, although transcripting can still be enabled
- through the Start-Transcript cmdlet.
-
- If you use the OutputDirectory setting to enable transcript logging to a shared location, be sure to limit access to that directory to prevent users
- from viewing the transcripts of other users or computers.
-
- Note: This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting.
-
-
- Turn on PowerShell Script Block Logging
-
- This policy setting enables logging of all PowerShell script input to the Microsoft-Windows-PowerShell/Operational event log. If you enable this policy setting,
- Windows PowerShell will log the processing of commands, script blocks, functions, and scripts - whether invoked interactively, or through automation.
-
- If you disable this policy setting, logging of PowerShell script input is disabled.
-
- If you enable the Script Block Invocation Logging, PowerShell additionally logs events when invocation of a command, script block, function, or script
- starts or stops. Enabling Invocation Logging generates a high volume of event logs.
-
- Note: This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting.
-
-
- Set the default source path for Update-Help
- This policy setting allows you to set the default value of the SourcePath parameter on the Update-Help cmdlet.
-
-If you enable this policy setting, the Update-Help cmdlet will use the specified value as the default value for the SourcePath parameter. This default value can be overridden by specifying a different value with the SourcePath parameter on the Update-Help cmdlet.
-
-If this policy setting is disabled or not configured, this policy setting does not set a default value for the SourcePath parameter of the Update-Help cmdlet.
-
-Note: This policy setting exists under both Computer Configuration and User Configuration in the Group Policy Editor. The Computer Configuration policy setting takes precedence over the User Configuration policy setting.
-
-
-
-
-
- Execution Policy
-
-
- To turn on logging for one or more modules, click Show, and then type the module names in the list. Wildcards are supported.
- Module Names
- To turn on logging for the Windows PowerShell core modules, type the following module names in the list:
- Microsoft.PowerShell.*
- Microsoft.WSMan.Management
-
-
-
- Include invocation headers:
-
-
- Log script block invocation start / stop events:
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/PreviousVersions.adml b/policy_templates/en-US/PreviousVersions.adml
deleted file mode 100644
index 04f51ab..0000000
--- a/policy_templates/en-US/PreviousVersions.adml
+++ /dev/null
@@ -1,60 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Prevent restoring previous versions from backups
- This policy setting lets you suppress the Restore button in the previous versions property page when the user has selected a previous version of a local file, in which the previous version is stored on a backup.
-
-If you enable this policy setting, the Restore button is disabled when the user selects a previous version corresponding to a backup.
-
-If you disable this policy setting, the Restore button remains active for a previous version corresponding to a backup. If the Restore button is clicked, Windows attempts to restore the file from the backup media.
-
-If you do not configure this policy setting, it is disabled by default. The Restore button is active when the previous version is of a local file and stored on the backup.
- Hide previous versions list for local files
- This policy setting lets you hide the list of previous versions of files that are on local disks. The previous versions could come from the on-disk restore points or from backup media.
-
-If you enable this policy setting, users cannot list or restore previous versions of files on local disks.
-
-If you disable this policy setting, users cannot list and restore previous versions of files on local disks.
-
-If you do not configure this policy setting, it defaults to disabled.
- Prevent restoring local previous versions
- This policy setting lets you suppress the Restore button in the previous versions property page when the user has selected a previous version of a local file.
-
-If you enable this policy setting, the Restore button is disabled when the user selects a previous version corresponding to a local file.
-
-If you disable this policy setting, the Restore button remains active for a previous version corresponding to a local file. If the user clicks the Restore button, Windows attempts to restore the file from the local disk.
-
-If you do not configure this policy setting, it is disabled by default. The Restore button is active when the previous version is of a local file.
- Hide previous versions list for remote files
- This policy setting lets you hide the list of previous versions of files that are on file shares. The previous versions come from the on-disk restore points on the file share.
-
-If you enable this policy setting, users cannot list or restore previous versions of files on file shares.
-
-If you disable this policy setting, users can list and restore previous versions of files on file shares.
-
-If you do not configure this policy setting, it is disabled by default.
- Prevent restoring remote previous versions
- This setting lets you suppress the Restore button in the previous versions property page when the user has selected a previous version of a file on a file share.
-
-If you enable this policy setting, the Restore button is disabled when the user selects a previous version corresponding to a file on a file share.
-
-If you disable this policy setting, the Restore button remains active for a previous version corresponding to a file on a file share. If the user clicks the Restore button, Windows attempts to restore the file from the file share.
-
-If you do not configure this policy setting, it is disabled by default. The Restore button is active when the previous version is of a file on a file share.
- Hide previous versions of files on backup location
- This policy setting lets you hide entries in the list of previous versions of a file in which the previous version is located on backup media. Previous versions can come from the on-disk restore points or the backup media.
-
-If you enable this policy setting, users cannot see any previous versions corresponding to backup copies, and can see only previous versions corresponding to on-disk restore points.
-
-If you disable this policy setting, users can see previous versions corresponding to backup copies as well as previous versions corresponding to on-disk restore points.
-
-If you do not configure this policy setting, it is disabled by default.
- Previous Versions
- Supported Windows Vista through Windows 7
-
-
-
diff --git a/policy_templates/en-US/Printing.adml b/policy_templates/en-US/Printing.adml
deleted file mode 100644
index cbf4404..0000000
--- a/policy_templates/en-US/Printing.adml
+++ /dev/null
@@ -1,563 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Activate Internet printing
- Internet printing lets you display printers on Web pages so that printers can be viewed, managed, and used across the Internet or an intranet.
-
- If you enable this policy setting, Internet printing is activated on this server.
-
- If you disable this policy setting or do not configure it, Internet printing is not activated.
-
- Internet printing is an extension of Internet Information Services (IIS). To use Internet printing, IIS must be installed, and printing support and this setting must be enabled.
-
- Note: This setting affects the server side of Internet printing only. It does not prevent the print client on the computer from printing across the Internet.
-
- Also, see the "Custom support URL in the Printers folder's left pane" setting in this folder and the "Browse a common Web site to find printers" setting in User Configuration\Administrative Templates\Control Panel\Printers.
- Isolate print drivers from applications
- Determines if print driver components are isolated from applications instead of normally loading them into applications. Isolating print drivers greatly reduces the risk of a print driver failure causing an application crash.
-
-Not all applications support driver isolation. By default, Microsoft Excel 2007, Excel 2010, Word 2007, Word 2010 and certain other applications are configured to support it. Other applications may also be capable of isolating print drivers, depending on whether they are configured for it.
-
-If you enable or do not configure this policy setting, then applications that are configured to support driver isolation will be isolated.
-
-If you disable this policy setting, then print drivers will be loaded within all associated application processes.
-
-Notes:
--This policy setting applies only to applications opted into isolation.
--This policy setting applies only to print drivers loaded by applications. Print drivers loaded by the print spooler are not affected.
--This policy setting is only checked once during the lifetime of a process. After changing the policy, a running application must be relaunched before settings take effect.
- Printers
- Manages network printer configuration and publishing options.
- Custom support URL in the Printers folder's left pane
- By default, the Printers folder includes a link to the Microsoft Support Web page called "Get help with printing". It can also include a link to a Web page supplied by the vendor of the currently selected printer.
-
- If you enable this policy setting, you replace the "Get help with printing" default link with a link to a Web page customized for your enterprise.
-
- If you disable this setting or do not configure it, or if you do not enter an alternate Internet address, the default link will appear in the Printers folder.
-
- Note: Web pages links only appear in the Printers folder when Web view is enabled. If Web view is disabled, the setting has no effect. (To enable Web view, open the Printers folder, and, on the Tools menu, click Folder Options, click the General tab, and then click "Enable Web content in folders.")
-
- Also, see the "Activate Internet printing" setting in this setting folder and the "Browse a common web site to find printers" setting in User Configuration\Administrative Templates\Control Panel\Printers.
-
- Web view is affected by the "Turn on Classic Shell" and "Do not allow Folder Options to be opened from the Options button on the View tab of the ribbon" settings in User Configuration\Administrative Templates\Windows Components\Windows Explorer, and by the "Enable Active Desktop" setting in User Configuration\Administrative Templates\Desktop\Active Desktop.
- If you enable this policy setting, it sets the maximum number of printers (of each type) that the Add Printer wizard will display on a computer on a managed network (when the computer is able to reach a domain controller, e.g. a domain-joined laptop on a corporate network.)
-
- If this policy setting is disabled, the network scan page will not be displayed.
-
- If this policy setting is not configured, the Add Printer wizard will display the default number of printers of each type:
- Directory printers: 20
- TCP/IP printers: 0
- Web Services printers: 0
- Bluetooth printers: 10
- Shared printers: 0
-
- In order to view available Web Services printers on your network, ensure that network discovery is turned on. To turn on network discovery, click "Start", click "Control Panel", and then click "Network and Internet". On the "Network and Internet" page, click "Network and Sharing Center". On the Network and Sharing Center page, click "Change advanced sharing settings". On the Advanced sharing settings page, click the arrow next to "Domain" arrow, click "turn on network discovery", and then click "Save changes".
-
- If you would like to not display printers of a certain type, enable this policy and set the number of printers to display to 0.
-
- In Windows 10 and later, only TCP/IP printers can be shown in the wizard. If you enable this policy setting, only TCP/IP printer limits are applicable. On Windows 10 only, if you disable or do not configure this policy setting, the default limit is applied.
-
- In Windows 8 and later, Bluetooth printers are not shown so its limit does not apply to those versions of Windows.
-
- Add Printer wizard - Network scan page (Managed network)
- Browse the network to find printers
- Allows users to use the Add Printer Wizard to search the network for shared printers.
-
-If you enable this setting or do not configure it, when users choose to add a network printer by selecting the "A network printer, or a printer attached to another computer" radio button on Add Printer Wizard's page 2, and also check the "Connect to this printer (or to browse for a printer, select this option and click Next)" radio button on Add Printer Wizard's page 3, and do not specify a printer name in the adjacent "Name" edit box, then Add Printer Wizard displays the list of shared printers on the network and invites to choose a printer from the shown list.
-
-If you disable this setting, the network printer browse page is removed from within the Add Printer Wizard, and users cannot search the network but must type a printer name.
-
-Note: This setting affects the Add Printer Wizard only. It does not prevent users from using other programs to search for shared printers or to connect to network printers.
- Always render print jobs on the server
- When printing through a print server, determines whether the print spooler on the client will process print jobs itself, or pass them on to the server to do the work.
-
-This policy setting only effects printing to a Windows print server.
-
-If you enable this policy setting on a client machine, the client spooler will not process print jobs before sending them to the print server. This decreases the workload on the client at the expense of increasing the load on the server.
-
-If you disable this policy setting on a client machine, the client itself will process print jobs into printer device commands. These commands will then be sent to the print server, and the server will simply pass the commands to the printer. This increases the workload of the client while decreasing the load on the server.
-
-If you do not enable this policy setting, the behavior is the same as disabling it.
-
-Note: This policy does not determine whether offline printing will be available to the client. The client print spooler can always queue print jobs when not connected to the print server. Upon reconnecting to the server, the client will submit any pending print jobs.
-
-Note: Some printer drivers require a custom print processor. In some cases the custom print processor may not be installed on the client machine, such as when the print server does not support transferring print processors during point-and-print. In the case of a print processor mismatch, the client spooler will always send jobs to the print server for rendering. Disabling the above policy setting does not override this behavior.
-
-Note: In cases where the client print driver does not match the server print driver (mismatched connection), the client will always process the print job, regardless of the setting of this policy.
- Always rasterize content to be printed using a software rasterizer
- Determines whether the XPS Rasterization Service or the XPS-to-GDI conversion (XGC) is forced to use a software rasterizer instead of a Graphics Processing Unit (GPU) to rasterize pages.
-
-This setting may improve the performance of the XPS Rasterization Service or the XPS-to-GDI conversion (XGC) on machines that have a relatively powerful CPU as compared to the machine’s GPU.
- Browse a common web site to find printers
- Adds a link to an Internet or intranet Web page to the Add Printer Wizard.
-
- You can use this setting to direct users to a Web page from which they can install printers.
-
- If you enable this setting and type an Internet or intranet address in the text box, the system adds a Browse button to the "Specify a Printer" page in the Add Printer Wizard. The Browse button appears beside the "Connect to a printer on the Internet or on a home or office network" option. When users click Browse, the system opens an Internet browser and navigates to the specified URL address to display the available printers.
-
- This setting makes it easy for users to find the printers you want them to add.
-
- Also, see the "Custom support URL in the Printers folder's left pane" and "Activate Internet printing" settings in "Computer Configuration\Administrative Templates\Printers."
- Disallow installation of printers using kernel-mode drivers
- Determines whether printers using kernel-mode drivers may be installed on the local computer. Kernel-mode drivers have access to system-wide memory, and therefore poorly-written kernel-mode drivers can cause stop errors.
-
-If you disable this setting, or do not configure it, then printers using a kernel-mode drivers may be installed on the local computer running Windows XP Home Edition and Windows XP Professional.
-
-If you do not configure this setting on Windows Server 2003 family products, the installation of kernel-mode printer drivers will be blocked.
-
-If you enable this setting, installation of a printer using a kernel-mode driver will not be allowed.
-
-Note: By applying this policy, existing kernel-mode drivers will be disabled upon installation of service packs or reinstallation of the Windows XP operating system. This policy does not apply to 64-bit kernel-mode printer drivers as they cannot be installed and associated with a print queue.
- Prevent addition of printers
- Prevents users from using familiar methods to add local and network printers.
-
- If this policy setting is enabled, it removes the Add Printer option from the Start menu. (To find the Add Printer option, click Start, click Printers, and then click Add Printer.) This setting also removes Add Printer from the Printers folder in Control Panel.
-
- Also, users cannot add printers by dragging a printer icon into the Printers folder. If they try, a message appears explaining that the setting prevents the action.
-
- However, this setting does not prevent users from using the Add Hardware Wizard to add a printer. Nor does it prevent users from running other programs to add printers.
-
- This setting does not delete printers that users have already added. However, if users have not added a printer when this setting is applied, they cannot print.
-
- Note: You can use printer permissions to restrict the use of printers without specifying a setting. In the Printers folder, right-click a printer, click Properties, and then click the Security tab.
-
- If this policy is disabled, or not configured, users can add printers using the methods described above.
- Prevent deletion of printers
- If this policy setting is enabled, it prevents users from deleting local and network printers.
-
- If a user tries to delete a printer, such as by using the Delete option in Printers in Control Panel, a message appears explaining that a setting prevents the action.
-
- This setting does not prevent users from running other programs to delete a printer.
-
- If this policy is disabled, or not configured, users can delete printers using the methods described above.
- This policy sets the maximum number of printers (of each type) that the Add Printer wizard will display on a computer on an unmanaged network (when the computer is not able to reach a domain controller, e.g. a domain-joined laptop on a home network.)
-
-If this setting is disabled, the network scan page will not be displayed.
-
-If this setting is not configured, the Add Printer wizard will display the default number of printers of each type:
-TCP/IP printers: 50
-Web Services printers: 50
-Bluetooth printers: 10
-Shared printers: 50
-
-If you would like to not display printers of a certain type, enable this policy and set the number of printers to display to 0.
-
-In Windows 10 and later, only TCP/IP printers can be shown in the wizard. If you enable this policy setting, only TCP/IP printer limits are applicable. On Windows 10 only, if you disable or do not configure this policy setting, the default limit is applied.
-
-In Windows 8 and later, Bluetooth printers are not shown so its limit does not apply to those versions of Windows.
- Add Printer wizard - Network scan page (Unmanaged network)
- Only use Package Point and print
- This policy restricts clients computers to use package point and print only.
-
-If this setting is enabled, users will only be able to point and print to printers that use package-aware drivers. When using package point and print, client computers will check the driver signature of all drivers that are downloaded from print servers.
-
-If this setting is disabled, or not configured, users will not be restricted to package-aware point and print only.
- Supported Windows XP SP1 through Windows Server 2008 RTM
- Package Point and print - Approved servers
- Restricts package point and print to approved servers.
-
-This policy setting restricts package point and print connections to approved servers. This setting only applies to Package Point and Print connections, and is completely independent from the "Point and Print Restrictions" policy that governs the behavior of non-package point and print connections.
-
-Windows Vista and later clients will attempt to make a non-package point and print connection anytime a package point and print connection fails, including attempts that are blocked by this policy. Administrators may need to set both policies to block all print connections to a specific print server.
-
-If this setting is enabled, users will only be able to package point and print to print servers approved by the network administrator. When using package point and print, client computers will check the driver signature of all drivers that are downloaded from print servers.
-
-If this setting is disabled, or not configured, package point and print will not be restricted to specific print servers.
- Computer location
- If this policy setting is enabled, it specifies the default location criteria used when searching for printers.
-
- This setting is a component of the Location Tracking feature of Windows printers. To use this setting, enable Location Tracking by enabling the "Pre-populate printer search location text" setting.
-
- When Location Tracking is enabled, the system uses the specified location as a criterion when users search for printers. The value you type here overrides the actual location of the computer conducting the search.
-
- Type the location of the user's computer. When users search for printers, the system uses the specified location (and other search criteria) to find a printer nearby. You can also use this setting to direct users to a particular printer or group of printers that you want them to use.
-
- If you disable this setting or do not configure it, and the user does not type a location as a search criterion, the system searches for a nearby printer based on the IP address and subnet mask of the user's computer.
- Pre-populate printer search location text
- Enables the physical Location Tracking setting for Windows printers.
-
-Use Location Tracking to design a location scheme for your enterprise and assign computers and printers to locations in the scheme. Location Tracking overrides the standard method used to locate and associate computers and printers. The standard method uses a printer's IP address and subnet mask to estimate its physical location and proximity to computers.
-
-If you enable this setting, users can browse for printers by location without knowing the printer's location or location naming scheme. Enabling Location Tracking adds a Browse button in the Add Printer wizard's Printer Name and Sharing Location screen and to the General tab in the Printer Properties dialog box. If you enable the Group Policy Computer location setting, the default location you entered appears in the Location field by default.
-
-If you disable this setting or do not configure it, Location Tracking is disabled. Printer proximity is estimated using the standard method (that is, based on IP address and subnet mask).
- Point and Print Restrictions
- This policy setting controls the client Point and Print behavior, including the security prompts for Windows Vista computers. The policy setting applies only to non-Print Administrator clients, and only to computers that are members of a domain.
-
- If you enable this policy setting:
- -Windows XP and later clients will only download print driver components from a list of explicitly named servers. If a compatible print driver is available on the client, a printer connection will be made. If a compatible print driver is not available on the client, no connection will be made.
- -You can configure Windows Vista clients so that security warnings and elevated command prompts do not appear when users Point and Print, or when printer connection drivers need to be updated.
-
- If you do not configure this policy setting:
- -Windows Vista client computers can point and print to any server.
- -Windows Vista computers will show a warning and an elevated command prompt when users create a printer connection to any server using Point and Print.
- -Windows Vista computers will show a warning and an elevated command prompt when an existing printer connection driver needs to be updated.
- -Windows Server 2003 and Windows XP client computers can create a printer connection to any server in their forest using Point and Print.
-
- If you disable this policy setting:
- -Windows Vista client computers can create a printer connection to any server using Point and Print.
- -Windows Vista computers will not show a warning or an elevated command prompt when users create a printer connection to any server using Point and Print.
- -Windows Vista computers will not show a warning or an elevated command prompt when an existing printer connection driver needs to be updated.
- -Windows Server 2003 and Windows XP client computers can create a printer connection to any server using Point and Print.
- -The "Users can only point and print to computers in their forest" setting applies only to Windows Server 2003 and Windows XP SP1 (and later service packs).
- Show warning and elevation prompt
- Do not show warning or elevation prompt
- Show warning only
- Default Active Directory path when searching for printers
- Specifies the Active Directory location where searches for printers begin.
-
- The Add Printer Wizard gives users the option of searching Active Directory for a shared printer.
-
- If you enable this policy setting, these searches begin at the location you specify in the "Default Active Directory path" box. Otherwise, searches begin at the root of Active Directory.
-
- This setting only provides a starting point for Active Directory searches for printers. It does not restrict user searches through Active Directory.
- Printer browsing
- Announces the presence of shared printers to print browse master servers for the domain.
-
-On domains with Active Directory, shared printer resources are available in Active Directory and are not announced.
-
-If you enable this setting, the print spooler announces shared printers to the print browse master servers.
-
-If you disable this setting, shared printers are not announced to print browse master servers, even if Active Directory is not available.
-
-If you do not configure this setting, shared printers are announced to browse master servers only when Active Directory is not available.
-
-Note: A client license is used each time a client computer announces a printer to a print browse master on the domain.
- Execute print drivers in isolated processes
- This policy setting determines whether the print spooler will execute print drivers in an isolated or separate process. When print drivers are loaded in an isolated process (or isolated processes), a print driver failure will not cause the print spooler service to fail.
-
-If you enable or do not configure this policy setting, the print spooler will execute print drivers in an isolated process by default.
-
-If you disable this policy setting, the print spooler will execute print drivers in the print spooler process.
-
-
-Notes:
--Other system or driver policy settings may alter the process in which a print driver is executed.
--This policy setting applies only to print drivers loaded by the print spooler. Print drivers loaded by applications are not affected.
--This policy setting takes effect without restarting the print spooler service.
- Override print driver execution compatibility setting reported by print driver
- This policy setting determines whether the print spooler will override the Driver Isolation compatibility reported by the print driver. This enables executing print drivers in an isolated process, even if the driver does not report compatibility.
-
-If you enable this policy setting, the print spooler isolates all print drivers that do not explicitly opt out of Driver Isolation.
-
-If you disable or do not configure this policy setting, the print spooler uses the Driver Isolation compatibility flag value reported by the print driver.
-
-Notes:
--Other system or driver policy settings may alter the process in which a print driver is executed.
--This policy setting applies only to print drivers loaded by the print spooler. Print drivers loaded by applications are not affected.
--This policy setting takes effect without restarting the print spooler service.
- Allow job name in event logs
-
- This policy controls whether the print job name will be included in print event logs.
-
- If you disable or do not configure this policy setting, the print job name will not be included.
-
- If you enable this policy setting, the print job name will be included in new log entries.
-
- Note: This setting does not apply to Branch Office Direct Printing jobs.
-
- Extend Point and Print connection to search Windows Update
- This policy setting allows you to manage where client computers search for Point and Printer drivers.
-
-If you enable this policy setting, the client computer will continue to search for compatible Point and Print drivers from Windows Update after it fails to find the compatible driver from the local driver store and the server driver cache.
-
-If you disable this policy setting, the client computer will only search the local driver store and server driver cache for compatible Point and Print drivers. If it is unable to find a compatible driver, then the Point and Print connection will fail.
-
-This policy setting is not configured by default, and the behavior depends on the version of Windows that you are using.
-By default, Windows Ultimate, Professional and Home SKUs will continue to search for compatible Point and Print drivers from Windows Update, if needed. However, you must explicitly enable this policy setting for other versions of Windows (for example Windows Enterprise, and all versions of Windows Server 2008 R2 and later) to have the same behavior.
- Do not allow v4 printer drivers to show printer extensions
- This policy determines if v4 printer drivers are allowed to run printer extensions.
-
- V4 printer drivers may include an optional, customized user interface known as a printer extension. These extensions may provide access to more device features, but this may not be appropriate for all enterprises.
-
- If you enable this policy setting, then all printer extensions will not be allowed to run.
-
- If you disable this policy setting or do not configure it, then all printer extensions that have been installed will be allowed to run.
- Change Microsoft XPS Document Writer (MXDW) default output format to the legacy Microsoft XPS format (*.xps)
- Microsoft XPS Document Writer (MXDW) generates OpenXPS (*.oxps) files by default in Windows 10, Windows 10 and Windows Server 2022.
-
- If you enable this group policy setting, the default MXDW output format is the legacy Microsoft XPS (*.xps).
-
- If you disable or do not configure this policy setting, the default MXDW output format is OpenXPS (*.oxps).
- Turn off Windows default printer management
- This preference allows you to change default printer management.
-
-If you enable this setting, Windows will not manage the default printer.
-
-If you disable this setting, Windows will manage the default printer.
-
-If you do not configure this setting, default printer management will not change.
- Enable Device Control Printing Restrictions
-
-Determines whether Device Control Printing Restrictions are enforced for printing on this computer.
-
-By default, there are no restrictions to printing based on connection type or printer Make/Model.
-
-If you enable this setting, the computer will restrict printing to printer connections on the corporate network or approved USB-connected printers.
-
-If you disable this setting or do not configure it, there are no restrictions to printing based on connection type or printer Make/Model.
- List of Approved USB-connected print devices
-
-
-This setting is a component of the Device Control Printing Restrictions. To use this setting, enable Device Control Printing by enabling the "Enable Device Control Printing Restrictions" setting.
-
-When Device Control Printing is enabled, the system uses the specified list of vid/pid values to determine if the current USB connected printer is approved for local printing.
-
-Type all the approved vid/pid combinations (separated by commas) that correspond to approved USB printer models. When a user tries to print to a USB printer queue the device vid/pid will be compared to the approved list.
-
- Limits print driver installation to Administrators
-
-Determines whether users that aren't Administrators can install print drivers on this computer.
-
-By default, users that aren't Administrators can't install print drivers on this computer.
-
-If you enable this setting or do not configure it, the system will limit installation of print drivers to Administrators of this computer.
-
-If you disable this setting, the system won't limit installation of print drivers to this computer.
-
- Manage processing of Queue-specific files
- Allow all Queue-specfic files
- Do not allow Queue-specific files
-
-Manages how Queue-specific files are processed during printer installation. At printer installation time, a vendor-supplied installation application can specify a set of files, of any type, to be associated with a particular print queue. The files are downloaded to each client that connects to the print server.
-
-You can enable this setting to change the default behavior involving queue-specific files. To use this setting, select one of the options below from the "Manage processing of Queue-specific files" box.
-
-If you disable or do not configure this policy setting, the default behavior is "Limit Queue-specific files to Color profiles".
-
--- "Do not allow Queue-specific files" specifies that no queue-specific files will be allowed/processed during print queue/printer connection installation.
-
--- "Limit Queue-specific files to Color profiles" specifies that only queue-specific files that adhere to the standard color profile scheme will be allowed. This means entries using the Registry Key CopyFiles\ICM, containing a Directory value of COLOR and supporting mscms.dll as the Module value. "Limit Queue-specific files to Color profiles" is the default behavior.
-
--- "Allow all Queue-specific files" specifies that all queue-specific files will be allowed/processed during print queue/printer connection installation.
-
- Limit Queue-specific files to Color profiles
- Require inbox signed drivers
- Allow all validly signed drivers
- Allow inbox and Print Drivers Trusted Store signed drivers
- Allow inbox, Print Drivers Trusted Store, WHQL, and Trusted Publisher Store signed drivers
- Allow inbox, Print Drivers Trusted Store, and WHQL signed drivers
- Manage Print Driver signature validation
-
- This policy setting controls the print driver signature validation mechanism. This policy controls the type of digital signature that is required for a print driver to be considered valid and installed on the system.
-
- As part of this validation the catalog/embedded signature is verified and all files in the driver must be a part of the catalog or have their own embedded signature that can be used for validation.
-
- You can enable this setting to change the default signature validation method. To use this setting, select one of the options below from the "Select the driver signature mechanism for this computer" box.
-
- If you disable or do not configure this policy setting, the default method is "Allow all validly signed drivers".
-
- -- "Require inbox signed drivers" specifies only drivers that are shipped as part of a Windows image are allowed on this computer.
-
- -- "Allow inbox and PrintDrivers Trusted Store signed drivers" specifies only drivers that are shipped as part of a Windows image or drivers that are signed by certificates installed in the 'PrintDrivers' certificate store are allowed on this computer.
-
- -- "Allow inbox, PrintDrivers Trusted Store, and WHQL signed drivers" specifies the only drivers allowed on this computer are those that are: shipped as part of a Windows image, signed by certificates installed in the 'PrintDrivers' certificate store, or signed by the Windows Hardware Quality Lab (WHQL).
-
- -- "Allow inbox, PrintDrivers Trusted Store, WHQL, and Trusted Publishers Store signed drivers" specifies the only drivers allowed on this computer are those that are: shipped as part of a Windows image, signed by certificates installed in the 'PrintDrivers' certificate store, signed by the Windows Hardware Quality Lab (WHQL), or signed by certificates installed in the 'Trusted Publishers' certificate store.
-
- -- "Allow all validly signed drivers" specfies that any print driver that has a valid embedded signature or can be validated against the print driver catalog can be installed on this computer.
-
- The 'PrintDrivers' certificate store needs to be created by an administrator under the local machine store location.
-
- The 'Trusted Publishers' certificate store can contain certificates from sources that are not related to print drivers.
-
-
- Select the driver signature mechanism for this computer
- Manage Print Driver exclusion list
-
-This policy setting controls the print driver exclusion list. The exclusion list allows an administrator to curate a list of printer drivers that are not allowed to be installed on the system.
-
-This checks outranks the signature check and allows drivers that have a valid signature level for the Print Driver signature validation policy to be excluded.
-
-Entries in the exclusion list consist of a SHA256 hash (or SHA1 hash for Win7) of the INF file and/or main driver DLL file of the driver and the name of the file.
-
-If you disable or do not configure this policy setting, the registry key and values associated with this policy setting will be deleted, if currently set to a value.
-
-
- Configure RPC listener settings
- RPC over named pipes
- RPC over TCP
- RPC over named pipes and TCP
- Negotiate
- Kerberos
-
-This policy setting controls which protocols incoming RPC connections to the print spooler are allowed to use.
-
-By default, RPC over TCP is enabled and Negotiate is used for the authentication protocol.
-
-Protocols to allow for incoming RPC connections:
- -- "RPC over named pipes": Incoming RPC connections are only allowed over named pipes
- -- "RPC over TCP": Incoming RPC connections are only allowed over TCP (the default option)
- -- "RPC over named pipes and TCP": Incoming RPC connections will be allowed over TCP and named pipes
-
-Authentication protocol to use for incoming RPC connections:
- -- "Negotiate": Use the Negotiate authentication protocol (the default option)
- -- "Kerberos": Use the Kerberos authentication protocol
-
-If you disable or do not configure this policy setting, the above defaults will be used.
-
- Configure RPC connection settings
- Default
- Authentication enabled
- Authentication disabled
-
-This policy setting controls which protocol and protocol settings to use for outgoing RPC connections to a remote print spooler.
-
-By default, RPC over TCP is used and authentication is always enabled. For RPC over named pipes, authentication is always enabled for domain joined machines but disabled for non domain joined machines.
-
-Protocol to use for outgoing RPC connections:
- -- "RPC over TCP": Use RPC over TCP for outgoing RPC connections to a remote print spooler
- -- "RPC over named pipes": Use RPC over named pipes for outgoing RPC connections to a remote print spooler
-
-Use authentication for outgoing RPC over named pipes connections:
- -- "Default": By default domain joined computers enable RPC authentication for RPC over named pipes while non domain joined computers disable RPC authentication for RPC over named pipes
- -- "Authentication enabled": RPC authentication will be used for outgoing RPC over named pipes connections
- -- "Authentication disabled": RPC authentication will not be used for outgoing RPC over named pipes connections
-
-If you disable or do not configure this policy setting, the above defaults will be used.
-
- Configure RPC over TCP port
-
-This policy setting controls which port is used for RPC over TCP for incoming connections to the print spooler and outgoing connections to remote print spoolers.
-
-By default dynamic TCP ports are used.
-
-RPC over TCP port:
- -- The port to use for RPC over TCP. A value of 0 is the default and indicates that dynamic TCP ports will be used
-
-If you disable or do not configure this policy setting, dynamic TCP ports are used.
-
- Always send job page count information for IPP printers
-
-Determines whether to always send page count information for accounting purposes for printers using the Microsoft IPP Class Driver.
-
-By default, pages are sent to the printer as soon as they are rendered and page count information is not sent to the printer unless pages must be reordered.
-
-If you enable this setting the system will render all print job pages up front and send the printer the total page count for the print job.
-
-If you disable this setting or do not configure it, pages are printed as soon as they are rendered and page counts are only sent when page reordering is required to process the job.
-
- Configure Redirection Guard
- Redirection Guard Disabled
- Redirection Guard Enabled
- Redirection Guard Audit Only
-
-Determines whether Redirection Guard is enabled for the print spooler.
-
-You can enable this setting to configure the Redirection Guard policy being applied to spooler.
-
-If you disable or do not configure this policy setting, Redirection Guard will default to being 'enabled'.
-
-If you enable this setting you may select the following options:
-
--- Enabled : Redirection Guard will prevent any file redirections from being followed
-
--- Disabed : Redirection Guard will not be enabled and file redirections may be used within the spooler process
-
--- Audit : Redirection Guard will log events as though it were enabled but will not actually prevent file redirections from being used within the spooler.
-
-
-
-
- Specify the URL. For example, the url would be: http://www.microsoft.com/support
-
-
-
-
-
- Number of directory printers
- Number of TCP/IP printers
- Number of Web Services Printers
- Number of Bluetooth printers
- Number of shared printers
-
-
- Enable this option to add a browse button for Internet printers
- in the Add Printer Wizard. Use this setting to allow users browsing
- the company's Intranet for printers. For example, you can
- specify a URL like: http://www.company.com/printers.
- To enable this option, the edit box below should not be empty.
-
-
-
-
-
- Number of TCP/IP printers
- Number of Web Services Printers
- Number of Bluetooth printers
- Number of shared printers
-
-
- Enter fully qualified server names
-
-
- Enter the location of this computer
- For example: CityName/Building 2/Floor 1/Office 1800
-
-
-
-
-
- Users can only point and print to these servers:
-
-
-
- Users can only point and print to machines in their forest
-
- Security Prompts:
- When installing drivers for a new connection:
- When updating drivers for an existing connection:
- This setting only applies to:
- Windows Vista and later
-
-
-
-
-
- example --> LDAP://DC=Domain1,DC=MyCompany,DC=com.
-
-
- Specify the list of approved USB-connected printer devices.
- The list is a comma separated list of USB vid/pid values. Example: 0351/0872,135E/2179
-
-
-
-
-
- Select the method by which Queue-specific files will be processed.
- Manage processing of Queue-Specific files:
-
-
- Select the driver signature mechanism for this computer:
-
-
-
- Enter a File Hash paired with the name of the file the Hash represents below.
-
- File Hash File Name:
-
-
- Configure protocol options for incoming RPC connections.
- Protocols to allow for incoming RPC connections:
- Authentication protocol to use for incoming RPC connections:
-
-
- Configure protocol options for outgoing RPC connections.
- Protocol to use for outgoing RPC connections:
- Use authentication for outgoing RPC connections:
-
-
- Configure port to use for RPC over TCP.
- RPC over TCP port:
-
-
- Configure options for Redirection Guard
- Redirection Guard Options
-
-
-
-
diff --git a/policy_templates/en-US/Printing2.adml b/policy_templates/en-US/Printing2.adml
deleted file mode 100644
index 5c81c84..0000000
--- a/policy_templates/en-US/Printing2.adml
+++ /dev/null
@@ -1,181 +0,0 @@
-
-
-
- Printing Group Policies
- Printing Group Policies valid on all Windows flavors except ARM
-
-
- Allow Print Spooler to accept client connections
- This policy controls whether the print spooler will accept client connections.
-
-When the policy is unconfigured or enabled, the spooler will always accept client connections.
-
-When the policy is disabled, the spooler will not accept client connections nor allow users to share printers. All printers currently shared will continue to be shared.
-
-The spooler must be restarted for changes to this policy to take effect.
- Automatically publish new printers in Active Directory
- Determines whether the Add Printer Wizard automatically publishes the computer's shared printers in Active Directory.
-
- If you enable this setting or do not configure it, the Add Printer Wizard automatically publishes all shared printers.
-
- If you disable this setting, the Add Printer Wizard does not automatically publish printers. However, you can publish shared printers manually.
-
- The default behavior is to automatically publish shared printers in Active Directory.
-
- Note: This setting is ignored if the "Allow printers to be published" setting is disabled.
- Prune printers that are not automatically republished
- Only if Print Server is found
- Determines whether the pruning service on a domain controller prunes printer objects that are not automatically republished whenever the host computer does not respond,just as it does with Windows 2000 printers. This setting applies to printers running operating systems other than Windows 2000 and to Windows 2000 printers published outside their forest.
-
- The Windows pruning service prunes printer objects from Active Directory when the computer that published them does not respond to contact requests. Computers running Windows 2000 Professional detect and republish deleted printer objects when they rejoin the network. However, because non-Windows 2000 computers and computers in other domains cannot republish printers in Active Directory automatically, by default, the system never prunes their printer objects.
-
- You can enable this setting to change the default behavior. To use this setting, select one of the following options from the "Prune non-republishing printers" box:
-
- -- "Never" specifies that printer objects that are not automatically republished are never pruned. "Never" is the default.
-
- -- "Only if Print Server is found" prunes printer objects that are not automatically republished only when the print server responds, but the printer is unavailable.
-
- -- "Whenever printer is not found" prunes printer objects that are not automatically republished whenever the host computer does not respond, just as it does with Windows 2000 printers.
-
- Note: This setting applies to printers published by using Active Directory Users and Computers or Pubprn.vbs. It does not apply to printers published by using Printers in Control Panel.
-
- Tip: If you disable automatic pruning, remember to delete printer objects manually whenever you remove a printer or print server.
- Never
- Whenever printer is not found
- 10 Minutes
- 12 Hours
- 1 Day
- 1 Hour
- 1 Week
- 2 Days
- 2 Weeks
- 30 Minutes
- 3 Days
- 3 Weeks
- 4 Days
- 4 Hours
- 4 Weeks
- 5 Days
- 5 Weeks
- 6 Days
- 6 Weeks
- 7 Weeks
- 8 Hours
- Continuous
- Directory pruning interval
- Specifies how often the pruning service on a domain controller contacts computers to verify that their printers are operational.
-
- The pruning service periodically contacts computers that have published printers. If a computer does not respond to the contact message (optionally, after repeated attempts), the pruning service "prunes" (deletes from Active Directory) printer objects the computer has published.
-
- By default, the pruning service contacts computers every eight hours and allows two repeated contact attempts before deleting printers from Active Directory.
-
- If you enable this setting, you can change the interval between contact attempts.
-
- If you do not configure or disable this setting the default values will be used.
-
- Note: This setting is used only on domain controllers.
- Infinite
- Above Normal
- Below Normal
- Highest
- Lowest
- Normal
- Directory pruning priority
- Sets the priority of the pruning thread.
-
- The pruning thread, which runs only on domain controllers, deletes printer objects from Active Directory if the printer that published the object does not respond to contact attempts. This process keeps printer information in Active Directory current.
-
- The thread priority influences the order in which the thread receives processor time and determines how likely it is to be preempted by higher priority threads.
-
- By default, the pruning thread runs at normal priority. However, you can adjust the priority to improve the performance of this service.
-
- Note: This setting is used only on domain controllers.
- Directory pruning retry
- Specifies how many times the pruning service on a domain controller repeats its attempt to contact a computer before pruning the computer's printers.
-
- The pruning service periodically contacts computers that have published printers to verify that the printers are still available for use. If a computer does not respond to the contact message, the message is repeated for the specified number of times. If the computer still fails to respond, then the pruning service "prunes" (deletes from Active Directory) printer objects the computer has published.
-
- By default, the pruning service contacts computers every eight hours and allows two retries before deleting printers from Active Directory. You can use this setting to change the number of retries.
-
- If you enable this setting, you can change the interval between attempts.
-
- If you do not configure or disable this setting, the default values are used.
-
- Note: This setting is used only on domain controllers.
- No Retry
- 1 Retry
- 2 Retries
- 3 Retries
- 4 Retries
- 5 Retries
- 6 Retries
- Log directory pruning retry events
- Specifies whether or not to log events when the pruning service on a domain controller attempts to contact a computer before pruning the computer's printers.
-
- The pruning service periodically contacts computers that have published printers to verify that the printers are still available for use. If a computer does not respond to the contact attempt, the attempt is retried a specified number of times, at a specified interval. The "Directory pruning retry" setting determines the number of times the attempt is retried; the default value is two retries. The "Directory Pruning Interval" setting determines the time interval between retries; the default value is every eight hours. If the computer has not responded by the last contact attempt, its printers are pruned from the directory.
-
- If you enable this policy setting, the contact events are recorded in the event log.
-
- If you disable or do not configure this policy setting, the contact events are not recorded in the event log.
-
- Note: This setting does not affect the logging of pruning events; the actual pruning of a printer is always logged.
-
- Note: This setting is used only on domain controllers.
- Allow printers to be published
- Determines whether the computer's shared printers can be published in Active Directory.
-
- If you enable this setting or do not configure it, users can use the "List in directory" option in the Printer's Properties' Sharing tab to publish shared printers in Active Directory.
-
- If you disable this setting, this computer's shared printers cannot be published in Active Directory, and the "List in directory" option is not available.
-
- Note: This settings takes priority over the setting "Automatically publish new printers in the Active Directory".
- Check published state
- Directs the system to periodically verify that the printers published by this computer still appear in Active Directory. This setting also specifies how often the system repeats the verification.
-
- By default, the system only verifies published printers at startup. This setting allows for periodic verification while the computer is operating.
-
- To enable this additional verification, enable this setting, and then select a verification interval.
-
- To disable verification, disable this setting, or enable this setting and select "Never" for the verification interval.
- 12 Hours
- 1 Day
- 1 Hour
- 30 Minutes
- 4 Hours
- 8 Hours
- Never
- Allow pruning of published printers
- Determines whether the domain controller can prune (delete from Active Directory) the printers published by this computer.
-
- By default, the pruning service on the domain controller prunes printer objects from Active Directory if the computer that published them does not respond to contact requests. When the computer that published the printers restarts, it republishes any deleted printer objects.
-
- If you enable this setting or do not configure it, the domain controller prunes this computer's printers when the computer does not respond.
-
- If you disable this setting, the domain controller does not prune this computer's printers. This setting is designed to prevent printers from being pruned when the computer is temporarily disconnected from the network.
-
- Note: You can use the "Directory Pruning Interval" and "Directory Pruning Retry" settings to adjust the contact interval and number of contact attempts.
-
-
-
- Select the method by which non-republishing printers should be pruned.
- Prune non-republishing printers:
-
-
- The Pruning Interval determines the period of time the pruner
- sleeps between checks for abandoned PrintQueues.
- Interval:
-
-
- Use this setting to change the pruning thread's priority.
- Priority level:
-
-
- Retries:
-
-
- Verify that all published printers are in Active Directory.
- Published State Check Interval:
-
-
-
-
diff --git a/policy_templates/en-US/Programs.adml b/policy_templates/en-US/Programs.adml
deleted file mode 100644
index b5f95b4..0000000
--- a/policy_templates/en-US/Programs.adml
+++ /dev/null
@@ -1,90 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Calculator
- Allow Graphing Calculator
- This policy setting allows you to control whether graphing functionality is available in the Windows Calculator app. If you disable this policy setting, graphing functionality will not be accessible in the Windows Calculator app. If you enable or don't configure this policy setting, users will be able to access graphing functionality.
- Programs
- Hide the Programs Control Panel
- This setting prevents users from using the Programs Control Panel in Category View and Programs and Features in Classic View.
-
-The Programs Control Panel allows users to uninstall, change, and repair programs, enable and disable Windows Features, set program defaults, view installed updates, and purchase software from Windows Marketplace. Programs published or assigned to the user by the system administrator also appear in the Programs Control Panel.
-
-If this setting is disabled or not configured, the Programs Control Panel in Category View and Programs and Features in Classic View will be available to all users.
-
-When enabled, this setting takes precedence over the other settings in this folder.
-
-This setting does not prevent users from using other tools and methods to install or uninstall programs.
-
- Hide "Programs and Features" page
- This setting prevents users from accessing "Programs and Features" to view, uninstall, change, or repair programs that are currently installed on the computer.
-
-If this setting is disabled or not configured, "Programs and Features" will be available to all users.
-
-This setting does not prevent users from using other tools and methods to view or uninstall programs. It also does not prevent users from linking to related Programs Control Panel Features including Windows Features, Get Programs, or Windows Marketplace.
-
- Hide "Installed Updates" page
- This setting prevents users from accessing "Installed Updates" page from the "View installed updates" task.
-
-"Installed Updates" allows users to view and uninstall updates currently installed on the computer. The updates are often downloaded directly from Windows Update or from various program publishers.
-
-If this setting is disabled or not configured, the "View installed updates" task and the "Installed Updates" page will be available to all users.
-
-This setting does not prevent users from using other tools and methods to install or uninstall programs.
-
- Hide "Set Program Access and Computer Defaults" page
- This setting removes the Set Program Access and Defaults page from the Programs Control Panel. As a result, users cannot view or change the associated page.
-
-The Set Program Access and Computer Defaults page allows administrators to specify default programs for certain activities, such as Web browsing or sending e-mail, as well as specify the programs that are accessible from the Start menu, desktop, and other locations.
-
-If this setting is disabled or not configured, the Set Program Access and Defaults button is available to all users.
-
-This setting does not prevent users from using other tools and methods to change program access or defaults.
-
-This setting does not prevent the Default Programs icon from appearing on the Start menu.
-
- Hide "Windows Marketplace"
- This setting prevents users from access the "Get new programs from Windows Marketplace" task from the Programs Control Panel in Category View, Programs and Features in Classic View, and Get Programs.
-
-Windows Marketplace allows users to purchase and/or download various programs to their computer for installation.
-
-Enabling this feature does not prevent users from navigating to Windows Marketplace using other methods.
-
-If this feature is disabled or is not configured, the "Get new programs from Windows Marketplace" task link will be available to all users.
-
-Note: If the "Hide Programs control Panel" setting is enabled, this setting is ignored.
-
- Hide "Get Programs" page
- Prevents users from viewing or installing published programs from the network.
-
-This setting prevents users from accessing the "Get Programs" page from the Programs Control Panel in Category View, Programs and Features in Classic View and the "Install a program from the netowrk" task. The "Get Programs" page lists published programs and provides an easy way to install them.
-
-Published programs are those programs that the system administrator has explicitly made available to the user with a tool such as Windows Installer. Typically, system administrators publish programs to notify users of their availability, to recommend their use, or to enable users to install them without having to search for installation files.
-
-If this setting is enabled, users cannot view the programs that have been published by the system administrator, and they cannot use the "Get Programs" page to install published programs. Enabling this feature does not prevent users from installing programs by using other methods. Users will still be able to view and installed assigned (partially installed) programs that are offered on the desktop or on the Start menu.
-
-If this setting is disabled or is not configured, the "Install a program from the network" task to the "Get Programs" page will be available to all users.
-
-Note: If the "Hide Programs Control Panel" setting is enabled, this setting is ignored.
-
- Hide "Windows Features"
- This setting prevents users from accessing the "Turn Windows features on or off" task from the Programs Control Panel in Category View, Programs and Features in Classic View, and Get Programs. As a result, users cannot view, enable, or disable various Windows features and services.
-
-If this setting is disabled or is not configured, the "Turn Windows features on or off" task will be available to all users.
-
-This setting does not prevent users from using other tools and methods to configure services or enable or disable program components.
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/PushToInstall.adml b/policy_templates/en-US/PushToInstall.adml
deleted file mode 100644
index 66b6006..0000000
--- a/policy_templates/en-US/PushToInstall.adml
+++ /dev/null
@@ -1,12 +0,0 @@
-
-
- Push To Install Policy
- Push To Install Policy
-
-
- Push To Install
- Turn off Push To Install service
- If you enable this setting, users will not be able to push Apps to this device from the Microsoft Store running on other devices or the web.
-
-
-
diff --git a/policy_templates/en-US/QOS.adml b/policy_templates/en-US/QOS.adml
deleted file mode 100644
index c189225..0000000
--- a/policy_templates/en-US/QOS.adml
+++ /dev/null
@@ -1,296 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Best Effort service type (ServiceTypeBestEffort). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Best Effort service type.
-
-If you disable this setting, the system uses the default DSCP value of 0.
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Controlled Load service type (ServiceTypeControlledLoad). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Controlled Load service type.
-
-If you disable this setting, the system uses the default DSCP value of 24 (0x18).
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Guaranteed service type (ServiceTypeGuaranteed). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Guaranteed service type.
-
-If you disable this setting, the system uses the default DSCP value of 40 (0x28).
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Network Control service type (ServiceTypeNetworkControl). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Network Control service type.
-
-If you disable this setting, the system uses the default DSCP value of 48 (0x30).
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Qualitative service type (ServiceTypeQualitative). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Qualitative service type.
-
-If you disable this setting, the system uses the default DSCP value of 0.
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Best Effort service type (ServiceTypeBestEffort). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that do not conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Best Effort service type.
-
-If you disable this setting, the system uses the default DSCP value of 0.
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Controlled Load service type (ServiceTypeControlledLoad). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that do not conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Controlled Load service type.
-
-If you disable this setting, the system uses the default DSCP value of 0.
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Guaranteed service type (ServiceTypeGuaranteed). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that do not conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Guaranteed service type.
-
-If you disable this setting, the system uses the default DSCP value of 0.
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Network Control service type (ServiceTypeNetworkControl). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that do not conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Network Control service type.
-
-If you disable this setting, the system uses the default DSCP value of 0.
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate Layer-3 Differentiated Services Code Point (DSCP) value for packets with the Qualitative service type (ServiceTypeQualitative). The Packet Scheduler inserts the corresponding DSCP value in the IP header of the packets.
-
-This setting applies only to packets that do not conform to the flow specification.
-
-If you enable this setting, you can change the default DSCP value associated with the Qualitative service type.
-
-If you disable this setting, the system uses the default DSCP value of 0.
-
-Important: If the DSCP value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- DSCP value of conforming packets
- DSCP value of non-conforming packets
- Limit outstanding packets
- Specifies the maximum number of outstanding packets permitted on the system. When the number of outstanding packets reaches this limit, the Packet Scheduler postpones all submissions to network adapters until the number falls below this limit.
-
-"Outstanding packets" are packets that the Packet Scheduler has submitted to a network adapter for transmission, but which have not yet been sent.
-
-If you enable this setting, you can limit the number of outstanding packets.
-
-If you disable this setting or do not configure it, then the setting has no effect on the system.
-
-Important: If the maximum number of outstanding packets is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Limit reservable bandwidth
- Determines the percentage of connection bandwidth that the system can reserve. This value limits the combined bandwidth reservations of all programs running on the system.
-
-By default, the Packet Scheduler limits the system to 80 percent of the bandwidth of a connection, but you can use this setting to override the default.
-
-If you enable this setting, you can use the "Bandwidth limit" box to adjust the amount of bandwidth the system can reserve.
-
-If you disable this setting or do not configure it, the system uses the default value of 80 percent of the connection.
-
-Important: If a bandwidth limit is set for a particular network adapter in the registry, this setting is ignored when configuring that network adapter.
- QoS Packet Scheduler
- Best effort service type
- Best effort service type
- Best effort service type
- Controlled load service type
- Controlled load service type
- Controlled load service type
- Guaranteed service type
- Guaranteed service type
- Guaranteed service type
- Network control service type
- Network control service type
- Network control service type
- Non-conforming packets
- Qualitative service type
- Qualitative service type
- Qualitative service type
- Set timer resolution
- Determines the smallest unit of time that the Packet Scheduler uses when scheduling packets for transmission. The Packet Scheduler cannot schedule packets for transmission more frequently than permitted by the value of this entry.
-
-If you enable this setting, you can override the default timer resolution established for the system, usually units of 10 microseconds.
-
-If you disable this setting or do not configure it, the setting has no effect on the system.
-
-Important: If a timer resolution is specified in the registry for a particular network adapter, then this setting is ignored when configuring that network adapter.
- Specifies an alternate link layer (Layer-2) priority value for packets with the Best Effort service type (ServiceTypeBestEffort). The Packet Scheduler inserts the corresponding priority value in the Layer-2 header of the packets.
-
-If you enable this setting, you can change the default priority value associated with the Best Effort service type.
-
-If you disable this setting, the system uses the default priority value of 0.
-
-Important: If the Layer-2 priority value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate link layer (Layer-2) priority value for packets with the Controlled Load service type (ServiceTypeControlledLoad). The Packet Scheduler inserts the corresponding priority value in the Layer-2 header of the packets.
-
-If you enable this setting, you can change the default priority value associated with the Controlled Load service type.
-
-If you disable this setting, the system uses the default priority value of 0.
-
-Important: If the Layer-2 priority value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate link layer (Layer-2) priority value for packets with the Guaranteed service type (ServiceTypeGuaranteed). The Packet Scheduler inserts the corresponding priority value in the Layer-2 header of the packets.
-
-If you enable this setting, you can change the default priority value associated with the Guaranteed service type.
-
-If you disable this setting, the system uses the default priority value of 0.
-
-Important: If the Layer-2 priority value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate link layer (Layer-2) priority value for packets with the Network Control service type (ServiceTypeNetworkControl). The Packet Scheduler inserts the corresponding priority value in the Layer-2 header of the packets.
-
-If you enable this setting, you can change the default priority value associated with the Network Control service type.
-
-If you disable this setting, the system uses the default priority value of 0.
-
-Important: If the Layer-2 priority value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate link layer (Layer-2) priority value for packets that do not conform to the flow specification. The Packet Scheduler inserts the corresponding priority value in the Layer-2 header of the packets.
-
-If you enable this setting, you can change the default priority value associated with nonconforming packets.
-
-If you disable this setting, the system uses the default priority value of 0.
-
-Important: If the Layer-2 priority value for nonconforming packets is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Specifies an alternate link layer (Layer-2) priority value for packets with the Qualitative service type (ServiceTypeQualitative). The Packet Scheduler inserts the corresponding priority value in the Layer-2 header of the packets.
-
-If you enable this setting, you can change the default priority value associated with the Qualitative service type.
-
-If you disable this setting, the system uses the default priority value of 0.
-
-Important: If the Layer-2 priority value for this service type is specified in the registry for a particular network adapter, this setting is ignored when configuring that network adapter.
- Layer-2 priority value
-
-
-
- Number of packets:
-
-
- Bandwidth limit (%):
-
-
- Enter a DSCP value for conforming packets with the
- Best effort service type
-
- DSCP value:
-
-
- Enter a DSCP value for non-conforming packets with the
- Best effort service type
-
- DSCP value:
-
-
- Enter a priority value for packets with the
- Best effort service type
-
- Priority value
-
-
- Enter a DSCP value for conforming packets with the
- Controlled load service type
-
- DSCP value:
-
-
- Enter a DSCP value for non-conforming packets with the
- Controlled load service type
-
- DSCP value:
-
-
- Enter a priority value for packets with the
- Controlled load service type
-
- Priority value
-
-
- Enter a DSCP value for conforming packets with the
- Guaranteed service type
-
- DSCP value:
-
-
- Enter a DSCP value for non-conforming packets with the
- Guaranteed service type
-
- DSCP value:
-
-
- Enter a priority value for packets with the
- Guaranteed service type
-
- Priority value
-
-
- Enter a DSCP value for conforming packets with the
- Network control service type
-
- DSCP value:
-
-
- Enter a DSCP value for non-conforming packets with the
- Network control service type
-
- DSCP value:
-
-
- Enter a priority value for packets with the
- Network control service type
-
- Priority value
-
-
- Enter a priority value for non-conforming packets.
-
- Priority value
-
-
- Enter a DSCP value for conforming packets with the
- Qualitative service type
-
- DSCP value:
-
-
- Enter a DSCP value for non-conforming packets with the
- Qualitative service type
-
- DSCP value:
-
-
- Enter a priority value for packets with the
- Qualitative service type
-
- Priority value
-
-
- Timer units (in microseconds):
-
-
-
-
diff --git a/policy_templates/en-US/RPC.adml b/policy_templates/en-US/RPC.adml
deleted file mode 100644
index 4bc8b37..0000000
--- a/policy_templates/en-US/RPC.adml
+++ /dev/null
@@ -1,153 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Remote Procedure Call
- Off
- Off with Exceptions
- On
- On with Exceptions
- Enable RPC Endpoint Mapper Client Authentication
- This policy setting controls whether RPC clients authenticate with the Endpoint Mapper Service when the call they are making contains authentication information. The Endpoint Mapper Service on computers running Windows NT4 (all service packs) cannot process authentication information supplied in this manner.
-
-If you disable this policy setting, RPC clients will not authenticate to the Endpoint Mapper Service, but they will be able to communicate with the Endpoint Mapper Service on Windows NT4 Server.
-
-If you enable this policy setting, RPC clients will authenticate to the Endpoint Mapper Service for calls that contain authentication information. Clients making such calls will not be able to communicate with the Windows NT4 Server Endpoint Mapper Service.
-
-If you do not configure this policy setting, it remains disabled. RPC clients will not authenticate to the Endpoint Mapper Service, but they will be able to communicate with the Windows NT4 Server Endpoint Mapper Service.
-
-Note: This policy will not be applied until the system is rebooted.
- Propagate extended error information
- This policy setting controls whether the RPC runtime generates extended error information when an error occurs.
-
-Extended error information includes the local time that the error occurred, the RPC version, and the name of the computer on which the error occurred, or from which it was propagated. Programs can retrieve the extended error information by using standard Windows application programming interfaces (APIs).
-
-If you disable this policy setting, the RPC Runtime only generates a status code to indicate an error condition.
-
-If you do not configure this policy setting, it remains disabled. It will only generate a status code to indicate an error condition.
-
-If you enable this policy setting, the RPC runtime will generate extended error information. You must select an error response type in the drop-down box.
-
--- "Off" disables all extended error information for all processes. RPC only generates an error code.
-
--- "On with Exceptions" enables extended error information, but lets you disable it for selected processes. To disable extended error information for a process while this policy setting is in effect, the command that starts the process must begin with one of the strings in the Extended Error Information Exception field.
-
--- "Off with Exceptions" disables extended error information, but lets you enable it for selected processes. To enable extended error information for a process while this policy setting is in effect, the command that starts the process must begin with one of the strings in the Extended Error Information Exception field.
-
--- "On" enables extended error information for all processes.
-
-Note: For information about the Extended Error Information Exception field, see the Windows Software Development Kit (SDK).
-
-Note: Extended error information is formatted to be compatible with other operating systems and older Microsoft operating systems, but only newer Microsoft operating systems can read and respond to the information.
-
-Note: The default policy setting, "Off," is designed for systems where extended error information is considered to be sensitive, and it should not be made available remotely.
-
-Note: This policy setting will not be applied until the system is rebooted.
- Off
- On
- Ignore Delegation Failure
- This policy setting controls whether the RPC Runtime ignores delegation failures when delegation is requested.
-
-The constrained delegation model, introduced in Windows Server 2003, does not report that delegation was enabled on a security context when a client connects to a server. Callers of RPC and COM are encouraged to use the RPC_C_QOS_CAPABILITIES_IGNORE_DELEGATE_FAILURE flag, but some applications written for the traditional delegation model prior to Windows Server 2003 may not use this flag and will encounter RPC_S_SEC_PKG_ERROR when connecting to a server that uses constrained delegation.
-
-If you disable this policy setting, the RPC Runtime will generate RPC_S_SEC_PKG_ERROR errors to applications that ask for delegation and connect to servers using constrained delegation.
-
-If you do not configure this policy setting, it remains disabled and will generate RPC_S_SEC_PKG_ERROR errors to applications that ask for delegation and connect to servers using constrained delegation.
-
-If you enable this policy setting, then:
-
--- "Off" directs the RPC Runtime to generate RPC_S_SEC_PKG_ERROR if the client asks for delegation, but the created security context does not support delegation.
-
--- "On" directs the RPC Runtime to accept security contexts that do not support delegation even if delegation was asked for.
-
-Note: This policy setting will not be applied until the system is rebooted.
- Set Minimum Idle Connection Timeout for RPC/HTTP connections
- This policy setting controls the idle connection timeout for RPC/HTTP connections.
-
-This policy setting is useful in cases where a network agent like an HTTP proxy or a router uses a lower idle connection timeout than the IIS server running the RPC/HTTP proxy. In such cases, RPC/HTTP clients may encounter errors because connections will be timed out faster than expected. Using this policy setting you can force the RPC Runtime and the RPC/HTTP Proxy to use a lower connection timeout.
-
-This policy setting is only applicable when the RPC Client, the RPC Server and the RPC HTTP Proxy are all running Windows Server 2003 family/Windows XP SP1 or higher versions. If either the RPC Client or the RPC Server or the RPC HTTP Proxy run on an older version of Windows, this policy setting will be ignored.
-
-The minimum allowed value for this policy setting is 90 seconds. The maximum is 7200 seconds (2 hours).
-
-If you disable this policy setting, the idle connection timeout on the IIS server running the RPC HTTP proxy will be used.
-
-If you do not configure this policy setting, it will remain disabled. The idle connection timeout on the IIS server running the RPC HTTP proxy will be used.
-
-If you enable this policy setting, and the IIS server running the RPC HTTP proxy is configured with a lower idle connection timeout, the timeout on the IIS server is used. Otherwise, the provided timeout value is used. The timeout is given in seconds.
-
-Note: This policy setting will not be applied until the system is rebooted.
- Restrict Unauthenticated RPC clients
- This policy setting controls how the RPC server runtime handles unauthenticated RPC clients connecting to RPC servers.
-
-This policy setting impacts all RPC applications. In a domain environment this policy setting should be used with caution as it can impact a wide range of functionality including group policy processing itself. Reverting a change to this policy setting can require manual intervention on each affected machine. This policy setting should never be applied to a domain controller.
-
-If you disable this policy setting, the RPC server runtime uses the value of "Authenticated" on Windows Client, and the value of "None" on Windows Server versions that support this policy setting.
-
-If you do not configure this policy setting, it remains disabled. The RPC server runtime will behave as though it was enabled with the value of "Authenticated" used for Windows Client and the value of "None" used for Server SKUs that support this policy setting.
-
-If you enable this policy setting, it directs the RPC server runtime to restrict unauthenticated RPC clients connecting to RPC servers running on a machine. A client will be considered an authenticated client if it uses a named pipe to communicate with the server or if it uses RPC Security. RPC Interfaces that have specifically requested to be accessible by unauthenticated clients may be exempt from this restriction, depending on the selected value for this policy setting.
-
--- "None" allows all RPC clients to connect to RPC Servers running on the machine on which the policy setting is applied.
-
--- "Authenticated" allows only authenticated RPC Clients (per the definition above) to connect to RPC Servers running on the machine on which the policy setting is applied. Exemptions are granted to interfaces that have requested them.
-
--- "Authenticated without exceptions" allows only authenticated RPC Clients (per the definition above) to connect to RPC Servers running on the machine on which the policy setting is applied. No exceptions are allowed.
-
-Note: This policy setting will not be applied until the system is rebooted.
- Authenticated
- Authenticated without exceptions
- None
- Auto1
- Auto2
- Full
- None
- Maintain RPC Troubleshooting State Information
- This policy setting determines whether the RPC Runtime maintains RPC state information for the system, and how much information it maintains. Basic state information, which consists only of the most commonly needed state data, is required for troubleshooting RPC problems.
-
-If you disable this policy setting, the RPC runtime defaults to "Auto2" level.
-
-If you do not configure this policy setting, the RPC defaults to "Auto2" level.
-
-If you enable this policy setting, you can use the drop-down box to determine which systems maintain RPC state information.
-
--- "None" indicates that the system does not maintain any RPC state information. Note: Because the basic state information required for troubleshooting has a negligible effect on performance and uses only about 4K of memory, this setting is not recommended for most installations.
-
--- "Auto1" directs RPC to maintain basic state information only if the computer has at least 64 MB of memory.
-
--- "Auto2" directs RPC to maintain basic state information only if the computer has at least 128 MB of memory and is running Windows 2000 Server, Windows 2000 Advanced Server, or Windows 2000 Datacenter Server.
-
--- "Server" directs RPC to maintain basic state information on the computer, regardless of its capacity.
-
--- "Full" directs RPC to maintain complete RPC state information on the system, regardless of its capacity. Because this level can degrade performance, it is recommended for use only while you are investigating an RPC problem.
-
-Note: To retrieve the RPC state information from a system that maintains it, you must use a debugging tool.
-
-Note: This policy setting will not be applied until the system is rebooted.
- Server
-
-
-
- Propagation of extended error information:
-
-
-
-
-
- Ignoring Delegation Failure:
-
-
- Minimum Idle Connection Timeout (in seconds):
-
-
- RPC Runtime Unauthenticated Client Restriction to Apply:
-
-
- RPC Runtime state information to maintain:
-
-
-
-
diff --git a/policy_templates/en-US/RacWmiProv.adml b/policy_templates/en-US/RacWmiProv.adml
deleted file mode 100644
index c465dc7..0000000
--- a/policy_templates/en-US/RacWmiProv.adml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Reliability Analysis Component
- Reliability Analysis Component
-
-
- Windows Reliability Analysis
- Configure Reliability WMI Providers
- This policy setting allows the Windows Management Instrumentation (WMI) providers Win32_ReliabilityStabilitymetrics and Win32_ReliabilityRecords to provide data to Reliability Monitor in the Security and Maintenance control panel, and to respond to WMI requests.
-
-If you enable or do not configure this policy setting, the listed providers will respond to WMI queries, and Reliability Monitor will display system reliability information.
-
-If you disable this policy setting, Reliability Monitor will not display system reliability information, and WMI-capable applications will be unable to access reliability information from the listed providers.
-
-
-
diff --git a/policy_templates/en-US/Radar.adml b/policy_templates/en-US/Radar.adml
deleted file mode 100644
index 6d4d3fd..0000000
--- a/policy_templates/en-US/Radar.adml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Windows Resource Exhaustion Detection and Resolution
- Configure Scenario Execution Level
- Determines the execution level for Windows Resource Exhaustion Detection and Resolution.
-
-If you enable this policy setting, you must select an execution level from the dropdown menu. If you select problem detection and troubleshooting only, the Diagnostic Policy Service (DPS) will detect Windows Resource Exhaustion problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will detect Windows Resource Exhaustion problems and indicate to the user that assisted resolution is available.
-
-If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve any Windows Resource Exhaustion problems that are handled by the DPS.
-
-If you do not configure this policy setting, the DPS will enable Windows Resource Exhaustion for resolution by default.
-
-This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
-
-No system restart or service restart is required for this policy to take effect: changes take effect immediately.
-
-This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios will not be executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
- Detection, Troubleshooting and Resolution
- Detection and Troubleshooting Only
-
-
-
- Scenario Execution Level
-
-
-
-
diff --git a/policy_templates/en-US/ReAgent.adml b/policy_templates/en-US/ReAgent.adml
deleted file mode 100644
index 784afa3..0000000
--- a/policy_templates/en-US/ReAgent.adml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- Recovery
- Recovery
-
-
- Recovery
- Allow restore of system to default state
- Requirements: Windows 7
- Description: This policy setting controls whether users can access the options in Recovery (in Control Panel) to restore the computer to the original state or from a user-created system image.
-
- If you enable or do not configure this policy setting, the items "Use a system image you created earlier to recover your computer" and "Reinstall Windows" (or "Return your computer to factory condition") appears on the "Advanced recovery methods" page of Recovery (in Control Panel) and will allow the user to restore the computer to the original state or from a user-created system image. This is the default setting.
-
- If you disable this policy setting, the items "Use a system image you created earlier to recover your computer" and "Reinstall Windows" (or "Return your computer to factory condition") in Recovery (in Control Panel) will be unavailable. However, with this policy setting disabled, users can still restore the computer to the original state or from a user-created system image by restarting the computer and accessing the System Recovery Options menu, if it is available.
-
-
-
diff --git a/policy_templates/en-US/Reliability.adml b/policy_templates/en-US/Reliability.adml
deleted file mode 100644
index 3335dc4..0000000
--- a/policy_templates/en-US/Reliability.adml
+++ /dev/null
@@ -1,70 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Enable Persistent Time Stamp
- This policy setting allows the system to detect the time of unexpected shutdowns by writing the current time to disk on a schedule controlled by the Timestamp Interval.
-
-If you enable this policy setting, you are able to specify how often the Persistent System Timestamp is refreshed and subsequently written to the disk. You can specify the Timestamp Interval in seconds.
-
-If you disable this policy setting, the Persistent System Timestamp is turned off and the timing of unexpected shutdowns is not recorded.
-
-If you do not configure this policy setting, the Persistent System Timestamp is refreshed according the default, which is every 60 seconds beginning with Windows Server 2003.
-
-Note: This feature might interfere with power configuration settings that turn off hard disks after a period of inactivity. These power settings may be accessed in the Power Options Control Panel.
- Report unplanned shutdown events
- This policy setting controls whether or not unplanned shutdown events can be reported when error reporting is enabled.
-
-If you enable this policy setting, error reporting includes unplanned shutdown events.
-
-If you disable this policy setting, unplanned shutdown events are not included in error reporting.
-
-If you do not configure this policy setting, users can adjust this setting using the control panel, which is set to "Upload unplanned shutdown events" by default.
-
-Also see the "Configure Error Reporting" policy setting.
- Activate Shutdown Event Tracker System State Data feature
- This policy setting defines when the Shutdown Event Tracker System State Data feature is activated.
-
-The system state data file contains information about the basic system state as well as the state of all running processes.
-
-If you enable this policy setting, the System State Data feature is activated when the user indicates that the shutdown or restart is unplanned.
-
-If you disable this policy setting, the System State Data feature is never activated.
-
-If you do not configure this policy setting, the default behavior for the System State Data feature occurs.
-
-Note: By default, the System State Data feature is always enabled on Windows Server 2003. See "Supported on" for all supported versions.
- Display Shutdown Event Tracker
- Always
- The Shutdown Event Tracker can be displayed when you shut down a workstation or server. This is an extra set of questions that is displayed when you invoke a shutdown to collect information related to why you are shutting down the computer.
-
-If you enable this setting and choose "Always" from the drop-down menu list, the Shutdown Event Tracker is displayed when the computer shuts down.
-
-If you enable this policy setting and choose "Server Only" from the drop-down menu list, the Shutdown Event Tracker is displayed when you shut down a computer running Windows Server. (See "Supported on" for supported versions.)
-
-If you enable this policy setting and choose "Workstation Only" from the drop-down menu list, the Shutdown Event Tracker is displayed when you shut down a computer running a client version of Windows. (See "Supported on" for supported versions.)
-
-If you disable this policy setting, the Shutdown Event Tracker is not displayed when you shut down the computer.
-
-If you do not configure this policy setting, the default behavior for the Shutdown Event Tracker occurs.
-
-Note: By default, the Shutdown Event Tracker is only displayed on computers running Windows Server.
- Server Only
- Workstation Only
-
-
-
- The setting allows you to customize how often the
- Persistent System Time Stamp is written to the disk.
- The range is 1 to 86400 seconds (1 day).
- Seconds:
-
-
- Shutdown Event Tracker should be displayed:
-
-
-
-
diff --git a/policy_templates/en-US/RemoteAssistance.adml b/policy_templates/en-US/RemoteAssistance.adml
deleted file mode 100644
index bf97a94..0000000
--- a/policy_templates/en-US/RemoteAssistance.adml
+++ /dev/null
@@ -1,153 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn on session logging
- This policy setting allows you to turn logging on or off. Log files are located in the user's Documents folder under Remote Assistance.
-
-If you enable this policy setting, log files are generated.
-
-If you disable this policy setting, log files are not generated.
-
-If you do not configure this setting, application-based settings are used.
- Turn on bandwidth optimization
- No optimization
- No full window drag
- Turn off background
- Full optimization
- This policy setting allows you to improve performance in low bandwidth scenarios.
-
-This setting is incrementally scaled from "No optimization" to "Full optimization". Each incremental setting includes the previous optimization setting.
-
-For example:
-
-"Turn off background" will include the following optimizations:
--No full window drag
--Turn off background
-
-"Full optimization" will include the following optimizations:
--Use 16-bit color (8-bit color in Windows Vista)
--Turn off font smoothing (not supported in Windows Vista)
--No full window drag
--Turn off background
-
-If you enable this policy setting, bandwidth optimization occurs at the level specified.
-
-If you disable this policy setting, application-based settings are used.
-
-If you do not configure this policy setting, application-based settings are used.
- Customize warning messages
- This policy setting lets you customize warning messages.
-
-The "Display warning message before sharing control" policy setting allows you to specify a custom message to display before a user shares control of his or her computer.
-
-The "Display warning message before connecting" policy setting allows you to specify a custom message to display before a user allows a connection to his or her computer.
-
-If you enable this policy setting, the warning message you specify overrides the default message that is seen by the novice.
-
-If you disable this policy setting, the user sees the default warning message.
-
-If you do not configure this policy setting, the user sees the default warning message.
- Configure Solicited Remote Assistance
- Allow helpers to remotely control the computer
- Days
- Hours
- Minutes
- Allow helpers to only view the computer
- This policy setting allows you to turn on or turn off Solicited (Ask for) Remote Assistance on this computer.
-
-If you enable this policy setting, users on this computer can use email or file transfer to ask someone for help. Also, users can use instant messaging programs to allow connections to this computer, and you can configure additional Remote Assistance settings.
-
-If you disable this policy setting, users on this computer cannot use email or file transfer to ask someone for help. Also, users cannot use instant messaging programs to allow connections to this computer.
-
-If you do not configure this policy setting, users can turn on or turn off Solicited (Ask for) Remote Assistance themselves in System Properties in Control Panel. Users can also configure Remote Assistance settings.
-
-If you enable this policy setting, you have two ways to allow helpers to provide Remote Assistance: "Allow helpers to only view the computer" or "Allow helpers to remotely control the computer."
-
-The "Maximum ticket time" policy setting sets a limit on the amount of time that a Remote Assistance invitation created by using email or file transfer can remain open.
-
-The "Select the method for sending email invitations" setting specifies which email standard to use to send Remote Assistance invitations. Depending on your email program, you can use either the Mailto standard (the invitation recipient connects through an Internet link) or the SMAPI (Simple MAPI) standard (the invitation is attached to your email message). This policy setting is not available in Windows Vista since SMAPI is the only method supported.
-
-If you enable this policy setting you should also enable appropriate firewall exceptions to allow Remote Assistance communications.
- Mailto
- Simple MAPI
- Configure Offer Remote Assistance
- Allow helpers to remotely control the computer
- Allow helpers to only view the computer
- This policy setting allows you to turn on or turn off Offer (Unsolicited) Remote Assistance on this computer.
-
-If you enable this policy setting, users on this computer can get help from their corporate technical support staff using Offer (Unsolicited) Remote Assistance.
-
-If you disable this policy setting, users on this computer cannot get help from their corporate technical support staff using Offer (Unsolicited) Remote Assistance.
-
-If you do not configure this policy setting, users on this computer cannot get help from their corporate technical support staff using Offer (Unsolicited) Remote Assistance.
-
-If you enable this policy setting, you have two ways to allow helpers to provide Remote Assistance: "Allow helpers to only view the computer" or "Allow helpers to remotely control the computer." When you configure this policy setting, you also specify the list of users or user groups that are allowed to offer remote assistance.
-
-To configure the list of helpers, click "Show." In the window that opens, you can enter the names of the helpers. Add each user or group one by one. When you enter the name of the helper user or user groups, use the following format:
-
-<Domain Name>\<User Name> or
-
-<Domain Name>\<Group Name>
-
-If you enable this policy setting, you should also enable firewall exceptions to allow Remote Assistance communications. The firewall exceptions required for Offer (Unsolicited) Remote Assistance depend on the version of Windows you are running.
-
-Windows Vista and later
-
-Enable the Remote Assistance exception for the domain profile. The exception must contain:
-Port 135:TCP
-%WINDIR%\System32\msra.exe
-%WINDIR%\System32\raserver.exe
-
-Windows XP with Service Pack 2 (SP2) and Windows XP Professional x64 Edition with Service Pack 1 (SP1)
-
-Port 135:TCP
-%WINDIR%\PCHealth\HelpCtr\Binaries\Helpsvc.exe
-%WINDIR%\PCHealth\HelpCtr\Binaries\Helpctr.exe
-%WINDIR%\System32\Sessmgr.exe
-
-For computers running Windows Server 2003 with Service Pack 1 (SP1)
-
-Port 135:TCP
-%WINDIR%\PCHealth\HelpCtr\Binaries\Helpsvc.exe
-%WINDIR%\PCHealth\HelpCtr\Binaries\Helpctr.exe
-Allow Remote Desktop Exception
- Remote Assistance
-
- Allow only Windows Vista or later connections
- This policy setting enables Remote Assistance invitations to be generated with improved encryption so that only computers running this version (or later versions) of the operating system can connect. This policy setting does not affect Remote Assistance connections that are initiated by instant messaging contacts or the unsolicited Offer Remote Assistance.
-
-If you enable this policy setting, only computers running this version (or later versions) of the operating system can connect to this computer.
-
-If you disable this policy setting, computers running this version and a previous version of the operating system can connect to this computer.
-
-If you do not configure this policy setting, users can configure the setting in System Properties in the Control Panel.
-
-
-
- Optimize settings for reduced bandwidth:
-
-
-
-
-
-
-
-
-
-
- Permit remote control of this computer:
- Maximum ticket time (value):
- Maximum ticket time (units):
- Method for sending email invitations:
-
-
- Permit remote control of this computer:
- Helpers:
-
-
-
-
diff --git a/policy_templates/en-US/RemovableStorage.adml b/policy_templates/en-US/RemovableStorage.adml
deleted file mode 100644
index 021d528..0000000
--- a/policy_templates/en-US/RemovableStorage.adml
+++ /dev/null
@@ -1,182 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Set time (in seconds) to force reboot
- This policy setting configures the amount of time (in seconds) that the operating system waits to reboot in order to enforce a change in access rights to removable storage devices.
-
-If you enable this policy setting, you can set the number of seconds you want the system to wait until a reboot.
-
-If you disable or do not configure this setting, the operating system does not force a reboot.
-
-Note: If no reboot is forced, the access right does not take effect until the operating system is restarted.
- CD and DVD: Deny read access
- This policy setting denies read access to the CD and DVD removable storage class.
-
-If you enable this policy setting, read access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, read access is allowed to this removable storage class.
- CD and DVD: Deny write access
- This policy setting denies write access to the CD and DVD removable storage class.
-
-If you enable this policy setting, write access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, write access is allowed to this removable storage class.
- CD and DVD: Deny execute access
- This policy setting denies execute access to the CD and DVD removable storage class.
-
-If you enable this policy setting, execute access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, execute access is allowed to this removable storage class.
- Custom Classes: Deny read access
- This policy setting denies read access to custom removable storage classes.
-
-If you enable this policy setting, read access is denied to these removable storage classes.
-
-If you disable or do not configure this policy setting, read access is allowed to these removable storage classes.
- Custom Classes: Deny write access
- This policy setting denies write access to custom removable storage classes.
-
-If you enable this policy setting, write access is denied to these removable storage classes.
-
-If you disable or do not configure this policy setting, write access is allowed to these removable storage classes.
- Removable Storage Access
- Floppy Drives: Deny read access
- This policy setting denies read access to the Floppy Drives removable storage class, including USB Floppy Drives.
-
-If you enable this policy setting, read access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, read access is allowed to this removable storage class.
- Floppy Drives: Deny write access
- This policy setting denies write access to the Floppy Drives removable storage class, including USB Floppy Drives.
-
-If you enable this policy setting, write access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, write access is allowed to this removable storage class.
- Floppy Drives: Deny execute access
- This policy setting denies execute access to the Floppy Drives removable storage class, including USB Floppy Drives.
-
-If you enable this policy setting, execute access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, execute access is allowed to this removable storage class.
- PAP Devices: Deny read access
- This policy setting denies read access to removable disks, which may include portable media players.
-
-If you enable this policy setting, read access will be denied to this removable storage class.
-
-If you disable or do not configure this policy setting, read access will be allowed to this removable storage class.
- PAP Devices: Deny write access
- This policy setting denies write access to removable disks, which may include portable media players.
-
-If you enable this policy setting, write access will be denied to this removable storage class.
-
-If you disable or do not configure this policy setting, write access will be allowed to this removable storage class.
- PAP Devices: Deny execute access
- This policy setting denies execute access to removable disks, which may include portable media players.
-
-If you enable this policy setting, execute access will be denied to this removable storage class.
-
-If you disable or do not configure this policy setting, execute access will be allowed to this removable storage class.
- Removable Disks: Deny read access
- This policy setting denies read access to removable disks.
-
-If you enable this policy setting, read access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, read access is allowed to this removable storage class.
- Removable Disks: Deny write access
- This policy setting denies write access to removable disks.
-
-If you enable this policy setting, write access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, write access is allowed to this removable storage class.
-
-Note: To require that users write data to BitLocker-protected storage, enable the policy setting "Deny write access to drives not protected by BitLocker," which is located in "Computer Configuration\Administrative Templates\Windows Components\BitLocker Drive Encryption\Removable Data Drives."
- Removable Disks: Deny execute access
- This policy setting denies execute access to removable disks.
-
-If you enable this policy setting, execute access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, execute access is allowed to this removable storage class.
- All Removable Storage classes: Deny all access
- Configure access to all removable storage classes.
-
-This policy setting takes precedence over any individual removable storage policy settings. To manage individual classes, use the policy settings available for each class.
-
-If you enable this policy setting, no access is allowed to any removable storage class.
-
-If you disable or do not configure this policy setting, write and read accesses are allowed to all removable storage classes.
- Tape Drives: Deny read access
- This policy setting denies read access to the Tape Drive removable storage class.
-
-If you enable this policy setting, read access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, read access is allowed to this removable storage class.
- Tape Drives: Deny write access
- This policy setting denies write access to the Tape Drive removable storage class.
-
-If you enable this policy setting, write access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, write access is allowed to this removable storage class.
- Tape Drives: Deny execute access
- This policy setting denies execute access to the Tape Drive removable storage class.
-
-If you enable this policy setting, execute access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, execute access is allowed to this removable storage class.
- WPD Devices: Deny read access
- This policy setting denies read access to removable disks, which may include media players, cellular phones, auxiliary displays, and CE devices.
-
-If you enable this policy setting, read access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, read access is allowed to this removable storage class.
- WPD Devices: Deny write access
- This policy setting denies write access to removable disks, which may include media players, cellular phones, auxiliary displays, and CE devices.
-
-If you enable this policy setting, write access is denied to this removable storage class.
-
-If you disable or do not configure this policy setting, write access is allowed to this removable storage class.
- All Removable Storage: Allow direct access in remote sessions
- This policy setting grants normal users direct access to removable storage devices in remote sessions.
-
-If you enable this policy setting, remote users can open direct handles to removable storage devices in remote sessions.
-
-If you disable or do not configure this policy setting, remote users cannot open direct handles to removable storage devices in remote sessions.
-
-
-
- Time (in seconds):
-
-
- Time (in seconds):
-
-
- Enter GUID in format {xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx},
- include brackets. Each custom GUID must be a separate entry
- GUID for custom removable storage class:
-
-
- Enter GUID in format {xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx},
- include brackets. Each custom GUID must be a separate entry
- GUID for custom removable storage class:
-
-
- Enter GUID in format {xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx},
- include brackets. Each custom GUID must be a separate entry
- GUID for custom removable storage class:
-
-
- Enter GUID in format {xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx},
- include brackets. Each custom GUID must be a separate entry
- GUID for custom removable storage class:
-
-
- Enter GUID in format {xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx},
- include brackets. Each custom GUID must be a separate entry
- GUID for custom removable storage class:
-
-
-
-
diff --git a/policy_templates/en-US/Scripts.adml b/policy_templates/en-US/Scripts.adml
deleted file mode 100644
index 00f661d..0000000
--- a/policy_templates/en-US/Scripts.adml
+++ /dev/null
@@ -1,161 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Specify maximum wait time for Group Policy scripts
- This policy setting determines how long the system waits for scripts applied by Group Policy to run.
-
-This setting limits the total time allowed for all logon, logoff, startup, and shutdown scripts applied by Group Policy to finish running. If the scripts have not finished running when the specified time expires, the system stops script processing and records an error event.
-
-If you enable this setting, then, in the Seconds box, you can type a number from 1 to 32,000 for the number of seconds you want the system to wait for the set of scripts to finish. To direct the system to wait until the scripts have finished, no matter how long they take, type 0.
-
-This interval is particularly important when other system tasks must wait while the scripts complete. By default, each startup script must complete before the next one runs. Also, you can use the ""Run logon scripts synchronously"" setting to direct the system to wait for the logon scripts to complete before loading the desktop.
-
-An excessively long interval can delay the system and inconvenience users. However, if the interval is too short, prerequisite tasks might not be done, and the system can appear to be ready prematurely.
-
-If you disable or do not configure this setting the system lets the combined set of scripts run for up to 600 seconds (10 minutes). This is the default.
- Run legacy logon scripts hidden
- This policy setting hides the instructions in logon scripts written for Windows NT 4.0 and earlier.
-
-Logon scripts are batch files of instructions that run when the user logs on. By default, Windows 2000 displays the instructions in logon scripts written for Windows NT 4.0 and earlier in a command window as they run, although it does not display logon scripts written for Windows 2000.
-
-If you enable this setting, Windows 2000 does not display logon scripts written for Windows NT 4.0 and earlier.
-
-If you disable or do not configure this policy setting, Windows 2000 displays login scripts written for Windows NT 4.0 and earlier.
-
-Also, see the "Run Logon Scripts Visible" setting.
-
- Display instructions in logoff scripts as they run
- This policy setting displays the instructions in logoff scripts as they run.
-
-Logoff scripts are batch files of instructions that run when the user logs off. By default, the system does not display the instructions in the logoff script.
-
-If you enable this policy setting, the system displays each instruction in the logoff script as it runs. The instructions appear in a command window. This policy setting is designed for advanced users.
-
-If you disable or do not configure this policy setting, the instructions are suppressed.
- Run logon scripts synchronously
- This policy setting directs the system to wait for logon scripts to finish running before it starts the File Explorer interface program and creates the desktop.
-
-If you enable this policy setting, File Explorer does not start until the logon scripts have finished running. This policy setting ensures that logon script processing is complete before the user starts working, but it can delay the appearance of the desktop.
-
-If you disable or do not configure this policy setting, the logon scripts and File Explorer are not synchronized and can run simultaneously.
-
-This policy setting appears in the Computer Configuration and User Configuration folders. The policy setting set in Computer Configuration takes precedence over the policy setting set in User Configuration.
- Display instructions in logon scripts as they run
- This policy setting displays the instructions in logon scripts as they run.
-
-Logon scripts are batch files of instructions that run when the user logs on. By default, the system does not display the instructions in logon scripts.
-
-If you enable this policy setting, the system displays each instruction in the logon script as it runs. The instructions appear in a command window. This policy setting is designed for advanced users.
-
-If you disable or do not configure this policy setting, the instructions are suppressed.
-
- Run Windows PowerShell scripts first at computer startup, shutdown
- This policy setting determines whether Windows PowerShell scripts are run before non-Windows PowerShell scripts during computer startup and shutdown. By default, Windows PowerShell scripts run after non-Windows PowerShell scripts.
-
-If you enable this policy setting, within each applicable Group Policy Object (GPO), Windows PowerShell scripts are run before non-Windows PowerShell scripts during computer startup and shutdown.
-
-For example, assume the following scenario:
-
-There are three GPOs (GPO A, GPO B, and GPO C). This policy setting is enabled in GPO A.
-
-GPO B and GPO C include the following computer startup scripts:
-
-GPO B: B.cmd, B.ps1
-GPO C: C.cmd, C.ps1
-
-Assume also that there are two computers, DesktopIT and DesktopSales.
-For DesktopIT, GPOs A, B, and C are applied. Therefore, the scripts for GPOs B and C run in the following order for DesktopIT:
-
-Within GPO B: B.ps1, B.cmd
-Within GPO C: C.ps1, C.cmd
-
-For DesktopSales, GPOs B and C are applied, but not GPO A. Therefore, the scripts for GPOs B and C run in the following order for DesktopSales:
-
-Within GPO B: B.cmd, B.ps1
-Within GPO C: C.cmd, C.ps1
-
-Note: This policy setting determines the order in which computer startup and shutdown scripts are run within all applicable GPOs. You can override this policy setting for specific script types within a specific GPO by configuring the following policy settings for the GPO:
-
-Computer Configuration\Policies\Windows Settings\Scripts (Startup/Shutdown)\Startup
-Computer Configuration\Policies\Windows Settings\Scripts (Startup/Shutdown)\Shutdown
-
- Run Windows PowerShell scripts first at user logon, logoff
- This policy setting determines whether Windows PowerShell scripts are run before non-Windows PowerShell scripts during user logon and logoff. By default, Windows PowerShell scripts run after non-Windows PowerShell scripts.
-
-If you enable this policy setting, within each applicable Group Policy Object (GPO), PowerShell scripts are run before non-PowerShell scripts during user logon and logoff.
-
-For example, assume the following scenario:
-
-There are three GPOs (GPO A, GPO B, and GPO C). This policy setting is enabled in GPO A.
-
-GPO B and GPO C include the following user logon scripts:
-
-GPO B: B.cmd, B.ps1
-GPO C: C.cmd, C.ps1
-
-Assume also that there are two users, Qin Hong and Tamara Johnston.
-For Qin, GPOs A, B, and C are applied. Therefore, the scripts for GPOs B and C run in the following order for Qin:
-
-Within GPO B: B.ps1, B.cmd
-Within GPO C: C.ps1, C.cmd
-
-For Tamara, GPOs B and C are applied, but not GPO A. Therefore, the scripts for GPOs B and C run in the following order for Tamara:
-
-Within GPO B: B.cmd, B.ps1
-Within GPO C: C.cmd, C.ps1
-
-Note: This policy setting determines the order in which user logon and logoff scripts are run within all applicable GPOs. You can override this policy setting for specific script types within a specific GPO by configuring the following policy settings for the GPO:
-
-User Configuration\Policies\Windows Settings\Scripts (Logon/Logoff)\Logon
-User Configuration\Policies\Windows Settings\Scripts (Logon/Logoff)\Logoff
-
-This policy setting appears in the Computer Configuration and User Configuration folders. The policy setting set in Computer Configuration takes precedence over the setting set in User Configuration.
-
- Display instructions in shutdown scripts as they run
- This policy setting displays the instructions in shutdown scripts as they run.
-
-Shutdown scripts are batch files of instructions that run when the user restarts the system or shuts it down. By default, the system does not display the instructions in the shutdown script.
-
-If you enable this policy setting, the system displays each instruction in the shutdown script as it runs. The instructions appear in a command window.
-
-If you disable or do not configure this policy setting, the instructions are suppressed.
- Run startup scripts asynchronously
- This policy setting lets the system run startup scripts simultaneously.
-
-Startup scripts are batch files that run before the user is invited to log on. By default, the system waits for each startup script to complete before it runs the next startup script.
-
-If you enable this policy setting, the system does not coordinate the running of startup scripts. As a result, startup scripts can run simultaneously.
-
-If you disable or do not configure this policy setting, a startup cannot run until the previous script is complete.
-
-Note: Starting with Windows Vista operating system, scripts that are configured to run asynchronously are no longer visible on startup, whether the ""Run startup scripts visible"" policy setting is enabled or not.
- Display instructions in startup scripts as they run
- This policy setting displays the instructions in startup scripts as they run.
-
-Startup scripts are batch files of instructions that run before the user is invited to log on. By default, the system does not display the instructions in the startup script.
-
-If you enable this policy setting, the system displays each instruction in the startup script as it runs. Instructions appear in a command window. This policy setting is designed for advanced users.
-
-If you disable or do not configure this policy setting, the instructions are suppressed.
-
-Note: Starting with Windows Vista operating system, scripts that are configured to run asynchronously are no longer visible on startup, whether this policy setting is enabled or not.
- Allow logon scripts when NetBIOS or WINS is disabled
- This policy setting allows user logon scripts to run when the logon cross-forest, DNS suffixes are not configured, and NetBIOS or WINS is disabled. This policy setting affects all user accounts interactively logging on to the computer.
-
-If you enable this policy setting, user logon scripts run if NetBIOS or WINS is disabled during cross-forest logons without the DNS suffixes being configured.
-
-If you disable or do not configure this policy setting, user account cross-forest, interactive logging cannot run logon scripts if NetBIOS or WINS is disabled, and the DNS suffixes are not configured.
- Scripts
-
-
-
- Seconds:
- Range is 0 to 32000, use 0 for infinite wait time
-
-
-
-
diff --git a/policy_templates/en-US/Search.adml b/policy_templates/en-US/Search.adml
deleted file mode 100644
index 727b1ca..0000000
--- a/policy_templates/en-US/Search.adml
+++ /dev/null
@@ -1,411 +0,0 @@
-
-
- enter name here
- enter description here
-
-
- Search
- Windows Components
- Microsoft Windows Vista or later
- Microsoft Windows Vista, or any version of Windows with Windows Search 3.01 or later
- Microsoft Windows XP, or Windows Server 2003 with Windows Search version 3.01 or later
- Microsoft Windows XP, or Windows Server 2003 with Windows Search version 4.0 or later
- Microsoft Windows XP, Windows Server 2003 with Windows Search version 3.01, or any version of Microsoft Windows with Windows Search 4.0 or later
- Microsoft Windows XP, Windows Server 2003 with Windows Search version 3.01, or any version of Microsoft Windows with Windows Search 4.0
- Any version of Microsoft Windows with Windows Search 4.0 or later
- Microsoft Windows Vista, or any version of Windows with Windows Search 4.0 or later
- Microsoft Windows Vista with Windows Search 4.0 or later
- Allow use of diacritics
- Microsoft Windows 7 or later
- Any version of Microsoft Windows with Windows Search 4.0
- Microsoft Windows 8 or later
- Microsoft Windows 8.1 or later
- Microsoft Windows 8.1. Not supported on Windows 10 or later
- This policy setting allows words that contain diacritic characters to be treated as separate words. If you enable this policy setting, words that only differ in diacritics are treated as different words. If you disable this policy setting, words with diacritics and words without diacritics are treated as identical words. This policy setting is not configured by default. If you do not configure this policy setting, the local setting, configured through Control Panel, will be used. Note: By default, the Control Panel setting is set to treat words that differ only because of diacritics as the same word.
- Always use automatic language detection when indexing content and properties
- This policy setting determines when Windows uses automatic language detection results, and when it relies on indexing history. If you enable this policy setting, Windows will always use automatic language detection to index (as it did in Windows 7). Using automatic language detection can increase memory usage. We recommend enabling this policy setting only on PCs where documents are stored in many languages. If you disable or do not configure this policy setting, Windows will use automatic language detection only when it can determine the language of a document with high confidence.
- Do not allow locations on removable drives to be added to libraries
- This policy setting configures whether or not locations on removable drives can be added to libraries.
-
-If you enable this policy setting, locations on removable drives cannot be added to libraries. In addition, locations on removable drives cannot be indexed.
-
-If you disable or do not configure this policy setting, locations on removable drives can be added to libraries. In addition, locations on removable drives can be indexed.
- Don't search the web or display web results in Search
- This policy setting allows you to control whether or not Search can perform queries on the web, if web results are displayed in Search, and if search highlights are shown in the search box and in search home.
-
-If you enable this policy setting, queries won't be performed on the web, web results won't be displayed when a user performs a query in Search, and search highlights will not be shown in the search box and in search home.
-
-If you disable this policy setting, queries will be performed on the web, web results will be displayed when a user performs a query in Search, and search highlights will be shown in the search box and in search home.
-
-If you don't configure this policy setting, a user can choose whether or not Search can perform queries on the web, and if the web results are displayed in Search, and if search highlights are shown in the search box and in search home.
- Don't search the web or display web results in Search over metered connections
- This policy setting allows you to control whether or not Search can perform queries on the web over metered connections, and if the web results are displayed in Search.
-
-If you enable this policy setting, queries won't be performed on the web over metered connections and web results won't be displayed when a user performs a query in Search.
-
-If you disable this policy setting, queries will be performed on the web over metered connections and web results will be displayed when a user performs a query in Search.
-
-If you don't configure this policy setting, a user can choose whether or not Search can perform queries on the web over metered connections, and if the web results are displayed in Search.
-
-Note: If you enable the "Don't search the web or display web results in Search" policy setting, queries won't be performed on the web over metered connections and web results won't be displayed when a user performs a query in Search.
- Set what information is shared in Search
- This policy setting allows you to control what information is shared with Bing in Search.
-
-If you enable this policy setting, you can specify one of four settings, which users won't be able to change:
-
- -User info and location: Share a user's search history, some Microsoft account info, and specific location to personalize their search and other Microsoft experiences.
-
- -User info only: Share a user's search history and some Microsoft account info to personalize their search and other Microsoft experiences.
-
- -Anonymous info: Share usage information but don't share search history, Microsoft account info or specific location.
-
-If you disable or don't configure this policy setting, users can choose what information is shared in Search.
- Do not use location for Search
- This policy setting allows you to control whether or not Search will use the user's current location when providing search results.
-
-If you enable this policy setting, Search won't use the user's current location when providing search results.
-
-If you disable or don't configure this policy setting, search will use the user's current location when providing search results.
- Set the SafeSearch setting for Search
- This policy setting allows you to control the SafeSearch setting used when performing a query in Search.
-
-If you enable this policy setting, you can specify one of three SafeSearch settings, which users won't be able to change:
-
- -Strict: Filter out adult text, images, and videos from search results;
-
- -Moderate: Filter adult images and videos but not text from search results;
-
- -Off: Don't filter adult content from search results.
-
-If you disable or don't configure this policy setting, users can specify the SafeSearch setting.
-
-Windows 10 users should use Search/DoNotUseWebResults
- User info and location
- User info only
- Anonymous info
- Strict
- Moderate
- Off
- Prevent automatically adding shared folders to the Windows Search index
- This policy setting configures how Windows Search adds shared folders to the search index.
-
-If you enable this policy setting, Windows Search is prevented from automatically adding shared folders to the index. Windows Search does not automatically add shares created on the computer to the scope of the index.
-
-If you disable or do not configure this policy setting, Windows Search monitors which folders are shared or not shared on this computer, and automatically adds them to or removes them from the index.
- Prevent adding user-specified locations to the All Locations menu
- This policy setting allows you to enable or disable the Add/Remove location options on the All Locations menu as well as any defined locations that were made by a user. When this policy is not configured, the default behavior is to allow users to add and remove new locations to the locations menu. When the policy is enabled, the Add and Remove locations options and any previously defined user locations will not be visible. When the policy is disabled, both the Add and Remove locations options as well as any previously specified user locations will be visible.
- Prevent the display of advanced indexing options for Windows Search in the Control Panel
- This policy setting hides or displays the Advanced Options dialog for Search and Indexing Options in the Control Panel.
-
-If you enable this policy setting, the Advanced Options dialog for Search and Indexing Options in the Control Panel cannot be opened.
-
-If you disable or do not configure this policy setting, users can acess the Advanced Options dialog for Search and Indexing Options in the Control Panel. This is the default for this policy setting.
- Prevent adding UNC locations to index from Control Panel
- Enabling this policy prevents users from adding UNC locations to the index from the Search and Indexing Options in Control Panel. Any UNC locations that have already been added to the index by the user will not be removed.
-
-When this policy is disabled or not configured, users will be able to add UNC locations to the index.
-
-This policy has no effect if the Files on Microsoft Networks add-in is not installed.
-
-Disabled by default.
- Prevent customization of indexed locations in Control Panel
- If enabled, Search and Indexing Options in Control Panel does not allow opening the Modify Locations dialog. Otherwise it can be opened. Disabled by default.
- Allow indexing of encrypted files
- This policy setting allows encrypted items to be indexed. If you enable this policy setting, indexing will attempt to decrypt and index the content (access restrictions will still apply). If you disable this policy setting, the search service components (including non-Microsoft components) are expected not to index encrypted items or encrypted stores. This policy setting is not configured by default. If you do not configure this policy setting, the local setting, configured through Control Panel, will be used. By default, the Control Panel setting is set to not index encrypted content.
-
-When this setting is enabled or disabled, the index is rebuilt completely.
-
-Full volume encryption (such as BitLocker Drive Encryption or a non-Microsoft solution) must be used for the location of the index to maintain security for encrypted files.
- Prevent indexing when running on battery power to conserve energy
- If enabled, the indexer pauses whenever the computer is running on battery. If disabled, the indexing follows the default behavior. Default is disabled.
- Prevent clients from querying the index remotely
- If enabled, clients will be unable to query this computer's index remotely. Thus, when they are browsing network shares that are stored on this computer, they will not search them using the index. If disabled, client search requests will use this computer's index. Default is disabled.
- Disable indexer backoff
- If enabled, the search indexer backoff feature will be disabled. Indexing will continue at full speed even when system activity is high. If disabled, backoff logic will be used to throttle back indexing activity when system activity is high. Default is disabled.
- Prevent indexing files in offline files cache
- If enabled, files on network shares made available offline are not indexed. Otherwise they are indexed. Disabled by default.
- Enable indexing uncached Exchange folders
- Enabling this policy allows indexing of mail items on a Microsoft Exchange server when Microsoft Outlook is not running in cached mode. The default behavior for search is to not index uncached Exchange folders. Disabling this policy will block any indexing of uncached Exchange folders. Delegate mailboxes are managed separately from online mailboxes. The "Enable Indexing of Uncached Exchange Folders" has no effect on delegate mailboxes. To stop indexing of online and delegate mailboxes you must disable both policies.
- Enable indexing of online delegate mailboxes
- Enabling this policy allows indexing of items for online delegate mailboxes on a Microsoft Exchange server. This policy affects only delegate mailboxes that are online. Microsoft Outlook 2007 allows users to cache portions of delegate mailboxes locally (for example, contacts or a calendar). This policy will not affect portions of a delegate mailbox that are cached locally. To have this policy affect all parts of a delegate mailbox, ensure that for Microsoft Outlook 2007 no portions of the delegate mailbox are cached locally. The default behavior for Search is to not index online delegate mailboxes. Disabling this policy will block any indexing of online delegate mailboxes. Online delegate mailboxes are managed separately from online mailboxes. The "Enable Indexing of Uncached Exchange Folders" policy has no effect on online delegate mailboxes. To stop indexing of online mailboxes and online delegate mailboxes you must disable both policies.
- Enable throttling for online mail indexing
- When using Microsoft Office Outlook in online mode, you can enable this policy to control how fast online mail is indexed on a Microsoft Exchange server. The lower you set this policy, the lower the burden will be on the corresponding Microsoft Exchange server. The default value for this policy is 120 items per minute. To lower the burden on Microsoft Exchange servers, lower the rate of items indexed per minute. If you disable this policy, then online mail items will be indexed at the speed that the Microsoft Exchange server can support. If you set this policy to not configured, then online mail items will be indexed at the speed of 120 items per minute. This policy has no effect on mail items when using Microsoft Office Outlook in cached mode.
- Number of items per minute
- Prevent indexing Microsoft Office Outlook
- Enable this policy to prevent indexing of any Microsoft Outlook items. The default is to automatically index Outlook items. If this policy is enabled then the user's Outlook items will not be added to the index and the user will not see them in search results.
- Prevent indexing e-mail attachments
- Enable this policy setting to prevent the indexing of the content of e-mail attachments. If enabled, indexing service components (including non-Microsoft components) are expected not to index e-mail attachments. Consider enabling this policy if you are concerned about the security or indexing performance of non-Microsoft document filters (iFilters). This policy is disabled by default.
- Prevent indexing public folders
- Enable this policy to prevent indexing public folders in Microsoft Office Outlook. When this policy is disabled or not configured, the user has the option to index cached public folders in Outlook. Public folders are only indexed when using Outlook 2003 or later. The user must be running in cached mode and the Download Public Folder Favorites option must be turned on.
- Prevent indexing certain paths
- If you enable this policy setting, you specify a list of paths to exclude from indexing. The user cannot enter any path that starts with one of the paths you specified.
-
-If you enable and then disable this policy setting, users can index any path not restricted by other policies, but their original list of paths to index is not restored.
-
- If you enable this policy setting, you specify a list of paths to exclude from indexing. The user cannot enter any path that starts with one of the paths you specified. On a per-user basis, this policy setting will work only if a protocol handler referencing a SID-based user scope, such as MAPI, is specified. File system paths that do not reference a specific SID will not be excluded from indexing if these are only specified in the Group Policy under "User Configuration." To restrict a file system path from indexing, please specify the file system path to be indexed under the "Computer Configuration" Group Policy.
-
-If you enable and then disable this policy setting, users can index any path not restricted by other policies, but their original list of paths to index is not restored.
-
- Default indexed paths
- Enabling this policy allows you to specify a list of paths to index by default. The user may override these paths and exclude them from indexing.
- Enabling this policy allows you to specify a list of paths to index by default. The user may override these paths and exclude them from indexing. On a per-user basis, this policy setting will work only if a protocol handler referencing a SID-based user scope, such as MAPI, is specified. File system paths that do not reference a specific SID will not be included for indexing if these are only specified in the Group Policy under "User Configuration." To include a file system path for indexing, please specify the file system path to be indexed under the "Computer Configuration" Group Policy.
- Default excluded paths
- Enabling this policy allows you to specify a list of paths to exclude from indexing by default. The user may override these paths and include them in indexing.
- Enabling this policy allows you to specify a list of paths to exclude from indexing by default. The user may override these paths and include them in indexing. On a per-user basis, this policy setting will work only if a protocol handler referencing a SID-based user scope, such as MAPI, is specified. File system paths that do not reference a specific SID will not be excluded from indexing if these are only specified in the Group Policy under "User Configuration." To restrict a file system path from indexing, please specify the file system path to be indexed under the "Computer Configuration" Group Policy.
- Indexer data location
- Store indexer database in this directory. This directory must be located on a local fixed drive.
- Path (under 128 characters):
- Add primary intranet search location
- Enabling this policy allows you to add a primary intranet search location within Windows Desktop Search. The value of this text should be:
-
-name,url
-
-For example:
-
-Intranet,http://intranetsearch.aspx?k=$w
-
-You must provide the following:
-1) A name for the scope, such as 'Intranet'.
-2) The URL to the search service. Use $w in place of the query term for the search service URL.
-
-If your intranet search service is SharePoint Portal Server, your query should resemble the following:
-http://sitename/Search.aspx?k=$w
-
-If your intranet search service is Windows SharePoint Services (WSS), the query should resemble the following, where XXXX is the locale ID of your WSS Service. For example, the English locale ID is 1033.
-http://sitename/_layouts/XXXX/searchresults.aspx?SearchString=$w
-
-This adds intranet search location to:
-1) The Windows Deskbar
-2) The Desktop Search results search box
-3) The WDS search box in Search Companion
-
- Intranet Search Scope Url
- Add secondary intranet search locations
- Enabling this policy allows you to add intranet search locations in addition to the primary intranet search location defined in the Add Primary Intranet Search Location policy. The value of this text should be:
-
-name1,url1;name2,url2;...nameN,urlN
-
-For example:
-
-MySearch,http://mysearch.aspx?q=$w;MySearch2,http://mysearch2?q=$w.
-
-For each search scope, provide:
-1) A name for the scope, such as 'IT Web'.
-2) The URL to the search service. Use $w in place of the query term for the search service URL.
-
-If your intranet search service is SharePoint Portal Server, your query should resemble the following:
-http://sitename/Search.aspx?k=$w
-
-If your intranet search service is Windows SharePoint Services (WSS), the query should resemble the following, where XXXX is the locale ID of your WSS Service. For example, the English locale ID is 1033.
-http://sitename/_layouts/XXXX/searchresults.aspx?SearchString=$w
-
-These additional intranet search locations are added to the All Locations list in the Desktop Search results.
- Intranet Search Scope Url
- Preview pane location
- Enabling this policy allows you to set the location of the preview pane in the Desktop Search results. You can also turn off the preview pane. The four options are:
-
-- Auto
-- Right
-- Bottom
-- Off
-
-You should consider enabling this policy to turn off the preview pane if your environment does not support Office XP or later. The full preview pane functionality is only available for Office documents in Office XP or later.
-
-When this policy is disabled or not configured, the preview pane shows automatically to the right of the Desktop Search results, and your users can choose the location of the preview pane
- Auto
- Right
- Bottom
- Off
- Set large or small icon view in desktop search results
- Enabling this policy allows you to specify whether you want large icon or small icon view for your Desktop Search results. The two options are:
-
-- Large Icon
-- Small Icon.
-
-If you have disabled the preview pane because your organization does not support Office XP or above, you should enforce the large icon view so that users can see snippets related to their desktop search query.
-
-When this policy is disabled or not configured, the default is small icon view.
- Small Icon
- Large Icon
- Do not allow web search
- Enabling this policy removes the option of searching the Web from Windows Desktop Search.
-
-When this policy is disabled or not configured, the Web option is available and users can search the Web via their default browser search engine.
- Stop indexing in the event of limited hard drive space
- Enabling this policy prevents indexing from continuing after less than the specified amount of hard drive space is left on the same drive as the index location. Select between 0 and 2147483647 MB.
-
-Enable this policy if computers in your environment have extremely limited hard drive space.
-
-When this policy is disabled or not configured, Windows Desktop Search automatically manages your index size.
- MB Limit
- Control rich previews for attachments
- Enabling this policy defines a semicolon-delimited list of file extensions which will be allowed to have rich attachment previews.
-
-When this policy is disabled or not configured the default settings will be set to .bmp;.emf;.gif;.jpg;.jpeg;.png;.wmf;.wrn;.txt;.err;.xml;.cpp;.c;.h;.cxx;.hxx;.idl;.cs;.vb;.idl;.xsd;.doc;.docx;.xls;.xlsx;.ppt;.pptx;.vsd;.xlsb;.xltx;.dot;.rtf
- Prevent unwanted iFilters and protocol handlers
- Enabling this policy prevents Windows Desktop Search from using iFilters and protocol handlers unless they are specified in the allow list. However, This policy will not prevent iFilters or protocol handlers from being installed, nor will it prevent them from being used by other applications or services.
-You can also specify an allow list of add-ins by providing the classID or ProgId string. For example, if you plan to deploy a particular iFilter, make sure that this iFilter is on the allow list, either as a GUID such as {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} (include the braces) or a ProgID such as VisFilter.CFilter.1.
-
-If you maintain a locked desktop environment, this setting is redundant because non-administrative users do not have permission to install new components. If your users have Administrator permissions or can install software, this policy prevents them from specifically using Windows Desktop Search-related add-ins.
-
-Note: Because of a limitation in the Group Policy editor, you must add at least one entry in the allow list, even if you want to enable this policy without an allow list. Create a list entry by putting a space in the name field and a space in the value field and then save it. This will create a placeholder entry that is ignored by the program.
- Allow List
- Prevent indexing of certain file types
- Enabling this policy allows you to edit the list of file types to exclude from indexing. The end user cannot modify this list. You should separate each extension type with a semicolon.
-
-Note that limitations of Group Policy Object Editor require this list to be split across multiple values. Desktop Search combines all these into a single exclusion list.
-
-When this policy is disabled or not configured, the user can edit the default list of excluded file types. If you enable and then disable this policy, the user's original list is restored.
-
-If you want to specify an initial default list of excluded file types that users can change later, see the administration guide for information about how to set up the initial machine preference.
- Exclude
- and
- and
- and
- Turn off storage and display of search history
- This policy setting prevents search queries from being stored in the registry. If you enable this policy setting, search suggestions based on previous searches won't appear in the search pane. Search suggestions provided by apps or by Windows based on local content will still appear.
-
-If you disable or do not configure this policy setting, users will get search suggestions based on previous searches in the search pane.
- Allow Cortana
- This policy setting specifies whether Cortana is allowed on the device.
-
-If you enable or don't configure this setting, Cortana will be allowed on the device. If you disable this setting, Cortana will be turned off.
-
-When Cortana is off, users will still be able to use search to find things on the device.
- Allow search highlights
- Disabling this setting turns off search highlights in the start menu search box and in search home. Enabling or not configuring this setting turns on search highlights in the start menu search box and in search home.
- Allow Cortana above lock screen
- This policy setting determines whether or not the user can interact with Cortana using speech while the system is locked.
-
-If you enable or don’t configure this setting, the user can interact with Cortana using speech while the system is locked.
-
-If you disable this setting, the system will need to be unlocked for the user to interact with Cortana using speech.
- Allow search and Cortana to use location
- This policy setting specifies whether search and Cortana can provide location aware search and Cortana results.
-
-If this is enabled, search and Cortana can access location information.
- Allow Cloud Search
- Allow Cortana Page in OOBE on an AAD account
- Allow search and Cortana to search cloud sources like OneDrive and SharePoint
- Allow the cortana opt-in page during windows setup out of the box experience
- Disable Cloud Search
- Disable Cortana Page in AAD
- Enable Cortana Page in AAD
- Enable Cloud Search
- User Selected
- Fully disable Search UI
- If you enable this policy, the Search UI will be disabled along with all its entry points, such as keyboard shortcuts, touchpad gestures, and type-to-search in the Start menu. The Start menu's search box and Search Taskbar button will also be hidden.
-
-If you disable or don't configure this policy setting, the user will be able to open the Search UI and its different entry points will be shown.
- Configures search on the taskbar
- This policy setting allows you to configure search on the taskbar.
-
-If you enable this policy setting and set it to hide, search on taskbar will be hidden by default. Users cannot change it in Settings.
-
-If you enable this policy setting and set it to search icon only, the search icon will be displayed on the taskbar by default. Users cannot change it in Settings.
-
-If you enable this policy setting and set it to search icon and label, the search icon and label will be displayed on the taskbar by default. Users cannot change it in Settings.
-
-If you enable this policy setting and set it to search box, the search box will be displayed on the taskbar by default. Users cannot change it in Settings.
-
-If you disable or do not configure this policy setting, search on taskbar will be configured according to the defaults for your Windows edition. Users will be able to change search on taskbar in Settings.
-
- Hide
- Search icon only
- Search icon and label
- Search box
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Preview Pane Location
-
-
- Set Large or Small Icon View in Desktop Search Results
-
-
- MB Limit
-
-
- Number of items per minute
-
-
- Allow List
-
-
- Prevent Indexing Certain Paths
-
-
- Prevent Indexing Certain Paths
-
-
- Default Indexed Paths
-
-
- Default Indexed Paths
-
-
- Default Excluded Paths
-
-
- Default Excluded Paths
-
-
-
-
- .386;.aps;.bin;.bk1;.bk2;.bkf;.blf;.bsc;.btr;.cat;.cfg;.cgm;.chk;.ci;.crwl;.cur;.dat;.dbg;.dct;.dir;.dl_;.el;.evt;.ex_;.exp;.eyb;.fnt;.fon;.ghi;.gthr;.hqx;.icm;.idb;.idx;.ilk;.imc;.in_;.inl;.inv
-
-
-
- .ipp;.jbf;.lib;.local;.log;.log1;.log2;.m14;.mac;.man;.manifest;.map;.MAPIMail;.mmf;.mui;.muimanifest;.mv;.ncb;.obj;.oc_;.ocx;.onecache;.onetoc;.onetoc2;.ost;.pch;.pdb;.pds;.pf;.pic;.pma;.pmc;.pml
-
-
-
- .pmr;.pst;.res;.rmp;.rpc;.rsp;.sbr;.sc2;.sit;.sr_;.sy_;.sym;.TMCONTAINER00000000000000000001;.tlb;.tlh;.tmf;.tmp;.ttc;.ttf;.ttx;.TMCONTAINER00000000000000000002;.ufm;.vbx;.vxd;.wll;.wlt;.xbm;.xix;.z96;.ZFSendToTarget
-
-
-
-
-
-
-
- Type of information
-
-
- Default Safe Search Setting
-
-
- Cloud Search Setting
-
-
- Cortana in AAD Setting
-
-
- Search on the taskbar
-
-
-
-
diff --git a/policy_templates/en-US/SearchOCR.adml b/policy_templates/en-US/SearchOCR.adml
deleted file mode 100644
index 58f05fe..0000000
--- a/policy_templates/en-US/SearchOCR.adml
+++ /dev/null
@@ -1,132 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow indexing of TIFF documents by performing OCR
- This policy setting allows turning OCR (Optical Character Recognition) processing on or off for TIFF files. If you enable this policy setting, textual content of TIFF files is indexed by performing OCR. If you disable or do not configure this policy setting, only the properties of TIFF files will be indexed.
-
- This policy setting also affects the "How should this file be indexed?" control panel setting, located in Control Panel\Indexing Options\Advanced Options\File Types. If you enable this policy setting, the control panel setting is set to "Index Properties and File Contents". If you disable or do not configure this policy setting, the control panel setting is set to "Index Properties Only".
-
- Select OCR language
- This policy setting allows selection of OCR (Optical Character Recognition) language. If you enable this policy setting, the selected OCR language is used in OCR processing during the indexing of TIFF files. If you disable or do not configure this policy setting, the default system language is used.
-
-Re-indexing is not initiated when you enable this policy and select the OCR language. This policy setting only applies to indexing of new files, unless re-indexing is initiated manually.
-
- Select OCR language from a code page
- This policy setting allows selecting of OCR (Optical Character Recognition) languages that belong to one of the supported code pages. If you enable this policy setting, the selected OCR languages are used in OCR processing during the indexing of TIFF files. The default system language is ignored unless it is among the selected OCR languages. If you disable or do not configure this policy setting, only the default system language is used.
-
-All selected OCR languages must belong to the same code page. If you select languages from more than one code page, the entire OCR language selection is ignored and only the default system language is used.
-
-Re-indexing is not initiated when you enable this policy and selecting OCR languages. This policy setting only applies to the indexing of new files, unless re-indexing is initiated manually.
-
- OCR
- Force TIFF IFilter to perform OCR for every page in a TIFF document
-
- This Group Policy setting lets users turn off the performance optimization so that the TIFF IFilter will perform OCR for every page in a TIFF document, which allows indexing of all recognized text. By default, the TIFF IFilter optimizes its performance by skipping OCR (Optical Character Recognition) for document pages that have non-textual content (for example, pictures). In some cases, pages that contain text can be misclassified as non-text pages. If this is the case, the text in these pages will not be indexed.
-
- If you enable this setting, TIFF IFilter will perform OCR for every page in a TIFF document to index all recognized text. Therefore, the OCR process will be slower. This decrease in performance can be significant if there are lots of non-textual pages (pictures) in TIFF documents on the system.
-
- If you disable or do not configure this setting, TIFF IFilter will optimize its performance by skipping non-textual content during the OCR process.
-
- Arabic
- Bulgarian
- Bosnian (Latin)
- Chinese (Simplified)
- Chinese (Traditional)
- Croatian
- Czech
- Danish
- Dutch
- English
- Finnish
- French
- German
- Greek
- Hungarian
- Italian
- Japanese
- Korean
- Norwegian
- Polish
- Portuguese
- Romanian
- Russian
- Serbian (Cyrillic)
- Serbian (Latin)
- Slovak
- Slovenian
- Spanish
- Swedish
- Turkish
-
-
-
- Choose one of the following OCR languages:
-
-
- Baltic (1257) code page
- Estonian
- Latvian
- Lithuanian
-
- Central European (1250, Latin 2) code page
- Albanian
- Croatian
- Czech
- Hungarian
- Polish
- Romanian
- Serbian Latin
- Slovak
- Slovenian
-
- Cyrillic (1251) code page
- Bulgarian
- Belarusian
- Macedonian (F.Y.R.O. Macedonia)
- Russian
- Serbian
- Ukrainian
-
- Western European (1252, Latin 1) code page
- Catalan
- Danish
- Dutch
- English
- Faroese
- Finnish
- French
- German
- Icelandic
- Indonesian
- Italian
- Malay
- Norwegian
- Portuguese
- Spanish
- Swedish
-
- Greek (1253) code page
- Greek
-
- Turkish (1254) code page
- Turkish
-
- Chinese Simplified (936, GB2312) code page
- Chinese (simplified)
-
- Chinese Traditional (950, Big5) code page
- Chinese (traditional)
-
- Japanese (932, Shift-JIS) code page
- Japanese
-
- Korean (949) code page
- Korean
-
-
-
-
diff --git a/policy_templates/en-US/Securitycenter.adml b/policy_templates/en-US/Securitycenter.adml
deleted file mode 100644
index 573d53c..0000000
--- a/policy_templates/en-US/Securitycenter.adml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Security Center
- Turn on Security Center (Domain PCs only)
- This policy setting specifies whether Security Center is turned on or off for computers that are joined to an Active Directory domain. When Security Center is turned on, it monitors essential security settings and notifies the user when the computer might be at risk. The Security Center Control Panel category view also contains a status section, where the user can get recommendations to help increase the computer's security. When Security Center is not enabled on the domain, neither the notifications nor the Security Center status section are displayed.
-
-Note that Security Center can only be turned off for computers that are joined to a Windows domain. When a computer is not joined to a Windows domain, the policy setting will have no effect.
-
-If you do not congifure this policy setting, the Security Center is turned off for domain members.
-
-If you enable this policy setting, Security Center is turned on for all users.
-
-If you disable this policy setting, Security Center is turned off for domain members.
-
-Windows XP SP2
-----------------------
-In Windows XP SP2, the essential security settings that are monitored by Security Center include firewall, antivirus, and Automatic Updates. Note that Security Center might not be available following a change to this policy setting until after the computer is restarted for Windows XP SP2 computers.
-
-Windows Vista
----------------------
-In Windows Vista, this policy setting monitors essential security settings to include firewall, antivirus, antispyware, Internet security settings, User Account Control, and Automatic Updates. Windows Vista computers do not require a reboot for this policy setting to take effect.
-
-
-
-
diff --git a/policy_templates/en-US/Sensors.adml b/policy_templates/en-US/Sensors.adml
deleted file mode 100644
index 2468267..0000000
--- a/policy_templates/en-US/Sensors.adml
+++ /dev/null
@@ -1,104 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off sensors
-
- This policy setting turns off the sensor feature for this computer.
-
- If you enable this policy setting, the sensor feature is turned off, and all programs on this computer cannot use the sensor feature.
-
- If you disable or do not configure this policy setting, all programs on this computer can use the sensor feature.
-
- Turn off location
-
- This policy setting turns off the location feature for this computer.
-
- If you enable this policy setting, the location feature is turned off, and all programs on this computer are prevented from using location information from the location feature.
-
- If you disable or do not configure this policy setting, all programs on this computer will not be prevented from using location information from the location feature.
-
- Turn off location scripting
-
- This policy setting turns off scripting for the location feature.
-
- If you enable this policy setting, scripts for the location feature will not run.
-
- If you disable or do not configure this policy setting, all location scripts will run.
-
- Location and Sensors
- Human Presence
- Force Instant Wake
- Determines whether Wake On Arrival is forced on/off by the MDM policy. The user will not be able to change this setting and the toggle in the UI will be greyed out.
- Defaults to user choice
- Forced On
- Forced Off
- Force Instant Lock
- Determines whether Lock on Leave is forced on/off by the MDM policy. The user will not be able to change this setting and the toggle in the UI will be greyed out.
- Defaults to user choice
- Forced On
- Forced Off
- Lock Timeout
- Determines the timeout for Lock on Leave forced by the MDM policy. The user will be unable to change this setting and the toggle in the UI will be greyed out.
- Defaults to user choice
- 10 seconds
- 30 seconds
- 2 minutes
- Immediate
- Force Instant Dim
- Determines whether Attention Based Display Dimming is forced on/off by the MDM policy. The user will not be able to change this setting and the toggle in the UI will be greyed out.
- Defaults to user choice
- Forced On
- Forced Off
- Force Disable Wake When Battery Saver On
- Determines whether Disable Wake on Approach When Battery Saver On checkbox is forced checked/unchecked by the MDM policy. The user will not be able to change this setting and the checkbox in the UI will be greyed out.
- Defaults to user choice
- Forced Checked
- Forced Unchecked
- Force Allow Wake When External Display Connected
- Determines whether Allow Wake on Approach When External Display Connected checkbox is forced checked/unchecked by the MDM policy. The user will not be able to change this setting and the checkbox in the UI will be greyed out.
- Defaults to user choice
- Forced Checked
- Forced Unchecked
- Force Allow Lock When External Display Connected
- Determines whether Allow Lock on Leave When Battery Saver On checkbox is forced checked/unchecked by the MDM policy. The user will not be able to change this setting and the checkbox in the UI will be greyed out.
- Defaults to user choice
- Forced Checked
- Forced Unchecked
- Force Allow Dim When External Display Connected
- Determines whether Allow Adaptive Dimming When Battery Saver On checkbox is forced checked/unchecked by the MDM policy. The user will not be able to change this setting and the checkbox in the UI will be greyed out.
- Defaults to user choice
- Forced Checked
- Forced Unchecked
-
-
-
- Choose one of the following actions
-
-
- Choose one of the following actions
-
-
- Choose one of the following timeouts
-
-
- Choose one of the following actions
-
-
- Choose one of the following actions
-
-
- Choose one of the following actions
-
-
- Choose one of the following actions
-
-
- Choose one of the following actions
-
-
-
-
diff --git a/policy_templates/en-US/ServerManager.adml b/policy_templates/en-US/ServerManager.adml
deleted file mode 100644
index ec09963..0000000
--- a/policy_templates/en-US/ServerManager.adml
+++ /dev/null
@@ -1,54 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Windows Server 2008 and Windows Server 2008 R2 operating systems only
- Do not display Server Manager automatically at logon
- This policy setting allows you to turn off the automatic display of Server Manager at logon.
-
-If you enable this policy setting, Server Manager is not displayed automatically when a user logs on to the server.
-
-If you disable this policy setting, Server Manager is displayed automatically when a user logs on to the server.
-
-If you do not configure this policy setting, Server Manager is displayed when a user logs on to the server. However, if the "Do not show me this console at logon" (Windows Server 2008 and Windows Server 2008 R2) or “Do not start Server Manager automatically at logon” (Windows Server 2012) option is selected, the console is not displayed automatically at logon.
-
-Note: Regardless of the status of this policy setting, Server Manager is available from the Start menu or the Windows taskbar.
-
- Configure the refresh interval for Server Manager
- This policy setting allows you to set the refresh interval for Server Manager. Each refresh provides Server Manager with updated information about which roles and features are installed on servers that you are managing by using Server Manager. Server Manager also monitors the status of roles and features installed on managed servers.
-
-If you enable this policy setting, Server Manager uses the refresh interval specified in the policy setting instead of the “Configure Refresh Interval” setting (in Windows Server 2008 and Windows Server 2008 R2), or the “Refresh the data shown in Server Manager every [x] [minutes/hours/days]” setting (in Windows Server 2012) that is configured in the Server Manager console.
-
-If you disable this policy setting, Server Manager does not refresh automatically. If you do not configure this policy setting, Server Manager uses the refresh interval settings that are specified in the Server Manager console.
-
-Note: The default refresh interval for Server Manager is two minutes in Windows Server 2008 and Windows Server 2008 R2, or 10 minutes in Windows Server 2012.
-
- Do not display Manage Your Server page at logon
- This policy setting allows you to turn off the automatic display of the Manage Your Server page.
-
-If you enable this policy setting, the Manage Your Server page is not displayed each time an administrator logs on to the server.
-
-If you disable or do not configure this policy setting, the Manage Your Server page is displayed each time an administrator logs on to the server. However, if the administrator has selected the "Don’t display this page at logon" option at the bottom of the Manage Your Server page, the page is not displayed.
-
- Do not display Initial Configuration Tasks window automatically at logon
- This policy setting allows you to turn off the automatic display of the Initial Configuration Tasks window at logon on Windows Server 2008 and Windows Server 2008 R2.
-
-If you enable this policy setting, the Initial Configuration Tasks window is not displayed when an administrator logs on to the server.
-
-If you disable this policy setting, the Initial Configuration Tasks window is displayed when an administrator logs on to the server.
-
-If you do not configure this policy setting, the Initial Configuration Tasks window is displayed when an administrator logs on to the server. However, if an administrator selects the "Do not show this window at logon" option, the window is not displayed on subsequent logons.
-
- Server Manager
-
-
-
- Minutes:
- Range is 1 to 34560
-
-
-
-
diff --git a/policy_templates/en-US/ServiceControlManager.adml b/policy_templates/en-US/ServiceControlManager.adml
deleted file mode 100644
index ab6a0e6..0000000
--- a/policy_templates/en-US/ServiceControlManager.adml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Service Control Manager Settings
- Security Settings
- Enable svchost.exe mitigation options
- This policy setting enables process mitigation options on svchost.exe processes.
-
-If you enable this policy setting, built-in system services hosted in svchost.exe processes will have stricter security policies enabled on them.
-
-This includes a policy requiring all binaries loaded in these processes to be signed by microsoft, as well as a policy disallowing dynamically-generated code.
-
-If you disable or do not configure this policy setting, these stricter security settings will not be applied.
-
-
-
diff --git a/policy_templates/en-US/Servicing.adml b/policy_templates/en-US/Servicing.adml
deleted file mode 100644
index 23f95c0..0000000
--- a/policy_templates/en-US/Servicing.adml
+++ /dev/null
@@ -1,29 +0,0 @@
-
-
-
- Windows Servicing Policies
- Windows Servicing Policies
-
-
- Specify settings for optional component installation and component repair
-
-This policy setting specifies the network locations that will be used for the repair of operating system corruption and for enabling optional features that have had their payload files removed.
-
-If you enable this policy setting and specify the new location, the files in that location will be used to repair operating system corruption and for enabling optional features that have had their payload files removed. You must enter the fully qualified path to the new location in the ""Alternate source file path"" text box. Multiple locations can be specified when each path is separated by a semicolon.
-
-The network location can be either a folder, or a WIM file. If it is a WIM file, the location should be specified by prefixing the path with “wim:” and include the index of the image to use in the WIM file. For example “wim:\\server\share\install.wim:3”.
-
-If you disable or do not configure this policy setting, or if the required files cannot be found at the locations specified in this policy setting, the files will be downloaded from Windows Update, if that is allowed by the policy settings for the computer.
-
-
-
-
-
-
-
- Never attempt to download payload from Windows Update
- Download repair content and optional features directly from Windows Update instead of Windows Server Update Services (WSUS)
-
-
-
-
diff --git a/policy_templates/en-US/SettingSync.adml b/policy_templates/en-US/SettingSync.adml
deleted file mode 100644
index 391647b..0000000
--- a/policy_templates/en-US/SettingSync.adml
+++ /dev/null
@@ -1,200 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
-
- Sync your settings
-
-
- Do not sync
- Prevent syncing to and from this PC. This turns off and disables the "sync your settings" switch on the "sync your settings" page in PC Settings.
-
-If you enable this policy setting, "sync your settings" will be turned off, and none of the "sync your setting" groups will be synced on this PC.
-
-Use the option "Allow users to turn syncing on" so that syncing it turned off by default but not disabled.
-
-If you do not set or disable this setting, "sync your settings" is on by default and configurable by the user.
-
-
- Do not sync app settings
- Prevent the "app settings" group from syncing to and from this PC. This turns off and disables the "app settings" group on the "sync your settings" page in PC settings.
-
-If you enable this policy setting, the "app settings" group will not be synced.
-
-Use the option "Allow users to turn app settings syncing on" so that syncing it turned off by default but not disabled.
-
-If you do not set or disable this setting, syncing of the "app settings" group is on by default and configurable by the user.
-
-
- Do not sync passwords
- Prevent the "passwords" group from syncing to and from this PC. This turns off and disables the "passwords" group on the "sync your settings" page in PC settings.
-
-If you enable this policy setting, the "passwords" group will not be synced.
-
-Use the option "Allow users to turn passwords syncing on" so that syncing it turned off by default but not disabled.
-
-If you do not set or disable this setting, syncing of the "passwords" group is on by default and configurable by the user.
-
-
- Do not sync personalize
- Prevent the "personalize" group from syncing to and from this PC. This turns off and disables the "personalize" group on the "sync your settings" page in PC settings.
-
-If you enable this policy setting, the "personalize" group will not be synced.
-
-Use the option "Allow users to turn personalize syncing on" so that syncing it turned off by default but not disabled.
-
-If you do not set or disable this setting, syncing of the "personalize" group is on by default and configurable by the user.
-
-
- Do not sync Apps
-
- Prevent the "AppSync" group from syncing to and from this PC. This turns off and disables the "AppSync" group on the "sync your settings" page in PC settings.
-
-If you enable this policy setting, the "AppSync" group will not be synced.
-
-Use the option "Allow users to turn app syncing on" so that syncing it turned off by default but not disabled.
-
-If you do not set or disable this setting, syncing of the "AppSync" group is on by default and configurable by the user.
-
-
-
- Do not sync other Windows settings
- Prevent the "Other Windows settings" group from syncing to and from this PC. This turns off and disables the "Other Windows settings" group on the "sync your settings" page in PC settings.
-
-If you enable this policy setting, the "Other Windows settings" group will not be synced.
-
-Use the option "Allow users to turn other Windows settings syncing on" so that syncing it turned off by default but not disabled.
-
-If you do not set or disable this setting, syncing of the "Other Windows settings" group is on by default and configurable by the user.
-
-
- Do not sync desktop personalization
- Prevent the "desktop personalization" group from syncing to and from this PC. This turns off and disables the "desktop personalization" group on the "sync your settings" page in PC settings.
-
-If you enable this policy setting, the "desktop personalization" group will not be synced.
-
-Use the option "Allow users to turn desktop personalization syncing on" so that syncing it turned off by default but not disabled.
-
-If you do not set or disable this setting, syncing of the "desktop personalization" group is on by default and configurable by the user.
-
-
-
- Do not sync browser settings
- Prevent the "browser" group from syncing to and from this PC. This turns off and disables the "browser" group on the "sync your settings" page in PC settings. The "browser" group contains settings and info like history and favorites.
-
-If you enable this policy setting, the "browser" group, including info like history and favorites, will not be synced.
-
-Use the option "Allow users to turn browser syncing on" so that syncing is turned off by default but not disabled.
-
-If you do not set or disable this setting, syncing of the "browser" group is on by default and configurable by the user.
-
-
-
- Do not sync on metered connections
- Prevent syncing to and from this PC when on metered Internet connections. This turns off and disables "sync your settings on metered connections" switch on the "sync your settings" page in PC Settings.
-
-If you enable this policy setting, syncing on metered connections will be turned off, and no syncing will take place when this PC is on a metered connection.
-
-If you do not set or disable this setting, syncing on metered connections is configurable by the user.
-
-
-
- Do not sync start settings
-
- Prevent the "Start layout" group from syncing to and from this PC. This turns off and disables the "Start layout" group on the "sync your settings" page in PC settings.
-
- If you enable this policy setting, the "Start layout" group will not be synced.
-
- Use the option "Allow users to turn start syncing on" so that syncing is turned off by default but not disabled.
-
- If you do not set or disable this setting, syncing of the "Start layout" group is on by default and configurable by the user.
-
-
-
- Do not sync accessibility settings
-
- Prevent the "accessibility" group from syncing to and from this PC. This turns off and disables the "accessibility" group on the "Windows backup" settings page in PC settings.
-
-If you enable this policy setting, the "accessibility", group will not be synced.
-
-Use the option "Allow users to turn accessibility syncing on" so that syncing is turned off by default but not disabled.
-
-If you do not set or disable this setting, syncing of the "accessibility" group is on by default and configurable by the user.
-
-
-
- Do not sync language preferences settings
-
- Prevent the "language preferences" group from syncing to and from this PC. This turns off and disables the "languages preferences" group on the "Windows backup" settings page in PC settings.
-
-If you enable this policy setting, the "language preferences", group will not be synced.
-
-Use the option "Allow users to turn language preferences syncing on" so that syncing is turned off by default but not disabled.
-
-If you do not set or disable this setting, syncing of the "language preferences" group is on by default and configurable by the user.
-
-
-
-
-
-
-
- Allow users to turn syncing on.
-
-
-
-
- Allow users to turn "app settings" syncing on.
-
-
-
-
- Allow users to turn "passwords" syncing on.
-
-
-
-
- Allow users to turn "personalize" syncing on.
-
-
-
-
- Allow users to turn "AppSync" syncing on.
-
-
-
-
- Allow users to turn "other Windows settings" syncing on.
-
-
-
-
- Allow users to turn "desktop personalization" syncing on.
-
-
-
-
- Allow users to turn "browser" syncing on.
-
-
-
-
- Allow users to turn "start layout" syncing on.
-
-
-
-
- Allow users to turn "acessibility" syncing on.
-
-
-
-
- Allow users to turn "language preferences" syncing on.
-
-
-
-
-
diff --git a/policy_templates/en-US/Setup.adml b/policy_templates/en-US/Setup.adml
deleted file mode 100644
index fc7d8f3..0000000
--- a/policy_templates/en-US/Setup.adml
+++ /dev/null
@@ -1,38 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Specify Windows Service Pack installation file location
- Specifies an alternate location for Windows Service Pack installation files.
-
-If you enable this policy setting, enter the fully qualified path to the new location in the "Windows Service Pack Setup file path" box.
-
-If you disable or do not configure this policy setting, the Windows Service Pack Setup source path will be the location used during the last time Windows Service Pack Setup was run on the system.
-
-
- Specify Windows installation file location
- Specifies an alternate location for Windows installation files.
-
-If you enable this policy setting, enter the fully qualified path to the new location in the "Windows Setup file path" box.
-
-If you disable or do not configure this policy setting, the Windows Setup source path will be the location used during the last time Windows Setup was run on the system.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/SharedFolders.adml b/policy_templates/en-US/SharedFolders.adml
deleted file mode 100644
index c021801..0000000
--- a/policy_templates/en-US/SharedFolders.adml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow DFS roots to be published
- This policy setting determines whether the user can publish DFS roots in Active Directory Domain Services (AD DS).
-
-If you enable or do not configure this policy setting, users can use the "Publish in Active Directory" option to publish DFS roots as shared folders in AD DS .
-
-If you disable this policy setting, users cannot publish DFS roots in AD DS and the "Publish in Active Directory" option is disabled. Note: The default is to allow shared folders to be published when this setting is not configured.
- Allow shared folders to be published
- This policy setting determines whether the user can publish shared folders in Active Directory Domain Services (AD DS).
-
-If you enable or do not configure this policy setting, users can use the "Publish in Active Directory" option in the Shared Folders snap-in to publish shared folders in AD DS.
-
-If you disable this policy setting, users cannot publish shared folders in AD DS, and the "Publish in Active Directory" option is disabled. Note: The default is to allow shared folders to be published when this setting is not configured.
-
-
-
diff --git a/policy_templates/en-US/Sharing.adml b/policy_templates/en-US/Sharing.adml
deleted file mode 100644
index d12b79d..0000000
--- a/policy_templates/en-US/Sharing.adml
+++ /dev/null
@@ -1,30 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Prevent users from sharing files within their profile.
- This policy setting specifies whether users can share files within their profile. By default users are allowed to share files within their profile to other users on their network after an administrator opts in the computer. An administrator can opt in the computer by using the sharing wizard to share a file within their profile.
-
-If you enable this policy setting, users cannot share files within their profile using the sharing wizard. Also, the sharing wizard cannot create a share at %root%\users and can only be used to create SMB shares on folders.
-
-If you disable or don't configure this policy setting, users can share files out of their user profile after an administrator has opted in the computer.
- Network Sharing
- Contains settings to control the behavior of File and Folder Sharing.
- Prevent the computer from joining a homegroup
- This policy setting specifies whether users can add computers to a homegroup. By default, users can add their computer to a homegroup on a private network.
-
-If you enable this policy setting, users cannot add computers to a homegroup. This policy setting does not affect other network sharing features.
-
-If you disable or do not configure this policy setting, users can add computers to a homegroup. However, data on a domain-joined computer is not shared with the homegroup.
-
-This policy setting is not configured by default.
-
-You must restart the computer for this policy setting to take effect.
- HomeGroup
- Contains settings to control the behavior of the HomeGroup.
-
-
-
diff --git a/policy_templates/en-US/Shell-CommandPrompt-RegEditTools.adml b/policy_templates/en-US/Shell-CommandPrompt-RegEditTools.adml
deleted file mode 100644
index 3202e8d..0000000
--- a/policy_templates/en-US/Shell-CommandPrompt-RegEditTools.adml
+++ /dev/null
@@ -1,67 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Prevent access to the command prompt
- This policy setting prevents users from running the interactive command prompt, Cmd.exe. This policy setting also determines whether batch files (.cmd and .bat) can run on the computer.
-
-If you enable this policy setting and the user tries to open a command window, the system displays a message explaining that a setting prevents the action.
-
-If you disable this policy setting or do not configure it, users can run Cmd.exe and batch files normally.
-
-Note: Do not prevent the computer from running batch files if the computer uses logon, logoff, startup, or shutdown batch file scripts, or for users that use Remote Desktop Services.
- No
- Yes
- Prevent access to registry editing tools
- Disables the Windows registry editor Regedit.exe.
-
-If you enable this policy setting and the user tries to start Regedit.exe, a message appears explaining that a policy setting prevents the action.
-
-If you disable this policy setting or do not configure it, users can run Regedit.exe normally.
-
-To prevent users from using other administrative tools, use the "Run only specified Windows applications" policy setting.
- Yes
- No
-
- Run only specified Windows applications
- Limits the Windows programs that users have permission to run on the computer.
-
-If you enable this policy setting, users can only run programs that you add to the list of allowed applications.
-
-If you disable this policy setting or do not configure it, users can run all applications.
-
-This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting programs in the command window even though they would be prevented from doing so using File Explorer.
-
-Note: Non-Microsoft applications with Windows 2000 or later certification are required to comply with this policy setting.
-Note: To create a list of allowed applications, click Show. In the Show Contents dialog box, in the Value column, type the application executable name (e.g., Winword.exe, Poledit.exe, Powerpnt.exe).
- Don't run specified Windows applications
- Prevents Windows from running the programs you specify in this policy setting.
-
-If you enable this policy setting, users cannot run programs that you add to the list of disallowed applications.
-
-If you disable this policy setting or do not configure it, users can run any programs.
-
-This policy setting only prevents users from running programs that are started by the File Explorer process. It does not prevent users from running programs, such as Task Manager, which are started by the system process or by other processes. Also, if users have access to the command prompt (Cmd.exe), this policy setting does not prevent them from starting programs in the command window even though they would be prevented from doing so using File Explorer.
-
-Note: Non-Microsoft applications with Windows 2000 or later certification are required to comply with this policy setting.
-Note: To create a list of allowed applications, click Show. In the Show Contents dialog box, in the Value column, type the application executable name (e.g., Winword.exe, Poledit.exe, Powerpnt.exe).
-
-
-
- Disable the command prompt script processing also?
-
-
- Disable regedit from running silently?
-
-
- List of allowed applications
-
-
- List of disallowed applications
-
-
-
-
diff --git a/policy_templates/en-US/ShellWelcomeCenter.adml b/policy_templates/en-US/ShellWelcomeCenter.adml
deleted file mode 100644
index 1a42b9b..0000000
--- a/policy_templates/en-US/ShellWelcomeCenter.adml
+++ /dev/null
@@ -1,16 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Do not display the Welcome Center at user logon
- This policy setting prevents the display of the Welcome Center at user logon.
-
-If you enable this policy setting, the Welcome Center is not displayed at user logon. The user can access the Welcome Center using the Control Panel or Start menu.
-
-If you disable or do not configure this policy setting, the Welcome Center is displayed at user logon.
-
-
-
diff --git a/policy_templates/en-US/Sidebar.adml b/policy_templates/en-US/Sidebar.adml
deleted file mode 100644
index 34ceba0..0000000
--- a/policy_templates/en-US/Sidebar.adml
+++ /dev/null
@@ -1,33 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Desktop Gadgets
- Turn off desktop gadgets
- This policy setting allows you to turn off desktop gadgets. Gadgets are small applets that display information or utilities on the desktop.
-
-If you enable this setting, desktop gadgets will be turned off.
-
-If you disable or do not configure this setting, desktop gadgets will be turned on.
-
-The default is for desktop gadgets to be turned on.
- Restrict unpacking and installation of gadgets that are not digitally signed.
- This policy setting allows you to restrict the installation of unsigned gadgets. Desktop gadgets can be deployed as compressed files, either digitally signed or unsigned.
-If you enable this setting, gadgets that have not been digitally signed will not be extracted.
-
-If you disable or do not configure this setting, both signed and unsigned gadgets will be extracted.
-The default is for Windows to extract both signed and unsigned gadgets.
- Turn Off user-installed desktop gadgets
- This policy setting allows you to turn off desktop gadgets that have been installed by the user.
-
-If you enable this setting, Windows will not run any user-installed gadgets.
-
-If you disable or do not configure this setting, Windows will run user-installed gadgets.
-
-The default is for Windows to run user installed gadgets.
-
-
-
diff --git a/policy_templates/en-US/SkyDrive.adml b/policy_templates/en-US/SkyDrive.adml
deleted file mode 100644
index 9cf0b86..0000000
--- a/policy_templates/en-US/SkyDrive.adml
+++ /dev/null
@@ -1,62 +0,0 @@
-
-
- Prevent OneDrive file sync
- Prevent files from being automatically synced to OneDrive
-
-
-
- OneDrive
-
-
- Prevent the usage of OneDrive for file storage
- This policy setting lets you prevent apps and features from working with files on OneDrive.
-If you enable this policy setting:
-
-* Users can’t access OneDrive from the OneDrive app and file picker.
-* Windows Store apps can’t access OneDrive using the WinRT API.
-* OneDrive doesn’t appear in the navigation pane in File Explorer.
-* OneDrive files aren’t kept in sync with the cloud.
-* Users can’t automatically upload photos and videos from the camera roll folder.
-
-If you disable or do not configure this policy setting, apps and features can work with OneDrive file storage.
-
-
- Prevent OneDrive from generating network traffic until the user signs in to OneDrive
- Enable this setting to prevent the OneDrive sync client (OneDrive.exe) from generating network traffic (checking for updates, etc.) until the user signs in to OneDrive or starts syncing files to the local computer.
-
-If you enable this setting, users must sign in to the OneDrive sync client on the local computer, or select to sync OneDrive or SharePoint files on the computer, for the sync client to start automatically.
-
-If this setting is not enabled, the OneDrive sync client will start automatically when users sign in to Windows.
-
-If you enable or disable this setting, do not return the setting to Not Configured. Doing so will not change the configuration and the last configured setting will remain in effect.
-
-
- Prevent the usage of OneDrive for file storage on Windows 8.1
- This policy setting lets you prevent apps and features from working with files on OneDrive for Windows 8.1.
-If you enable this policy setting:
-
-* Users can’t access OneDrive from the OneDrive app and file picker.
-* Windows Store apps can’t access OneDrive using the WinRT API.
-* OneDrive doesn’t appear in the navigation pane in File Explorer.
-* OneDrive files aren’t kept in sync with the cloud.
-* Users can’t automatically upload photos and videos from the camera roll folder.
-
-If you disable or do not configure this policy setting, apps and features can work with OneDrive file storage.
-
-
- Prevent OneDrive files from syncing over metered connections
- This policy setting allows configuration of OneDrive file sync behavior on metered connections.
- Block syncing on all metered connections
- Block syncing on metered connections only when roaming
-
-
- Save documents to OneDrive by default
- This policy setting lets you disable OneDrive as the default save location. It does not prevent apps and users from saving files on OneDrive. If you disable this policy setting, files will be saved locally by default. Users will still be able to change the value of this setting to save to OneDrive by default. They will also be able to open and save files on OneDrive using the OneDrive app and file picker, and Windows Store apps will still be able to access OneDrive using the WinRT API. If you enable or do not configure this policy setting, users with a connected account will save documents to OneDrive by default.
-
-
-
- Metered Network Setting
-
-
-
-
diff --git a/policy_templates/en-US/SmartScreen.adml b/policy_templates/en-US/SmartScreen.adml
deleted file mode 100644
index 871e923..0000000
--- a/policy_templates/en-US/SmartScreen.adml
+++ /dev/null
@@ -1,78 +0,0 @@
-
-
-
- Windows Defender SmartScreen
- Configuration for Windows Defender SmartScreen
-
-
-
- Windows Defender SmartScreen
- Explorer
- Microsoft Edge
-
- Configure Windows Defender SmartScreen
- Warn and prevent bypass
- Warn
-
- Turn off app recommendations
- Allow apps from Store only
- Show me app recommendations
- Warn me before installing apps from outside the Store
-
- This policy allows you to turn Windows Defender SmartScreen on or off. SmartScreen helps protect PCs by warning users before running potentially malicious programs downloaded from the Internet. This warning is presented as an interstitial dialog shown before running an app that has been downloaded from the Internet and is unrecognized or known to be malicious. No dialog is shown for apps that do not appear to be suspicious.
-
-Some information is sent to Microsoft about files and programs run on PCs with this feature enabled.
-
-If you enable this policy, SmartScreen will be turned on for all users. Its behavior can be controlled by the following options:
-
-• Warn and prevent bypass
-• Warn
-
-If you enable this policy with the "Warn and prevent bypass" option, SmartScreen's dialogs will not present the user with the option to disregard the warning and run the app. SmartScreen will continue to show the warning on subsequent attempts to run the app.
-
-If you enable this policy with the "Warn" option, SmartScreen's dialogs will warn the user that the app appears suspicious, but will permit the user to disregard the warning and run the app anyway. SmartScreen will not warn the user again for that app if the user tells SmartScreen to run the app.
-
-If you disable this policy, SmartScreen will be turned off for all users. Users will not be warned if they try to run suspicious apps from the Internet.
-
-If you do not configure this policy, SmartScreen will be enabled by default, but users may change their settings.
- Configure App Install Control
- App Install Control is a feature of Windows Defender SmartScreen that helps protect PCs by allowing users to install apps only from the Store. SmartScreen must be enabled for this feature to work properly.
-
-If you enable this setting, you must choose from the following behaviors:
-
- - Turn off app recommendations
-
- - Show me app recommendations
-
- - Warn me before installing apps from outside the Store
-
- - Allow apps from Store only
-
-If you disable or don't configure this setting, users will be able to install apps from anywhere, including files downloaded from the Internet.
-
- Configure Windows Defender SmartScreen
- This policy setting lets you configure whether to turn on Windows Defender SmartScreen. Windows Defender SmartScreen provides warning messages to help protect your employees from potential phishing scams and malicious software. By default, Windows Defender SmartScreen is turned on.
-
-If you enable this setting, Windows Defender SmartScreen is turned on and employees can't turn it off.
-
-If you disable this setting, Windows Defender SmartScreen is turned off and employees can't turn it on.
-
-If you don't configure this setting, employees can choose whether to use Windows Defender SmartScreen.
- Prevent bypassing Windows Defender SmartScreen prompts for sites
- This policy setting lets you decide whether employees can override the Windows Defender SmartScreen warnings about potentially malicious websites.
-
-If you enable this setting, employees can't ignore Windows Defender SmartScreen warnings and they are blocked from continuing to the site.
-
-If you disable or don't configure this setting, employees can ignore Windows Defender SmartScreen warnings and continue to the site.
-
-
-
-
- Pick one of the following settings:
-
-
- Pick one of the following settings:
-
-
-
-
diff --git a/policy_templates/en-US/Smartcard.adml b/policy_templates/en-US/Smartcard.adml
deleted file mode 100644
index e3757f4..0000000
--- a/policy_templates/en-US/Smartcard.adml
+++ /dev/null
@@ -1,144 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow certificates with no extended key usage certificate attribute
- This policy setting lets you allow certificates without an Extended Key Usage (EKU) set to be used for logon.
-
-In versions of Windows prior to Windows Vista, smart card certificates that are used for logon require an enhanced key usage (EKU) extension with a smart card logon object identifier. This policy setting can be used to modify that restriction.
-
-If you enable this policy setting, certificates with the following attributes can also be used to log on with a smart card:
-- Certificates with no EKU
-- Certificates with an All Purpose EKU
-- Certificates with a Client Authentication EKU
-
-If you disable or do not configure this policy setting, only certificates that contain the smart card logon object identifier can be used to log on with a smart card.
- Allow Integrated Unblock screen to be displayed at the time of logon
- This policy setting lets you determine whether the integrated unblock feature will be available in the logon User Interface (UI).
-
-In order to use the integrated unblock feature your smart card must support this feature. Please check with your hardware manufacturer to see if your smart card supports this feature.
-
-If you enable this policy setting, the integrated unblock feature will be available.
-
-If you disable or do not configure this policy setting then the integrated unblock feature will not be available.
- Allow signature keys valid for Logon
- This policy setting lets you allow signature key-based certificates to be enumerated and available for logon.
-
-If you enable this policy setting then any certificates available on the smart card with a signature only key will be listed on the logon screen.
-
-If you disable or do not configure this policy setting, any available smart card signature key-based certificates will not be listed on the logon screen.
- Allow time invalid certificates
- This policy setting permits those certificates to be displayed for logon that are either expired or not yet valid.
-
-Under previous versions of Microsoft Windows, certificates were required to contain a valid time and not be expired. The certificate must still be accepted by the domain controller in order to be used. This setting only controls the displaying of the certificate on the client machine.
-
-If you enable this policy setting certificates will be listed on the logon screen regardless of whether they have an invalid time or their time validity has expired.
-
-If you disable or do not configure this policy setting, certificates which are expired or not yet valid will not be listed on the logon screen.
- Filter duplicate logon certificates
- This policy settings lets you configure if all your valid logon certificates are displayed.
-
-During the certificate renewal period, a user can have multiple valid logon certificates issued from the same certificate template. This can cause confusion as to which certificate to select for logon. The common case for this behavior is when a certificate is renewed and the old one has not yet expired. Two certificates are determined to be the same if they are issued from the same template with the same major version and they are for the same user (determined by their UPN).
-
-If there are two or more of the "same" certificate on a smart card and this policy is enabled then the certificate that is used for logon on Windows 2000, Windows XP, and Windows 2003 Server will be shown, otherwise the the certificate with the expiration time furthest in the future will be shown. Note: This setting will be applied after the following policy: "Allow time invalid certificates"
-
-If you enable or do not configure this policy setting, filtering will take place.
-
-If you disable this policy setting, no filtering will take place.
-
- Turn on certificate propagation from smart card
- This policy setting allows you to manage the certificate propagation that occurs when a smart card is inserted.
-
-If you enable or do not configure this policy setting then certificate propagation will occur when you insert your smart card.
-
-If you disable this policy setting, certificate propagation will not occur and the certificates will not be made available to applications such as Outlook.
- Configure root certificate clean up
- This policy setting allows you to manage the clean up behavior of root certificates. If you enable this policy setting then root certificate cleanup will occur according to the option selected. If you disable or do not configure this setting then root certificate clean up will occur on log off.
- Turn on root certificate propagation from smart card
- This policy setting allows you to manage the root certificate propagation that occurs when a smart card is inserted.
-
-If you enable or do not configure this policy setting then root certificate propagation will occur when you insert your smart card. Note: For this policy setting to work the following policy setting must also be enabled: Turn on certificate propagation from smart card.
-
-If you disable this policy setting then root certificates will not be propagated from the smart card.
- Prevent plaintext PINs from being returned by Credential Manager
- This policy setting prevents plaintext PINs from being returned by Credential Manager.
-
-If you enable this policy setting, Credential Manager does not return a plaintext PIN.
-
-If you disable or do not configure this policy setting, plaintext PINs can be returned by Credential Manager.
-
-Note: Enabling this policy setting could prevent certain smart cards from working on Windows. Please consult your smart card manufacturer to find out whether you will be affected by this policy setting.
-
- Force the reading of all certificates from the smart card
- This policy setting allows you to manage the reading of all certificates from the smart card for logon.
-
-During logon Windows will by default only read the default certificate from the smart card unless it supports retrieval of all certificates in a single call. This setting forces Windows to read all the certificates from the card. This can introduce a significant performance decrease in certain situations. Please contact your smart card vendor to determine if your smart card and associated CSP supports the required behavior.
-
-If you enable this setting, then Windows will attempt to read all certificates from the smart card regardless of the feature set of the CSP.
-
-If you disable or do not configure this setting, Windows will only attempt to read the default certificate from those cards that do not support retrieval of all certificates in a single call. Certificates other than the default will not be available for logon.
- Display string when smart card is blocked
- This policy setting allows you to manage the displayed message when a smart card is blocked.
-
-If you enable this policy setting, the specified message will be displayed to the user when the smart card is blocked. Note: The following policy setting must be enabled - Allow Integrated Unblock screen to be displayed at the time of logon.
-
-If you disable or do not configure this policy setting, the default message will be displayed to the user when the smart card is blocked, if the integrated unblock feature is enabled.
- Reverse the subject name stored in a certificate when displaying
- This policy setting lets you reverse the subject name from how it is stored in the certificate when displaying it during logon.
-
-By default the user principal name (UPN) is displayed in addition to the common name to help users distinguish one certificate from another. For example, if the certificate subject was CN=User1, OU=Users, DN=example, DN=com and had an UPN of user1@example.com then "User1" will be displayed along with "user1@example.com." If the UPN is not present then the entire subject name will be displayed. This setting controls the appearance of that subject name and might need to be adjusted per organization.
-
-If you enable this policy setting or do not configure this setting, then the subject name will be reversed.
-
-If you disable , the subject name will be displayed as it appears in the certificate.
- No cleanup
- Clean up certificates on smart card removal
- Clean up certificates on log off
- Smart Card
- Allow user name hint
- This policy setting lets you determine whether an optional field will be displayed during logon and elevation that allows a user to enter his or her user name or user name and domain, thereby associating a certificate with that user.
-
-If you enable this policy setting then an optional field that allows a user to enter their user name or user name and domain will be displayed.
-
-If you disable or do not configure this policy setting, an optional field that allows users to enter their user name or user name and domain will not be displayed.
- Turn on Smart Card Plug and Play service
- This policy setting allows you to control whether Smart Card Plug and Play is enabled.
-
-If you enable or do not configure this policy setting, Smart Card Plug and Play will be enabled and the system will attempt to install a Smart Card device driver when a card is inserted in a Smart Card Reader for the first time.
-
-If you disable this policy setting, Smart Card Plug and Play will be disabled and a device driver will not be installed when a card is inserted in a Smart Card Reader.
-
-Note: This policy setting is applied only for smart cards that have passed the Windows Hardware Quality Labs (WHQL) testing process.
- Notify user of successful smart card driver installation
- This policy setting allows you to control whether a confirmation message is displayed when a smart card device driver is installed.
-
-If you enable or do not configure this policy setting, a confirmation message will be displayed when a smart card device driver is installed.
-
-If you disable this policy setting, a confirmation message will not be displayed when a smart card device driver is installed.
-
-Note: This policy setting is applied only for smart cards that have passed the Windows Hardware Quality Labs (WHQL) testing process.
- Allow ECC certificates to be used for logon and authentication
- This policy setting allows you to control whether elliptic curve cryptography (ECC) certificates on a smart card can be used to log on to a domain.
-
-If you enable this policy setting, ECC certificates on a smart card can be used to log on to a domain.
-
-If you disable or do not configure this policy setting, ECC certificates on a smart card cannot be used to log on to a domain.
-
-Note: This policy setting only affects a user's ability to log on to a domain. ECC certificates on a smart card that are used for other applications, such as document signing, are not affected by this policy setting.
-Note: If you use an ECDSA key to log on, you must also have an associated ECDH key to permit logons when you are not connected to the network.
-
-
-
- Root certificate clean up options
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/Snmp.adml b/policy_templates/en-US/Snmp.adml
deleted file mode 100644
index 90a0e95..0000000
--- a/policy_templates/en-US/Snmp.adml
+++ /dev/null
@@ -1,70 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Specify communities
- Specify permitted managers
- This policy setting determines the permitted list of hosts that can submit a query to the Simple Network Management (SNMP) agent running on the client computer.
-
-Simple Network Management Protocol is a protocol designed to give a user the capability to remotely manage a computer network by polling and setting terminal values and monitoring network events.
-
-The manager is located on the host computer on the network. The manager's role is to poll the agents for certain requested information.
-
-If you enable this policy setting, the SNMP agent only accepts requests from the list of permitted managers that you configure using this setting.
-
-If you disable or do not configure this policy setting, SNMP service takes the permitted managers configured on the local computer instead.
-
-Best practice: For security purposes, it is recommended to restrict the HKLM\SOFTWARE\Policies\SNMP\Parameters\PermittedManagers key to allow only the local admin group full control.
-
-Note: This policy setting has no effect if the SNMP agent is not installed on the client computer.
-
-Also, see the other two SNMP policy settings: "Specify trap configuration" and "Specify Community Name".
- SNMP
- This policy setting allows trap configuration for the Simple Network Management Protocol (SNMP) agent.
-
-Simple Network Management Protocol is a protocol designed to give a user the capability to remotely manage a computer network by polling and setting terminal values and monitoring network events.
-
-This policy setting allows you to configure the name of the hosts that receive trap messages for the community sent by the SNMP service. A trap message is an alert or significant event that allows the SNMP agent to notify management systems asynchronously.
-
-If you enable this policy setting, the SNMP service sends trap messages to the hosts within the "public" community.
-
-If you disable or do not configure this policy setting, the SNMP service takes the trap configuration configured on the local computer instead.
-
-Note: This setting has no effect if the SNMP agent is not installed on the client computer.
-
-Also, see the other two SNMP settings: "Specify permitted managers" and "Specify Community Name".
- Specify traps for public community
- This policy setting configures a list of the communities defined to the Simple Network Management Protocol (SNMP) service.
-
-SNMP is a protocol designed to give a user the capability to remotely manage a computer network, by polling and setting terminal values and monitoring network events.
-
-A valid community is a community recognized by the SNMP service, while a community is a group of hosts (servers, workstations, hubs, and routers) that are administered together by SNMP. The SNMP service is a managed network node that receives SNMP packets from the network.
-
-If you enable this policy setting, the SNMP agent only accepts requests from management systems within the communities it recognizes, and only SNMP Read operation is allowed for the community.
-
-If you disable or do not configure this policy setting, the SNMP service takes the Valid Communities configured on the local computer instead.
-
-Best practice: For security purposes, it is recommended to restrict the HKLM\SOFTWARE\Policies\SNMP\Parameters\ValidCommunities key to allow only the local admin group full control.
-
-Note: It is good practice to use a cryptic community name.
-
-Note: This policy setting has no effect if the SNMP agent is not installed on the client computer.
-
-Also, see the other two SNMP settings: "Specify permitted managers" and "Specify trap configuration".
-
-
-
- Communities
-
-
- Permitted managers
-
-
- Trap configuration
-
-
-
-
diff --git a/policy_templates/en-US/SoundRec.adml b/policy_templates/en-US/SoundRec.adml
deleted file mode 100644
index 2a78155..0000000
--- a/policy_templates/en-US/SoundRec.adml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Do not allow Sound Recorder to run
- Specifies whether Sound Recorder can run.
-
-Sound Recorder is a feature of Microsoft Windows Vista that can be used to record sound from an audio input device where the recorded sound is encoded and saved as an audio file.
-
-If you enable this policy setting, Sound Recorder will not run.
-
-If you disable or do not configure this policy setting, Sound Recorder can be run.
- Sound Recorder
-
-
-
diff --git a/policy_templates/en-US/Speech.adml b/policy_templates/en-US/Speech.adml
deleted file mode 100644
index 81e75d0..0000000
--- a/policy_templates/en-US/Speech.adml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- Speech
- Speech platform related policies.
-
-
- Speech
- Allow Automatic Update of Speech Data
- Specifies whether the device will receive updates to the speech recognition and speech synthesis models.
-
-A speech model contains data used by the speech engine to convert audio to text (or vice-versa). The models are periodically updated to improve accuracy and performance. Models are non-executable data files.
-
-If enabled (default), the device will periodically check for updated speech models and then download them from a Microsoft service using the Background Internet Transfer Service (BITS).
-
-
-
diff --git a/policy_templates/en-US/StartMenu.adml b/policy_templates/en-US/StartMenu.adml
deleted file mode 100644
index f61632c..0000000
--- a/policy_templates/en-US/StartMenu.adml
+++ /dev/null
@@ -1,681 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- At least Windows Server 2008 R2 or Windows 7. Not supported on Windows 10 or later
- Windows 7 and Windows 10
- Clear the recent programs list for new users
- If you enable this policy setting, the recent programs list in the start menu will be blank for each new user.
-
-If you disable or do not configure this policy, the start menu recent programs list will be pre-populated with programs for each new user.
- Remove Games link from Start Menu
- If you enable this policy the start menu will not show a link to the Games folder.
-
-If you disable or do not configure this policy, the start menu will show a link to the Games folder, unless the user chooses to remove it in the start menu control panel.
- Remove Search Computer link
- If you enable this policy, the "See all results" link will not be shown when the user performs a search in the start menu search box.
-
-If you disable or do not configure this policy, the "See all results" link will be shown when the user performs a search in the start menu search box.
- Remove See More Results / Search Everywhere link
-
- If you enable this policy, a "See more results" / "Search Everywhere" link will not be shown when the user performs a search in the start menu search box.
-
-If you disable or do not configure this policy, a "See more results" link will be shown when the user performs a search in the start menu search box. If a 3rd party protocol handler is installed, a "Search Everywhere" link will be shown instead of the "See more results" link.
- Add Search Internet link to Start Menu
-
-If you enable this policy, a "Search the Internet" link is shown when the user performs a search in the start menu search box. This button launches the default browser with the search terms.
-
-If you disable this policy, there will not be a "Search the Internet" link when the user performs a search in the start menu search box.
-
-If you do not configure this policy (default), there will not be a "Search the Internet" link on the start menu.
- Do not search for files
- If you enable this policy setting the Start menu search box will not search for files.
-
-If you disable or do not configure this policy setting, the Start menu will search for files, unless the user chooses not to do so directly in Control Panel. If you enable this policy, a "See more results" / "Search Everywhere" link will not be shown when the user performs a search in the start menu search box.
- Do not search Internet
- If you enable this policy the start menu search box will not search for internet history or favorites.
-
-If you disable or do not configure this policy, the start menu will search for for internet history or favorites, unless the user chooses not to in the start menu control panel.
- Do not search programs and Control Panel items
- If you enable this policy setting the Start menu search box will not search for programs or Control Panel items.
-
-If you disable or do not configure this policy setting, the Start menu search box will search for programs and Control Panel items, unless the user chooses not to do so directly in Control Panel.
- Do not search communications
- If you enable this policy the start menu search box will not search for communications.
-
-If you disable or do not configure this policy, the start menu will search for communications, unless the user chooses not to in the start menu control panel.
- Remove user folder link from Start Menu
- If you enable this policy the start menu will not show a link to the user's storage folder.
-
-If you disable or do not configure this policy, the start menu will display a link, unless the user chooses to remove it in the start menu control panel.
- Add the Run command to the Start Menu
- If you enable this setting, the Run command is added to the Start menu. If you disable or do not configure this setting, the Run command is not visible on the Start menu by default, but it can be added from the Taskbar and Start menu properties. If the Remove Run link from Start Menu policy is set, the Add the Run command to the Start menu policy has no effect.
- Clear history of recently opened documents on exit
- Clear history of recently opened documents on exit.
-
-If you enable this setting, the system deletes shortcuts to recently used document files when the user logs off. As a result, the Recent Items menu on the Start menu is always empty when the user logs on. In addition, recently and frequently used items in the Jump Lists off of programs in the Start Menu and Taskbar will be cleared when the user logs off.
-
-If you disable or do not configure this setting, the system retains document shortcuts, and when a user logs on, the Recent Items menu and the Jump Lists appear just as it did when the user logged off.
-
-Note: The system saves document shortcuts in the user profile in the System-drive\Users\User-name\Recent folder.
-
-Also, see the "Remove Recent Items menu from Start Menu" and "Do not keep history of recently opened documents" policies in this folder. The system only uses this setting when neither of these related settings are selected.
-
-This setting does not clear the list of recent files that Windows programs display at the bottom of the File menu. See the "Do not keep history of recently opened documents" setting.
-
-This policy setting also does not hide document shortcuts displayed in the Open dialog box. See the "Hide the dropdown list of recent files" setting.
-
-This policy also does not clear items that the user may have pinned to the Jump Lists, or Tasks that the application has provided for their menu. See the "Do not allow pinning items in Jump Lists" setting.
- Add Logoff to the Start Menu
- This policy only applies to the classic version of the start menu and does not affect the new style start menu.
-
-Adds the "Log Off <username>" item to the Start menu and prevents users from removing it.
-
-If you enable this setting, the Log Off <username> item appears in the Start menu. This setting also removes the Display Logoff item from Start Menu Options. As a result, users cannot remove the Log Off <username> item from the Start Menu.
-
-If you disable this setting or do not configure it, users can use the Display Logoff item to add and remove the Log Off item.
-
-This setting affects the Start menu only. It does not affect the Log Off item on the Windows Security dialog box that appears when you press Ctrl+Alt+Del.
-
-Note: To add or remove the Log Off item on a computer, click Start, click Settings, click Taskbar and Start Menu, click the Start Menu Options tab, and then, in the Start Menu Settings box, click Display Logoff.
-
-Also, see "Remove Logoff" in User Configuration\Administrative Templates\System\Logon/Logoff.
- Gray unavailable Windows Installer programs Start Menu shortcuts
- Displays Start menu shortcuts to partially installed programs in gray text.
-
-This setting makes it easier for users to distinguish between programs that are fully installed and those that are only partially installed.
-
-Partially installed programs include those that a system administrator assigns using Windows Installer and those that users have configured for full installation upon first use.
-
-If you disable this setting or do not configure it, all Start menu shortcuts appear as black text.
-
-Note: Enabling this setting can make the Start menu slow to open.
- Turn off personalized menus
- Disables personalized menus.
-
-Windows personalizes long menus by moving recently used items to the top of the menu and hiding items that have not been used recently. Users can display the hidden items by clicking an arrow to extend the menu.
-
-If you enable this setting, the system does not personalize menus. All menu items appear and remain in standard order. Also, this setting removes the "Use Personalized Menus" option so users do not try to change the setting while a setting is in effect.
-
-Note: Personalized menus require user tracking. If you enable the "Turn off user tracking" setting, the system disables user tracking and personalized menus and ignores this setting.
-
-Tip: To Turn off personalized menus without specifying a setting, click Start, click Settings, click Taskbar and Start Menu, and then, on the General tab, clear the "Use Personalized Menus" option.
- Lock the Taskbar
- This setting affects the taskbar, which is used to switch between running applications.
-
-The taskbar includes the Start button, list of currently running tasks, and the notification area. By default, the taskbar is located at the bottom of the screen, but it can be dragged to any side of the screen. When it is locked, it cannot be moved or resized.
-
-If you enable this setting, it prevents the user from moving or resizing the taskbar. While the taskbar is locked, auto-hide and other taskbar options are still available in Taskbar properties.
-
-If you disable this setting or do not configure it, the user can configure the taskbar position.
-
-Note: Enabling this setting also locks the QuickLaunch bar and any other toolbars that the user has on their taskbar. The toolbar's position is locked, and the user cannot show and hide various toolbars using the taskbar context menu.
- Add "Run in Separate Memory Space" check box to Run dialog box
- Lets users run a 16-bit program in a dedicated (not shared) Virtual DOS Machine (VDM) process.
-
-All DOS and 16-bit programs run on Windows 2000 Professional and Windows XP Professional in the Windows Virtual DOS Machine program. VDM simulates a 16-bit environment, complete with the DLLs required by 16-bit programs. By default, all 16-bit programs run as threads in a single, shared VDM process. As such, they share the memory space allocated to the VDM process and cannot run simultaneously.
-
-Enabling this setting adds a check box to the Run dialog box, giving users the option of running a 16-bit program in its own dedicated NTVDM process. The additional check box is enabled only when a user enters a 16-bit program in the Run dialog box.
- Turn off notification area cleanup
- This setting affects the notification area, also called the "system tray."
-
-The notification area is located in the task bar, generally at the bottom of the screen, and it includes the clock and current notifications. This setting determines whether the items are always expanded or always collapsed. By default, notifications are collapsed. The notification cleanup << icon can be referred to as the "notification chevron."
-
-If you enable this setting, the system notification area expands to show all of the notifications that use this area.
-
-If you disable this setting, the system notification area will always collapse notifications.
-
-If you do not configure it, the user can choose if they want notifications collapsed.
- Remove Balloon Tips on Start Menu items
- Hides pop-up text on the Start menu and in the notification area.
-
-When you hold the cursor over an item on the Start menu or in the notification area, the system displays pop-up text providing additional information about the object.
-
-If you enable this setting, some of this pop-up text is not displayed. The pop-up text affected by this setting includes "Click here to begin" on the Start button, "Where have all my programs gone" on the Start menu, and "Where have my icons gone" in the notification area.
-
-If you disable this setting or do not configure it, all pop-up text is displayed on the Start menu and in the notification area.
- Prevent users from customizing their Start Screen
- This policy setting allows you to prevent users from changing their Start screen layout.
-
-If you enable this setting, you will prevent a user from selecting an app, resizing a tile, pinning/unpinning a tile or a secondary tile, entering the customize mode and rearranging tiles within Start and Apps.
-
-If you disable or do not configure this setting, you will allow a user to select an app, resize a tile, pin/unpin a tile or a secondary tile, enter the customize mode and rearrange tiles within Start and Apps.
- Clear tile notifications during log on
- If you enable this setting, the system deletes tile notifications when the user logs on. As a result, the Tiles in the start view will always show their default content when the user logs on. In addition, any cached versions of these notifications will be cleared when the user logs on.
-
-If you disable or do not configure this setting, the system retains notifications, and when a user logs on, the tiles appear just as they did when the user logged off, including the history of previous notifications for each tile.
-
-This setting does not prevent new notifications from appearing. See the "Turn off Application Notifications" setting to prevent new notifications.
- Pin Apps to Start when installed
- This policy setting allows pinning apps to Start by default, when they are included by AppID on the list.
-
- Start Layout
- Specifies the Start layout for users.
-
-This setting lets you specify the Start layout for users and prevents them from changing its configuration. The Start layout you specify must be stored in an XML file that was generated by the Export-StartLayout PowerShell cmdlet.
-To use this setting, you must first manually configure a device's Start layout to the desired look and feel. Once you are done, run the Export-StartLayout PowerShell cmdlet on that same device. The cmdlet will generate an XML file representing the layout you configured.
-
-Once the XML file is generated and moved to the desired file path, type the fully qualified path and name of the XML file. You can type a local path, such as C:\StartLayouts\myLayout.xml or a UNC path, such as \\Server\Share\Layout.xml. If the specified file is not available when the user logs on, the layout won't be changed. Users cannot customize their Start screen while this setting is enabled.
-
-If you disable this setting or do not configure it, the Start screen layout won't be changed and users will be able to customize it.
- Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands
- This policy setting prevents users from performing the following commands from the Start menu or Windows Security screen: Shut Down, Restart, Sleep, and Hibernate. This policy setting does not prevent users from running Windows-based programs that perform these functions.
-
-If you enable this policy setting, the Power button and the Shut Down, Restart, Sleep, and Hibernate commands are removed from the Start menu. The Power button is also removed from the Windows Security screen, which appears when you press CTRL+ALT+DELETE.
-
-If you disable or do not configure this policy setting, the Power button and the Shut Down, Restart, Sleep, and Hibernate commands are available on the Start menu. The Power button on the Windows Security screen is also available.
-
-Note: Third-party programs certified as compatible with Microsoft Windows Vista, Windows XP SP2, Windows XP SP1, Windows XP, or Windows 2000 Professional are required to support this policy setting.
- Remove and prevent access to the Shut Down, Restart, Sleep, and Hibernate commands
- This policy setting prevents users from performing the following commands from the Windows security screen, the logon screen, and the Start menu: Shut Down, Restart, Sleep, and Hibernate. This policy setting does not prevent users from running Windows-based programs that perform these functions.
-
-If you enable this policy setting, the shutdown, restart, sleep, and hibernate commands are removed from the Start menu. The Power button is also removed from the Windows Security screen, which appears when you press CTRL+ALT+DELETE, and from the logon screen.
-
-If you disable or do not configure this policy setting, the Power button and the Shut Down, Restart, Sleep, and Hibernate commands are available on the Start menu. The Power button on the Windows Security and logon screens is also available.
- Remove common program groups from Start Menu
- Removes items in the All Users profile from the Programs menu on the Start menu.
-
-By default, the Programs menu contains items from the All Users profile and items from the user's profile. If you enable this setting, only items in the user's profile appear in the Programs menu.
-
-Tip: To see the Program menu items in the All Users profile, on the system drive, go to ProgramData\Microsoft\Windows\Start Menu\Programs.
- Remove Favorites menu from Start Menu
- Prevents users from adding the Favorites menu to the Start menu or classic Start menu.
-
-If you enable this setting, the Display Favorites item does not appear in the Advanced Start menu options box.
-
-If you disable or do not configure this setting, the Display Favorite item is available.
-
-Note:The Favorities menu does not appear on the Start menu by default. To display the Favorites menu, right-click Start, click Properties, and then click Customize. If you are using Start menu, click the Advanced tab, and then, under Start menu items, click the Favorites menu. If you are using the classic Start menu, click Display Favorites under Advanced Start menu options.
-
-Note:The items that appear in the Favorites menu when you install Windows are preconfigured by the system to appeal to most users. However, users can add and remove items from this menu, and system administrators can create a customized Favorites menu for a user group.
-
-Note:This setting only affects the Start menu. The Favorites item still appears in File Explorer and in Internet Explorer.
- Remove Search link from Start Menu
- This policy setting allows you to remove the Search link from the Start menu, and disables some File Explorer search elements. Note that this does not remove the search box from the new style Start menu.
-
-If you enable this policy setting, the Search item is removed from the Start menu and from the context menu that appears when you right-click the Start menu. Also, the system does not respond when users press the Application key (the key with the Windows logo)+ F.
-
-Note: Enabling this policy setting also prevents the user from using the F3 key.
-
-In File Explorer, the Search item still appears on the Standard buttons toolbar, but the system does not respond when the user presses Ctrl+F. Also, Search does not appear in the context menu when you right-click an icon representing a drive or a folder.
-
-This policy setting affects the specified user interface elements only. It does not affect Internet Explorer and does not prevent the user from using other methods to search.
-
-If you disable or do not configure this policy setting, the Search link is available from the Start menu.
- Show or hide "Most used" list from Start menu
- If you enable this policy setting, you can configure Start menu to show or hide the list of user's most used apps, regardless of user settings.
-
-Selecting "Show" will force the "Most used" list to be shown, and user cannot change to hide it using the Settings app.
-
-Selecting "Hide" will force the "Most used" list to be hidden, and user cannot change to show it using the Settings app.
-
-Selecting "Not Configured", or if you disable or do not configure this policy setting, all will allow users to turn on or off the display of "Most used" list using the Settings app. This is default behavior.
-
-Note: configuring this policy to "Show" or "Hide" on supported versions of Windows 10 will supercede any policy setting of "Remove frequent programs list from the Start Menu" (which manages same part of Start menu but with fewer options).
- Not Configured
- Show
- Hide
- Remove frequent programs list from the Start Menu
- If you enable this setting, the frequently used programs list is removed from the Start menu.
-
-If you disable this setting or do not configure it, the frequently used programs list remains on the simple Start menu.
- Remove Help menu from Start Menu
- This policy setting allows you to remove the Help command from the Start menu.
-
-If you enable this policy setting, the Help command is removed from the Start menu.
-
-If you disable or do not configure this policy setting, the Help command is available from the Start menu.
-
-This policy setting only affects the Start menu. It does not remove the Help menu from File Explorer and does not prevent users from running Help.
- Turn off user tracking
- This policy setting allows you to turn off user tracking.
-
-If you enable this policy setting, the system does not track the programs that the user runs, and does not display frequently used programs in the Start Menu.
-
-If you disable or do not configure this policy setting, the system tracks the programs that the user runs. The system uses this information to customize Windows features, such as showing frequently used programs in the Start Menu.
-
-Also, see these related policy settings: "Remove frequent programs liist from the Start Menu" and "Turn off personalized menus".
-
-This policy setting does not prevent users from pinning programs to the Start Menu or Taskbar. See the "Remove pinned programs list from the Start Menu" and "Do not allow pinning programs to the Taskbar" policy settings.
-
- Remove All Programs list from the Start menu
- If you enable this setting, the Start Menu will either collapse or remove the all apps list from the Start menu.
-
-Selecting "Collapse" will not display the app list next to the pinned tiles in Start. An "All apps" button will be displayed on Start to open the all apps list. This is equivalent to setting the "Show app list in Start" in Settings to Off.
-
-Selecting "Collapse and disable setting" will do the same as the collapse option and disable the "Show app list in Start menu" in Settings, so users cannot turn it to On.
-
-Selecting "Remove and disable setting" will remove the all apps list from Start and disable the "Show app list in Start menu" in Settings, so users cannot turn it to On. Select this option for compatibility with earlier versions of Windows.
-
-If you disable or do not configure this setting, the all apps list will be visible by default, and the user can change "Show app list in Start" in Settings.
- None
- Collapse
- Collapse and disable setting
- Remove and disable setting
-
- Remove Network Connections from Start Menu
- This policy setting allows you to remove Network Connections from the Start Menu.
-
-If you enable this policy setting, users are prevented from running Network Connections.
-
-Enabling this policy setting prevents the Network Connections folder from opening. This policy setting also removes Network Connections from Settings on the Start menu.
-
-Network Connections still appears in Control Panel and in File Explorer, but if users try to start it, a message appears explaining that a setting prevents the action.
-
-If you disable or do not configure this policy setting, Network Connections is available from the Start Menu.
-
-Also, see the "Disable programs on Settings menu" and "Disable Control Panel" policy settings and the policy settings in the Network Connections folder (Computer Configuration and User Configuration\Administrative Templates\Network\Network Connections).
- Remove pinned programs list from the Start Menu
- If you enable this setting, the "Pinned Programs" list is removed from the Start menu. Users cannot pin programs to the Start menu.
-
-In Windows XP and Windows Vista, the Internet and email checkboxes are removed from the 'Customize Start Menu' dialog.
-
-If you disable this setting or do not configure it, the "Pinned Programs" list remains on the Start menu. Users can pin and unpin programs in the Start Menu.
- Do not keep history of recently opened documents
- Prevents the operating system and installed programs from creating and displaying shortcuts to recently opened documents.
-
-If you enable this setting, the system and Windows programs do not create shortcuts to documents opened while the setting is in effect. Also, they retain but do not display existing document shortcuts. The system empties the Recent Items menu on the Start menu, and Windows programs do not display shortcuts at the bottom of the File menu. In addition, the Jump Lists off of programs in the Start Menu and Taskbar do not show lists of recently or frequently used files, folders, or websites.
-
-If you disable or do not configure this setting, the system will store and display shortcuts to recently and frequently used files, folders, and websites.
-
-Note: The system saves document shortcuts in the user profile in the System-drive\Users\User-name\Recent folder.
-
-Also, see the "Remove Recent Items menu from Start Menu" and "Clear history of recently opened documents on exit" policies in this folder.
-
-If you enable this setting but do not enable the "Remove Recent Items menu from Start Menu" setting, the Recent Items menu appears on the Start menu, but it is empty.
-
-If you enable this setting, but then later disable it or set it to Not Configured, the document shortcuts saved before the setting was enabled reappear in the Recent Items menu and program File menus, and Jump Lists.
-
-This setting does not hide or prevent the user from pinning files, folders, or websites to the Jump Lists. See the "Do not allow pinning items in Jump Lists" setting. This policy also does not hide Tasks that the application has provided for their Jump List. This setting does not hide document shortcuts displayed in the Open dialog box. See the "Hide the dropdown list of recent files" setting.
-
-Note: It is a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
- Remove Recent Items menu from Start Menu
- Removes the Recent Items menu from the Start menu. Removes the Documents menu from the classic Start menu.
-
-The Recent Items menu contains links to the non-program files that users have most recently opened. It appears so that users can easily reopen their documents.
-
-If you enable this setting, the system saves document shortcuts but does not display the Recent Items menu in the Start Menu, and users cannot turn the menu on.
-
-If you later disable the setting, so that the Recent Items menu appears in the Start Menu, the document shortcuts saved before the setting was enabled and while it was in effect appear in the Recent Items menu.
-
-When the setting is disabled, the Recent Items menu appears in the Start Menu, and users cannot remove it.
-
-If the setting is not configured, users can turn the Recent Items menu on and off.
-
-Note: This setting does not prevent Windows programs from displaying shortcuts to recently opened documents. See the "Do not keep history of recently opened documents" setting.
-
-This setting also does not hide document shortcuts displayed in the Open dialog box. See the "Hide the dropdown list of recent files" setting.
- Do not use the search-based method when resolving shell shortcuts
- This policy setting prevents the system from conducting a comprehensive search of the target drive to resolve a shortcut.
-
-If you enable this policy setting, the system does not conduct the final drive search. It just displays a message explaining that the file is not found.
-
-If you disable or do not configure this policy setting, by default, when the system cannot find the target file for a shortcut (.lnk), it searches all paths associated with the shortcut. If the target file is located on an NTFS partition, the system then uses the target's file ID to find a path. If the resulting path is not correct, it conducts a comprehensive search of the target drive in an attempt to find the file.
-
-Note: This policy setting only applies to target files on NTFS partitions. FAT partitions do not have this ID tracking and search capability.
-
-Also, see the "Do not track Shell shortcuts during roaming" and the "Do not use the tracking-based method when resolving shell shortcuts" policy settings.
- Do not use the tracking-based method when resolving shell shortcuts
- This policy setting prevents the system from using NTFS tracking features to resolve a shortcut.
-
-If you enable this policy setting, the system does not try to locate the file by using its file ID. It skips this step and begins a comprehensive search of the drive specified in the target path.
-
-If you disable or do not configure this policy setting, by default, when the system cannot find the target file for a shortcut (.lnk), it searches all paths associated with the shortcut. If the target file is located on an NTFS partition, the system then uses the target's file ID to find a path. If the resulting path is not correct, it conducts a comprehensive search of the target drive in an attempt to find the file.
-
-Note: This policy setting only applies to target files on NTFS partitions. FAT partitions do not have this ID tracking and search capability.
-
-Also, see the "Do not track Shell shortcuts during roaming" and the "Do not use the search-based method when resolving shell shortcuts" policy settings.
- Remove Run menu from Start Menu
- Allows you to remove the Run command from the Start menu, Internet Explorer, and Task Manager.
-
-If you enable this setting, the following changes occur:
-
-(1) The Run command is removed from the Start menu.
-
-(2) The New Task (Run) command is removed from Task Manager.
-
-(3) The user will be blocked from entering the following into the Internet Explorer Address Bar:
-
---- A UNC path: \\<server>\<share>
-
----Accessing local drives: e.g., C:
-
---- Accessing local folders: e.g., \temp>
-
-Also, users with extended keyboards will no longer be able to display the Run dialog box by pressing the Application key (the key with the Windows logo) + R.
-
-If you disable or do not configure this setting, users will be able to access the Run command in the Start menu and in Task Manager and use the Internet Explorer Address Bar.
-
-
-
-Note:This setting affects the specified interface only. It does not prevent users from using other methods to run programs.
-
-Note: It is a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
- Remove programs on Settings menu
- This policy setting allows you to remove programs on Settings menu.
-
-If you enable this policy setting, the Control Panel, Printers, and Network and Connection folders are removed from Settings on the Start menu, and from Computer and File Explorer. It also prevents the programs represented by these folders (such as Control.exe) from running.
-
-However, users can still start Control Panel items by using other methods, such as right-clicking the desktop to start Display or right-clicking Computer to start System.
-
-If you disable or do not configure this policy setting, the Control Panel, Printers, and Network and Connection folders from Settings are available on the Start menu, and from Computer and File Explorer.
-
-Also, see the "Disable Control Panel," "Disable Display in Control Panel," and "Remove Network Connections from Start Menu" policy settings.
- Prevent changes to Taskbar and Start Menu Settings
- This policy setting allows you to prevent changes to Taskbar and Start Menu Settings.
-
-If you enable this policy setting, The user will be prevented from opening the Taskbar Properties dialog box.
-
-If the user right-clicks the taskbar and then clicks Properties, a message appears explaining that a setting prevents the action.
-
-If you disable or do not configure this policy setting, the Taskbar and Start Menu items are available from Settings on the Start menu.
- Remove Default Programs link from the Start menu.
- This policy setting allows you to remove the Default Programs link from the Start menu.
-
-If you enable this policy setting, the Default Programs link is removed from the Start menu.
-
-Clicking the Default Programs link from the Start menu opens the Default Programs control panel and provides administrators the ability to specify default programs for certain activities, such as Web browsing or sending e-mail, as well as which programs are accessible from the Start menu, desktop, and other locations.
-
-If you disable or do not configure this policy setting, the Default Programs link is available from the Start menu.
-
-Note: This policy setting does not prevent the Set Default Programs for This Computer option from appearing in the Default Programs control panel.
- Remove Documents icon from Start Menu
- This policy setting allows you to remove the Documents icon from the Start menu and its submenus.
-
-If you enable this policy setting, the Documents icon is removed from the Start menu and its submenus. Enabling this policy setting only removes the icon. It does not prevent the user from using other methods to gain access to the contents of the Documents folder.
-
-Note: To make changes to this policy setting effective, you must log off and then log on.
-
-If you disable or do not configure this policy setting, he Documents icon is available from the Start menu.
-
-Also, see the "Remove Documents icon on the desktop" policy setting.
- Remove Music icon from Start Menu
- This policy setting allows you to remove the Music icon from Start Menu.
-
-If you enable this policy setting, the Music icon is no longer available from Start Menu.
-
-If you disable or do not configure this policy setting, the Music icon is available from Start Menu.
- Remove Network icon from Start Menu
- This policy setting allows you to remove the Network icon from Start Menu.
-
-If you enable this policy setting, the Network icon is no longer available from Start Menu.
-
-If you disable or do not configure this policy setting, the Network icon is available from Start Menu.
- Remove Pictures icon from Start Menu
- This policy setting allows you to remove the Pictures icon from Start Menu.
-
-If you enable this policy setting, the Pictures icon is no longer available from Start Menu.
-
-If you disable or do not configure this policy setting, the Pictures icon is available from Start Menu.
- Remove user's folders from the Start Menu
- Hides all folders on the user-specific (top) section of the Start menu. Other items appear, but folders are hidden.
-
-This setting is designed for use with redirected folders. Redirected folders appear on the main (bottom) section of the Start menu. However, the original, user-specific version of the folder still appears on the top section of the Start menu. Because the appearance of two folders with the same name might confuse users, you can use this setting to hide user-specific folders.
-
-Note that this setting hides all user-specific folders, not just those associated with redirected folders.
-
-If you enable this setting, no folders appear on the top section of the Start menu. If users add folders to the Start Menu directory in their user profiles, the folders appear in the directory but not on the Start menu.
-
-If you disable this setting or do not configured it, Windows 2000 Professional and Windows XP Professional display folders on both sections of the Start menu.
- Force classic Start Menu
- This setting affects the presentation of the Start menu.
-
-The classic Start menu in Windows 2000 Professional allows users to begin common tasks, while the new Start menu consolidates common items onto one menu. When the classic Start menu is used, the following icons are placed on the desktop: Documents, Pictures, Music, Computer, and Network. The new Start menu starts them directly.
-
-If you enable this setting, the Start menu displays the classic Start menu in the Windows 2000 style and displays the standard desktop icons.
-
-If you disable this setting, the Start menu only displays in the new style, meaning the desktop icons are now on the Start page.
-
-If you do not configure this setting, the default is the new style, and the user can change the view.
- Remove Clock from the system notification area
- Prevents the clock in the system notification area from being displayed.
-
-If you enable this setting, the clock will not be displayed in the system notification area.
-
-If you disable or do not configure this setting, the default behavior of the clock appearing in the notification area will occur.
- Prevent grouping of taskbar items
- This setting affects the taskbar buttons used to switch between running programs.
-
-Taskbar grouping consolidates similar applications when there is no room on the taskbar. It kicks in when the user's taskbar is full.
-
-If you enable this setting, it prevents the taskbar from grouping items that share the same program name. By default, this setting is always enabled.
-
-If you disable or do not configure it, items on the taskbar that share the same program are grouped together. The users have the option to disable grouping if they choose.
- Do not display any custom toolbars in the taskbar
- This setting affects the taskbar.
-
-The taskbar includes the Start button, buttons for currently running tasks, custom toolbars, the notification area, and the system clock. Toolbars include Quick Launch, Address, Links, Desktop, and other custom toolbars created by the user or by an application.
-
-If this setting is enabled, the taskbar does not display any custom toolbars, and the user cannot add any custom toolbars to the taskbar. Moreover, the "Toolbars" menu command and submenu are removed from the context menu. The taskbar displays only the Start button, taskbar buttons, the notification area, and the system clock.
-
-If this setting is disabled or is not configured, the taskbar displays all toolbars. Users can add or remove custom toolbars, and the "Toolbars" command appears in the context menu.
- Remove access to the context menus for the taskbar
- This policy setting allows you to remove access to the context menus for the taskbar.
-
-If you enable this policy setting, the menus that appear when you right-click the taskbar and items on the taskbar are hidden, such as the Start button, the clock, and the taskbar buttons.
-
-If you disable or do not configure this policy setting, the context menus for the taskbar are available.
-
-This policy setting does not prevent users from using other methods to issue the commands that appear on these menus.
- Hide the notification area
- This setting affects the notification area (previously called the "system tray") on the taskbar.
-
-Description: The notification area is located at the far right end of the task bar and includes the icons for current notifications and the system clock.
-
-If this setting is enabled, the user’s entire notification area, including the notification icons, is hidden. The taskbar displays only the Start button, taskbar buttons, custom toolbars (if any), and the system clock.
-
-If this setting is disabled or is not configured, the notification area is shown in the user's taskbar.
-
-Note: Enabling this setting overrides the "Turn off notification area cleanup" setting, because if the notification area is hidden, there is no need to clean up the icons.
- Remove user name from Start Menu
- This policy setting allows you to remove the user name label from the Start Menu in Windows XP and Windows Server 2003.
-
-If you enable this policy setting, the user name label is removed from the Start Menu in Windows XP and Windows Server 2003.
-
-To remove the user name folder on Windows Vista, set the "Remove user folder link from Start Menu" policy setting.
-
-If you disable or do not configure this policy setting, the user name label appears on the Start Menu in Windows XP and Windows Server 2003.
- Remove links and access to Windows Update
- This policy setting allows you to remove links and access to Windows Update.
-
-If you enable this policy setting, users are prevented from connecting to the Windows Update Web site.
-
-Enabling this policy setting blocks user access to the Windows Update Web site at http://windowsupdate.microsoft.com. Also, the policy setting removes the Windows Update hyperlink from the Start menu and from the Tools menu in Internet Explorer.
-
-Windows Update, the online extension of Windows, offers software updates to keep a user’s system up-to-date. The Windows Update Product Catalog determines any system files, security fixes, and Microsoft updates that users need and shows the newest versions available for download.
-
-If you disable or do not configure this policy setting, the Windows Update hyperlink is available from the Start menu and from the Tools menu in Internet Explorer.
-
-Also, see the "Hide the "Add programs from Microsoft" option" policy setting.
- Remove the "Undock PC" button from the Start Menu
- If you enable this setting, the "Undock PC" button is removed from the simple Start Menu, and your PC cannot be undocked.
-
-If you disable this setting or do not configure it, the "Undock PC" button remains on the simple Start menu, and your PC can be undocked.
- Remove Logoff on the Start Menu
- This policy setting allows you to removes the "Log Off <username>" item from the Start menu and prevents users from restoring it.
-
-If you enable this policy setting, the Log Off <username> item does not appear in the Start menu. This policy setting also removes the Display Logoff item from Start Menu Options. As a result, users cannot restore the Log Off <username> item to the Start Menu.
-
-If you disable or do not configure this policy setting, users can use the Display Logoff item to add and remove the Log Off item.
-
-This policy setting affects the Start menu only. It does not affect the Log Off item on the Windows Security dialog box that appears when you press Ctrl+Alt+Del, and it does not prevent users from using other methods to log off.
-
-Tip: To add or remove the Log Off item on a computer, click Start, click Settings, click Taskbar and Start Menu, click the Start Menu Options tab and, in the Start Menu Settings box, click Display Logoff.
-
-See also: "Remove Logoff" policy setting in User Configuration\Administrative Templates\System\Logon/Logoff.
- Prevent users from uninstalling applications from Start
- If you enable this setting, users cannot uninstall apps from Start.
-
-If you disable this setting or do not configure it, users can access the uninstall command from Start
- Change Start Menu power button
- Set the default action of the power button on the Start menu.
-
-If you enable this setting, the Start Menu will set the power button to the chosen action, and not let the user change this action.
-
-If you set the button to either Sleep or Hibernate, and that state is not supported on a computer, then the button will fall back to Shut Down.
-
-If you disable or do not configure this setting, the Start Menu power button will be set to Shut Down by default, and the user can change this setting to another action.
- Log off
- Shut Down
- Restart
- Sleep
- Hibernate
- Switch User
- Lock
- Show QuickLaunch on Taskbar
- This policy setting controls whether the QuickLaunch bar is displayed in the Taskbar.
-
-If you enable this policy setting, the QuickLaunch bar will be visible and cannot be turned off.
-
-If you disable this policy setting, the QuickLaunch bar will be hidden and cannot be turned on.
-
-If you do not configure this policy setting, then users will be able to turn the QuickLaunch bar on and off.
- Remove Homegroup link from Start Menu
- If you enable this policy the Start menu will not show a link to Homegroup. It also removes the homegroup item from the Start Menu options. As a result, users cannot add the homegroup link to the Start Menu.
-
- If you disable or do not configure this policy, users can use the Start Menu options to add or remove the homegroup link from the Start Menu.
- Remove Downloads link from Start Menu
- This policy setting allows you to remove the Downloads link from the Start Menu.
-
-If you enable this policy setting, the Start Menu does not show a link to the Downloads folder.
-
-If you disable or do not configure this policy setting, the Downloads link is available from the Start Menu.
- Remove File Explorer link from Start Menu Places bar
- This policy setting allows you to remove the File Explorer link from the Start Menu Places bar.
-
-If you enable this policy setting, File Explorer will not appear in the Start Menu Places list.
-
-If you disable or do not configure this policy setting, File Explorer can be displayed in the Start Menu Places list.
- Remove Settings link from Start Menu Places bar
- This policy setting allows you to remove the Settings link from the Start Menu Places bar.
-
-If you enable this policy setting, Settings will not appear in the Start Menu Places list.
-
-If you disable or do not configure this policy setting, Settings can be displayed in the Start Menu Places list.
- Remove Recorded TV link from Start Menu
- This policy setting allows you to remove the Recorded TV link from the Start Menu.
-
-If you enable this policy setting, the Start Menu does not show a link to the Recorded TV library.
-
-If you disable or do not configure this policy setting, the Recorded TV link is available from the Start Menu.
- Remove Videos link from Start Menu
- This policy setting allows you to remove the Videos link from the Start Menu.
-
-If you enable this policy setting, the Start Menu does not show a link to the Videos library.
-
-If you disable or do not configure this policy setting, the Videos link is available from the Start Menu.
- Show "Run as different user" command on Start
- This policy setting shows or hides the "Run as different user" command on the Start application bar.
-
-If you enable this setting, users can access the "Run as different user" command from Start for applications which support this functionality.
-
-If you disable this setting or do not configure it, users cannot access the "Run as different user" command from Start for any applications.
-
-Note: This setting does not prevent users from using other methods, such as the shift right-click menu on application's jumplists in the taskbar to issue the "Run as different user" command.
- Go to the desktop instead of Start when signing in
- This policy setting allows users to go to the desktop instead of the Start screen when they sign in.
-
-If you enable this policy setting, users will always go to the desktop when they sign in.
-
-If you disable this policy setting, users will always go to the Start screen when they sign in.
-
-If you don’t configure this policy setting, the default setting for the user’s device will be used, and the user can choose to change it.
- Show the Apps view automatically when the user goes to Start
- This policy setting allows the Apps view to be opened by default when the user goes to Start.
-
-If you enable this policy setting, the Apps view will appear whenever the user goes to Start. Users will still be able to switch between the Apps view and the Start screen.
-
-If you disable or don’t configure this policy setting, the Start screen will appear by default whenever the user goes to Start, and the user will be able to switch between the Apps view and the Start screen. Also, the user will be able to configure this setting.
- Search just apps from the Apps view
- This policy setting prevents the user from searching apps, files, settings (and the web if enabled) when the user searches from the Apps view.
-
-This policy setting is only applied when the Apps view is set as the default view for Start.
-
-If you enable this policy setting, searching from the Apps view will only search the list of installed apps.
-
-If you disable or don’t configure this policy setting, the user can configure this setting.
- List desktop apps first in the Apps view
- This policy setting allows desktop apps to be listed first in the Apps view in Start.
-
-If you enable this policy setting, desktop apps would be listed first when the apps are sorted by category in the Apps view. The other sorting options would continue to be available and the user could choose to change their default sorting options.
-
-If you disable or don't configure this policy setting, the desktop apps won't be listed first when the apps are sorted by category, and the user can configure this setting.
- Show Start on the display the user is using when they press the Windows logo key
- This policy setting allows the Start screen to appear on the display the user is using when they press the Windows logo key. This setting only applies to users who are using multiple displays.
-
-If you enable this policy setting, the Start screen will appear on the display the user is using when they press the Windows logo key.
-
-If you disable or don't configure this policy setting, the Start screen will always appear on the main display when the user presses the Windows logo key. Users will still be able to open Start on other displays by pressing the Start button on that display. Also, the user will be able to configure this setting.
- Force Start to be either full screen size or menu size
- If you enable this policy and set it to Start menu or full screen Start, Start will be that size and users will be unable to change the size of Start in Settings.
-
-If you disable or don’t configure this policy setting, Windows will automatically select the size based on hardware form factor and users will be able to change the size of Start in Settings.
- Start menu
- Full screen Start
- Remove the People Bar from the taskbar
- This policy allows you to remove the People Bar from the taskbar and disables the My People experience.
-
-If you enable this policy the people icon will be removed from the taskbar, the corresponding settings toggle is removed from the taskbar settings page, and users will not be able to pin people to the taskbar.
- Remove "Recently added" list from Start Menu
- This policy allows you to prevent the Start Menu from displaying a list of recently installed applications.
-
-If you enable this policy, the Start Menu will no longer display the "Recently added" list. The corresponding setting will also be disabled in Settings.
- Remove Recommended section from Start Menu
- This policy allows you to prevent the Start Menu from displaying a list of recommended applications and files.
-
-If you enable this policy setting, the Start Menu will no longer show the section containing a list of recommended files and apps.
-
- Remove Personalized Website Recommendations from the Recommended section in the Start Menu
- This policy setting allows you to hide the personalized websites in the recommended section of the Start Menu.
-
-If you enable this policy setting, the Start Menu will no longer show personalized website recommendations in the recommended section.
- Disable context menus in the Start Menu
- This policy allows you to prevent users from being able to open context menus in the Start Menu.
-
-If you enable this policy, then invocations of context menus within the Start Menu will be ignored.
- Simplify Quick Settings Layout
- If you enable this policy, Quick Settings will be reduced to only having the WiFi, Bluetooth, Accessibility, and VPN buttons; the brightness and volume sliders; and battery indicator and link to the Settings app.
-
-If you disable or don't configure this policy setting, the regular Quick Settings layout will appear whenever Quick Settings is invoked.
- Disable Editing Quick Settings
- If you enable this policy, the user will be unable to modify Quick Settings.
-
-If you disable or don't configure this policy setting, the user will be able to edit Quick Settings, such as pinning or unpinning buttons.
- Remove Quick Settings
- This policy setting removes Quick Settings from the bottom right area on the taskbar.
-
-The quick settings area is located at the left of the clock in the taskbar and includes icons for current network and volume.
-
-If this setting is enabled, Quick Settings is not displayed in the quick settings area.
-
-A reboot is required for this policy setting to take effect.
-
-
-
- Choose one of the following actions
-
-
- Choose one of the following actions
-
-
- Add AppIDs to the list:
-
-
-
-
-
-
- Reapply layout at every logon
-
-
- Choose one of the following sizes
-
-
- Choose one of the following actions
-
-
-
-
diff --git a/policy_templates/en-US/StorageHealth.adml b/policy_templates/en-US/StorageHealth.adml
deleted file mode 100644
index 447130e..0000000
--- a/policy_templates/en-US/StorageHealth.adml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-Storage Health
-ADMX file for Storage Health
-
-
- Storage Health
- Allow downloading updates to the Disk Failure Prediction Model
-
- Allows downloading new updates to ML Model parameters for predicting storage disk failure.
-
- Enabled:
- Updates would be downloaded for the Disk Failure Prediction Failure Model.
-
- Disabled:
- Updates would not be downloaded for the Disk Failure Prediction Failure Model.
-
- Not configured:
- Same as Enabled.
-
-
-
-
diff --git a/policy_templates/en-US/StorageSense.adml b/policy_templates/en-US/StorageSense.adml
deleted file mode 100644
index a9bc9eb..0000000
--- a/policy_templates/en-US/StorageSense.adml
+++ /dev/null
@@ -1,106 +0,0 @@
-
-Storage Sense
-ADMX file for Storage Sense
-
-
- Storage Sense
- Allow Storage Sense
-
-Storage Sense can automatically clean some of the user’s files to free up disk space. By default, Storage Sense is automatically turned on when the machine runs into low disk space and is set to run whenever the machine runs into storage pressure. This cadence can be changed in Storage settings or set with the "Configure Storage Sense cadence" group policy.
-
-Enabled:
-Storage Sense is turned on for the machine, with the default cadence as ‘during low free disk space’. Users cannot disable Storage Sense, but they can adjust the cadence (unless you also configure the "Configure Storage Sense cadence" group policy).
-
-Disabled:
-Storage Sense is turned off the machine. Users cannot enable Storage Sense.
-
-Not Configured:
-By default, Storage Sense is turned off until the user runs into low disk space or the user enables it manually. Users can configure this setting in Storage settings.
-
- Configure Storage Sense cadence
-
-Storage Sense can automatically clean some of the user’s files to free up disk space.
-
-If the group policy "Allow Storage Sense" is disabled, then this policy does not have any effect.
-
-Enabled:
-You must provide the desired Storage Sense cadence. Supported options are: daily, weekly, monthly, and during low free disk space. The default is 0 (during low free disk space).
-
-Disabled or Not Configured:
-By default, the Storage Sense cadence is set to “during low free disk space”. Users can configure this setting in Storage settings.
-
- Every day
- Every week
- Every month
- During low free disk space
- Allow Storage Sense Temporary Files cleanup
-
-When Storage Sense runs, it can delete the user’s temporary files that are not in use.
-
-If the group policy "Allow Storage Sense" is disabled, then this policy does not have any effect.
-
-Enabled:
-Storage Sense will delete the user’s temporary files that are not in use. Users cannot disable this setting in Storage settings.
-
-Disabled:
-Storage Sense will not delete the user’s temporary files. Users cannot enable this setting in Storage settings.
-
-Not Configured:
-By default, Storage Sense will delete the user’s temporary files. Users can configure this setting in Storage settings.
-
- Configure Storage Sense Recycle Bin cleanup threshold
-
-When Storage Sense runs, it can delete files in the user’s Recycle Bin if they have been there for over a certain amount of days.
-
-If the group policy "Allow Storage Sense" is disabled, then this policy does not have any effect.
-
-Enabled:
-You must provide the minimum age threshold (in days) of a file in the Recycle Bin before Storage Sense will delete it. Supported values are: 0 - 365.
-If you set this value to zero, Storage Sense will not delete files in the user’s Recycle Bin. The default is 30 days.
-
-Disabled or Not Configured:
-By default, Storage Sense will delete files in the user’s Recycle Bin that have been there for over 30 days. Users can configure this setting in Storage settings.
-
- Configure Storage Storage Downloads cleanup threshold
-
-When Storage Sense runs, it can delete files in the user’s Downloads folder if they haven’t been opened for more than a certain number of days.
-
-If the group policy "Allow Storage Sense" is disabled, then this policy does not have any effect.
-
-Enabled:
-You must provide the minimum number of days a file can remain unopened before Storage Sense deletes it from Downloads folder. Supported values are: 0 - 365.
-If you set this value to zero, Storage Sense will not delete files in the user’s Downloads folder. The default is 0, or never deleting files in the Downloads folder.
-
-Disabled or Not Configured:
-By default, Storage Sense will not delete files in the user’s Downloads folder. Users can configure this setting in Storage settings.
-
- Configure Storage Sense Cloud Content dehydration threshold
-
-When Storage Sense runs, it can dehydrate cloud-backed content that hasn’t been opened in a certain amount of days.
-
-If the group policy "Allow Storage Sense" is disabled, then this policy does not have any effect.
-
-Enabled:
-You must provide the minimum number of days a cloud-backed file can remain unopened before Storage Sense dehydrates it from the sync root. Supported values are: 0 - 365.
-If you set this value to zero, Storage Sense will not dehydrate any cloud-backed content. The default value is 0, or never dehydrating cloud-backed content.
-
-Disabled or Not Configured:
-By default, Storage Sense will not dehydrate any cloud-backed content. Users can configure this setting in Storage settings.
-
-
-
-
- Run Storage Sense:
-
-
- Minimum age (in days) of a files in the Recycle Bin folder before Storage sense will delete it (0 is never deleting files):
-
-
- Minimum age (in days) of a files in the Downloads folder before Storage sense will delete it (0 is never deleting files):
-
-
- Number of days since a cloud-backed file has been opened before Storage Sense will dehydrate it (0 is never dehydrating files):
-
-
-
-
diff --git a/policy_templates/en-US/SystemRestore.adml b/policy_templates/en-US/SystemRestore.adml
deleted file mode 100644
index 4df05a4..0000000
--- a/policy_templates/en-US/SystemRestore.adml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- System Restore
- Turn off Configuration
- Allows you to disable System Restore configuration through System Protection.
-
-This policy setting allows you to turn off System Restore configuration through System Protection.
-
-System Restore enables users, in the event of a problem, to restore their computers to a previous state without losing personal data files. The behavior of this policy setting depends on the "Turn off System Restore" policy setting.
-
-If you enable this policy setting, the option to configure System Restore through System Protection is disabled.
-
-If you disable or do not configure this policy setting, users can change the System Restore settings through System Protection.
-
-Also, see the "Turn off System Restore" policy setting. If the "Turn off System Restore" policy setting is enabled, the "Turn off System Restore configuration" policy setting is overwritten.
- Turn off System Restore
- Allows you to disable System Restore.
-
-This policy setting allows you to turn off System Restore.
-
-System Restore enables users, in the event of a problem, to restore their computers to a previous state without losing personal data files. By default, System Restore is turned on for the boot volume.
-
-If you enable this policy setting, System Restore is turned off, and the System Restore Wizard cannot be accessed. The option to configure System Restore or create a restore point through System Protection is also disabled.
-
-If you disable or do not configure this policy setting, users can perform System Restore and configure System Restore settings through System Protection.
-
-Also, see the "Turn off System Restore configuration" policy setting. If the "Turn off System Restore" policy setting is disabled or not configured, the "Turn off System Restore configuration" policy setting is used to determine whether the option to configure System Restore is available.
-
-
-
diff --git a/policy_templates/en-US/TPM.adml b/policy_templates/en-US/TPM.adml
deleted file mode 100644
index 560ce5e..0000000
--- a/policy_templates/en-US/TPM.adml
+++ /dev/null
@@ -1,142 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- This policy setting allows you to manage the Group Policy list of Trusted Platform Module (TPM) commands blocked by Windows.
-
-If you enable this policy setting, Windows will block the specified commands from being sent to the TPM on the computer. TPM commands are referenced by a command number. For example, command number 129 is TPM_OwnerReadInternalPub, and command number 170 is TPM_FieldUpgrade. To find the command number associated with each TPM command with TPM 1.2, run "tpm.msc" and navigate to the "Command Management" section.
-
-If you disable or do not configure this policy setting, only those TPM commands specified through the default or local lists may be blocked by Windows. The default list of blocked TPM commands is pre-configured by Windows. You can view the default list by running "tpm.msc", navigating to the "Command Management" section, and making visible the "On Default Block List" column. The local list of blocked TPM commands is configured outside of Group Policy by running "tpm.msc" or through scripting against the Win32_Tpm interface. See related policy settings to enforce or ignore the default and local lists of blocked TPM commands.
- Configure the list of blocked TPM commands
- This policy setting allows you to enforce or ignore the computer's default list of blocked Trusted Platform Module (TPM) commands.
-
-If you enable this policy setting, Windows will ignore the computer's default list of blocked TPM commands and will only block those TPM commands specified by Group Policy or the local list.
-
-The default list of blocked TPM commands is pre-configured by Windows. You can view the default list by running "tpm.msc", navigating to the "Command Management" section, and making visible the "On Default Block List" column. The local list of blocked TPM commands is configured outside of Group Policy by running "tpm.msc" or through scripting against the Win32_Tpm interface. See the related policy setting to configure the Group Policy list of blocked TPM commands.
-
-If you disable or do not configure this policy setting, Windows will block the TPM commands in the default list, in addition to commands in the Group Policy and local lists of blocked TPM commands.
- Ignore the default list of blocked TPM commands
- This policy setting allows you to enforce or ignore the computer's local list of blocked Trusted Platform Module (TPM) commands.
-
-If you enable this policy setting, Windows will ignore the computer's local list of blocked TPM commands and will only block those TPM commands specified by Group Policy or the default list.
-
-The local list of blocked TPM commands is configured outside of Group Policy by running "tpm.msc" or through scripting against the Win32_Tpm interface. The default list of blocked TPM commands is pre-configured by Windows. See the related policy setting to configure the Group Policy list of blocked TPM commands.
-
-If you disable or do not configure this policy setting, Windows will block the TPM commands found in the local list, in addition to commands in the Group Policy and default lists of blocked TPM commands.
- Ignore the local list of blocked TPM commands
- Trusted Platform Module Services
- Configure the level of TPM owner authorization information available to the operating system
- This policy setting configures how much of the TPM owner authorization information is stored in the registry of the local computer. Depending on the amount of TPM owner authorization information stored locally, the operating system and TPM-based applications can perform certain TPM actions which require TPM owner authorization without requiring the user to enter the TPM owner password.
-
-You can choose to have the operating system store either the full TPM owner authorization value, the TPM administrative delegation blob plus the TPM user delegation blob, or none.
-
-If you enable this policy setting, Windows will store the TPM owner authorization in the registry of the local computer according to the operating system managed TPM authentication setting you choose.
-
-Choose the operating system managed TPM authentication setting of "Full" to store the full TPM owner authorization, the TPM administrative delegation blob and the TPM user delegation blob in the local registry. This setting allows use of the TPM without requiring remote or external storage of the TPM owner authorization value. This setting is appropriate for scenarios which do not depend on preventing reset of the TPM anti-hammering logic or changing the TPM owner authorization value. Some TPM-based applications may require this setting be changed before features which depend on the TPM anti-hammering logic can be used.
-
-Choose the operating system managed TPM authentication setting of "Delegated" to store only the TPM administrative delegation blob and the TPM user delegation blob in the local registry. This setting is appropriate for use with TPM-based applications that depend on the TPM anti-hammering logic.
-
-Choose the operating system managed TPM authentication setting of "None" for compatibility with previous operating systems and applications or for use with scenarios that require TPM owner authorization not be stored locally. Using this setting might cause issues with some TPM-based applications.
-
-Note: If the operating system managed TPM authentication setting is changed from "Full" to "Delegated", the full TPM owner authorization value will be regenerated and any copies of the original TPM owner authorization value will be invalid.
-
- Full
- Delegated
- None
- Standard User Lockout Duration
- This policy setting allows you to manage the duration in minutes for counting standard user authorization failures for Trusted Platform Module (TPM) commands requiring authorization. If the number of TPM commands with an authorization failure within the duration equals a threshold, a standard user is prevented from sending commands requiring authorization to the TPM.
-
-This setting helps administrators prevent the TPM hardware from entering a lockout mode because it slows the speed standard users can send commands requiring authorization to the TPM.
-
-An authorization failure occurs each time a standard user sends a command to the TPM and receives an error response indicating an authorization failure occurred. Authorization failures older than this duration are ignored.
-
-For each standard user two thresholds apply. Exceeding either threshold will prevent the standard user from sending a command to the TPM that requires authorization.
-
-The Standard User Lockout Threshold Individual value is the maximum number of authorization failures each standard user may have before the user is not allowed to send commands requiring authorization to the TPM.
-
-The Standard User Lockout Total Threshold value is the maximum total number of authorization failures all standard users may have before all standard users are not allowed to send commands requiring authorization to the TPM.
-
-The TPM is designed to protect itself against password guessing attacks by entering a hardware lockout mode when it receives too many commands with an incorrect authorization value. When the TPM enters a lockout mode it is global for all users including administrators and Windows features like BitLocker Drive Encryption. The number of authorization failures a TPM allows and how long it stays locked out vary by TPM manufacturer. Some TPMs may enter lockout mode for successively longer periods of time with fewer authorization failures depending on past failures. Some TPMs may require a system restart to exit the lockout mode. Other TPMs may require the system to be on so enough clock cycles elapse before the TPM exits the lockout mode.
-
-An administrator with the TPM owner password may fully reset the TPM's hardware lockout logic using the TPM Management Console (tpm.msc). Each time an administrator resets the TPM's hardware lockout logic all prior standard user TPM authorization failures are ignored; allowing standard users to use the TPM normally again immediately.
-
-If this value is not configured, a default value of 480 minutes (8 hours) is used.
-
- Standard User Individual Lockout Threshold
- This policy setting allows you to manage the maximum number of authorization failures for each standard user for the Trusted Platform Module (TPM). If the number of authorization failures for the user within the duration for Standard User Lockout Duration equals this value, the standard user is prevented from sending commands to the Trusted Platform Module (TPM) that require authorization.
-
-This setting helps administrators prevent the TPM hardware from entering a lockout mode because it slows the speed standard users can send commands requiring authorization to the TPM.
-
-An authorization failure occurs each time a standard user sends a command to the TPM and receives an error response indicating an authorization failure occurred. Authorization failures older than the duration are ignored.
-
-For each standard user two thresholds apply. Exceeding either threshold will prevent the standard user from sending a command to the TPM that requires authorization.
-
-This value is the maximum number of authorization failures each standard user may have before the user is not allowed to send commands requiring authorization to the TPM.
-
-The Standard User Lockout Total Threshold value is the maximum total number of authorization failures all standard users may have before all standard users are not allowed to send commands requiring authorization to the TPM.
-
-The TPM is designed to protect itself against password guessing attacks by entering a hardware lockout mode when it receives too many commands with an incorrect authorization value. When the TPM enters a lockout mode it is global for all users including administrators and Windows features like BitLocker Drive Encryption. The number of authorization failures a TPM allows and how long it stays locked out vary by TPM manufacturer. Some TPMs may enter lockout mode for successively longer periods of time with fewer authorization failures depending on past failures. Some TPMs may require a system restart to exit the lockout mode. Other TPMs may require the system to be on so enough clock cycles elapse before the TPM exits the lockout mode.
-
-An administrator with the TPM owner password may fully reset the TPM's hardware lockout logic using the TPM Management Console (tpm.msc). Each time an administrator resets the TPM's hardware lockout logic all prior standard user TPM authorization failures are ignored; allowing standard users to use the TPM normally again immediately.
-
-If this value is not configured, a default value of 4 is used.
-
-A value of zero means the OS will not allow standard users to send commands to the TPM which may cause an authorization failure.
-
-
- Standard User Total Lockout Threshold
- This policy setting allows you to manage the maximum number of authorization failures for all standard users for the Trusted Platform Module (TPM). If the total number of authorization failures for all standard users within the duration for Standard User Lockout Duration equals this value, all standard users are prevented from sending commands to the Trusted Platform Module (TPM) that require authorization.
-
-This setting helps administrators prevent the TPM hardware from entering a lockout mode because it slows the speed standard users can send commands requiring authorization to the TPM.
-
-An authorization failure occurs each time a standard user sends a command to the TPM and receives an error response indicating an authorization failure occurred. Authorization failures older than the duration are ignored.
-
-For each standard user two thresholds apply. Exceeding either threshold will prevent the standard user from sending a command to the TPM that requires authorization.
-
-The Standard User Individual Lockout value is the maximum number of authorization failures each standard user may have before the user is not allowed to send commands requiring authorization to the TPM.
-
-This value is the maximum total number of authorization failures all standard users may have before all standard users are not allowed to send commands requiring authorization to the TPM.
-
-The TPM is designed to protect itself against password guessing attacks by entering a hardware lockout mode when it receives too many commands with an incorrect authorization value. When the TPM enters a lockout mode it is global for all users including administrators and Windows features like BitLocker Drive Encryption. The number of authorization failures a TPM allows and how long it stays locked out vary by TPM manufacturer. Some TPMs may enter lockout mode for successively longer periods of time with fewer authorization failures depending on past failures. Some TPMs may require a system restart to exit the lockout mode. Other TPMs may require the system to be on so enough clock cycles elapse before the TPM exits the lockout mode.
-
-An administrator with the TPM owner password may fully reset the TPM's hardware lockout logic using the TPM Management Console (tpm.msc). Each time an administrator resets the TPM's hardware lockout logic all prior standard user TPM authorization failures are ignored; allowing standard users to use the TPM normally again immediately.
-
-If this value is not configured, a default value of 9 is used.
-
-A value of zero means the OS will not allow standard users to send commands to the TPM which may cause an authorization failure.
-
-
- Configure the system to use legacy Dictionary Attack Prevention Parameters setting for TPM 2.0.
- This policy setting configures the TPM to use the Dictionary Attack Prevention Parameters (lockout threshold and recovery time) to the values that were used for Windows 10 Version 1607 and below. Setting this policy will take effect only if a) the TPM was originally prepared using a version of Windows after Windows 10 Version 1607 and b) the System has a TPM 2.0. Note that enabling this policy will only take effect after the TPM maintenance task runs (which typically happens after a system restart). Once this policy has been enabled on a system and has taken effect (after a system restart), disabling it will have no impact and the system's TPM will remain configured using the legacy Dictionary Attack Prevention parameters, regardless of the value of this group policy. The only way for the disabled setting of this policy to take effect on a system where it was once enabled is to a) disable it from group policy and b)clear the TPM on the system.
- Device Health Attestation Service
- Enable Device Health Attestation Monitoring and Reporting
- This group policy enables Device Health Attestation reporting (DHA-report) on supported devices. It enables supported devices to send Device Health Attestation related information (device boot logs, PCR values, TPM certificate, etc.) to Device Health Attestation Service (DHA-Service) every time a device starts. Device Health Attestation Service validates the security state and health of the devices, and makes the findings accessible to enterprise administrators via a cloud based reporting portal. This policy is independent of DHA reports that are initiated by device manageability solutions (like MDM or SCCM), and will not interfere with their workflows.
- Configure the system to clear the TPM if it is not in a ready state.
- This policy setting configures the system to prompt the user to clear the TPM if the TPM is detected to be in any state other than Ready. This policy will take effect only if the system’s TPM is in a state other than Ready, including if the TPM is “Ready, with reduced functionality”. The prompt to clear the TPM will start occurring after the next reboot, upon user login only if the logged in user is part of the Administrators group for the system. The prompt can be dismissed, but will reappear after every reboot and login until the policy is disabled or until the TPM is in a Ready state.
-
-
-
-
- Specify the commands to block by adding their numbers to the list.
- The list of blocked TPM commands:
- For example, to block the commands TPM_OwnerReadInternalPub
- and TPM_FieldUpgrade, add items 129 and 170 to the list.
-
-
- Operating system managed TPM authentication level:
-
-
- Duration for counting TPM authorization failures (minutes):
-
-
- Maximum number of authorization failures per duration:
-
-
- Maximum number of authorization failures per duration:
-
-
-
-
diff --git a/policy_templates/en-US/TabletPCInputPanel.adml b/policy_templates/en-US/TabletPCInputPanel.adml
deleted file mode 100644
index f65f96c..0000000
--- a/policy_templates/en-US/TabletPCInputPanel.adml
+++ /dev/null
@@ -1,136 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off AutoComplete integration with Input Panel
- Turns off the integration of application auto complete lists with Tablet PC Input Panel in applications where this behavior is available.
-
-Tablet PC Input Panel is a Tablet PC accessory that enables you to use handwriting or an on-screen keyboard to enter text, symbols, numbers, or keyboard shortcuts.
-
-If you enable this policy, application auto complete lists will never appear next to Input Panel. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you disable this policy, application auto complete lists will appear next to Input Panel in applications where the functionality is available. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you do not configure this policy, application auto complete lists will appear next to Input Panel in applications where the functionality is available. Users will be able to configure this setting on the Text completion tab in Input Panel Options.
- Prevent Input Panel tab from appearing
- Prevents Input Panel tab from appearing on the edge of the Tablet PC screen.
-
-Tablet PC Input Panel is a Tablet PC accessory that enables you to use handwriting or an on-screen keyboard to enter text, symbols, numbers, or keyboard shortcuts.
-
-If you enable this policy, Input Panel tab will not appear on the edge of the Tablet PC screen. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you disable this policy, Input Panel tab will appear on the edge of the Tablet PC screen. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you do not configure this policy, Input Panel tab will appear on the edge of the Tablet PC screen. Users will be able to configure this setting on the Opening tab in Input Panel Options.
-
-Caution: If you enable both the “Prevent Input Panel from appearing next to text entry areas” policy and the “Prevent Input Panel tab from appearing” policy, and disable the “Show Input Panel taskbar icon” policy, the user will then have no way to access Input Panel.
- For tablet pen input, don’t show the Input Panel icon
- Prevents the Tablet PC Input Panel icon from appearing next to any text entry area in applications where this behavior is available. This policy applies only when using a tablet pen as an input device.
-
-Tablet PC Input Panel is a Tablet PC accessory that enables you to use handwriting or an on-screen keyboard to enter text, symbols, numbers, or keyboard shortcuts.
-
-If you enable this policy, Input Panel will never appear next to text entry areas when using a tablet pen as an input device. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you disable this policy, Input Panel will appear next to any text entry area in applications where this behavior is available. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you do not configure this policy, Input Panel will appear next to text entry areas in applications where this behavior is available. Users will be able to configure this setting on the Opening tab in Input Panel Options.
-
-Caution: If you enable both the “Prevent Input Panel from appearing next to text entry areas” policy and the “Prevent Input Panel tab from appearing” policy, and disable the “Show Input Panel taskbar icon” policy, the user will then have no way to access Input Panel.
- For touch input, don’t show the Input Panel icon
- Prevents the Tablet PC Input Panel icon from appearing next to any text entry area in applications where this behavior is available. This policy applies only when a user is using touch input.
-
-Tablet PC Input Panel is a Tablet PC accessory that enables you to use handwriting or an on-screen keyboard to enter text, symbols, numbers, or keyboard shortcuts.
-
-If you enable this policy, Input Panel will never appear next to any text entry area when a user is using touch input. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you disable this policy, Input Panel will appear next to text entry areas in applications where this behavior is available. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you do not configure this policy, Input Panel will appear next to text entry areas in applications where this behavior is available. Users will be able to configure this setting on the Opening tab in Input Panel Options.
- Turn off password security in Input Panel
- High
- Low
- Medium
- Medium High
- Medium Low
- Adjusts password security settings in Touch Keyboard and Handwriting panel (a.k.a. Tablet PC Input Panel in Windows 7 and Windows Vista). These settings include using the on-screen keyboard by default, preventing users from switching to another Input Panel skin (the writing pad or character pad), and not showing what keys are tapped when entering a password.
-
-Touch Keyboard and Handwriting panel enables you to use handwriting or an on-screen keyboard to enter text, symbols, numbers, or keyboard shortcuts.
-
-If you enable this policy and choose “Low” from the drop-down box, password security is set to “Low.” At this setting, all password security settings are turned off. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you enable this policy and choose “Medium-Low” from the drop-down box, password security is set to “Medium-Low.” At this setting, when users enter passwords from Input Panel they use the on-screen keyboard by default, skin switching is allowed, and Input Panel displays the cursor and which keys are tapped. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you enable this policy and choose “Medium” from the drop-down box, password security is set to “Medium.” At this setting, when users enter passwords from Input Panel they use the on-screen keyboard by default, skin switching is not allowed, and Input Panel displays the cursor and which keys are tapped. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you enable this policy and choose to “Medium-High” from the drop-down box, password security is set to “Medium-High.” At this setting, when users enter passwords from Input Panel they use the on-screen keyboard by default, skin switching is allowed, and Input Panel does not display the cursor or which keys are tapped. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you enable this policy and choose “High” from the drop-down box, password security is set to “High.” At this setting, when users enter passwords from Input Panel they use the on-screen keyboard by default, skin switching is not allowed, and Input Panel does not display the cursor or which keys are tapped. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you disable this policy, password security is set to “Medium-High.” At this setting, when users enter passwords from Input Panel they use the on-screen keyboard by default, skin switching is allowed, and Input Panel does not display the cursor or which keys are tapped. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you do not configure this policy, password security is set to “Medium-High” by default. At this setting, when users enter passwords from Input Panel they use the on-screen keyboard by default, skin switching is allowed, and Input Panel does not display the cursor or which keys are tapped. Users will be able to configure this setting on the Advanced tab in Input Panel Options in Windows 7 and Windows Vista.
-
-Caution: If you lower password security settings, people who can see the user’s screen might be able to see their passwords.
- Include rarely used Chinese, Kanji, or Hanja characters
- Includes rarely used Chinese, Kanji, and Hanja characters when handwriting is converted to typed text. This policy applies only to the use of the Microsoft recognizers for Chinese (Simplified), Chinese (Traditional), Japanese, and Korean. This setting appears in Input Panel Options (in Windows 7 and Windows Vista only) only when these input languages or keyboards are installed.
-
-Touch Keyboard and Handwriting panel (a.k.a. Tablet PC Input Panel in Windows 7 and Windows Vista) enables you to use handwriting or an on-screen keyboard to enter text, symbols, numbers, or keyboard shortcuts.
-
-If you enable this policy, rarely used Chinese, Kanji, and Hanja characters will be included in recognition results when handwriting is converted to typed text. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you disable this policy, rarely used Chinese, Kanji, and Hanja characters will not be included in recognition results when handwriting is converted to typed text. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you do not configure this policy, rarely used Chinese, Kanji, and Hanja characters will not be included in recognition results when handwriting is converted to typed text. Users will be able to configure this setting on the Ink to text conversion tab in Input Panel Options (in Windows 7 and Windows Vista).
- Disable text prediction
- Prevents the Touch Keyboard and Handwriting panel (a.k.a. Tablet PC Input Panel in Windows 7 and Windows Vista) from providing text prediction suggestions. This policy applies for both the on-screen keyboard and the handwriting tab when the feature is available for the current input area and input language.
-
-Touch Keyboard and Handwriting panel enables you to use handwriting or an on-screen keyboard to enter text, symbols, numbers, or keyboard shortcuts.
-
-If you enable this policy, Input Panel will not provide text prediction suggestions. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you disable this policy, Input Panel will provide text prediction suggestions. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
-If you do not configure this policy, Input Panel will provide text prediction suggestions. Users will be able to configure this setting on the Text Completion tab in Input Panel Options in Windows 7 and Windows Vista.
-
- Turn off tolerant and Z-shaped scratch-out gestures
- All
- None
- Tolerant
-
- Turns off both the more tolerant scratch-out gestures that were added in Windows Vista and the Z-shaped scratch-out gesture that was available in Microsoft Windows XP Tablet PC Edition.
-
- The tolerant gestures let users scratch out ink in Input Panel by using strikethrough and other scratch-out gesture shapes.
-
- Tablet PC Input Panel is a Tablet PC accessory that enables you to use handwriting or an on-screen keyboard to enter text, symbols, numbers, or keyboard shortcuts.
-
- If you enable this policy and choose “All” from the drop-down menu, no scratch-out gestures will be available in Input Panel. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
- If you enable this policy and choose “Tolerant," users will be able to use the Z-shaped scratch-out gesture that was available in Microsoft Windows XP Tablet PC Edition. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
- If you enable this policy and choose “None,” users will be able to use both the tolerant scratch-out gestures and the Z-shaped scratch-out gesture. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
- If you disable this policy, users will be able to use both the tolerant scratch-out gestures and the Z-shaped scratch-out gesture. Users will not be able to configure this setting in the Input Panel Options dialog box.
-
- If you do not configure this policy, users will be able to use both the tolerant scratch-out gestures and the Z-shaped scratch-out gesture. Users will be able to configure this setting on the Gestures tab in Input Panel Options.
-
- Input Panel
-
-
-
- Turn off password security in Input Panel
-
-
- Turn off password security in Input Panel
-
-
- Turn off tolerant and Z-shaped scratch-out gestures
-
-
- Turn off tolerant and Z-shaped scratch-out gestures
-
-
-
-
diff --git a/policy_templates/en-US/TabletShell.adml b/policy_templates/en-US/TabletShell.adml
deleted file mode 100644
index a574e6a..0000000
--- a/policy_templates/en-US/TabletShell.adml
+++ /dev/null
@@ -1,97 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Accessories
- Cursors
- Do not allow Inkball to run
- Prevents start of InkBall game.
-
-If you enable this policy, the InkBall game will not run.
-
-If you disable this policy, the InkBall game will run.
-
-If you do not configure this policy, the InkBall game will run.
- Do not allow Windows Journal to be run
- Prevents start of Windows Journal.
-
-If you enable this policy, the Windows Journal accessory will not run.
-
-If you disable this policy, the Windows Journal accessory will run.
-
-If you do not configure this policy, the Windows Journal accessory will run.
- Do not allow printing to Journal Note Writer
- Prevents printing to Journal Note Writer.
-
-If you enable this policy, the Journal Note Writer printer driver will not allow printing to it. It will remain displayed in the list of available printers, but attempts to print to it will fail.
-
-If you disable this policy, you will be able to use this feature to print to a Journal Note.
-
-If you do not configure this policy, users will be able to use this feature to print to a Journal Note.
- Do not allow Snipping Tool to run
- Prevents the snipping tool from running.
-
-If you enable this policy setting, the Snipping Tool will not run.
-
-If you disable this policy setting, the Snipping Tool will run.
-
-If you do not configure this policy setting, the Snipping Tool will run.
- Hardware Buttons
- Pen Flicks Learning
- Pen UX Behaviors
- Prevent Back-ESC mapping
- Removes the Back->ESC mapping that normally occurs when menus are visible, and for applications that subscribe to this behavior.
-
-If you enable this policy, a button assigned to Back will not map to ESC.
-
-If you disable this policy, Back->ESC mapping will occur.
-
-If you do not configure this policy, Back->ESC mapping will occur.
- Prevent flicks
- Makes pen flicks and all related features unavailable.
-
-If you enable this policy, pen flicks and all related features are unavailable. This includes: pen flicks themselves, pen flicks training, pen flicks training triggers in Internet Explorer, the pen flicks notification and the pen flicks tray icon.
-
-If you disable or do not configure this policy, pen flicks and related features are available.
- Prevent Flicks Learning Mode
- Makes pen flicks learning mode unavailable.
-
-If you enable this policy, pen flicks are still available but learning mode is not. Pen flicks are off by default and can be turned on system-wide, but cannot be restricted to learning mode applications. This means that the pen flicks training triggers in Internet Explorer are disabled and that the pen flicks notification will never be displayed. However, pen flicks, the pen flicks tray icon and pen flicks training (that can be accessed through CPL) are still available. Conceptually this policy is a subset of the Disable pen flicks policy.
-
-If you disable or do not configure this policy, all the features described above will be available.
- Prevent launch an application
- Prevents the user from launching an application from a Tablet PC hardware button.
-
-If you enable this policy, applications cannot be launched from a hardware button, and "Launch an application" is removed from the drop down menu for configuring button actions (in the Tablet PC Control Panel buttons tab).
-
-If you disable this policy, applications can be launched from a hardware button.
-
-If you do not configure this policy, applications can be launched from a hardware button.
- Prevent press and hold
- Prevents press and hold actions on hardware buttons, so that only one action is available per button.
-
-If you enable this policy, press and hold actions are unavailable, and the button configuration dialog will display the following text: "Some settings are controlled by Group Policy. If a setting is unavailable, contact your system administrator."
-
-If you disable this policy, press and hold actions for buttons will be available.
-
-If you do not configure this policy, press and hold actions will be available.
- Turn off hardware buttons
- Turns off Tablet PC hardware buttons.
-
-If you enable this policy, no actions will occur when the buttons are pressed, and the buttons tab in Tablet PC Control Panel will be removed.
-
-If you disable this policy, user and OEM defined button actions will occur when the buttons are pressed.
-
-If you do not configure this policy, user and OEM defined button actions will occur when the buttons are pressed.
- Turn off pen feedback
- Disables visual pen action feedback, except for press and hold feedback.
-
-If you enable this policy, all visual pen action feedback is disabled except for press and hold feedback. Additionally, the mouse cursors are shown instead of the pen cursors.
-
-If you disable or do not configure this policy, visual feedback and pen cursors will be shown unless the user disables them in Control Panel.
-
-
-
diff --git a/policy_templates/en-US/TaskScheduler.adml b/policy_templates/en-US/TaskScheduler.adml
deleted file mode 100644
index 5a57779..0000000
--- a/policy_templates/en-US/TaskScheduler.adml
+++ /dev/null
@@ -1,69 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Prohibit Browse
- Limits newly scheduled to items on the user's Start menu, and prevents the user from changing the scheduled program for existing tasks.
-
-This setting removes the Browse button from the Schedule Task Wizard and from the Task tab of the properties dialog box for a task. Also, users cannot edit the "Run" box or the "Start in" box that determine the program and path for a task.
-
-As a result, when users create a task, they must select a program from the list in the Scheduled Task Wizard, which displays only the tasks that appear on the Start menu and its submenus. Once a task is created, users cannot change the program a task runs.
-
-Important: This setting does not prevent users from creating a new task by pasting or dragging any program into the Scheduled Tasks folder. To prevent this action, use the "Prohibit Drag-and-Drop" setting.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
- Hide Advanced Properties Checkbox in Add Scheduled Task Wizard
- This setting removes the "Open advanced properties for this task when I click Finish" checkbox from the last page of the Scheduled Task Wizard. This policy is only designed to simplify task creation for beginning users.
-
-The checkbox, when checked, instructs Task Scheduler to automatically open the newly created task's property sheet upon completion of the "Add Scheduled Task" wizard. The task's property sheet allows users to change task characteristics such as: the program the task runs, details of its schedule, idle time and power management settings, and its security context. Beginning users will often not be interested or confused by having the property sheet displayed automatically. Note that the checkbox is not checked by default even if this setting is Disabled or Not Configured.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
- Prohibit Drag-and-Drop
- Prevents users from adding or removing tasks by moving or copying programs in the Scheduled Tasks folder.
-
-This setting disables the Cut, Copy, Paste, and Paste Shortcut items on the context menu and the Edit menu in Scheduled Tasks. It also disables the drag-and-drop features of the Scheduled Tasks folder.
-
-As a result, users cannot add new scheduled tasks by dragging, moving, or copying a document or program into the Scheduled tasks folder.
-
-This setting does not prevent users from using other methods to create new tasks, and it does not prevent users from deleting tasks.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
- Prevent Task Run or End
- Prevents users from starting and stopping tasks manually.
-
-This setting removes the Run and End Task items from the context menu that appears when you right-click a task. As a result, users cannot start tasks manually or force tasks to end before they are finished.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
- Hide Property Pages
- Prevents users from viewing and changing the properties of an existing task.
-
-This setting removes the Properties item from the File menu in Scheduled Tasks and from the context menu that appears when you right-click a task. As a result, users cannot change any properties of a task. They can only see the properties that appear in Detail view and in the task preview.
-
-This setting prevents users from viewing and changing characteristics such as the program the task runs, its schedule details, idle time and power management settings, and its security context.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Tip: This setting affects existing tasks only. To prevent users from changing the properties of newly created tasks, use the "Remove Advanced Menu" setting.
- Prohibit New Task Creation
- Prevents users from creating new tasks.
-
-This setting removes the Add Scheduled Task item that starts the New Task Wizard. Also, the system does not respond when users try to move, paste, or drag programs or documents into the Scheduled Tasks folder.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Important: This setting does not prevent administrators of a computer from using At.exe to create new tasks or prevent administrators from submitting tasks from remote computers.
- Prohibit Task Deletion
- Prevents users from deleting tasks from the Scheduled Tasks folder.
-
-This setting removes the Delete command from the Edit menu in the Scheduled Tasks folder and from the menu that appears when you right-click a task. Also, the system does not respond when users try to cut or drag a task from the Scheduled Tasks folder.
-
-Note: This setting appears in the Computer Configuration and User Configuration folders. If both settings are configured, the setting in Computer Configuration takes precedence over the setting in User Configuration.
-
-Important: This setting does not prevent administrators of a computer from using At.exe to delete tasks.
- Task Scheduler
-
-
-
diff --git a/policy_templates/en-US/Taskbar.adml b/policy_templates/en-US/Taskbar.adml
deleted file mode 100644
index 506f8d7..0000000
--- a/policy_templates/en-US/Taskbar.adml
+++ /dev/null
@@ -1,204 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Remove the battery meter
- This policy setting allows you to remove the battery meter from the system control area.
-
-If you enable this policy setting, the battery meter is not displayed in the system notification area.
-
-If you disable or do not configure this policy setting, the battery meter is displayed in the system notification area.
- Remove the networking icon
- This policy setting allows you to remove the networking icon from the system control area.
-
-If you enable this policy setting, the networking icon is not displayed in the system notification area.
-
-If you disable or do not configure this policy setting, the networking icon is displayed in the system notification area.
- Remove the volume control icon
- This policy setting allows you to remove the volume control icon from the system control area.
-
-If you enable this policy setting, the volume control icon is not displayed in the system notification area.
-
-If you disable or do not configure this policy setting, the volume control icon is displayed in the system notification area.
- Remove the Security and Maintenance icon
- This policy setting allows you to remove Security and Maintenance from the system control area.
-
-If you enable this policy setting, the Security and Maintenance icon is not displayed in the system notification area.
-
-If you disable or do not configure this policy setting, the Security and Maintenance icon is displayed in the system notification area.
- Remove the Meet Now icon
- This policy setting allows you to remove the Meet Now icon from the system control area.
-
-If you enable this policy setting, the Meet Now icon is not displayed in the system notification area.
-
-If you disable or do not configure this policy setting, the Meet Now icon is displayed in the system notification area.
- Lock all taskbar settings
- This policy setting allows you to lock all taskbar settings.
-
-If you enable this policy setting, the user cannot access the taskbar control panel. The user is also unable to resize, move or rearrange toolbars on their taskbar.
-
-If you disable or do not configure this policy setting, the user will be able to set any taskbar setting that is not prevented by another policy setting.
- Prevent users from adding or removing toolbars
- This policy setting allows you to prevent users from adding or removing toolbars.
-
-If you enable this policy setting, the user is not allowed to add or remove any toolbars to the taskbar. Applications are not able to add toolbars either.
-
-If you disable or do not configure this policy setting, the users and applications are able to add toolbars to the taskbar.
- Prevent users from rearranging toolbars
- This policy setting allows you to prevent users from rearranging toolbars.
-
-If you enable this policy setting, users are not able to drag or drop toolbars to the taskbar.
-
-If you disable or do not configure this policy setting, users are able to rearrange the toolbars on the taskbar.
- Turn off all balloon notifications
- This policy setting allows you to turn off all notification balloons.
-
-If you enable this policy setting, no notification balloons are shown to the user.
-
-If you disable or do not configure this policy setting, notification balloons are shown to the user.
- Prevent users from moving taskbar to another screen dock location
- This policy setting allows you to prevent users from moving taskbar to another screen dock location.
-
-If you enable this policy setting, users are not able to drag their taskbar to another area of the monitor(s).
-
-If you disable or do not configure this policy setting, users are able to drag their taskbar to another area of the monitor unless prevented by another policy setting.
- Prevent users from resizing the taskbar
- This policy setting allows you to prevent users from resizing the taskbar.
-
-If you enable this policy setting, users are not be able to resize their taskbar.
-
-If you disable or do not configure this policy setting, users are able to resize their taskbar unless prevented by another setting.
- Turn off taskbar thumbnails
- This policy setting allows you to turn off taskbar thumbnails.
-
-If you enable this policy setting, the taskbar thumbnails are not displayed and the system uses standard text for the tooltips.
-
-If you disable or do not configure this policy setting, the taskbar thumbnails are displayed.
- Remove pinned programs from the Taskbar
- This policy setting allows you to remove pinned programs from the taskbar.
-
-If you enable this policy setting, pinned programs are prevented from being shown on the Taskbar. Users cannot pin programs to the Taskbar.
-
-If you disable or do not configure this policy setting, users can pin programs so that the program shortcuts stay on the Taskbar.
- Turn off feature advertisement balloon notifications
- This policy setting allows you to turn off feature advertisement balloon notifications.
-
-If you enable this policy setting, certain notification balloons that are marked as feature advertisements are not shown.
-
-If you disable do not configure this policy setting, feature advertisement balloons are shown.
- Turn off automatic promotion of notification icons to the taskbar
- This policy setting allows you to turn off automatic promotion of notification icons to the taskbar.
-
-If you enable this policy setting, newly added notification icons are not temporarily promoted to the Taskbar. Users can still configure icons to be shown or hidden in the Notification Control Panel.
-
-If you disable or do not configure this policy setting, newly added notification icons are temporarily promoted to the Taskbar.
- Disable showing balloon notifications as toasts.
- This policy disables the functionality that converts balloons to toast notifications.
-
-If you enable this policy setting, system and application notifications will render as balloons instead of toast notifications.
-
-Enable this policy setting if a specific app or system component that uses balloon notifications has compatibility issues with toast notifications.
-
-If you disable or don’t configure this policy setting, all notifications will appear as toast notifications.
-
-A reboot is required for this policy setting to take effect.
- Do not display or track items in Jump Lists from remote locations
- This policy setting allows you to control displaying or tracking items in Jump Lists from remote locations.
-
-The Start Menu and Taskbar display Jump Lists off of programs. These menus include files, folders, websites and other relevant items for that program. This helps users more easily reopen their most important documents and other tasks.
-
-If you enable this policy setting, the Start Menu and Taskbar only track the files that the user opens locally on this computer. Files that the user opens over the network from remote computers are not tracked or shown in the Jump Lists. Use this setting to reduce network traffic, particularly over slow network connections.
-
-If you disable or do not configure this policy setting, all files that the user opens appear in the menus, including files located remotely on another computer.
-
-Note: This setting does not prevent Windows from displaying remote files that the user has explicitly pinned to the Jump Lists. See the ""Do not allow pinning items in Jump Lists"" policy setting.
- Do not allow pinning programs to the Taskbar
- This policy setting allows you to control pinning programs to the Taskbar.
-
-If you enable this policy setting, users cannot change the programs currently pinned to the Taskbar. If any programs are already pinned to the Taskbar, these programs continue to show in the Taskbar. However, users cannot unpin these programs already pinned to the Taskbar, and they cannot pin new programs to the Taskbar.
-
-If you disable or do not configure this policy setting, users can change the programs currently pinned to the Taskbar.
- Do not allow pinning items in Jump Lists
- This policy setting allows you to control pinning items in Jump Lists.
-
-If you enable this policy setting, users cannot pin files, folders, websites, or other items to their Jump Lists in the Start Menu and Taskbar. Users also cannot unpin existing items pinned to their Jump Lists. Existing items already pinned to their Jump Lists will continue to show.
-
-If you disable or do not configure this policy setting, users can pin files, folders, websites, and other items to a program's Jump List so that the items is always present in this menu.
-
- Do not allow taskbars on more than one display
- This policy setting allows you to prevent taskbars from being displayed on more than one monitor.
-
-If you enable this policy setting, users are not able to show taskbars on more than one display. The multiple display section is not enabled in the taskbar properties dialog.
-
-If you disable or do not configure this policy setting, users can show taskbars on more than one display.
- Show Windows Store apps on the taskbar
-
-This policy setting allows users to see Windows Store apps on the taskbar.
-
-If you enable this policy setting, users will see Windows Store apps on the taskbar.
-
-If you disable this policy setting, users won’t see Windows Store apps on the taskbar.
-
-If you don’t configure this policy setting, the default setting for the user’s device will be used, and the user can choose to change it.
- Remove Notifications and Action Center
- This policy setting removes Notifications and Action Center from the notification area on the taskbar.
-
-The notification area is located at the far right end of the taskbar and includes icons for current notifications and the system clock.
-
-If this setting is enabled, Notifications and Action Center is not displayed in the notification area. The user will be able to read notifications when they appear, but they won’t be able to review any notifications they miss.
-
-If you disable or do not configure this policy setting, Notification and Security and Maintenance will be displayed on the taskbar.
-
-A reboot is required for this policy setting to take effect.
- Do not allow pinning Store app to the Taskbar
-
-This policy setting allows you to control pinning the Store app to the Taskbar.
-
-If you enable this policy setting, users cannot pin the Store app to the Taskbar. If the Store app is already pinned to the Taskbar, it will be removed from the Taskbar on next login.
-
-If you disable or do not configure this policy setting, users can pin the Store app to the Taskbar.
- Show additional calendar
- By default, the calendar is set according to the locale of the operating system, and users can show an additional calendar. For zh-CN and zh-SG locales, an additional calendar shows the lunar month and date and holiday names in Simplified Chinese (Lunar) by default. For zh-TW, zh-HK, and zh-MO locales, an additional calendar shows the lunar month and date and holiday names in Traditional Chinese (Lunar) by default.
-
-If you enable this policy setting, users can show an additional calendar in either Simplified Chinese (Lunar) or Traditional Chinese (Lunar), regardless of the locale.
-
-If you disable this policy setting, users cannot show an additional calendar, regardless of the locale.
-
-If you do not configure this policy setting, the calendar will be set according to the default logic.
- Simplified Chinese (Lunar)
- Traditional Chinese (Lunar)
- Chat
- Configures the Chat icon on the taskbar
- This policy setting allows you to configure the Chat icon on the taskbar.
-
-If you enable this policy setting and set it to Show, the Chat icon will be displayed on the taskbar by default. Users can show or hide it in Settings.
-
-If you enable this policy setting and set it to Hide, the Chat icon will be hidden by default. Users can show or hide it in Settings.
-
-If you enable this policy setting and set it to Disabled, the Chat icon will not be displayed, and users cannot show or hide it in Settings.
-
-If you disable or do not configure this policy setting, the Chat icon will be configured according to the defaults for your Windows edition.
- Show
- Hide
- Disabled
- Hide the TaskView button
- This policy setting allows you to hide the TaskView button.
-
-If you enable this policy setting, the TaskView button will be hidden and the Settings toggle will be disabled.
-
-
-
- Calendar:
-
-
- Configure the Chat icon setting
-
- State:
-
-
-
-
-
diff --git a/policy_templates/en-US/TenantRestrictions.adml b/policy_templates/en-US/TenantRestrictions.adml
deleted file mode 100644
index 75b388e..0000000
--- a/policy_templates/en-US/TenantRestrictions.adml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
- Tenant Restriction Policies
- Prototype policies for Tenant Restrictions v2
-
-
- Tenant Restrictions
- Cloud Policy Details
- This setting enables and configures the device-based tenant restrictions feature for Azure Active Directory.
-
-When you enable this setting, compliant applications will be prevented from accessing disallowed tenants, according to a policy set in your Azure AD tenant.
-
-Note: Creation of a policy in your home tenant is required, and additional security measures for managed devices are recommended for best protection. Refer to Azure AD Tenant Restrictions for more details.
-
-https://go.microsoft.com/fwlink/?linkid=2148762
-
-Before enabling firewall protection, ensure that a Windows Defender Application Control (WDAC) policy that correctly tags applications has been applied to the target devices. Enabling firewall protection without a corresponding WDAC policy will prevent all applications from reaching Microsoft endpoints. This firewall setting is not supported on all versions of Windows - see the following link for more information.
-For details about setting up WDAC with tenant restrictions, see https://go.microsoft.com/fwlink/?linkid=2155230
-
-
-
-
-
-
- Enable firewall protection of Microsoft endpoints
- Hostnames (optional):
- Subdomain Supported Hostnames (optional):
- IP Ranges (optional):
-
-
-
-
diff --git a/policy_templates/en-US/TerminalServer.adml b/policy_templates/en-US/TerminalServer.adml
deleted file mode 100644
index eb6879e..0000000
--- a/policy_templates/en-US/TerminalServer.adml
+++ /dev/null
@@ -1,1384 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Enable auto-subscription
- Controls the list of URLs that the user should be auto-subscribed to
- At least Windows 10 or Windows Server 2016
- At least Windows 8 or Windows RT
- At least Windows Server 2012
- At least Windows 8 Enterprise or Windows Server 2012
- Windows 7 or Windows Server 2008 R2 (and their subsequent Service Packs) only
- Windows Server 2008 R2, Windows Server 2008, Windows Server 2003, Windows 7, Windows Vista, and Windows XP
- At least Windows Server 2008 R2
- At least Windows 7
- At least Windows Server 2012 with RDSH role installed
- At least Windows 7 with Service Pack 1 or Windows Server 2008 R2 with Service Pack 1
- At least Windows Vista with Service Pack 1
- At least Windows 2000 Terminal Services
- At least Windows Server 2003
- At least Windows Server 2003 with Service Pack 1
- Windows Server 2003 with Service Pack 1 only
- At least Windows Server 2003 with Service Pack 2
- At least Windows XP
- At least Windows Server 2003, Enterprise Edition
- At least Windows XP and Windows Server 2003 only
- At least Windows Server 2008 or Windows 7
- Windows Server 2008 R2 only
- Windows 10 Version 1903, Windows 10 Version 1909, and Windows 10 Version 2004
- Remote Desktop Session Host
- Controls configuration of a Remote Desktop Session Host server
- RD Licensing
- Connections
- Controls connection settings on a Remote Desktop Session Host server
- Printer Redirection
- Controls printer configuration for Remote Desktop Services sessions
- Session Time Limits
- Controls time limits for Remote Desktop Services sessions
- Profiles
- Controls roaming profile and home directory settings for Remote Desktop Services sessions
- 15 bit
- 16 bit
- 24 bit
- 8 bit
- 32 bit
-
- This policy setting allows you to specify whether users can redirect the remote computer's audio and video output in a Remote Desktop Services session.
-Users can specify where to play the remote computer's audio output by configuring the remote audio settings on the Local Resources tab in Remote Desktop Connection (RDC). Users can choose to play the remote audio on the remote computer or on the local computer. Users can also choose to not play the audio. Video playback can be configured by using the videoplayback setting in a Remote Desktop Protocol (.rdp) file. By default, video playback is enabled.
-
-By default, audio and video playback redirection is not allowed when connecting to a computer running Windows Server 2008 R2, Windows Server 2008, or Windows Server 2003. Audio and video playback redirection is allowed by default when connecting to a computer running Windows 8, Windows Server 2012, Windows 7, Windows Vista, or Windows XP Professional.
-
-If you enable this policy setting, audio and video playback redirection is allowed.
-
-If you disable this policy setting, audio and video playback redirection is not allowed, even if audio playback redirection is specified in RDC, or video playback is specified in the .rdp file.
-
-If you do not configure this policy setting audio and video playback redirection is not specified at the Group Policy level.
-
- This policy setting allows you to specify whether users can record audio to the remote computer in a Remote Desktop Services session.
-Users can specify whether to record audio to the remote computer by configuring the remote audio settings on the Local Resources tab in Remote Desktop Connection (RDC). Users can record audio by using an audio input device on the local computer, such as a built-in microphone.
-
-By default, audio recording redirection is not allowed when connecting to a computer running Windows Server 2008 R2. Audio recording redirection is allowed by default when connecting to a computer running at least Windows 7, or Windows Server 2008 R2.
-
-If you enable this policy setting, audio recording redirection is allowed.
-
-If you disable this policy setting, audio recording redirection is not allowed, even if audio recording redirection is specified in RDC.
-
-If you do not configure this policy setting, Audio recording redirection is not specified at the Group Policy level.
-
- Limit audio playback quality
- This policy setting allows you to limit the audio playback quality for a Remote Desktop Services session. Limiting the quality of audio playback can improve connection performance, particularly over slow links.
-
-If you enable this policy setting, you must select one of the following: High, Medium, or Dynamic. If you select High, the audio will be sent without any compression and with minimum latency. This requires a large amount of bandwidth. If you select Medium, the audio will be sent with some compression and with minimum latency as determined by the codec that is being used. If you select Dynamic, the audio will be sent with a level of compression that is determined by the bandwidth of the remote connection.
-
-The audio playback quality that you specify on the remote computer by using this policy setting is the maximum quality that can be used for a Remote Desktop Services session, regardless of the audio playback quality configured on the client computer. For example, if the audio playback quality configured on the client computer is higher than the audio playback quality configured on the remote computer, the lower level of audio playback quality will be used.
-
-Audio playback quality can be configured on the client computer by using the audioqualitymode setting in a Remote Desktop Protocol (.rdp) file. By default, audio playback quality is set to Dynamic.
-
-If you disable or do not configure this policy setting, audio playback quality will be set to Dynamic.
- Dynamic
- Medium
- High
- Automatic reconnection
- Specifies whether to allow Remote Desktop Connection clients to automatically reconnect to sessions on an RD Session Host server if their network link is temporarily lost. By default, a maximum of twenty reconnection attempts are made at five second intervals.
-
-If the status is set to Enabled, automatic reconnection is attempted for all clients running Remote Desktop Connection whenever their network connection is lost.
-
-If the status is set to Disabled, automatic reconnection of clients is prohibited.
-
-If the status is set to Not Configured, automatic reconnection is not specified at the Group Policy level. However, users can configure automatic reconnection using the "Reconnect if connection is dropped" checkbox on the Experience tab in Remote Desktop Connection.
-
- Remote Desktop Connection Client
- Allow audio and video playback redirection
- Allow audio recording redirection
- Do not allow Clipboard redirection
- Do not allow COM port redirection
- Client Compatible
- Do not set default client printer to be default printer in a session
- This policy setting allows you to specify whether the client default printer is automatically set as the default printer in a session on an RD Session Host server.
-
-By default, Remote Desktop Services automatically designates the client default printer as the default printer in a session on an RD Session Host server. You can use this policy setting to override this behavior.
-
-If you enable this policy setting, the default printer is the printer specified on the remote computer.
-
-If you disable this policy setting, the RD Session Host server automatically maps the client default printer and sets it as the default printer upon connection.
-
-If you do not configure this policy setting, the default printer is not specified at the Group Policy level.
-
-
- Use Remote Desktop Easy Print printer driver first
- This policy setting allows you to specify whether the Remote Desktop Easy Print printer driver is used first to install all client printers.
-
-If you enable or do not configure this policy setting, the RD Session Host server first tries to use the Remote Desktop Easy Print printer driver to install all client printers. If for any reason the Remote Desktop Easy Print printer driver cannot be used, a printer driver on the RD Session Host server that matches the client printer is used. If the RD Session Host server does not have a printer driver that matches the client printer, the client printer is not available for the Remote Desktop session.
-
-If you disable this policy setting, the RD Session Host server tries to find a suitable printer driver to install the client printer. If the RD Session Host server does not have a printer driver that matches the client printer, the server tries to use the Remote Desktop Easy Print driver to install the client printer. If for any reason the Remote Desktop Easy Print printer driver cannot be used, the client printer is not available for the Remote Desktop Services session.
-
-Note: If the "Do not allow client printer redirection" policy setting is enabled, the "Use Remote Desktop Easy Print printer driver first" policy setting is ignored.
-
- Do not allow passwords to be saved
- Controls whether passwords can be saved on this computer from Remote Desktop Connection.
-
-If you enable this setting the password saving checkbox in Remote Desktop Connection will be disabled and users will no longer be able to save passwords. When a user opens an RDP file using Remote Desktop Connection and saves his settings, any password that previously existed in the RDP file will be deleted.
-
-If you disable this setting or leave it not configured, the user will be able to save passwords using Remote Desktop Connection.
- Controls whether a user can save passwords using Remote Desktop Connection.
-
-If you enable this setting the credential saving checkbox in Remote Desktop Connection will be disabled and users will no longer be able to save passwords. When a user opens an RDP file using Remote Desktop Connection and saves his settings, any password that previously existed in the RDP file will be deleted.
-
-If you disable this setting or leave it not configured, the user will be able to save passwords using Remote Desktop Connection
- This policy setting specifies whether to prevent the mapping of client drives in a Remote Desktop Services session (drive redirection).
-
-By default, an RD Session Host server maps client drives automatically upon connection. Mapped drives appear in the session folder tree in File Explorer or Computer in the format <driveletter> on <computername>. You can use this policy setting to override this behavior.
-
-If you enable this policy setting, client drive redirection is not allowed in Remote Desktop Services sessions, and Clipboard file copy redirection is not allowed on computers running Windows XP, Windows Server 2003, Windows Server 2012 (and later) or Windows 8 (and later).
-
-If you disable this policy setting, client drive redirection is always allowed. In addition, Clipboard file copy redirection is always allowed if Clipboard redirection is allowed.
-
-If you do not configure this policy setting, client drive redirection and Clipboard file copy redirection are not specified at the Group Policy level.
-
- Do not allow drive redirection
- Controls Remote Desktop Connection client settings
- Do not allow LPT port redirection
- Do not allow supported Plug and Play device redirection
- Do not allow video capture redirection
- Do not allow location redirection
- Do not allow client printer redirection
- This policy setting specifies whether to prevent the sharing of Clipboard contents (Clipboard redirection) between a remote computer and a client computer during a Remote Desktop Services session.
-
-You can use this setting to prevent users from redirecting Clipboard data to and from the remote computer and the local computer. By default, Remote Desktop Services allows Clipboard redirection.
-
-If you enable this policy setting, users cannot redirect Clipboard data.
-
-If you disable this policy setting, Remote Desktop Services always allows Clipboard redirection.
-
-If you do not configure this policy setting, Clipboard redirection is not specified at the Group Policy level.
-
- This policy setting allows you to specify the maximum color resolution (color depth) for Remote Desktop Services connections.
-
-You can use this policy setting to set a limit on the color depth of any connection that uses RDP. Limiting the color depth can improve connection performance, particularly over slow links, and reduce server load.
-
-If you enable this policy setting, the color depth that you specify is the maximum color depth allowed for a user's RDP connection. The actual color depth for the connection is determined by the color support available on the client computer. If you select Client Compatible, the highest color depth supported by the client will be used.
-
-If you disable or do not configure this policy setting, the color depth for connections is not specified at the Group Policy level.
-
-Note:
-1. Setting the color depth to 24 bits is only supported on Windows Server 2003 and Windows XP Professional.
-2. The value specified in this policy setting is not applied to connections from client computers that are using at least Remote Desktop Protocol 8.0 (computers running at least Windows 8 or Windows Server 2012). The 32-bit color depth format is always used for these connections.
-3. For connections from client computers that are using Remote Desktop Protocol 7.1 or earlier versions that are connecting to computers running at least Windows 8 or Windows Server 2012, the minimum of the following values is used as the color depth format:
-a. Value specified by this policy setting
-b. Maximum color depth supported by the client
-c. Value requested by the client
-
-If the client does not support at least 16 bits, the connection is terminated.
-
- Limit maximum color depth
- Controls Remote Desktop Services configuration and properties of client sessions for individual computers or groups of computers.
- This policy setting specifies whether to prevent the redirection of data to client COM ports from the remote computer in a Remote Desktop Services session.
-
-You can use this setting to prevent users from redirecting data to COM port peripherals or mapping local COM ports while they are logged on to a Remote Desktop Services session. By default, Remote Desktop Services allows this COM port redirection.
-
-If you enable this policy setting, users cannot redirect server data to the local COM port.
-
-If you disable this policy setting, Remote Desktop Services always allows COM port redirection.
-
-If you do not configure this policy setting, COM port redirection is not specified at the Group Policy level.
-
-
- This policy setting lets you control the redirection of supported Plug and Play and RemoteFX USB devices, such as Windows Portable Devices, to the remote computer in a Remote Desktop Services session.
-
-By default, Remote Desktop Services does not allow redirection of supported Plug and Play and RemoteFX USB devices.
-
-If you disable this policy setting, users can redirect their supported Plug and Play devices to the remote computer. Users can use the More option on the Local Resources tab of Remote Desktop Connection to choose the supported Plug and Play devices to redirect to the remote computer.
-
-If you enable this policy setting, users cannot redirect their supported Plug and Play devices to the remote computer.If you do not configure this policy setting, users can redirect their supported Plug and Play devices to the remote computer only if it is running Windows Server 2012 R2 and earlier versions.
-
-Note: You can disable redirection of specific types of supported Plug and Play devices by using Computer Configuration\Administrative Templates\System\Device Installation\Device Installation Restrictions policy settings.
-
-
- This policy setting lets you control the redirection of video capture devices to the remote computer in a Remote Desktop Services session.
-
-By default, Remote Desktop Services allows redirection of video capture devices.
-
-If you enable this policy setting, users cannot redirect their video capture devices to the remote computer.
-
-If you disable or do not configure this policy setting, users can redirect their video capture devices to the remote computer. Users can use the More option on the Local Resources tab of Remote Desktop Connection to choose the video capture devices to redirect to the remote computer.
-
-
- This policy setting lets you control the redirection of location data to the remote computer in a Remote Desktop Services session.
-
-By default, Remote Desktop Services allows redirection of location data.
-
-If you enable this policy setting, users cannot redirect their location data to the remote computer.
-
-If you disable or do not configure this policy setting, users can redirect their location data to the remote computer.
-
-
- This policy setting allows you to limit the number of monitors that a user can use to display a Remote Desktop Services session. Limiting the number of monitors to display a Remote Desktop Services session can improve connection performance, particularly over slow links, and reduce server load.
-
-If you enable this policy setting, you can specify the number of monitors that can be used to display a Remote Desktop Services session. You can specify a number from 1 to 16.
-
-If you disable or do not configure this policy setting, the number of monitors that can be used to display a Remote Desktop Services session is not specified at the Group Policy level.
-
- Limit number of monitors
- Allow users to connect remotely by using Remote Desktop Services
- This policy setting allows you to configure remote access to computers by using Remote Desktop Services.
-
-If you enable this policy setting, users who are members of the Remote Desktop Users group on the target computer can connect remotely to the target computer by using Remote Desktop Services.
-
-If you disable this policy setting, users cannot connect remotely to the target computer by using Remote Desktop Services. The target computer will maintain any current connections, but will not accept any new incoming connections.
-
-If you do not configure this policy setting, Remote Desktop Services uses the Remote Desktop setting on the target computer to determine whether the remote connection is allowed. This setting is found on the Remote tab in the System properties sheet. By default, remote connections are not allowed.
-
-Note: You can limit which clients are able to connect remotely by using Remote Desktop Services by configuring the policy setting at Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Security\Require user authentication for remote connections by using Network Level Authentication.
-
-You can limit the number of users who can connect simultaneously by configuring the policy setting at Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Connections\Limit number of connections, or by configuring the policy setting Maximum Connections by using the Remote Desktop Session Host WMI Provider.
-
- Limit maximum display resolution
- This policy setting allows you to specify the maximum display resolution that can be used by each monitor used to display a Remote Desktop Services session. Limiting the resolution used to display a remote session can improve connection performance, particularly over slow links, and reduce server load.
-
-If you enable this policy setting, you must specify a resolution width and height. The resolution specified will be the maximum resolution that can be used by each monitor used to display a Remote Desktop Services session.
-
-If you disable or do not configure this policy setting, the maximum resolution that can be used by each monitor to display a Remote Desktop Services session will be determined by the values specified on the Display Settings tab in the Remote Desktop Session Host Configuration tool.
-
- Enforce Removal of Remote Desktop Wallpaper
- Specifies whether desktop wallpaper is displayed to remote clients connecting via Remote Desktop Services.
-
-You can use this setting to enforce the removal of wallpaper during a Remote Desktop Services session. By default, Windows XP Professional displays wallpaper to remote clients connecting through Remote Desktop, depending on the client configuration (see the Experience tab in the Remote Desktop Connection options for more information). Servers running Windows Server 2003 do not display wallpaper by default to Remote Desktop Services sessions.
-
-If the status is set to Enabled, wallpaper never appears in a Remote Desktop Services session.
-
-If the status is set to Disabled, wallpaper might appear in a Remote Desktop Services session, depending on the client configuration.
-
-If the status is set to Not Configured, the default behavior applies.
- G:
- H:
- I:
- J:
- K:
- L:
- M:
- N:
- O:
- P:
- Q:
- R:
- S:
- T:
- U:
- V:
- W:
- X:
- Y:
- Z:
- Security
- Controls security settings on an RD Session Host server
- Client Compatible
- Specifies whether to require the use of a specific encryption level to secure communications between client computers and RD Session Host servers during Remote Desktop Protocol (RDP) connections. This policy only applies when you are using native RDP encryption. However, native RDP encryption (as opposed to SSL encryption) is not recommended. This policy does not apply to SSL encryption.
-
-If you enable this policy setting, all communications between clients and RD Session Host servers during remote connections must use the encryption method specified in this setting. By default, the encryption level is set to High. The following encryption methods are available:
-
-* High: The High setting encrypts data sent from the client to the server and from the server to the client by using strong 128-bit encryption. Use this encryption level in environments that contain only 128-bit clients (for example, clients that run Remote Desktop Connection). Clients that do not support this encryption level cannot connect to RD Session Host servers.
-
-* Client Compatible: The Client Compatible setting encrypts data sent between the client and the server at the maximum key strength supported by the client. Use this encryption level in environments that include clients that do not support 128-bit encryption.
-
-* Low: The Low setting encrypts only data sent from the client to the server by using 56-bit encryption.
-
-If you disable or do not configure this setting, the encryption level to be used for remote connections to RD Session Host servers is not enforced through Group Policy.
-
-Important
-
-FIPS compliance can be configured through the System cryptography. Use FIPS compliant algorithms for encryption, hashing, and signing settings in Group Policy (under Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options.) The FIPS compliant setting encrypts and decrypts data sent from the client to the server and from the server to the client, with the Federal Information Processing Standard (FIPS) 140 encryption algorithms, by using Microsoft cryptographic modules. Use this encryption level when communications between clients and RD Session Host servers requires the highest level of encryption.
-
- High Level
- Low Level
- Set client connection encryption level
- Do nothing if one is not found.
- Default to PCL if one is not found.
- Show both PCL and PS if one is not found.
- Default to PS if one is not found.
- Specify RD Session Host server fallback printer driver behavior
- This policy setting allows you to specify the RD Session Host server fallback printer driver behavior.
-
-By default, the RD Session Host server fallback printer driver is disabled. If the RD Session Host server does not have a printer driver that matches the client's printer, no printer will be available for the Remote Desktop Services session.
-
-If you enable this policy setting, the fallback printer driver is enabled, and the default behavior is for the RD Session Host server to find a suitable printer driver. If one is not found, the client's printer is not available. You can choose to change this default behavior. The available options are:
-
-"Do nothing if one is not found" - If there is a printer driver mismatch, the server will attempt to find a suitable driver. If one is not found, the client's printer is not available. This is the default behavior.
-
-"Default to PCL if one is not found" - If no suitable printer driver can be found, default to the Printer Control Language (PCL) fallback printer driver.
-
-"Default to PS if one is not found" - If no suitable printer driver can be found, default to the PostScript (PS) fallback printer driver.
-
-"Show both PCL and PS if one is not found" - If no suitable driver can be found, show both PS and PCL-based fallback printer drivers.
-
-If you disable this policy setting, the RD Session Host server fallback driver is disabled and the RD Session Host server will not attempt to use the fallback printer driver.
-
-If you do not configure this policy setting, the fallback printer driver behavior is off by default.
-
-Note: If the "Do not allow client printer redirection" setting is enabled, this policy setting is ignored and the fallback printer driver is disabled.
- Deny logoff of an administrator logged in to the console session
- This policy setting determines whether an administrator attempting to connect remotely to the console of a server can log off an administrator currently logged on to the console.
-
-This policy is useful when the currently connected administrator does not want to be logged off by another administrator. If the connected administrator is logged off, any data not previously saved is lost.
-
-If you enable this policy setting, logging off the connected administrator is not allowed.
-
-If you disable or do not configure this policy setting, logging off the connected administrator is allowed.
-
-Note: The console session is also known as Session 0. Console access can be obtained by using the /console switch from Remote Desktop Connection in the computer field name or from the command line.
- RD Gateway
- Controls configuration to access an RD Gateway server
- Ask for credentials, use Basic protocol
- Use locally logged-on credentials
- Ask for credentials, use NTLM protocol
- Ask for credentials, use Negotiate protocol
- Set RD Gateway authentication method
- Specifies the authentication method that clients must use when attempting to connect to an RD Session Host server through an RD Gateway server. You can enforce this policy setting or you can allow users to overwrite this policy setting. By default, when you enable this policy setting, it is enforced. When this policy setting is enforced, users cannot override this setting, even if they select the "Use these RD Gateway server settings" option on the client.
-
-To allow users to overwrite this policy setting, select the "Allow users to change this setting" check box. When you do this, users can specify an alternate authentication method by configuring settings on the client, using an RDP file, or using an HTML script. If users do not specify an alternate authentication method, the authentication method that you specify in this policy setting is used by default.
-
-If you disable or do not configure this policy setting, the authentication method that is specified by the user is used, if one is specified. If an authentication method is not specified, the Negotiate protocol that is enabled on the client or a smart card can be used for authentication.
- Enable connection through RD Gateway
- If you enable this policy setting, when Remote Desktop Connection cannot connect directly to a remote computer (an RD Session Host server or a computer with Remote Desktop enabled), the clients will attempt to connect to the remote computer through an RD Gateway server. In this case, the clients will attempt to connect to the RD Gateway server that is specified in the "Set RD Gateway server address" policy setting.
-
-You can enforce this policy setting or you can allow users to overwrite this setting. By default, when you enable this policy setting, it is enforced. When this policy setting is enforced, users cannot override this setting, even if they select the "Use these RD Gateway server settings" option on the client.
-
-Note: To enforce this policy setting, you must also specify the address of the RD Gateway server by using the "Set RD Gateway server address" policy setting, or client connection attempts to any remote computer will fail, if the client cannot connect directly to the remote computer. To enhance security, it is also highly recommended that you specify the authentication method by using the "Set RD Gateway authentication method" policy setting. If you do not specify an authentication method by using this policy setting, either the NTLM protocol that is enabled on the client or a smart card can be used.
-
-To allow users to overwrite this policy setting, select the "Allow users to change this setting" check box. When you do this, users on the client can choose not to connect through the RD Gateway server by selecting the "Do not use an RD Gateway server" option. Users can specify a connection method by configuring settings on the client, using an RDP file, or using an HTML script. If users do not specify a connection method, the connection method that you specify in this policy setting is used by default.
-
-If you disable or do not configure this policy setting, clients will not use the RD Gateway server address that is specified in the "Set RD Gateway server address" policy setting. If an RD Gateway server is specified by the user, a client connection attempt will be made through that RD Gateway server.
-
- Set RD Gateway server address
- Specifies the address of the RD Gateway server that clients must use when attempting to connect to an RD Session Host server. You can enforce this policy setting or you can allow users to overwrite this policy setting. By default, when you enable this policy setting, it is enforced. When this policy setting is enforced, users cannot override this setting, even if they select the "Use these RD Gateway server settings" option on the client.
-
-Note: It is highly recommended that you also specify the authentication method by using the "Set RD Gateway authentication method" policy setting. If you do not specify an authentication method by using this setting, either the NTLM protocol that is enabled on the client or a smart card can be used.
-
-To allow users to overwrite the "Set RD Gateway server address" policy setting and connect to another RD Gateway server, you must select the "Allow users to change this setting" check box and users will be allowed to specify an alternate RD Gateway server. Users can specify an alternative RD Gateway server by configuring settings on the client, using an RDP file, or using an HTML script. If users do not specify an alternate RD Gateway server, the server that you specify in this policy setting is used by default.
-
-Note: If you disable or do not configure this policy setting, but enable the "Enable connections through RD Gateway" policy setting, client connection attempts to any remote computer will fail, if the client cannot connect directly to the remote computer. If an RD Gateway server is specified by the user, a client connection attempt will be made through that RD Gateway server.
- Use smart-card
- Remote Desktop Services
- Join RD Connection Broker
- This policy setting allows you to specify whether the RD Session Host server should join a farm in RD Connection Broker. RD Connection Broker tracks user sessions and allows a user to reconnect to their existing session in a load-balanced RD Session Host server farm. To participate in RD Connection Broker, the Remote Desktop Session Host role service must be installed on the server.
-
-If the policy setting is enabled, the RD Session Host server joins the farm that is specified in the RD Connection Broker farm name policy setting. The farm exists on the RD Connection Broker server that is specified in the Configure RD Connection Broker server name policy setting.
-
-If you disable this policy setting, the server does not join a farm in RD Connection Broker, and user session tracking is not performed. If the policy setting is disabled, you cannot use either the Remote Desktop Session Host Configuration tool or the Remote Desktop Services WMI Provider to join the server to RD Connection Broker.
-
-If the policy setting is not configured, the policy setting is not specified at the Group Policy level.
-
-Notes:
-
- 1. If you enable this policy setting, you must also enable the Configure RD Connection Broker farm name and Configure RD Connection Broker server name policy settings.
-
- 2. For Windows Server 2008, this policy setting is supported on at least Windows Server 2008 Standard.
-
- Configure keep-alive connection interval
- This policy setting allows you to enter a keep-alive interval to ensure that the session state on the RD Session Host server is consistent with the client state.
-
-After an RD Session Host server client loses the connection to an RD Session Host server, the session on the RD Session Host server might remain active instead of changing to a disconnected state, even if the client is physically disconnected from the RD Session Host server. If the client logs on to the same RD Session Host server again, a new session might be established (if the RD Session Host server is configured to allow multiple sessions), and the original session might still be active.
-
-If you enable this policy setting, you must enter a keep-alive interval. The keep-alive interval determines how often, in minutes, the server checks the session state. The range of values you can enter is 1 to 999,999.
-
-If you disable or do not configure this policy setting, a keep-alive interval is not set and the server will not check the session state.
- Licensing
- Controls configuration of RD Licensing settings on an RD Session Host server
- License server security group
- This policy setting allows you to specify the RD Session Host servers to which a Remote Desktop license server will offer Remote Desktop Services client access licenses (RDS CALs).
-
-You can use this policy setting to control which RD Session Host servers are issued RDS CALs by the Remote Desktop license server. By default, a license server issues an RDS CAL to any RD Session Host server that requests one.
-
-If you enable this policy setting and this policy setting is applied to a Remote Desktop license server, the license server will only respond to RDS CAL requests from RD Session Host servers whose computer accounts are a member of the RDS Endpoint Servers group on the license server.
-
-By default, the RDS Endpoint Servers group is empty.
-
-If you disable or do not configure this policy setting, the Remote Desktop license server issues an RDS CAL to any RD Session Host server that requests one. The RDS Endpoint Servers group is not deleted or changed in any way by disabling or not configuring this policy setting.
-
-Note: You should only enable this policy setting when the license server is a member of a domain. You can only add computer accounts for RD Session Host servers to the RDS Endpoint Servers group when the license server is a member of a domain.
- Use the specified Remote Desktop license servers
- Controls configuration of a Remote Desktop license server
- This policy setting allows you to specify the order in which an RD Session Host server attempts to locate Remote Desktop license servers.
-
-If you enable this policy setting, an RD Session Host server first attempts to locate the specified license servers. If the specified license servers cannot be located, the RD Session Host server will attempt automatic license server discovery. In the automatic license server discovery process, an RD Session Host server in a Windows Server-based domain attempts to contact a license server in the following order:
-
- 1. Remote Desktop license servers that are published in Active Directory Domain Services.
-
- 2. Remote Desktop license servers that are installed on domain controllers in the same domain as the RD Session Host server.
-
-If you disable or do not configure this policy setting, the RD Session Host server does not specify a license server at the Group Policy level.
-
- Hide notifications about RD Licensing problems that affect the RD Session Host server
- This policy setting determines whether notifications are displayed on an RD Session Host server when there are problems with RD Licensing that affect the RD Session Host server.
-
-By default, notifications are displayed on an RD Session Host server after you log on as a local administrator, if there are problems with RD Licensing that affect the RD Session Host server. If applicable, a notification will also be displayed that notes the number of days until the licensing grace period for the RD Session Host server will expire.
-
-If you enable this policy setting, these notifications will not be displayed on the RD Session Host server.
-
-If you disable or do not configure this policy setting, these notifications will be displayed on the RD Session Host server after you log on as a local administrator.
- Set the Remote Desktop licensing mode
-
- This policy setting allows you to specify the type of Remote Desktop Services client access license (RDS CAL) that is required to connect to this RD Session Host server.
-
- You can use this policy setting to select one of two licensing modes: Per User or Per Device.
-
- Per User licensing mode requires that each user account connecting to this RD Session Host server have an RDS Per User CAL issued from an RD Licensing server.
-
- Per Device licensing mode requires that each device connecting to this RD Session Host server have an RDS Per Device CAL issued from an RD Licensing server.
-
- If you enable this policy setting, the Remote Desktop licensing mode that you specify is honored by the Remote Desktop license server and RD Session Host.
-
- If you disable or do not configure this policy setting, the licensing mode is not specified at the Group Policy level.
-
- Note: AAD Per User mode is deprecated on Windows 11 and above.
-
- Per Device
- Per User
- AAD Per User
- This policy setting specifies whether to prevent the redirection of data to client LPT ports during a Remote Desktop Services session.
-
-You can use this setting to prevent users from mapping local LPT ports and redirecting data from the remote computer to local LPT port peripherals. By default, Remote Desktop Services allows LPT port redirection.
-
-If you enable this policy setting, users in a Remote Desktop Services session cannot redirect server data to the local LPT port.
-
-If you disable this policy setting, LPT port redirection is always allowed.
-
-If you do not configure this policy setting, LPT port redirection is not specified at the Group Policy level.
-
- Specifies whether Remote Desktop Services limits the number of simultaneous connections to the server.
-
-You can use this setting to restrict the number of Remote Desktop Services sessions that can be active on a server. If this number is exceeded, addtional users who try to connect receive an error message telling them that the server is busy and to try again later. Restricting the number of sessions improves performance because fewer sessions are demanding system resources. By default, RD Session Host servers allow an unlimited number of Remote Desktop Services sessions, and Remote Desktop for Administration allows two Remote Desktop Services sessions.
-
-To use this setting, enter the number of connections you want to specify as the maximum for the server. To specify an unlimited number of connections, type 999999.
-
-If the status is set to Enabled, the maximum number of connections is limited to the specified number consistent with the version of Windows and the mode of Remote Desktop Services running on the server.
-
-If the status is set to Disabled or Not Configured, limits to the number of connections are not enforced at the Group Policy level.
-
-Note: This setting is designed to be used on RD Session Host servers (that is, on servers running Windows with Remote Desktop Session Host role service installed).
- Limit number of connections
- Remove "Disconnect" option from Shut Down dialog
- This policy setting allows you to remove the "Disconnect" option from the Shut Down Windows dialog box in Remote Desktop Services sessions.
-
-You can use this policy setting to prevent users from using this familiar method to disconnect their client from an RD Session Host server.
-
-If you enable this policy setting, "Disconnect" does not appear as an option in the drop-down list in the Shut Down Windows dialog box.
-
-If you disable or do not configure this policy setting, "Disconnect" is not removed from the list in the Shut Down Windows dialog box.
-
-Note: This policy setting affects only the Shut Down Windows dialog box. It does not prevent users from using other methods to disconnect from a Remote Desktop Services session. This policy setting also does not prevent disconnected sessions at the server. You can control how long a disconnected session remains active on the server by configuring the "Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\RD Session Host\Session Time Limits\Set time limit for disconnected sessions" policy setting.
- Remove Windows Security item from Start menu
- Specifies whether to remove the Windows Security item from the Settings menu on Remote Desktop clients. You can use this setting to prevent inexperienced users from logging off from Remote Desktop Services inadvertently.
-
-If the status is set to Enabled, Windows Security does not appear in Settings on the Start menu. As a result, users must type a security attention sequence, such as CTRL+ALT+END, to open the Windows Security dialog box on the client computer.
-
-If the status is set to Disabled or Not Configured, Windows Security remains in the Settings menu.
- On the Local machine
- On the Network
- Always prompt for password upon connection
- Prevent license upgrade
- This policy setting allows you to specify which version of Remote Desktop Services client access license (RDS CAL) a Remote Desktop Services license server will issue to clients connecting to RD Session Host servers running other Windows-based operating systems.
-
-A license server attempts to provide the most appropriate RDS or TS CAL for a connection. For example, a Windows Server 2008 license server will try to issue a Windows Server 2008 TS CAL for clients connecting to a terminal server running Windows Server 2008, and will try to issue a Windows Server 2003 TS CAL for clients connecting to a terminal server running Windows Server 2003.
-
-By default, if the most appropriate RDS CAL is not available for a connection, a Windows Server 2008 license server will issue a Windows Server 2008 TS CAL, if available, to the following:
-
-* A client connecting to a Windows Server 2003 terminal server
-* A client connecting to a Windows 2000 terminal server
-
-If you enable this policy setting, the license server will only issue a temporary RDS CAL to the client if an appropriate RDS CAL for the RD Session Host server is not available. If the client has already been issued a temporary RDS CAL and the temporary RDS CAL has expired, the client will not be able to connect to the RD Session Host server unless the RD Licensing grace period for the RD Session Host server has not expired.
-
-If you disable or do not configure this policy setting, the license server will exhibit the default behavior noted earlier.
- This policy setting allows you to specify whether to prevent the mapping of client printers in Remote Desktop Services sessions.
-
-You can use this policy setting to prevent users from redirecting print jobs from the remote computer to a printer attached to their local (client) computer. By default, Remote Desktop Services allows this client printer mapping.
-
-If you enable this policy setting, users cannot redirect print jobs from the remote computer to a local client printer in Remote Desktop Services sessions.
-
-If you disable this policy setting, users can redirect print jobs with client printer mapping.
-
-If you do not configure this policy setting, client printer mapping is not specified at the Group Policy level.
-
- This policy setting specifies whether Remote Desktop Services always prompts the client for a password upon connection.
-
-You can use this setting to enforce a password prompt for users logging on to Remote Desktop Services, even if they already provided the password in the Remote Desktop Connection client.
-
-By default, Remote Desktop Services allows users to automatically log on by entering a password in the Remote Desktop Connection client.
-
-If you enable this policy setting, users cannot automatically log on to Remote Desktop Services by supplying their passwords in the Remote Desktop Connection client. They are prompted for a password to log on.
-
-If you disable this policy setting, users can always log on to Remote Desktop Services automatically by supplying their passwords in the Remote Desktop Connection client.
-
-If you do not configure this policy setting, automatic logon is not specified at the Group Policy level.
-
- Device and Resource Redirection
- Controls access to devices and resources on a client computer in Remote Desktop Services sessions
- Set rules for remote control of Remote Desktop Services user sessions
- No remote control allowed
- Full Control with user's permission
- Full Control without user's permission
- View Session with user's permission
- View Session without user's permission
- If you enable this policy setting, administrators can interact with a user's Remote Desktop Services session based on the option selected. Select the desired level of control and permission from the options list:
-
-1. No remote control allowed: Disallows an administrator to use remote control or view a remote user session.
-2. Full Control with user's permission: Allows the administrator to interact with the session, with the user's consent.
-3. Full Control without user's permission: Allows the administrator to interact with the session, without the user's consent.
-4. View Session with user's permission: Allows the administrator to watch the session of a remote user with the user's consent.
-5. View Session without user's permission: Allows the administrator to watch the session of a remote user without the user's consent.
-
-If you disable this policy setting, administrators can interact with a user's Remote Desktop Services session, with the user's consent.
- Require secure RPC communication
- Specifies whether a Remote Desktop Session Host server requires secure RPC communication with all clients or allows unsecured communication.
-
-You can use this setting to strengthen the security of RPC communication with clients by allowing only authenticated and encrypted requests.
-
-If the status is set to Enabled, Remote Desktop Services accepts requests from RPC clients that support secure requests, and does not allow unsecured communication with untrusted clients.
-
-If the status is set to Disabled, Remote Desktop Services always requests security for all RPC traffic. However, unsecured communication is allowed for RPC clients that do not respond to the request.
-
-If the status is set to Not Configured, unsecured communication is allowed.
-
-Note: The RPC interface is used for administering and configuring Remote Desktop Services.
- Configure RD Connection Broker farm name
- This policy setting allows you to specify the name of a farm to join in RD Connection Broker. RD Connection Broker uses the farm name to determine which RD Session Host servers are in the same RD Session Host server farm. Therefore, you must use the same farm name for all RD Session Host servers in the same load-balanced farm. The farm name does not have to correspond to a name in Active Directory Domain Services.
-
-If you specify a new farm name, a new farm is created in RD Connection Broker. If you specify an existing farm name, the server joins that farm in RD Connection Broker.
-
-If you enable this policy setting, you must specify the name of a farm in RD Connection Broker.
-
-If you disable or do not configure this policy setting, the farm name is not specified at the Group Policy level.
-
-Notes:
-
- 1. This policy setting is not effective unless both the Join RD Connection Broker and the Configure RD Connection Broker server name policy settings are enabled and configured by using Group Policy.
-
- 2. For Windows Server 2008, this policy setting is supported on at least Windows Server 2008 Standard.
-
- Use IP Address Redirection
- This policy setting allows you to specify the redirection method to use when a client device reconnects to an existing Remote Desktop Services session in a load-balanced RD Session Host server farm. This setting applies to an RD Session Host server that is configured to use RD Connection Broker and not to the RD Connection Broker server.
-
-If you enable this policy setting, a Remote Desktop Services client queries the RD Connection Broker server and is redirected to their existing session by using the IP address of the RD Session Host server where their session exists. To use this redirection method, client computers must be able to connect directly by IP address to RD Session Host servers in the farm.
-
-If you disable this policy setting, the IP address of the RD Session Host server is not sent to the client. Instead, the IP address is embedded in a token. When a client reconnects to the load balancer, the routing token is used to redirect the client to their existing session on the correct RD Session Host server in the farm. Only disable this setting when your network load-balancing solution supports the use of RD Connection Broker routing tokens and you do not want clients to directly connect by IP address to RD Session Host servers in the load-balanced farm.
-
-If you do not configure this policy setting, the Use IP address redirection policy setting is not enforced at the group Group policy Policy level and the default will be used. This setting is enabled by default.
-
-Notes:
-
- 1. For Windows Server 2008, this policy setting is supported on at least Windows Server 2008 Standard.
-
- Configure RD Connection Broker server name
- This policy setting allows you to specify the RD Connection Broker server that the RD Session Host server uses to track and redirect user sessions for a load-balanced RD Session Host server farm. The specified server must be running the Remote Desktop Connection Broker service. All RD Session Host servers in a load-balanced farm should use the same RD Connection Broker server.
-
-If you enable this policy setting, you must specify the RD Connection Broker server by using its fully qualified domain name (FQDN). In Windows Server 2012, for a high availability setup with multiple RD Connection Broker servers, you must provide a semi-colon separated list of the FQDNs of all the RD Connection Broker servers.
-
-If you disable or do not configure this policy setting, the policy setting is not specified at the Group Policy level.
-
-Notes:
-
- 1. For Windows Server 2008, this policy setting is supported on at least Windows Server 2008 Standard.
-
- 2. This policy setting is not effective unless the Join RD Connection Broker policy setting is enabled.
-
- 3. To be an active member of an RD Session Host server farm, the computer account for each RD Session Host server in the farm must be a member of one of the following local groups on the RD Connection Broker server: Session Directory Computers, Session Broker Computers, or RDS Endpoint Servers.
-
-
- RD Connection Broker
- Controls configuration of an RD Session Host server that is a member of a load-balanced RD Session Host server farm
- This policy setting specifies whether to require the use of a specific security layer to secure communications between clients and RD Session Host servers during Remote Desktop Protocol (RDP) connections.
-
-If you enable this policy setting, all communications between clients and RD Session Host servers during remote connections must use the security method specified in this setting. The following security methods are available:
-
-* Negotiate: The Negotiate method enforces the most secure method that is supported by the client. If Transport Layer Security (TLS) version 1.0 is supported, it is used to authenticate the RD Session Host server. If TLS is not supported, native Remote Desktop Protocol (RDP) encryption is used to secure communications, but the RD Session Host server is not authenticated. Native RDP encryption (as opposed to SSL encryption) is not recommended.
-
-* RDP: The RDP method uses native RDP encryption to secure communications between the client and RD Session Host server. If you select this setting, the RD Session Host server is not authenticated. Native RDP encryption (as opposed to SSL encryption) is not recommended.
-
-* SSL (TLS 1.0): The SSL method requires the use of TLS 1.0 to authenticate the RD Session Host server. If TLS is not supported, the connection fails. This is the recommended setting for this policy.
-
-If you disable or do not configure this policy setting, the security method to be used for remote connections to RD Session Host servers is not specified at the Group Policy level.
-
- Negotiate
- Require use of specific security layer for remote (RDP) connections
- RDP
- SSL
- End session when time limits are reached
- This policy setting specifies whether to end a Remote Desktop Services session that has timed out instead of disconnecting it.
-
-You can use this setting to direct Remote Desktop Services to end a session (that is, the user is logged off and the session is deleted from the server) after time limits for active or idle sessions are reached. By default, Remote Desktop Services disconnects sessions that reach their time limits.
-
-Time limits are set locally by the server administrator or by using Group Policy. See the policy settings Set time limit for active Remote Desktop Services sessions and Set time limit for active but idle Remote Desktop Services sessions policy settings.
-
-If you enable this policy setting, Remote Desktop Services ends any session that reaches its time-out limit.
-
-If you disable this policy setting, Remote Desktop Services always disconnects a timed-out session, even if specified otherwise by the server administrator.
-
-If you do not configure this policy setting, Remote Desktop Services disconnects a timed-out session, unless specified otherwise in local settings.
-
-Note: This policy setting only applies to time-out limits that are explicitly set by the administrator. This policy setting does not apply to time-out events that occur due to connectivity or network conditions. This setting appears in both Computer Configuration and User Configuration. If both settings are configured, the Computer Configuration setting takes precedence.
-
- Remote Session Environment
- Controls configuration of the user interface in Remote Desktop Services sessions
- RemoteFX for Windows Server 2008 R2
- Configures all policies that apply to RemoteFX for Windows Server 2008 R2 with Service Pack 1.
- Set time limit for disconnected sessions
- This policy setting allows you to configure a time limit for disconnected Remote Desktop Services sessions.
-
-You can use this policy setting to specify the maximum amount of time that a disconnected session remains active on the server. By default, Remote Desktop Services allows users to disconnect from a Remote Desktop Services session without logging off and ending the session.
-
-When a session is in a disconnected state, running programs are kept active even though the user is no longer actively connected. By default, these disconnected sessions are maintained for an unlimited time on the server.
-
-If you enable this policy setting, disconnected sessions are deleted from the server after the specified amount of time. To enforce the default behavior that disconnected sessions are maintained for an unlimited time, select Never. If you have a console session, disconnected session time limits do not apply.
-
-
-If you disable or do not configure this policy setting, this policy setting is not specified at the Group Policy level. Be y default, Remote Desktop Services disconnected sessions are maintained for an unlimited amount of time.
-
-Note: This policy setting appears in both Computer Configuration and User Configuration. If both policy settings are configured, the Computer Configuration policy setting takes precedence.
-
- Set time limit for active but idle Remote Desktop Services sessions
- This policy setting allows you to specify the maximum amount of time that an active Remote Desktop Services session can be idle (without user input) before it is automatically disconnected.
-
-If you enable this policy setting, you must select the desired time limit in the Idle session limit list. Remote Desktop Services will automatically disconnect active but idle sessions after the specified amount of time. The user receives a warning two minutes before the session disconnects, which allows the user to press a key or move the mouse to keep the session active. If you have a console session, idle session time limits do not apply.
-
-If you disable or do not configure this policy setting, the time limit is not specified at the Group Policy level. By default, Remote Desktop Services allows sessions to remain active but idle for an unlimited amount of time.
-
-If you want Remote Desktop Services to end instead of disconnect a session when the time limit is reached, you can configure the policy setting Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits\End session when time limits are reached.
-
-Note: This policy setting appears in both Computer Configuration and User Configuration. If both policy settings are configured, the Computer Configuration policy setting takes precedence.
-
- Set time limit for active Remote Desktop Services sessions
- This policy setting allows you to specify the maximum amount of time that a Remote Desktop Services session can be active before it is automatically disconnected.
-
-If you enable this policy setting, you must select the desired time limit in the Active session limit list. Remote Desktop Services will automatically disconnect active sessions after the specified amount of time. The user receives a warning two minutes before the Remote Desktop Services session disconnects, which allows the user to save open files and close programs. If you have a console session, active session time limits do not apply.
-
-If you disable or do not configure this policy setting, this policy setting is not specified at the Group Policy level. By default, Remote Desktop Services allows sessions to remain active for an unlimited amount of time.
-
-If you want Remote Desktop Services to end instead of disconnect a session when the time limit is reached, you can configure the policy setting Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Session Time Limits\End session when time limits are reached.
-
-Note: This policy setting appears in both Computer Configuration and User Configuration. If both policy settings are configured, the Computer Configuration policy setting takes precedence.
-
- Allow reconnection from original client only
- Specifies whether to allow users to reconnect to a disconnected Remote Desktop Services session using a computer other than the original client computer.
-
-You can use this setting to prevent Remote Desktop Services users from reconnecting to the disconnected session using a computer other than the client computer from which they originally created the session. By default, RD Session Host allows users to reconnect to disconnected sessions from any client computer.
-
-If the status is set to Enabled, users can reconnect to disconnected sessions only from the original client computer. If a user attempts to connect to the disconnected session from another computer, a new session is created instead.
-
-If the status is set to Disabled, users can always connect to the disconnected session from any computer.
-
-If the status is set to Not Configured, session reconnection from the original client computer is not specified at the Group Policy level.
-
-Important: This option is only supported for Citrix ICA clients that provide a serial number when connecting; this setting is ignored if the user is connecting with a Windows client. Also note that this setting appears in both Computer Configuration and User Configuration. If both settings are configured, the Computer Configuration setting overrides.
- Controls time limits for Remote Desktop Services sessions on an RD Session Host server
- Restrict Remote Desktop Services users to a single Remote Desktop Services session
- This policy setting allows you to restrict users to a single Remote Desktop Services session.
-
-If you enable this policy setting, users who log on remotely by using Remote Desktop Services will be restricted to a single session (either active or disconnected) on that server. If the user leaves the session in a disconnected state, the user automatically reconnects to that session at the next logon.
-
-If you disable this policy setting, users are allowed to make unlimited simultaneous remote connections by using Remote Desktop Services.
-
-If you do not configure this policy setting, this policy setting is not specified at the Group Policy level.
-
- Do not allow smart card device redirection
- This policy setting allows you to control the redirection of smart card devices in a Remote Desktop Services session.
-
-If you enable this policy setting, Remote Desktop Services users cannot use a smart card to log on to a Remote Desktop Services session.
-
-If you disable or do not configure this policy setting, smart card device redirection is allowed. By default, Remote Desktop Services automatically redirects smart card devices on connection.
-
-Note: The client computer must be running at least Microsoft Windows 2000 Server or at least Microsoft Windows XP Professional and the target server must be joined to a domain.
- Start a program on connection
- Configures Remote Desktop Services to run a specified program automatically upon connection.
-
-You can use this setting to specify a program to run automatically when a user logs on to a remote computer.
-
-By default, Remote Desktop Services sessions provide access to the full Windows desktop, unless otherwise specified with this setting, by the server administrator, or by the user in configuring the client connection. Enabling this setting overrides the "Start Program" settings set by the server administrator or user. The Start menu and Windows Desktop are not displayed, and when the user exits the program the session is automatically logged off.
-
-To use this setting, in Program path and file name, type the fully qualified path and file name of the executable file to be run when the user logs on. If necessary, in Working Directory, type the fully qualified path to the starting directory for the program. If you leave Working Directory blank, the program runs with its default working directory. If the specified program path, file name, or working directory is not the name of a valid directory, the RD Session Host server connection fails with an error message.
-
-If the status is set to Enabled, Remote Desktop Services sessions automatically run the specified program and use the specified Working Directory (or the program default directory, if Working Directory is not specified) as the working directory for the program.
-
-If the status is set to Disabled or Not Configured, Remote Desktop Services sessions start with the full desktop, unless the server administrator or user specify otherwise. (See "Computer Configuration\Administrative Templates\System\Logon\Run these programs at user logon" setting.)
-
-Note: This setting appears in both Computer Configuration and User Configuration. If both settings are configured, the Computer Configuration setting overrides.
- Temporary folders
- Do not delete temp folders upon exit
- This policy setting specifies whether Remote Desktop Services retains a user's per-session temporary folders at logoff.
-
-You can use this setting to maintain a user's session-specific temporary folders on a remote computer, even if the user logs off from a session. By default, Remote Desktop Services deletes a user's temporary folders when the user logs off.
-
-If you enable this policy setting, a user's per-session temporary folders are retained when the user logs off from a session.
-
-If you disable this policy setting, temporary folders are deleted when a user logs off, even if the server administrator specifies otherwise.
-
-If you do not configure this policy setting, Remote Desktop Services deletes the temporary folders from the remote computer at logoff, unless specified otherwise by the server administrator.
-
-Note: This setting only takes effect if per-session temporary folders are in use on the server. If you enable the Do not use temporary folders per session policy setting, this policy setting has no effect.
-
- This policy setting allows you to prevent Remote Desktop Services from creating session-specific temporary folders.
-
-You can use this policy setting to disable the creation of separate temporary folders on a remote computer for each session. By default, Remote Desktop Services creates a separate temporary folder for each active session that a user maintains on a remote computer. These temporary folders are created on the remote computer in a Temp folder under the user's profile folder and are named with the sessionid.
-
-If you enable this policy setting, per-session temporary folders are not created. Instead, a user's temporary files for all sessions on the remote computer are stored in a common Temp folder under the user's profile folder on the remote computer.
-
-If you disable this policy setting, per-session temporary folders are always created, even if the server administrator specifies otherwise.
-
-If you do not configure this policy setting, per-session temporary folders are created unless the server administrator specifies otherwise.
-
- Controls creation and deletion of temporary folders for Remote Desktop Services sessions
- Do not use temporary folders per session
- 1 minute
- 5 minutes
- 10 minutes
- 15 minutes
- 30 minutes
- 1 hour
- 2 hours
- 3 hours
- 6 hours
- 8 hours
- 12 hours
- 16 hours
- 18 hours
- 1 day
- 2 days
- 3 days
- 4 days
- 5 days
- Never
- Allow time zone redirection
- This policy setting determines whether the client computer redirects its time zone settings to the Remote Desktop Services session.
-
-If you enable this policy setting, clients that are capable of time zone redirection send their time zone information to the server. The server base time is then used to calculate the current session time (current session time = server base time + client time zone).
-
-If you disable or do not configure this policy setting, the client computer does not redirect its time zone information and the session time zone is the same as the server time zone.
-
-Note: Time zone redirection is possible only when connecting to at least a Microsoft Windows Server 2003 terminal server with a client using RDP 5.1 and later.
- This policy setting specifies whether to disable the administrator rights to customize security permissions for the Remote Desktop Session Host server.
-
-You can use this setting to prevent administrators from making changes to the user groups allowed to connect remotely to the RD Session Host server. By default, administrators are able to make such changes.
-
-If you enable this policy setting the default security descriptors for existing groups on the RD Session Host server cannot be changed. All the security descriptors are read-only.
-
-If you disable or do not configure this policy setting, server administrators have full read/write permissions to the user security descriptors by using the Remote Desktop Session WMI Provider.
-
-Note: The preferred method of managing user access is by adding a user to the Remote Desktop Users group.
-
- Do not allow local administrators to customize permissions
- Always show desktop on connection
- This policy setting determines whether the desktop is always displayed after a client connects to a remote computer or an initial program can run. It can be used to require that the desktop be displayed after a client connects to a remote computer, even if an initial program is already specified in the default user profile, Remote Desktop Connection, Remote Desktop Services client, or through Group Policy.
-
-If you enable this policy setting, the desktop is always displayed when a client connects to a remote computer. This policy setting overrides any initial program policy settings.
-
-If you disable or do not configure this policy setting, an initial program can be specified that runs on the remote computer after the client connects to the remote computer. If an initial program is not specified, the desktop is always displayed on the remote computer after the client connects to the remote computer.
-
-Note: If this policy setting is enabled, then the "Start a program on connection" policy setting is ignored.
- Allow UI Automation redirection
- This policy setting determines whether User Interface (UI) Automation client applications running on the local computer can access UI elements on the server.
-
-UI Automation gives programs access to most UI elements, which lets you use assistive technology products like Magnifier and Narrator that need to interact with the UI in order to work properly. UI information also allows automated test scripts to interact with the UI.
-
-Remote Desktop sessions don't currently support UI Automation redirection.
-
-If you enable or don't configure this policy setting, any UI Automation clients on your local computer can interact with remote apps. For example, you can use your local computer's Narrator and Magnifier clients to interact with UI on a web page you opened in a remote session.
-
-If you disable this policy setting, UI Automation clients running on your local computer can't interact with remote apps.
-
- Do not allow WebAuthn redirection
- This policy setting lets you control the redirection of web authentication (WebAuthn) requests from a Remote Desktop session to the local device. This redirection enables users to authenticate to resources inside the Remote Desktop session using their local authenticator (e.g., Windows Hello for Business, security key, or other).
-
-By default, Remote Desktop allows redirection of WebAuthn requests.
-
-If you enable this policy setting, users can't use their local authenticator inside the Remote Desktop session.
-
-If you disable or do not configure this policy setting, users can use local authenticators inside the Remote Desktop session.
-
- Disable Cloud Clipboard integration for server-to-client data transfer
- This policy setting lets you control whether data transferred from the remote session to the client using clipboard redirection is added to the client-side Cloud Clipboard.
-
-By default, Remote Desktop disables integration with the client-side Cloud Clipboard for data transfered from the remote session using clipboard redirection.
-
-If you enable or do not configure this policy setting, data copied in the remote session and pasted on the client, will not be added to the client-side Cloud Clipboard.
-
-If you disable this policy setting, data copied in the remote session and pasted on the client, will be added to the client-side Cloud Clipboard (if enabled).
-
- This policy setting allows you to specify whether to require user authentication for remote connections to the RD Session Host server by using Network Level Authentication. This policy setting enhances security by requiring that user authentication occur earlier in the remote connection process.
-
-If you enable this policy setting, only client computers that support Network Level Authentication can connect to the RD Session Host server.
-
-To determine whether a client computer supports Network Level Authentication, start Remote Desktop Connection on the client computer, click the icon in the upper-left corner of the Remote Desktop Connection dialog box, and then click About. In the About Remote Desktop Connection dialog box, look for the phrase Network Level Authentication supported.
-
-If you disable this policy setting, Network Level Authentication is not required for user authentication before allowing remote connections to the RD Session Host server.
-
-If you do not configure this policy setting, the local setting on the target computer will be enforced. On Windows Server 2012 and Windows 8, Network Level Authentication is enforced by default.
-
-Important: Disabling this policy setting provides less security because user authentication will occur later in the remote connection process.
-
- Require user authentication for remote connections by using Network Level Authentication
- Controls configuration of Remote Desktop Services technologies that enable access to a server running Windows-based programs or the full Windows desktop
- Set Remote Desktop Services User Home Directory
- Specifies whether Remote Desktop Services uses the specified network share or local directory path as the root of the user's home directory for a Remote Desktop Services session.
-
-To use this setting, select the location for the home directory (network or local) from the Location drop-down list. If you choose to place the directory on a network share, type the Home Dir Root Path in the form \\Computername\Sharename, and then select the drive letter to which you want the network share to be mapped.
-
-If you choose to keep the home directory on the local computer, type the Home Dir Root Path in the form "Drive:\Path" (without quotes), without environment variables or ellipses. Do not specify a placeholder for user alias, because Remote Desktop Services automatically appends this at logon.
-
-Note: The Drive Letter field is ignored if you choose to specify a local path. If you choose to specify a local path but then type the name of a network share in Home Dir Root Path, Remote Desktop Services places user home directories in the network location.
-
-If the status is set to Enabled, Remote Desktop Services creates the user's home directory in the specified location on the local computer or the network. The home directory path for each user is the specified Home Dir Root Path and the user's alias.
-
-If the status is set to Disabled or Not Configured, the user's home directory is as specified at the server.
- This policy setting allows you to specify the network path that Remote Desktop Services uses for roaming user profiles.
-
-By default, Remote Desktop Services stores all user profiles locally on the RD Session Host server. You can use this policy setting to specify a network share where user profiles can be centrally stored, allowing a user to access the same profile for sessions on all RD Session Host servers that are configured to use the network share for user profiles.
-
-If you enable this policy setting, Remote Desktop Services uses the specified path as the root directory for all user profiles. The profiles are contained in subfolders named for the account name of each user.
-
-To configure this policy setting, type the path to the network share in the form of \\Computername\Sharename. Do not specify a placeholder for the user account name, because Remote Desktop Services automatically adds this when the user logs on and the profile is created. If the specified network share does not exist, Remote Desktop Services displays an error message on the RD Session Host server and will store the user profiles locally on the RD Session Host server.
-
-If you disable or do not configure this policy setting, user profiles are stored locally on the RD Session Host server. You can configure a user's profile path on the Remote Desktop Services Profile tab on the user's account Properties dialog box.
-
-Notes:
-1. The roaming user profiles enabled by the policy setting apply only to Remote Desktop Services connections. A user might also have a Windows roaming user profile configured. The Remote Desktop Services roaming user profile always takes precedence in a Remote Desktop Services session.
-2. To configure a mandatory Remote Desktop Services roaming user profile for all users connecting remotely to the RD Session Host server, use this policy setting together with the "Use mandatory profiles on the RD Session Host server" policy setting located in Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\RD Session Host\Profiles. The path set in the "Set path for Remote Desktop Services Roaming User Profile" policy setting should contain the mandatory profile.
-
- This policy setting allows you to specify whether Remote Desktop Services uses a mandatory profile for all users connecting remotely to the RD Session Host server.
-
-If you enable this policy setting, Remote Desktop Services uses the path specified in the "Set path for Remote Desktop Services Roaming User Profile" policy setting as the root folder for the mandatory user profile. All users connecting remotely to the RD Session Host server use the same user profile.
-
-If you disable or do not configure this policy setting, mandatory user profiles are not used by users connecting remotely to the RD Session Host server.
-
-Note:
-
-For this policy setting to take effect, you must also enable and configure the "Set path for Remote Desktop Services Roaming User Profile" policy setting.
-
-
- Set path for Remote Desktop Services Roaming User Profile
- Use mandatory profiles on the RD Session Host server
- Limit the size of the entire roaming user profile cache
- This policy setting allows you to limit the size of the entire roaming user profile cache on the local drive. This policy setting only applies to a computer on which the Remote Desktop Session Host role service is installed.
-
-Note: If you want to limit the size of an individual user profile, use the "Limit profile size" policy setting located in User Configuration\Policies\Administrative Templates\System\User Profiles.
-
-If you enable this policy setting, you must specify a monitoring interval (in minutes) and a maximum size (in gigabytes) for the entire roaming user profile cache. The monitoring interval determines how often the size of the entire roaming user profile cache is checked. When the size of the entire roaming user profile cache exceeds the maximum size that you have specified, the oldest (least recently used) roaming user profiles will be deleted until the size of the entire roaming user profile cache is less than the maximum size specified.
-
-If you disable or do not configure this policy setting, no restriction is placed on the size of the entire roaming user profile cache on the local drive.
-
-Note: This policy setting is ignored if the "Prevent Roaming Profile changes from propagating to the server" policy setting located in Computer Configuration\Policies\Administrative Templates\System\User Profiles is enabled.
-
- Server authentication certificate template
- This policy setting allows you to specify the name of the certificate template that determines which certificate is automatically selected to authenticate an RD Session Host server.
-
-A certificate is needed to authenticate an RD Session Host server when TLS 1.0, 1.1 or 1.2 is used to secure communication between a client and an RD Session Host server during RDP connections.
-
-If you enable this policy setting, you need to specify a certificate template name. Only certificates created by using the specified certificate template will be considered when a certificate to authenticate the RD Session Host server is automatically selected. Automatic certificate selection only occurs when a specific certificate has not been selected.
-
-If no certificate can be found that was created with the specified certificate template, the RD Session Host server will issue a certificate enrollment request and will use the current certificate until the request is completed. If more than one certificate is found that was created with the specified certificate template, the certificate that will expire latest and that matches the current name of the RD Session Host server will be selected.
-
-If you disable or do not configure this policy, the certificate template name is not specified at the Group Policy level. By default, a self-signed certificate is used to authenticate the RD Session Host server.
-
-Note: If you select a specific certificate to be used to authenticate the RD Session Host server, that certificate will take precedence over this policy setting.
-
- Allow .rdp files from unknown publishers
- This policy setting allows you to specify whether users can run unsigned Remote Desktop Protocol (.rdp) files and .rdp files from unknown publishers on the client computer.
-
-If you enable or do not configure this policy setting, users can run unsigned .rdp files and .rdp files from unknown publishers on the client computer. Before a user starts an RDP session, the user receives a warning message and is asked to confirm whether they want to connect.
-
-If you disable this policy setting, users cannot run unsigned .rdp files and .rdp files from unknown publishers on the client computer. If the user tries to start an RDP session, the user receives a message that the publisher has been blocked.
-
- This policy setting allows you to specify whether users can run unsigned Remote Desktop Protocol (.rdp) files and .rdp files from unknown publishers on the client computer.
-
-If you enable or do not configure this policy setting, users can run unsigned .rdp files and .rdp files from unknown publishers on the client computer. Before a user starts an RDP session, the user receives a warning message and is asked to confirm whether they want to connect.
-
-If you disable this policy setting, users cannot run unsigned .rdp files and .rdp files from unknown publishers on the client computer. If the user tries to start an RDP session, the user receives a message that the publisher has been blocked.
-
- Allow .rdp files from valid publishers and user's default .rdp settings
- This policy setting allows you to specify whether users can run Remote Desktop Protocol (.rdp) files from a publisher that signed the file with a valid certificate. A valid certificate is one that is issued by an authority recognized by the client, such as the issuers in the client's Third-Party Root Certification Authorities certificate store. This policy setting also controls whether the user can start an RDP session by using default .rdp settings (for example, when a user directly opens the Remote Desktop Connection [RDC] client without specifying an .rdp file).
-
-If you enable or do not configure this policy setting, users can run .rdp files that are signed with a valid certificate. Users can also start an RDP session with default .rdp settings by directly opening the RDC client. When a user starts an RDP session, the user is asked to confirm whether they want to connect.
-
-If you disable this policy setting, users cannot run .rdp files that are signed with a valid certificate. Additionally, users cannot start an RDP session by directly opening the RDC client and specifying the remote computer name. When a user tries to start an RDP session, the user receives a message that the publisher has been blocked.
-
-Note: You can define this policy setting in the Computer Configuration node or in the User Configuration node. If you configure this policy setting for the computer, all users on the computer are affected.
-
- This policy setting allows you to specify whether users can run Remote Desktop Protocol (.rdp) files from a publisher that signed the file with a valid certificate. A valid certificate is one issued by an authority recognized by the client, such as the issuers in the client's Third-Party Root Certification Authorities certificate store. This policy setting also controls whether the user can start an RDP session by using default .rdp settings (for example, when a user directly opens the Remote Desktop Connection [RDC] client without specifying an .rdp file).
-
-If you enable or do not configure this policy setting, users can run .rdp files that are signed with a valid certificate. Users can also start an RDP session with default .rdp settings by directly opening the RDC client. When a user starts an RDP session, the user is asked to confirm whether they want to connect.
-
-If you disable this policy setting, users cannot run .rdp files that are signed with a valid certificate. Additionally, users cannot start an RDP session by directly opening the RDC client and specifying the remote computer name. When a user tries to start an RDP session, the user receives a message that the publisher has been blocked.
-
-Note: You can define this policy setting in the Computer Configuration node or in the User Configuration node. If you configure this policy setting for the computer, all users on the computer are affected.
-
- Specify SHA1 thumbprints of certificates representing trusted .rdp publishers
- This policy setting allows you to specify a list of Secure Hash Algorithm 1 (SHA1) certificate thumbprints that represent trusted Remote Desktop Protocol (.rdp) file publishers.
-
-If you enable this policy setting, any certificate with an SHA1 thumbprint that matches a thumbprint on the list is trusted. If a user tries to start an .rdp file that is signed by a trusted certificate, the user does not receive any warning messages when they start the file. To obtain the thumbprint, view the certificate details, and then click the Thumbprint field.
-
-If you disable or do not configure this policy setting, no publisher is treated as a trusted .rdp publisher.
-
-Notes:
-
-You can define this policy setting in the Computer Configuration node or in the User Configuration node. If you configure this policy setting for the computer, the list of certificate thumbprints trusted for a user is a combination of the list defined for the computer and the list defined for the user.
-
-This policy setting overrides the behavior of the "Allow .rdp files from valid publishers and user's default .rdp settings" policy setting.
-
-If the list contains a string that is not a certificate thumbprint, it is ignored.
-
- This policy setting allows you to specify a list of Secure Hash Algorithm 1 (SHA1) certificate thumbprints that represent trusted Remote Desktop Protocol (.rdp) file publishers.
-
-If you enable this policy setting, any certificate with an SHA1 thumbprint that matches a thumbprint on the list is trusted. If a user tries to start an .rdp file that is signed by a trusted certificate, the user does not receive any warning messages when they start the file. To obtain the thumbprint, view the certificate details, and then click the Thumbprint field.
-
-If you disable or do not configure this policy setting, no publisher is treated as a trusted .rdp publisher.
-
-Note:
-
-You can define this policy setting in the Computer Configuration node or in the User Configuration node. If you configure this policy setting for the computer, the list of certificate thumbprints trusted for a user is a combination of the list defined for the computer and the list defined for the user.
-
-This policy setting overrides the behavior of the "Allow .rdp files from valid publishers and user's default .rdp settings" policy setting.
-
-If the list contains a string that is not a certificate thumbprint, it is ignored.
-
-
- Prompt for credentials on the client computer
- This policy setting determines whether a user will be prompted on the client computer to provide credentials for a remote connection to an RD Session Host server.
-
-If you enable this policy setting, a user will be prompted on the client computer instead of on the RD Session Host server to provide credentials for a remote connection to an RD Session Host server. If saved credentials for the user are available on the client computer, the user will not be prompted to provide credentials.
-
-Note: If you enable this policy setting in releases of Windows Server 2008 R2 with SP1 or Windows Server 2008 R2, and a user is prompted on both the client computer and on the RD Session Host server to provide credentials, clear the Always prompt for password check box on the Log on Settings tab in Remote Desktop Session Host Configuration.
-
-If you disable or do not configure this policy setting, the version of the operating system on the RD Session Host server will determine when a user is prompted to provide credentials for a remote connection to an RD Session Host server. For Windows Server 2003 and Windows 2000 Server a user will be prompted on the terminal server to provide credentials for a remote connection. For Windows Server 2008 and Windows Server 2008 R2, a user will be prompted on the client computer to provide credentials for a remote connection.
-
-
- Configure server authentication for client
- Always connect, even if authentication fails
- Do not connect if authentication fails
- Warn me if authentication fails
- This policy setting allows you to specify whether the client will establish a connection to the RD Session Host server when the client cannot authenticate the RD Session Host server.
-
-If you enable this policy setting, you must specify one of the following settings:
-
-Always connect, even if authentication fails: The client connects to the RD Session Host server even if the client cannot authenticate the RD Session Host server.
-
-Warn me if authentication fails: The client attempts to authenticate the RD Session Host server. If the RD Session Host server can be authenticated, the client establishes a connection to the RD Session Host server. If the RD Session Host server cannot be authenticated, the user is prompted to choose whether to connect to the RD Session Host server without authenticating the RD Session Host server.
-
-Do not connect if authentication fails: The client establishes a connection to the RD Session Host server only if the RD Session Host server can be authenticated.
-
-If you disable or do not configure this policy setting, the authentication setting that is specified in Remote Desktop Connection or in the .rdp file determines whether the client establishes a connection to the RD Session Host server when the client cannot authenticate the RD Session Host server.
-
-
- Configure image quality for RemoteFX Adaptive Graphics
- This policy setting allows you to specify the visual quality for remote users when connecting to this computer by using Remote Desktop Connection. You can use this policy setting to balance the network bandwidth usage with the visual quality that is delivered.
- If you enable this policy setting and set quality to Low, RemoteFX Adaptive Graphics uses an encoding mechanism that results in low quality images. This mode consumes the lowest amount of network bandwidth of the quality modes.
- If you enable this policy setting and set quality to Medium, RemoteFX Adaptive Graphics uses an encoding mechanism that results in medium quality images. This mode provides better graphics quality than low quality and uses less bandwidth than high quality.
- If you enable this policy setting and set quality to High, RemoteFX Adaptive Graphics uses an encoding mechanism that results in high quality images and consumes moderate network bandwidth.
- If you enable this policy setting and set quality to Lossless, RemoteFX Adaptive Graphics uses lossless encoding. In this mode, the color integrity of the graphics data is not impacted. However, this setting results in a significant increase in network bandwidth consumption. We recommend that you set this for very specific cases only.
- If you disable or do not configure this policy setting, RemoteFX Adaptive Graphics uses an encoding mechanism that results in medium quality images.
-
-
- Lossless
- High
- Medium
- Low
-
- Configure RemoteFX Adaptive Graphics
- This policy setting allows the administrator to configure the RemoteFX experience for Remote Desktop Session Host or Remote Desktop Virtualization Host servers. By default, the system will choose the best experience based on available nework bandwidth.
-
-If you enable this policy setting, the RemoteFX experience could be set to one of the following options:
-1. Let the system choose the experience for the network condition
-2. Optimize for server scalability
-3. Optimize for minimum bandwidth usage
-
-If you disable or do not configure this policy setting, the RemoteFX experience will change dynamically based on the network condition."
-
- Optimize for server scalability
- Let the system choose experience for network condition
- Optimize for minimum bandwidth usage
-
- Configure compression for RemoteFX data
- This policy setting allows you to specify which Remote Desktop Protocol (RDP) compression algorithm to use.
-
-By default, servers use an RDP compression algorithm that is based on the server's hardware configuration.
-
-If you enable this policy setting, you can specify which RDP compression algorithm to use. If you select the algorithm that is optimized to use less memory, this option is less memory-intensive, but uses more network bandwidth. If you select the algorithm that is optimized to use less network bandwidth, this option uses less network bandwidth, but is more memory-intensive. Additionally, a third option is available that balances memory usage and network bandwidth. In Windows 8 only the compression algorithm that balances memory usage and bandwidth is used.
-
-You can also choose not to use an RDP compression algorithm. Choosing not to use an RDP compression algorithm will use more network bandwidth and is only recommended if you are using a hardware device that is designed to optimize network traffic. Even if you choose not to use an RDP compression algorithm, some graphics data will still be compressed.
-
-If you disable or do not configure this policy setting, the default RDP compression algorithm will be used.
-
- Balances memory and network bandwidth
- Optimized to use less network bandwidth
- Optimized to use less memory
- Do not use an RDP compression algorithm
-
- Use advanced RemoteFX graphics for RemoteApp
- This policy setting allows you to enable RemoteApp programs to use advanced graphics, including support for transparency, live thumbnails, and seamless application moves. This policy setting applies only to RemoteApp programs and does not apply to remote desktop sessions.
-
-If you enable or do not configure this policy setting, RemoteApp programs published from this RD Session Host server will use these advanced graphics.
-
-If you disable this policy setting, RemoteApp programs published from this RD Session Host server will not use these advanced graphics. You may want to choose this option if you discover that applications published as RemoteApp programs do not support these advanced graphics.
-
-
-
-
- Use WDDM graphics display driver for Remote Desktop Connections
- This policy setting lets you enable WDDM graphics display driver for Remote Desktop Connections.
-
-If you enable this policy setting, Remote Desktop Connections will use WDDM graphics display driver.
-
-If you disable or do not configure this policy setting, Remote Desktop Connections will NOT use WDDM graphics display driver. In this case, the Remote Desktop Connections will use XDDM graphics display driver.
-
-For this change to take effect, you must restart Windows.
-
-
- This policy setting lets you enable WDDM graphics display driver for Remote Desktop Connections.
-
-If you enable or do not configure this policy setting, Remote Desktop Connections will use WDDM graphics display driver.
-
-If you disable this policy setting, Remote Desktop Connections will NOT use WDDM graphics display driver. In this case, the Remote Desktop Connections will use XDDM graphics display driver.
-
-For this change to take effect, you must restart Windows.
-
-
- This policy setting lets you enable WDDM graphics display driver for Remote Desktop Connections.
-
-If you enable this policy setting, Remote Desktop Connections will use WDDM graphics display driver.
-
-If you disable this policy setting, Remote Desktop Connections will NOT use WDDM graphics display driver. In this case, the Remote Desktop Connections will use XDDM graphics display driver.
-
-If you do not configure this policy setting, Remote Desktop Connections on the RD Session Host server will NOT use WDDM graphics display driver. In all other cases, Remote Desktop Connections will use WDDM graphics display driver.
-
-For this change to take effect, you must restart Windows.
-
-
-
- Configure H.264/AVC hardware encoding for Remote Desktop Connections
- This policy setting lets you enable H.264/AVC hardware encoding support for Remote Desktop Connections. When you enable hardware encoding, if an error occurs, we will attempt to use software encoding. If you disable or do not configure this policy, we will always use software encoding.
-
-
- Prioritize H.264/AVC 444 graphics mode for Remote Desktop Connections
- This policy setting prioritizes the H.264/AVC 444 graphics mode for non-RemoteFX vGPU scenarios. When you use this setting on the RDP server, the server will use H.264/AVC 444 as the codec in an RDP 10 connection where both the client and server can use H.264/AVC 444.
-
-
-
- Do not allow hardware accelerated decoding
- This policy setting specifies whether the Remote Desktop Connection can use hardware acceleration if supported hardware is available. If you use this setting, the Remote Desktop Client will use only software decoding. For example, if you have a problem that you suspect may be related to hardware acceleration, use this setting to disable the acceleration; then, if the problem still occurs, you will know that there are additional issues to investigate. If you disable this setting or leave it not configured, the Remote Desktop client will use hardware accelerated decoding if supported hardware is available.
-
-
-
- Optimize visual experience for Remote Desktop Service Sessions
- This policy setting allows you to specify the visual experience that remote users receive in Remote Desktop Services sessions. Remote sessions on the remote computer are then optimized to support this visual experience.
-
-By default, Remote Desktop Services sessions are optimized for rich multimedia, such as applications that use Silverlight or Windows Presentation Foundation.
-
-If you enable this policy setting, you must select the visual experience for which you want to optimize Remote Desktop Services sessions. You can select either Rich multimedia or Text.
-
-If you disable or do not configure this policy setting, Remote Desktop Services sessions are optimized for rich multimedia.
-
- Rich multimedia
- Text
-
- RemoteFX USB Device Redirection
- Allow RDP redirection of other supported RemoteFX USB devices from this computer
- Allow RDP redirection of other supported RemoteFX USB devices from this computer
- This policy setting allows you to permit RDP redirection of other supported RemoteFX USB devices from this computer. Redirected RemoteFX USB devices will not be available for local usage on this computer.
-
-If you enable this policy setting, you can choose to give the ability to redirect other supported RemoteFX USB devices over RDP to all users or only to users who are in the Administrators group on the computer.
-
-If you disable or do not configure this policy setting, other supported RemoteFX USB devices are not available for RDP redirection by using any user account.
-
-For this change to take effect, you must restart Windows.
-
-
- Adminstrators Only
- Adminstrators and Users
- Configure RemoteFX USB Redirection access rights
-
- Configure RemoteFX
- This policy setting allows you to control the availability of RemoteFX on both a Remote Desktop Virtualization Host (RD Virtualization Host) server and a Remote Desktop Session Host (RD Session Host) server.
-
-When deployed on an RD Virtualization Host server, RemoteFX delivers a rich user experience by rendering content on the server by using graphics processing units (GPUs). By default, RemoteFX for RD Virtualization Host uses server-side GPUs to deliver a rich user experience over LAN connections and RDP 7.1.
-
-When deployed on an RD Session Host server, RemoteFX delivers a rich user experience by using a hardware-accelerated compression scheme.
-
-If you enable this policy setting, RemoteFX will be used to deliver a rich user experience over LAN connections and RDP 7.1.
-
-If you disable this policy setting, RemoteFX will be disabled.
-
-If you do not configure this policy setting, the default behavior will be used. By default, RemoteFX for RD Virtualization Host is enabled and RemoteFX for RD Session Host is disabled.
-
-
- Optimize visual experience when using RemoteFX
- This policy setting allows you to specify the visual experience that remote users will have in Remote Desktop Connection (RDC) connections that use RemoteFX. You can use this policy to balance the network bandwidth usage with the type of graphics experience that is delivered.
-
-Depending on the requirements of your users, you can reduce network bandwidth usage by reducing the screen capture rate. You can also reduce network bandwidth usage by reducing the image quality (increasing the amount of image compression that is performed).
-
-If you have a higher than average bandwidth network, you can maximize the utilization of bandwidth by selecting the highest setting for screen capture rate and the highest setting for image quality.
-
-By default, Remote Desktop Connection sessions that use RemoteFX are optimized for a balanced experience over LAN conditions. If you disable or do not configure this policy setting, Remote Desktop Connection sessions that use RemoteFX will be the same as if the medium screen capture rate and the medium image compression settings were selected (the default behavior).
-
- Highest (best quality)
- Medium (default)
- Lowest
- Highest (best quality)
- Medium (default)
- Lowest
-
- Enable RemoteFX encoding for RemoteFX clients designed for Windows Server 2008 R2 SP1
- This policy setting allows you to configure graphics encoding to use the RemoteFX Codec on the Remote Desktop Session Host server so that the sessions are compatible with non-Windows thin client devices designed for Windows Server 2008 R2 SP1. These clients only support the Windows Server 2008 R2 SP1 RemoteFX Codec.If you enable this policy setting, users' sessions on this server will only use the Windows Server 2008 R2 SP1 RemoteFX Codec for encoding. This mode is compatible with thin client devices that only support the Windows Server 2008 R2 SP1 RemoteFX Codec.If you disable or do not configure this policy setting, non-Windows thin clients that only support the Windows Server 2008 R2 SP1 RemoteFX Codec will not be able to connect to this server. This policy setting applies only to clients that are using Remote Desktop Protocol (RDP) 7.1, and does not affect clients that are using other RDP versions.
-
-
- RemoteApp and Desktop Connections
- Controls configuration of RemoteApp and Desktop Connections
- Specify default connection URL
- This policy setting specifies the default connection URL for RemoteApp and Desktop Connections. The default connection URL is a specific connection that can only be configured by using Group Policy. In addition to the capabilities that are common to all connections, the default connection URL allows document file types to be associated with RemoteApp programs.
-
-The default connection URL must be configured in the form of http://contoso.com/rdweb/Feed/webfeed.aspx.
-
-If you enable this policy setting, the specified URL is configured as the default connection URL for the user and replaces any existing connection URL. The user cannot change the default connection URL. The user's default logon credentials are used when setting up the default connection URL.
-
-If you disable or do not configure this policy setting, the user has no default connection URL.
-
-Note: RemoteApp programs that are installed through RemoteApp and Desktop Connections from an untrusted server can compromise the security of a user's account.
-
-
- Select RDP transport protocols
- This policy setting allows you to specify which protocols can be used for Remote Desktop Protocol (RDP) access to this server.
-
-If you enable this policy setting, you must specify if you would like RDP to use UDP.
-
-You can select one of the following options: "Use both UDP and TCP", "Use only TCP" or "Use either UDP or TCP (default)"
-
-If you select "Use either UDP or TCP" and the UDP connection is successful, most of the RDP traffic will use UDP.
-
-If the UDP connection is not successful or if you select "Use only TCP," all of the RDP traffic will use TCP.
-
-If you disable or do not configure this policy setting, RDP will choose the optimal protocols for delivering the best user experience.
-
- Use both UDP and TCP
- Use only TCP
- Use either UDP or TCP
-
- Select network detection on the server
- This policy setting allows you to specify how the Remote Desktop Protocol will try to detect the network quality (bandwidth and latency).
-
-You can choose to disable Connect Time Detect, Continuous Network Detect, or both Connect Time Detect and Continuous Network Detect.
-
-If you disable Connect Time Detect, Remote Desktop Protocol will not determine the network quality at the connect time, and it will assume that all traffic to this server originates from a low-speed connection.
-
-If you disable Continuous Network Detect, Remote Desktop Protocol will not try to adapt the remote user experience to varying network quality.
-
-If you disable Connect Time Detect and Continuous Network Detect, Remote Desktop Protocol will not try to determine the network quality at the connect time; instead it will assume that all traffic to this server originates from a low-speed connection, and it will not try to adapt the user experience to varying network quality.
-
-If you disable or do not configure this policy setting, Remote Desktop Protocol will spend up to a few seconds trying to determine the network quality prior to the connection, and it will continuously try to adapt the user experience to varying network quality.
-
- Use both Connect Time Detect and Continuous Network Detect
- Turn off Connect Time Detect
- Turn off Continuous Network Detect
- Turn off Connect Time Detect and Continuous Network Detect
-
- Turn Off UDP On Client
- This policy setting specifies whether the UDP protocol will be used to access servers via Remote Desktop Protocol.
-
-If you enable this policy setting, Remote Desktop Protocol traffic will only use the TCP protocol.
-
-If you disable or do not configure this policy setting, Remote Desktop Protocol traffic will attempt to use both TCP and UDP protocols.
-
-
- Suspend user sign-in to complete app registration
- This policy setting allows you to specify whether the app registration is completed before showing the Start screen to the user.
-
-By default, when a new user signs in to a computer, the Start screen is shown and apps are registered in the background. However, some apps may not work until app registration is complete.
-
-If you enable this policy setting, user sign-in is blocked for up to 6 minutes to complete the app registration. You can use this policy setting when customizing the Start screen on Remote Desktop Session Host servers.
-
-If you disable or do not configure this policy setting, the Start screen is shown and apps are registered in the background.
-
- Use hardware graphics adapters for all Remote Desktop Services sessions
- This policy setting enables system administrators to change the graphics rendering for all Remote Desktop Services sessions.
-
-If you enable this policy setting, all Remote Desktop Services sessions use the hardware graphics renderer instead of the Microsoft Basic Render Driver as the default adapter.
-
-If you disable this policy setting, all Remote Desktop Services sessions use the Microsoft Basic Render Driver as the default adapter.
-
-If you do not configure this policy setting, Remote Desktop Services sessions on the RD Session Host server use the Microsoft Basic Render Driver as the default adapter. In all other cases, Remote Desktop Services sessions use the hardware graphics renderer by default.
-
-NOTE: The policy setting enables load-balancing of graphics processing units (GPU) on a computer with more than one GPU installed. The GPU configuration of the local session is not affected by this policy setting.
-
-
-
-
-
- Color Depth
-
-
- Maximum Monitors
-
-
- Width
- Height
-
-
- Encryption Level
- Choose the encryption level from the drop-down list.
-
-
- When attempting to find a suitable driver:
-
-
- Allow users to change this setting
- Set RD Gateway authentication method
-
-
- Allow users to change this setting
-
-
- Allow users to change this setting
-
-
-
-
-
- Keep-Alive interval:
-
-
-
-
-
- Separate license server names with commas.
- Example: Server1,Server2.example.com,192.168.1.1
-
-
- Specify the licensing mode for the RD Session Host server.
-
-
- RD Maximum Connections allowed
- Type 999999 for unlimited connections.
-
-
- Options:
-
-
- Options:
-
-
-
-
-
-
-
-
-
-
-
-
- Security Layer
- Choose the security layer from the drop-down list.
-
-
- End a disconnected session
-
-
- End a disconnected session
-
-
- Idle session limit:
-
-
- Idle session limit:
-
-
- Active session limit :
-
-
- Active session limit :
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Location:
-
-
-
- If home path is on the network, specify drive letter for the mapped drive.
- Drive Letter
-
-
-
-
-
- Specify the path in the form, \\Computername\Sharename
-
-
- Monitoring interval (minutes):
- Maximum cache size (GBs):
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Authentication setting:
-
-
- Image quality:
-
-
- RDP experience:
-
-
- RDP compression algorithm:
-
-
- Visual experience:
-
-
- Audio Quality
-
-
- RemoteFX USB Redirection Access Rights
-
-
- Screen capture rate (frames per second):
- Screen Image Quality:
-
-
-
-
-
-
-
- Select Network Detect Level
-
-
- Select Transport Type
-
-
-
-
diff --git a/policy_templates/en-US/TextInput.adml b/policy_templates/en-US/TextInput.adml
deleted file mode 100644
index f64b18c..0000000
--- a/policy_templates/en-US/TextInput.adml
+++ /dev/null
@@ -1,14 +0,0 @@
-
-
- TextInput policies
- TextInput related policies.
-
-
- Text Input
- When this policy setting is enabled, some language features (such as handwriting recognizers and spell checking dictionaries) included with a language can be uninstalled from a user’s machine when the language is uninstalled. The language can be reinstalled with a different selection of included language features if needed. When this policy setting is disabled, language features remain on the user’s machine when the language is uninstalled.
- Allow uninstallation of language features when a language is uninstalled
- This policy setting controls the ability to send inking and typing data to Microsoft to improve the language recognition and suggestion capabilities of apps and services running on Windows.
- Improve inking and typing recognition
-
-
-
diff --git a/policy_templates/en-US/Thumbnails.adml b/policy_templates/en-US/Thumbnails.adml
deleted file mode 100644
index 32ecf62..0000000
--- a/policy_templates/en-US/Thumbnails.adml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off the display of thumbnails and only display icons.
- This policy setting allows you to configure how File Explorer displays thumbnail images or icons on the local computer.
-
-File Explorer displays thumbnail images by default.
-
-If you enable this policy setting, File Explorer displays only icons and never displays thumbnail images.
-
-If you disable or do not configure this policy setting, File Explorer displays only thumbnail images.
- Turn off the display of thumbnails and only display icons on network folders
- This policy setting allows you to configure how File Explorer displays thumbnail images or icons on network folders.
-
-File Explorer displays thumbnail images on network folders by default.
-
-If you enable this policy setting, File Explorer displays only icons and never displays thumbnail images on network folders.
-
-If you disable or do not configure this policy setting, File Explorer displays only thumbnail images on network folders.
- Turn off the caching of thumbnails in hidden thumbs.db files
- Turns off the caching of thumbnails in hidden thumbs.db files.
-
-This policy setting allows you to configure File Explorer to cache thumbnails of items residing in network folders in hidden thumbs.db files.
-
-If you enable this policy setting, File Explorer does not create, read from, or write to thumbs.db files.
-
-If you disable or do not configure this policy setting, File Explorer creates, reads from, and writes to thumbs.db files.
-
-
-
-
diff --git a/policy_templates/en-US/TouchInput.adml b/policy_templates/en-US/TouchInput.adml
deleted file mode 100644
index 7a773ad..0000000
--- a/policy_templates/en-US/TouchInput.adml
+++ /dev/null
@@ -1,34 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Touch Input
- Turn off Tablet PC touch input
- Turn off Tablet PC touch input
-
-Turns off touch input, which allows the user to interact with their computer using their finger.
-
-If you enable this setting, the user will not be able to produce input with touch. They will not be able to use touch input or touch gestures such as tap and double tap, the touch pointer, and other touch-specific features.
-
-If you disable this setting, the user can produce input with touch, by using gestures, the touch pointer, and other-touch specific features.
-
-If you do not configure this setting, touch input is on by default.
-
-Note: Changes to this setting will not take effect until the user logs off.
- Turn off Touch Panning
- Turn off Panning
-Turns off touch panning, which allows users pan inside windows by touch. On a compatible PC with a touch digitizer, by default users are able to scroll or pan inside a scrolling area by dragging up or down directly on the scrolling content.
-
-If you enable this setting, the user will not be able to pan windows by touch.
-
-If you disable this setting, the user can pan windows by touch.
-
-If you do not configure this setting, Touch Panning is on by default.
-
-Note: Changes to this setting will not take effect until the user logs off.
-
-
-
diff --git a/policy_templates/en-US/UserExperienceVirtualization.adml b/policy_templates/en-US/UserExperienceVirtualization.adml
deleted file mode 100644
index c476ca9..0000000
--- a/policy_templates/en-US/UserExperienceVirtualization.adml
+++ /dev/null
@@ -1,1075 +0,0 @@
-
-
- Microsoft User Experience Virtualization policy settings
- Group policy settings for Microsoft User Experience Virtualization
-
-
- At least Windows 7 or Windows Server 2008 R2
- Microsoft User Experience Virtualization
- Microsoft User Experience Virtualization group policy settings
- Applications
- Microsoft User Experience Virtualization group policy settings
- Windows Apps
- Synchronization timeout
- This policy setting configures the number of milliseconds that the computer waits when retrieving user settings from the settings storage location.
-You can use this setting to override the default value of 2000 milliseconds.
-If you enable this policy setting, set the number of milliseconds that the system waits to retrieve settings.
-If you disable or do not configure this policy setting, the default value of 2000 milliseconds is used.
-
- Settings storage path
- This policy setting configures where the settings package files that contain user settings are stored.
-If you enable this policy setting, the user settings are stored in the specified location.
-If you disable or do not configure this policy setting, the user settings are stored in the user’s home directory if configured for your environment.
-
- Settings package size warning threshold
- This policy setting allows you to configure the UE-V Agent to write a warning event to the event log when a settings package file size reaches a defined threshold. By default the UE-V Agent does not report information about package file size.
-If you enable this policy setting, specify the threshold file size in bytes. When the settings package file exceeds this threshold the UE-V Agent will write a warning event to the event log.
-If you disable or do not configure this policy setting, no event is written to the event log to report settings package size.
-
- Settings template catalog path
- This policy setting configures where custom settings location templates are stored and if the catalog will be used to replace the default Microsoft templates installed with the UE-V Agent.
-If you enable this policy setting, the UE-V Agent checks the specified location once each day and updates its synchronization behavior based on the templates in this location. Settings location templates added or updated since the last check are registered by the UE-V Agent. The UE-V Agent deregisters templates that were removed from this location.
-If you specify a UNC path and leave the option to replace the default Microsoft templates unchecked, the UE-V Agent will use the default Microsoft templates installed by the UE-V Agent and custom templates in the settings template catalog. If there are custom templates in the settings template catalog which use the same ID as the default Microsoft templates, they will be ignored.
-If you specify a UNC path and check the option to replace the default Microsoft templates, all of the default Microsoft templates installed by the UE-V Agent will be deleted from the computer and only the templates located in the settings template catalog will be used.
-If you disable this policy setting, the UE-V Agent will not use the custom settings location templates. If you disable this policy setting after it has been enabled, the UE-V Agent will not restore the default Microsoft templates.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Internet Explorer Common Settings
- This policy setting configures the synchronization of user settings which are common between the versions of Internet Explorer.
-By default, the user settings which are common between the versions of Internet Explorer synchronize between computers. Use the policy setting to prevent the user settings of Internet Explorer from synchronization between computers.
-If you enable this policy setting, the user settings which are common between the versions of Internet Explorer continue to synchronize.
-If you disable this policy setting, the user settings which are common between the versions of Internet Explorer are excluded from settings synchronization. If any version of the Internet Explorer settings are enabled this policy setting should not be disabled.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Internet Explorer 8
- This policy setting configures the synchronization of user settings for Internet Explorer 8.
-By default, the user settings of Internet Explorer 8 synchronize between computers. Use the policy setting to prevent the user settings for Internet Explorer 8 from synchronization between computers.
-If you enable this policy setting, the Internet Explorer 8 user settings continue to synchronize.
-If you disable this policy setting, Internet Explorer 8 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Internet Explorer 9
- This policy setting configures the synchronization of user settings for Internet Explorer 9.
-By default, the user settings of Internet Explorer 9 synchronize between computers. Use the policy setting to prevent the user settings for Internet Explorer 9 from synchronization between computers.
-If you enable this policy setting, the Internet Explorer 9 user settings continue to synchronize.
-If you disable this policy setting, Internet Explorer 9 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Internet Explorer 10
- This policy setting configures the synchronization of user settings of Internet Explorer 10.
-By default, the user settings of Internet Explorer 10 synchronize between computers. Use the policy setting to prevent the user settings for Internet Explorer 10 from synchronization between computers.
-If you enable this policy setting, the Internet Explorer 10 user settings continue to synchronize.
-If you disable this policy setting, Internet Explorer 10 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Internet Explorer 11
- This policy setting configures the synchronization of user settings of Internet Explorer 11.
-By default, the user settings of Internet Explorer 11 synchronize between computers. Use the policy setting to prevent the user settings for Internet Explorer 11 from synchronization between computers.
-If you enable this policy setting, the Internet Explorer 11 user settings continue to synchronize.
-If you disable this policy setting, Internet Explorer 11 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Calculator
- This policy setting configures the synchronization of user settings of Calculator.
-By default, the user settings of Calculator synchronize between computers. Use the policy setting to prevent the user settings of Calculator from synchronization between computers.
-If you enable this policy setting, the Calculator user settings continue to synchronize.
-If you disable this policy setting, Calculator user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Notepad
- This policy setting configures the synchronization of user settings of Notepad.
-By default, the user settings of Notepad synchronize between computers. Use the policy setting to prevent the user settings of Notepad from synchronization between computers.
-If you enable this policy setting, the Notepad user settings continue to synchronize.
-If you disable this policy setting, Notepad user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- WordPad
- This policy setting configures the synchronization of user settings of WordPad.
-By default, the user settings of WordPad synchronize between computers. Use the policy setting to prevent the user settings of WordPad from synchronization between computers.
-If you enable this policy setting, the WordPad user settings continue to synchronize.
-If you disable this policy setting, WordPad user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 2016 Common Settings
-
-This policy setting configures the synchronization of user settings which are common between the Microsoft Office Suite 2016 applications.
-By default, the user settings which are common between the Microsoft Office Suite 2016 applications synchronize between computers. Use the policy setting to prevent the user settings which are common between the Microsoft Office Suite 2016 applications from synchronization between computers.
-If you enable this policy setting, the user settings which are common between the Microsoft Office Suite 2016 applications continue to synchronize.
-If you disable this policy setting, the user settings which are common between the Microsoft Office Suite 2016 applications are excluded from the synchronization settings. If any of the Microsoft Office Suite 2016 applications are enabled, this policy setting should not be disabled.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Access 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Access 2016.
-By default, the user settings of Microsoft Access 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Access 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft Access 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Access 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Excel 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Excel 2016.
-By default, the user settings of Microsoft Excel 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Excel 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft Excel 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Excel 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Lync 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Lync 2016.
-By default, the user settings of Microsoft Lync 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Lync 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft Lync 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Lync 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 2016 Upload Center
-
-This policy setting configures the synchronization of user settings for Microsoft Office 2016 Upload Center.
-By default, the user settings of Microsoft Office 2016 Upload Center synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Office 2016 Upload Center from synchronization between computers.
-If you enable this policy setting, Microsoft Office 2016 Upload Center user settings continue to synchronize.
-If you disable this policy setting, Microsoft Office 2016 Upload Center user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft OneDrive for Business 2016
-
-This policy setting configures the synchronization of user settings for OneDrive for Business 2016.
-By default, the user settings of OneDrive for Business 2016 synchronize between computers. Use the policy setting to prevent the user settings of OneDrive for Business 2016 from synchronization between computers.
-If you enable this policy setting, OneDrive for Business 2016 user settings continue to synchronize.
-If you disable this policy setting, OneDrive for Business 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft OneNote 2016
-
-This policy setting configures the synchronization of user settings for Microsoft OneNote 2016.
-By default, the user settings of Microsoft OneNote 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft OneNote 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft OneNote 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft OneNote 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Outlook 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Outlook 2016.
-By default, the user settings of Microsoft Outlook 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Outlook 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft Outlook 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Outlook 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft PowerPoint 2016
-
-This policy setting configures the synchronization of user settings for Microsoft PowerPoint 2016.
-By default, the user settings of Microsoft PowerPoint 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft PowerPoint 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft PowerPoint 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft PowerPoint 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Project 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Project 2016.
-By default, the user settings of Microsoft Project 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Project 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft Project 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Project 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Publisher 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Publisher 2016.
-By default, the user settings of Microsoft Publisher 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Publisher 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft Publisher 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Publisher 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Visio 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Visio 2016.
-By default, the user settings of Microsoft Visio 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Visio 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft Visio 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Visio 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Word 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Word 2016.
-By default, the user settings of Microsoft Word 2016 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Word 2016 from synchronization between computers.
-If you enable this policy setting, Microsoft Word 2016 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Word 2016 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Common 2016 backup only
-
-This policy setting configures the backup of certain user settings which are common between the Microsoft Office Suite 2016 applications.
-Microsoft Office Suite 2016 has user settings which are common between applications and are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific common Microsoft Office Suite 2016 applications.
-If you enable this policy setting, certain user settings which are common between the Microsoft Office Suite 2016 applications will continue to be backed up.
-If you disable this policy setting, certain user settings which are common between the Microsoft Office Suite 2016 applications will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Access 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Access 2016.
-Microsoft Access 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Access 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft Access 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Access 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Excel 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Excel 2016.
-Microsoft Excel 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Excel 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft Excel 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Excel 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Lync 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Lync 2016.
-Microsoft Lync 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Lync 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft Lync 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Lync 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- OneNote 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft OneNote 2016.
-Microsoft OneNote 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft OneNote 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft OneNote 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft OneNote 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Outlook 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Outlook 2016.
-Microsoft Outlook 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Outlook 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft Outlook 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Outlook 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- PowerPoint 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft PowerPoint 2016.
-Microsoft PowerPoint 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft PowerPoint 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft PowerPoint 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft PowerPoint 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Project 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Project 2016.
-Microsoft Project 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Project 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft Project 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Project 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Publisher 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Publisher 2016.
-Microsoft Publisher 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Publisher 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft Publisher 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Publisher 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Visio 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Visio 2016.
-Microsoft Visio 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Visio 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft Visio 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Visio 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Word 2016 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Word 2016.
-Microsoft Word 2016 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Word 2016 settings.
-If you enable this policy setting, certain user settings of Microsoft Word 2016 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Word 2016 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Common 2016
-
-This policy setting configures the synchronization of user settings which are common between the Microsoft Office Suite 2016 applications.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings which are common between the Microsoft Office Suite 2016 applications will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings which are common between the Microsoft Office Suite 2016 applications from synchronization between computers with UE-V.
-If you enable this policy setting, user settings which are common between the Microsoft Office Suite 2016 applications continue to synchronize with UE-V.
-If you disable this policy setting, user settings which are common between the Microsoft Office Suite 2016 applications are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Access 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Access 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Access 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Access 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Access 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Access 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Excel 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Excel 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Excel 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Excel 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Excel 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Excel 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Lync 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Lync 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Lync 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Lync 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Lync 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Lync 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 OneNote 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 OneNote 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 OneNote 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 OneNote 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 OneNote 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 OneNote 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Outlook 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Outlook 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Outlook 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Outlook 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Outlook 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Outlook 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 PowerPoint 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 PowerPoint 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 PowerPoint 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 PowerPoint 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 PowerPoint 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 PowerPoint 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Project 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Project 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Project 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Project 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Project 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Project 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Publisher 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Publisher 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Publisher 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Publisher 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Publisher 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Publisher 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Visio 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Visio 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Visio 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Visio 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Visio 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Visio 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Word 2016
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Word 2016.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Word 2016 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Word 2016 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Word 2016 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Word 2016 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 2013 Common Settings
-
-This policy setting configures the synchronization of user settings which are common between the Microsoft Office Suite 2013 applications.
-By default, the user settings which are common between the Microsoft Office Suite 2013 applications synchronize between computers. Use the policy setting to prevent the user settings which are common between the Microsoft Office Suite 2013 applications from synchronization between computers.
-If you enable this policy setting, the user settings which are common between the Microsoft Office Suite 2013 applications continue to synchronize.
-If you disable this policy setting, the user settings which are common between the Microsoft Office Suite 2013 applications are excluded from the synchronization settings. If any of the Microsoft Office Suite 2013 applications are enabled, this policy setting should not be disabled.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Access 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Access 2013.
-By default, the user settings of Microsoft Access 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Access 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft Access 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Access 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Excel 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Excel 2013.
-By default, the user settings of Microsoft Excel 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Excel 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft Excel 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Excel 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft InfoPath 2013
-
-This policy setting configures the synchronization of user settings for Microsoft InfoPath 2013.
-By default, the user settings of Microsoft InfoPath 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft InfoPath 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft InfoPath 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft InfoPath 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Lync 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Lync 2013.
-By default, the user settings of Microsoft Lync 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Lync 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft Lync 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Lync 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 2013 Upload Center
-
-This policy setting configures the synchronization of user settings for Microsoft Office 2013 Upload Center.
-By default, the user settings of Microsoft Office 2013 Upload Center synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Office 2013 Upload Center from synchronization between computers.
-If you enable this policy setting, Microsoft Office 2013 Upload Center user settings continue to synchronize.
-If you disable this policy setting, Microsoft Office 2013 Upload Center user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft OneDrive for Business 2013
-
-This policy setting configures the synchronization of user settings for OneDrive for Business 2013.
-By default, the user settings of OneDrive for Business 2013 synchronize between computers. Use the policy setting to prevent the user settings of OneDrive for Business 2013 from synchronization between computers.
-If you enable this policy setting, OneDrive for Business 2013 user settings continue to synchronize.
-If you disable this policy setting, OneDrive for Business 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft OneNote 2013
-
-This policy setting configures the synchronization of user settings for Microsoft OneNote 2013.
-By default, the user settings of Microsoft OneNote 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft OneNote 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft OneNote 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft OneNote 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Outlook 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Outlook 2013.
-By default, the user settings of Microsoft Outlook 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Outlook 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft Outlook 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Outlook 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft PowerPoint 2013
-
-This policy setting configures the synchronization of user settings for Microsoft PowerPoint 2013.
-By default, the user settings of Microsoft PowerPoint 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft PowerPoint 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft PowerPoint 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft PowerPoint 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Project 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Project 2013.
-By default, the user settings of Microsoft Project 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Project 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft Project 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Project 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Publisher 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Publisher 2013.
-By default, the user settings of Microsoft Publisher 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Publisher 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft Publisher 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Publisher 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft SharePoint Designer 2013
-
-This policy setting configures the synchronization of user settings for Microsoft SharePoint Designer 2013.
-By default, the user settings of Microsoft SharePoint Designer 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft SharePoint Designer 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft SharePoint Designer 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft SharePoint Designer 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Visio 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Visio 2013.
-By default, the user settings of Microsoft Visio 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Visio 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft Visio 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Visio 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Word 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Word 2013.
-By default, the user settings of Microsoft Word 2013 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Word 2013 from synchronization between computers.
-If you enable this policy setting, Microsoft Word 2013 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Word 2013 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Common 2013 backup only
-
-This policy setting configures the backup of certain user settings which are common between the Microsoft Office Suite 2013 applications.
-Microsoft Office Suite 2013 has user settings which are common between applications and are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific common Microsoft Office Suite 2013 applications.
-If you enable this policy setting, certain user settings which are common between the Microsoft Office Suite 2013 applications will continue to be backed up.
-If you disable this policy setting, certain user settings which are common between the Microsoft Office Suite 2013 applications will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Access 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Access 2013.
-Microsoft Access 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Access 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft Access 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Access 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Excel 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Excel 2013.
-Microsoft Excel 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Excel 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft Excel 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Excel 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- InfoPath 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft InfoPath 2013.
-Microsoft InfoPath 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft InfoPath 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft InfoPath 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft InfoPath 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Lync 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Lync 2013.
-Microsoft Lync 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Lync 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft Lync 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Lync 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- OneNote 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft OneNote 2013.
-Microsoft OneNote 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft OneNote 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft OneNote 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft OneNote 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Outlook 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Outlook 2013.
-Microsoft Outlook 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Outlook 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft Outlook 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Outlook 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- PowerPoint 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft PowerPoint 2013.
-Microsoft PowerPoint 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft PowerPoint 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft PowerPoint 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft PowerPoint 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Project 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Project 2013.
-Microsoft Project 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Project 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft Project 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Project 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Publisher 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Publisher 2013.
-Microsoft Publisher 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Publisher 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft Publisher 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Publisher 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- SharePoint Designer 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft SharePoint Designer 2013.
-Microsoft SharePoint Designer 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft SharePoint Designer 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft SharePoint Designer 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft SharePoint Designer 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Visio 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Visio 2013.
-Microsoft Visio 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Visio 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft Visio 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Visio 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Word 2013 backup only
-
-This policy setting configures the backup of certain user settings for Microsoft Word 2013.
-Microsoft Word 2013 has user settings that are backed up instead of synchronizing between computers. Use the policy setting to suppress the backup of specific Microsoft Word 2013 settings.
-If you enable this policy setting, certain user settings of Microsoft Word 2013 will continue to be backed up.
-If you disable this policy setting, certain user settings of Microsoft Word 2013 will not be backed up.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Common 2013
-
-This policy setting configures the synchronization of user settings which are common between the Microsoft Office Suite 2013 applications.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings which are common between the Microsoft Office Suite 2013 applications will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings which are common between the Microsoft Office Suite 2013 applications from synchronization between computers with UE-V.
-If you enable this policy setting, user settings which are common between the Microsoft Office Suite 2013 applications continue to synchronize with UE-V.
-If you disable this policy setting, user settings which are common between the Microsoft Office Suite 2013 applications are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Access 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Access 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Access 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Access 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Access 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Access 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Excel 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Excel 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Excel 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Excel 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Excel 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Excel 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 InfoPath 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 InfoPath 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 InfoPath 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 InfoPath 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 InfoPath 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 InfoPath 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Lync 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Lync 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Lync 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Lync 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Lync 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Lync 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 OneNote 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 OneNote 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 OneNote 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 OneNote 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 OneNote 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 OneNote 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Outlook 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Outlook 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Outlook 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Outlook 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Outlook 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Outlook 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 PowerPoint 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 PowerPoint 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 PowerPoint 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 PowerPoint 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 PowerPoint 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 PowerPoint 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Project 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Project 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Project 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Project 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Project 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Project 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Publisher 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Publisher 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Publisher 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Publisher 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Publisher 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Publisher 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 SharePoint Designer 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 SharePoint Designer 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 SharePoint Designer 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 SharePoint Designer 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 SharePoint Designer 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 SharePoint Designer 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Visio 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Visio 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Visio 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Visio 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Visio 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Visio 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 365 Word 2013
-
-This policy setting configures the synchronization of user settings for Microsoft Office 365 Word 2013.
-Microsoft Office 365 synchronizes certain settings by default without UE-V. If the synchronization capabilities of Microsoft Office 365 are disabled, then the user settings of Microsoft Office 365 Word 2013 will synchronize between a user’s work computers with UE-V by default. Use this policy setting to prevent the user settings of Microsoft Office 365 Word 2013 from synchronization between computers with UE-V.
-If you enable this policy setting, Microsoft Office 365 Word 2013 user settings continue to sync with UE-V.
-If you disable this policy setting, Microsoft Office 365 Word 2013 user settings are excluded from synchronization with UE-V.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Office 2010 Common Settings
- This policy setting configures the synchronization of user settings which are common between the Microsoft Office Suite 2010 applications.
-By default, the user settings which are common between the Microsoft Office Suite 2010 applications synchronize between computers. Use the policy setting to prevent the user settings which are common between the Microsoft Office Suite 2010 applications from synchronization between computers.
-If you enable this policy setting, the user settings which are common between the Microsoft Office Suite 2010 applications continue to synchronize.
-If you disable this policy setting, the user settings which are common between the Microsoft Office Suite 2010 applications are excluded from the synchronization settings. If any of the Microsoft Office Suite 2010 applications are enabled, this policy setting should not be disabled
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Access 2010
- This policy setting configures the synchronization of user settings for Microsoft Access 2010.
-By default, the user settings of Microsoft Access 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Access 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft Access 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Access 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Excel 2010
- This policy setting configures the synchronization of user settings for Microsoft Excel 2010.
-By default, the user settings of Microsoft Excel 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Excel 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft Excel 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Excel 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft InfoPath 2010
- This policy setting configures the synchronization of user settings for Microsoft InfoPath 2010.
-By default, the user settings of Microsoft InfoPath 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft InfoPath 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft InfoPath 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft InfoPath 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft OneNote 2010
- This policy setting configures the synchronization of user settings for Microsoft OneNote 2010.
-By default, the user settings of Microsoft OneNote 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft OneNote 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft OneNote 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft OneNote 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Lync 2010
- This policy setting configures the synchronization of user settings for Microsoft Lync 2010.
-By default, the user settings of Microsoft Lync 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Lync 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft Lync 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Lync 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Outlook 2010
- This policy setting configures the synchronization of user settings for Microsoft Outlook 2010.
-By default, the user settings of Microsoft Outlook 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Outlook 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft Outlook 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Outlook 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft PowerPoint 2010
- This policy setting configures the synchronization of user settings for Microsoft PowerPoint 2010.
-By default, the user settings of Microsoft PowerPoint 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft PowerPoint 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft PowerPoint 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft PowerPoint 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Project 2010
- This policy setting configures the synchronization of user settings for Microsoft Project 2010.
-By default, the user settings of Microsoft Project 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Project 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft Project 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Project 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Publisher 2010
- This policy setting configures the synchronization of user settings for Microsoft Publisher 2010.
-By default, the user settings of Microsoft Publisher 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Publisher 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft Publisher 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Publisher 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft SharePoint Designer 2010
- This policy setting configures the synchronization of user settings for Microsoft SharePoint Designer 2010.
-By default, the user settings of Microsoft SharePoint Designer 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft SharePoint Designer 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft SharePoint Designer 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft SharePoint Designer 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft SharePoint Workspace 2010
- This policy setting configures the synchronization of user settings for Microsoft SharePoint Workspace 2010.
-By default, the user settings of Microsoft SharePoint Workspace 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft SharePoint Workspace 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft SharePoint Workspace 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft SharePoint Workspace 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Word 2010
- This policy setting configures the synchronization of user settings for Microsoft Word 2010.
-By default, the user settings of Microsoft Word 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Word 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft Word 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Word 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft Visio 2010
- This policy setting configures the synchronization of user settings for Microsoft Visio 2010.
-By default, the user settings of Microsoft Visio 2010 synchronize between computers. Use the policy setting to prevent the user settings of Microsoft Visio 2010 from synchronization between computers.
-If you enable this policy setting, Microsoft Visio 2010 user settings continue to synchronize.
-If you disable this policy setting, Microsoft Visio 2010 user settings are excluded from the synchronization settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- PC settings
- This policy setting configures the synchronization of user settings for PC settings.
-By default, the user settings of PC settings sync between computers. Use the policy setting to prevent the user settings of PC settings from synchronizing between computers.
-If you enable this policy setting, PC settings user settings continue to sync.
-If you disable this policy setting, PC settings user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Store
- This policy setting configures the synchronization of user settings for the Store app.
-By default, the user settings of Store sync between computers. Use the policy setting to prevent the user settings of Store from synchronizing between computers.
-If you enable this policy setting, Store user settings continue to sync.
-If you disable this policy setting, Store user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Finance
- This policy setting configures the synchronization of user settings for the Finance app.
-By default, the user settings of Finance sync between computers. Use the policy setting to prevent the user settings of Finance from synchronizing between computers.
-If you enable this policy setting, Finance user settings continue to sync.
-If you disable this policy setting, Finance user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Maps
- This policy setting configures the synchronization of user settings for the Maps app.
-By default, the user settings of Maps sync between computers. Use the policy setting to prevent the user settings of Maps from synchronizing between computers.
-If you enable this policy setting, Maps user settings continue to sync.
-If you disable this policy setting, Maps user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- News
- This policy setting configures the synchronization of user settings for the News app.
-By default, the user settings of News sync between computers. Use the policy setting to prevent the user settings of News from synchronizing between computers.
-If you enable this policy setting, News user settings continue to sync.
-If you disable this policy setting, News user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Sports
- This policy setting configures the synchronization of user settings for the Sports app.
-By default, the user settings of Sports sync between computers. Use the policy setting to prevent the user settings of Sports from synchronizing between computers.
-If you enable this policy setting, Sports user settings continue to sync.
-If you disable this policy setting, Sports user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Travel
- This policy setting configures the synchronization of user settings for the Travel app.
-By default, the user settings of Travel sync between computers. Use the policy setting to prevent the user settings of Travel from synchronizing between computers.
-If you enable this policy setting, Travel user settings continue to sync.
-If you disable this policy setting, Travel user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Weather
- This policy setting configures the synchronization of user settings for the Weather app.
-By default, the user settings of Weather sync between computers. Use the policy setting to prevent the user settings of Weather from synchronizing between computers.
-If you enable this policy setting, Weather user settings continue to sync.
-If you disable this policy setting, Weather user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Bing
- This policy setting configures the synchronization of user settings for the Bing app.
-By default, the user settings of Bing sync between computers. Use the policy setting to prevent the user settings of Bing from synchronizing between computers.
-If you enable this policy setting, Bing user settings continue to sync.
-If you disable this policy setting, Bing user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Reader
- This policy setting configures the synchronization of user settings for the Reader app.
-By default, the user settings of Reader sync between computers. Use the policy setting to prevent the user settings of Reader from synchronizing between computers.
-If you enable this policy setting, Reader user settings continue to sync.
-If you disable this policy setting, Reader user settings are excluded from the synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Mail, Calendar, People, and Messaging
- This policy setting configures the synchronization of user settings for Mail, Calendar, People, and Messaging.
-By default, the user settings of Mail, Calendar, People, and Messaging synchronize between computers. Use this policy setting to prevent the user settings of Mail, Calendar, People, and Messaging from synchronizing between computers.
-If you enable this policy setting, Mail, Calendar, People, and Messaging user settings continue to sync.
-If you disable this policy setting, Mail, Calendar, People, and Messaging user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Games
- This policy setting configures the synchronization of user settings for the Games app.
-By default, the user settings of Games sync between computers. Use the policy setting to prevent the user settings of Games from synchronizing between computers.
-If you enable this policy setting, Games user settings continue to sync.
-If you disable this policy setting, Games user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Music
- This policy setting configures the synchronization of user settings for the Music app.
-By default, the user settings of Music sync between computers. Use the policy setting to prevent the user settings of Music from synchronizing between computers.
-If you enable this policy setting, Music user settings continue to sync.
-If you disable this policy setting, Music user settings are excluded from the synchronizing settings.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Microsoft PlayReady
- This policy setting configures the synchronization of user settings for Microsoft PlayReady.
-By default, the user settings of Microsoft PlayReady sync between computers. Use the policy setting to prevent the user settings of Microsoft PlayReady from synchronizing between computers.
-If you enable this policy setting, Microsoft PlayReady user settings continue to sync.
-If you disable this policy setting, Microsoft PlayReady user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Video
- This policy setting configures the synchronization of user settings for the Video app.
-By default, the user settings of Video sync between computers. Use the policy setting to prevent the user settings of Video from synchronizing between computers.
-If you enable this policy setting, Video user settings continue to sync.
-If you disable this policy setting, Video user settings are excluded from synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Synchronize Windows settings
-
-This policy setting configures the synchronization of Windows settings between computers.
-Certain Windows settings will synchronize between computers by default. These settings include Windows themes, Windows desktop settings, Ease of Access settings, and network printers. Use this policy setting to specify which Windows settings synchronize between computers. You can also use these settings to enable synchronization of users' sign-in information for certain apps, networks, and certificates.
-If you enable this policy setting, only the selected Windows settings synchronize. Unselected Windows settings are excluded from settings synchronization.
-If you disable this policy setting, all Windows Settings are excluded from the settings synchronization.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Use User Experience Virtualization (UE-V)
- This policy setting allows you to enable or disable User Experience Virtualization (UE-V). Only applies to Windows 10 or earlier.
- Configure Sync Method
- This policy setting configures the sync provider used by User Experience Virtualization (UE-V) to sync settings between users’ computers. With Sync Method set to ”SyncProvider,” the UE-V Agent uses a built-in sync provider to keep user settings synchronized between the computer and the settings storage location. This is the default value. You can disable the sync provider on computers that never go offline and are always connected to the settings storage location.
-When SyncMethod is set to “None,” the UE-V Agent uses no sync provider. Settings are written directly to the settings storage location rather than being cached to sync later.
-Set SyncMethod to “External” when an external synchronization engine is being deployed for settings sync. This could use OneDrive, Work Folders, SharePoint or any other engine that uses a local folder to synchronize data between users’ computers. In this mode, UE-V writes settings data to the local folder specified in the settings storage path. These settings are then synchronized to other computers by an external synchronization engine. UE-V has no control over this synchronization. It only reads and writes the settings data when the normal UE-V triggers take place.
-With notifications enabled, UE-V users receive a message when the settings sync is delayed. The notification delay policy setting defines the delay before a notification appears.
-If you disable this policy setting, the sync provider is used to synchronize settings between computers and the settings storage location.
-If you do not configure this policy setting, any defined values will be deleted.
-
-
- Sync provider assembly
- This policy setting allows you to configure which assembly the User Experience Virtualization (UE-V) Agent will use for sync provider functionality.
-By default, the UE-V Agent uses the default sync provider dll. Use this policy setting to specify a different sync provider assembly to load.
-If you enable this policy setting, the UE-V Agent will attempt to load the assembly provided and will not use the default sync provider.
-If you disable this policy setting, the sync provider loads the default .
-If you do not configure this policy setting, any defined values will be deleted.
-
- Tray Icon
- This policy setting enables the User Experience Virtualization (UE-V) tray icon. By default, an icon appears in the system tray that displays notifications for UE-V. This icon also provides a link to the UE-V Agent application, Company Settings Center. Users can open the Company Settings Center by right-clicking the icon and selecting Open or by double-clicking the icon. When this group policy setting is enabled, the UE-V tray icon is visible, the UE-V notifications display, and the Company Settings Center is accessible from the tray icon.
-With this setting disabled, the tray icon does not appear in the system tray, UE-V never displays notifications, and the user cannot access Company Settings Center from the system tray. The Company Settings Center remains accessible through the Control Panel and the Start menu or Start screen.
-If you do not configure this policy setting, any defined values are deleted.
-
- Sync provider assembly
- This policy setting configures which assembly the User Experience Virtualization (UE-V) Agent uses for sync provider functionality.
-By default, the UE-V Agent uses the default sync provider. This policy setting can specify a different sync provider.
-If you enable this policy setting, the UE-V Agent attempts to load the dll provided and will not use the default sync provider.
-With this policy setting disabled, the UE-V Agent loads the default sync provider.
-If this policy setting is not configured, any defined values are deleted.
-
- Do not synchronize Windows Apps
- This policy setting defines whether the User Experience Virtualization (UE-V) Agent synchronizes settings for Windows apps.
-By default, the UE-V Agent synchronizes settings for Windows apps between the computer and the settings storage location.
-If you enable this policy setting, the UE-V Agent will not synchronize settings for Windows apps.
-If you disable this policy setting, the UE-V Agent will synchronize settings for Windows apps.
-If you do not configure this policy setting, any defined values are deleted.
-Note: If the user connects their Microsoft account for their computer then the UE-V Agent will not synchronize Windows apps. The Windows apps will default to whatever settings are configured in the Sync your settings configuration in Windows.
-
- Windows App Sync
- This policy setting configures whether User Experience Virtualization (UE-V) synchronizes settings for specified Windows apps. By default, the UE-V Agent does not synchronize settings for Windows apps. This policy setting allows you to list the Windows apps by their package family name. UE-V synchronizes the listed app settings between each user’s work computers that run the same Windows app. If you enable this policy setting and list Windows app package family names, the UE-V Agent will synchronize the settings for the listed apps.
-If you disable this policy, no Windows apps will synchronize their settings.
-If you do not configure this policy setting, any defined values are deleted.
-
- First Use Notification
- This policy setting enables a notification in the system tray that appears when the User Experience Virtualization (UE-V) Agent runs for the first time.
-By default, a notification informs users that Company Settings Center, the user-facing name for the UE-V Agent, now helps to synchronize settings between their work computers.
-With this setting enabled, the notification appears the first time that the UE-V Agent runs.
-With this setting disabled, no notification appears.
-If you do not configure this policy setting, any defined values are deleted.
-
- Sync Unlisted Windows Apps
- This policy setting defines the default settings sync behavior of the User Experience Virtualization (UE-V) Agent for Windows apps that are not explicitly listed in Windows App List.
-By default, the UE-V Agent only synchronizes settings of those Windows apps included in the Windows App List.
-With this setting enabled, the settings of all Windows apps not expressly disable in the Windows App List are synchronized.
-With this setting disabled, only the settings of the Windows apps set to synchronize in the Windows App List are synchronized.
-If you do not configure this policy setting, any defined values are deleted.
-
- Sync settings over metered connections
- This policy setting defines whether the User Experience Virtualization (UE-V) Agent synchronizes settings over metered connections.
-By default, the UE-V Agent does not synchronize settings over a metered connection.
-With this setting enabled, the UE-V Agent synchronizes settings over a metered connection.
-With this setting disabled, the UE-V Agent does not synchronize settings over a metered connection.
-If you do not configure this policy setting, any defined values are deleted.
-
- Sync settings over metered connections even when roaming
- This policy setting defines whether the User Experience Virtualization (UE-V) Agent synchronizes settings over metered connections outside of the home provider network, for example when connected via a roaming connection.
-By default, the UE-V Agent does not synchronize settings over a metered connection that is roaming.
-With this setting enabled, the UE-V Agent synchronizes settings over a metered connection that is roaming.
-With this setting disabled, the UE-V Agent will not synchronize settings over a metered connection that is roaming.
-If you do not configure this policy setting, any defined values are deleted.
-
- Contact IT Link Text
- This policy setting specifies the text of the Contact IT URL hyperlink in the Company Settings Center.
-If you enable this policy setting, the Company Settings Center displays the specified text in the link to the Contact IT URL.
-If you disable this policy setting, the Company Settings Center does not display an IT Contact link.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Contact IT URL
- This policy setting specifies the URL for the Contact IT link in the Company Settings Center.
-If you enable this policy setting, the Company Settings Center Contact IT text links to the specified URL. The link can be of any standard protocol such as http or mailto.
-If you disable this policy setting, the Company Settings Center does not display an IT Contact link.
-If you do not configure this policy setting, any defined values will be deleted.
-
- Ping the settings storage location before sync
- This policy setting allows you to configure the User Experience Virtualization (UE-V) sync provider to ping the settings storage path before attempting to sync settings. If the ping is successful then the sync provider attempts to synchronize the settings packages. If the ping is unsuccessful then the sync provider doesn’t attempt the synchronization.
-If you enable this policy setting, the sync provider pings the settings storage location before synchronizing settings packages.
-If you disable this policy setting, the sync provider doesn’t ping the settings storage location before synchronizing settings packages.
-If you do not configure this policy, any defined values will be deleted.
-
- VDI Configuration
- This policy setting configures the synchronization of User Experience Virtualization (UE-V) rollback information for computers running in a non-persistent, pooled VDI environment. UE-V settings rollback data and checkpoints are normally stored only on the local computer. With this policy setting enabled, the rollback information is copied to the settings storage location when the user logs off or shuts down their VDI session. Enable this setting to register a VDI-specific settings location template and restore data on computers in pooled VDI environments that reset to a clean state on logout. With this policy enabled you can roll settings back to the state when UE-V was installed or to “last-known-good” configurations. Only enable this policy setting on computers running in a non-persistent VDI environment. The VDI Collection Name defines the name of the virtual desktop collection containing the virtual computers.
-If you enable this policy setting, the UE-V rollback state is copied to the settings storage location on logout and restored on login.
-If you disable this policy setting, no UE-V rollback state is copied to the settings storage location.
-If you do not configure this policy, no UE-V rollback state is copied to the settings storage location.
-
- SyncProvider
- None
- External
- Enable UEV
- This policy setting allows you to enable or disable User Experience Virtualization (UE-V) feature. Reboot is needed for enable to take effect. With Auto-register inbox templates enabled, the UE-V inbox templates such as Office 2016 will be automatically registered when the UE-V Service is enabled. If this option is changed, it will only take effect when UE-V service is re-enabled.
-
-
-
- Synchronization timeout (in milliseconds):
-
-
- In the text box type a universal naming convention (UNC) path, such as \\servername\sharename.
-
-
-
-
-
- In the text box type a universal naming convention (UNC) path, such as \\servername\sharename or a folder location on the computer.
-
-
-
- Replace the default Microsoft templates
-
-
- Package size threshold (in bytes):
-
-
- Desktop settings
- Ease of access
- Themes
- Roaming Credentials
- Network Printers
-
-
-
-
-
-
-
- Sync Method:
- Enable notification
- Notification delay (in seconds):
-
-
- Type the synchronized Windows app package family names in the text box type.
-
-
-
- In the text box type a universal naming convention (UNC) path, such as \\servername\sharename\syncprovider.dll.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Auto-register inbox templates
-
-
-
-
diff --git a/policy_templates/en-US/UserProfiles.adml b/policy_templates/en-US/UserProfiles.adml
deleted file mode 100644
index 1490719..0000000
--- a/policy_templates/en-US/UserProfiles.adml
+++ /dev/null
@@ -1,432 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Add the Administrators security group to roaming user profiles
- This policy setting adds the Administrator security group to the roaming user profile share.
-
-Once an administrator has configured a user's roaming profile, the profile will be created at the user's next login. The profile is created at the location that is specified by the administrator.
-
-For the Windows XP Professional and Windows 2000 Professional operating systems, the default file permissions for the newly generated profile are full control, or read and write access for the user, and no file access for the administrators group.
-
-By configuring this policy setting, you can alter this behavior.
-
-If you enable this policy setting, the administrator group is also given full control to the user's profile folder.
-
-If you disable or do not configure this policy setting, only the user is given full control of their user profile, and the administrators group has no file system access to this folder.
-
-Note: If the policy setting is enabled after the profile is created, the policy setting has no effect.
-
-Note: The policy setting must be configured on the client computer, not the server, for it to have any effect, because the client computer sets the file share permissions for the roaming profile at creation time.
-
-Note: In the default case, administrators have no file access to the user's profile, but they may still take ownership of this folder to grant themselves file permissions.
-
-Note: The behavior when this policy setting is enabled is exactly the same behavior as in Windows NT 4.0.
- Do not check for user ownership of Roaming Profile Folders
- This policy setting disables the more secure default setting for the user's roaming user profile folder.
-
-After an administrator has configured a user's roaming profile, the profile will be created at the user's next login. The profile is created at the location that is specified by the administrator.
-
-For Windows 2000 Professional pre-SP4 and Windows XP pre-SP1 operating systems, the default file permissions for the newly generated profile are full control access for the user and no file access for the administrators group. No checks are made for the correct permissions if the profile folder already exists. For Windows Server 2003 family, Windows 2000 Professional SP4 and Windows XP SP1, the default behavior is to check the folder for the correct permissions if the profile folder already exists, and not copy files to or from the roaming folder if the permissions are not correct.
-
-By configuring this policy setting, you can alter this behavior.
-
-If you enable this policy setting Windows will not check the permissions for the folder in the case where the folder exists.
-
-If you disable or do not configure this policy setting AND the roaming profile folder exists AND the user or administrators group are not the owner of the folder, Windows will not copy files to or from the roaming folder. The user will be shown an error message and an entry will be written to the event log. The user's cached profile will be used, or a temporary profile issued if no cached profile exists.
-
-Note: The policy setting must be configured on the client computer not the server for it to have any effect because the client computer sets the file share permissions for the roaming profile at creation time.
-
-Note: The behavior when this policy setting is enabled is exactly the same behavior as in Windows 2000 Professional pre-SP4 and Windows XP Professional.
- Connect home directory to root of the share
- This policy setting restores the definitions of the %HOMESHARE% and %HOMEPATH% environment variables to those used in Windows NT 4.0 and earlier. Along with %HOMEDRIVE%, these variables define the home directory of a user profile. The home directory is a persistent mapping of a drive letter on the local computer to a local or remote directory.
-
-If you enable this policy setting, the system uses the Windows NT 4.0 definitions. %HOMESHARE% stores only the network share (such as \\server\share). %HOMEPATH% stores the remainder of the fully qualified path to the home directory (such as \dir1\dir2\homedir). As a result, users can access any directory on the home share by using the home directory drive letter.
-
-If you disable or do not configure this policy setting, the system uses the definitions introduced with Windows 2000. %HOMESHARE% stores the fully qualified path to the home directory (such as \\server\share\dir1\dir2\homedir). Users can access the home directory and any of its subdirectories from the home drive letter, but they cannot see or access its parent directories. %HOMEPATH% stores a final backslash and is included for compatibility with earlier systems.
- Delete cached copies of roaming profiles
- This policy setting determines whether Windows keeps a copy of a user's roaming profile on the local computer's hard drive when the user logs off.
-
-Roaming profiles reside on a network server. By default, when users with roaming profiles log off, the system also saves a copy of their roaming profile on the hard drive of the computer they are using in case the server that stores the roaming profile is unavailable when the user logs on again. The local copy is also used when the remote copy of the roaming user profile is slow to load.
-
-If you enable this policy setting, any local copies of the user's roaming profile are deleted when the user logs off. The roaming profile still remains on the network server that stores it.
-
-If you disable or do not configure this policy setting, Windows keeps a copy of a user's roaming profile on the local computer's hard drive when the user logs off.
-
-Important: Do not enable this policy setting if you are using the slow link detection feature. To respond to a slow link, the system requires a local copy of the user's roaming profile.
- Disable detection of slow network connections
- This policy setting disables the detection of slow network connections.
-
-Slow link detection measures the speed of the connection between a user's computer and the remote server that stores the roaming user profile. When the system detects a slow link, the related policy settings in this folder tell the computer how to respond.
-
-If you enable this policy setting, the system does not detect slow connections or recognize any connections as being slow. As a result, the system does not respond to slow connections to user profiles, and it ignores the policy settings that tell the system how to respond to a slow connection.
-
-If you disable this policy setting or do not configure it, slow link detection is enabled. The system measures the speed of the connection between the user's computer and profile server. If the connection is slow (as defined by the "Slow network connection timeout for user profiles" policy setting), the system applies the other policy settings set in this folder to determine how to proceed. By default, when the connection is slow, the system loads the local copy of the user profile.
- Prompt user when a slow network connection is detected
- This policy setting provides users with the ability to download their roaming profile, even when a slow network connection with their roaming profile server is detected.
-
-If you enable this policy setting, users will be allowed to define whether they want their roaming profile to be downloaded when a slow link with their roaming profile server is detected.
-
-In operating systems earlier than Microsoft Windows Vista, a dialog box will be shown to the user during logon if a slow network connection is detected. The user then is able to choose to download the remote copy of the user profile. In Microsoft Windows Vista, a check box appears on the logon screen and the user must choose whether to download the remote user profile before Windows detects the network connection speed.
-
-If you disable or do not configure this policy setting, the system does not consult the user. Instead, the system uses the local copy of the user profile. If you have enabled the "Wait for remote user profile" policy setting, the system downloads the remote copy of the user profile without consulting the user. In Microsoft Windows Vista, the system will ignore the user choice made on the logon screen.
-
-Note: This policy setting and related policy settings in this folder define the system's response when roaming user profiles are slow to download. To adjust the time within which the user must respond to this notice in operating systems earlier than Microsoft Windows Vista, use the "Timeout for dialog boxes" policy setting.
-
-Important: If the "Do not detect slow network connections" setting is enabled, this policy setting is ignored. Also, if the "Delete cached copies of roaming profiles" policy setting is enabled, there is no local copy of the roaming profile to load when the system detects a slow connection.
- Exclude directories in roaming profile
- This policy setting lets you exclude folders that are normally included in the user's profile. As a result, these folders do not need to be stored by the network server on which the profile resides and do not follow users to other computers.
-
-Note: When excluding content from the profile you should try to exclude the narrowest set of data that will address your needs. For example, if there is one application with data that should not be roamed then add only that application's specific folder under the AppData\Roaming folder rather than all of the AppData\Roaming folder to the exclusion list.
-
-By default, the Appdata\Local and Appdata\LocalLow folders and all their subfolders such as the History, Temp, and Temporary Internet Files folders are excluded from the user's roaming profile.
-
-In operating systems earlier than Microsoft Windows Vista, only the History, Local Settings, Temp, and Temporary Internet Files folders are excluded from the user's roaming profile by default.
-
-If you enable this policy setting, you can exclude additional folders.
-
-If you disable this policy setting or do not configure it, only the default folders are excluded.
-
-Note: You cannot use this policy setting to include the default folders in a roaming user profile.
- Leave Windows Installer and Group Policy Software Installation Data
- This policy setting determines whether the system retains a roaming user's Windows Installer and Group Policy based software installation data on their profile deletion.
-
-By default Windows deletes all information related to a roaming user (which includes the user's settings, data, Windows Installer related data, and the like) when their profile is deleted. As a result, the next time a roaming user whose profile was previously deleted on that client logs on, they will need to reinstall all apps published via policy at logon increasing logon time. You can use this policy setting to change this behavior.
-
-If you enable this policy setting, Windows will not delete Windows Installer or Group Policy software installation data for roaming users when profiles are deleted from the machine. This will improve the performance of Group Policy based Software Installation during user logon when a user profile is deleted and that user subsequently logs on to the machine.
-
-If you disable or do not configure this policy setting, Windows will delete the entire profile for roaming users, including the Windows Installer and Group Policy software installation data when those profiles are deleted.
-
-Note: If this policy setting is enabled for a machine, local administrator action is required to remove the Windows Installer or Group Policy software installation data stored in the registry and file system of roaming users' profiles on the machine.
- Limit profile size
- This policy setting sets the maximum size of each user profile and determines the system's response when a user profile reaches the maximum size. This policy setting affects both local and roaming profiles.
-
-If you disable this policy setting or do not configure it, the system does not limit the size of user profiles.
-
-If you enable this policy setting, you can:
-
--- Set a maximum permitted user profile size.
--- Determine whether the registry files are included in the calculation of the profile size.
--- Determine whether users are notified when the profile exceeds the permitted maximum size.
--- Specify a customized message notifying users of the oversized profile.
--- Determine how often the customized message is displayed.
-
-Note: In operating systems earlier than Microsoft Windows Vista, Windows will not allow users to log off until the profile size has been reduced to within the allowable limit. In Microsoft Windows Vista, Windows will not block users from logging off. Instead, if the user has a roaming user profile, Windows will not synchronize the user's profile with the roaming profile server if the maximum profile size limit specified here is exceeded.
- Only allow local user profiles
- This setting determines if roaming user profiles are available on a particular computer. By default, when roaming profile users log on to a computer, their roaming profile is copied down to the local computer. If they have already logged on to this computer in the past, the roaming profile is merged with the local profile. Similarly, when the user logs off this computer, the local copy of their profile, including any changes they have made, is merged with the server copy of their profile.
-
-Using the setting, you can prevent users configured to use roaming profiles from receiving their profile on a specific computer.
-
-If you enable this setting, the following occurs on the affected computer: At first logon, the user receives a new local profile, rather than the roaming profile. At logoff, changes are saved to the local profile. All subsequent logons use the local profile.
-
-If you disable this setting or do not configure it, the default behavior occurs, as indicated above.
-
-If you enable both the "Prevent Roaming Profile changes from propagating to the server" setting and the "Only allow local user profiles" setting, roaming profiles are disabled.
-
-Note: This setting only affects roaming profile users.
- Establish timeout value for dialog boxes
- This policy setting controls how long Windows waits for a user response before it uses a default user profile for roaming user profiles.
-
-The default user profile is applied when the user does not respond to messages explaining that any of the following events has occurred:
-
--- The system detects a slow connection between the user's computer and the server that stores users' roaming user profiles.
-
--- The system cannot access users' server-based profiles when users log on or off.
-
--- Users' local profiles are newer than their server-based profiles.
-
-If you enable this policy setting, you can override the amount of time Windows waits for user input before using a default user profile for roaming user profiles. The default timeout value is 30 seconds. To use this policy setting, type the number of seconds Windows should wait for user input. The minumum value is 0 seconds, and the maximum is 600 seconds.
-
-If you disable or do not configure this policy setting, Windows waits 30 seconds for user input before applying the default user profile .
- Do not log users on with temporary profiles
- This policy setting will automatically log off a user when Windows cannot load their profile.
-
-If Windows cannot access the user profile folder or the profile contains errors that prevent it from loading, Windows logs on the user with a temporary profile. This policy setting allows the administrator to disable this behavior, preventing Windows from loggin on the user with a temporary profile.
-
-If you enable this policy setting, Windows will not log on a user with a temporary profile. Windows logs the user off if their profile cannot be loaded.
-
-If you disable this policy setting or do not configure it, Windows logs on the user with a temporary profile when Windows cannot load their user profile.
-
-Also, see the "Delete cached copies of roaming profiles" policy setting.
- Maximum retries to unload and update user profile
- This policy setting determines how many times the system tries to unload and update the registry portion of a user profile. When the number of trials specified by this policy setting is exhausted, the system stops trying. As a result, the user profile might not be current, and local and roaming user profiles might not match.
-
-When a user logs off of the computer, the system unloads the user-specific section of the registry (HKEY_CURRENT_USER) into a file (NTUSER.DAT) and updates it. However, if another program or service is reading or editing the registry, the system cannot unload it. The system tries repeatedly (at a rate of once per second) to unload and update the registry settings. By default, the system repeats its periodic attempts 60 times (over the course of one minute).
-
-If you enable this policy setting, you can adjust the number of times the system tries to unload and update the user's registry settings. (You cannot adjust the retry rate.)
-
-If you disable this policy setting or do not configure it, the system repeats its attempt 60 times.
-
-If you set the number of retries to 0, the system tries just once to unload and update the user's registry settings. It does not try again.
-
-Note: This policy setting is particularly important to servers running Remote Desktop Services. Because Remote Desktop Services edits the users' registry settings when they log off, the system's first few attempts to unload the user settings are more likely to fail.
-
-This policy setting does not affect the system's attempts to update the files in the user profile.
-
-Tip: Consider increasing the number of retries specified in this policy setting if there are many user profiles stored in the computer's memory. This indicates that the system has not been able to unload the profile.
-
-Also, check the Application Log in Event Viewer for events generated by Userenv. The system records an event whenever it tries to unload the registry portion of the user profile. The system also records an event when it fails to update the files in a user profile.
- Prevent Roaming Profile changes from propagating to the server
- This policy setting determines if the changes a user makes to their roaming profile are merged with the server copy of their profile.
-
-By default, when a user with a roaming profile logs on to a computer, the roaming profile is copied down to the local computer. If the user has logged on to the computer in the past, the roaming profile is merged with the local profile. Similarly, when the user logs off the computer, the local copy of their profile, including any changes, is merged with the server copy of the profile.
-
-Using this policy setting, you can prevent changes made to a roaming profile on a particular computer from being persisted.
-
-If you enable this policy setting, changes a user makes to their roaming profile aren't merged with the server (roaming) copy when the user logs off.
-
-If you disable or not configure this policy setting, the default behavior occurs, as indicated above.
-
-Note: This policy setting only affects roaming profile users.
- Wait for remote user profile
- This policy setting directs the system to wait for the remote copy of the roaming user profile to load, even when loading is slow. Also, the system waits for the remote copy when the user is notified about a slow connection, but does not respond in the time allowed.
-
-This policy setting and related policy settings in this folder together define the system's response when roaming user profiles are slow to load.
-
-If you enable this policy setting, the system waits for the remote copy of the roaming user profile to load, even when loading is slow.
-
-If you disable this policy setting or do not configure it, when a remote profile is slow to load, the system loads the local copy of the roaming user profile. The local copy is also used when the user is consulted (as set in the "Prompt user when slow link is detected" policy setting), but does not respond in the time allowed (as set in the "Timeout for dialog boxes" policy setting).
-
-Waiting for the remote profile is appropriate when users move between computers frequently and the local copy of their profile is not always current. Using the local copy is desirable when quick logging on is a priority.
-
-Important: If the "Do not detect slow network connections" policy setting is enabled, this policy setting is ignored. Also, if the "Delete cached copies of roaming profiles" policy setting is enabled, there is no local copy of the roaming profile to load when the system detects a slow connection.
- Control slow network connection timeout for user profiles
- This policy setting defines a slow connection for roaming user profiles and establishes thresholds for two tests of network speed.
-
-To determine the network performance characteristics, a connection is made to the file share storing the user's profile and 64 kilobytes of data is transfered. From that connection and data transfer, the network's latency and connection speed are determined.
-
-This policy setting and related policy settings in this folder together define the system's response when roaming user profiles are slow to load.
-
-If you enable this policy setting, you can change how long Windows waits for a response from the server before considering the connection to be slow.
-
-If you disable or do not configure this policy setting, Windows considers the network connection to be slow if the server returns less than 500 kilobits of data per second or take 120 milliseconds to respond.Consider increasing this value for clients using DHCP Service-assigned addresses or for computers accessing profiles across dial-up connections.Important: If the "Do not detect slow network connections" policy setting is enabled, this policy setting is ignored. Also, if the "Delete cached copies of roaming profiles" policy setting is enabled, there is no local copy of the roaming profile to load when the system detects a slow connection.
- User Profiles
- Delete user profiles older than a specified number of days on system restart
- This policy setting allows an administrator to automatically delete user profiles on system restart that have not been used within a specified number of days. Note: One day is interpreted as 24 hours after a specific user profile was accessed.
-
-If you enable this policy setting, the User Profile Service will automatically delete on the next system restart all user profiles on the computer that have not been used within the specified number of days.
-
-If you disable or do not configure this policy setting, User Profile Service will not automatically delete any profiles on the next system restart.
- Specify network directories to sync at logon/logoff time only
- This policy setting allows you to specify which network directories will be synchronized only at logon and logoff via Offline Files. This policy setting is meant to be used in conjunction with Folder Redirection, to help resolve issues with applications that do not work well with Offline Files while the user is online.
-
-If you enable this policy setting, the network paths specified in this policy setting will be synchronized only by Offline Files during user logon and logoff, and will be taken offline while the user is logged on.
-
-If you disable or do not configure this policy setting, the paths specified in this policy setting will behave like any other cached data via Offline Files and continue to remain online while the user is logged on, if the network paths are accessible.
-
-Note: You should not use this policy setting to suspend any of the root redirected folders such as Appdata\Roaming, Start Menu, and Documents. You should suspend only the subfolders of these parent folders.
- Do not forcefully unload the users registry at user logoff
- This policy setting controls whether Windows forcefully unloads the user's registry at logoff, even if there are open handles to the per-user registry keys.
-
-Note: This policy setting should only be used for cases where you may be running into application compatibility issues due to this specific Windows behavior. It is not recommended to enable this policy by default as it may prevent users from getting an updated version of their roaming user profile.
-
-If you enable this policy setting, Windows will not forcefully unload the users registry at logoff, but will unload the registry when all open handles to the per-user registry keys are closed.
-
-If you disable or do not configure this policy setting, Windows will always unload the users registry at logoff, even if there are any open handles to the per-user registry keys at user logoff.
- Set maximum wait time for the network if a user has a roaming user profile or remote home directory
- This policy setting controls how long Windows waits for a response from the network before logging on a user without a remote home directory and withou synchronizing roaming user profiles. This policy setting is useful for the cases in which a network might take typically longer to initialize, such as with a wireless network.
-
-Note: Windows doesn't wait for the network if the physical network connection is not available on the computer (if the media is disconnected or the network adapter is not available).
-
-If you enable this policy setting, Windows waits for the network to become available up to the maximum wait time specified in this policy setting. Setting the value to zero causes Windows to proceed without waiting for the network.
-
-If you disable or do not configure this policy setting, Windows waits for the network for a maximum of 30 seconds.
- Set roaming profile path for all users logging onto this computer
- This policy setting specifies whether Windows should use the specified network path as the roaming user profile path for all users logging onto this computer.
-
-To use this policy setting, type the path to the network share in the form \\Computername\Sharename\. It is recommended to use a path such as \\Computername\Sharename\%USERNAME% to give each user an individual profile folder. If not specified, all users logging onto this computer will use the same roaming profile folder as specified by this policy. You need to ensure that you have set the appropriate security on the folder to allow all users to access the profile.
-
-If you enable this policy setting, all users logging on this computer will use the roaming profile path specified in this policy.
-
-If you disable or do not configure this policy setting, users logging on this computer will use their local profile or standard roaming user profile.
-
-Note: There are four ways to configure a roaming profile for a user. Windows reads profile configuration in the following order and uses the first configured policy setting it reads.
-
-1. Terminal Services roaming profile path specified by Terminal Services policy
-2. Terminal Services roaming profile path specified by the user object
-3. A per-computer roaming profile path specified in this policy
-4. A per-user roaming profile path specified in the user object
- Set the schedule for background upload of a roaming user profile's registry file while user is logged on
- This policy setting sets the schedule for background uploading of a roaming user profile's registry file (ntuser.dat). This policy setting controls only the uploading of a roaming user profile's registry file (other user data and regular profiles are not be uploaded) and uploads it only if the user is logged on. This policy setting does not stop the roaming user profile's registry file from being uploaded at user logoff.
-
-If "Run at set interval" is chosen, then an interval must be set, with a value of 1-720 hours. Once set, Windows uploads the profile's registry file at the specified interval after the user logs on. For example, with a value of 6 hours, the registry file of the roaming user profile is uploaded to the server every six hours while the user is logged on.
-
-If "Run at specified time of day" is chosen, then a time of day must be specified. Once set, Windows uploads the registry file at the same time every day, as long as the user is logged on.
-
-For both scheduling options, there is a random one hour delay attached per-trigger to avoid overloading the server with simultaneous uploads. For example, if the settings dictate that the user's registry file is to be uploaded at 6pm, it will actually upload at a random time between 6pm and 7pm.
-
-Note: If "Run at set interval" is selected, the "Time of day" option is disregarded. Likewise, if "Run at set time of day" is chosen, the "Interval (hours)" option is disregarded.
-
-If you enable this policy setting, Windows uploads the registry file of the user's roaming user profile in the background according to the schedule set here while the user is logged on. Regular profiles are not affected.
-
-If this setting is disabled or not configured, the registry file for a roaming user profile will not be uploaded in the background while the user is logged on.
-
- Run at set interval
- Run at specified time of day
- 00:00
- 01:00
- 02:00
- 03:00
- 04:00
- 05:00
- 06:00
- 07:00
- 08:00
- 09:00
- 10:00
- 11:00
- 12:00
- 13:00
- 14:00
- 15:00
- 16:00
- 17:00
- 18:00
- 19:00
- 20:00
- 21:00
- 22:00
- 23:00
- User management of sharing user name, account picture, and domain information with apps (not desktop apps)
- This setting prevents users from managing the ability to allow apps to access the user name, account picture, and domain information.
-
-If you enable this policy setting, sharing of user name, picture and domain information may be controlled by setting one of the following options:
-
-"Always on" - users will not be able to change this setting and the user's name and account picture will be shared with apps (not desktop apps). In addition apps (not desktop apps) that have the enterprise authentication capability will also be able to retrieve the user's UPN, SIP/URI, and DNS.
-
-"Always off" - users will not be able to change this setting and the user's name and account picture will not be shared with apps (not desktop apps). In addition apps (not desktop apps) that have the enterprise authentication capability will not be able to retrieve the user's UPN, SIP/URI, and DNS. Selecting this option may have a negative impact on certain enterprise software and/or line of business apps that depend on the domain information protected by this setting to connect with network resources.
-
-If you do not configure or disable this policy the user will have full control over this setting and can turn it off and on. Selecting this option may have a negative impact on certain enterprise software and/or line of business apps that depend on the domain information protected by this setting to connect with network resources if users choose to turn the setting off.
-
- Always on
- Always off
- Turn off the advertising ID
- This policy setting turns off the advertising ID, preventing apps from using the ID for experiences across apps.
-
-If you enable this policy setting, the advertising ID is turned off. Apps can't use the ID for experiences across apps.
-
-If you disable or do not configure this policy setting, users can control whether apps can use the advertising ID for experiences across apps.
-
- Download roaming profiles on primary computers only
- This policy setting controls on a per-computer basis whether roaming profiles are downloaded on a user's primary computers only. This policy setting is useful to improve logon performance and to increase security for user data on computers where the user might not want to download private data, such as on a meeting room computer or on a computer in a remote office.
-
-To designate a user's primary computers, an administrator must use management software or a script to add primary computer attributes to the user's account in Active Directory Domain Services (AD DS). This policy setting also requires the Windows Server 2012 version of the Active Directory schema to function.
-
-If you enable this policy setting and the user has a roaming profile, the roaming profile is downloaded on the user's primary computer only.
-
-If you disable or do not configure this policy setting and the user has a roaming profile, the roaming profile is downloaded on every computer that the user logs on to.
-
- Set user home folder
- This policy setting allows you to specify the location and root (file share or local path) of a user's home folder for a logon session.
-
-If you enable this policy setting, the user's home folder is configured to the specified local or network location, creating a new folder for each user name.
-
-To use this policy setting, in the Location list, choose the location for the home folder. If you choose “On the network,” enter the path to a file share in the Path box (for example, \\ComputerName\ShareName), and then choose the drive letter to assign to the file share. If you choose “On the local computer,” enter a local path (for example, C:\HomeFolder) in the Path box.
-
-Do not specify environment variables or ellipses in the path. Also, do not specify a placeholder for the user name because the user name will be appended at logon.
-
-Note: The Drive letter box is ignored if you choose “On the local computer” from the Location list. If you choose “On the local computer” and enter a file share, the user's home folder will be placed in the network location without mapping the file share to a drive letter.
-
-If you disable or do not configure this policy setting, the user's home folder is configured as specified in the user's Active Directory Domain Services account.
-
-If the "Set Remote Desktop Services User Home Directory" policy setting is enabled, the “Set user home folder” policy setting has no effect.
- On the local computer
- On the network
- G:
- H:
- I:
- J:
- K:
- L:
- M:
- N:
- O:
- P:
- Q:
- R:
- S:
- T:
- U:
- V:
- W:
- X:
- Y:
- Z:
-
-
-
-
-
-
- You can enter multiple directory names, semi-colon separated,
- all relative to the root of the user's profile
-
-
-
-
- You have exceeded your profile storage space. Before you can log off, you need to move some items from your profile to network or local storage.
-
- Max Profile size (KB)
- Show registry files in the file list
- Notify user when profile storage space is exceeded.
- Remind user every X minutes:
-
-
- Time (seconds)
-
-
- Max retries:
-
-
- Connection speed (Kbps):
- Time (milliseconds)
-
-
- Delete user profiles older than (days)
-
-
-
-
-
- You can enter multiple directory names, semi-colon separated.
-
-
- Wait for network for maximum (seconds)
-
-
-
-
-
- It is recommended to add %USERNAME% in the path to give each user different profile directory.
-
-
- Scheduling method:
- The following settings are only required and applicable
- if "Run at set interval" is selected.
- Interval (hours):
- The following settings are only required and applicable
- if "Run at specified time of day" is selected.
- Time of day:
-
-
- Allow apps (not desktop apps) to have access to the user name, account picture, and domain information.
-
- Action:
-
- Always on = locks the setting on
- Always off = locks the setting off
-
-
- Location:
-
-
-
- If you chose "On the Network," specify the drive letter for the mapped drive.
- Drive letter
-
-
-
-
diff --git a/policy_templates/en-US/VolumeEncryption.adml b/policy_templates/en-US/VolumeEncryption.adml
deleted file mode 100644
index 0f936bd..0000000
--- a/policy_templates/en-US/VolumeEncryption.adml
+++ /dev/null
@@ -1,1036 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- This policy setting allows you to manage the Active Directory Domain Services (AD DS) backup of BitLocker Drive Encryption recovery information. This provides an administrative method of recovering data encrypted by BitLocker to prevent data loss due to lack of key information. This policy setting is only applicable to computers running Windows Server 2008 or Windows Vista.
-
-If you enable this policy setting, BitLocker recovery information is automatically and silently backed up to AD DS when BitLocker is turned on for a computer. This policy setting is applied when you turn on BitLocker.
-
-Note: You might need to set up appropriate schema extensions and access control settings on the domain before AD DS backup can succeed. More information about setting up AD DS backup for BitLocker is available on Microsoft TechNet.
-
-BitLocker recovery information includes the recovery password and some unique identifier data. You can also include a package that contains a BitLocker-protected drive's encryption key. This key package is secured by one or more recovery passwords and may help perform specialized recovery when the disk is damaged or corrupted.
-
-If you select the option to "Require BitLocker backup to AD DS" BitLocker cannot be turned on unless the computer is connected to the domain and the backup of BitLocker recovery information to AD DS succeeds. This option is selected by default to help ensure that BitLocker recovery is possible. If this option is not selected, AD DS backup is attempted but network or other backup failures do not prevent BitLocker setup. Backup is not automatically retried and the recovery password may not have been stored in AD DS during BitLocker setup.
-
-If you disable or do not configure this policy setting, BitLocker recovery information is not backed up to AD DS.
-
-Note: Trusted Platform Module (TPM) initialization might occur during BitLocker setup. Enable the "Turn on TPM backup to Active Directory Domain Services" policy setting in System\Trusted Platform Module Services to ensure that TPM information is also backed up.
-
- Store BitLocker recovery information in Active Directory Domain Services (Windows Server 2008 and Windows Vista)
- Recovery passwords and key packages
- Recovery passwords only
-
- This policy setting allows you to control whether the BitLocker Drive Encryption setup wizard will be able to set up an additional authentication method that is required each time the computer starts. This policy setting is applied when you turn on BitLocker.
-
-Note: This policy is only applicable to computers running Windows Server 2008 or Windows Vista.
-
-On a computer with a compatible Trusted Platform Module (TPM), two authentication methods can be used at startup to provide added protection for encrypted data. When the computer starts, it can require users to insert a USB flash drive containing a startup key. It can also require users to enter a 4-digit to 20-digit startup personal identification number (PIN).
-
-A USB flash drive containing a startup key is needed on computers without a compatible TPM. Without a TPM, BitLocker-encrypted data is protected solely by the key material on this USB flash drive.
-
-If you enable this policy setting, the wizard will display the page to allow the user to configure advanced startup options for BitLocker. You can further configure setting options for computers with and without a TPM.
-
-If you disable or do not configure this policy setting, the BitLocker setup wizard will display basic steps that allow users to turn on BitLocker on computers with a TPM. In this basic wizard, no additional startup key or startup PIN can be configured.
-
-
- Require additional authentication at startup (Windows Server 2008 and Windows Vista)
- Require additional authentication at startup
-
- This policy setting allows you to configure whether BitLocker requires additional authentication each time the computer starts and whether you are using BitLocker with or without a Trusted Platform Module (TPM). This policy setting is applied when you turn on BitLocker.
-
-Note: Only one of the additional authentication options can be required at startup, otherwise a policy error occurs.
-
-If you want to use BitLocker on a computer without a TPM, select the "Allow BitLocker without a compatible TPM" check box. In this mode either a password or a USB drive is required for start-up. When using a startup key, the key information used to encrypt the drive is stored on the USB drive, creating a USB key. When the USB key is inserted the access to the drive is authenticated and the drive is accessible. If the USB key is lost or unavailable or if you have forgotten the password then you will need to use one of the BitLocker recovery options to access the drive.
-
-On a computer with a compatible TPM, four types of authentication methods can be used at startup to provide added protection for encrypted data. When the computer starts, it can use only the TPM for authentication, or it can also require insertion of a USB flash drive containing a startup key, the entry of a 6-digit to 20-digit personal identification number (PIN), or both.
-
-If you enable this policy setting, users can configure advanced startup options in the BitLocker setup wizard.
-
-If you disable or do not configure this policy setting, users can configure only basic options on computers with a TPM.
-
-Note: If you want to require the use of a startup PIN and a USB flash drive, you must configure BitLocker settings using the command-line tool manage-bde instead of the BitLocker Drive Encryption setup wizard.
-
-
- Allow network unlock at startup
- This policy setting controls whether a BitLocker-protected computer that is connected to a trusted wired Local Area Network (LAN) and joined to a domain can create and use Network Key Protectors on TPM-enabled computers to automatically unlock the operating system drive when the computer is started.
-
-If you enable this policy, clients configured with a BitLocker Network Unlock certificate will be able to create and use Network Key Protectors.
-
-To use a Network Key Protector to unlock the computer, both the computer and the BitLocker Drive Encryption Network Unlock server must be provisioned with a Network Unlock certificate. The Network Unlock certificate is used to create Network Key Protectors, and protects the information exchanged with the server to unlock the computer. You can use the group policy setting "Computer Configuration\Windows Settings\Security Settings\Public Key Policies\BitLocker Drive Encryption Network Unlock Certificate" on the domain controller to distribute this certificate to computers in your organization. This unlock method uses the TPM on the computer, so computers that do not have a TPM cannot create Network Key Protectors to automatically unlock with Network Unlock.
-
-If you disable or do not configure this policy setting, BitLocker clients will not be able to create and use Network Key Protectors.
-
-Note: For reliability and security, computers should also have a TPM startup PIN that can be used when the computer is disconnected from the wired network or the server at startup.
-
-
-
- Allow startup key and PIN with TPM
- Require startup key and PIN with TPM
- Do not allow startup key and PIN with TPM
-
- Allow TPM
- Require TPM
- Do not allow TPM
-
- Allow startup PIN with TPM
- Require startup PIN with TPM
- Do not allow startup PIN with TPM
-
- Allow startup key with TPM
- Require startup key with TPM
- Do not allow startup key with TPM
-
-
- This policy setting allows you to control whether the BitLocker Drive Encryption setup wizard can display and specify BitLocker recovery options. This policy is only applicable to computers running Windows Server 2008 or Windows Vista. This policy setting is applied when you turn on BitLocker.
-
-Two recovery options can be used to unlock BitLocker-encrypted data in the absence of the required startup key information. The user either can type a 48-digit numerical recovery password or insert a USB flash drive containing a 256-bit recovery key.
-
-If you enable this policy setting, you can configure the options that the setup wizard displays to users for recovering BitLocker encrypted data. Saving to a USB flash drive will store the 48-digit recovery password as a text file and the 256-bit recovery key as a hidden file. Saving to a folder will store the 48-digit recovery password as a text file. Printing will send the 48-digit recovery password to the default printer. For example, not allowing the 48-digit recovery password will prevent users from being able to print or save recovery information to a folder.
-
-If you disable or do not configure this policy setting, the BitLocker setup wizard will present users with ways to store recovery options.
-
-Note: If Trusted Platform Module (TPM) initialization is needed during the BitLocker setup, TPM owner information will be saved or printed with the BitLocker recovery information.
-
-Note: The 48-digit recovery password will not be available in FIPS-compliance mode.
-
-Important: This policy setting provides an administrative method of recovering data encrypted by BitLocker to prevent data loss due to lack of key information. If you do not allow both user recovery options you must enable the "Store BitLocker recovery information in Active Directory Domain Services (Windows Server 2008 and Windows Vista)" policy setting to prevent a policy error.
-
-
-
- Choose how users can recover BitLocker-protected drives (Windows Server 2008 and Windows Vista)
- Require recovery password (default)
- Do not allow recovery password
-
- Require recovery key (default)
- Do not allow recovery key
-
-
- Choose how BitLocker-protected operating system drives can be recovered
-
- This policy setting allows you to control how BitLocker-protected operating system drives are recovered in the absence of the required startup key information. This policy setting is applied when you turn on BitLocker.
-
-The "Allow certificate-based data recovery agent" check box is used to specify whether a data recovery agent can be used with BitLocker-protected operating system drives. Before a data recovery agent can be used it must be added from the Public Key Policies item in either the Group Policy Management Console or the Local Group Policy Editor. Consult the BitLocker Drive Encryption Deployment Guide on Microsoft TechNet for more information about adding data recovery agents.
-
-In "Configure user storage of BitLocker recovery information" select whether users are allowed, required, or not allowed to generate a 48-digit recovery password or a 256-bit recovery key.
-
-Select "Omit recovery options from the BitLocker setup wizard" to prevent users from specifying recovery options when they turn on BitLocker on a drive. This means that you will not be able to specify which recovery option to use when you turn on BitLocker, instead BitLocker recovery options for the drive are determined by the policy setting.
-
-In "Save BitLocker recovery information to Active Directory Domain Services", choose which BitLocker recovery information to store in AD DS for operating system drives. If you select "Backup recovery password and key package", both the BitLocker recovery password and key package are stored in AD DS. Storing the key package supports recovering data from a drive that has been physically corrupted. If you select "Backup recovery password only," only the recovery password is stored in AD DS.
-
-Select the "Do not enable BitLocker until recovery information is stored in AD DS for operating system drives" check box if you want to prevent users from enabling BitLocker unless the computer is connected to the domain and the backup of BitLocker recovery information to AD DS succeeds.
-
-Note: If the "Do not enable BitLocker until recovery information is stored in AD DS for operating system drives" check box is selected, a recovery password is automatically generated.
-
-If you enable this policy setting, you can control the methods available to users to recover data from BitLocker-protected operating system drives.
-
-If this policy setting is disabled or not configured, the default recovery options are supported for BitLocker recovery. By default a DRA is allowed, the recovery options can be specified by the user including the recovery password and recovery key, and recovery information is not backed up to AD DS.
-
-
-
- Require 48-digit recovery password
- Allow 48-digit recovery password
- Do not allow 48-digit recovery password
-
- Require 256-bit recovery key
- Do not allow 256-bit recovery key
- Allow 256-bit recovery key
-
- Choose how BitLocker-protected fixed drives can be recovered
- This policy setting allows you to control how BitLocker-protected fixed data drives are recovered in the absence of the required credentials. This policy setting is applied when you turn on BitLocker.
-
-The "Allow data recovery agent" check box is used to specify whether a data recovery agent can be used with BitLocker-protected fixed data drives. Before a data recovery agent can be used it must be added from the Public Key Policies item in either the Group Policy Management Console or the Local Group Policy Editor. Consult the BitLocker Drive Encryption Deployment Guide on Microsoft TechNet for more information about adding data recovery agents.
-
-In "Configure user storage of BitLocker recovery information" select whether users are allowed, required, or not allowed to generate a 48-digit recovery password or a 256-bit recovery key.
-
-Select "Omit recovery options from the BitLocker setup wizard" to prevent users from specifying recovery options when they turn on BitLocker on a drive. This means that you will not be able to specify which recovery option to use when you turn on BitLocker, instead BitLocker recovery options for the drive are determined by the policy setting.
-
-In "Save BitLocker recovery information to Active Directory Domain Services" choose which BitLocker recovery information to store in AD DS for fixed data drives. If you select "Backup recovery password and key package", both the BitLocker recovery password and key package are stored in AD DS. Storing the key package supports recovering data from a drive that has been physically corrupted. If you select "Backup recovery password only," only the recovery password is stored in AD DS.
-
-Select the "Do not enable BitLocker until recovery information is stored in AD DS for fixed data drives" check box if you want to prevent users from enabling BitLocker unless the computer is connected to the domain and the backup of BitLocker recovery information to AD DS succeeds.
-
-Note: If the "Do not enable BitLocker until recovery information is stored in AD DS for fixed data drives" check box is selected, a recovery password is automatically generated.
-
-If you enable this policy setting, you can control the methods available to users to recover data from BitLocker-protected fixed data drives.
-
-If this policy setting is not configured or disabled, the default recovery options are supported for BitLocker recovery. By default a DRA is allowed, the recovery options can be specified by the user including the recovery password and recovery key, and recovery information is not backed up to AD DS
-
-
-
- Require 48-digit recovery password
- Allow 48-digit recovery password
- Do not allow 48-digit recovery password
-
- Require 256-bit recovery key
- Do not allow 256-bit recovery key
- Allow 256-bit recovery key
-
- Choose how BitLocker-protected removable drives can be recovered
-
- This policy setting allows you to control how BitLocker-protected removable data drives are recovered in the absence of the required credentials. This policy setting is applied when you turn on BitLocker.
-
-The "Allow data recovery agent" check box is used to specify whether a data recovery agent can be used with BitLocker-protected removable data drives. Before a data recovery agent can be used it must be added from the Public Key Policies item in either the Group Policy Management Console or the Local Group Policy Editor. Consult the BitLocker Drive Encryption Deployment Guide on Microsoft TechNet for more information about adding data recovery agents.
-
-In "Configure user storage of BitLocker recovery information" select whether users are allowed, required, or not allowed to generate a 48-digit recovery password or a 256-bit recovery key.
-
-Select "Omit recovery options from the BitLocker setup wizard" to prevent users from specifying recovery options when they turn on BitLocker on a drive. This means that you will not be able to specify which recovery option to use when you turn on BitLocker, instead BitLocker recovery options for the drive are determined by the policy setting.
-
-In "Save BitLocker recovery information to Active Directory Domain Services" choose which BitLocker recovery information to store in AD DS for removable data drives. If you select "Backup recovery password and key package", both the BitLocker recovery password and key package are stored in AD DS. If you select "Backup recovery password only" only the recovery password is stored in AD DS.
-
-Select the "Do not enable BitLocker until recovery information is stored in AD DS for removable data drives" check box if you want to prevent users from enabling BitLocker unless the computer is connected to the domain and the backup of BitLocker recovery information to AD DS succeeds.
-
-Note: If the "Do not enable BitLocker until recovery information is stored in AD DS for fixed data drives" check box is selected, a recovery password is automatically generated.
-
-If you enable this policy setting, you can control the methods available to users to recover data from BitLocker-protected removable data drives.
-
-If this policy setting is not configured or disabled, the default recovery options are supported for BitLocker recovery. By default a DRA is allowed, the recovery options can be specified by the user including the recovery password and recovery key, and recovery information is not backed up to AD DS
-
- Require 48-digit recovery password
- Allow 48-digit recovery password
- Do not allow 48-digit recovery password
-
- Require 256-bit recovery key
- Do not allow 256-bit recovery key
- Allow 256-bit recovery key
-
-
- This policy setting allows you to specify the default path that is displayed when the BitLocker Drive Encryption setup wizard prompts the user to enter the location of a folder in which to save the recovery password. This policy setting is applied when you turn on BitLocker.
-
-If you enable this policy setting, you can specify the path that will be used as the default folder location when the user chooses the option to save the recovery password in a folder. You can specify either a fully qualified path or include the target computer's environment variables in the path. If the path is not valid, the BitLocker setup wizard will display the computer's top-level folder view.
-
-If you disable or do not configure this policy setting, the BitLocker setup wizard will display the computer's top-level folder view when the user chooses the option to save the recovery password in a folder.
-
-Note: This policy setting does not prevent the user from saving the recovery password in another folder.
-
-
-
- Choose default folder for recovery password
-
- This policy setting allows you to configure the algorithm and cipher strength used by BitLocker Drive Encryption. This policy setting is applied when you turn on BitLocker. Changing the encryption method has no effect if the drive is already encrypted or if encryption is in progress. Consult the BitLocker Drive Encryption Deployment Guide on Microsoft TechNet for more information about the encryption methods available. This policy is only applicable to computers running Windows Server 2008, Windows Vista, Windows Server 2008 R2, or Windows 7.
-
-If you enable this policy setting you will be able to choose an encryption algorithm and key cipher strength for BitLocker to use to encrypt drives.
-
-If you disable or do not configure this policy setting, BitLocker will use the default encryption method of AES 128-bit with Diffuser or the encryption method specified by the setup script.
-
-
- This policy setting allows you to configure the algorithm and cipher strength used by BitLocker Drive Encryption. This policy setting is applied when you turn on BitLocker. Changing the encryption method has no effect if the drive is already encrypted or if encryption is in progress. Consult the BitLocker Drive Encryption Deployment Guide on Microsoft TechNet for more information about the encryption methods available. This policy is only applicable to computers running Windows 8 and later.
-
-If you enable this policy setting you will be able to choose an encryption algorithm and key cipher strength for BitLocker to use to encrypt drives.
-
-If you disable or do not configure this policy setting, BitLocker will use AES with the same bit strength (128-bit or 256-bit) as the "Choose drive encryption method and cipher strength (Windows Vista, Windows Server 2008, Windows 7)" policy setting, if it is set. If neither policy is set, BitLocker will use the default encryption method of AES 128-bit or the encryption method specified by the setup script.
-
-
- This policy setting allows you to configure the algorithm and cipher strength used by BitLocker Drive Encryption. This policy setting is applied when you turn on BitLocker. Changing the encryption method has no effect if the drive is already encrypted, or if encryption is in progress.
-
-If you enable this policy setting you will be able to configure an encryption algorithm and key cipher strength for fixed data drives, operating system drives, and removable data drives individually. For fixed and operating system drives, we recommend that you use the XTS-AES algorithm. For removable drives, you should use AES-CBC 128-bit or AES-CBC 256-bit if the drive will be used in other devices that are not running Windows 10 (Version 1511).
-
-If you disable or do not configure this policy setting, BitLocker will use AES with the same bit strength (128-bit or 256-bit) as the "Choose drive encryption method and cipher strength (Windows Vista, Windows Server 2008, Windows 7)" and "Choose drive encryption method and cipher strength" policy settings (in that order), if they are set. If none of the policies are set, BitLocker will use the default encryption method of XTS-AES 128-bit or the encryption method specified by the setup script.”
-
-
- Choose drive encryption method and cipher strength (Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2)
- Choose drive encryption method and cipher strength (Windows 8, Windows Server 2012, Windows 8.1, Windows Server 2012 R2, Windows 10 [Version 1507])
- Choose drive encryption method and cipher strength (Windows 10 [Version 1511] and later)
- AES 128-bit with Diffuser
- AES 256-bit with Diffuser
- AES 128-bit (default)
- AES-CBC 128-bit
- AES-CBC 128-bit (default)
- AES 256-bit
- AES-CBC 256-bit
- XTS-AES 128-bit (default)
- XTS-AES 128-bit
- XTS-AES 256-bit
-
- BitLocker Drive Encryption
- This policy setting allows you to configure how the computer's Trusted Platform Module (TPM) security hardware secures the BitLocker encryption key. This policy setting does not apply if the computer does not have a compatible TPM or if BitLocker has already been turned on with TPM protection.
-
-If you enable this policy setting before turning on BitLocker, you can configure the boot components that the TPM will validate before unlocking access to the BitLocker-encrypted operating system drive. If any of these components change while BitLocker protection is in effect, the TPM will not release the encryption key to unlock the drive and the computer will instead display the BitLocker Recovery console and require that either the recovery password or recovery key be provided to unlock the drive.
-
-If you disable or do not configure this policy setting, the TPM uses the default platform validation profile or the platform validation profile specified by the setup script. A platform validation profile consists of a set of Platform Configuration Register (PCR) indices ranging from 0 to 23, The default platform validation profile secures the encryption key against changes to the Core Root of Trust of Measurement (CRTM), BIOS, and Platform Extensions (PCR 0), the Option ROM Code (PCR 2), the Master Boot Record (MBR) Code (PCR 4), the NTFS Boot Sector (PCR 8), the NTFS Boot Block (PCR 9), the Boot Manager (PCR 10), and the BitLocker Access Control (PCR 11). The descriptions of PCR settings for computers that use an Extensible Firmware Interface (EFI) are different than the PCR settings described for computers that use a standard BIOS.
-
-Warning: Changing from the default platform validation profile affects the security and manageability of your computer. BitLocker's sensitivity to platform modifications (malicious or authorized) is increased or decreased depending upon inclusion or exclusion (respectively) of the PCRs.
-
-
- Configure TPM platform validation profile (Windows Vista, Windows Server 2008, Windows 7, Windows Server 2008 R2)
-
- This policy setting allows you to configure how the computer's Trusted Platform Module (TPM) security hardware secures the BitLocker encryption key. This policy setting does not apply if the computer does not have a compatible TPM or if BitLocker has already been turned on with TPM protection.
-
-Important: This group policy only applies to computers with BIOS configurations or to computers with UEFI firmware with a Compatibility Service Module (CSM) enabled. Computers using a native UEFI firmware configuration store different values into the Platform Configuration Registers (PCRs). Use the "Configure TPM platform validation profile for native UEFI firmware configurations" group policy setting to configure the TPM PCR profile for computers using native UEFI firmware.
-
-If you enable this policy setting before turning on BitLocker, you can configure the boot components that the TPM will validate before unlocking access to the BitLocker-encrypted operating system drive. If any of these components change while BitLocker protection is in effect, the TPM will not release the encryption key to unlock the drive and the computer will instead display the BitLocker Recovery console and require that either the recovery password or recovery key be provided to unlock the drive.
-
-If you disable or do not configure this policy setting, BitLocker uses the default platform validation profile or the platform validation profile specified by the setup script. A platform validation profile consists of a set of Platform Configuration Register (PCR) indices ranging from 0 to 23. The default platform validation profile secures the encryption key against changes to the Core Root of Trust of Measurement (CRTM), BIOS, and Platform Extensions (PCR 0), the Option ROM Code (PCR 2), the Master Boot Record (MBR) Code (PCR 4), the NTFS Boot Sector (PCR 8), the NTFS Boot Block (PCR 9), the Boot Manager (PCR 10), and the BitLocker Access Control (PCR 11).
-
-Warning: Changing from the default platform validation profile affects the security and manageability of your computer. BitLocker's sensitivity to platform modifications (malicious or authorized) is increased or decreased depending upon inclusion or exclusion (respectively) of the PCRs.
-
-
- Configure TPM platform validation profile for BIOS-based firmware configurations
-
- This policy setting allows you to configure how the computer's Trusted Platform Module (TPM) security hardware secures the BitLocker encryption key. This policy setting does not apply if the computer does not have a compatible TPM or if BitLocker has already been turned on with TPM protection.
-
-Important: This group policy only applies to computers with a native UEFI firmware configuration. Computers with BIOS or UEFI firmware with a Compatibility Service Module (CSM) enabled store different values into the Platform Configuration Registers (PCRs). Use the "Configure TPM platform validation profile for BIOS-based firmware configurations" group policy setting to configure the TPM PCR profile for computers with BIOS configurations or computers with UEFI firmware with a CSM enabled.
-
-If you enable this policy setting before turning on BitLocker, you can configure the boot components that the TPM will validate before unlocking access to the BitLocker-encrypted operating system drive. If any of these components change while BitLocker protection is in effect, the TPM will not release the encryption key to unlock the drive and the computer will instead display the BitLocker Recovery console and require that either the recovery password or recovery key be provided to unlock the drive.
-
-If you disable or do not configure this policy setting, BitLocker uses the default platform validation profile for the available hardware or the platform validation profile specified by the setup script. A platform validation profile consists of a set of Platform Configuration Register (PCR) indices ranging from 0 to 23.
-
-On PCs that lack Secure Boot State (PCR 7) support, the default platform validation profile secures the encryption key against changes to the core system firmware executable code (PCR 0), extended or pluggable executable code (PCR 2), boot manager (PCR 4), and the BitLocker access control (PCR 11).
-
-When Secure Boot State (PCR7) support is available, the default platform validation profile secures the encryption key using Secure Boot State (PCR 7) and the BitLocker access control (PCR 11).
-
-Warning: Changing from the default platform validation profile affects the security and manageability of your computer. BitLocker's sensitivity to platform modifications (malicious or authorized) is increased or decreased depending upon inclusion or exclusion (respectively) of the PCRs. Specifically, setting this policy with PCR 7 omitted, will override the "Allow Secure Boot for integrity validation" group policy, preventing BitLocker from using Secure Boot for platform or Boot Configuration Data (BCD) integrity validation. Setting this policy may result in BitLocker recovery when firmware is updated. If you set this policy to include PCR 0, suspend BitLocker prior to applying firmware updates.
-
-It is recommended to not configure this policy, to allow Windows to select the PCR profile for the best combination of security and usability based on the available hardware on each PC.
-
-
- Configure TPM platform validation profile for native UEFI firmware configurations
-
- This policy setting controls computer restart performance at the risk of exposing BitLocker secrets. This policy setting is applied when you turn on BitLocker. BitLocker secrets include key material used to encrypt data. This policy setting applies only when BitLocker protection is enabled.
-
-If you enable this policy setting, memory will not be overwritten when the computer restarts. Preventing memory overwrite may improve restart performance but will increase the risk of exposing BitLocker secrets.
-
-If you disable or do not configure this policy setting, BitLocker secrets are removed from memory when the computer restarts.
-
-
- Prevent memory overwrite on restart
-
- This policy setting allows you to block direct memory access (DMA) for all Thunderbolt hot pluggable PCI downstream ports until a user logs into Windows. Once a user logs in, Windows will enumerate the PCI devices connected to the host Thunderbolt PCI ports. Every time the user locks the machine, DMA will be blocked on hot plug Thunderbolt PCI ports with no children devices, until the user logs in again. Devices which were already enumerated when the machine was unlocked will continue to function until unplugged or the system is rebooted or hibernated. This policy setting is only enforced when BitLocker or device encryption is enabled.
-
-Note: Some PCs may not be compatible with this policy if the system firmware enables DMA for newly attached Thunderbolt devices before exposing the new devices to Windows.
-
-
- Disable new DMA devices when this computer is locked
-
- Operating System Drives
- Fixed Data Drives
- Removable Data Drives
-
- Provide the unique identifiers for your organization
- This policy setting allows you to associate unique organizational identifiers to a new drive that is enabled with BitLocker. These identifiers are stored as the identification field and allowed identification field. The identification field allows you to associate a unique organizational identifier to BitLocker-protected drives. This identifier is automatically added to new BitLocker-protected drives and can be updated on existing BitLocker-protected drives using the manage-bde command-line tool. An identification field is required for management of certificate-based data recovery agents on BitLocker-protected drives and for potential updates to the BitLocker To Go Reader. BitLocker will only manage and update data recovery agents when the identification field on the drive matches the value configured in the identification field. In a similar manner, BitLocker will only update the BitLocker To Go Reader when the identification field on the drive matches the value configured for the identification field.
-
-The allowed identification field is used in combination with the "Deny write access to removable drives not protected by BitLocker" policy setting to help control the use of removable drives in your organization. It is a comma separated list of identification fields from your organization or other external organizations.
-
-You can configure the identification fields on existing drives by using manage-bde.exe.
-
-If you enable this policy setting, you can configure the identification field on the BitLocker-protected drive and any allowed identification field used by your organization.
-
-When a BitLocker-protected drive is mounted on another BitLocker-enabled computer the identification field and allowed identification field will be used to determine whether the drive is from an outside organization.
-
-If you disable or do not configure this policy setting, the identification field is not required.
-
-Note: Identification fields are required for management of certificate-based data recovery agents on BitLocker-protected drives. BitLocker will only manage and update certificate-based data recovery agents when the identification field is present on a drive and is identical to the value configured on the computer. The identification field can be any value of 260 characters or fewer.
-
-
-
-
- Validate smart card certificate usage rule compliance
- This policy setting allows you to associate an object identifier from a smart card certificate to a BitLocker-protected drive. This policy setting is applied when you turn on BitLocker.
-
-The object identifier is specified in the enhanced key usage (EKU) of a certificate. BitLocker can identify which certificates may be used to authenticate a user certificate to a BitLocker-protected drive by matching the object identifier in the certificate with the object identifier that is defined by this policy setting.
-
-Default object identifier is 1.3.6.1.4.1.311.67.1.1
-
-Note: BitLocker does not require that a certificate have an EKU attribute, but if one is configured for the certificate it must be set to an object identifier (OID) that matches the OID configured for BitLocker.
-
-If you enable this policy setting, the object identifier specified in the "Object identifier" box must match the object identifier in the smart card certificate.
-
-If you disable or do not configure this policy setting, a default object identifier is used.
-
-
-
- Use enhanced Boot Configuration Data validation profile
- This policy setting allows you to choose specific Boot Configuration Data (BCD) settings to verify during platform validation.
-
-If you enable this policy setting, you will be able to add additional settings, remove the default settings, or both.
-
-If you disable this policy setting, the computer will revert to a BCD profile similar to the default BCD profile used by Windows 7.
-
-If you do not configure this policy setting, the computer will verify the default Windows BCD settings.
-
-Note: When BitLocker is using Secure Boot for platform and Boot Configuration Data (BCD) integrity validation, as defined by the "Allow Secure Boot for integrity validation" group policy, the "Use enhanced Boot Configuration Data validation profile" group policy is ignored.
-
-The setting that controls boot debugging (0x16000010) will always be validated and will have no effect if it is included in the provided fields.
-
-
- Store recovery passwords and key packages
- Store recovery passwords only
-
-
- Configure minimum PIN length for startup
-
- This policy setting allows you to configure a minimum length for a Trusted Platform Module (TPM) startup PIN. This policy setting is applied when you turn on BitLocker. The startup PIN must have a minimum length of 4 digits and can have a maximum length of 20 digits.
-
- If you enable this policy setting, you can require a minimum number of digits to be used when setting the startup PIN.
-
- If you disable or do not configure this policy setting, users can configure a startup PIN of any length between 6 and 20 digits.
-
- NOTE: If minimum PIN length is set below 6 digits, Windows will attempt to update the TPM 2.0 lockout period to be greater than the default when a PIN is changed. If successful, Windows will only reset the TPM lockout period back to default if the TPM is reset.
-
-
-
- Allow certificate-based data recovery agents
-
- Deny write access to fixed drives not protected by BitLocker
- This policy setting determines whether BitLocker protection is required for fixed data drives to be writable on a computer.
-
-If you enable this policy setting, all fixed data drives that are not BitLocker-protected will be mounted as read-only. If the drive is protected by BitLocker, it will be mounted with read and write access.
-
-If you disable or do not configure this policy setting, all fixed data drives on the computer will be mounted with read and write access.
-
-
-
- Configure use of passwords for fixed data drives
- This policy setting specifies whether a password is required to unlock BitLocker-protected fixed data drives. If you choose to permit the use of a password, you can require that a password be used, enforce complexity requirements on the password, and configure a minimum length for the password. For the complexity requirement setting to be effective the Group Policy setting "Password must meet complexity requirements" located in Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy\ must be also enabled.
-
-Note: These settings are enforced when turning on BitLocker, not when unlocking a volume. BitLocker will allow unlocking a drive with any of the protectors available on the drive.
-
-If you enable this policy setting, users can configure a password that meets the requirements you define. To require the use of a password, select "Require password for fixed data drive". To enforce complexity requirements on the password, select "Require complexity".
-
-When set to "Require complexity" a connection to a domain controller is necessary when BitLocker is enabled to validate the complexity the password. When set to "Allow complexity" a connection to a domain controller will be attempted to validate the complexity adheres to the rules set by the policy, but if no domain controllers are found the password will still be accepted regardless of actual password complexity and the drive will be encrypted using that password as a protector. When set to "Do not allow complexity", no password complexity validation will be done.
-
-Passwords must be at least 8 characters. To configure a greater minimum length for the password, enter the desired number of characters in the "Minimum password length" box.
-
-If you disable this policy setting, the user is not allowed to use a password.
-
-If you do not configure this policy setting, passwords will be supported with the default settings, which do not include password complexity requirements and require only 8 characters.
-
-Note: Passwords cannot be used if FIPS-compliance is enabled. The "System cryptography: Use FIPS-compliant algorithms for encryption, hashing, and signing" policy setting in Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options specifies whether FIPS-compliance is enabled.
-
-
-
- Configure use of passwords for operating system drives
- This policy setting specifies the constraints for passwords used to unlock BitLocker-protected operating system drives. If non-TPM protectors are allowed on operating system drives, you can provision a password, enforce complexity requirements on the password, and configure a minimum length for the password. For the complexity requirement setting to be effective the Group Policy setting "Password must meet complexity requirements" located in Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy\ must be also enabled.
-
-Note: These settings are enforced when turning on BitLocker, not when unlocking a volume. BitLocker will allow unlocking a drive with any of the protectors available on the drive.
-
-If you enable this policy setting, users can configure a password that meets the requirements you define. To enforce complexity requirements on the password, select "Require complexity".
-
-When set to "Require complexity" a connection to a domain controller is necessary when BitLocker is enabled to validate the complexity the password. When set to "Allow complexity" a connection to a domain controller will be attempted to validate the complexity adheres to the rules set by the policy, but if no domain controllers are found the password will still be accepted regardless of actual password complexity and the drive will be encrypted using that password as a protector. When set to "Do not allow complexity", no password complexity validation will be done.
-
-Passwords must be at least 8 characters. To configure a greater minimum length for the password, enter the desired number of characters in the "Minimum password length" box.
-
-If you disable or do not configure this policy setting, the default length constraint of 8 characters will apply to operating system drive passwords and no complexity checks will occur.
-
-Note: Passwords cannot be used if FIPS-compliance is enabled. The "System cryptography: Use FIPS-compliant algorithms for encryption, hashing, and signing" policy setting in Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options specifies whether FIPS-compliance is enabled.
-
-
-
-
- Allow password complexity
- Do not allow password complexity
- Require password complexity
-
- Backup recovery passwords and key packages
- Backup recovery passwords only
-
-
- Allow access to BitLocker-protected fixed data drives from earlier versions of Windows
- This policy setting configures whether or not fixed data drives formatted with the FAT file system can be unlocked and viewed on computers running Windows Server 2008, Windows Vista, Windows XP with Service Pack 3 (SP3), or Windows XP with Service Pack 2 (SP2) operating systems.
-
-If this policy setting is enabled or not configured, fixed data drives formatted with the FAT file system can be unlocked on computers running Windows Server 2008, Windows Vista, Windows XP with SP3, or Windows XP with SP2, and their content can be viewed. These operating systems have read-only access to BitLocker-protected drives.
-
-When this policy setting is enabled, select the "Do not install BitLocker To Go Reader on FAT formatted fixed drives" check box to help prevent users from running BitLocker To Go Reader from their fixed drives. If BitLocker To Go Reader (bitlockertogo.exe) is present on a drive that does not have an identification field specified, or if the drive has the same identification field as specified in the "Provide unique identifiers for your organization" policy setting, the user will be prompted to update BitLocker and BitLocker To Go Reader will be deleted from the drive. In this situation, for the fixed drive to be unlocked on computers running Windows Server 2008, Windows Vista, Windows XP with SP3, or Windows XP with SP2, BitLocker To Go Reader must be installed on the computer. If this check box is not selected, BitLocker To Go Reader will be installed on the fixed drive to enable users to unlock the drive on computers running Windows Server 2008, Windows Vista, Windows XP with SP3, or Windows XP with SP2 that do not have BitLocker To Go Reader installed.
-
-If this policy setting is disabled, fixed data drives formatted with the FAT file system that are BitLocker-protected cannot be unlocked on computers running Windows Server 2008, Windows Vista, Windows XP with SP3, or Windows XP with SP2. Bitlockertogo.exe will not be installed.
-
-Note: This policy setting does not apply to drives that are formatted with the NTFS file system.
-
-
-
-
- Allow certificate-based data recovery agents
-
- Configure use of smart cards on fixed data drives
- This policy setting allows you to specify whether smart cards can be used to authenticate user access to the BitLocker-protected fixed data drives on a computer.
-
-If you enable this policy setting smart cards can be used to authenticate user access to the drive. You can require a smart card authentication by selecting the "Require use of smart cards on fixed data drives" check box.
-
-Note: These settings are enforced when turning on BitLocker, not when unlocking a drive. BitLocker will allow unlocking a drive with any of the protectors available on the drive.
-
-If you disable this policy setting, users are not allowed to use smart cards to authenticate their access to BitLocker-protected fixed data drives.
-
-If you do not configure this policy setting, smart cards can be used to authenticate user access to a BitLocker-protected drive.
-
-
-
- Configure use of passwords for removable data drives
- This policy setting specifies whether a password is required to unlock BitLocker-protected removable data drives. If you choose to allow use of a password, you can require a password to be used, enforce complexity requirements, and configure a minimum length. For the complexity requirement setting to be effective the Group Policy setting "Password must meet complexity requirements" located in Computer Configuration\Windows Settings\Security Settings\Account Policies\Password Policy\ must be also enabled.
-
-Note: These settings are enforced when turning on BitLocker, not when unlocking a volume. BitLocker will allow unlocking a drive with any of the protectors available on the drive.
-
-If you enable this policy setting, users can configure a password that meets the requirements that you define. To require the use of a password, select "Require password for removable data drive". To enforce complexity requirements on the password, select "Require complexity".
-
-When set to "Require complexity" a connection to a domain controller is necessary when BitLocker is enabled to validate the complexity the password. When set to "Allow complexity" a connection to a domain controller will be attempted to validate the complexity adheres to the rules set by the policy, but if no domain controllers are found the password will still be accepted regardless of actual password complexity and the drive will be encrypted using that password as a protector. When set to "Do not allow complexity", no password complexity validation will be done.
-
-Passwords must be at least 8 characters. To configure a greater minimum length for the password, enter the desired number of characters in the "Minimum password length" box.
-
-If you disable this policy setting, the user is not allowed to use a password.
-
-If you do not configure this policy setting, passwords will be supported with the default settings, which do not include password complexity requirements and require only 8 characters.
-
-Note: Passwords cannot be used if FIPS-compliance is enabled. The "System cryptography: Use FIPS-compliant algorithms for encryption, hashing, and signing" policy setting in Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options specifies whether FIPS-compliance is enabled.
-
-
-
- Deny write access to removable drives not protected by BitLocker
- This policy setting configures whether BitLocker protection is required for a computer to be able to write data to a removable data drive.
-
-If you enable this policy setting, all removable data drives that are not BitLocker-protected will be mounted as read-only. If the drive is protected by BitLocker, it will be mounted with read and write access.
-
-If the "Deny write access to devices configured in another organization" option is selected, only drives with identification fields matching the computer's identification fields will be given write access. When a removable data drive is accessed it will be checked for valid identification field and allowed identification fields. These fields are defined by the "Provide the unique identifiers for your organization" policy setting.
-
-If you disable or do not configure this policy setting, all removable data drives on the computer will be mounted with read and write access.
-
-Note: This policy setting can be overridden by the policy settings under User Configuration\Administrative Templates\System\Removable Storage Access. If the "Removable Disks: Deny write access" policy setting is enabled this policy setting will be ignored.
-
-
-
- Control use of BitLocker on removable drives
- This policy setting controls the use of BitLocker on removable data drives. This policy setting is applied when you turn on BitLocker.
-
-When this policy setting is enabled you can select property settings that control how users can configure BitLocker. Choose "Allow users to apply BitLocker protection on removable data drives" to permit the user to run the BitLocker setup wizard on a removable data drive. Choose "Allow users to suspend and decrypt BitLocker on removable data drives" to permit the user to remove BitLocker Drive encryption from the drive or suspend the encryption while maintenance is performed. Consult the BitLocker Drive Encryption Deployment Guide on Microsoft TechNet for more information on suspending BitLocker protection.
-
-If you do not configure this policy setting, users can use BitLocker on removable disk drives.
-
-If you disable this policy setting, users cannot use BitLocker on removable disk drives.
-
-
-
-
- Backup recovery passwords and key packages
- Backup recovery passwords only
-
- Allow access to BitLocker-protected removable data drives from earlier versions of Windows
- This policy setting configures whether or not removable data drives formatted with the FAT file system can be unlocked and viewed on computers running Windows Server 2008, Windows Vista, Windows XP with Service Pack 3 (SP3), or Windows XP with Service Pack 2 (SP2) operating systems.
-
-If this policy setting is enabled or not configured, removable data drives formatted with the FAT file system can be unlocked on computers running Windows Server 2008, Windows Vista, Windows XP with SP3, or Windows XP with SP2, and their content can be viewed. These operating systems have read-only access to BitLocker-protected drives.
-
-When this policy setting is enabled, select the "Do not install BitLocker To Go Reader on FAT formatted removable drives" check box to help prevent users from running BitLocker To Go Reader from their removable drives. If BitLocker To Go Reader (bitlockertogo.exe) is present on a drive that does not have an identification field specified, or if the drive has the same identification field as specified in the "Provide unique identifiers for your organization" policy setting, the user will be prompted to update BitLocker and BitLocker To Go Reader will be deleted from the drive. In this situation, for the removable drive to be unlocked on computers running Windows Server 2008, Windows Vista, Windows XP with SP3, or Windows XP with SP2, BitLocker To Go Reader must be installed on the computer. If this check box is not selected, BitLocker To Go Reader will be installed on the removable drive to enable users to unlock the drive on computers running Windows Server 2008, Windows Vista, Windows XP with SP3, or Windows XP with SP2 that do not have BitLocker To Go Reader installed.
-
-If this policy setting is disabled, removable data drives formatted with the FAT file system that are BitLocker-protected cannot be unlocked on computers running Windows Server 2008, Windows Vista, Windows XP with SP3, or Windows XP with SP2. Bitlockertogo.exe will not be installed.
-
-Note: This policy setting does not apply to drives that are formatted with the NTFS file system.
-
-
-
- Allow certificate-based data recovery agents
-
- Configure use of smart cards on removable data drives
- This policy setting allows you to specify whether smart cards can be used to authenticate user access to BitLocker-protected removable data drives on a computer.
-
-If you enable this policy setting smart cards can be used to authenticate user access to the drive. You can require a smart card authentication by selecting the "Require use of smart cards on removable data drives" check box.
-
-Note: These settings are enforced when turning on BitLocker, not when unlocking a drive. BitLocker will allow unlocking a drive with any of the protectors available on the drive.
-
-If you disable this policy setting, users are not allowed to use smart cards to authenticate their access to BitLocker-protected removable data drives.
-
-If you do not configure this policy setting, smart cards are available to authenticate user access to a BitLocker-protected removable data drive.
-
-
-
- Allow enhanced PINs for startup
- This policy setting allows you to configure whether or not enhanced startup PINs are used with BitLocker.
-
-Enhanced startup PINs permit the use of characters including uppercase and lowercase letters, symbols, numbers, and spaces. This policy setting is applied when you turn on BitLocker.
-
-If you enable this policy setting, all new BitLocker startup PINs set will be enhanced PINs.
-
-Note: Not all computers may support enhanced PINs in the pre-boot environment. It is strongly recommended that users perform a system check during BitLocker setup.
-
-If you disable or do not configure this policy setting, enhanced PINs will not be used.
-
-
-
- Reset platform validation data after BitLocker recovery
- This policy setting allows you to control whether or not platform validation data is refreshed when Windows is started following BitLocker recovery.
-
-If you enable this policy setting, platform validation data will be refreshed when Windows is started following BitLocker recovery.
-
-If you disable this policy setting, platform validation data will not be refreshed when Windows is started following BitLocker recovery.
-
-If you do not configure this policy setting, platform validation data will be refreshed when Windows is started following BitLocker recovery.
-
-
-
- Enforce drive encryption type on operating system drives
-
- Enforce drive encryption type on fixed data drives
-
- Enforce drive encryption type on removable data drives
-
- This policy setting allows you to configure the encryption type used by BitLocker Drive Encryption. This policy setting is applied when you turn on BitLocker. Changing the encryption type has no effect if the drive is already encrypted or if encryption is in progress. Choose full encryption to require that the entire drive be encrypted when BitLocker is turned on. Choose used space only encryption to require that only the portion of the drive used to store data is encrypted when BitLocker is turned on.
-
-If you enable this policy setting the encryption type that BitLocker will use to encrypt drives is defined by this policy and the encryption type option will not be presented in the BitLocker setup wizard.
-
-If you disable or do not configure this policy setting, the BitLocker setup wizard will ask the user to select the encryption type before turning on BitLocker.
-
-
-
- Allow user to choose (default)
- Full encryption
- Used Space Only encryption
-
- Disallow standard users from changing the PIN or password
- This policy setting allows you to configure whether or not standard users are allowed to change BitLocker volume PINs, provided they are able to provide the existing PIN first.
-
-This policy setting is applied when you turn on BitLocker.
-
-If you enable this policy setting, standard users will not be allowed to change BitLocker PINs or passwords.
-
-If you disable or do not configure this policy setting, standard users will be permitted to change BitLocker PINs and passwords.
-
-
-
- Configure use of hardware-based encryption for operating system drives
-
- Configure use of hardware-based encryption for fixed data drives
-
- Configure use of hardware-based encryption for removable data drives
-
- This policy setting allows you to manage BitLocker’s use of hardware-based encryption on operating system drives and specify which encryption algorithms it can use with hardware-based encryption. Using hardware-based encryption can improve performance of drive operations that involve frequent reading or writing of data to the drive.
-
-If you enable this policy setting, you can specify additional options that control whether BitLocker software-based encryption is used instead of hardware-based encryption on computers that do not support hardware-based encryption and whether you want to restrict the encryption algorithms and cipher suites used with hardware-based encryption.
-
-If you disable this policy setting, BitLocker cannot use hardware-based encryption with operating system drives and BitLocker software-based encryption will be used by default when the drive is encrypted.
-
-If you do not configure this policy setting, BitLocker will use software-based encryption irrespective of hardware-based encryption availability.
-
-Note: The “Choose drive encryption method and cipher strength” policy setting does not apply to hardware-based encryption. The encryption algorithm used by hardware-based encryption is set when the drive is partitioned. By default, BitLocker uses the algorithm configured on the drive to encrypt the drive. The “Restrict encryption algorithms and cipher suites allowed for hardware-based encryption” option enables you to restrict the encryption algorithms that BitLocker can use with hardware encryption. If the algorithm set for the drive is not available, BitLocker will disable the use of hardware-based encryption.
-Encryption algorithms are specified by object identifiers (OID). For example:
-- AES 128 in CBC mode OID: 2.16.840.1.101.3.4.1.2
-- AES 256 in CBC mode OID: 2.16.840.1.101.3.4.1.42
-
-
- This policy setting allows you to manage BitLocker’s use of hardware-based encryption on fixed data drives and specify which encryption algorithms it can use with hardware-based encryption. Using hardware-based encryption can improve performance of drive operations that involve frequent reading or writing of data to the drive.
-
-If you enable this policy setting, you can specify additional options that control whether BitLocker software-based encryption is used instead of hardware-based encryption on computers that do not support hardware-based encryption and whether you want to restrict the encryption algorithms and cipher suites used with hardware-based encryption.
-
-If you disable this policy setting, BitLocker cannot use hardware-based encryption with operating system drives and BitLocker software-based encryption will be used by default when the drive is encrypted.
-
-If you do not configure this policy setting, BitLocker will use software-based encryption irrespective of hardware-based encryption availability.
-
-Note: The “Choose drive encryption method and cipher strength” policy setting does not apply to hardware-based encryption. The encryption algorithm used by hardware-based encryption is set when the drive is partitioned. By default, BitLocker uses the algorithm configured on the drive to encrypt the drive. The “Restrict encryption algorithms and cipher suites allowed for hardware-based encryption” option enables you to restrict the encryption algorithms that BitLocker can use with hardware encryption. If the algorithm set for the drive is not available, BitLocker will disable the use of hardware-based encryption.
-Encryption algorithms are specified by object identifiers (OID). For example:
-- AES 128 in CBC mode OID: 2.16.840.1.101.3.4.1.2
-- AES 256 in CBC mode OID: 2.16.840.1.101.3.4.1.42
-
-
- This policy setting allows you to manage BitLocker’s use of hardware-based encryption on removable data drives and specify which encryption algorithms it can use with hardware-based encryption. Using hardware-based encryption can improve performance of drive operations that involve frequent reading or writing of data to the drive.
-
-If you enable this policy setting, you can specify additional options that control whether BitLocker software-based encryption is used instead of hardware-based encryption on computers that do not support hardware-based encryption and whether you want to restrict the encryption algorithms and cipher suites used with hardware-based encryption.
-
-If you disable this policy setting, BitLocker cannot use hardware-based encryption with operating system drives and BitLocker software-based encryption will be used by default when the drive is encrypted.
-
-If you do not configure this policy setting, BitLocker will use software-based encryption irrespective of hardware-based encryption availability.
-
-Note: The “Choose drive encryption method and cipher strength” policy setting does not apply to hardware-based encryption. The encryption algorithm used by hardware-based encryption is set when the drive is partitioned. By default, BitLocker uses the algorithm configured on the drive to encrypt the drive. The “Restrict encryption algorithms and cipher suites allowed for hardware-based encryption” option enables you to restrict the encryption algorithms that BitLocker can use with hardware encryption. If the algorithm set for the drive is not available, BitLocker will disable the use of hardware-based encryption.
-Encryption algorithms are specified by object identifiers (OID). For example:
-- AES 128 in CBC mode OID: 2.16.840.1.101.3.4.1.2
-- AES 256 in CBC mode OID: 2.16.840.1.101.3.4.1.42
-
-
- Enable use of BitLocker authentication requiring preboot keyboard input on slates
- This policy setting allows users to turn on authentication options that require user input from the pre-boot environment, even if the platform lacks pre-boot input capability.
-
-The Windows touch keyboard (such as that used by tablets) isn't available in the pre-boot environment where BitLocker requires additional information such as a PIN or Password.
-
-If you enable this policy setting, devices must have an alternative means of pre-boot input (such as an attached USB keyboard).
-
-If this policy is not enabled, the Windows Recovery Environment must be enabled on tablets to support the entry of the BitLocker recovery password. When the Windows Recovery Environment is not enabled and this policy is not enabled, you cannot turn on BitLocker on a device that uses the Windows touch keyboard.
-
-Note that if you do not enable this policy setting, options in the "Require additional authentication at startup" policy might not be available on such devices. These options include:
-- Configure TPM startup PIN: Required/Allowed
-- Configure TPM startup key and PIN: Required/Allowed
-- Configure use of passwords for operating system drives.
-
-
- Allow devices compliant with InstantGo or HSTI to opt out of pre-boot PIN.
- This policy setting allows users on devices that are compliant with InstantGo or Microsoft Hardware Security Test Interface (HSTI) to not have a PIN for pre-boot authentication. This overrides the "Require startup PIN with TPM" and "Require startup key and PIN with TPM" options of the "Require additional authentication at startup" policy on compliant hardware.
-
-If you enable this policy setting, users on InstantGo and HSTI compliant devices will have the choice to turn on BitLocker without pre-boot authentication.
-
-If this policy is not enabled, the options of "Require additional authentication at startup" policy apply.
-
-
- Allow Secure Boot for integrity validation
- This policy setting allows you to configure whether Secure Boot will be allowed as the platform integrity provider for BitLocker operating system drives.
-
-Secure Boot ensures that the PC's pre-boot environment only loads firmware that is digitally signed by authorized software publishers. Secure Boot also provides more flexibility for managing pre-boot configuration than legacy BitLocker integrity checks.
-
-If you enable or do not configure this policy setting, BitLocker will use Secure Boot for platform integrity if the platform is capable of Secure Boot-based integrity validation.
-
-If you disable this policy setting, BitLocker will use legacy platform integrity validation, even on systems capable of Secure Boot-based integrity validation.
-
-When this policy is enabled and the hardware is capable of using Secure Boot for BitLocker scenarios, the "Use enhanced Boot Configuration Data validation profile" group policy setting is ignored and Secure Boot verifies BCD settings according to the Secure Boot policy setting, which is configured separately from BitLocker.
-
-Note: If the group policy setting "Configure TPM platform validation profile for native UEFI firmware configurations" is enabled and has PCR 7 omitted, Bitlocker will be prevented from using Secure Boot for platform or Boot Configuration Data (BCD) integrity validation.
-
-Warning: Disabling this policy may result in BitLocker recovery when firmware is updated. If you disable this policy, suspend BitLocker prior to applying firmware updates.
-
- At least Windows Server 2012 or Windows 8
- Windows Server 2012 R2, Windows 8.1, Windows Server 2012, Windows 8, Windows Server 2008, Windows 7, and Windows Vista
- Configure pre-boot recovery message and URL
-
- Use default recovery message and URL
- Use custom recovery message
- Use custom recovery URL
- This policy setting lets you configure the entire recovery message or replace the existing URL that are displayed on the pre-boot key recovery screen when the OS drive is locked.
-
-If you select the "Use default recovery message and URL" option, the default BitLocker recovery message and URL will be displayed in the pre-boot key recovery screen. If you have previously configured a custom recovery message or URL and want to revert to the default message, you must keep the policy enabled and select the "Use default recovery message and URL" option.
-
-If you select the "Use custom recovery message" option, the message you type in the "Custom recovery message option" text box will be displayed in the pre-boot key recovery screen. If a recovery URL is available, include it in the message.
-
-If you select the "Use custom recovery URL" option, the URL you type in the "Custom recovery URL option" text box will replace the default URL in the default recovery message, which will be displayed in the pre-boot key recovery screen.
-
-Note: Not all characters and languages are supported in pre-boot. It is strongly recommended that you test that the characters you use for the custom message or URL appear correctly on the pre-boot recovery screen.
-
-
-
-
- Require BitLocker backup to AD DS
- If selected, cannot turn on BitLocker if backup fails (recommended default).
- If not selected, can turn on BitLocker even if backup fails. Backup is not automatically retried.
- Select BitLocker recovery information to store:
-
- A recovery password is a 48-digit number that unlocks access to a BitLocker-protected drive.
- A key package contains a drive's BitLocker encryption key secured by one or more recovery passwords
- Key packages may help perform specialized recovery when the disk is damaged or corrupted.
-
-
-
- Allow BitLocker without a compatible TPM (requires a password or a startup key on a USB flash drive)
- Settings for computers with a TPM:
- Configure TPM startup key:
- Configure TPM startup PIN:
- Important: If you require the startup key, you must not allow the startup PIN.
- If you require the startup PIN, you must not allow the startup key. Otherwise, a policy error occurs.
- Note: Do not allow both startup PIN and startup key options to hide the advanced page on a computer with a TPM.
-
-
-
- Allow BitLocker without a compatible TPM (requires a password or a startup key on a USB flash drive)
- Settings for computers with a TPM:
- Configure TPM startup:
- Configure TPM startup PIN:
- Configure TPM startup key:
- Configure TPM startup key and PIN:
-
-
-
-
- Important: To prevent data loss, you must have a way to recover BitLocker encryption keys. If you do not allow both recovery options below, you must enable backup of BitLocker recovery information to AD DS. Otherwise, a policy error occurs.
- Configure 48-digit recovery password:
- Configure 256-bit recovery key:
- Note: If you do not allow the recovery password and require the recovery key, users cannot turn on BitLocker without saving to USB.
-
-
-
-
- Allow data recovery agent
- Configure user storage of BitLocker recovery information:
-
-
- Omit recovery options from the BitLocker setup wizard
- Save BitLocker recovery information to AD DS for operating system drives
- Configure storage of BitLocker recovery information to AD DS:
- Do not enable BitLocker until recovery information is stored to AD DS for operating system drives
-
-
-
- Allow data recovery agent
- Configure user storage of BitLocker recovery information:
-
-
- Omit recovery options from the BitLocker setup wizard
- Save BitLocker recovery information to AD DS for fixed data drives
- Configure storage of BitLocker recovery information to AD DS:
- Do not enable BitLocker until recovery information is stored to AD DS for fixed data drives
-
-
-
- Allow data recovery agent
- Configure user storage of BitLocker recovery information:
-
-
- Omit recovery options from the BitLocker setup wizard
- Save BitLocker recovery information to AD DS for removable data drives
- Configure storage of BitLocker recovery information to AD DS:
- Do not enable BitLocker until recovery information is stored to AD DS for removable data drives
-
-
-
-
-
-
-
- Specify a fully qualified path or include the computer's environment variables in the path.
- For example, enter "\\server\backupfolder", or "%SecureDriveEnvironmentVariable%\backupfolder"
- Note: In all cases, the user will be able to select other folders in which to save the recovery password.
-
-
-
-
- Select the encryption method:
-
-
-
- Select the encryption method:
-
-
-
- Select the encryption method for operating system drives:
- Select the encryption method for fixed data drives:
- Select the encryption method for removable data drives:
-
-
-
- Select the encryption type:
-
-
-
- Select the encryption type:
-
-
-
- Select the encryption type:
-
-
-
- A platform validation profile consists of a set of Platform Configuration Register (PCR) indices. Each PCR index is associated with components that run when Windows starts.
- Use the check boxes below to choose the PCR indices to include in the profile.
- Exercise caution when changing this setting.
- We recommend the default of PCRs 0, 2, 4, 8, 9, 10, and 11.
- For BitLocker protection to take effect, you must include PCR 11.
-
- Consult online documentation for more information about the benefits and risks of changing the default TPM platform validation profile.
-
- PCR 0: Core Root of Trust of Measurement (CRTM), BIOS, and Platform Extensions
- PCR 1: Platform and Motherboard Configuration and Data
- PCR 2: Option ROM Code
- PCR 3: Option ROM Configuration and Data
- PCR 4: Master Boot Record (MBR) Code
- PCR 5: Master Boot Record (MBR) Partition Table
- PCR 6: State Transition and Wake Events
- PCR 7: Computer Manufacturer-Specific
- PCR 8: NTFS Boot Sector
- PCR 9: NTFS Boot Block
- PCR 10: Boot Manager
- PCR 11: BitLocker Access Control
- PCR 12: Reserved for Future Use
- PCR 13: Reserved for Future Use
- PCR 14: Reserved for Future Use
- PCR 15: Reserved for Future Use
- PCR 16: Reserved for Future Use
- PCR 17: Reserved for Future Use
- PCR 18: Reserved for Future Use
- PCR 19: Reserved for Future Use
- PCR 20: Reserved for Future Use
- PCR 21: Reserved for Future Use
- PCR 22: Reserved for Future Use
- PCR 23: Reserved for Future Use
-
-
-
- A platform validation profile consists of a set of Platform Configuration Register (PCR) indices. Each PCR index is associated with components that run when Windows starts.
- Use the check boxes below to choose the PCR indices to include in the profile.
- Exercise caution when changing this setting.
- We recommend the default of PCRs 0, 2, 4, 8, 9, 10, and 11.
- For BitLocker protection to take effect, you must include PCR 11.
-
- Consult online documentation for more information about the benefits and risks of changing the default TPM platform validation profile.
-
- PCR 0: Core Root of Trust of Measurement (CRTM), BIOS, and Platform Extensions
- PCR 1: Platform and Motherboard Configuration and Data
- PCR 2: Option ROM Code
- PCR 3: Option ROM Configuration and Data
- PCR 4: Master Boot Record (MBR) Code
- PCR 5: Master Boot Record (MBR) Partition Table
- PCR 6: State Transition and Wake Events
- PCR 7: Computer Manufacturer-Specific
- PCR 8: NTFS Boot Sector
- PCR 9: NTFS Boot Block
- PCR 10: Boot Manager
- PCR 11: BitLocker Access Control
- PCR 12: Reserved for Future Use
- PCR 13: Reserved for Future Use
- PCR 14: Reserved for Future Use
- PCR 15: Reserved for Future Use
- PCR 16: Reserved for Future Use
- PCR 17: Reserved for Future Use
- PCR 18: Reserved for Future Use
- PCR 19: Reserved for Future Use
- PCR 20: Reserved for Future Use
- PCR 21: Reserved for Future Use
- PCR 22: Reserved for Future Use
- PCR 23: Reserved for Future Use
-
-
-
- A platform validation profile consists of a set of Platform Configuration Register (PCR) indices. Each PCR index is associated with components that run when Windows starts.
- Use the check boxes below to choose the PCR indices to include in the profile.
- Exercise caution when changing this setting.
- We recommend the default of PCRs 0, 2, 4, and 11.
- For BitLocker protection to take effect, you must include PCR 11.
-
- Consult online documentation for more information about the benefits and risks of changing the default TPM platform validation profile.
-
- PCR 0: Core System Firmware executable code
- PCR 1: Core System Firmware data
- PCR 2: Extended or pluggable executable code
- PCR 3: Extended or pluggable firmware data
- PCR 4: Boot Manager
- PCR 5: GPT / Partition Table
- PCR 6: Resume from S4 and S5 Power State Events
- PCR 7: Secure Boot State
- PCR 8: Initialized to 0 with no Extends (reserved for future use)
- PCR 9: Initialized to 0 with no Extends (reserved for future use)
- PCR 10: Initialized to 0 with no Extends (reserved for future use)
- PCR 11: BitLocker Access Control
- PCR 12: Data events and highly volatile events
- PCR 13: Boot Module Details
- PCR 14: Boot Authorities
- PCR 15: Reserved for Future Use
- PCR 16: Reserved for Future Use
- PCR 17: Reserved for Future Use
- PCR 18: Reserved for Future Use
- PCR 19: Reserved for Future Use
- PCR 20: Reserved for Future Use
- PCR 21: Reserved for Future Use
- PCR 22: Reserved for Future Use
- PCR 23: Reserved for Future Use
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 1.3.6.1.4.1.311.67.1.1
-
-
-
-
- Verify the following additional BCD settings:
-
- Exclude the following additional BCD settings:
-
-
-
-
- Minimum characters:
-
-
-
- Require password for fixed data drive
- Configure password complexity for fixed data drives:
- Minimum password length for fixed data drive:
- Note: You must enable the "Password must meet complexity requirements" policy setting for the password complexity setting to take effect.
-
-
-
- Configure password complexity for operating system drives:
- Minimum password length for operating system drive:
- Note: You must enable the "Password must meet complexity requirements" policy setting for the password complexity setting to take effect.
- Require ASCII-only passwords for removable OS drives
-
-
-
- Require use of smart cards on fixed data drives
-
-
-
- Require password for removable data drive
- Configure password complexity for removable data drives:
- Minimum password length for removable data drive:
-Note: You must enable the "Password must meet complexity requirements" policy setting for the password complexity setting to take effect.
-
-
-
- Allow users to apply BitLocker protection on removable data drives
- Allow users to suspend and decrypt BitLocker protection on removable data drives
-
-
-
- Do not allow write access to devices configured in another organization
-
-
-
-
- Require use of smart cards on removable data drives
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Do not install BitLocker To Go Reader on FAT formatted fixed drives
-
-
-
- Do not install BitLocker To Go Reader on FAT formatted removable drives
-
-
-
- Use BitLocker software-based encryption when hardware encryption is not available
- Restrict encryption algorithms and cipher suites allowed for hardware-based encryption
-
-
- 2.16.840.1.101.3.4.1.2;2.16.840.1.101.3.4.1.42
-
-
-
-
- Use BitLocker software-based encryption when hardware encryption is not available
- Restrict encryption algorithms and cipher suites allowed for hardware-based encryption
-
-
- 2.16.840.1.101.3.4.1.2;2.16.840.1.101.3.4.1.42
-
-
-
-
- Use BitLocker software-based encryption when hardware encryption is not available
- Restrict encryption algorithms and cipher suites allowed for hardware-based encryption
-
-
- 2.16.840.1.101.3.4.1.2;2.16.840.1.101.3.4.1.42
-
-
-
-
- Select an option for the pre-boot recovery message:
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/W32Time.adml b/policy_templates/en-US/W32Time.adml
deleted file mode 100644
index 93a4bf8..0000000
--- a/policy_templates/en-US/W32Time.adml
+++ /dev/null
@@ -1,188 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- This policy setting allows you to specify Clock discipline and General values for the Windows Time service (W32time) for domain controllers including RODCs.
-
-If this policy setting is enabled, W32time Service on target machines use the settings provided here. Otherwise, the service on target machines use locally configured settings values.
-
-For more details on individual parameters, combinations of parameter values as well as definitions of flags, see https://go.microsoft.com/fwlink/?linkid=847809.
-
- FrequencyCorrectRate
-This parameter controls the rate at which the W32time corrects the local clock's frequency. Lower values cause larger corrections; larger values cause smaller corrections. Default: 4 (scalar).
-
- HoldPeriod
-This parameter indicates how many consistent time samples the client computer must receive in a series before subsequent time samples are evaluated as potential spikes. Default: 5
-
- LargePhaseOffset
-If a time sample differs from the client computer's local clock by more than LargePhaseOffset, the local clock is deemed to have drifted considerably, or in other words, spiked. Default: 50,000,000 100-nanosecond units (ns) or 5 seconds.
-
- MaxAllowedPhaseOffset
-If a response is received that has a time variation that is larger than this parameter value, W32time sets the client computer's local clock immediately to the time that is accepted as accurate from the Network Time Protocol (NTP) server. If the time variation is less than this value, the client computer's local clock is corrected gradually. Default: 300 seconds.
-
- MaxNegPhaseCorrection
-If a time sample is received that indicates a time in the past (as compared to the client computer's local clock) that has a time difference that is greater than the MaxNegPhaseCorrection value, the time sample is discarded. Default: 172,800 seconds.
-
- MaxPosPhaseCorrection
-If a time sample is received that indicates a time in the future (as compared to the client computer's local clock) that has a time difference greater than the MaxPosPhaseCorrection value, the time sample is discarded. Default: 172,800 seconds.
-
- PhaseCorrectRate
-This parameter controls how quickly W32time corrects the client computer's local clock difference to match time samples that are accepted as accurate from the NTP server. Lower values cause the clock to correct more quickly; larger values cause the clock to correct more slowly. Default: 7 (scalar).
-
- PollAdjustFactor
-This parameter controls how quickly W32time changes polling intervals. When responses are considered to be accurate, the polling interval lengthens automatically. When responses are considered to be inaccurate, the polling interval shortens automatically. Default: 5 (scalar).
-
- SpikeWatchPeriod
-This parameter specifies the amount of time that samples with time offset larger than LargePhaseOffset are received before these samples are accepted as accurate. SpikeWatchPeriod is used in conjunction with HoldPeriod to help eliminate sporadic, inaccurate time samples that are returned from a peer. Default: 900 seconds.
-
- UpdateInterval
-This parameter specifies the amount of time that W32time waits between corrections when the clock is being corrected gradually. When it makes a gradual correction, the service adjusts the clock slightly, waits this amount of time, and then checks to see if another adjustment is needed, until the correction is finished. Default: 100 1/100th second units, or 1 second.
-
- General parameters:
-
- AnnounceFlags
-This parameter is a bitmask value that controls how time service availability is advertised through NetLogon. Default: 0x0a hexadecimal
-
- EventLogFlags
-This parameter controls special events that may be logged to the Event Viewer System log. Default: 0x02 hexadecimal bitmask.
-
- LocalClockDispersion
-This parameter indicates the maximum error in seconds that is reported by the NTP server to clients that are requesting a time sample. (Applies only when the NTP server is using the time of the local CMOS clock.) Default: 10 seconds.
-
- MaxPollInterval
-This parameter controls the maximum polling interval, which defines the maximum amount of time between polls of a peer. Default: 10 in log base-2, or 1024 seconds. (Should not be set higher than 15.)
-
- MinPollInterval
-This parameter controls the minimum polling interval that defines the minimum amount of time between polls of a peer. Default: 6 in log base-2, or 64 seconds.
-
- ClockHoldoverPeriod
-This parameter indicates the maximum number of seconds a system clock can nominally hold its accuracy without synchronizing with a time source. If this period of time passes without W32time obtaining new samples from any of its input providers, W32time initiates a rediscovery of time sources. Default: 7800 seconds.
-
- RequireSecureTimeSyncRequests
-This parameter controls whether or not the DC will respond to time sync requests that use older authentication protocols. If enabled (set to 1), the DC will not respond to requests using such protocols. Default: 0 Boolean.
-
- UtilizeSslTimeData
-This parameter controls whether W32time will use time data computed from SSL traffic on the machine as an additional input for correcting the local clock. Default: 1 (enabled) Boolean
-
- ClockAdjustmentAuditLimit
-This parameter specifies the smallest local clock adjustments that may be logged to the W32time service event log on the target machine. Default: 800 Parts per million (PPM).
-
- RODC parameters:
-
- ChainEntryTimeout
-This parameter specifies the maximum amount of time that an entry can remain in the chaining table before the entry is considered to be expired. Expired entries may be removed when the next request or response is processed. Default: 16 seconds.
-
- ChainMaxEntries
-This parameter controls the maximum number of entries that are allowed in the chaining table. If the chaining table is full and no expired entries can be removed, any incoming requests are discarded. Default: 128 entries.
-
- ChainMaxHostEntries
-This parameter controls the maximum number of entries that are allowed in the chaining table for a particular host. Default: 4 entries.
-
- ChainDisable
-This parameter controls whether or not the chaining mechanism is disabled. If chaining is disabled (set to 0), the RODC can synchronize with any domain controller, but hosts that do not have their passwords cached on the RODC will not be able to synchronize with the RODC. Default: 0 Boolean.
-
- ChainLoggingRate
-This parameter controls the frequency at which an event that indicates the number of successful and unsuccessful chaining attempts is logged to the System log in Event Viewer. Default: 30 minutes.
-
-
-This policy setting specifies a set of parameters for controlling the Windows NTP Client.
-
-If you enable this policy setting, you can specify the following parameters for the Windows NTP Client.
-
-If you disable or do not configure this policy setting, the WIndows NTP Client uses the defaults of each of the following parameters.
-
-NtpServer
-The Domain Name System (DNS) name or IP address of an NTP time source. This value is in the form of ""dnsName,flags"" where ""flags"" is a hexadecimal bitmask of the flags for that host. For more information, see the NTP Client Group Policy Settings Associated with Windows Time section of the Windows Time Service Group Policy Settings. The default value is ""time.windows.com,0x09"".
-
-Type
-This value controls the authentication that W32time uses. The default value is NT5DS.
-
-CrossSiteSyncFlags
-This value, expressed as a bitmask, controls how W32time chooses time sources outside its own site. The possible values are 0, 1, and 2. Setting this value to 0 (None) indicates that the time client should not attempt to synchronize time outside its site. Setting this value to 1 (PdcOnly) indicates that only the computers that function as primary domain controller (PDC) emulator operations masters in other domains can be used as synchronization partners when the client has to synchronize time with a partner outside its own site. Setting a value of 2 (All) indicates that any synchronization partner can be used. This value is ignored if the NT5DS value is not set. The default value is 2 decimal (0x02 hexadecimal).
-
-ResolvePeerBackoffMinutes
-This value, expressed in minutes, controls how long W32time waits before it attempts to resolve a DNS name when a previous attempt failed. The default value is 15 minutes.
-
-ResolvePeerBackoffMaxTimes
-This value controls how many times W32time attempts to resolve a DNS name before the discovery process is restarted. Each time DNS name resolution fails, the amount of time to wait before the next attempt will be twice the previous amount. The default value is seven attempts.
-
-SpecialPollInterval
-This NTP client value, expressed in seconds, controls how often a manually configured time source is polled when the time source is configured to use a special polling interval. If the SpecialInterval flag is enabled on the NTPServer setting, the client uses the value that is set as the SpecialPollInterval, instead of a variable interval between MinPollInterval and MaxPollInterval values, to determine how frequently to poll the time source. SpecialPollInterval must be in the range of [MinPollInterval, MaxPollInterval], else the nearest value of the range is picked. Default: 1024 seconds.
-
-EventLogFlags
-This value is a bitmask that controls events that may be logged to the System log in Event Viewer. Setting this value to 0x1 indicates that W32time will create an event whenever a time jump is detected. Setting this value to 0x2 indicates that W32time will create an event whenever a time source change is made. Because it is a bitmask value, setting 0x3 (the addition of 0x1 and 0x2) indicates that both time jumps and time source changes will be logged.
-
- This policy setting specifies whether the Windows NTP Client is enabled.
-
-Enabling the Windows NTP Client allows your computer to synchronize its computer clock with other NTP servers. You might want to disable this service if you decide to use a third-party time provider.
-
-If you enable this policy setting, you can set the local computer clock to synchronize time with NTP servers.
-
-If you disable or do not configure this policy setting, the local computer clock does not synchronize time with NTP servers.
-
- This policy setting allows you to specify whether the Windows NTP Server is enabled.
-
-If you enable this policy setting for the Windows NTP Server, your computer can service NTP requests from other computers.
-
-
-If you disable or do not configure this policy setting, your computer cannot service NTP requests from other computers.
-
-
- Global Configuration Settings
- Configure Windows NTP Client
- Enable Windows NTP Client
- Enable Windows NTP Server
- Windows Time Service
- Time Providers
- AllSync
- NoSync
- NT5DS
- NTP
-
-
-
- Clock Discipline Parameters
- FrequencyCorrectRate
- HoldPeriod
- LargePhaseOffset
- MaxAllowedPhaseOffset
- MaxNegPhaseCorrection
- MaxPosPhaseCorrection
- PhaseCorrectRate
- PollAdjustFactor
- SpikeWatchPeriod
- UpdateInterval
- General Parameters
- AnnounceFlags
- EventLogFlags
- LocalClockDispersion
- MaxPollInterval
- MinPollInterval
- ClockHoldoverPeriod
- RequireSecureTimeSyncRequests
- UtilizeSslTimeData
- ClockAdjustmentAuditLimit
- ChainEntryTimeout
- ChainMaxEntries
- ChainMaxHostEntries
- ChainDisable
- ChainLoggingRate
-
-
-
-
- time.windows.com,0x9
-
- Type
- CrossSiteSyncFlags
- ResolvePeerBackoffMinutes
- ResolvePeerBackoffMaxTimes
- SpecialPollInterval
- EventLogFlags
-
-
-
-
diff --git a/policy_templates/en-US/WCM.adml b/policy_templates/en-US/WCM.adml
deleted file mode 100644
index 6bab4ec..0000000
--- a/policy_templates/en-US/WCM.adml
+++ /dev/null
@@ -1,77 +0,0 @@
-
-
-
- Windows Connection Manager Group Policy Settings
- Windows Connection Manager Group Policy Settings
-
-
- Windows Connection Manager
- Prohibit connection to non-domain networks when connected to domain authenticated network
- This policy setting prevents computers from connecting to both a domain based network and a non-domain based network at the same time.
-
-If this policy setting is enabled, the computer responds to automatic and manual network connection attempts based on the following circumstances:
-
-Automatic connection attempts
-- When the computer is already connected to a domain based network, all automatic connection attempts to non-domain networks are blocked.
-- When the computer is already connected to a non-domain based network, automatic connection attempts to domain based networks are blocked.
-
-Manual connection attempts
-- When the computer is already connected to either a non-domain based network or a domain based network over media other than Ethernet, and a user attempts to create a manual connection to an additional network in violation of this policy setting, the existing network connection is disconnected and the manual connection is allowed.
-- When the computer is already connected to either a non-domain based network or a domain based network over Ethernet, and a user attempts to create a manual connection to an additional network in violation of this policy setting, the existing Ethernet connection is maintained and the manual connection attempt is blocked.
-
-If this policy setting is not configured or is disabled, computers are allowed to connect simultaneously to both domain and non-domain networks.
-
- Prohibit connection to roaming Mobile Broadband networks
- This policy setting prevents clients from connecting to Mobile Broadband networks when the client is registered on a roaming provider network.
-
-If this policy setting is enabled, all automatic and manual connection attempts to roaming provider networks are blocked until the client registers with the home provider network.
-
-If this policy setting is not configured or is disabled, clients are allowed to connect to roaming provider Mobile Broadband networks.
-
- Minimize the number of simultaneous connections to the Internet or a Windows Domain
- 0 = Allow simultaneous connections
- 1 = Minimize simultaneous connections
- 2 = Stay connected to cellular
- 3 = Prevent Wi-Fi when on Ethernet
-
- This policy setting determines if a computer can have multiple connections to the internet or to a Windows domain. If multiple connections are allowed, it then determines how network traffic will be routed.
-
- If this policy setting is set to 0, a computer can have simultaneous connections to the internet, to a Windows domain, or to both. Internet traffic can be routed over any connection - including a cellular connection and any metered network. This was previously the Disabled state for this policy setting. This option was first available in Windows 8.
-
- If this policy setting is set to 1, any new automatic internet connection is blocked when the computer has at least one active internet connection to a preferred type of network. Here's the order of preference (from most preferred to least preferred): Ethernet, WLAN, then cellular. Ethernet is always preferred when connected. Users can still manually connect to any network. This was previously the Enabled state for this policy setting. This option was first available in Windows 8.
-
- If this policy setting is set to 2, the behavior is similar to 1. However, if a cellular data connection is available, it will always stay connected for services that require a cellular connection. When the user is connected to a WLAN or Ethernet connection, no internet traffic will be routed over the cellular connection. This option was first available in Windows 10 (Version 1703).
-
- If this policy setting is set to 3, the behavior is similar to 2. However, if there's an Ethernet connection, Windows won't allow users to connect to a WLAN manually. A WLAN can only be connected (automatically or manually) when there's no Ethernet connection.
-
- This policy setting is related to the "Enable Windows to soft-disconnect a computer from a network" policy setting.
-
- Disable power management in connected standby mode
- This policy setting specifies that power management is disabled when the machine enters connected standby mode.
-
-If this policy setting is enabled, Windows Connection Manager does not manage adapter radios to reduce power consumption when the machine enters connected standby mode.
-
-If this policy setting is not configured or is disabled, power management is enabled when the machine enters connected standby mode.
-
- Enable Windows to soft-disconnect a computer from a network
- This policy setting determines whether Windows will soft-disconnect a computer from a network.
-
-If this policy setting is enabled or not configured, Windows will soft-disconnect a computer from a network when it determines that the computer should no longer be connected to a network.
-
-If this policy setting is disabled, Windows will disconnect a computer from a network immediately when it determines that the computer should no longer be connected to a network.
-
-When soft disconnect is enabled:
-- When Windows decides that the computer should no longer be connected to a network, it waits for traffic to settle on that network. The existing TCP session will continue uninterrupted.
-- Windows then checks the traffic level on the network periodically. If the traffic level is above a certain threshold, no further action is taken. The computer stays connected to the network and continues to use it. For example, if the network connection is currently being used to download files from the Internet, the files will continue to be downloaded using that network connection.
-- When the network traffic drops below this threshold, the computer will be disconnected from the network. Apps that keep a network connection active even when they're not actively using it (for example, email apps) might lose their connection. If this happens, these apps should re-establish their connection over a different network.
-
-This policy setting depends on other group policy settings. For example, if 'Minimize the number of simultaneous connections to the Internet or a Windows Domain' is disabled, Windows will not disconnect from any networks.
-
-
-
-
- Minimize Policy Options
-
-
-
-
diff --git a/policy_templates/en-US/WDI.adml b/policy_templates/en-US/WDI.adml
deleted file mode 100644
index aa786eb..0000000
--- a/policy_templates/en-US/WDI.adml
+++ /dev/null
@@ -1,43 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Diagnostics: Configure scenario retention
- This policy setting determines the data retention limit for Diagnostic Policy Service (DPS) scenario data.
-
-If you enable this policy setting, you must enter the maximum size of scenario data that should be retained in megabytes. Detailed troubleshooting data related to scenarios will be retained until this limit is reached.
-
-If you disable or do not configure this policy setting, the DPS deletes scenario data once it exceeds 128 megabytes in size.
-
-No reboots or service restarts are required for this policy setting to take effect: changes take effect immediately.
-
-This policy setting will only take effect when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenario data will not be deleted. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
- Detection, Troubleshooting and Resolution
- Detection and Troubleshooting Only
- Diagnostics: Configure scenario execution level
- This policy setting determines the execution level for Diagnostic Policy Service (DPS) scenarios.
-
-If you enable this policy setting, you must select an execution level from the drop-down menu. If you select problem detection and troubleshooting only, the DPS will detect problems and attempt to determine their root causes. These root causes will be logged to the event log when detected, but no corrective action will be taken. If you select detection, troubleshooting and resolution, the DPS will attempt to automatically fix problems it detects or indicate to the user that assisted resolution is available.
-
-If you disable this policy setting, Windows cannot detect, troubleshoot, or resolve any problems that are handled by the DPS.
-
-If you do not configure this policy setting, the DPS enables all scenarios for resolution by default, unless you configure separate scenario-specific policy settings.
-
-This policy setting takes precedence over any scenario-specific policy settings when it is enabled or disabled. Scenario-specific policy settings only take effect if this policy setting is not configured.
-
-No reboots or service restarts are required for this policy setting to take effect: changes take effect immediately.
-
-
-
-
- Scenario data size limit (in MB)
-
-
- Scenario Execution Level
-
-
-
-
diff --git a/policy_templates/en-US/WPN.adml b/policy_templates/en-US/WPN.adml
deleted file mode 100644
index 8c06674..0000000
--- a/policy_templates/en-US/WPN.adml
+++ /dev/null
@@ -1,134 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Notifications
- Enables group policy for the WNS FQDN
- This policy sets a special WNS FQDN for specific environments.
- Turn off tile notifications
-
- This policy setting turns off tile notifications.
-
- If you enable this policy setting, applications and system features will not be able to update their tiles and tile badges in the Start screen.
-
- If you disable or do not configure this policy setting, tile and badge notifications are enabled and can be turned off by the administrator or user.
-
- No reboots or service restarts are required for this policy setting to take effect.
-
- Turn off toast notifications
-
- This policy setting turns off toast notifications for applications.
-
- If you enable this policy setting, applications will not be able to raise toast notifications.
-
- Note that this policy does not affect taskbar notification balloons.
-
- Note that Windows system features are not affected by this policy. You must enable/disable system features individually to stop their ability to raise toast notifications.
-
- If you disable or do not configure this policy setting, toast notifications are enabled and can be turned off by the administrator or user.
-
- No reboots or service restarts are required for this policy setting to take effect.
-
- Turn off toast notifications on the lock screen
-
- This policy setting turns off toast notifications on the lock screen.
-
- If you enable this policy setting, applications will not be able to raise toast notifications on the lock screen.
-
- If you disable or do not configure this policy setting, toast notifications on the lock screen are enabled and can be turned off by the administrator or user.
-
- No reboots or service restarts are required for this policy setting to take effect.
-
- Turn off notifications network usage
-
- This policy setting blocks applications from using the network to send notifications to update tiles, tile badges, toast, or raw notifications. This policy setting turns off the connection between Windows and the Windows Push Notification Service (WNS). This policy setting also stops applications from being able to poll application services to update tiles.
-
- If you enable this policy setting, applications and system features will not be able receive notifications from the network from WNS or via notification polling APIs.
-
- If you enable this policy setting, notifications can still be raised by applications running on the machine via local API calls from within the application.
-
- If you disable or do not configure this policy setting, the client computer will connect to WNS at user login and applications will be allowed to poll for tile notification updates in the background.
-
- No reboots or service restarts are required for this policy setting to take effect.
-
- Turn off Quiet Hours
-
- This policy setting turns off Quiet Hours functionality.
-
- If you enable this policy setting, toast notifications will not be suppressed and some background tasks will not be deferred during the designated Quiet Hours time window each day.
-
- If you disable this policy setting, toast notifications will be suppressed and some background task deferred during the designated Quiet Hours time window. Users will not be able to change this or any other Quiet Hours settings.
-
- If you do not configure this policy setting, Quiet Hours are enabled by default but can be turned off or by the administrator or user.
-
- Turn off calls during Quiet Hours
- Set the time Quiet Hours begins each day
-
- This policy setting specifies the number of minutes after midnight (local time) that Quiet Hours is to begin each day.
-
- If you enable this policy setting, the specified time will be used, and users will not be able to customize any Quiet Hours settings.
-
- If you disable this policy setting, a default value will be used, and users will not be able to change it or any other Quiet Hours setting.
-
- If you do not configure this policy setting, a default value will be used, which administrators and users will be able to modify.
-
- Set the time Quiet Hours ends each day
-
- This policy setting specifies the number of minutes after midnight (local time) that Quiet Hours is to end each day.
-
- If you enable this policy setting, the specified time will be used, and users will not be able to customize any Quiet Hours settings.
-
- If you disable this policy setting, a default value will be used, and users will not be able to change it or any other Quiet Hours setting.
-
- If you do not configure this policy setting, a default value will be used, which administrators and users will be able to modify.
-
-
- This policy setting blocks voice and video calls during Quiet Hours.
-
- If you enable this policy setting, voice and video calls will be blocked during the designated Quiet Hours time window each day, and users will not be able to customize any other Quiet Hours settings.
-
- If you disable this policy setting, voice and video calls will be allowed during Quiet Hours, and users will not be able to customize this or any other Quiet Hours settings.
-
- If you do not configure this policy setting, voice and video calls will be allowed during Quiet Hours by default. Adminstrators and users will be able to modify this setting.
-
- Turn off notification mirroring
-
- This policy setting turns off notification mirroring.
-
- If you enable this policy setting, notifications from applications and system will not be mirrored to your other devices.
-
- If you disable or do not configure this policy setting, notifications will be mirrored, and can be turned off by the administrator or user.
-
- No reboots or service restarts are required for this policy setting to take effect.
-
- Turn on multiple expanded toast notifications in action center
-
- This policy setting turns on multiple expanded toast notifications in action center.
-
- If you enable this policy setting, the first three notifications of each application will be expanded by default in action center.
-
- If you disable or do not configure this policy setting, only the first notification of each application will be expanded by default in action center.
-
- Windows 10 only. This will be immediately deprecated for Windows 11.
-
- No reboots or service restarts are required for this policy setting to take effect.
-
-
-
-
- Minutes after midnight:
-
-
- Minutes after midnight:
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/WebThreatDefense.adml b/policy_templates/en-US/WebThreatDefense.adml
deleted file mode 100644
index c6756b5..0000000
--- a/policy_templates/en-US/WebThreatDefense.adml
+++ /dev/null
@@ -1,50 +0,0 @@
-
-
-
- WebThreatDefense
- Configuration for WebThreatDefense Service
-
-
- Enhanced Phishing Protection
-
- Service Enabled
-
-This policy setting determines whether Enhanced Phishing Protection in Microsoft Defender SmartScreen is in audit mode or off. Users do not see notifications for any protection scenarios when Enhanced Phishing Protection in Microsoft Defender is in audit mode. Audit mode captures unsafe password entry events and sends telemetry through Microsoft Defender.
-
-If you enable this policy setting, Enhanced Phishing Protection in Microsoft Defender SmartScreen is enabled in audit mode and your users are unable to turn it off.
-
-If you disable this policy setting, Enhanced Phishing Protection in Microsoft Defender SmartScreen is off and it will not capture events, send telemetry, or notify users. Additionally, your users are unable to turn it on.
-
-If you don’t configure this setting, users can decide whether or not they will enable Enhanced Phishing Protection in Microsoft Defender SmartScreen.
-
-
- Notify Malicious
-
-This policy setting determines whether Enhanced Phishing Protection in Microsoft Defender SmartScreen warns your users if they type their work or school password into one of the following malicious scenarios: into a reported phishing site, into a Microsoft login URL with an invalid certificate, or into an application connecting to either a reported phishing site or a Microsoft login URL with an invalid certificate.
-
-If you enable this policy setting, Enhanced Phishing Protection in Microsoft Defender SmartScreen warns your users if they type their work or school password into one of the malicious scenarios described above and encourages them to change their password.
-
-If you disable or don’t configure this policy setting, Enhanced Phishing Protection in Microsoft Defender SmartScreen will not warn your users if they type their work or school password into one of the malicious scenarios described above.
-
-
- Notify Password Reuse
-
-This policy setting determines whether Enhanced Phishing Protection in Microsoft Defender SmartScreen warns your users if they reuse their work or school password.
-
-If you enable this policy setting, Enhanced Phishing Protection in Microsoft Defender SmartScreen warns users if they reuse their work or school password and encourages them to change it.
-
-If you disable or don’t configure this policy setting, Enhanced Phishing Protection in Microsoft Defender SmartScreen will not warn users if they reuse their work or school password.
-
-
- Notify Unsafe App
-
-This policy setting determines whether Enhanced Phishing Protection in Microsoft Defender SmartScreen warns your users if they type their work or school passwords in Notepad, Winword, or M365 Office apps like OneNote, Word, Excel, etc.
-
-If you enable this policy setting, Enhanced Phishing Protection in Microsoft Defender SmartScreen warns your users if they store their password in text editor apps.
-
-If you disable or don’t configure this policy setting, Enhanced Phishing Protection in Microsoft Defender SmartScreen will not warn users if they store their password in text editor apps.
-
-
-
-
-
diff --git a/policy_templates/en-US/WinCal.adml b/policy_templates/en-US/WinCal.adml
deleted file mode 100644
index a2118e7..0000000
--- a/policy_templates/en-US/WinCal.adml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off Windows Calendar
- Windows Calendar is a feature that allows users to manage appointments and tasks by creating personal calendars, publishing them, and subscribing to other users calendars.
-
-If you enable this setting, Windows Calendar will be turned off.
-
-If you disable or do not configure this setting, Windows Calendar will be turned on.
-
-The default is for Windows Calendar to be turned on.
- Windows Calendar
-
-
-
diff --git a/policy_templates/en-US/WinInit.adml b/policy_templates/en-US/WinInit.adml
deleted file mode 100644
index aca3388..0000000
--- a/policy_templates/en-US/WinInit.adml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off legacy remote shutdown interface
- This policy setting controls the legacy remote shutdown interface (named pipe). The named pipe remote shutdown interface is needed in order to shutdown this system from a remote Windows XP or Windows Server 2003 system.
-
-If you enable this policy setting, the system does not create the named pipe remote shutdown interface.
-
-If you disable or do not configure this policy setting, the system creates the named pipe remote shutdown interface.
- Shutdown Options
- Timeout for hung logon sessions during shutdown
- This policy setting configures the number of minutes the system waits for the hung logon sessions before proceeding with the system shutdown.
-
-If you enable this policy setting, the system waits for the hung logon sessions for the number of minutes specified.
-
-If you disable or do not configure this policy setting, the default timeout value is 3 minutes for workstations and 15 minutes for servers.
- Shutdown
- Require use of fast startup
- This policy setting controls the use of fast startup.
-
-If you enable this policy setting, the system requires hibernate to be enabled.
-
-If you disable or do not configure this policy setting, the local setting is used.
-
-
-
- Hung session timeout in Minutes:
-
-
-
-
diff --git a/policy_templates/en-US/WinLogon.adml b/policy_templates/en-US/WinLogon.adml
deleted file mode 100644
index 79e69de..0000000
--- a/policy_templates/en-US/WinLogon.adml
+++ /dev/null
@@ -1,129 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Display information about previous logons during user logon
- This policy setting controls whether or not the system displays information about previous logons and logon failures to the user.
-
-For local user accounts and domain user accounts in domains of at least a Windows Server 2008 functional level, if you enable this setting, a message appears after the user logs on that displays the date and time of the last successful logon by that user, the date and time of the last unsuccessful logon attempted with that user name, and the number of unsuccessful logons since the last successful logon by that user. This message must be acknowledged by the user before the user is presented with the Microsoft Windows desktop.
-
-For domain user accounts in Windows Server 2003, Windows 2000 native, or Windows 2000 mixed functional level domains, if you enable this setting, a warning message will appear that Windows could not retrieve the information and the user will not be able to log on. Therefore, you should not enable this policy setting if the domain is not at the Windows Server 2008 domain functional level.
-
-If you disable or do not configure this setting, messages about the previous logon or logon failures are not displayed.
- Windows Logon Options
- Disconnect
- Lock
- Logoff
- Remove logon hours expiration warnings
- This policy controls whether the logged on user should be notified when his logon hours are about to expire. By default, a user is notified before logon hours expire, if actions have been set to occur when the logon hours expire.
-
-If you enable this setting, warnings are not displayed to the user before the logon hours expire.
-
-If you disable or do not configure this setting, users receive warnings before the logon hours expire, if actions have been set to occur when the logon hours expire.
-
-Note: If you configure this setting, you might want to examine and appropriately configure the “Set action to take when logon hours expire” setting. If “Set action to take when logon hours expire” is disabled or not configured, the “Remove logon hours expiration warnings” setting will have no effect, and users receive no warnings about logon hour expiration
- Set action to take when logon hours expire
- This policy controls which action will be taken when the logon hours expire for the logged on user. The actions include lock the workstation, disconnect the user, or log the user off completely.
-
-If you choose to lock or disconnect a session, the user cannot unlock the session or reconnect except during permitted logon hours.
-
-If you choose to log off a user, the user cannot log on again except during permitted logon hours. If you choose to log off a user, the user might lose unsaved data.
-
-If you enable this setting, the system will perform the action you specify when the user’s logon hours expire.
-
-If you disable or do not configure this setting, the system takes no action when the user’s logon hours expire. The user can continue the existing session, but cannot log on to a new session.
-
-Note: If you configure this setting, you might want to examine and appropriately configure the “Remove logon hours expiration warnings” setting
- Report when logon server was not available during user logon
- This policy controls whether the logged on user should be notified if the logon server could not be contacted during logon and he has been logged on using previously stored account information.
-
-If enabled, a notification popup will be displayed to the user when the user logs on with cached credentials.
-
-If disabled or not configured, no popup will be displayed to the user.
-
- Disable or enable software Secure Attention Sequence
- This policy setting controls whether or not software can simulate the Secure Attention Sequence (SAS).
-
-If you enable this policy setting, you have one of four options:
-
-If you set this policy setting to "None," user mode software cannot simulate the SAS.
-If you set this policy setting to "Services," services can simulate the SAS.
-If you set this policy setting to "Ease of Access applications," Ease of Access applications can simulate the SAS.
-If you set this policy setting to "Services and Ease of Access applications," both services and Ease of Access applications can simulate the SAS.
-
-If you disable or do not configure this setting, only Ease of Access applications running on the secure desktop can simulate the SAS.
-
- None
- Services
- Ease of Access applications
- Services and Ease of Access applications
-
- Custom User Interface
- Specifies an alternate user interface.
-
-The Explorer program (%windir%\explorer.exe) creates the familiar Windows interface, but you can use this setting to specify an alternate interface. If you enable this setting, the system starts the interface you specify instead of Explorer.exe.
-
-To use this setting, copy your interface program to a network share or to your system drive. Then, enable this setting, and type the name of the interface program, including the file name extension, in the Shell name text box. If the interface program file is not located in a folder specified in the Path environment variable for your system, enter the fully qualified path to the file.
-
-If you disable this setting or do not configure it, the setting is ignored and the system displays the Explorer interface.
-
-Tip: To find the folders indicated by the Path environment variable, click System Properties in Control Panel, click the Advanced tab, click the Environment Variables button, and then, in the System variables box, click Path.
-
- Sign-in and lock last interactive user automatically after a restart
- This policy setting controls whether a device will automatically sign in and lock the last interactive user after the system restarts or after a shutdown and cold boot.
-
-This only occurs if the last interactive user didn’t sign out before the restart or shutdown.
-
-If the device is joined to Active Directory or Azure Active Directory, this policy only applies to Windows Update restarts. Otherwise, this will apply to both Windows Update restarts and user-initiated restarts and shutdowns.
-
-If you don’t configure this policy setting, it is enabled by default. When the policy is enabled, the user is automatically signed in and the session is automatically locked with all lock screen apps configured for that user after the device boots.
-
-After enabling this policy, you can configure its settings through the ConfigAutomaticRestartSignOn policy, which configures the mode of automatically signing in and locking the last interactive user after a restart or cold boot.
-
-If you disable this policy setting, the device does not configure automatic sign in. The user’s lock screen apps are not restarted after the system restarts.
-
- Configure the mode of automatically signing in and locking last interactive user after a restart or cold boot
- This policy setting controls the configuration under which an automatic restart and sign on and lock occurs after a restart or cold boot. If you chose “Disabled” in the “Sign-in and lock last interactive user automatically after a restart” policy, then automatic sign on will not occur and this policy does not need to be configured.
-
-If you enable this policy setting, you can choose one of the following two options:
-
-1. “Enabled if BitLocker is on and not suspended” specifies that automatic sign on and lock will only occur if BitLocker is active and not suspended during the reboot or shutdown. Personal data can be accessed on the device’s hard drive at this time if BitLocker is not on or suspended during an update. BitLocker suspension temporarily removes protection for system components and data but may be needed in certain circumstances to successfully update boot-critical components.
- BitLocker is suspended during updates if:
- - The device doesn’t have TPM 2.0 and PCR7, or
- - The device doesn’t use a TPM-only protector
-2. “Always Enabled” specifies that automatic sign on will happen even if BitLocker is off or suspended during reboot or shutdown. When BitLocker is not enabled, personal data is accessible on the hard drive. Automatic restart and sign on should only be run under this condition if you are confident that the configured device is in a secure physical location.
-
-If you disable or don’t configure this setting, automatic sign on will default to the “Enabled if BitLocker is on and not suspended” behavior.
-
- Enabled if BitLocker is on and not suspended
- Always Enabled
-
- Enable MPR notifications for the system
- This policy controls the configuration under which winlogon sends MPR notifications in the system.
-
-If you enable this setting or do not configure it, winlogon sends MPR notifications if a credential manager is configured.
-
-If you disable this setting, winlogon does not send MPR notifications.
-
-
-
-
- Set action to take when logon hours expire
-
-
- Set which software is allowed to generate the Secure Attention Sequence
-
-
- Configure the mode of automatically signing in and locking last interactive user after a restart or cold boot
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/WinMaps.adml b/policy_templates/en-US/WinMaps.adml
deleted file mode 100644
index c00cdae..0000000
--- a/policy_templates/en-US/WinMaps.adml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Maps
- Turn off Automatic Download and Update of Map Data
- Enables or disables the automatic download and update of map data.
-
-If you enable this setting the automatic download and update of map data is turned off.
-
-If you disable this setting the automatic download and update of map data is turned on.
-
-If you don't configure this setting the automatic download and update of map data is determined by a registry setting that the user can change using Windows Settings.
- Turn off unsolicited network traffic on the Offline Maps settings page
- This policy setting allows you to turn on or turn off unsolicited network traffic on the Offline Maps page in Settings > System > Offline Maps.
-
-If you enable this policy setting, features that generate network traffic on the Offline Maps settings page are turned off. Note: This may turn off the entire settings page.
-
-If you disable or do not configure this policy setting, the Offline Maps setting page may generate network traffic.
-
-
-
diff --git a/policy_templates/en-US/Windows.adml b/policy_templates/en-US/Windows.adml
deleted file mode 100644
index 743030a..0000000
--- a/policy_templates/en-US/Windows.adml
+++ /dev/null
@@ -1,116 +0,0 @@
-
-
-
- Windows Vista base categories and supported component definitions
- This file contains all the base categories and supported component definitions used by operating system components.
-
-
-
- Windows Server 2008 and Windows Vista
- Windows 2000 or later, running IIS. Not supported on Windows Server 2003.
- At least Internet Explorer 6 Service Pack 1
- At least Windows 2000
- Windows 2000 only
- At least Windows 2000 Service Pack 1
- At least Windows 2000 Service Pack 3
- Windows XP Professional Service Pack 1 or At least Windows 2000 Service Pack 3
- Windows Server 2012 R2, Windows 8.1, Windows RT 8.1, Windows Server 2008, Windows Server 2003, Windows 7, Windows Vista, Windows XP Professional Service Pack 1 and Windows 2000 Service Pack 3
- At least Windows Server 2003
- Windows Server 2003 only
- Windows Server 2003 and Windows XP only
- Windows Server 2003, Windows XP, and Windows 2000 only
- At least Windows Server 2003 operating systems, Windows XP Professional Service Pack 1, or Windows 2000 Service Pack 3
- At least Windows Vista
- At least Windows Vista Service Pack 1
- Windows Vista only
- At least Windows Server 2003 operating systems or Windows XP Professional
- Windows XP or at least Windows Vista
- At least Windows Server 2003 operating systems, Windows XP Professional Service Pack 1, or Windows 2000 Service Pack 4
- At least Windows Server 2003 operating systems Service Pack 1, Windows XP Professional Service Pack 2, or Windows 2000 Service Pack 5
- Windows XP Professional only
- At least Windows Server 2003 operating systems or Windows XP Professional with SP1
- At least Windows XP Professional with SP2
- At least Windows Server 2003 operating systems or Windows XP Professional with SP2
- At least Windows Server 2003 operating systems with SP1 or Windows XP Professional with SP2
- Windows Server 2003 and Windows XP only
- At least Windows Server 2008 R2 or Windows 7
- At least Windows Server 2012, Windows 8 or Windows RT
- At least Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1
- At least Windows Server 2012 R2 or Windows 8.1
- At least Windows 8.1 or Windows RT 8.1
- Windows Server 2012, Windows 8, Windows RT, Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1 only
- Windows Server 2012 R2, Windows 8.1 or Windows RT 8.1 only
- Windows Server 2012 R2, Windows 8.1, Windows RT 8.1, Windows Server 2008, Windows Server 2003, Windows 7, Windows Vista, Windows XP, and Windows 2000
- Windows 8.1, Windows 8, Windows 7, and Windows Vista only
- At least Windows Server 2016, Windows 10
- Windows Server 2016 Version 1703, Windows 10 Version 1703, Windows 10, Windows 8.1, Windows 8, Windows 7, and Windows Vista only
- Windows Server 2016 Version 1709, Windows 10 Version 1709, Windows Server 2016 Version 1703, Windows 10 Version 1703, Windows 10, Windows 8.1, Windows 8, Windows 7, and Windows Vista only
- Windows Server 2016 Version 1709, Windows 10 Version 1709, Windows Server 2016 Version 1703, Windows 10 Version 1703, Windows 10, Windows 8.1, Windows 8, and Windows 7 only
- Windows Server 2016, Windows 10 up to Version 1703
- At least Windows Server 2016, Windows 10 Version 1607
- At least Windows Server 2016, Windows 10 Version 1703
- At least Windows Server 2016, Windows 10 Version 1709
- At least Windows Server 2016, Windows 10 Version 1803
- At least Windows Server 2016, Windows 10 Version 1809
- At least Windows Server 2016, Windows 10 Version 1903
- At least Windows 10 Version 1903
- At least Windows Server 2016, Windows 10 Version 1909
- At least Windows 10 Version 1909
- At least Windows Server 2019 Version 2004, Windows 10 Version 2004
- At least Windows 10 Version 2004
- Windows 10 only with at least Windows 10 Version 2004
- At least Windows Server 2016, Windows 10 Version 2106
- At least Windows 10 Version 2106
- At least Windows Server 2016 or Windows 10
- At least Windows 10
- Windows 10 Enterprise, Windows 10 Education, or later
- Windows 10 Enterprise or Windows 10 Education with Microsoft Defender Application Guard in Enterprise mode
- Microsoft Edge on Windows 10 Enterprise or Windows 10 Education with Microsoft Defender Application Guard in Enterprise mode
- At least Windows Server 2016
- Windows 11 SE
- At least Windows 11 Version 22H2
- At least Windows 11 Version 22H2
- At least Windows 11 Pro, Enterprise, or Education
- At least Windows 11
- At least Windows Server 2012, Windows 8 or Windows RT or at least Internet Explorer 10
- Windows Server 2008, Windows Server 2003, Windows Vista, Windows XP, and Windows 2000
- Windows Server 2008, Windows Server 2003, Windows Vista, and Windows XP
- Windows Server 2008, Windows Server 2003, Windows Vista, and Windows XP SP2
- Windows Server 2008 R2 and Windows 7
- Windows Server 2008, Windows 7, and Windows Vista
- Windows Server 2008, Windows Server 2003, Windows 7, Windows Vista, and Windows XP
- Windows Server 2008, Windows Server 2003, Windows 7, Windows Vista, Windows XP, and Windows 2000
- At least Windows 2000 through Windows 8.1 or Windows Server 2012 R2
- At least Windows 7 through Windows 8.1 or Windows Server 2012 R2
- Windows Server 2008, Windows 7, Windows Vista, and Windows 10
- Windows Server 2008, Windows Server 2003, Windows 7, Windows Vista, Windows XP, and Windows 10
- Windows Server 2008, Windows Server 2003, Windows 7, Windows Vista, Windows XP, Windows 2000, and Windows 10
- At least Windows 8.1 Update 2
- Windows operating systems from Windows Vista through Windows 7
- Windows Server 2003 and versions of Windows from Windows XP Professional through Windows 7.
- System
- Allows configuration of various system component settings.
- Internet Communication Management
- Internet Communication settings
- Troubleshooting and Diagnostics
- Windows Components
- Contains settings for operating system components.
- File Explorer
- Manages File Explorer settings. These include shell properties, folder options, file menus, and available drives.
- Tablet PC
- Data Collection and Preview Builds
- Network
- Allows configuration of components of the operating system used by a client computer to connect to a network. This includes DNS settings and Offline Files.
- Shared Folders
- Manages configuration and behavior of shared folders.
- Printers
- Manages network printer configuration and publishing options.
- Start Menu and Taskbar
- Contains settings that allow you to add, remove, or disable items from the Start menu, taskbar, and notification area.
- Control Panel
- Contains settings to allow configuration of Control Panel, including the items that it does or does not display.
- Desktop
- Contains settings to manage behavior of the user's desktop, as well as which default icons are displayed on that desktop.
-
-
-
diff --git a/policy_templates/en-US/WindowsAnytimeUpgrade.adml b/policy_templates/en-US/WindowsAnytimeUpgrade.adml
deleted file mode 100644
index 764f6b6..0000000
--- a/policy_templates/en-US/WindowsAnytimeUpgrade.adml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Add features to Windows 10
- Contains settings to control the behavior of the Add features to Windows 10 wizard.
- Prevent the wizard from running.
- By default, Add features to Windows 10 is available for all administrators.
-
-If you enable this policy setting, the wizard will not run.
-
-If you disable this policy setting or set it to Not Configured, the wizard will run.
-
-
-
diff --git a/policy_templates/en-US/WindowsBackup.adml b/policy_templates/en-US/WindowsBackup.adml
deleted file mode 100644
index 7ededcb..0000000
--- a/policy_templates/en-US/WindowsBackup.adml
+++ /dev/null
@@ -1,42 +0,0 @@
-
-
-
- Windows Backup
- Windows Backup
-
-
- Allow only system backup
- This policy setting allows you to manage whether backups of only system volumes is allowed or both OS and data volumes can be backed up.
-
-If you enable this policy setting, machine administrator/backup operator can backup only volumes hosting OS components and no data only volumes can be backed up.If you disable or do not configure this policy setting, backups can include both system or data volumes.
- Disallow locally attached storage as backup target
- This policy setting allows you to manage whether backups of a machine can run to locally attached storage or not.
-
-If you enable this policy setting, machine administrator/backup operator cannot use Windows Server Backup to run backups to a locally attached storage or disk.
-
-If you disable or do not configure this policy setting, there is no restriction on locally attached storage or disk being backup target.
- Disallow network as backup target
- This policy setting allows you to manage whether backups of a machine can run to a network share or not.
-
-If you enable this policy setting, machine administrator/backup operator cannot use Windows Server Backup to run backups to a network share.
-
-If you disable or do not configure this policy setting, there is no restriction on network share being backup target.
- Disallow optical media as backup target
- This policy setting allows you to manage whether backups of a machine can run to an optical media or not.
-
-If you enable this policy setting, machine administrator/backup operator cannot use Windows Server Backup to run backups to an optical media.
-
-If you disable or do not configure this policy setting, there is no restriction on optical media being backup target.
- Disallow run-once backups
- This policy setting allows you to manage whether run-once backups of a machine can be run or not.
-
-If you enable this policy setting, machine administrator/backup operator cannot use Windows Server Backup to run non-scheduled run-once backups.
-
-If you disable or do not configure this policy setting, there is no restriction on running run-once backups.
- Windows Server 2008 and later.
- Backup
- Server
- Windows Components
-
-
-
diff --git a/policy_templates/en-US/WindowsColorSystem.adml b/policy_templates/en-US/WindowsColorSystem.adml
deleted file mode 100644
index 22a2ee3..0000000
--- a/policy_templates/en-US/WindowsColorSystem.adml
+++ /dev/null
@@ -1,18 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Prohibit installing or uninstalling color profiles
- This policy setting affects the ability of users to install or uninstall color profiles.
-
-If you enable this policy setting, users cannot install new color profiles or uninstall previously installed color profiles.
-
-If you disable or do not configure this policy setting, all users can install new color profiles. Standard users can uninstall color profiles that they previously installed. Administrators will be able to uninstall all color profiles.
- Windows Color System
- Contains settings for managing the list of installed color profiles, and the associations between color profiles and color devices.
-
-
-
diff --git a/policy_templates/en-US/WindowsConnectNow.adml b/policy_templates/en-US/WindowsConnectNow.adml
deleted file mode 100644
index f71844d..0000000
--- a/policy_templates/en-US/WindowsConnectNow.adml
+++ /dev/null
@@ -1,41 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Windows Connect Now
- Prohibit access of the Windows Connect Now wizards
- This policy setting prohibits access to Windows Connect Now (WCN) wizards.
-
-If you enable this policy setting, the wizards are turned off and users have no access to any of the wizard tasks. All the configuration related tasks, including "Set up a wireless router or access point" and "Add a wireless device" are disabled.
-
-If you disable or do not configure this policy setting, users can access the wizard tasks, including "Set up a wireless router or access point" and "Add a wireless device." The default for this policy setting allows users to access all WCN wizards.
- Configuration of wireless settings using Windows Connect Now
- This policy setting allows the configuration of wireless settings using Windows Connect Now (WCN). The WCN Registrar enables the discovery and configuration of devices over Ethernet (UPnP), over In-band 802.11 WLAN, through the Windows Portable Device API (WPD), and via USB Flash drives.
-
-Additional options are available to allow discovery and configuration over a specific medium.
-
-If you enable this policy setting, additional choices are available to turn off the operations over a specific medium.
-
-If you disable this policy setting, operations are disabled over all media.
-
-If you do not configure this policy setting, operations are enabled over all media.
-
-The default for this policy setting allows operations over all media.
- WCN over Ethernet (UPnP)
- WCN over In-band 802.11 WLAN
-
-
-
- Turn off ability to configure using WCN over Ethernet (UPnP)
- Turn off ability to configure using WCN over In-band 802.11 WLAN
- Turn off ability to configure using a USB Flash Drive
- Turn off ability to configure Windows Portable Device (WPD)
- Maximum number of WCN devices allowed:
- Higher precedence medium for devices discovered by multiple media:
-
-
-
-
diff --git a/policy_templates/en-US/WindowsDefender.adml b/policy_templates/en-US/WindowsDefender.adml
deleted file mode 100644
index 59adcca..0000000
--- a/policy_templates/en-US/WindowsDefender.adml
+++ /dev/null
@@ -1,1343 +0,0 @@
-
-enter display name here
-enter description here
-
-
- Microsoft Defender Antivirus
- Endpoint Protection
- Exclusions
- Features
- Device Control
- Microsoft Defender Exploit Guard
- Attack Surface Reduction
- Controlled Folder Access
- Network Protection
- Network Inspection System
- Exclusions
- Quarantine
- Real-time Protection
- Remediation
- Reporting
- Scan
- Security Intelligence Updates
- MAPS
- Threats
- Client Interface
- MpEngine
- Allow antimalware service to startup with normal priority
- This policy setting controls the load priority for the antimalware service. Increasing the load priority will allow for faster service startup, but may impact performance.
-
- If you enable or do not configure this setting, the antimalware service will load as a normal priority task.
-
- If you disable this setting, the antimalware service will load as a low priority task.
-
- Allows Microsoft Defender Antivirus to update and communicate over a metered connection.
-
- Disabled (Default):
- Updates and communications are not allowed over metered connections.
-
- Enabled:
- Allow managed devices to update through metered connections. Data charges may apply.
- Control whether or not exclusions are visible to Local Admins.
-
- This policy setting controls whether or not exclusions are visible to Local Admins. For end users (that are not Local Admins) exclusions are not visible, whether or not this setting is enabled.
- Disabled(Default):
- If you disable or do not configure this setting, Local Admins will be able to see exclusions in the Windows Security App or via PowerShell.
-
- Enabled:
- If you enable this setting, Local Admins will no longer be able to see the exclusion list in Windows Security App or via PowerShell.
- Note: Applying this setting will not remove exclusions, it will only prevent them from being visible to Local Admins. This is reflected in Get-MpPreference.
- This settings controls whether Network Protection is allowed to be configured into block or audit mode on Windows Server.
-
- Disabled (Default):
- If Not Configured or Disabled, network protection is not allowed to be configured into block or audit mode on Windows Server.
-
- Enabled:
- If Enabled, administrators can control whether Network Protection is allowed to be configured into block or audit mode on Windows Server.
- Note, that this configuration is dependent on the EnableNetworkProtection configuration. If this configuration is false, EnableNetworkProtection will be ignored, otherwise network protection will start on Windows Server depending on the value of EnableNetworkProtection.
- This setting controls datagram processing for network protection.
-
- Enabled (Default):
- If Not Configured or Disabled, datagram processing will be enabled for network protection.
-
- Enabled:
- If Enabled, datagram processing will be disabled for network protection.
- Turn off Auto Exclusions
-
- Allows an administrator to specify if Automatic Exclusions feature for Server SKUs should be turned off.
-
- Disabled (Default):
- Microsoft Defender will exclude pre-defined list of paths from the scan to improve performance.
-
- Enabled:
- Microsoft Defender will not exclude pre-defined list of paths from scans. This can impact machine performance in some scenarios.
-
- Not configured:
- Same as Disabled.
-
- Turn off Endpoint Protection
- This policy setting turns off Endpoint Protection.
-
- If you enable this policy setting, Endpoint Protection does not run, and computers are not scanned for malware or other potentially unwanted software.
-
- If you disable or do not configure this policy setting, by default Endpoint Protection runs and computers are scanned for malware and other potentially unwanted software.
-
- Turn off Microsoft Defender Antivirus
- This policy setting turns off Microsoft Defender Antivirus.
-
- If you enable this policy setting, Microsoft Defender Antivirus does not run, and will not scan computers for malware or other potentially unwanted software.
-
- If you disable this policy setting, Microsoft Defender Antivirus will run regardless of any other installed antivirus product.
-
- If you do not configure this policy setting, Windows will internally manage Microsoft Defender Antivirus. If you install another antivirus program, Windows automatically disables Microsoft Defender Antivirus. Otherwise, Microsoft Defender Antivirus will scan your computers for malware and other potentially unwanted software.
-
- Enabling or disabling this policy may lead to unexpected or unsupported behavior. It is recommended that you leave this policy setting unconfigured.
- Configure local administrator merge behavior for lists
- This policy setting controls whether or not complex list settings configured by a local administrator are merged with Group Policy settings. This setting applies to lists such as threats and Exclusions.
-
- If you disable or do not configure this setting, unique items defined in Group Policy and in preference settings configured by the local administrator will be merged into the resulting effective policy. In the case of conflicts, Group policy Settings will override preference settings.
-
- If you enable this setting, only items defined by Group Policy will be used in the resulting effective policy. Group Policy settings will override preference settings configured by the local administrator.
- Turn off routine remediation
-
- This policy setting allows you to configure whether Microsoft Defender Antivirus automatically takes action on all detected threats. The action to be taken on a particular threat is determined by the combination of the policy-defined action, user-defined action, and the signature-defined action.
-
- If you enable this policy setting, Microsoft Defender Antivirus does not automatically take action on the detected threats, but prompts users to choose from the actions available for each threat.
-
- If you disable or do not configure this policy setting, Microsoft Defender Antivirus automatically takes action on all detected threats after a nonconfigurable delay of approximately five seconds.
-
- This policy setting allows you to configure whether Endpoint Protection automatically takes action on all detected threats. The action to be taken on a particular threat is determined by the combination of the policy-defined action, user-defined action, and the signature-defined action.
-
- If you enable this policy setting, Endpoint Protection does not automatically take action on the detected threats, but prompts users to choose from the actions available for each threat.
-
- If you disable or do not configure this policy setting, Endpoint Protection automatically takes action on all detected threats after a nonconfigurable delay of approximately five seconds.
-
- Define addresses to bypass proxy server
- This policy, if defined, will prevent antimalware from using the configured proxy server when communicating with the specified IP addresses. The address value should be entered as a valid URL.
-
- If you enable this setting, the proxy server will be bypassed for the specified addresses.
-
- If you disable or do not configure this setting, the proxy server will not be bypassed for the specified addresses.
- Define proxy auto-config (.pac) for connecting to the network
- This policy setting defines the URL of a proxy .pac file that should be used when the client attempts to connect the network for security intelligence updates and MAPS reporting. If the proxy auto-config fails or if there is no proxy auto-config specified, the client will fall back to the alternative options (in order):
- 1. Proxy server (if specified)
- 2. Proxy .pac URL (if specified)
- 3. None
- 4. Internet Explorer proxy settings
- 5. Autodetect
-
- If you enable this setting, the proxy setting will be set to use the specified proxy .pac according to the order specified above.
-
- If you disable or do not configure this setting, the proxy will skip over this fallback step according to the order specified above.
- Define proxy server for connecting to the network
- This policy setting allows you to configure the named proxy that should be used when the client attempts to connect to the network for security intelligence updates and MAPS reporting. If the named proxy fails or if there is no proxy specified, the client will fall back to the alternative options (in order):
- 1. Proxy server (if specified)
- 2. Proxy .pac URL (if specified)
- 3. None
- 4. Internet Explorer proxy settings
- 5. Autodetect
-
- If you enable this setting, the proxy will be set to the specified URL according to the order specified above. The URL should be proceeded with either http:// or https://.
-
- If you disable or do not configure this setting, the proxy will skip over this fallback step according to the order specified above.
-
- Randomize scheduled task times
- This policy setting allows you to configure the scheduled scan, and the scheduled security intelligence update, start time window in hours.
-
- If you disable or do not configure this setting, scheduled tasks will begin at a random time within 4 hours after the time specified in Task Scheduler.
- If you enable this setting, you can widen, or narrow, this randomization period. Specify a randomization window of between 1 and 23 hours.
- Configure scheduled task times randomization window
- This policy setting allows you to configure scheduled scan start time and the scheduled security intelligence update start time window in hours.
-
- If you disable or do not configure this setting, scheduled tasks will begin at a random time within an interval of 4 hours after the specified start time.
- If you enable this setting, you must pick a randomization window in hours. The possible randomization window interval is between 1 and 23 hours.
- Allow antimalware service to remain running always
- This policy setting allows you to configure whether or not the antimalware service remains running when antivirus and antispyware security intelligence is disabled. It is recommended that this setting remain disabled.
-
- If you enable this setting, the antimalware service will always remain running even if both antivirus and antispyware security intelligence is disabled.
-
- If you disable or do not configure this setting, the antimalware service will be stopped when both antivirus and antispyware security intelligence is disabled. If the computer is restarted, the service will be started if it is set to Automatic startup. After the service has started, there will be a check to see if antivirus and antispyware security intelligence is enabled. If at least one is enabled, the service will remain running. If both are disabled, the service will be stopped.
- Configure detection for potentially unwanted applications
-
- Enable or disable detection for potentially unwanted applications. You can choose to block, audit, or allow when potentially unwanted software is being downloaded or attempts to install itself on your computer.
-
- Enabled:
- Specify the mode in the Options section:
- -Block: Potentially unwanted software will be blocked.
- -Audit Mode: Potentially unwanted software will not be blocked, however if this feature would have blocked access if it were set to Block, then a record of the event will be in the event logs.
-
- Disabled:
- Potentially unwanted software will not be blocked.
-
- Not configured:
- Same as Disabled.
-
- Define the directory path to copy support log files
- This policy setting allows you to configure the directory path where the support log files would be copied to. The value of this setting should be a valid directory path.
-
- If you enable this setting, the support log files will be copied to the specified support log location path.
-
- If you disable or do not configure this setting, the support logs files will not be copied to any location.
- Extension Exclusions
- This policy setting allows you specify a list of file types that should be excluded from scheduled, custom, and real-time scanning. File types should be added under the Options for this setting. Each entry must be listed as a name value pair, where the name should be a string representation of the file type extension (such as "obj" or "lib"). The value is not used and it is recommended that this be set to 0.
- Path Exclusions
- This policy setting allows you to disable scheduled and real-time scanning for files under the paths specified or for the fully qualified resources specified. Paths should be added under the Options for this setting. Each entry must be listed as a name value pair, where the name should be a string representation of a path or a fully qualified resource name. As an example, a path might be defined as: "c:\Windows" to exclude all files in this directory. A fully qualified resource name might be defined as: "C:\Windows\App.exe". The value is not used and it is recommended that this be set to 0.
- Process Exclusions
- This policy setting allows you to disable real-time scanning for any file opened by any of the specified processes. This policy does not apply to scheduled scans. The process itself will not be excluded. To exclude the process, use the Path exclusion. Processes should be added under the Options for this setting. Each entry must be listed as a name value pair, where the name should be a string representation of the path to the process image. Note that only executables can be excluded. For example, a process might be defined as: "c:\windows\app.exe". The value is not used and it is recommended that this be set to 0.
- Ip Address Exclusions
- Allows an administrator to explicitly disable network packet inspection made by wdnisdrv on a particular set of IP addresses.
- Turn on protocol recognition
- This policy setting allows you to configure protocol recognition for network protection against exploits of known vulnerabilities.
-
- If you enable or do not configure this setting, protocol recognition will be enabled.
-
- If you disable this setting, protocol recognition will be disabled.
- Turn on definition retirement
- This policy setting allows you to configure definition retirement for network protection against exploits of known vulnerabilities. Definition retirement checks to see if a computer has the required security updates necessary to protect it against a particular vulnerability. If the system is not vulnerable to the exploit detected by a definition, then that definition is "retired". If all security intelligence for a given protocal are retired then that protocol is no longer parsed. Enabling this feature helps to improve performance. On a computer that is up-to-date with all the latest security updates, network protection will have no impact on network performance.
-
- If you enable or do not configure this setting, definition retirement will be enabled.
-
- If you disable this setting, definition retirement will be disabled.
- Specify additional definition sets for network traffic inspection
- This policy setting defines additional definition sets to enable for network traffic inspection. Definition set GUIDs should be added under the Options for this setting. Each entry must be listed as a name value pair, where the name should be a string representation of a definition set GUID. As an example, the definition set GUID to enable test security intelligence is defined as: “{b54b6ac9-a737-498e-9120-6616ad3bf590}”. The value is not used and it is recommended that this be set to 0.
- Configure local setting override for the removal of items from Quarantine folder
- This policy setting configures a local override for the configuration of the number of days items should be kept in the Quarantine folder before being removed. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure removal of items from Quarantine folder
- This policy setting defines the number of days items should be kept in the Quarantine folder before being removed.
-
- If you enable this setting, items will be removed from the Quarantine folder after the number of days specified.
-
- If you disable or do not configure this setting, items will be kept in the quarantine folder indefinitely and will not be automatically removed.
-
- Turn on script scanning
- This policy setting allows you to configure script scanning.
-
- If you enable or do not configure this setting, script scanning will be enabled.
-
- If you disable this setting, script scanning will be disabled.
-
- Turn on behavior monitoring
- This policy setting allows you to configure behavior monitoring.
-
- If you enable or do not configure this setting, behavior monitoring will be enabled.
-
- If you disable this setting, behavior monitoring will be disabled.
- Scan all downloaded files and attachments
- This policy setting allows you to configure scanning for all downloaded files and attachments.
-
- If you enable or do not configure this setting, scanning for all downloaded files and attachments will be enabled.
-
- If you disable this setting, scanning for all downloaded files and attachments will be disabled.
- Monitor file and program activity on your computer
- This policy setting allows you to configure monitoring for file and program activity.
-
- If you enable or do not configure this setting, monitoring for file and program activity will be enabled.
-
- If you disable this setting, monitoring for file and program activity will be disabled.
- Turn on raw volume write notifications
- This policy setting controls whether raw volume write notifications are sent to behavior monitoring.
-
- If you enable or do not configure this setting, raw write notifications will be enabled.
-
- If you disable this setting, raw write notifications be disabled.
- Turn off real-time protection
- This policy turns off real-time protection in Microsoft Defender Antivirus.
-
- Real-time protection consists of always-on scanning with file and process behavior monitoring and heuristics. When real-time protection is on, Microsoft Defender Antivirus detects malware and potentially unwanted software that attempts to install itself or run on your device, and prompts you to take action on malware detections.
-
- If you enable this policy setting, real-time protection is turned off.
-
- If you either disable or do not configure this policy setting, real-time protection is turned on.
-
- This policy setting turns off real-time protection prompts for known malware detection.
-
- Endpoint Protection alerts you when malware or potentially unwanted software attempts to install itself or to run on your computer.
-
- If you enable this policy setting, Endpoint Protection will not prompt users to take actions on malware detections.
-
- If you disable or do not configure this policy setting, Endpoint Protection will prompt users to take actions on malware detections.
-
- Turn on process scanning whenever real-time protection is enabled
- This policy setting allows you to configure process scanning when real-time protection is turned on. This helps to catch malware which could start when real-time protection is turned off.
-
- If you enable or do not configure this setting, a process scan will be initiated when real-time protection is turned on.
-
- If you disable this setting, a process scan will not be initiated when real-time protection is turned on.
- Define the maximum size of downloaded files and attachments to be scanned
- This policy setting defines the maximum size (in kilobytes) of downloaded files and attachments that will be scanned.
-
- If you enable this setting, downloaded files and attachments smaller than the size specified will be scanned.
-
- If you disable or do not configure this setting, a default size will be applied.
- Configure local setting override for turn on behavior monitoring
- This policy setting configures a local override for the configuration of behavior monitoring. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure local setting override for monitoring file and program activity on your computer
- This policy setting configures a local override for the configuration of monitoring for file and program activity on your computer. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure local setting override for scanning all downloaded files and attachments
- This policy setting configures a local override for the configuration of scanning for all downloaded files and attachments. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure local setting override to turn on real-time protection
- This policy setting configures a local override for the configuration to turn on real-time protection. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure local setting override for monitoring for incoming and outgoing file activity
- This policy setting configures a local override for the configuration of monitoring for incoming and outgoing file activity. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure monitoring for incoming and outgoing file and program activity
- This policy setting allows you to configure monitoring for incoming and outgoing files, without having to turn off monitoring entirely. It is recommended for use on servers where there is a lot of incoming and outgoing file activity but for performance reasons need to have scanning disabled for a particular scan direction. The appropriate configuration should be evaluated based on the server role.
-
- Note that this configuration is only honored for NTFS volumes. For any other file system type, full monitoring of file and program activity will be present on those volumes.
-
- The options for this setting are mutually exclusive:
- 0 = Scan incoming and outgoing files (default)
- 1 = Scan incoming files only
- 2 = Scan outgoing files only
-
- Any other value, or if the value does not exist, resolves to the default (0).
-
- If you enable this setting, the specified type of monitoring will be enabled.
-
- If you disable or do not configure this setting, monitoring for incoming and outgoing files will be enabled.
- bi-directional (full on-access)
- scan only incoming (disable on-open)
- scan only outgoing (disable on-close)
- Configure local setting override for the time of day to run a scheduled full scan to complete remediation
- This policy setting configures a local override for the configuration of the time to run a scheduled full scan to complete remediation. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Specify the day of the week to run a scheduled full scan to complete remediation
- This policy setting allows you to specify the day of the week on which to perform a scheduled full scan in order to complete remediation. The scan can also be configured to run every day or to never run at all.
-
- This setting can be configured with the following ordinal number values:
- (0x0) Every Day
- (0x1) Sunday
- (0x2) Monday
- (0x3) Tuesday
- (0x4) Wednesday
- (0x5) Thursday
- (0x6) Friday
- (0x7) Saturday
- (0x8) Never (default)
-
- If you enable this setting, a scheduled full scan to complete remediation will run at the frequency specified.
-
- If you disable or do not configure this setting, a scheduled full scan to complete remediation will run at a default frequency.
- Never
- Every Day
- Sunday
- Monday
- Tuesday
- Wednesday
- Thursday
- Friday
- Saturday
- Specify the time of day to run a scheduled full scan to complete remediation
- This policy setting allows you to specify the time of day at which to perform a scheduled full scan in order to complete remediation. The time value is represented as the number of minutes past midnight (00:00). For example, 120 (0x78) is equivalent to 02:00 AM. The schedule is based on local time on the computer where the scan is executing.
-
- If you enable this setting, a scheduled full scan to complete remediation will run at the time of day specified.
-
- If you disable or do not configure this setting, a scheduled full scan to complete remediation will run at a default time.
- Configure time out for detections requiring additional action
- This policy setting configures the time in minutes before a detection in the "additional action" state moves to the "cleared" state.
- Configure time out for detections in critically failed state
- This policy setting configures the time in minutes before a detection in the “critically failed” state to moves to either the “additional action” state or the “cleared” state.
- Configure Watson events
- This policy setting allows you to configure whether or not Watson events are sent.
-
- If you enable or do not configure this setting, Watson events will be sent.
-
- If you disable this setting, Watson events will not be sent.
- Configure time out for detections in non-critical failed state
- This policy setting configures the time in minutes before a detection in the "non-critically failed" state moves to the "cleared" state.
- Configure time out for detections in recently remediated state
- This policy setting configures the time in minutes before a detection in the "completed" state moves to the "cleared" state.
- Configure Windows software trace preprocessor components
- This policy configures Windows software trace preprocessor (WPP Software Tracing) components.
- Configure WPP tracing level
- This policy allows you to configure tracing levels for Windows software trace preprocessor (WPP Software Tracing).
- Tracing levels are defined as:
- 1 - Error
- 2 - Warning
- 3 - Info
- 4 - Debug
- Turn off enhanced notifications
-
- Use this policy setting to specify if you want Microsoft Defender Antivirus enhanced notifications to display on clients.
-
- If you disable or do not configure this setting, Microsoft Defender Antivirus enhanced notifications will display on clients.
-
- If you enable this setting, Microsoft Defender Antivirus enhanced notifications will not display on clients.
-
- Configure time interval for service health reports
- This policy setting configures the time interval (in minutes) for the service health reports to be sent from endpoints.
-
- If you disable or do not configure this setting, the default value will be applied. The default value is set at 60 minutes (1 hour).
-
- If you configure this setting to 0, no service health reports will be sent.
-
- The maximum value allowed to be set is 14400 minutes (10 days).
- Allow users to pause scan
- This policy setting allows you to manage whether or not end users can pause a scan in progress.
-
- If you enable or do not configure this setting, a new context menu will be added to the task tray icon to allow the user to pause a scan.
-
- If you disable this setting, users will not be able to pause scans.
- Specify the maximum depth to scan archive files
- This policy setting allows you to configure the maximum directory depth level into which archive files such as .ZIP or .CAB are unpacked during scanning. The default directory depth level is 0.
-
- If you enable this setting, archive files will be scanned to the directory depth level specified.
-
- If you disable or do not configure this setting, archive files will be scanned to the default directory depth level.
- Specify the maximum size of archive files to be scanned
- This policy setting allows you to configure the maximum size of archive files such as .ZIP or .CAB that will be scanned. The value represents file size in kilobytes (KB). The default value is 0 and represents no limit to archive size for scanning.
-
- If you enable this setting, archive files less than or equal to the size specified will be scanned.
-
- If you disable or do not configure this setting, archive files will be scanned according to the default value.
- Specify the maximum percentage of CPU utilization during a scan
- This policy setting allows you to configure the maximum percentage CPU utilization permitted during a scan. Valid values for this setting are a percentage represented by the integers 5 to 100. A value of 0 indicates that there should be no throttling of CPU utilization. The default value is 50.
-
- If you enable this setting, CPU utilization will not exceed the percentage specified.
-
- If you disable or do not configure this setting, CPU utilization will not exceed the default value.
- Check for the latest virus and spyware security intelligence before running a scheduled scan
- This policy setting allows you to manage whether a check for new virus and spyware security intelligence will occur before running a scan.
-
- This setting applies to scheduled scans, but it has no effect on scans initiated manually from the user interface or to the ones started from the command line using "mpcmdrun -Scan".
-
- If you enable this setting, a check for new security intelligence will occur before running a scan.
-
- If you disable this setting or do not configure this setting, the scan will start using the existing security intelligence.
- Scan archive files
- This policy setting allows you to configure scans for malicious software and unwanted software in archive files such as .ZIP or .CAB files.
-
- If you enable or do not configure this setting, archive files will be scanned.
-
- If you disable this setting, archive files will not be scanned. However, archives are always scanned during directed scans.
- Turn on catch-up full scan
- This policy setting allows you to configure catch-up scans for scheduled full scans. A catch-up scan is a scan that is initiated because a regularly scheduled scan was missed. Usually these scheduled scans are missed because the computer was turned off at the scheduled time.
-
- If you enable this setting, catch-up scans for scheduled full scans will be turned on. If a computer is offline for two consecutive scheduled scans, a catch-up scan is started the next time someone logs on to the computer. If there is no scheduled scan configured, there will be no catch-up scan run.
-
- If you disable or do not configure this setting, catch-up scans for scheduled full scans will be turned off.
- CPU throttling type
- This policy setting determines whether the maximum percentage CPU utilization permitted during a scan applies only to scheduled scans, or to both scheduled and custom scans (but not real-time protection). The maximum CPU utilization limit is also referred to as CPU throttling, or a CPU usage limit.
-
- The default value for this policy setting is True, which means CPU throttling is applied only to scheduled scans.
-
- If you either enable or do not configure this setting, CPU throttling will apply only to scheduled scans.
-
- If you disable this setting, CPU throttling will apply to scheduled and custom scans.
- Turn on catch-up quick scan
- This policy setting allows you to configure catch-up scans for scheduled quick scans. A catch-up scan is a scan that is initiated because a regularly scheduled scan was missed. Usually these scheduled scans are missed because the computer was turned off at the scheduled time.
-
- If you enable this setting, catch-up scans for scheduled quick scans will be turned on. If a computer is offline for two consecutive scheduled scans, a catch-up scan is started the next time someone logs on to the computer. If there is no scheduled scan configured, there will be no catch-up scan run.
-
- If you disable or do not configure this setting, catch-up scans for scheduled quick scans will be turned off.
- Turn on e-mail scanning
- This policy setting allows you to configure e-mail scanning. When e-mail scanning is enabled, the engine will parse the mailbox and mail files, according to their specific format, in order to analyze the mail bodies and attachments. Several e-mail formats are currently supported, for example: pst (Outlook), dbx, mbx, mime (Outlook Express), binhex (Mac). Email scanning is not supported on modern email clients.
-
- If you enable this setting, e-mail scanning will be enabled.
-
- If you disable or do not configure this setting, e-mail scanning will be disabled.
- Turn on heuristics
- This policy setting allows you to configure heuristics. Suspicious detections will be suppressed right before reporting to the engine client. Turning off heuristics will reduce the capability to flag new threats. It is recommended that you do not turn off heuristics.
-
- If you enable or do not configure this setting, heuristics will be enabled.
-
- If you disable this setting, heuristics will be disabled.
- Scan packed executables
- This policy setting allows you to configure scanning for packed executables. It is recommended that this type of scanning remain enabled.
-
- If you enable or do not configure this setting, packed executables will be scanned.
-
- If you disable this setting, packed executables will not be scanned.
- Scan removable drives
- This policy setting allows you to manage whether or not to scan for malicious software and unwanted software in the contents of removable drives, such as USB flash drives, when running a full scan.
-
- If you enable this setting, removable drives will be scanned during any type of scan.
-
- If you disable or do not configure this setting, removable drives will not be scanned during a full scan. Removable drives may still be scanned during quick scan and custom scan.
- Turn on reparse point scanning
- This policy setting allows you to configure reparse point scanning. If you allow reparse points to be scanned, there is a possible risk of recursion. However, the engine supports following reparse points to a maximum depth so at worst scanning could be slowed. Reparse point scanning is disabled by default and this is the recommended state for this functionality.
-
- If you enable this setting, reparse point scanning will be enabled.
-
- If you disable or do not configure this setting, reparse point scanning will be disabled.
- Create a system restore point
- This policy setting allows you to create a system restore point on the computer on a daily basis prior to cleaning.
-
- If you enable this setting, a system restore point will be created.
-
- If you disable or do not configure this setting, a system restore point will not be created.
- Run full scan on mapped network drives
- This policy setting allows you to configure scanning mapped network drives.
-
- If you enable this setting, mapped network drives will be scanned.
-
- If you disable or do not configure this setting, mapped network drives will not be scanned.
- Scan network files
- This policy setting allows you to configure scanning for network files. It is recommended that you do not enable this setting.
-
- If you enable this setting, network files will be scanned.
-
- If you disable or do not configure this setting, network files will not be scanned.
- Configure local setting override for maximum percentage of CPU utilization
- This policy setting configures a local override for the configuration of maximum percentage of CPU utilization during scan. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure local setting override for the scan type to use for a scheduled scan
- This policy setting configures a local override for the configuration of the scan type to use during a scheduled scan. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure local setting override for schedule scan day
- This policy setting configures a local override for the configuration of scheduled scan day. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure local setting override for scheduled quick scan time
- This policy setting configures a local override for the configuration of scheduled quick scan time. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Configure local setting override for scheduled scan time
- This policy setting configures a local override for the configuration of scheduled scan time. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Turn on removal of items from scan history folder
- This policy setting defines the number of days items should be kept in the scan history folder before being permanently removed. The value represents the number of days to keep items in the folder. If set to zero, items will be kept forever and will not be automatically removed. By default, the value is set to 30 days.
-
- If you enable this setting, items will be removed from the scan history folder after the number of days specified.
-
- If you disable or do not configure this setting, items will be kept in the scan history folder for the default number of days.
- Specify the interval to run quick scans per day
- This policy setting allows you to specify an interval at which to perform a quick scan. The time value is represented as the number of hours between quick scans. Valid values range from 1 (every hour) to 24 (once per day). If set to zero, interval quick scans will not occur. By default, this setting is set to 0.
-
- If you enable this setting, a quick scan will run at the interval specified.
-
- If you disable or do not configure this setting, quick scan controlled by this config will not be run.
- Start the scheduled scan only when computer is on but not in use
- This policy setting allows you to configure scheduled scans to start only when your computer is on but not in use.
-
- If you enable or do not configure this setting, scheduled scans will only run when the computer is on but not in use.
-
- If you disable this setting, scheduled scans will run at the scheduled time.
- Specify the scan type to use for a scheduled scan
- This policy setting allows you to specify the scan type to use during a scheduled scan. Scan type options are:
- 1 = Quick Scan (default)
- 2 = Full Scan
-
- If you enable this setting, the scan type will be set to the specified value.
-
- If you disable or do not configure this setting, the default scan type will used.
- Quick scan
- Full system scan
- Specify the day of the week to run a scheduled scan
- This policy setting allows you to specify the day of the week on which to perform a scheduled scan. The scan can also be configured to run every day or to never run at all.
-
- This setting can be configured with the following ordinal number values:
- (0x0) Every Day
- (0x1) Sunday
- (0x2) Monday
- (0x3) Tuesday
- (0x4) Wednesday
- (0x5) Thursday
- (0x6) Friday
- (0x7) Saturday
- (0x8) Never (default)
-
- If you enable this setting, a scheduled scan will run at the frequency specified.
-
- If you disable or do not configure this setting, a scheduled scan will run at a default frequency.
- Never
- Every Day
- Sunday
- Monday
- Tuesday
- Wednesday
- Thursday
- Friday
- Saturday
- Specify the time for a daily quick scan
- This policy setting allows you to specify the time of day at which to perform a daily quick scan. The time value is represented as the number of minutes past midnight (00:00). For example, 120 (0x78) is equivalent to 02:00 AM. By default, this setting is set to disabled. The schedule is based on local time on the computer where the scan is executing.
-
- If you enable this setting, a daily quick scan will run at the time of day specified.
-
- If you disable or do not configure this setting, daily quick scan controlled by this config will not be run.
- Specify the time of day to run a scheduled scan
- This policy setting allows you to specify the time of day at which to perform a scheduled scan. The time value is represented as the number of minutes past midnight (00:00). For example, 120 (0x78) is equivalent to 02:00 AM. By default, this setting is set to a time value of 2:00 AM. The schedule is based on local time on the computer where the scan is executing.
-
- If you enable this setting, a scheduled scan will run at the time of day specified.
-
- If you disable or do not configure this setting, a scheduled scan will run at a default time.
- Define the number of days after which a catch-up scan is forced
-
- This policy setting allows you to define the number of consecutive scheduled scans that can be missed after which a catch-up scan will be forced. By default, the value of this setting is 2 consecutive scheduled scans.
-
- If you enable this setting, a catch-up scan will occur after the specified number consecutive missed scheduled scans.
-
- If you disable or do not configure this setting, a catch-up scan will occur after the 2 consecutive missed scheduled scans.
- Configure low CPU priority for scheduled scans
-
- This policy setting allows you to enable or disable low CPU priority for scheduled scans.
-
- If you enable this setting, low CPU priority will be used during scheduled scans.
-
- If you disable or do not configure this setting, not changes will be made to CPU priority for scheduled scans.
-
- Define the number of days before spyware security intelligence is considered out of date
- This policy setting allows you to define the number of days that must pass before spyware security intelligence is considered out of date. If security intelligence is determined to be out of date, this state may trigger several additional actions, including falling back to an alternative update source or displaying a warning icon in the user interface. By default, this value is set to 7 days.
-
- If you enable this setting, spyware security intelligence will be considered out of date after the number of days specified have passed without an update.
-
- If you disable or do not configure this setting, spyware security intelligence will be considered out of date after the default number of days have passed without an update.
- Define the number of days before virus security intelligence is considered out of date
- This policy setting allows you to define the number of days that must pass before virus security intelligence is considered out of date. If security intelligence is determined to be out of date, this state may trigger several additional actions, including falling back to an alternative update source or displaying a warning icon in the user interface. By default, this value is set to 7 days.
-
- If you enable this setting, virus security intelligence will be considered out of date after the number of days specified have passed without an update.
-
- If you disable or do not configure this setting, virus security intelligence will be considered out of date after the default number of days have passed without an update.
- Define file shares for downloading security intelligence updates
- This policy setting allows you to configure UNC file share sources for downloading security intelligence updates. Sources will be contacted in the order specified. The value of this setting should be entered as a pipe-separated string enumerating the security intelligence update sources. For example: "{\\unc1 | \\unc2 }". The list is empty by default.
-
- If you enable this setting, the specified sources will be contacted for security intelligence updates. Once security intelligence updates have been successfully downloaded from one specified source, the remaining sources in the list will not be contacted.
-
- If you disable or do not configure this setting, the list will remain empty by default and no sources will be contacted.
- Define security intelligence location for VDI clients.
- This policy setting allows you to define the security intelligence location for VDI-configured computers.
-
- If you disable or do not configure this setting, security intelligence will be referred from the default local source.
- Turn on scan after security intelligence update
- This policy setting allows you to configure the automatic scan which starts after a security intelligence update has occurred.
-
- If you enable or do not configure this setting, a scan will start following a security intelligence update.
-
- If you disable this setting, a scan will not start following a security intelligence update.
- Allow security intelligence updates when running on battery power
- This policy setting allows you to configure security intelligence updates when the computer is running on battery power.
-
- If you enable or do not configure this setting, security intelligence updates will occur as usual regardless of power state.
-
- If you disable this setting, security intelligence updates will be turned off while the computer is running on battery power.
- Initiate security intelligence update on startup
- This policy setting allows you to configure security intelligence updates on startup when there is no antimalware engine present.
-
- If you enable or do not configure this setting, security intelligence updates will be initiated on startup when there is no antimalware engine present.
-
- If you disable this setting, security intelligence updates will not be initiated on startup when there is no antimalware engine present.
- Define the order of sources for downloading security intelligence updates
- This policy setting allows you to define the order in which different security intelligence update sources should be contacted. The value of this setting should be entered as a pipe-separated string enumerating the security intelligence update sources in order. Possible values are: “InternalDefinitionUpdateServer”, “MicrosoftUpdateServer”, “MMPC”, and “FileShares”
-
- For example: { InternalDefinitionUpdateServer | MicrosoftUpdateServer | MMPC }
-
- If you enable this setting, security intelligence update sources will be contacted in the order specified. Once security intelligence updates have been successfully downloaded from one specified source, the remaining sources in the list will not be contacted.
-
- If you disable or do not configure this setting, security intelligence update sources will be contacted in a default order.
- Allow security intelligence updates from Microsoft Update
- This policy setting allows you to enable download of security intelligence updates from Microsoft Update even if the Automatic Updates default server is configured to another download source such as Windows Update.
-
- If you enable this setting, security intelligence updates will be downloaded from Microsoft Update.
-
- If you disable or do not configure this setting, security intelligence updates will be downloaded from the configured download source.
- Allow real-time security intelligence updates based on reports to Microsoft MAPS
- This policy setting allows you to enable real-time security intelligence updates in response to reports sent to Microsoft MAPS. If the service reports a file as an unknown and Microsoft MAPS finds that the latest security intelligence update has security intelligence for a threat involving that file, the service will receive all of the latest security intelligence for that threat immediately. You must have configured your computer to join Microsoft MAPS for this functionality to work.
-
- If you enable or do not configure this setting, real-time security intelligence updates will be enabled.
-
- If you disable this setting, real-time security intelligence updates will disabled.
- Specify the day of the week to check for security intelligence updates
- This policy setting allows you to specify the day of the week on which to check for security intelligence updates. The check can also be configured to run every day or to never run at all.
-
- This setting can be configured with the following ordinal number values:
- (0x0) Every Day (default)
- (0x1) Sunday
- (0x2) Monday
- (0x3) Tuesday
- (0x4) Wednesday
- (0x5) Thursday
- (0x6) Friday
- (0x7) Saturday
- (0x8) Never
-
- If you enable this setting, the check for security intelligence updates will occur at the frequency specified.
-
- If you disable or do not configure this setting, the check for security intelligence updates will occur at a default frequency.
- Never
- Every Day
- Sunday
- Monday
- Tuesday
- Wednesday
- Thursday
- Friday
- Saturday
- Specify the time to check for security intelligence updates
- This policy setting allows you to specify the time of day at which to check for security intelligence updates. The time value is represented as the number of minutes past midnight (00:00). For example, 120 (0x78) is equivalent to 02:00 AM. By default this setting is configured to check for security intelligence updates 15 minutes before the scheduled scan time. The schedule is based on local time on the computer where the check is occurring.
-
- If you enable this setting, the check for security intelligence updates will occur at the time of day specified.
-
- If you disable or do not configure this setting, the check for security intelligence updates will occur at the default time.
- Allow notifications to disable security intelligence based reports to Microsoft MAPS
- This policy setting allows you to configure the antimalware service to receive notifications to disable individual security intelligence in response to reports it sends to Microsoft MAPS. Microsoft MAPS uses these notifications to disable security intelligence that are causing false positive reports. You must have configured your computer to join Microsoft MAPS for this functionality to work.
-
- If you enable this setting or do not configure, the antimalware service will receive notifications to disable security intelligence.
-
- If you disable this setting, the antimalware service will not receive notifications to disable security intelligence.
- Define the number of days after which a catch-up security intelligence update is required
- This policy setting allows you to define the number of days after which a catch-up security intelligence update will be required. By default, the value of this setting is 1 day.
-
- If you enable this setting, a catch-up security intelligence update will occur after the specified number of days.
-
- If you disable or do not configure this setting, a catch-up security intelligence update will be required after the default number of days.
- Specify the interval for expiry notification
-
- This policy setting allows you to specify an interval(in days) for expiry notification.
- If a signature expiry or platform expiry is impending, this value tells how soon AM UI will notify customers.
-
- Value should be greater than zero for the policy to be active.
-
- Specify the interval to check for security intelligence updates
- This policy setting allows you to specify an interval at which to check for security intelligence updates. The time value is represented as the number of hours between update checks. Valid values range from 1 (every hour) to 24 (once per day).
-
- If you enable this setting, checks for security intelligence updates will occur at the interval specified.
-
- If you disable or do not configure this setting, checks for security intelligence updates will occur at the default interval.
- Check for the latest virus and spyware security intelligence on startup
- This policy setting allows you to manage whether a check for new virus and spyware security intelligence will occur immediately after service startup.
-
- If you enable this setting, a check for new security intelligence will occur after service startup.
-
- If you disable this setting or do not configure this setting, a check for new security intelligence will not occur after service startup.
- Configure the 'Block at First Sight' feature
- This feature ensures the device checks in real time with the Microsoft Active Protection Service (MAPS) before allowing certain content to be run or accessed. If this feature is disabled, the check will not occur, which will lower the protection state of the device.
- Enabled – The Block at First Sight setting is turned on.
- Disabled – The Block at First Sight setting is turned off.
-
- This feature requires these Group Policy settings to be set as follows:
- MAPS -> The “Join Microsoft MAPS” must be enabled or the “Block at First Sight” feature will not function.
- MAPS -> The “Send file samples when further analysis is required” should be set to 1 (Send safe samples) or 3 (Send all samples). Setting to 0 (Always Prompt) will lower the protection state of the device. Setting to 2 (Never send) means the “Block at First Sight” feature will not function.
- Real-time Protection -> The “Scan all downloaded files and attachments” policy must be enabled or the “Block at First Sight” feature will not function.
- Real-time Protection -> Do not enable the “Turn off real-time protection” policy or the “Block at First Sight” feature will not function.
- Configure local setting override for reporting to Microsoft MAPS
- This policy setting configures a local override for the configuration to join Microsoft MAPS. This setting can only be set by Group Policy.
-
- If you enable this setting, the local preference setting will take priority over Group Policy.
-
- If you disable or do not configure this setting, Group Policy will take priority over the local preference setting.
- Send file samples when further analysis is required
-
- This policy setting configures behaviour of samples submission when opt-in for MAPS telemetry is set.
-
- Possible options are:
- (0x0) Always prompt
- (0x1) Send safe samples automatically
- (0x2) Never send
- (0x3) Send all samples automatically
-
-
- Always prompt
- Send safe samples
- Never send
- Send all samples
-
- Join Microsoft MAPS
- This policy setting allows you to join Microsoft MAPS. Microsoft MAPS is the online community that helps you choose how to respond to potential threats. The community also helps stop the spread of new malicious software infections.
-
- You can choose to send basic or additional information about detected software. Additional information helps Microsoft create new security intelligence and help it to protect your computer. This information can include things like location of detected items on your computer if harmful software was removed. The information will be automatically collected and sent. In some instances, personal information might unintentionally be sent to Microsoft. However, Microsoft will not use this information to identify you or contact you.
-
- Possible options are:
- (0x0) Disabled (default)
- (0x1) Basic membership
- (0x2) Advanced membership
-
- Basic membership will send basic information to Microsoft about software that has been detected, including where the software came from, the actions that you apply or that are applied automatically, and whether the actions were successful.
-
- Advanced membership, in addition to basic information, will send more information to Microsoft about malicious software, spyware, and potentially unwanted software, including the location of the software, file names, how the software operates, and how it has impacted your computer.
-
- If you enable this setting, you will join Microsoft MAPS with the membership specified.
-
- If you disable or do not configure this setting, you will not join Microsoft MAPS.
-
- In Windows 10, Basic membership is no longer available, so setting the value to 1 or 2 enrolls the device into Advanced membership.
- Disabled
- Basic MAPS
- Advanced MAPS
- Specify threats upon which default action should not be taken when detected
- This policy setting customize which remediation action will be taken for each listed Threat ID when it is detected during a scan. Threats should be added under the Options for this setting. Each entry must be listed as a name value pair. The name defines a valid Threat ID, while the value contains the action ID for the remediation action that should be taken.
-
- Valid remediation action values are:
- 2 = Quarantine
- 3 = Remove
- 6 = Ignore
- Specify threat alert levels at which default action should not be taken when detected
- This policy setting allows you to customize which automatic remediation action will be taken for each threat alert level.Threat alert levels should be added under the Options for this setting. Each entry must be listed as a name value pair. The name defines a threat alert level. The value contains the action ID for the remediation action that should be taken.
-
- Valid threat alert levels are:
- 1 = Low
- 2 = Medium
- 4 = High
- 5 = Severe
-
- Valid remediation action values are:
- 2 = Quarantine
- 3 = Remove
- 6 = Ignore
- Enable headless UI mode
-
- This policy setting allows you to configure whether or not to display AM UI to the users.
- If you enable this setting AM UI won't be available to users.
-
- Suppresses reboot notifications
-
- This policy setting allows user to supress reboot notifications in UI only mode (for cases where UI can't be in lockdown mode).
-
- If you enable this setting AM UI won't show reboot notifications.
-
- Suppress all notifications
- Use this policy setting to specify if you want Microsoft Defender Antivirus notifications to display on clients.
- If you disable or do not configure this setting, Microsoft Defender Antivirus notifications will display on clients.
-
- If you enable this setting, Microsoft Defender Antivirus notifications will not display on clients.
-
- Display additional text to clients when they need to perform an action
- This policy setting allows you to configure whether or not to display additional text to clients when they need to perform an action. The text displayed is a custom administrator-defined string. For example, the phone number to call the company help desk. The client interface will only display a maximum of 1024 characters. Longer strings will be truncated before display.
-
- If you enable this setting, the additional text specified will be displayed.
-
- If you disable or do not configure this setting, there will be no additional text displayed.
- Select cloud protection level
-
- This policy setting determines how aggressive Microsoft Defender Antivirus will be in blocking and scanning suspicious files.
-
- If this setting is on, Microsoft Defender Antivirus will be more aggressive when identifying suspicious files to block and scan; otherwise, it will be less aggressive and therefore block and scan with less frequency.
-
- For more information about specific values that are supported, see the Microsoft Defender Antivirus documentation site.
-
- Note: This feature requires the "Join Microsoft MAPS" setting enabled in order to function.
-
- Possible options are:
- (0x0) Default Microsoft Defender Antivirus blocking level
- (0x1) Moderate Microsoft Defender Antivirus blocking level, delivers verdict only for high confidence detections
- (0x2) High blocking level - aggressively block unknowns while optimizing client performance (greater chance of false positives)
- (0x4) High+ blocking level – aggressively block unknowns and apply additional protection measures (may impact client performance)
- (0x6) Zero tolerance blocking level – block all unknown executables
-
- Default blocking level
- Moderate blocking level
- High blocking level
- High+ blocking level
- Zero tolerance blocking level
- Configure extended cloud check
-
- This feature allows Microsoft Defender Antivirus to block a suspicious file for up to 60 seconds, and scan it in the cloud to make sure it's safe.
-
- The typical cloud check timeout is 10 seconds. To enable the extended cloud check feature, specify the extended time in seconds, up to an additional 50 seconds.
-
- For example, if the desired timeout is 60 seconds, specify 50 seconds in this setting, which will enable the extended cloud check feature, and will raise the total time to 60 seconds.
-
- Note: This feature depends on three other MAPS settings - "Configure the 'Block at First Sight' feature; "Join Microsoft MAPS"; "Send file samples when further analysis is required" all need to be enabled.
-
- Enable file hash computation feature
-
- Enable or disable file hash computation feature.
-
- Enabled:
- When this feature is enabled Microsoft Defender will compute hash value for files it scans.
-
- Disabled:
- File hash value is not computed
-
- Not configured:
- Same as Disabled.
-
- Prevent users and apps from accessing dangerous websites
-
- Enable or disable Microsoft Defender Exploit Guard network protection to prevent employees from using any application to access dangerous domains that may host phishing scams, exploit-hosting sites, and other malicious content on the Internet.
-
- Enabled:
- Specify the mode in the Options section:
- -Block: Users and applications will not be able to access dangerous domains
- -Audit Mode: Users and applications can connect to dangerous domains, however if this feature would have blocked access if it were set to Block, then a record of the event will be in the event logs.
-
- Disabled:
- Users and applications will not be blocked from connecting to dangerous domains.
-
- Not configured:
- Same as Disabled.
-
- Exclude files and paths from Attack Surface Reduction Rules
-
- Exclude files and paths from Attack Surface Reduction (ASR) rules.
-
- Enabled:
- Specify the folders or files and resources that should be excluded from ASR rules in the Options section.
- Enter each rule on a new line as a name-value pair:
- - Name column: Enter a folder path or a fully qualified resource name. For example, ""C:\Windows"" will exclude all files in that directory. ""C:\Windows\App.exe"" will exclude only that specific file in that specific folder
- - Value column: Enter ""0"" for each item
-
- Disabled:
- No exclusions will be applied to the ASR rules.
-
- Not configured:
- Same as Disabled.
-
- You can configure ASR rules in the Configure Attack Surface Reduction rules GP setting.
-
- Configure Attack Surface Reduction rules
-
- Set the state for each Attack Surface Reduction (ASR) rule.
-
- After enabling this setting, you can set each rule to the following in the Options section:
- - Block: the rule will be applied
- - Audit Mode: if the rule would normally cause an event, then it will be recorded (although the rule will not actually be applied)
- - Off: the rule will not be applied
- - Not Configured: the rule is enabled with default values
- - Warn: the rule will be applied and the end-user will have the option to bypass the block
-
- Unless the ASR rule is disabled, a subsample of audit events are collected for ASR rules will the value of not configured.
-
- Enabled:
- Specify the state for each ASR rule under the Options section for this setting.
- Enter each rule on a new line as a name-value pair:
- - Name column: Enter a valid ASR rule ID
- - Value column: Enter the status ID that relates to state you want to specify for the associated rule
-
- The following status IDs are permitted under the value column:
- - 1 (Block)
- - 0 (Off)
- - 2 (Audit)
- - 5 (Not Configured)
- - 6 (Warn)
-
-
- Example:
- xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 0
- xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 1
- xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx 2
-
- Disabled:
- No ASR rules will be configured.
-
- Not configured:
- Same as Disabled.
-
- You can exclude folders or files in the ""Exclude files and paths from Attack Surface Reduction Rules"" GP setting.
-
- Configure Controlled folder access
-
- Enable or disable controlled folder access for untrusted applications. You can choose to block, audit, or allow attempts by untrusted apps to:
- - Modify or delete files in protected folders, such as the Documents folder
- - Write to disk sectors
-
- You can also choose to only block or audit writes to disk sectors while still allowing the modification or deletion of files in protected folders.
-
- Microsoft Defender Antivirus automatically determines which applications can be trusted. You can add additional trusted applications in the Configure allowed applications GP setting.
- Default system folders are automatically protected, but you can add folders in the Configure protected folders GP setting.
-
- Block:
- The following will be blocked:
- - Attempts by untrusted apps to modify or delete files in protected folders
- - Attempts by untrusted apps to write to disk sectors
- The Windows event log will record these blocks under Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational > ID 1123.
-
-
- Disabled:
- The following will not be blocked and will be allowed to run:
- - Attempts by untrusted apps to modify or delete files in protected folders
- - Attempts by untrusted apps to write to disk sectors
- These attempts will not be recorded in the Windows event log.
-
-
- Audit Mode:
- The following will not be blocked and will be allowed to run:
- - Attempts by untrusted apps to modify or delete files in protected folders
- - Attempts by untrusted apps to write to disk sectors
- The Windows event log will record these attempts under Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational > ID 1124.
-
-
- Block disk modification only:
- The following will be blocked:
- - Attempts by untrusted apps to write to disk sectors
- The Windows event log will record these attempts under Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational > ID 1123.
-
- The following will not be blocked and will be allowed to run:
- - Attempts by untrusted apps to modify or delete files in protected folders
- These attempts will not be recorded in the Windows event log.
-
-
- Audit disk modification only:
- The following will not be blocked and will be allowed to run:
- - Attempts by untrusted apps to write to disk sectors
- - Attempts by untrusted apps to modify or delete files in protected folders
- Only attempts to write to protected disk sectors will be recorded in the Windows event log (under Applications and Services Logs > Microsoft > Windows > Windows Defender > Operational > ID 1124).
- Attempts to modify or delete files in protected folders will not be recorded.
-
- Not configured:
- Same as Disabled.
-
- Disable (Default)
- Block
- Audit Mode
- Block disk modification only
- Audit disk modification only
- Configure allowed applications
-
- Add additional applications that should be considered "trusted" by controlled folder access.
-
- These applications are allowed to modify or delete files in controlled folder access folders.
-
- Microsoft Defender Antivirus automatically determines which applications should be trusted. You can configure this setting to add additional applications.
-
- Enabled:
- Specify additional allowed applications in the Options section..
-
- Disabled:
- No additional applications will be added to the trusted list.
-
- Not configured:
- Same as Disabled.
-
- You can enable controlled folder access in the Configure controlled folder access GP setting.
-
- Default system folders are automatically guarded, but you can add folders in the configure protected folders GP setting.
-
- Configure protected folders
-
- Specify additional folders that should be guarded by the Controlled folder access feature.
-
- Files in these folders cannot be modified or deleted by untrusted applications.
-
- Default system folders are automatically protected. You can configure this setting to add additional folders.
- The list of default system folders that are protected is shown in Windows Security.
-
- Enabled:
- Specify additional folders that should be protected in the Options section.
-
- Disabled:
- No additional folders will be protected.
-
- Not configured:
- Same as Disabled.
-
- You can enable controlled folder access in the Configure controlled folder access GP setting.
-
- Microsoft Defender Antivirus automatically determines which applications can be trusted. You can add additional trusted applications in the Configure allowed applications GP setting.
-
- Define device control policy groups
-
- Please follow the device control policy groups xml schema to fill out the policy groups data.
- Alternatively you could use a file path containing the XML groups data.
-
- Define device control policy rules
-
- Please follow the device control policy rules xml schema to fill out the policy rules data.
- Alternatively you could use a file path containing the XML rules data.
-
- Select the channel for Microsoft Defender monthly platform updates
- Enable this policy to specify when devices receive Microsoft Defender platform updates during the monthly gradual rollout.
-
- Beta Channel: Devices set to this channel will be the first to receive new updates. Select Beta Channel to participate in identifying and reporting issues to Microsoft. Devices in the Windows Insider Program are subscribed to this channel by default. For use in (manual) test environments only and a limited number of devices.
- Current Channel (Preview): Devices set to this channel will be offered updates earliest during the monthly gradual release cycle. Suggested for pre-production/validation environments.
- Current Channel (Staged): Devices will be offered updates after the monthly gradual release cycle. Suggested to apply to a small, representative part of your production population (~10%).
- Current Channel (Broad): Devices will be offered updates only after the gradual release cycle completes. Suggested to apply to a broad set of devices in your production population (~10-100%).
- Critical - Time delay: Devices will be offered updates with a 48-hour delay. Suggested for critical environments only.
-
- If you disable or do not configure this policy, the device will stay up to date automatically during the gradual release cycle. Suitable for most devices.
-
- Select the channel for Microsoft Defender monthly engine updates
- Enable this policy to specify when devices receive Microsoft Defender engine updates during the monthly gradual rollout.
-
- Beta Channel: Devices set to this channel will be the first to receive new updates. Select Beta Channel to participate in identifying and reporting issues to Microsoft. Devices in the Windows Insider Program are subscribed to this channel by default. For use in (manual) test environments only and a limited number of devices.
- Current Channel (Preview): Devices set to this channel will be offered updates earliest during the monthly gradual release cycle. Suggested for pre-production/validation environments.
- Current Channel (Staged): Devices will be offered updates after the monthly gradual release cycle. Suggested to apply to a small, representative part of your production population (~10%).
- Current Channel (Broad): Devices will be offered updates only after the gradual release cycle completes. Suggested to apply to a broad set of devices in your production population (~10-100%).
- Critical - Time delay: Devices will be offered updates with a 48-hour delay. Suggested for critical environments only.
-
- If you disable or do not configure this policy, the device will stay up to date automatically during the gradual release cycle. Suitable for most devices.
-
- Select the channel for Microsoft Defender daily security intelligence updates
- Enable this policy to specify when devices receive Microsoft Defender security intelligence updates during the daily gradual rollout.
-
- Current Channel (Staged): Devices will be offered updates after the release cycle. Suggested to apply to a small, representative part of production population (~10%).
- Current Channel (Broad): Devices will be offered updates only after the gradual release cycle completes. Suggested to apply to a broad set of devices in your production population (~10-100%).
- Critical - Time delay: Devices will be offered updates with a 48-hour delay. Suggested for critical environments only.
-
- If you disable or do not configure this policy, the device will stay up to date automatically during the daily release cycle. Suitable for most devices.
-
- Beta Channel
- Current Channel (Preview)
- Current Channel (Staged)
- Current Channel (Broad)
- Critical - Time delay
- Disable gradual rollout of Microsoft Defender updates.
- Enable this policy to disable gradual rollout of Defender updates.
-
- Current Channel (Broad): Devices set to this channel will be offered updates last during the gradual release cycle. Best for datacenter machines that only receive limited updates.
-
- Note: This setting applies to both monthly as well as daily Defender updates and will override any previously configured channel selections for platform and engine updates.
-
- If you disable or do not configure this policy, the device will remain in Current Channel (Default) unless specified otherwise in specific channels for platform and engine updates. Stay up to date automatically during the gradual release cycle. Suitable for most devices.
- Select Device Control Default Enforcement Policy
-
- Default Allow: Choosing this default enforcement, will Allow any operations to occur on the attached devices if no policy rules are found to match.
- Default Deny: Choosing this default enforcement, will Deny any operations to occur on the attached devices if no policy rules are found to match.
-
- Default Enforcement will establish what decision should be made during the Device Control access checks when none of the policy rules match.
-
- Default Allow
- Default Deny
- Define Device Control evidence data remote location
-
- Define evidence file remote location, where Device Control service will move evidence data captured.
-
- Device Control
-
- Enable or Disable Defender Device Control on this machine.
- Note: You must be enrolled as E3 or E5 in order for Device Control to be enabled.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Extension Exclusions
-
-
- Path Exclusions
-
-
- Process Exclusions
-
-
- IP Address Exclusions
-
-
- Specify additional definition sets for network traffic inspection
-
-
- Configure removal of items from Quarantine folder
-
-
- Define the maximum size of downloaded files and attachments to be scanned
-
-
- Configure monitoring for incoming and outgoing file and program activity
-
-
- Specify the day of the week to run a scheduled full scan to complete remediation
-
-
- Specify the time of day to run a scheduled full scan to complete remediation
-
-
- Define the number of scheduled scans that can be missed after which a catch-up scan is forced
-
-
- Configure time out for detections requiring additional action
-
-
- Configure time out for detections in critically failed state
-
-
- Configure time out for detections in non-critical failed state
-
-
- Configure time out for detections in recently remediated state
-
-
- Configure Windows software trace preprocessor components
-
-
- Configure WPP tracing level
-
-
- Configure time interval for service health reports
-
-
- Specify the maximum depth to scan archive files
-
-
- Specify the maximum size of archive files to be scanned
-
-
- Specify the maximum percentage of CPU utilization during a scan
-
-
- Turn on removal of items from scan history folder
-
-
- Specify the interval to run quick scans per day
-
-
- Specify the scan type to use for a scheduled scan
-
-
- Specify the day of the week to run a scheduled scan
-
-
- Specify the time for a daily quick scan
-
-
- Specify the time of day to run a scheduled scan
-
-
- Define the number of days before spyware security intelligence is considered out of date
-
-
- Define the number of days before virus security intelligence is considered out of date
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Specify the day of the week to check for security intelligence updates
-
-
- Specify the time to check for security intelligence updates
-
-
- Define the number of days after which a catch-up security intelligence update is required
-
-
- Specify the interval to check for security intelligence updates
-
-
- Join Microsoft MAPS
-
-
- Send file samples when further analysis is required
-
-
- Specify threats upon which default action should not be taken when detected
-
-
- Specify threat alert levels at which default action should not be taken when detected
-
-
-
-
-
-
-
- Specify the interval for expiry notification
-
-
- Select cloud blocking level
-
-
- Specify the extended cloud check time in seconds
-
-
- Configure the guard my folders feature
-
-
- Exclusions from ASR rules:
-
-
- Set the state for each ASR rule:
-
-
- Enter the applications that should be trusted:
-
-
- Enter the folders that should be guarded:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Specify scheduler randomization window in hours.
-
-
- Select the channel for Microsoft Defender monthly platform updates:
-
-
- Select the channel for Microsoft Defender monthly engine updates:
-
-
- Select the channel for Microsoft Defender daily security intelligence updates:
-
-
- Select Device Control Default Enforcement Policy
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/WindowsDefenderSecurityCenter.adml b/policy_templates/en-US/WindowsDefenderSecurityCenter.adml
deleted file mode 100644
index 87b072c..0000000
--- a/policy_templates/en-US/WindowsDefenderSecurityCenter.adml
+++ /dev/null
@@ -1,348 +0,0 @@
-
-Windows Security
-ADMX file for Windows Security
-
-
- Windows Security
- Virus and threat protection
- Firewall and network protection
- App and browser protection
- Device performance and health
- Family options
- Notifications
- Enterprise Customization
- Account protection
- Device security
- Systray
- Hide the Virus and threat protection area
-
- Hide the Virus and threat protection area in Windows Security.
-
- Enabled:
- The Virus and threat protection area will be hidden.
-
- Disabled:
- The Virus and threat protection area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Hide the Ransomware data recovery area
-
- Hide the Ransomware data recovery area in Windows Security.
-
- Enabled:
- The Ransomware data recovery area will be hidden.
-
- Disabled:
- The Ransomware data recovery area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Hide the Firewall and network protection area
-
- Hide the Firewall and network protection area in Windows Security.
-
- Enabled:
- The Firewall and network protection area will be hidden.
-
- Disabled:
- The Firewall and network protection area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Hide the App and browser protection area
-
- Hide the App and browser protection area in Windows Security.
-
- Enabled:
- The App and browser protection area will be hidden.
-
- Disabled:
- The App and browser protection area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Prevent users from modifying settings
-
- Prevent users from making changes to the Exploit protection settings area in Windows Security.
-
- Enabled:
- Local users can not make changes in the Exploit protection settings area.
-
- Disabled:
- Local users are allowed to make changes in the Exploit protection settings area.
-
- Not configured:
- Same as Disabled.
-
- Hide the Device performance and health area
-
- Hide the Device performance and health area in Windows Security.
-
- Enabled:
- The Device performance and health area will be hidden.
-
- Disabled:
- The Device performance and health area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Hide the Family options area
-
- Hide the Family options area in Windows Security.
-
- Enabled:
- The Family options area will be hidden.
-
- Disabled:
- The Family options area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Hide all notifications
-
- Hide notifications from Windows Security.
-
- Enabled:
- Local users will not see notifications from Windows Security.
-
- Disabled:
- Local users can see notifications from Windows Security.
-
- Not configured:
- Same as Disabled.
-
- Hide non-critical notifications
-
- Only show critical notifications from Windows Security.
-
- If the Suppress all notifications GP setting has been enabled, this setting will have no effect.
-
- Enabled:
- Local users will only see critical notifications from Windows Security. They will not see other types of notifications, such as regular PC or device health information.
-
- Disabled:
- Local users will see all types of notifications from Windows Security.
-
- Not configured:
- Same as Disabled.
-
- Configure customized notifications
-
- Display specified contact information to local users in Windows Security notifications.
-
- Enabled:
- Your company contact information will be displayed in notifications that come from Windows Security.
-
- After setting this to Enabled, you must configure the Specify contact company name GP setting and at least one of the following GP settings:
- -Specify contact phone number or Skype ID
- -Specify contact email number or email ID
- -Specify contact website
- Please note that in some cases we will be limiting the contact options that are displayed based on the notification space available.
-
- Disabled:
- No contact information will be shown on notifications.
-
- Not configured:
- Same as Disabled.
-
- Configure customized contact information
-
- Display specified contact information to local users in a contact card flyout menu in Windows Security
-
- Enabled:
- Your company contact information will be displayed in a flyout menu in Windows Security.
-
- After setting this to Enabled, you must configure the Specify contact company name GP setting and at least one of the following GP settings:
- -Specify contact phone number or Skype ID
- -Specify contact email number or email ID
- -Specify contact website
-
- Disabled:
- No contact information will be shown in Windows Security.
-
- Not configured:
- Same as Disabled.
-
- Specify contact company name
-
- Specify the company name that will be displayed in Windows Security and associated notifications. This setting must be enabled for any contact information to appear.
-
- Enabled:
- Enter the company name in the Options section.
-
- Disabled:
- Company information will not be shown at all in either Windows Security or any notifications that it creates.
-
- Not configured:
- Same as Disabled.
-
- Specify contact phone number or Skype ID
-
- Specify the phone number or Skype ID that will be displayed in Windows Security and associated notifications.
-
- Users can click on the contact information to automatically call the supplied number. Skype will be used to initiate the call.
-
- Enabled:
- Enter the phone number or Skype ID in the Options section.
-
- Disabled:
- A contact phone number or Skype ID will not be shown in either Windows Security or any notifications it creates.
-
- Not configured:
- Same as Disabled.
-
- Specify contact email address or Email ID
-
- Specify the email address or email ID that will be displayed in Windows Security and associated notifications.
-
- Users can click on the contact information to create an email that will be sent to the specified address. The default email application will be used.
-
- Enabled:
- Enter the email address or email ID in the Options section.
-
- Disabled:
- A contact email address or email ID will not be shown in either Windows Security or any notifications it creates.
-
- Not configured:
- Same as Disabled.
-
- Specify contact website
-
- Specify the URL that will be displayed in Windows Security and associated notifications.
-
- Users can click on the contact information to visit the specified website. The default web browser will be used.
-
- Enabled:
- Enter the URL in the Options section.
-
- Disabled:
- A contact website URL will not be shown in either Windows Security or any notifications it creates.
-
- Not configured:
- Same as Disabled.
-
- Hide the Account protection area
-
- Hide the Account protection area in Windows Security.
-
- Enabled:
- The Account protection area will be hidden.
-
- Disabled:
- The Account protection area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Hide the Device security area
-
- Hide the Device security area in Windows Security.
-
- Enabled:
- The Device security area will be hidden.
-
- Disabled:
- The Device security area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Hide the Security processor (TPM) troubleshooter page
-
- Hide the Security processor (TPM) troubleshooting area in Windows Security.
-
- Enabled:
- The Security processor (TPM) troubleshooting area will be hidden.
-
- Disabled:
- The Security processor (TPM) troubleshooting area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Hide the Secure boot area
-
- Hide the Secure boot area in Windows Security.
-
- Enabled:
- The Secure boot area will be hidden.
-
- Disabled:
- The Secure boot area will be shown.
-
- Not configured:
- Same as Disabled.
-
- Disable the Clear TPM button
-
- Disable the Clear TPM button in Windows Security.
-
- Enabled:
- The Clear TPM button will be unavailable for use.
-
- Disabled:
- The Clear TPM button will be available for use.
-
- Not configured:
- Same as Disabled.
-
- Hide the TPM Firmware Update recommendation.
-
- Hide the recommendation to update TPM Firmware when a vulnerable firmware is detected.
-
- Enabled:
- Users will not be shown a recommendation to update their TPM Firmware.
-
- Disabled:
- Users will see a recommendation to update their TPM Firmware if Windows Security detects the system contains a TPM with vulnerable firmware.
-
- Not configured:
- Same as Disabled.
-
- Hide Windows Security Systray
-
- This policy setting hides the Windows Security notification area control.
-
- The user needs to either sign out and sign in or reboot the computer for this setting to take effect.
-
- Enabled:
- Windows Security notification area control will be hidden.
-
- Disabled:
- Windows Security notification area control will be shown.
-
- Not configured:
- Same as Disabled.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/WindowsExplorer.adml b/policy_templates/en-US/WindowsExplorer.adml
deleted file mode 100644
index c49fbdf..0000000
--- a/policy_templates/en-US/WindowsExplorer.adml
+++ /dev/null
@@ -1,627 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Restrict A, B, C and D drives only
- Restrict A, B and C drives only
- Restrict A and B drives only
- Restrict all drives
- Turn on Classic Shell
- This setting allows an administrator to revert specific Windows Shell behavior to classic Shell behavior.
-
-If you enable this setting, users cannot configure their system to open items by single-clicking (such as in Mouse in Control Panel). As a result, the user interface looks and operates like the interface for Windows NT 4.0, and users cannot restore the new features.
-Enabling this policy will also turn off the preview pane and set the folder options for File Explorer to Use classic folders view and disable the users ability to change these options.
-
-If you disable or not configure this policy, the default File Explorer behavior is applied to the user.
-
-Note: In operating systems earlier than Windows Vista, enabling this policy will also disable the Active Desktop and Web view. This setting will also take precedence over the "Enable Active Desktop" setting. If both policies are enabled, Active Desktop is disabled.
-
-Also, see the "Disable Active Desktop" setting in User Configuration\Administrative Templates\Desktop\Active Desktop and the "Do not allow Folder Options to be opened from the Options button on the View tab of the ribbon" setting in User Configuration\Administrative Templates\Windows Components\File Explorer.
- Common Open File Dialog
- Display confirmation dialog when deleting files
- Allows you to have File Explorer display a confirmation dialog whenever a file is deleted or moved to the Recycle Bin.
-
-If you enable this setting, a confirmation dialog is displayed when a file is deleted or moved to the Recycle Bin by the user.
-
-If you disable or do not configure this setting, the default behavior of not displaying a confirmation dialog occurs.
- Restrict C drive only
- Restrict D drive only
- Allow only per user or approved shell extensions
- This setting is designed to ensure that shell extensions can operate on a per-user basis. If you enable this setting, Windows is directed to only run those shell extensions that have either been approved by an administrator or that will not impact other users of the machine.
-
-A shell extension only runs if there is an entry in at least one of the following locations in registry.
-
-For shell extensions that have been approved by the administrator and are available to all users of the computer, there must be an entry at HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved.
-
-For shell extensions to run on a per-user basis, there must be an entry at HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Shell Extensions\Approved.
- Do not track Shell shortcuts during roaming
- This policy setting determines whether Windows traces shortcuts back to their sources when it cannot find the target on the user's system.
-
-Shortcut files typically include an absolute path to the original target file as well as the relative path to the current target file. When the system cannot find the file in the current target path, then, by default, it searches for the target in the original path. If the shortcut has been copied to a different computer, the original path might lead to a network computer, including external resources, such as an Internet server.
-
-If you enable this policy setting, Windows only searches the current target path. It does not search for the original path even when it cannot find the target file in the current target path.
-
-If you disable or do not configure this policy setting, Windows searches for the original path when it cannot find the target file in the current target path.
-
- Maximum number of recent documents
- "This policy setting allows you to set the maximum number of shortcuts the system can display in the Recent Items menu on the Start menu.
-
-The Recent Items menu contains shortcuts to the nonprogram files the user has most recently opened.
-
-If you enable this policy setting, the system displays the number of shortcuts specified by the policy setting.
-
-If you disable or do not configure this policy setting, by default, the system displays shortcuts to the 10 most recently opened documents."
-
- Remove the Search the Internet "Search again" link
- If you enable this policy, the "Internet" "Search again" link will not be shown when the user performs a search in the Explorer window.
-
-If you disable this policy, there will be an "Internet" "Search again" link when the user performs a search in the Explorer window. This button launches a search in the default browser with the search terms.
-
-If you do not configure this policy (default), there will be an "Internet" link when the user performs a search in the Explorer window.
- Pin Internet search sites to the "Search again" links and the Start menu
- This policy setting allows you to add Internet or intranet sites to the "Search again" links located at the bottom of search results in File Explorer and the Start menu links. The "Search again" links at the bottom of the Search Results view allow the user to reconduct a search but in a different location. The Internet search site will be searched with the text in the search box. To add an Internet search site, specify the URL of the search site in OpenSearch format with {searchTerms} for the query string (for example, http://www.example.com/results.aspx?q={searchTerms}).
-
-You can add up to five additional links to the "Search again" links at the bottom of results returned in File Explorer after a search is executed. These links will be shared between Internet search sites and Search Connectors/Libraries. Search Connector/Library links take precedence over Internet search links.
-
-The first several links will also be pinned to the Start menu. A total of four links can be pinned on the Start menu. The "See more results" link will be pinned first by default, unless it is disabled via Group Policy. The "Search the Internet" link is pinned second, if it is pinned via Group Policy (though this link is disabled by default). If a custom Internet search link is pinned using the "Custom Internet search provider" Group Policy, this link will be pinned third on the Start menu. The remaining link(s) will be shared between pinned Internet/intranet links and pinned Search Connectors/Libraries. Search Connector/Library links take precedence over Internet/intranet search links.
-
-If you enable this policy setting, the specified Internet sites will appear in the "Search again" links and the Start menu links.
-
-If you disable or do not configure this policy setting, no custom Internet search sites will be added to the "Search again" links or the Start menu links.
- Pin Libraries or Search Connectors to the "Search again" links and the Start menu
- This policy setting allows up to five Libraries or Search Connectors to be pinned to the "Search again" links and the Start menu links. The "Search again" links at the bottom of the Search Results view allow the user to reconduct a search but in a different location. To add a Library or Search Connector link, specify the path of the .Library-ms or .searchConnector-ms file in the "Location" text box (for example, "C:\sampleLibrary.Library-ms" for the Documents library, or "C:\sampleSearchConnector.searchConnector-ms" for a Search Connector). The pinned link will only work if this path is valid and the location contains the specified .Library-ms or .searchConnector-ms file.
-
-You can add up to five additional links to the "Search again" links at the bottom of results returned in File Explorer after a search is executed. These links will be shared between Internet search sites and Search Connectors/Libraries. Search Connector/Library links take precedence over Internet search links.
-
-The first several links will also be pinned to the Start menu. A total of four links can be included on the Start menu. The "See more results" link will be pinned first by default, unless it is disabled via Group Policy. The "Search the Internet" link is pinned second, if it is pinned via Group Policy (though this link is disabled by default). If a custom Internet search link is pinned using the "Custom Internet search provider" Group Policy, this link will be pinned third on the Start menu. The remaining link(s) will be shared between pinned Search Connectors/Libraries and pinned Internet/intranet search links. Search Connector/Library links take precedence over Internet/intranet search links.
-
-If you enable this policy setting, the specified Libraries or Search Connectors will appear in the "Search again" links and the Start menu links.
-
-If you disable or do not configure this policy setting, no Libraries or Search Connectors will appear in the "Search again" links or the Start menu links.
- Hide the common dialog back button
- Hide the Back button in the Open dialog box.
-
-This policy setting lets you remove new features added in Microsoft Windows 2000 Professional, so the Open dialog box appears as it did in Windows NT 4.0 and earlier. This policy setting affects only programs that use the standard Open dialog box provided to developers of Windows programs.
-
-If you enable this policy setting, the Back button is removed from the standard Open dialog box.
-
-If you disable or do not configure this policy setting, the Back button is displayed for any standard Open dialog box.
-
-To see an example of the standard Open dialog box, start Notepad and, on the File menu, click Open.
-
-Note: In Windows Vista, this policy setting applies only to applications that are using the Windows XP common dialog box style. This policy setting does not apply to the new Windows Vista common dialog box style. Also, third-party applications with Windows 2000 or later certification to are required to adhere to this policy setting.
- Turn off caching of thumbnail pictures
- This policy setting allows you to turn off caching of thumbnail pictures.
-
-If you enable this policy setting, thumbnail views are not cached.
-
-If you disable or do not configure this policy setting, thumbnail views are cached.
-
-Note: For shared corporate workstations or computers where security is a top concern, you should enable this policy setting to turn off the thumbnail view cache, because the thumbnail cache can be read by everyone.
- Remove CD Burning features
- This policy setting allows you to remove CD Burning features. File Explorer allows you to create and modify re-writable CDs if you have a CD writer connected to your PC.
-
-If you enable this policy setting, all features in the File Explorer that allow you to use your CD writer are removed.
-
-If you disable or do not configure this policy setting, users are able to use the File Explorer CD burning features.
-
-Note: This policy setting does not prevent users from using third-party applications to create or modify CDs using a CD writer.
- Remove UI to change menu animation setting
- This policy setting allows you to prevent users from enabling or disabling minor animations in the operating system for the movement of windows, menus, and lists.
-
-If you enable this policy setting, the "Use transition effects for menus and tooltips" option in Display in Control Panel is disabled, and cannot be toggled by users.
-
-Effects, such as animation, are designed to enhance the user's experience but might be confusing or distracting to some users.
-
-If you disable or do not configure this policy setting, users are allowed to turn on or off these minor system animations using the "Use transition effects for menus and tooltips" option in Display in Control Panel.
- Remove UI to change keyboard navigation indicator setting
- Disables the "Hide keyboard navigation indicators until I use the ALT key" option in Display in Control Panel.
-
-When this Display Properties option is selected, the underlining that indicates a keyboard shortcut character (hot key) does not appear on menus until you press ALT.
-
-Effects, such as transitory underlines, are designed to enhance the user's experience but might be confusing or distracting to some users.
- Remove DFS tab
- This policy setting allows you to remove the DFS tab from File Explorer.
-
-If you enable this policy setting, the DFS (Distributed File System) tab is removed from File Explorer and from other programs that use the File Explorer browser, such as My Computer. As a result, users cannot use this tab to view or change the properties of the DFS shares available from their computer.
-
-This policy setting does not prevent users from using other methods to configure DFS.
-
-If you disable or do not configure this policy setting, the DFS tab is available.
- Hide these specified drives in My Computer
- This policy setting allows you to hide these specified drives in My Computer.
-
-This policy setting allows you to remove the icons representing selected hard drives from My Computer and File Explorer. Also, the drive letters representing the selected drives do not appear in the standard Open dialog box.
-
-If you enable this policy setting, select a drive or combination of drives in the drop-down list.
-
-Note: This policy setting removes the drive icons. Users can still gain access to drive contents by using other methods, such as by typing the path to a directory on the drive in the Map Network Drive dialog box, in the Run dialog box, or in a command window.
-
-Also, this policy setting does not prevent users from using programs to access these drives or their contents. And, it does not prevent users from using the Disk Management snap-in to view and change drive characteristics.
-
-If you disable or do not configure this policy setting, all drives are displayed, or select the "Do not restrict drives" option in the drop-down list.
-
-Also, see the "Prevent access to drives from My Computer" policy setting.
- No Entire Network in Network Locations
- Removes all computers outside of the user's workgroup or local domain from lists of network resources in File Explorer and Network Locations.
-
-If you enable this setting, the system removes the Entire Network option and the icons representing networked computers from Network Locations and from the browser associated with the Map Network Drive option.
-
-This setting does not prevent users from viewing or connecting to computers in their workgroup or domain. It also does not prevent users from connecting to remote computers by other commonly used methods, such as by typing the share name in the Run dialog box or the Map Network Drive dialog box.
-
-To remove computers in the user's workgroup or domain from lists of network resources, use the "No Computers Near Me in Network Locations" setting.
-
-Note: It is a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
- Remove File menu from File Explorer
- Removes the File menu from My Computer and File Explorer.
-
-This setting does not prevent users from using other methods to perform tasks available on the File menu.
- Hide the dropdown list of recent files
- Removes the list of most recently used files from the Open dialog box.
-
-If you disable this setting or do not configure it, the "File name" field includes a drop-down list of recently used files. If you enable this setting, the "File name" field is a simple text box. Users must browse directories to find a file or type a file name in the text box.
-
-This setting, and others in this folder, lets you remove new features added in Windows 2000 Professional, so that the Open dialog box looks like it did in Windows NT 4.0 and earlier. These policies only affect programs that use the standard Open dialog box provided to developers of Windows programs.
-
-To see an example of the standard Open dialog box, start Wordpad and, on the File menu, click Open.
-
-Note: In Windows Vista, this policy setting applies only to applications that are using the Windows XP common dialog box style. This policy setting does not apply to the new Windows Vista common dialog box style. It is a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
- Do not allow Folder Options to be opened from the Options button on the View tab of the ribbon
- This policy setting allows you to prevent users from accessing Folder Options through the View tab on the ribbon in File Explorer.
-
-Folder Options allows users to change the way files and folders open, what appears in the navigation pane, and other advanced view settings.
-
-If you enable this policy setting, users will receive an error message if they tap or click the Options button or choose the Change folder and search options command, and they will not be able to open Folder Options.
-
-If you disable or do not configure this policy setting, users can open Folder Options from the View tab on the ribbon.
- Remove Hardware tab
- Removes the Hardware tab.
-
-This setting removes the Hardware tab from Mouse, Keyboard, and Sounds and Audio Devices in Control Panel. It also removes the Hardware tab from the Properties dialog box for all local drives, including hard drives, floppy disk drives, and CD-ROM drives. As a result, users cannot use the Hardware tab to view or change the device list or device properties, or use the Troubleshoot button to resolve problems with the device.
- Hides the Manage item on the File Explorer context menu
- Removes the Manage item from the File Explorer context menu. This context menu appears when you right-click File Explorer or My Computer.
-
-The Manage item opens Computer Management (Compmgmt.msc), a console tool that includes many of the primary Windows 2000 administrative tools, such as Event Viewer, Device Manager, and Disk Management. You must be an administrator to use many of the features of these tools.
-
-This setting does not remove the Computer Management item from the Start menu (Start, Programs, Administrative Tools, Computer Management), nor does it prevent users from using other methods to start Computer Management.
-
-Tip: To hide all context menus, use the "Remove File Explorer's default context menu" setting.
- Remove Shared Documents from My Computer
- This policy setting allows you to remove the Shared Documents folder from My Computer.
-
-When a Windows client is in a workgroup, a Shared Documents icon appears in the File Explorer Web view under "Other Places" and also under "Files Stored on This Computer" in My Computer. Using this policy setting, you can choose not to have these items displayed.
-
-If you enable this policy setting, the Shared Documents folder is not displayed in the Web view or in My Computer.
-
-If you disable or do not configure this policy setting, the Shared Documents folder is displayed in Web view and also in My Computer when the client is part of a workgroup.
-
-Note: The ability to remove the Shared Documents folder via Group Policy is only available on Windows XP Professional.
- Remove "Map Network Drive" and "Disconnect Network Drive"
- Prevents users from using File Explorer or Network Locations to map or disconnect network drives.
-
-If you enable this setting, the system removes the Map Network Drive and Disconnect Network Drive commands from the toolbar and Tools menus in File Explorer and Network Locations and from menus that appear when you right-click the File Explorer or Network Locations icons.
-
-This setting does not prevent users from connecting to another computer by typing the name of a shared folder in the Run dialog box.
-
-Note:
-
-This setting was documented incorrectly on the Explain tab in Group Policy for Windows 2000. The Explain tab states incorrectly that this setting prevents users from connecting and disconnecting drives.
-
-Note: It is a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
- Hide the common dialog places bar
- Removes the shortcut bar from the Open dialog box.
-
-This setting, and others in this folder, lets you remove new features added in Windows 2000 Professional, so that the Open dialog box looks like it did in Windows NT 4.0 and earlier. These policies only affect programs that use the standard Open dialog box provided to developers of Windows programs.
-
-To see an example of the standard Open dialog box, start Wordpad and, on the File menu, click Open.
-
-Note: In Windows Vista, this policy setting applies only to applications that are using the Windows XP common dialog box style. This policy setting does not apply to the new Windows Vista common dialog box style. It is a requirement for third-party applications with Windows 2000 or later certification to adhere to this setting.
- Do not move deleted files to the Recycle Bin
- When a file or folder is deleted in File Explorer, a copy of the file or folder is placed in the Recycle Bin. Using this setting, you can change this behavior.
-
-If you enable this setting, files and folders that are deleted using File Explorer will not be placed in the Recycle Bin and will therefore be permanently deleted.
-
-If you disable or do not configure this setting, files and folders deleted using File Explorer will be placed in the Recycle Bin.
- Do not request alternate credentials
- Prevents users from submitting alternate logon credentials to install a program.
-
-This setting suppresses the "Install Program As Other User" dialog box for local and network installations. This dialog box, which prompts the current user for the user name and password of an administrator, appears when users who are not administrators try to install programs locally on their computers. This setting allows administrators who have logged on as regular users to install programs without logging off and logging on again using their administrator credentials.
-
-Many programs can be installed only by an administrator. If you enable this setting and a user does not have sufficient permissions to install a program, the installation continues with the current user's logon credentials. As a result, the installation might fail, or it might complete but not include all features. Or, it might appear to complete successfully, but the installed program might not operate correctly.
-
-If you disable this setting or do not configure it, the "Install Program As Other User" dialog box appears whenever users install programs locally on the computer.
-
-By default, users are not prompted for alternate logon credentials when installing programs from a network share. If enabled, this setting overrides the "Request credentials for network installations" setting.
- Remove Security tab
- Removes the Security tab from File Explorer.
-
-If you enable this setting, users opening the Properties dialog box for all file system objects, including folders, files, shortcuts, and drives, will not be able to access the Security tab. As a result, users will be able to neither change the security settings nor view a list of all users that have access to the resource in question.
-
-If you disable or do not configure this setting, users will be able to access the security tab.
- Remove Search button from File Explorer
- This policy setting allows you to remove the Search button from the File Explorer toolbar.
-
-If you enable this policy setting, the Search button is removed from the Standard Buttons toolbar that appears in File Explorer and other programs that use the File Explorer window, such as My Computer and Network Locations.
-
-Enabling this policy setting does not remove the Search button or affect any search features of Internet browser windows, such as the Internet Explorer window.
-
-If you disable or do not configure this policy setting, the Search button is available from the File Explorer toolbar.
-
-This policy setting does not affect the Search items on the File Explorer context menu or on the Start menu. To remove Search from the Start menu, use the "Remove Search menu from Start menu" policy setting (in User Configuration\Administrative Templates\Start Menu and Taskbar). To hide all context menus, use the "Remove File Explorer's default context menu" policy setting.
- Remove File Explorer's default context menu
- Removes shortcut menus from the desktop and File Explorer. Shortcut menus appear when you right-click an item.
-
-If you enable this setting, menus do not appear when you right-click the desktop or when you right-click the items in File Explorer. This setting does not prevent users from using other methods to issue commands available on the shortcut menus.
- Prevent access to drives from My Computer
- Prevents users from using My Computer to gain access to the content of selected drives.
-
-If you enable this setting, users can browse the directory structure of the selected drives in My Computer or File Explorer, but they cannot open folders and access the contents. Also, they cannot use the Run dialog box or the Map Network Drive dialog box to view the directories on these drives.
-
-To use this setting, select a drive or combination of drives from the drop-down list. To allow access to all drive directories, disable this setting or select the "Do not restrict drives" option from the drop-down list.
-
-Note: The icons representing the specified drives still appear in My Computer, but if users double-click the icons, a message appears explaining that a setting prevents the action.
-
- Also, this setting does not prevent users from using programs to access local and network drives. And, it does not prevent them from using the Disk Management snap-in to view and change drive characteristics.
-
-Also, see the "Hide these specified drives in My Computer" setting.
- Turn off Windows Key hotkeys
- Turn off Windows Key hotkeys.
-
-Keyboards with a Windows key provide users with shortcuts to common shell features. For example, pressing the keyboard sequence Windows+R opens the Run dialog box; pressing Windows+E starts File Explorer. By using this setting, you can disable these Windows Key hotkeys.
-
-If you enable this setting, the Windows Key hotkeys are unavailable.
-
-If you disable or do not configure this setting, the Windows Key hotkeys are available.
- No Computers Near Me in Network Locations
- This policy setting allows you to remove computers in the user's workgroup and domain from lists of network resources in File Explorer and Network Locations.
-
-If you enable this policy setting, the system removes the "Computers Near Me" option and the icons representing nearby computers from Network Locations. This policy setting also removes these icons from the Map Network Drive browser.
-
-If you disable or do not configure this policy setting, computers in the user's workgroup and domain appear in lists of network resources in File Explorer and Network Locations.
-
-This policy setting does not prevent users from connecting to computers in their workgroup or domain by other commonly used methods, such as typing the share name in the Run dialog box or the Map Network Drive dialog box.
-
-To remove network computers from lists of network resources, use the "No Entire Network in Network Locations" policy setting.
-
- Items displayed in Places Bar
- Configures the list of items displayed in the Places Bar in the Windows File/Open dialog. If enable this setting you can specify from 1 to 5 items to be displayed in the Places Bar.
-
-The valid items you may display in the Places Bar are:
-
-1) Shortcuts to a local folders -- (ex. C:\Windows)
-
-2) Shortcuts to remote folders -- (\\server\share)
-
-3) FTP folders
-
-4) web folders
-
-5) Common Shell folders.
-
-The list of Common Shell Folders that may be specified:
-
-Desktop, Recent Places, Documents, Pictures, Music, Recently Changed, Attachments and Saved Searches.
-
-If you disable or do not configure this setting the default list of items will be displayed in the Places Bar.
-
-Note: In Windows Vista, this policy setting applies only to applications that are using the Windows XP common dialog box style. This policy setting does not apply to the new Windows Vista common dialog box style.
- Request credentials for network installations
- Prompts users for alternate logon credentials during network-based installations.
-
-This setting displays the "Install Program As Other User" dialog box even when a program is being installed from files on a network computer across a local area network connection.
-
-If you disable this setting or do not configure it, this dialog box appears only when users are installing programs from local media.
-
-The "Install Program as Other User" dialog box prompts the current user for the user name and password of an administrator. This setting allows administrators who have logged on as regular users to install programs without logging off and logging on again using their administrator credentials.
-
-If the dialog box does not appear, the installation proceeds with the current user's permissions. If these permissions are not sufficient, the installation might fail, or it might complete but not include all features. Or, it might appear to complete successfully, but the installed program might not operate correctly.
-
-Note: If it is enabled, the "Do not request alternate credentials" setting takes precedence over this setting. When that setting is enabled, users are not prompted for alternate logon credentials on any installation.
- Maximum allowed Recycle Bin size
- Limits the percentage of a volume's disk space that can be used to store deleted files.
-
-If you enable this setting, the user has a maximum amount of disk space that may be used for the Recycle Bin on their workstation.
-
-If you disable or do not configure this setting, users can change the total amount of disk space used by the Recycle Bin.
-
-Note: This setting is applied to all volumes.
- Do not restrict drives
- This policy setting allows you to configure the amount of functionality that the shell protocol can have. When using the full functionality of this protocol, applications can open folders and launch files. The protected mode reduces the functionality of this protocol allowing applications to only open a limited set of folders. Applications are not able to open files with this protocol when it is in the protected mode. It is recommended to leave this protocol in the protected mode to increase the security of Windows.
-
-If you enable this policy setting the protocol is fully enabled, allowing the opening of folders and files.
-
-If you disable this policy setting the protocol is in the protected mode, allowing applications to only open a limited set of folders.
-
-If you do not configure this policy setting the protocol is in the protected mode, allowing applications to only open a limited set of folders.
- Turn off shell protocol protected mode
- Disable Known Folders
- This policy setting allows you to specify a list of known folders that should be disabled. Disabling a known folder will prevent the underlying file or directory from being created via the known folder API. If the folder exists before the policy is applied, the folder must be manually deleted since the policy only blocks the creation of the folder.
-
-You can specify a known folder using its known folder id or using its canonical name. For example, the Sample Videos known folder can be disabled by specifying {440fcffd-a92b-4739-ae1a-d4a54907c53f} or SampleVideos.
-
-Note: Disabling a known folder can introduce application compatibility issues in applications that depend on the existence of the known folder.
- Turn off the display of snippets in Content view mode
- This policy setting allows you to turn off the display of snippets in Content view mode.
-
-If you enable this policy setting, File Explorer will not display snippets in Content view mode.
-
-If you disable or do not configure this policy setting, File Explorer shows snippets in Content view mode by default.
-
- Verify old and new Folder Redirection targets point to the same share before redirecting
- This policy setting allows you to prevent data loss when you change the target location for Folder Redirection, and the new and old targets point to the same network share, but have different network paths.
-
-If you enable this policy setting, Folder Redirection creates a temporary file in the old location in order to verify that new and old locations point to the same network share. If both new and old locations point to the same share, the target path is updated and files are not copied or deleted. The temporary file is deleted.
-
-If you disable or do not configure this policy setting, Folder Redirection does not create a temporary file and functions as if both new and old locations point to different shares when their network paths are different.
-
-Note: If the paths point to different network shares, this policy setting is not required. If the paths point to the same network share, any data contained in the redirected folders is deleted if this policy setting is not enabled.
-
- Turn off Windows Libraries features that rely on indexed file data
- This policy setting allows you to turn off Windows Libraries features that need indexed file metadata to function properly. If you enable this policy, some Windows Libraries features will be turned off to better handle included folders that have been redirected to non-indexed network locations.
-Setting this policy will:
- * Disable all Arrangement views except for "By Folder"
- * Disable all Search filter suggestions other than "Date Modified" and "Size"
- * Disable view of file content snippets in Content mode when search results are returned
- * Disable ability to stack in the Context menu and Column headers
- * Exclude Libraries from the scope of Start search
-This policy will not enable users to add unsupported locations to Libraries.
-
-If you enable this policy, Windows Libraries features that rely on indexed file data will be disabled.
-If you disable or do not configure this policy, all default Windows Libraries features will be enabled.
- Turn off display of recent search entries in the File Explorer search box
-
-Disables suggesting recent queries for the Search Box and prevents entries into the Search Box from being stored in the registry for future references.
-
-File Explorer shows suggestion pop-ups as users type into the Search Box. These suggestions are based on their past entries into the Search Box.
-
-Note: If you enable this policy, File Explorer will not show suggestion pop-ups as users type into the Search Box, and it will not store Search Box entries into the registry for future references. If the user types a property, values that match this property will be shown but no data will be saved in the registry or re-shown on subsequent uses of the search box.
-
- Disable binding directly to IPropertySetStorage without intermediate layers.
-
-Changes the behavior of IShellFolder::BindToObject for IID_IPropertySetStorage to not bind directly to the IPropertySetStorage implementation, and to include the intermediate layers provided by the Property System. This behavior is consistent with Windows Vista's behavior in this scenario.
-
-This disables access to user-defined properties, and properties stored in NTFS secondary streams.
-
- Turn off numerical sorting in File Explorer
-
-This policy setting allows you to have file names sorted literally (as in Windows 2000 and earlier) rather than in numerical order.
-If you enable this policy setting, File Explorer will sort file names by each digit in a file name (for example, 111 < 22 < 3).
-If you disable or do not configure this policy setting, File Explorer will sort file names by increasing number value (for example, 3 < 22 < 111).
-
- Allow OpenSearch queries in File Explorer
-
-This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
-
-If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
-
-If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
-
-If you do not configure this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
-
-
-This policy setting allows you to manage whether OpenSearch queries in this zone can be performed using Search Connectors in File Explorer. Search Connectors allow rich searching of remote sources from within File Explorer. Search results will be returned in File Explorer and can be acted upon like local files.
-
-If you enable this policy setting, users can perform OpenSearch queries in this zone using Search Connectors.
-
-If you disable this policy setting, users are prevented from performing OpenSearch queries in this zone using Search Connectors.
-
-If you do not configure this policy setting, users cannot perform OpenSearch queries in this zone using Search Connectors.
-
- Allow previewing and custom thumbnails of OpenSearch query results in File Explorer
-
-This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it is the zone of the thumbnail that is checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that is different than the location of the item.
-
-If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
-
-If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
-
-If you do not configure this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
-
-Changes to this setting may not be applied until the user logs off from Windows.
-
-
-This policy setting allows you to manage whether a user may preview an item from this zone or display custom thumbnails in the preview pane in File Explorer. While this policy setting usually applies to items returned by OpenSearch queries using Search Connectors (which allow rich searching of remote sources from within the File Explorer), it might affect other items as well that are marked from this zone. For example, some application-specific items such as MAPI (Messaging Application Programming Interface) items that are returned as search results in File Explorer will be affected. MAPI items reside in the Internet zone, so disabling this policy for the Internet zone will prevent the previewing of these items in File Explorer. For the case of custom thumbnails, it is the zone of the thumbnail that is checked, not the zone of item. Typically these are the same but a source is able to define a specific location of a thumbnail that is different than the location of the item.
-
-If you enable this policy setting, users can preview items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
-
-If you disable this policy setting, users will be prevented from previewing items and get custom thumbnails from OpenSearch query results in this zone using File Explorer.
-
-If you do not configure this policy setting, users cannot preview items or get custom thumbnails from OpenSearch query results in this zone using File Explorer.
-
-Changes to this setting may not be applied until the user logs off from Windows.
-
- Disable
- Enable
- Location where all default Library definition files for users/machines reside.
-
-This policy setting allows you to specify a location where all default Library definition files for users/machines reside.
-
-If you enable this policy setting, administrators can specify a path where all default Library definition files for users reside. The user will not be allowed to make changes to these Libraries from the UI. On every logon, the policy settings are verified and Libraries for the user are updated or changed according to the path defined.
-
-If you disable or do not configure this policy setting, no changes are made to the location of the default Library definition files.
-
- Configure Windows Defender SmartScreen
- Warn and prevent bypass
- Warn
- This policy allows you to turn Windows Defender SmartScreen on or off. SmartScreen helps protect PCs by warning users before running potentially malicious programs downloaded from the Internet. This warning is presented as an interstitial dialog shown before running an app that has been downloaded from the Internet and is unrecognized or known to be malicious. No dialog is shown for apps that do not appear to be suspicious.
-
-Some information is sent to Microsoft about files and programs run on PCs with this feature enabled.
-
-If you enable this policy, SmartScreen will be turned on for all users. Its behavior can be controlled by the following options:
-
-• Warn and prevent bypass
-• Warn
-
-If you enable this policy with the "Warn and prevent bypass" option, SmartScreen's dialogs will not present the user with the option to disregard the warning and run the app. SmartScreen will continue to show the warning on subsequent attempts to run the app.
-
-If you enable this policy with the "Warn" option, SmartScreen's dialogs will warn the user that the app appears suspicious, but will permit the user to disregard the warning and run the app anyway. SmartScreen will not warn the user again for that app if the user tells SmartScreen to run the app.
-
-If you disable this policy, SmartScreen will be turned off for all users. Users will not be warned if they try to run suspicious apps from the Internet.
-
-If you do not configure this policy, SmartScreen will be enabled by default, but users may change their settings.
-
- Show lock in the user tile menu
- Shows or hides lock from the user tile menu.
-If you enable this policy setting, the lock option will be shown in the User Tile menu.
-
-If you disable this policy setting, the lock option will never be shown in the User Tile menu.
-
-If you do not configure this policy setting, users will be able to choose whether they want lock to show through the Power Options Control Panel.
- Show sleep in the power options menu
- Shows or hides sleep from the power options menu.
-
-If you enable this policy setting, the sleep option will be shown in the Power Options menu (as long as it is supported by the machine's hardware).
-
-If you disable this policy setting, the sleep option will never be shown in the Power Options menu.
-
-If you do not configure this policy setting, users will be able to choose whether they want sleep to show through the Power Options Control Panel.
- Show hibernate in the power options menu
- Shows or hides hibernate from the power options menu.
-
-If you enable this policy setting, the hibernate option will be shown in the Power Options menu (as long as it is supported by the machine's hardware).
-
-If you disable this policy setting, the hibernate option will never be shown in the Power Options menu.
-
-If you do not configure this policy setting, users will be able to choose whether they want hibernate to show through the Power Options Control Panel.
- Do not show the 'new application installed' notification
- This policy removes the end-user notification for new application associations. These associations are based on file types (e.g. *.txt) or protocols (e.g. http:)
-
-If this group policy is enabled, no notifications will be shown. If the group policy is not configured or disabled, notifications will be shown to the end user if a new application has been installed that can handle the file type or protocol association that was invoked.
- Start File Explorer with ribbon minimized
- This policy setting allows you to specify whether the ribbon appears minimized or in full when new File Explorer windows are opened. If you enable this policy setting, you can set how the ribbon appears the first time users open File Explorer and whenever they open new windows. If you disable or do not configure this policy setting, users can choose how the ribbon appears when they open new windows.
- Always open new File Explorer windows with the ribbon minimized.
- Never open new File Explorer windows with the ribbon minimized.
- Minimize the ribbon when File Explorer is opened the first time.
- Display the full ribbon when File Explorer is opened the first time.
- Allow the use of remote paths in file shortcut icons
- This policy setting determines whether remote paths can be used for file shortcut (.lnk file) icons.
-
-If you enable this policy setting, file shortcut icons are allowed to be obtained from remote paths.
-
-If you disable or do not configure this policy setting, file shortcut icons that use remote paths are prevented from being displayed.
-
-Note: Allowing the use of remote paths in file shortcut icons can expose users’ computers to security risks.
- Set a default associations configuration file
- This policy specifies the path to a file (e.g. either stored locally or on a network location) that contains file type and protocol default application associations. This file can be created using the DISM tool.
-
-For example:
-Dism.exe /Online /Export-DefaultAppAssociations:C:\AppAssoc.txt
-
-For more information, refer to the DISM documentation on TechNet.
-
-If this group policy is enabled and the client machine is domain-joined, the file will be processed and default associations will be applied at logon time.
-
-If the group policy is not configured, disabled, or the client machine is not domain-joined, no default associations will be applied at logon time.
-
-If the policy is enabled, disabled, or not configured, users will still be able to override default file type and protocol associations.
-
-
-
- Maximum number of recent documents
-
-
- Internet search sites to add:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Locations to pin:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Pick one of the following combinations
-
-
- Pick one of the following combinations
-
-
- Places to display:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Value represents percentage of hard disk that can be used (0 - 100).
-
- Maximum Recycle Bin size:
-
-
- Disable these Known Folders.
-
-
-
-
-
-
-
- Pick one of the following settings:
-
-
-
-
- c:\windows\system32\defaultassociations.xml
-
-
-
- Pick one of the following settings
-
-
-
-
diff --git a/policy_templates/en-US/WindowsFileProtection.adml b/policy_templates/en-US/WindowsFileProtection.adml
deleted file mode 100644
index 7cb07ba..0000000
--- a/policy_templates/en-US/WindowsFileProtection.adml
+++ /dev/null
@@ -1,62 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Windows File Protection
- Specify Windows File Protection cache location
- This policy setting specifies an alternate location for the Windows File Protection cache.
-
-If you enable this policy setting, enter the fully qualified local path to the new location in the "Cache file path" box.
-
-If you disable this setting or do not configure it, the Windows File Protection cache is located in the %Systemroot%\System32\Dllcache directory.
-
-Note: Do not put the cache on a network shared directory.
- Limit Windows File Protection cache size
- This policy setting specifies the maximum amount of disk space that can be used for the Windows File Protection file cache.
-
-Windows File Protection adds protected files to the cache until the cache content reaches the quota. If the quota is greater than 50 MB, Windows File Protection adds other important Windows XP files to the cache until the cache size reaches the quota.
-
-If you enable this policy setting, enter the maximum amount of disk space to be used (in MB). To indicate that the cache size is unlimited, select "4294967295" as the maximum amount of disk space.
-
-If you disable this policy setting or do not configure it, the default value is set to 50 MB on Windows XP Professional and is unlimited (4294967295 MB) on Windows Server 2003.
- Set Windows File Protection scanning
- Scan during startup
- This policy setting allows you to set when Windows File Protection scans protected files. This policy setting directs Windows File Protection to enumerate and scan all system files for changes.
-
-If you enable this policy setting, select a rate from the "Scanning Frequency" box. You can use this setting to direct Windows File Protection to scan files more often.
-
--- "Do not scan during startup," the default, scans files only during setup.
-
--- "Scan during startup" also scans files each time you start Windows XP. This setting delays each startup.
-
-If you disable or do not configure this policy setting, by default, files are scanned only during setup.
-
-Note: This policy setting affects file scanning only. It does not affect the standard background file change detection that Windows File Protection provides.
- Do not scan during startup
- Hide the file scan progress window
- This policy setting hides the file scan progress window. This window provides status information to sophisticated users, but it might confuse novices.
-
-If you enable this policy setting, the file scan window does not appear during file scanning.
-
-If you disable or do not configure this policy setting, the file scan progress window appears.
-
-
-
-
-
-
-
-
- To indicate that the cache size is not limited, select the
- maximum value, 4294967295.
- Cache size (in MB)
-
-
- Scanning frequency:
-
-
-
-
diff --git a/policy_templates/en-US/WindowsFirewall.adml b/policy_templates/en-US/WindowsFirewall.adml
deleted file mode 100644
index bb4f8ca..0000000
--- a/policy_templates/en-US/WindowsFirewall.adml
+++ /dev/null
@@ -1,441 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allows you to view and change the program exceptions list defined by Group Policy. Windows Defender Firewall uses two program exception lists: one is defined by Group Policy settings and the other is defined by the Windows Defender Firewall component in Control Panel.
-
-If you enable this policy setting, you can view and change the program exceptions list defined by Group Policy. If you add a program to this list and set its status to Enabled, that program can receive unsolicited incoming messages on any port that it asks Windows Defender Firewall to open, even if that port is blocked by another policy setting, such as the "Windows Defender Firewall: Define inbound port exceptions" policy setting. To view the program list, enable the policy setting and then click the Show button. To add a program, enable the policy setting, note the syntax, click the Show button. In the Show Contents dialog box type a definition string that uses the syntax format. To remove a program, click its definition, and then press the DELETE key. To edit a definition, remove the current definition from the list and add a new one with different parameters. To allow administrators to add programs to the local program exceptions list that is defined by the Windows Defender Firewall component in Control Panel, also enable the "Windows Defender Firewall: Allow local program exceptions" policy setting.
-
-If you disable this policy setting, the program exceptions list defined by Group Policy is deleted. If a local program exceptions list exists, it is ignored unless you enable the "Windows Defender Firewall: Allow local program exceptions" policy setting.
-
-If you do not configure this policy setting, Windows Defender Firewall uses only the local program exceptions list that administrators define by using the Windows Defender Firewall component in Control Panel.
-
-Note: If you type an invalid definition string, Windows Defender Firewall adds it to the list without checking for errors. This allows you to add programs that you have not installed yet, but be aware that you can accidentally create multiple entries for the same program with conflicting Scope or Status values. Scope parameters are combined for multiple entries.
-
-Note: If you set the Status parameter of a definition string to "disabled," Windows Defender Firewall ignores port requests made by that program and ignores other definitions that set the Status of that program to "enabled." Therefore, if you set the Status to "disabled," you prevent administrators from allowing the program to ask Windows Defender Firewall to open additional ports. However, even if the Status is "disabled," the program can still receive unsolicited incoming messages through a port if another policy setting opens that port.
-
-Note: Windows Defender Firewall opens ports for the program only when the program is running and "listening" for incoming messages. If the program is not running, or is running but not listening for those messages, Windows Defender Firewall does not open its ports.
- Windows Defender Firewall: Define inbound program exceptions
- Allows administrators to use the Windows Defender Firewall component in Control Panel to define a local program exceptions list. Windows Defender Firewall uses two program exceptions lists; the other is defined by the "Windows Defender Firewall: Define inbound program exceptions" policy setting.
-
-If you enable this policy setting, the Windows Defender Firewall component in Control Panel allows administrators to define a local program exceptions list.
-
-If you disable this policy setting, the Windows Defender Firewall component in Control Panel does not allow administrators to define a local program exceptions list. However, local administrators will still be allowed to create firewall rules in the Windows Defender Firewall with Advanced Security snap-in. If you wish to prevent all locally created rules from applying, use the Group Policy Object Editor snap-in and configure Computer Configuration\Windows Settings\Security Settings\Windows Defender Firewall with Advanced Security to specify that local firewall rules should not apply.
- Windows Defender Firewall: Allow local program exceptions
- Allows unsolicited incoming messages from specified systems that authenticate using the IPsec transport.
-
-If you enable this policy setting, you must type a security descriptor containing a list of computers or groups of computers. If a computer on that list authenticates using IPsec, Windows Defender Firewall does not block its unsolicited messages. This policy setting overrides other policy settings that would block those messages.
-
-If you disable or do not configure this policy setting, Windows Defender Firewall makes no exception for messages sent by computers that authenticate using IPsec. If you enable this policy setting and add systems to the list, upon disabling this policy, Windows Defender Firewall deletes the list.
-
-Note: You define entries in this list by using Security Descriptor Definition Language (SDDL) strings. For more information about the SDDL format, see the Windows Defender Firewall deployment information at the Microsoft Web site (http://go.microsoft.com/fwlink/?LinkId=25131).
- Windows Defender Firewall: Allow authenticated IPsec bypass
- Windows Defender Firewall
- Turns on Windows Defender Firewall.
-
-If you enable this policy setting, Windows Defender Firewall runs and ignores the "Computer Configuration\Administrative Templates\Network\Network Connections\Prohibit use of Internet Connection Firewall on your DNS domain network" policy setting.
-
-If you disable this policy setting, Windows Defender Firewall does not run. This is the only way to ensure that Windows Defender Firewall does not run and administrators who log on locally cannot start it.
-
-If you do not configure this policy setting, administrators can use the Windows Defender Firewall component in Control Panel to turn Windows Defender Firewall on or off, unless the "Prohibit use of Internet Connection Firewall on your DNS domain network" policy setting overrides.
- Windows Defender Firewall: Protect all network connections
- Specifies that Windows Defender Firewall blocks all unsolicited incoming messages. This policy setting overrides all other Windows Defender Firewall policy settings that allow such messages.
-
-If you enable this policy setting, in the Windows Defender Firewall component of Control Panel, the "Block all incoming connections" check box is selected and administrators cannot clear it. You should also enable the "Windows Defender Firewall: Protect all network connections" policy setting; otherwise, administrators who log on locally can work around the "Windows Defender Firewall: Do not allow exceptions" policy setting by turning off the firewall.
-
-If you disable this policy setting, Windows Defender Firewall applies other policy settings that allow unsolicited incoming messages. In the Windows Defender Firewall component of Control Panel, the "Block all incoming connections" check box is cleared and administrators cannot select it.
-
-If you do not configure this policy setting, Windows Defender Firewall applies other policy settings that allow unsolicited incoming messages. In the Windows Defender Firewall component of Control Panel, the "Block all incoming connections" check box is cleared by default, but administrators can change it.
- Windows Defender Firewall: Do not allow exceptions
- Allows inbound file and printer sharing. To do this, Windows Defender Firewall opens UDP ports 137 and 138, and TCP ports 139 and 445.
-
-If you enable this policy setting, Windows Defender Firewall opens these ports so that this computer can receive print jobs and requests for access to shared files. You must specify the IP addresses or subnets from which these incoming messages are allowed. In the Windows Defender Firewall component of Control Panel, the "File and Printer Sharing" check box is selected and administrators cannot clear it.
-
-If you disable this policy setting, Windows Defender Firewall blocks these ports, which prevents this computer from sharing files and printers. If an administrator attempts to open any of these ports by adding them to a local port exceptions list, Windows Defender Firewall does not open the port. In the Windows Defender Firewall component of Control Panel, the "File and Printer Sharing" check box is cleared and administrators cannot select it.
-
-If you do not configure this policy setting, Windows Defender Firewall does not open these ports. Therefore, the computer cannot share files or printers unless an administrator uses other policy settings to open the required ports. In the Windows Defender Firewall component of Control Panel, the "File and Printer Sharing" check box is cleared. Administrators can change this check box.
-
-Note: If any policy setting opens TCP port 445, Windows Defender Firewall allows inbound ICMP echo requests (the message sent by the Ping utility), even if the "Windows Defender Firewall: Allow ICMP exceptions" policy setting would block them. Policy settings that can open TCP port 445 include "Windows Defender Firewall: Allow inbound file and printer sharing exception," "Windows Defender Firewall: Allow inbound remote administration exception," and "Windows Defender Firewall: Define inbound port exceptions."
- Windows Defender Firewall: Allow inbound file and printer sharing exception
- Defines the set of Internet Control Message Protocol (ICMP) message types that Windows Defender Firewall allows. Utilities can use ICMP messages to determine the status of other computers. For example, Ping uses the echo request message. If you do not enable the "Allow inbound echo request" message type, Windows Defender Firewall blocks echo request messages sent by Ping running on other computers, but it does not block outbound echo request messages sent by Ping running on this computer.
-
-If you enable this policy setting, you must specify which ICMP message types Windows Defender Firewall allows this computer to send or receive.
-
-If you disable this policy setting, Windows Defender Firewall blocks all the listed incoming and outgoing ICMP message types. As a result, utilities that use the blocked ICMP messages will not be able to send those messages to or from this computer. If you enable this policy setting and allow certain message types, then later disable this policy setting, Windows Defender Firewall deletes the list of message types that you had enabled.
-
-If you do not configure this policy setting, Windows Defender Firewall behaves as if you had disabled it.
-
-Note: If any policy setting opens TCP port 445, Windows Defender Firewall allows inbound echo requests, even if the "Windows Defender Firewall: Allow ICMP exceptions" policy setting would block them. Policy settings that can open TCP port 445 include "Windows Defender Firewall: Allow file and printer sharing exception," "Windows Defender Firewall: Allow remote administration exception," and "Windows Defender Firewall: Define inbound port exceptions."
-
-Note: Other Windows Defender Firewall policy settings affect only incoming messages, but several of the options of the "Windows Defender Firewall: Allow ICMP exceptions" policy setting affect outgoing communication.
- Windows Defender Firewall: Allow ICMP exceptions
- Allows Windows Defender Firewall to record information about the unsolicited incoming messages that it receives.
-
-If you enable this policy setting, Windows Defender Firewall writes the information to a log file. You must provide the name, location, and maximum size of the log file. The location can contain environment variables. You must also specify whether to record information about incoming messages that the firewall blocks (drops) and information about successful incoming and outgoing connections. Windows Defender Firewall does not provide an option to log successful incoming messages.
-
-If you are configuring the log file name, ensure that the Windows Defender Firewall service account has write permissions to the folder containing the log file. Default path for the log file is %systemroot%\system32\LogFiles\Firewall\pfirewall.log.
-
-If you disable this policy setting, Windows Defender Firewall does not record information in the log file. If you enable this policy setting, and Windows Defender Firewall creates the log file and adds information, then upon disabling this policy setting, Windows Defender Firewall leaves the log file intact.
-
-If you do not configure this policy setting, Windows Defender Firewall behaves as if the policy setting were disabled.
-
-
- Windows Defender Firewall: Allow logging
- Prevents Windows Defender Firewall from displaying notifications to the user when a program requests that Windows Defender Firewall add the program to the program exceptions list.
-
-If you enable this policy setting, Windows Defender Firewall prevents the display of these notifications.
-
-If you disable this policy setting, Windows Defender Firewall allows the display of these notifications. In the Windows Defender Firewall component of Control Panel, the "Notify me when Windows Defender Firewall blocks a new program" check box is selected and administrators cannot clear it.
-
-If you do not configure this policy setting, Windows Defender Firewall behaves as if the policy setting were disabled, except that in the Windows Defender Firewall component of Control Panel, the "Notify me when Windows Defender Firewall blocks a new program" check box is selected by default, and administrators can change it.
- Windows Defender Firewall: Prohibit notifications
- Allows you to view and change the inbound port exceptions list defined by Group Policy. Windows Defender Firewall uses two port exception lists: one is defined by Group Policy settings and the other is defined by the Windows Defender Firewall component in Control Panel.
-
-If you enable this policy setting, you can view and change the inbound port exceptions list defined by Group Policy. To view this port exceptions list, enable the policy setting and then click the Show button. To add a port, enable the policy setting, note the syntax, click the Show button. In the Show Contents dialog box type a definition string that uses the syntax format. To remove a port, click its definition, and then press the DELETE key. To edit a definition, remove the current definition from the list and add a new one with different parameters. To allow administrators to add ports to the local port exceptions list that is defined by the Windows Defender Firewall component in Control Panel, also enable the "Windows Defender Firewall: Allow local port exceptions" policy setting.
-
-If you disable this policy setting, the port exceptions list defined by Group Policy is deleted, but other policy settings can continue to open or block ports. Also, if a local port exceptions list exists, it is ignored unless you enable the "Windows Defender Firewall: Allow local port exceptions" policy setting.
-
-If you do not configure this policy setting, Windows Defender Firewall uses only the local port exceptions list that administrators define by using the Windows Defender Firewall component in Control Panel. Other policy settings can continue to open or block ports.
-
-Note: If you type an invalid definition string, Windows Defender Firewall adds it to the list without checking for errors, and therefore you can accidentally create multiple entries for the same port with conflicting Scope or Status values. Scope parameters are combined for multiple entries. If entries have different Status values, any definition with the Status set to "disabled" overrides all definitions with the Status set to "enabled," and the port does not receive messages. Therefore, if you set the Status of a port to "disabled," you can prevent administrators from using the Windows Defender Firewall component in Control Panel to enable the port.
-
-Note: The only effect of setting the Status value to "disabled" is that Windows Defender Firewall ignores other definitions for that port that set the Status to "enabled." If another policy setting opens a port, or if a program in the program exceptions list asks Windows Defender Firewall to open a port, Windows Defender Firewall opens the port.
-
-Note: If any policy setting opens TCP port 445, Windows Defender Firewall allows inbound ICMP echo request messages (the message sent by the Ping utility), even if the "Windows Defender Firewall: Allow ICMP exceptions" policy setting would block them. Policy settings that can open TCP port 445 include "Windows Defender Firewall: Allow inbound file and printer sharing exception," "Windows Defender Firewall: Allow inbound remote administration exception," and "Windows Defender Firewall: Define inbound port exceptions."
- Windows Defender Firewall: Define inbound port exceptions
- Allows administrators to use the Windows Defender Firewall component in Control Panel to define a local port exceptions list. Windows Defender Firewall uses two port exceptions lists; the other is defined by the "Windows Defender Firewall: Define inbound port exceptions" policy setting.
-
-If you enable this policy setting, the Windows Defender Firewall component in Control Panel allows administrators to define a local port exceptions list.
-
-If you disable this policy setting, the Windows Defender Firewall component in Control Panel does not allow administrators to define a local port exceptions list. However, local administrators will still be allowed to create firewall rules in the Windows Defender Firewall with Advanced Security snap-in. If you wish to prevent all locally created rules from applying, use the Group Policy Object Editor snap-in and configure Computer Configuration\Windows Settings\Security Settings\Windows Defender Firewall with Advanced Security to specify that local firewall rules should not apply.
- Windows Defender Firewall: Allow local port exceptions
- Domain Profile
- Standard Profile
- Allows remote administration of this computer using administrative tools such as the Microsoft Management Console (MMC) and Windows Management Instrumentation (WMI). To do this, Windows Defender Firewall opens TCP ports 135 and 445. Services typically use these ports to communicate using remote procedure calls (RPC) and Distributed Component Object Model (DCOM). Additionally, on Windows XP Professional with at least SP2 and Windows Server 2003 with at least SP1, this policy setting also allows SVCHOST.EXE and LSASS.EXE to receive unsolicited incoming messages and allows hosted services to open additional dynamically-assigned ports, typically in the range of 1024 to 1034. On Windows Vista, this policy setting does not control connections to SVCHOST.EXE and LSASS.EXE.
-
-If you enable this policy setting, Windows Defender Firewall allows the computer to receive the unsolicited incoming messages associated with remote administration. You must specify the IP addresses or subnets from which these incoming messages are allowed.
-
-If you disable or do not configure this policy setting, Windows Defender Firewall does not open TCP port 135 or 445. Also, on Windows XP Professional with at least SP2 and Windows Server 2003 with at least SP1, Windows Defender Firewall prevents SVCHOST.EXE and LSASS.EXE from receiving unsolicited incoming messages, and prevents hosted services from opening additional dynamically-assigned ports. Because disabling this policy setting does not block TCP port 445, it does not conflict with the "Windows Defender Firewall: Allow file and printer sharing exception" policy setting.
-
-Note: Malicious users often attempt to attack networks and computers using RPC and DCOM. We recommend that you contact the manufacturers of your critical programs to determine if they are hosted by SVCHOST.exe or LSASS.exe or if they require RPC and DCOM communication. If they do not, then do not enable this policy setting.
-
-Note: If any policy setting opens TCP port 445, Windows Defender Firewall allows inbound ICMP echo request messages (the message sent by the Ping utility), even if the "Windows Defender Firewall: Allow ICMP exceptions" policy setting would block them. Policy settings that can open TCP port 445 include "Windows Defender Firewall: Allow inbound file and printer sharing exception," "Windows Defender Firewall: Allow inbound remote administration exception," and "Windows Defender Firewall: Define inbound port exceptions."
- Windows Defender Firewall: Allow inbound remote administration exception
- Allows this computer to receive inbound Remote Desktop requests. To do this, Windows Defender Firewall opens TCP port 3389.
-
-If you enable this policy setting, Windows Defender Firewall opens this port so that this computer can receive Remote Desktop requests. You must specify the IP addresses or subnets from which these incoming messages are allowed. In the Windows Defender Firewall component of Control Panel, the "Remote Desktop" check box is selected and administrators cannot clear it.
-
-If you disable this policy setting, Windows Defender Firewall blocks this port, which prevents this computer from receiving Remote Desktop requests. If an administrator attempts to open this port by adding it to a local port exceptions list, Windows Defender Firewall does not open the port. In the Windows Defender Firewall component of Control Panel, the "Remote Desktop" check box is cleared and administrators cannot select it.
-
-If you do not configure this policy setting, Windows Defender Firewall does not open this port. Therefore, the computer cannot receive Remote Desktop requests unless an administrator uses other policy settings to open the port. In the Windows Defender Firewall component of Control Panel, the "Remote Desktop" check box is cleared. Administrators can change this check box."
- Windows Defender Firewall: Allow inbound Remote Desktop exceptions
- Prevents this computer from receiving unicast responses to its outgoing multicast or broadcast messages.
-
-If you enable this policy setting, and this computer sends multicast or broadcast messages to other computers, Windows Defender Firewall blocks the unicast responses sent by those other computers.
-
-If you disable or do not configure this policy setting, and this computer sends a multicast or broadcast message to other computers, Windows Defender Firewall waits as long as three seconds for unicast responses from the other computers and then blocks all later responses.
-
-Note: This policy setting has no effect if the unicast message is a response to a Dynamic Host Configuration Protocol (DHCP) broadcast message sent by this computer. Windows Defender Firewall always permits those DHCP unicast responses. However, this policy setting can interfere with the NetBIOS messages that detect name conflicts.
- Windows Defender Firewall: Prohibit unicast response to multicast or broadcast requests
- Allows this computer to receive unsolicited inbound Plug and Play messages sent by network devices, such as routers with built-in firewalls. To do this, Windows Defender Firewall opens TCP port 2869 and UDP port 1900.
-
-If you enable this policy setting, Windows Defender Firewall opens these ports so that this computer can receive Plug and Play messages. You must specify the IP addresses or subnets from which these incoming messages are allowed. In the Windows Defender Firewall component of Control Panel, the "UPnP framework" check box is selected and administrators cannot clear it.
-
-If you disable this policy setting, Windows Defender Firewall blocks these ports, which prevents this computer from receiving Plug and Play messages. If an administrator attempts to open these ports by adding them to a local port exceptions list, Windows Defender Firewall does not open the ports. In the Windows Defender Firewall component of Control Panel, the "UPnP framework" check box is cleared and administrators cannot select it.
-
-If you do not configure this policy setting, Windows Defender Firewall does not open these ports. Therefore, the computer cannot receive Plug and Play messages unless an administrator uses other policy settings to open the required ports or enable the required programs. In the Windows Defender Firewall component of Control Panel, the "UPnP framework" check box is cleared. Administrators can change this check box."
- Windows Defender Firewall: Allow inbound UPnP framework exceptions
-
-
-
- Define program exceptions:
- Specify the program to allow or block.
- Syntax:
- <Path>:<Scope>:<Status>:<Name>
- <Path> is the program path and file name
- <Scope> is either "*" (for all networks) or
- a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- <Status> is either "enabled" or "disabled"
- <Name> is a text string
- Example:
- The following definition string adds the
- TEST.EXE program to the program exceptions list
- and allows it to receive messages from 10.0.0.1,
- or any system on the 10.3.4.x subnet:
- %programfiles%\test.exe:10.0.0.1,10.3.4.0/24:enabled:Test program
-
-
- Define program exceptions:
- Specify the program to allow or block.
- Syntax:
- <Path>:<Scope>:<Status>:<Name>
- <Path> is the program path and file name
- <Scope> is either "*" (for all networks) or
- a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- <Status> is either "enabled" or "disabled"
- <Name> is a text string
- Example:
- The following definition string adds the
- TEST.EXE program to the program exceptions list
- and allows it to receive messages from 10.0.0.1,
- or any system on the 10.3.4.x subnet:
- %programfiles%\test.exe:10.0.0.1,10.3.4.0/24:enabled:Test program
-
-
-
-
-
- Specify the IPsec peers to exempt
- using an SDDL string.
- Syntax:
- O:<OwnerSID>G:<GroupSID>D:<DACLflags>
- <OwnerSID> is the owner security descriptor
- <GroupSID> is the group security descriptor
- <DACLflags> is a list of ACEs
- Example:
- O:DAG:DAD:(A;;RCGW;;;S-1-5-21-2157571284-1609012320)
-
-
-
-
-
- Syntax:
- Type "*" to allow messages from any network, or
- else type a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- Example: to allow messages from 10.0.0.1,
- 10.0.0.2, and from any system on the
- local subnet or on the 10.3.4.x subnet,
- type the following in the "Allow unsolicited"
- incoming messages from these IP addresses":
- 10.0.0.1,10.0.0.2,localsubnet,10.3.4.0/24
-
-
-
-
-
- Syntax:
- Type "*" to allow messages from any network, or
- else type a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- Example: to allow messages from 10.0.0.1,
- 10.0.0.2, and from any system on the
- local subnet or on the 10.3.4.x subnet,
- type the following in the "Allow unsolicited"
- incoming messages from these IP addresses":
- 10.0.0.1,10.0.0.2,localsubnet,10.3.4.0/24
-
-
- Allow outbound destination unreachable
- Allow outbound source quench
- Allow redirect
- Allow inbound echo request
- Allow inbound router request
- Allow outbound time exceeded
- Allow outbound parameter problem
- Allow inbound timestamp request
- Allow inbound mask request
- Allow outbound packet too big
-
-
- Allow outbound destination unreachable
- Allow outbound source quench
- Allow redirect
- Allow inbound echo request
- Allow inbound router request
- Allow outbound time exceeded
- Allow outbound parameter problem
- Allow inbound timestamp request
- Allow inbound mask request
- Allow outbound packet too big
-
-
- Log dropped packets
- Log successful connections
-
-
- %systemroot%\system32\LogFiles\Firewall\pfirewall.log
-
- Size limit (KB):
-
-
- Log dropped packets
- Log successful connections
-
-
- %systemroot%\system32\LogFiles\Firewall\pfirewall.log
-
- Size limit (KB):
-
-
- Define port exceptions:
- Specify the port to open or block.
- Syntax:
- <Port>:<Transport>:<Scope>:<Status>:<Name>
- <Port> is a decimal port number
- <Transport> is either "TCP" or "UDP"
- <Scope> is either "*" (for all networks) or
- a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- <Status> is either "enabled" or "disabled"
- <Name> is a text string
- Example:
- The following definition string adds TCP port 80
- to the port exceptions list and allows it to
- receive messages from 10.0.0.1, 10.0.0.2, or any
- system on the 10.3.4.x subnet:
- 80:TCP:10.0.0.1,10.0.0.2,10.3.4.0/24:enabled:Web service
-
-
- Define port exceptions:
- Specify the port to open or block.
- Syntax:
- <Port>:<Transport>:<Scope>:<Status>:<Name>
- <Port> is a decimal port number
- <Transport> is either "TCP" or "UDP"
- <Scope> is either "*" (for all networks) or
- a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- <Status> is either "enabled" or "disabled"
- <Name> is a text string
- Example:
- The following definition string adds TCP port 80
- to the port exceptions list and allows it to
- receive messages from 10.0.0.1, 10.0.0.2, or any
- system on the 10.3.4.x subnet:
- 80:TCP:10.0.0.1,10.0.0.2,10.3.4.0/24:enabled:Web service
-
-
-
-
-
- Syntax:
- Type "*" to allow messages from any network, or
- else type a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- Example: to allow messages from 10.0.0.1,
- 10.0.0.2, and from any system on the
- local subnet or on the 10.3.4.x subnet,
- type the following in the "Allow unsolicited"
- incoming messages from these IP addresses":
- 10.0.0.1,10.0.0.2,localsubnet,10.3.4.0/24
-
-
-
-
-
- Syntax:
- Type "*" to allow messages from any network, or
- else type a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- Example: to allow messages from 10.0.0.1,
- 10.0.0.2, and from any system on the
- local subnet or on the 10.3.4.x subnet,
- type the following in the "Allow unsolicited"
- incoming messages from these IP addresses":
- 10.0.0.1,10.0.0.2,localsubnet,10.3.4.0/24
-
-
-
-
-
- Syntax:
- Type "*" to allow messages from any network, or
- else type a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- Example: to allow messages from 10.0.0.1,
- 10.0.0.2, and from any system on the
- local subnet or on the 10.3.4.x subnet,
- type the following in the "Allow unsolicited"
- incoming messages from these IP addresses":
- 10.0.0.1,10.0.0.2,localsubnet,10.3.4.0/24
-
-
-
-
-
- Syntax:
- Type "*" to allow messages from any network, or
- else type a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- Example: to allow messages from 10.0.0.1,
- 10.0.0.2, and from any system on the
- local subnet or on the 10.3.4.x subnet,
- type the following in the "Allow unsolicited"
- incoming messages from these IP addresses":
- 10.0.0.1,10.0.0.2,localsubnet,10.3.4.0/24
-
-
-
-
-
- Syntax:
- Type "*" to allow messages from any network, or
- else type a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- Example: to allow messages from 10.0.0.1,
- 10.0.0.2, and from any system on the
- local subnet or on the 10.3.4.x subnet,
- type the following in the "Allow unsolicited"
- incoming messages from these IP addresses":
- 10.0.0.1,10.0.0.2,localsubnet,10.3.4.0/24
-
-
-
-
-
- Syntax:
- Type "*" to allow messages from any network, or
- else type a comma-separated list that contains
- any number or combination of these:
- IP addresses, such as 10.0.0.1
- Subnet descriptions, such as 10.2.3.0/24
- The string "localsubnet"
- Example: to allow messages from 10.0.0.1,
- 10.0.0.2, and from any system on the
- local subnet or on the 10.3.4.x subnet,
- type the following in the "Allow unsolicited"
- incoming messages from these IP addresses":
- 10.0.0.1,10.0.0.2,localsubnet,10.3.4.0/24
-
-
-
-
diff --git a/policy_templates/en-US/WindowsInkWorkspace.adml b/policy_templates/en-US/WindowsInkWorkspace.adml
deleted file mode 100644
index 4dac743..0000000
--- a/policy_templates/en-US/WindowsInkWorkspace.adml
+++ /dev/null
@@ -1,24 +0,0 @@
-
-
-
- Windows Ink Workspace
- Windows Ink Workspace
-
-
- At least Windows 10 Redstone
- Windows Ink Workspace
- Allow Windows Ink Workspace
- Allow Windows Ink Workspace
- Disabled
- On, but disallow access above lock
- On
- Allow suggested apps in Windows Ink Workspace
- Allow suggested apps in Windows Ink Workspace
-
-
-
- Choose one of the following actions
-
-
-
-
diff --git a/policy_templates/en-US/WindowsMessenger.adml b/policy_templates/en-US/WindowsMessenger.adml
deleted file mode 100644
index e5bcfa9..0000000
--- a/policy_templates/en-US/WindowsMessenger.adml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Do not automatically start Windows Messenger initially
- This policy setting prevents Windows Messenger from automatically running at logon.
-
-If you enable this policy setting, Windows Messenger is not loaded automatically when a user logs on.
-
-If you disable or do not configure this policy setting, Windows Messenger will be loaded automatically at logon.
-
-Note: This policy setting simply prevents Windows Messenger from running initially. If the user invokes and uses Windows Messenger from that point on, Windows Messenger will be loaded.
-
-The user can also configure this behavior on the Preferences tab on the Tools menu in the Windows Messenger user interface.
-
-Note: If you do not want users to use Windows Messenger, enable the "Do not allow Windows Messenger to run" policy setting.
-
-Note: This policy setting is available under both Computer Configuration and User Configuration. If both are present, the Computer Configuration version of this policy setting takes precedence.
- Do not automatically start Windows Messenger initially
- Do not allow Windows Messenger to be run
- This policy setting allows you to prevent Windows Messenger from running.
-
-If you enable this policy setting, Windows Messenger does not run.
-
-If you disable or do not configure this policy setting, Windows Messenger can be used.
-
-Note: If you enable this policy setting, Remote Assistance also cannot use Windows Messenger.
-
-Note: This policy setting is available under both Computer Configuration and User Configuration. If both are present, the Computer Configuration version of this policy setting takes precedence.
- Do not allow Windows Messenger to be run
- Windows Messenger
-
-
-
diff --git a/policy_templates/en-US/WindowsProducts.adml b/policy_templates/en-US/WindowsProducts.adml
deleted file mode 100644
index b2195af..0000000
--- a/policy_templates/en-US/WindowsProducts.adml
+++ /dev/null
@@ -1,109 +0,0 @@
-
-
-
- Windows Vista products table
- This file contains all the product definitions used in supported on definitions.
-
-
-
-
- Windows operating system
- Windows 2000 operating systems
- Windows 2000
- Windows 2000 Service Pack 1
- Windows 2000 Service Pack 2
- Windows 2000 Service Pack 3
- Windows 2000 Service Pack 4
-
- Windows XP operating systems
- Windows XP
- Windows XP Service Pack 1
- Windows XP Service Pack 2
-
- Windows Server 2003 operating systems
- Windows Server 2003
- Windows Server 2003 Service Pack 1
- Windows Server 2003 R2
- Windows Server 2003 Service Pack 2
-
- Windows Vista operating systems
- Windows Vista
- Windows Vista Service Pack 1
-
- Windows Server 2008 operating systems
- Windows Server 2008
- Windows Server 2008 R2
-
- Windows 7 operating systems
- Windows 7
-
- Windows 8 operating systems
- Windows 8
-
- Windows Server 2012 operating systems
- Windows Server 2012
-
- Windows RT operating systems
- Windows RT
-
- Windows 8.1 operating systems
- Windows 8.1
-
- Windows Server 2012 R2 operating systems
- Windows Server 2012 R2
-
- Windows RT 8.1 operating systems
- Windows RT 8.1
-
- Windows 10 operating systems
- Windows 10
-
- Windows Server 2016 operating systems
- Windows Server 2016
-
- Windows 10 RT operating systems
- Windows 10 RT
-
-
- Internet Explorer
- Internet Explorer 3
- Internet Explorer 4
- Internet Explorer 5
- Internet Explorer 6
- Internet Explorer 7
- Internet Explorer 8
- Internet Explorer 9
- Internet Explorer 10
- Internet Explorer 11
-
-
- Background Intelligent Transfer Service
- BITS 1.5
- BITS 2.0
- BITS 3.5
- BITS 4.0
-
-
- NetMeeting
- NetMeeting 3.0
-
-
- Windows Installer
- Windows Installer v2
- Windows Installer v3
- Windows Installer v4
- Windows 2000 with Windows Installer v2
-
-
- Windows Search
- Windows Server 2003 or Windows XP with Windows Search installed
-
-
- Windows Media Player
- Windows Media Player 8
- Windows Media Player 9
- Windows Media Player 10
- Windows Media Player 11
-
-
-
diff --git a/policy_templates/en-US/WindowsRemoteManagement.adml b/policy_templates/en-US/WindowsRemoteManagement.adml
deleted file mode 100644
index 2270d7a..0000000
--- a/policy_templates/en-US/WindowsRemoteManagement.adml
+++ /dev/null
@@ -1,188 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow remote server management through WinRM
- Allow Basic authentication
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) client uses Basic authentication.
-
-If you enable this policy setting, the WinRM client uses Basic authentication. If WinRM is configured to use HTTP transport, the user name and password are sent over the network as clear text.
-
-If you disable or do not configure this policy setting, the WinRM client does not use Basic authentication.
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) service accepts Basic authentication from a remote client.
-
- If you enable this policy setting, the WinRM service accepts Basic authentication from a remote client.
-
- If you disable or do not configure this policy setting, the WinRM service does not accept Basic authentication from a remote client.
- Allow unencrypted traffic
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) client sends and receives unencrypted messages over the network.
-
-If you enable this policy setting, the WinRM client sends and receives unencrypted messages over the network.
-
-If you disable or do not configure this policy setting, the WinRM client sends or receives only encrypted messages over the network.
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) service sends and receives unencrypted messages over the network.
-
-If you enable this policy setting, the WinRM client sends and receives unencrypted messages over the network.
-
-If you disable or do not configure this policy setting, the WinRM client sends or receives only encrypted messages over the network.
- Disallow WinRM from storing RunAs credentials
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) service will not allow RunAs credentials to be stored for any plug-ins.
-
-If you enable this policy setting, the WinRM service will not allow the RunAsUser or RunAsPassword configuration values to be set for any plug-ins. If a plug-in has already set the RunAsUser and RunAsPassword configuration values, the RunAsPassword configuration value will be erased from the credential store on this computer.
-
-If you disable or do not configure this policy setting, the WinRM service will allow the RunAsUser and RunAsPassword configuration values to be set for plug-ins and the RunAsPassword value will be stored securely.
-
-If you enable and then disable this policy setting,any values that were previously configured for RunAsPassword will need to be reset.
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) service automatically listens on the network for requests on the HTTP transport over the default HTTP port.
-
-If you enable this policy setting, the WinRM service automatically listens on the network for requests on the HTTP transport over the default HTTP port.
-
-To allow WinRM service to receive requests over the network, configure the Windows Firewall policy setting with exceptions for Port 5985 (default port for HTTP).
-
-If you disable or do not configure this policy setting, the WinRM service will not respond to requests from a remote computer, regardless of whether or not any WinRM listeners are configured.
-
-The service listens on the addresses specified by the IPv4 and IPv6 filters. The IPv4 filter specifies one or more ranges of IPv4 addresses, and the IPv6 filter specifies one or more ranges of IPv6addresses. If specified, the service enumerates the available IP addresses on the computer and uses only addresses that fall within one of the filter ranges.
-
-You should use an asterisk (*) to indicate that the service listens on all available IP addresses on the computer. When * is used, other ranges in the filter are ignored. If the filter is left blank, the service does not listen on any addresses.
-
-For example, if you want the service to listen only on IPv4 addresses, leave the IPv6 filter empty.
-
-Ranges are specified using the syntax IP1-IP2. Multiple ranges are separated using "," (comma) as the delimiter.
-
-Example IPv4 filters:\n2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22
-Example IPv6 filters:\n3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562
- Disallow Digest authentication
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) client uses Digest authentication.
-
-If you enable this policy setting, the WinRM client does not use Digest authentication.
-
-If you disable or do not configure this policy setting, the WinRM client uses Digest authentication.
- Disallow Negotiate authentication
- Disallow Kerberos authentication
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) client uses Negotiate authentication.
-
-If you enable this policy setting, the WinRM client does not use Negotiate authentication.
-
-If you disable or do not configure this policy setting, the WinRM client uses Negotiate authentication.
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) service accepts Negotiate authentication from a remote client.
-
- If you enable this policy setting, the WinRM service does not accept Negotiate authentication from a remote client.
-
- If you disable or do not configure this policy setting, the WinRM service accepts Negotiate authentication from a remote client.
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) client uses Kerberos authentication directly.
-
-If you enable this policy setting, the Windows Remote Management (WinRM) client does not use Kerberos authentication directly. Kerberos can still be used if the WinRM client is using the Negotiate authentication and Kerberos is selected.
-
-If you disable or do not configure this policy setting, the WinRM client uses the Kerberos authentication directly.
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) service accepts Kerberos credentials over the network.
-
- If you enable this policy setting, the WinRM service does not accept Kerberos credentials over the network.
-
- If you disable or do not configure this policy setting, the WinRM service accepts Kerberos authentication from a remote client.
- Allow CredSSP authentication
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) client uses CredSSP authentication.
-
-If you enable this policy setting, the WinRM client uses CredSSP authentication.
-
-If you disable or do not configure this policy setting, the WinRM client does not use CredSSP authentication.
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) service accepts CredSSP authentication from a remote client.
-
- If you enable this policy setting, the WinRM service accepts CredSSP authentication from a remote client.
-
- If you disable or do not configure this policy setting, the WinRM service does not accept CredSSP authentication from a remote client.
-
- Specify channel binding token hardening level
- This policy setting allows you to set the hardening level of the Windows Remote Management (WinRM) service with regard to channel binding tokens.
-
- If you enable this policy setting, the WinRM service uses the level specified in HardeningLevel to determine whether or not to accept a received request, based on a supplied channel binding token.
-
- If you disable or do not configure this policy setting, you can configure the hardening level locally on each computer.
-
- If HardeningLevel is set to Strict, any request not containing a valid channel binding token is rejected.
-
- If HardeningLevel is set to Relaxed (default value), any request containing an invalid channel binding token is rejected. However, a request that does not contain a channel binding token is accepted (though it is not protected from credential-forwarding attacks).
-
- If HardeningLevel is set to None, all requests are accepted (though they are not protected from credential-forwarding attacks).
-
- None
- Strict
- Relaxed
- Windows Remote Management (WinRM)
- WinRM Client
- WinRM Service
- Trusted Hosts
- This policy setting allows you to manage whether the Windows Remote Management (WinRM) client uses the list specified in TrustedHostsList to determine if the destination host is a trusted entity.
-
-If you enable this policy setting, the WinRM client uses the list specified in TrustedHostsList to determine if the destination host is a trusted entity. The WinRM client uses this list when neither HTTPS nor Kerberos are used to authenticate the identity of the host.
-
-If you disable or do not configure this policy setting and the WinRM client needs to use the list of trusted hosts, you must configure the list of trusted hosts locally on each computer.
- Turn On Compatibility HTTP Listener
- Turn On Compatibility HTTPS Listener
- This policy setting turns on or turns off an HTTP listener created for backward compatibility purposes in the Windows Remote Management (WinRM) service.
-
- If you enable this policy setting, the HTTP listener always appears.
-
- If you disable or do not configure this policy setting, the HTTP listener never appears.
-
- When certain port 80 listeners are migrated to WinRM 2.0, the listener port number changes to 5985.
-
- A listener might be automatically created on port 80 to ensure backward compatibility.
- This policy setting turns on or turns off an HTTPS listener created for backward compatibility purposes in the Windows Remote Management (WinRM) service.
-
- If you enable this policy setting, the HTTPS listener always appears.
-
- If you disable or do not configure this policy setting, the HTTPS listener never appears.
-
- When certain port 443 listeners are migrated to WinRM 2.0, the listener port number changes to 5986.
-
- A listener might be automatically created on port 443 to ensure backward compatibility.
-
-
-
-
-
-
-
-
-
- Syntax:
- Type "*" to allow messages from any IP address, or leave the
- field empty to listen on no IP address. You can specify one
- or more ranges of IP addresses.
-
- Example IPv4 filters:
- 2.0.0.1-2.0.0.20, 24.0.0.1-24.0.0.22
- *
-
- Example IPv6 filters:
- 3FFE:FFFF:7654:FEDA:1245:BA98:0000:0000-3FFE:FFFF:7654:FEDA:1245:BA98:3210:4562
- *
-
-
-
-
-
- Syntax:
- Configure the trusted hosts by a comma separated list
- of host names. You can use wildcards (*) but only
- one wildcard is allowed in a host name pattern.
- Use "<local>" (case insensitive) is used to indicate
- all host names that do not contain a period (.).
- The list can be empty to indicate that no host is trusted.
- Use asterisk (*) to indicate that all hosts are trusted.
- If you use *, then no other pattern can appear in the list.
-
-
- Examples:
- *.mydomain.com indicates that all computer in mydomain.com are trusted
- 2.0.* indicates that all IP addresses starting with 2.0. are trusted
-
-
- Hardening Level:
-
-
-
-
diff --git a/policy_templates/en-US/WindowsRemoteShell.adml b/policy_templates/en-US/WindowsRemoteShell.adml
deleted file mode 100644
index dad8c49..0000000
--- a/policy_templates/en-US/WindowsRemoteShell.adml
+++ /dev/null
@@ -1,83 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow Remote Shell Access
- This policy setting configures access to remote shells.
-
-If you enable or do not configure this policy setting, new remote shell connections are accepted by the server.
-
-If you set this policy to ‘disabled’, new remote shell connections are rejected by the server.
- Specify idle Timeout
- This policy setting configures the maximum time in milliseconds remote shell will stay open without any user activity until it is automatically deleted.
-
-Any value from 0 to 0x7FFFFFFF can be set. A minimum of 60000 milliseconds (1 minute) is used for smaller values.
-
-If you enable this policy setting, the server will wait for the specified amount of time since the last received message from the client before terminating the open shell.
-
-If you do not configure or disable this policy setting, the default value of 900000 or 15 min will be used.
- MaxConcurrentUsers
- This policy setting configures the maximum number of users able to concurrently perform remote shell operations on the system.
-
-The value can be any number from 1 to 100.
-
-If you enable this policy setting, the new shell connections are rejected if they exceed the specified limit.
-
-If you disable or do not configure this policy setting, the default number is five users.
- Specify maximum amount of memory in MB per Shell
- This policy setting configures the maximum total amount of memory in megabytes that can be allocated by any active remote shell and all its child processes.
-
-Any value from 0 to 0x7FFFFFFF can be set, where 0 equals unlimited memory, which means the ability of remote operations to allocate memory is only limited by the available virtual memory.
-
-If you enable this policy setting, the remote operation is terminated when a new allocation exceeds the specified quota.
-
-If you disable or do not configure this policy setting, the value 150 is used by default.
- Specify maximum number of processes per Shell
- This policy setting configures the maximum number of processes a remote shell is allowed to launch.
-
-If you enable this policy setting, you can specify any number from 0 to 0x7FFFFFFF to set the maximum number of process per shell. Zero (0) means unlimited number of processes.
-
-If you disable or do not configure this policy setting, the limit is five processes per shell.
- Specify Shell Timeout
-
-This policy setting is deprecated and has no effect when set to any state: Enabled, Disabled, or Not Configured.
-
- Specify maximum number of remote shells per user
- This policy setting configures the maximum number of concurrent shells any user can remotely open on the same system.
-
-Any number from 0 to 0x7FFFFFFF cand be set, where 0 means unlimited number of shells.
-
-If you enable this policy setting, the user cannot open new remote shells if the count exceeds the specified limit.
-
-If you disable or do not configure this policy setting, by default the limit is set to two remote shells per user.
-
- Windows Remote Shell
-
-
-
- AllowRemoteShellAccess
-
-
- IdleTimeout
-
-
- MaxConcurrentUsers
-
-
- MaxMemoryPerShellMB
-
-
- MaxProcessesPerShell
-
-
- ShellTimeOut
-
-
- MaxShellsPerUser
-
-
-
-
diff --git a/policy_templates/en-US/WindowsSandbox.adml b/policy_templates/en-US/WindowsSandbox.adml
deleted file mode 100644
index 1fcfc0d..0000000
--- a/policy_templates/en-US/WindowsSandbox.adml
+++ /dev/null
@@ -1,87 +0,0 @@
-
-
- Windows Sandbox
- Turn on Windows Sandbox in Managed Mode
-
-
- Windows Sandbox
-
- Allow vGPU sharing for Windows Sandbox
- This policy setting is to enable or disable the virtualized GPU.
-
-If you enable this policy setting, vGPU will be supported in the Windows Sandbox.
-
-If you disable this policy setting, Windows Sandbox will use software rendering, which can be slower than virtualized GPU.
-
-If you do not configure this policy setting, vGPU will be enabled.
-
-Note that enabling virtualized GPU can potentially increase the attack surface of the sandbox.
-
-
-
-
- Allow networking in Windows Sandbox
- This policy setting enables or disables networking in the sandbox. You can disable network access to decrease the attack surface exposed by the sandbox.
-
-If you enable this policy setting, networking is done by creating a virtual switch on the host, and connects the Windows Sandbox to it via a virtual NIC.
-
-If you disable this policy setting, networking is disabled in Windows Sandbox.
-
-If you do not configure this policy setting, networking will be enabled.
-
-Note that enabling networking can expose untrusted applications to the internal network.
-
-
-
-
- Allow audio input in Windows Sandbox
- This policy setting enables or disables audio input to the Sandbox.
-
-If you enable this policy setting, Windows Sandbox will be able to receive audio input from the user. Applications using a microphone may require this setting.
-
-If you disable this policy setting, Windows Sandbox will not be able to receive audio input from the user. Applications using a microphone may not function properly with this setting.
-
-If you do not configure this policy setting, audio input will be enabled.
-
-Note that there may be security implications of exposing host audio input to the container.
-
-
-
-
- Allow video input in Windows Sandbox
- This policy setting enables or disables video input to the Sandbox.
-
-If you enable this policy setting, video input is enabled in Windows Sandbox.
-
-If you disable this policy setting, video input is disabled in Windows Sandbox. Applications using video input may not function properly in Windows Sandbox.
-
-If you do not configure this policy setting, video input will be disabled. Applications that use video input may not function properly in Windows Sandbox.
-
-Note that there may be security implications of exposing host video input to the container.
-
-
-
- Allow printer sharing with Windows Sandbox
- This policy setting enables or disables printer sharing from the host into the Sandbox.
-
-If you enable this policy setting, host printers will be shared into Windows Sandbox.
-
-If you disable this policy setting, Windows Sandbox will not be able to view printers from the host.
-
-If you do not configure this policy setting, printer redirection will be disabled.
-
-
-
-
- Allow clipboard sharing with Windows Sandbox
- This policy setting enables or disables clipboard sharing with the sandbox.
-
-If you enable this policy setting, copy and paste between the host and Windows Sandbox are permitted.
-
-If you disable this policy setting, copy and paste in and out of Sandbox will be restricted.
-
-If you do not configure this policy setting, clipboard sharing will be enabled.
-
-
-
-
diff --git a/policy_templates/en-US/WindowsStore.adml b/policy_templates/en-US/WindowsStore.adml
deleted file mode 100644
index 7f069e7..0000000
--- a/policy_templates/en-US/WindowsStore.adml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
- Store Policy
- Store Policy
-
-
- Turn off the Store application
- Denies or allows access to the Store application.
-
-If you enable this setting, access to the Store application is denied. Access to the Store is required for installing app updates.
-
-If you disable or don't configure this setting, access to the Store application is allowed.
- Turn off Automatic Download and Install of updates
- Enables or disables the automatic download and installation of app updates.
-
-If you enable this setting, the automatic download and installation of app updates is turned off.
-
-If you disable this setting, the automatic download and installation of app updates is turned on.
-
-If you don't configure this setting, the automatic download and installation of app updates is determined by a registry setting that the user can change using Settings in the Microsoft Store.
-
- Turn off Automatic Download of updates on Win8 machines
- Enables or disables the automatic download of app updates on PCs running Windows 8.
-
-If you enable this setting, the automatic download of app updates is turned off.
-
-If you disable this setting, the automatic download of app updates is turned on.
-
-If you don't configure this setting, the automatic download of app updates is determined by a registry setting that the user can change using Settings in the Microsoft Store.
- Turn off the offer to update to the latest version of Windows
- Enables or disables the Store offer to update to the latest version of Windows.
-
-If you enable this setting, the Store application will not offer updates to the latest version of Windows.
-
-If you disable or do not configure this setting the Store application will offer updates to the latest version of Windows.
- Disable all apps from Microsoft Store
- Disable turns off the launch of all apps from the Microsoft Store that came pre-installed or were downloaded. Apps will not be updated. Your Store will also be disabled. Enable turns all of it back on. This setting applies only to Enterprise and Education editions of Windows.
- Only display the private store within the Microsoft Store
- Denies access to the retail catalog in the Microsoft Store, but displays the private store.
-
-If you enable this setting, users will not be able to view the retail catalog in the Microsoft Store, but they will be able to view apps in the private store.
-
-If you disable or don't configure this setting, users can access the retail catalog in the Microsoft Store.
- Store
-
-
-
diff --git a/policy_templates/en-US/WindowsUpdate.adml b/policy_templates/en-US/WindowsUpdate.adml
deleted file mode 100644
index c9eee19..0000000
--- a/policy_templates/en-US/WindowsUpdate.adml
+++ /dev/null
@@ -1,841 +0,0 @@
-
-
-
-
- enter display name here
- enter description here
-
-
- Windows 7, Windows Server 2008 R2, Windows Vista, Windows XP SP2
- Windows 7, Windows Server 2008 R2, Windows Vista, Windows Server 2003, Windows XP SP2, Windows XP SP1 , Windows 2000 SP4, Windows 2000 SP3
- At least Windows XP Professional Service Pack 1 or Windows 2000 Service Pack 3, excluding Windows RT
- At least Windows Server 2003 operating systems or Windows XP Professional with SP1, excluding Windows RT
- At least Windows XP Professional Service Pack 1 or At least Windows 2000 Service Pack 3 through Windows 8.1 or Windows Server 2012 R2 with most current service pack. Not supported on Windows 10 and above.
- At least Windows Vista through Windows 8.1 or Windows Server 2012 R2 with most current service pack. Not supported on Windows 10 and above.
- Windows XP Professional Service Pack 1 or At least Windows 2000 Service Pack 3
-Option 7 only supported on servers of at least Windows Server 2016 edition
- Windows Server 2016 through Windows Server 2022, or Windows 10
- At least Windows Server 2019, or Windows 10 Version 1809
- At least Windows Server 2022, or Windows 10 Version 2004
- This policy setting allows you to manage whether the 'Install Updates and Shut Down' option is displayed in the Shut Down Windows dialog box.
-
-If you enable this policy setting, 'Install Updates and Shut Down' will not appear as a choice in the Shut Down Windows dialog box, even if updates are available for installation when the user selects the Shut Down option in the Start menu.
-
-If you disable or do not configure this policy setting, the 'Install Updates and Shut Down' option will be available in the Shut Down Windows dialog box if updates are available when the user selects the Shut Down option in the Start menu.
- Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box
- This policy setting allows you to manage whether the 'Install Updates and Shut Down' option is allowed to be the default choice in the Shut Down Windows dialog.
-
-If you enable this policy setting, the user's last shut down choice (Hibernate, Restart, etc.) is the default option in the Shut Down Windows dialog box, regardless of whether the 'Install Updates and Shut Down' option is available in the 'What do you want the computer to do?' list.
-
-If you disable or do not configure this policy setting, the 'Install Updates and Shut Down' option will be the default option in the Shut Down Windows dialog box if updates are available for installation at the time the user selects the Shut Down option in the Start menu.
-
-Note that this policy setting has no impact if the Computer Configuration\Administrative Templates\Windows Components\Windows Update\Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box policy setting is enabled.
- This policy setting allows you to manage whether the 'Install Updates and Shut Down' option is allowed to be the default choice in the Shut Down Windows dialog.
-
-If you enable this policy setting, the user's last shut down choice (Hibernate, Restart, etc.) is the default option in the Shut Down Windows dialog box, regardless of whether the 'Install Updates and Shut Down' option is available in the 'What do you want the computer to do?' list.
-
-If you disable or do not configure this policy setting, the 'Install Updates and Shut Down' option will be the default option in the Shut Down Windows dialog box if updates are available for installation at the time the user selects the Shut Down option in the Start menu.
-
-Note that this policy setting has no impact if the User Configuration\Administrative Templates\Windows Components\Windows Update\Do not display 'Install Updates and Shut Down' option in Shut Down Windows dialog box policy setting is enabled.
- Do not adjust default option to 'Install Updates and Shut Down' in Shut Down Windows dialog box
- Remove access to use all Windows Update features
- This setting allows you to remove access to Windows Update.
-
-If you enable this setting, all Windows Update features are removed. This includes blocking access to the Windows Update Web site at http://windowsupdate.microsoft.com, from the Windows Update hyperlink on the Start menu, and also on the Tools menu in Internet Explorer. Windows automatic updating is also disabled; you will neither be notified about nor will you receive critical updates from Windows Update. This setting also prevents Device Manager from automatically installing driver updates from the Windows Update Web site.
-
-If enabled you can configure one of the following notification options:
-
-0 = Do not show any notifications
-
-This setting will remove all access to Windows Update features and no notifications will be shown.
-
-1 = Show restart required notifications
-
-This setting will show notifications about restarts that are required to complete an installation.
-
-On Windows 8 and Windows RT, if this policy is Enabled, then only notifications related to restarts and the inability to detect updates will be shown. The notification options are not supported. Notifications on the login screen will always show up.
- 0 - Do not show any notifications
- 1 - Show restart required notifications
- Configure Automatic Updates
- Specifies whether this computer will receive security updates and other important downloads through the Windows automatic updating service.
-
-Note: This policy does not apply to Windows RT.
-
-This setting lets you specify whether automatic updates are enabled on this computer. If the service is enabled, you must select one of the four options in the Group Policy Setting:
-
- 2 = Notify before downloading and installing any updates.
-
- When Windows finds updates that apply to this computer, users will be notified that updates are ready to be downloaded. After going to Windows Update, users can download and install any available updates.
-
- 3 = (Default setting) Download the updates automatically and notify when they are ready to be installed
-
- Windows finds updates that apply to the computer and downloads them in the background (the user is not notified or interrupted during this process). When the downloads are complete, users will be notified that they are ready to install. After going to Windows Update, users can install them.
-
- 4 = Automatically download updates and install them on the schedule specified below.
-
- When "Automatic" is selected as the scheduled install time, Windows will automatically check, download, and install updates. The device will reboot as per Windows default settings unless configured by group policy. (Applies to Windows 10, version 1809 and higher)
-
- Specify the schedule using the options in the Group Policy Setting. For version 1709 and above, there is an additional choice of limiting updating to a weekly, bi-weekly, or monthly occurrence. If no schedule is specified, the default schedule for all installations will be every day at 3:00 AM. If any updates require a restart to complete the installation, Windows will restart the computer automatically. (If a user is signed in to the computer when Windows is ready to restart, the user will be notified and given the option to delay the restart.)
-
- On Windows 8 and later, you can set updates to install during automatic maintenance instead of a specific schedule. Automatic maintenance will install updates when the computer is not in use and avoid doing so when the computer is running on battery power. If automatic maintenance is unable to install updates for 2 days, Windows Update will install updates right away. Users will then be notified about an upcoming restart, and that restart will only take place if there is no potential for accidental data loss.
-
- 5 = Allow local administrators to select the configuration mode that Automatic Updates should notify and install updates. (This option has not been carried over to any Win 10 Versions)
-
- With this option, local administrators will be allowed to use the Windows Update control panel to select a configuration option of their choice. Local administrators will not be allowed to disable the configuration for Automatic Updates.
-
- 7 = Notify for install and notify for restart. (Windows Server only)
-
- With this option from Windows Server 2016, applicable only to Server SKU devices, local administrators will be allowed to use Windows Update to proceed with installations or reboots manually.
-
-If the status for this policy is set to Disabled, any updates that are available on Windows Update must be downloaded and installed manually. To do this, search for Windows Update using Start.
-
-If the status is set to Not Configured, use of Automatic Updates is not specified at the Group Policy level. However, an administrator can still configure Automatic Updates through Control Panel.
-
- 7 - Auto Download, Notify to install, Notify to Restart
- 5 - Allow local admin to choose setting
- 4 - Auto download and schedule the install
- 3 - Auto download and notify for install
- 2 - Notify for download and auto install
- 0 - Every day
- 6 - Every Friday
- 2 - Every Monday
- 7 - Every Saturday
- 1 - Every Sunday
- 5 - Every Thursday
- 3 - Every Tuesday
- 4 - Every Wednesday
- 00:00
- 01:00
- 10:00
- 11:00
- 12:00
- 13:00
- 14:00
- 15:00
- 16:00
- 17:00
- 18:00
- 19:00
- 02:00
- 20:00
- 21:00
- 22:00
- 23:00
- 03:00
- 04:00
- 05:00
- 06:00
- 07:00
- 08:00
- 09:00
- Automatic
- Specify intranet Microsoft update service location
-
- Specifies an intranet server to host updates from Microsoft Update. You can then use this update service to automatically update computers on your network.
-
- This setting lets you specify a server on your network to function as an internal update service. The Automatic Updates client will search this service for updates that apply to the computers on your network.
-
- To use this setting, you must set two server name values: the server from which the Automatic Updates client detects and downloads updates, and the server to which updated workstations upload statistics. You can set both values to be the same server. An optional server name value can be specified to configure Windows Update Agent to download updates from an alternate download server instead of the intranet update service.
-
- If the status is set to Enabled, the Automatic Updates client connects to the specified intranet Microsoft update service (or alternate download server), instead of Windows Update, to search for and download updates. Enabling this setting means that end users in your organization don't have to go through a firewall to get updates, and it gives you the opportunity to test updates before deploying them.
-
- If the status is set to Disabled or Not Configured, and if Automatic Updates is not disabled by policy or user preference, the Automatic Updates client connects directly to the Windows Update site on the Internet.
-
- The alternate download server configures the Windows Update Agent to download files from an alternative download server instead of the intranet update service.
-
- The option to download files with missing Urls allows content to be downloaded from the Alternate Download Server when there are no download Urls for files in the update metadata. This option should only be used when the intranet update service does not provide download Urls in the update metadata for files which are present on the alternate download server.
-
- Note: If the "Configure Automatic Updates" policy is disabled, then this policy has no effect.
-
- Note: If the "Alternate Download Server" is not set, it will use the intranet update service by default to download updates.
-
- Note: The option to "Download files with no Url..." is only used if the "Alternate Download Server" is set.
-
- Note: This policy is not supported on Windows RT. Setting this policy will not have any effect on Windows RT PCs.
-
- To ensure the highest level of security, Microsoft recommends securing WSUS with TLS/SSL protocol, thereby using HTTPS based intranet servers to keep systems secure. If a proxy is required, we recommend configuring system proxy. To ensure highest levels of security, additionally leverage WSUS TLS certificate pinning on all devices.
-
- In order to keep clients inherently secure, we are no longer allowing intranet servers to leverage user proxy by default for detecting updates. If you need to leverage user proxy for detecting updates while using an intranet server despite the vulnerabilities it presents, you must configure the proxy behavior to "Allow user proxy to be used as a fallback if detection using system proxy fails".
-
- Detection for updates against intranet servers will fail when user proxy is needed as a fallback and the alternate proxy behavior is not configured.
- Only use system proxy for detecting updates (default)
- Allow user proxy to be used as a fallback if detection using system proxy fails
- Specify source service for specific classes of Windows Updates
- When this policy is enabled, devices will receive Windows updates for the classes listed from the specified update source: either Windows Update or Windows Server Update Service.
-
- Note: To receive any updates from the Windows Server Update Service you must have properly configured an intranet Microsoft update service location via the “Specify intranet Microsoft update service location” policy.
-
- If this policy is not configured or is disabled, the device will continue to detect updates per your other policy configurations.
-
- Note: If you are using “Do not allow deferral policies to cause scans against Windows Update” currently to ensure devices only scan against your specified server, we recommend configuring this policy instead or in addition to such.
- Windows Update
- Windows Server Update Services
- Specifies the hours that Windows will use to determine how long to wait before checking for available updates. The exact wait time is a sum of the specific value and a random variant of 0-4 hours.
-
- If the status is set to Enabled, Windows will check for available updates at the specified interval.
-
- If the status is set to Disabled or Not Configured, Windows will check for available updates at the default interval of 22 hours.
-
- Note: The "Specify intranet Microsoft update service location" setting must be enabled for this policy to have effect.
-
- Note: If the "Configure Automatic Updates" policy is disabled, this policy has no effect.
-
- Note: This policy is not supported on Windows RT. Setting this policy will not have any effect on Windows RT PCs.
- Automatic Updates detection frequency
- This policy setting allows you to control whether non-administrative users will receive update notifications based on the "Configure Automatic Updates" policy setting.
-
-If you enable this policy setting, Windows Automatic Update and Microsoft Update will include non-administrators when determining which logged-on user should receive update notifications. Non-administrative users will be able to install all optional, recommended, and important content for which they received a notification. Users will not see a User Account Control window and do not need elevated permissions to install these updates, except in the case of updates that contain User Interface , End User License Agreement , or Windows Update setting changes.
-
-There are two situations where the effect of this setting depends on the operating system: Hide/Restore updates, and Cancel an install.
-
-On XP: If you enable this policy setting, users will not see a User Account Control window and do not need elevated permissions to do either of these update-related tasks.
-
-On Vista: If you enable this policy setting, users will not see a User Account Control window and do not need elevated permissions to do either of these tasks. If you do not enable this policy setting, then users will always see an Account Control window and require elevated permissions to do either of these tasks.
-
-On Windows 7 : This policy setting has no effect. Users will always see an Account Control window and require elevated permissions to do either of these tasks.
-
-On Windows 8 and Windows RT: This policy setting has no effect. Users will always see an Account Control window and require elevated permissions to do either of these tasks.
-
-If you disable this policy setting, then only administrative users will receive update notifications.
-
-Note: On Windows 8 and Windows RT this policy setting is enabled by default. In all prior versions of windows, it is disabled by default.
-
-If the "Configure Automatic Updates" policy setting is disabled or is not configured, then the Elevate Non-Admin policy setting has no effect.
- Allow non-administrators to receive update notifications
- Specifies whether Automatic Updates should automatically install certain updates that neither interrupt Windows services nor restart Windows.
-
-If the status is set to Enabled, Automatic Updates will immediately install these updates once they are downloaded and ready to install.
-
-If the status is set to Disabled, such updates will not be installed immediately.
-
-Note: If the "Configure Automatic Updates" policy is disabled, this policy has no effect.
- Allow Automatic Updates immediate installation
- Specifies whether Automatic Updates will deliver both important as well as recommended updates from the Windows Update update service.
-
-When this policy is enabled, Automatic Updates will install recommended updates as well as important updates from Windows Update update service.
-
-When disabled or not configured Automatic Updates will continue to deliver important updates if it is already configured to do so.
- Turn on recommended updates via Automatic Updates
- This policy setting allows you to control whether users see detailed enhanced notification messages about featured software from the Microsoft Update service. Enhanced notification messages convey the value and promote the installation and use of optional software. This policy setting is intended for use in loosely managed environments in which you allow the end user access to the Microsoft Update service.
-
-If you enable this policy setting, a notification message will appear on the user's computer when featured software is available. The user can click the notification to open the Windows Update Application and get more information about the software or install it. The user can also click "Close this message" or "Show me later" to defer the notification as appropriate.
-
-In Windows 7, this policy setting will only control detailed notifications for optional applications. In Windows Vista, this policy setting controls detailed notifications for optional applications and updates.
-
-If you disable or do not configure this policy setting, Windows 7 users will not be offered detailed notification messages for optional applications, and Windows Vista users will not be offered detailed notification messages for optional applications or updates.
-
-By default, this policy setting is disabled.
-
-If you are not using the Microsoft Update service, then the Software Notifications policy setting has no effect.
-
-If the "Configure Automatic Updates" policy setting is disabled or is not configured, then the Software Notifications policy setting has no effect.
-
- Turn on Software Notifications
- Specifies whether the Windows Update will use the Windows Power Management features to automatically wake up the system from sleep, if there are updates scheduled for installation.
-
-Windows Update will only automatically wake up the system if Windows Update is configured to install updates automatically. If the system is in sleep when the scheduled install time occurs and there are updates to be applied, then Windows Update will use the Windows Power management features to automatically wake the system up to install the updates.
-
-Windows update will also wake the system up and install an update if an install deadline occurs.
-
-The system will not wake unless there are updates to be installed. If the system is on battery power, when Windows Update wakes it up, it will not install updates and the system will automatically return to sleep in 2 minutes.
- Enabling Windows Update Power Management to automatically wake up the system to install scheduled updates
- Specifies that to complete a scheduled installation, Automatic Updates will wait for the computer to be restarted by any user who is logged on, instead of causing the computer to restart automatically.
-
-If the status is set to Enabled, Automatic Updates will not restart a computer automatically during a scheduled installation if a user is logged in to the computer. Instead, Automatic Updates will notify the user to restart the computer.
-
-Be aware that the computer needs to be restarted for the updates to take effect.
-
-If the status is set to Disabled or Not Configured, Automatic Updates will notify the user that the computer will automatically restart in 5 minutes to complete the installation.
-
-Note: This policy applies only when Automatic Updates is configured to perform scheduled installations of updates. If the "Configure Automatic Updates" policy is disabled, this policy has no effect.
- No auto-restart with logged on users for scheduled automatic updates installations
- Always automatically restart at the scheduled time
- If you enable this policy, a restart timer will always begin immediately after Windows Update installs important updates, instead of first notifying users on the login screen for at least two days.
-
-The restart timer can be configured to start with any value from 15 to 180 minutes. When the timer runs out, the restart will proceed even if the PC has signed-in users.
-
-If you disable or do not configure this policy, Windows Update will not alter its restart behavior.
-
-If the "No auto-restart with logged on users for scheduled automatic updates installations" policy is enabled, then this policy has no effect.
-
- Windows Automatic Updates
- This setting controls automatic updates to a user's computer.
-
-Whenever a user connects to the Internet, Windows searches for updates available for the software and hardware on their computer and automatically downloads them. This happens in the background, and the user is prompted when downloaded components are ready to be installed, or prior to downloading, depending on their configuration.
-
-If you enable this setting, it prohibits Windows from searching for updates.
-
-If you disable or do not configure it, Windows searches for updates and automatically downloads them.
-
-Note: Windows Update is an online catalog customized for your computer that consists of items such as drivers, critical updates, Help files, and Internet products that you can download to keep your computer up to date.
-
-Also, see the "Remove links and access to Windows Update" setting. If the "Remove links and access to Windows Update" setting is enabled, the links to Windows Update on the Start menu are also removed.
-
-Note: If you have installed Windows XP Service Pack 1 or the update to Automatic Updates that was released after Windows XP was originally shipped, then you should use the new Automatic Updates settings located at: 'Computer Configuration / Administrative Templates / Windows Update'
-
- Specifies the amount of time for Automatic Updates to wait before prompting again with a scheduled restart.
-
- If the status is set to Enabled, a scheduled restart will occur the specified number of minutes after the previous prompt for restart was postponed.
-
- If the status is set to Disabled or Not Configured, the default interval is 10 minutes.
-
- Note: This policy applies only when Automatic Updates is configured to perform scheduled installations of updates. If the "Configure Automatic Updates" policy is disabled, this policy has no effect. This policy has no effect on Windows RT
- Re-prompt for restart with scheduled installations
- Specifies the amount of time for Automatic Updates to wait before proceeding with a scheduled restart.
-
-If the status is set to Enabled, a scheduled restart will occur the specified number of minutes after the installation is finished.
-
-If the status is set to Disabled or Not Configured, the default wait time is 15 minutes.
-
-Note: This policy applies only when Automatic Updates is configured to perform scheduled installations of updates. If the "Configure Automatic Updates" policy is disabled, this policy has no effect.
- Delay Restart for scheduled installations
- Specifies the amount of time for Automatic Updates to wait, following system startup, before proceeding with a scheduled installation that was missed previously.
-
-If the status is set to Enabled, a scheduled installation that did not take place earlier will occur the specified number of minutes after the computer is next started.
-
-If the status is set to Disabled, a missed scheduled installation will occur with the next scheduled installation.
-
-If the status is set to Not Configured, a missed scheduled installation will occur one minute after the computer is next started.
-
-Note: This policy applies only when Automatic Updates is configured to perform scheduled installations of updates. If the "Configure Automatic Updates" policy is disabled, this policy has no effect.
- Reschedule Automatic Updates scheduled installations
- Specifies the target group name or names that should be used to receive updates from an intranet Microsoft update service.
-
-If the status is set to Enabled, the specified target group information is sent to the intranet Microsoft update service which uses it to determine which updates should be deployed to this computer.
-
-If the intranet Microsoft update service supports multiple target groups this policy can specify multiple group names separated by semicolons. Otherwise, a single group must be specified.
-
-If the status is set to Disabled or Not Configured, no target group information will be sent to the intranet Microsoft update service.
-
-Note: This policy applies only when the intranet Microsoft update service this computer is directed to is configured to support client-side targeting. If the "Specify intranet Microsoft update service location" policy is disabled or not configured, this policy has no effect.
-Note: This policy is not supported on Windows RT. Setting this policy will not have any effect on Windows RT PCs.
- Enable client-side targeting
- Windows Update
-
- Manage updates offered from Windows Update
- Manage updates offered from Windows Server Update Service
- Manage end user experience
- Legacy Policies
-
- Allow signed updates from an intranet Microsoft update service location
- This policy setting allows you to manage whether Automatic Updates accepts updates signed by entities other than Microsoft when the update is found on an intranet Microsoft update service location.
-
-If you enable this policy setting, Automatic Updates accepts updates received through an intranet Microsoft update service location, if they are signed by a certificate found in the "Trusted Publishers" certificate store of the local computer.
-
-If you disable or do not configure this policy setting, updates from an intranet Microsoft update service location must be signed by Microsoft.
-
-Note: Updates from a service other than an intranet Microsoft update service must always be signed by Microsoft and are not affected by this policy setting.
-Note: This policy is not supported on Windows RT. Setting this policy will not have any effect on Windows RT PCs.
- Do not connect to any Windows Update Internet locations
- Even when Windows Update is configured to receive updates from an intranet update service, it will periodically retrieve information from the public Windows Update service to enable future connections to Windows Update, and other services like Microsoft Update or the Windows Store.
-
-Enabling this policy will disable that functionality, and may cause connection to public services such as the Windows Store to stop working.
-
-Note: This policy applies only when this PC is configured to connect to an intranet update service using the "Specify intranet Microsoft update service location" policy.
- Manage preview builds
- Enable this policy to manage which updates you receive prior to the update being released to the world.
-
-Dev Channel
-Ideal for highly technical users. Insiders in the Dev Channel will receive builds from our active development branch that is earliest in a development cycle. These builds are not matched to a specific Windows 10 release.
-
-Beta Channel
-Ideal for feature explorers who want to see upcoming Windows 10 features. Your feedback will be especially important here as it will help our engineers ensure key issues are fixed before a major release.
-
-Release Preview Channel (default)
-Insiders in the Release Preview Channel will have access to the upcoming release of Windows 10 prior to it being released to the world. These builds are supported by Microsoft. The Release Preview Channel is where we recommend companies preview and validate upcoming Windows 10 releases before broad deployment within their organization.
-
-Release Preview Channel, Quality Updates Only
-Ideal for those who want to validate the features and fixes coming soon to their current version. Note, released feature updates will continue to be offered in accordance with configured policies when this option is selected.
-
-Note: Preview Build enrollment requires a telemetry level setting of 2 or higher and your domain registered on insider.windows.com. For additional information on Preview Builds, see: https://aka.ms/wipforbiz
-
-If you disable or do not configure this policy, Windows Update will not offer you any pre-release updates and you will receive such content once released to the world. Disabling this policy will cause any devices currently on a pre-release build to opt out and stay on the latest Feature Update once released.
- Dev Channel
- Beta Channel
- Release Preview Channel
- Release Preview of Quality Updates Only
- Select when Preview Builds and Feature Updates are received
- Enable this policy to specify when to receive Feature Updates.
-
-Defer Updates | This enables devices to defer taking the next Feature Update available for their current product (or a new product if specified in the Select the target Feature Update version policy). You can defer a Feature Update for up to 14 days for all pre-release channels and up to 365 days for the General Availability Channel. To learn more about the current releases, please see aka.ms/WindowsTargetVersioninfo
-
-Pause Updates | To prevent Feature Updates from being offered to the device, you can temporarily pause Feature Updates. This pause will remain in effect for 35 days from the specified start date or until the field is cleared. Note, Quality Updates will still be offered even if Feature Updates are paused.
- Select when Quality Updates are received
- Enable this policy to specify when to receive quality updates.
-
-You can defer receiving quality updates for up to 30 days.
-
-To prevent quality updates from being received on their scheduled time, you can temporarily pause quality updates. The pause will remain in effect for 35 days or until you clear the start date field.
-
-To resume receiving Quality Updates which are paused, clear the start date field.
-
-If you disable or do not configure this policy, Windows Update will not alter its behavior.
- Select the target Feature Update version
- Enter the product and version as listed on the Windows Update target version page:
-
- aka.ms/WindowsTargetVersioninfo
-
-The device will request that Windows Update product and version in subsequent scans.
-
-Entering a target product and clicking OK or Apply means I accept the Microsoft Software License Terms for it found at aka.ms/WindowsTargetVersioninfo. If an organization is licensing the software, I am authorized to bind the organization.
-
-If you enter an invalid value, you will remain on your current version until you correct the values to a supported product and version.
- Disable safeguards for Feature Updates
-
- Enable this setting when Feature Updates should be deployed to devices without blocking on any safeguard holds. Safeguard holds are known compatibility issues that block the upgrade from being deployed to affected devices until the issue is resolved. Enabling this policy can allow an organization to deploy the Feature Update to devices for testing, or to deploy the Feature Update without blocking on safeguard holds.
-
- Do not include drivers with Windows Updates
- Enable this policy to not include drivers with Windows quality updates.
-
-If you disable or do not configure this policy, Windows Update will include updates that have a Driver classification.
- Turn off auto-restart for updates during active hours
- If you enable this policy, the PC will not automatically restart after updates during active hours. The PC will attempt to restart outside of active hours.
-
-Note that the PC must restart for certain updates to take effect.
-
-If you disable or do not configure this policy and have no other reboot group policies, the user selected active hours will be in effect.
-
-If any of the following two policies are enabled, this policy has no effect:
- 1. No auto-restart with logged on users for scheduled automatic updates installations.
- 2. Always automatically restart at scheduled time.
-
-Note that the default max active hours range is 18 hours from the active hours start time unless otherwise configured via the Specify active hours range for auto-restarts policy.
- 10 AM
- 10 PM
- 11 AM
- 11 PM
- 12 AM
- 12 PM
- 1 AM
- 1 PM
- 2 AM
- 2 PM
- 3 AM
- 3 PM
- 4 AM
- 4 PM
- 5 AM
- 5 PM
- 6 AM
- 6 PM
- 7 AM
- 7 PM
- 8 AM
- 8 PM
- 9 AM
- 9 PM
-
- Specify deadline before auto-restart for update installation
- Specify the deadline before the PC will automatically restart to apply updates. The deadline can be set 2 to 14 days past the default restart date.
-
-The restart may happen inside active hours.
-
-If you disable or do not configure this policy, the PC will restart according to the default schedule.
-
-Enabling either of the following two policies will override the above policy:
- 1. No auto-restart with logged on users for scheduled automatic updates installations.
- 2. Always automatically restart at scheduled time.
-
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
-
- Remove access to use all Windows Update features
- This setting allows you to remove access to scan Windows Update.
-
-If you enable this setting user access to Windows Update scan, download and install is removed.
-
-
- Remove access to "Pause updates" feature
- This setting allows to remove access to "Pause updates" feature.
-
-Once enabled user access to pause updates is removed.
-
-
- Specify active hours range for auto-restarts
- Enable this policy to specify the maximum number of hours from the start time that users can set their active hours.
-
-The max active hours range can be set between 8 and 18 hours.
-
-If you disable or do not configure this policy, the default max active hours range will be used.
-
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
-
- Configure auto-restart required notification for updates
- Enable this policy to specify the method by which the auto-restart required notification is dismissed. When a restart is required to install updates, the auto-restart required notification is displayed. By default, the notification is automatically dismissed after 25 seconds.
-
-The method can be set to require user action to dismiss the notification.
-
-If you disable or do not configure this policy, the default method will be used.
-
- 1 - Auto
- 2 - User Action
-
- Configure auto-restart reminder notifications for updates
- Enable this policy to specify when auto-restart reminders are displayed.
-
-You can specify the amount of time prior to a scheduled restart to notify the user.
-
-If you disable or do not configure this policy, the default period will be used.
-
- 15
- 30
- 60
- 120
- 240
-
- Turn off auto-restart notifications for update installations
- This policy setting allows you to control whether users receive notifications for auto restarts for update installations including reminder and warning notifications.
-
-Enable this policy to turn off all auto restart notifications.
-
-If you disable or do not configure this policy, the default notification behaviors will be unchanged.
-
-
- Configure auto-restart warning notifications schedule for updates
- Enable this policy to control when notifications are displayed to warn users about a scheduled restart for the update installation deadline. Users are not able to postpone the scheduled restart once the deadline has been reached and the restart is automatically executed.
-
-Specifies the amount of time prior to a scheduled restart to display the warning reminder to the user.
-
-You can specify the amount of time prior to a scheduled restart to notify the user that the auto restart is imminent to allow them time to save their work.
-
-If you disable or do not configure this policy, the default notification behaviors will be used.
-
- 2
- 4
- 8
- 12
- 24
- 15
- 30
- 60
- Specify Engaged restart transition and notification schedule for updates
- Enable this policy to control the timing before transitioning from Auto restarts scheduled outside of active hours to Engaged restart, which requires the user to schedule. The period can be set between 0 and 30 days from the time the restart becomes pending.
-
-You can specify the number of days a user can snooze Engaged restart reminder notifications. The snooze period can be set between 1 and 3 days.
-
-You can specify the deadline in days before automatically scheduling and executing a pending restart regardless of active hours. The deadline can be set between 2 and 30 days from the time the restart becomes pending. If configured, the pending restart will transition from Auto-restart to Engaged restart (pending user schedule) to automatically executed, within the specified period.
-
-If you do not specify a deadline or if the deadline is set to 0, the PC won't automatically restart and will require the person to schedule it prior to restart.
-
-If you disable or do not configure this policy, the PC will restart following the default schedule.
-
-Enabling any of the following policies will override the above policy:
- 1. No auto-restart with logged on users for scheduled automatic updates installations
- 2. Always automatically restart at scheduled time
- 3. Specify deadline before auto-restart for update installation
-
- 0
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
- 1
- 2
- 3
-
- Update Power Policy for Cart Restarts
- Enabling this policy for EDU devices that remain on Carts overnight will skip power checks to ensure update reboots will happen at the scheduled install time.
-
- Allow updates to be downloaded automatically over metered connections
- Enabling this policy will automatically download updates, even over metered data connections (charges may apply)
-
- Do not allow update deferral policies to cause scans against Windows Update
- Enable this policy to not allow update deferral policies to cause scans against Windows Update.
-
-If this policy is disabled or not configured, then the Windows Update client may initiate automatic scans against Windows Update while update deferral policies are enabled.
-Note: This policy applies only when the intranet Microsoft update service this computer is directed to is configured to support client-side targeting. If the "Specify intranet Microsoft update service location" policy is disabled or not configured, this policy has no effect.
-
- Display options for update notifications
- 0 (default) – Use the default Windows Update notifications
-1 – Turn off all notifications, excluding restart warnings
-2 – Turn off all notifications, including restart warnings
-
-This policy allows you to define what Windows Update notifications users see. This policy doesn’t control how and when updates are downloaded and installed.
-
-Important: if you choose not to get update notifications and also define other Group policy so that devices aren’t automatically getting updates, neither you nor device users will be aware of critical security, quality, or feature updates, and your devices may be at risk.
-
-If you select “Apply only during active hours” in conjunction with Option 1 or 2, then notifications will only be disabled during active hours. You can set active hours by setting “Turn off auto-restart for updates during active hours” or allow the device to set active hours based on user behavior. To ensure that the device stays secure, a notification will still be shown if this option is selected once “Specify deadlines for automatic updates and restarts” deadline has been reached if configured, regardless of active hours.
-
- 0 (default) – Default OS Windows Update notifications
- 1 – Disable all notifications, excluding restart warnings
- 2 – Disable all notifications, including restart warnings
- Specify deadlines for automatic updates and restarts
- This policy lets you specify the number of days before quality and feature updates are installed on devices automatically, and a grace period after which required restarts occur automatically.
-
-Set deadlines for feature updates and quality updates to meet your compliance goals. Updates will be downloaded and installed as soon as they are offered and automatic restarts will be attempted outside of active hours. Once the deadline has passed, restarts will occur regardless of active hours, and users will not be able to reschedule. If the deadline is set to 0 days, the update will be installed immediately upon offering, but might not finish within the day due to device availability and network connectivity.
-
-Set a grace period for feature updates and quality updates to guarantee users a minimum time to manage their restarts once updates are installed. Users will be able to schedule restarts during the grace period and Windows can still automatically restart outside of active hours if users choose not to schedule restarts. The grace period might not take effect if users already have more than the number of days set as grace period to manage their restart, based on deadline configurations.
-
-You can set the device to delay restarting until both the deadline and grace period have expired.
-
-If you disable or do not configure this policy, devices will get updates and will restart according to the default schedule.
-
-This policy will override the following policies:
-1. Specify deadline before auto restart for update installation
-2. Specify Engaged restart transition and notification schedule for updates
-3. Always automatically restart at the scheduled time
-4. Configure Automatic Updates
-
- 0
- 1
- 2
- 3
- 4
- 5
- 6
- 7
- 8
- 9
- 10
- 11
- 12
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23
- 24
- 25
- 26
- 27
- 28
- 29
- 30
-
- Enable features introduced via servicing that are off by default
- Features introduced via servicing (outside of the annual feature update) are off by default for devices that have their Windows updates managed*.
-
-If this policy is configured to “Enabled”, then all features available in the latest monthly quality update installed will be on.
-
-If this policy is set to “Not Configured” or “Disabled” then features that are shipped via a monthly quality update (servicing) will remain off until the feature update that includes these features is installed.
-
- *Windows update managed devices are those that have their Windows updates managed via policy; whether via the cloud using Windows Update for Business or on-premises with Windows Server Update Services (WSUS).
-
-
-
-
-
- Configure notifications:
-
-
- Configure automatic updating:
- The following settings are only required and applicable if 4 is selected.
- Install during automatic maintenance
- Scheduled install day:
- Scheduled install time:
- If you have selected “4 – Auto download and schedule the install” for your scheduled install day and specified a schedule, you also have the option to limit updating to a weekly, bi-weekly or monthly occurrence, using the options below:
- Every week
- First week of the month
- Second week of the month
- Third week of the month
- Fourth week of the month
-
- Install updates for other Microsoft products
-
-
-
-
-
-
-
-
-
-
-
- (example: https://IntranetUpd01)
- Download files with no Url in the metadata if alternate download server is set.
- Do not enforce TLS certificate pinning for Windows Update client for detecting updates.
- Select the proxy behavior for Windows Update client for detecting updates:
-
-
- Specify source service for the following classes of Windows updates:
- Feature Updates
- Quality Updates
- Driver Updates
- Other Updates
-
-
- Check for updates at the following
- interval (hours):
-
-
- Wait the following period before prompting again with a scheduled
- restart (minutes):
-
-
- Wait the following period before proceeding with a scheduled
- restart (minutes):
-
-
- Wait after system
- startup (minutes):
-
-
-
-
-
-
-
- The restart timer will give users this much time to save their
- work (minutes):
-
-
-
-
-
-
-
-
-
-
- Select the Windows readiness level for the updates you want to receive:
-
-
- How many days after a Feature Update is released would you like to defer the update before it is offered to the device?
-
-
-
- (format yyyy-mm-dd example: 2016-10-30)
-
-
- After a quality update is released, defer receiving it for this many days:
-
-
-
- (format yyyy-mm-dd example: 2016-10-30)
-
-
- Active Hours
- Start:
- End:
-
-
- Specify the number of days before a pending restart will automatically be executed outside of active hours:
- Quality Updates (days):
- Feature Updates (days):
-
-
- Specify the max active hours range:
- Max range:
-
-
- Specify the method by which the auto-restart required notification is dismissed:
- Method:
-
-
- Specify the period for auto-restart reminder notifications:
- Period (min):
-
-
- Specify the period for auto-restart warning reminder notifications:
- Reminder (hours):
- Specify the period for auto-restart immiment warning notifications:
- Warning (mins):
-
-
- Transition : Specify the timing before transitioning from Auto-restart to Engaged restart (pending user schedule).
- Snooze : Specify snooze for Engaged restart reminder notifications.
- Deadline : Specify the deadline before a pending restart will automatically be executed outside of active hours.
-
- For Quality Updates :
- Transition (days) :
- Snooze (days) :
- Deadline (days) :
-
- For Feature Updates :
- Transition (days) :
- Snooze (days) :
- Deadline (days) :
-
-
- Specify the update notifications display options :
-
- Apply only during active hours
-
-
- Quality Updates
- Deadline (days):
- Grace period (days):
-
- Feature Updates
- Deadline (days):
- Grace Period (days):
-
- Don't auto-restart until end of grace period
-
-
-
-
diff --git a/policy_templates/en-US/Winsrv.adml b/policy_templates/en-US/Winsrv.adml
deleted file mode 100644
index 6622880..0000000
--- a/policy_templates/en-US/Winsrv.adml
+++ /dev/null
@@ -1,17 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off automatic termination of applications that block or cancel shutdown
- This policy setting specifies whether Windows will allow console applications and GUI applications without visible top-level windows to block or cancel shutdown. By default, such applications are automatically terminated if they attempt to cancel shutdown or block it indefinitely.
-
-If you enable this setting, console applications or GUI applications without visible top-level windows that block or cancel shutdown will not be automatically terminated during shutdown.
-
-If you disable or do not configure this setting, these applications will be automatically terminated during shutdown, helping to ensure that Windows can shut down faster and more smoothly.
- Shutdown Options
-
-
-
diff --git a/policy_templates/en-US/WirelessDisplay.adml b/policy_templates/en-US/WirelessDisplay.adml
deleted file mode 100644
index 2404443..0000000
--- a/policy_templates/en-US/WirelessDisplay.adml
+++ /dev/null
@@ -1,40 +0,0 @@
-
-
- Connect
- Select an item to view its description
-
-
-
- Connect
-
-
- Don't allow this PC to be projected to
- This policy setting allows you to turn off projection to a PC.
-
-
-
-If you turn it on, your PC isn't discoverable and can't be projected to except if the user manually launches the Wireless Display app.
-
-
-
-If you turn it off or don't configure it, your PC is discoverable and can be projected to above lock screen only. The user has an option to turn it always on or off except for manual launch, too.
-
- Require pin for pairing
- This policy setting allows you to require a pin for pairing.
-
-If you set this to 'Never', a pin isn't required for pairing.
-
-If you set this to 'First Time', the pairing ceremony for new devices will always require a PIN.
-
-If you set this to 'Always', all pairings will require PIN.
- Never
- First Time
- Always
-
-
-
- Choose one of the following actions
-
-
-
-
diff --git a/policy_templates/en-US/WordWheel.adml b/policy_templates/en-US/WordWheel.adml
deleted file mode 100644
index f8c6767..0000000
--- a/policy_templates/en-US/WordWheel.adml
+++ /dev/null
@@ -1,39 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Custom Instant Search Internet search provider
- Set up the menu name and URL for the custom Internet search provider.
-
-If you enable this setting, the specified menu name and URL will be used for Internet searches.
-
-If you disable or not configure this setting, the default Internet search provider will be used.
- Hide the "Search the Internet" link from the Search box drop down.
- This policy setting allows you to manage whether the "Search the Internet" link does not appear in the Start menu and the Instant Search box drop down list.
-
-If you enable this policy setting, the "Search the Internet" link is hidden from the Start menu and the Instant Search box drop down list.
-
-If you disable or do not configure this policy setting, the "Search the Internet" link appears in the Start menu and Instant Search box drop down list.
- Require an explicit commit before conducting searches.
- This policy setting allows you to manage whether to require a specific commit before conducting searches.
-
-If you enable this policy setting, a specific commit is required before conducting searches.
-
-If you disable or do not configure this policy setting, a specific commit is not required.
- Instant Search
-
-
-
-
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/WorkFolders-Client.adml b/policy_templates/en-US/WorkFolders-Client.adml
deleted file mode 100644
index 844be24..0000000
--- a/policy_templates/en-US/WorkFolders-Client.adml
+++ /dev/null
@@ -1,55 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Work Folders
- Force automatic setup for all users
- This policy setting specifies whether Work Folders should be set up automatically for all users of the affected computer.
-
-If you enable this policy setting, Work Folders will be set up automatically for all users of the affected computer. This prevents users from choosing not to use Work Folders on the computer; it also prevents them from manually specifying the local folder in which Work Folders stores files. Work Folders will use the settings specified in the "Specify Work Folders settings" policy setting in User Configuration\Administrative Templates\Windows Components\WorkFolders. If the "Specify Work Folders settings" policy setting does not apply to a user, Work Folders is not automatically set up.
-
-If you disable or do not configure this policy setting, Work Folders uses the "Force automatic setup" option of the "Specify Work Folders settings" policy setting to determine whether to automatically set up Work Folders for a given user.
-
- Specify Work Folders settings
- This policy setting specifies the Work Folders server for affected users, as well as whether or not users are allowed to change settings when setting up Work Folders on a domain-joined computer.
-
-If you enable this policy setting, affected users receive Work Folders settings when they sign in to a domain-joined PC. If this policy setting is disabled or not configured, no Work Folders settings are specified for the affected users, though users can manually set up Work Folders by using the Work Folders Control Panel item.
-
-The "Work Folders URL" can specify either the URL used by the organization for Work Folders discovery, or the specific URL of the file server that stores the affected users' data.
-
-The "Work Folders Local Path" specifies the local folder used on the client machine to sync files. This path may contain environment variables. Note: In order for this configuration to take effect, a valid 'Work Folders URL' must also be specified.
-
-The “On-demand file access preference” option controls whether to enable on-demand file access. When enabled, the user controls which files in Work Folders are available offline on a given PC. The rest of the files in Work Folders are always visible and don’t take up any space on the PC, but the user must be connected to the Internet to access them.
-
-If you enable this policy setting, on-demand file access is enabled.
-If you disable this policy setting, on-demand file access is disabled, and enough storage space to store all the user’s files is required on each of their PCs.
-If you specify User choice or do not configure this policy setting, the user decides whether to enable on-demand file access. However, if the Force automatic setup policy setting is enabled, Work Folders is set up automatically with on-demand file access enabled.
-
-The "Force automatic setup" option specifies that Work Folders should be set up automatically without prompting users. This prevents users from choosing not to use Work Folders on the computer; it also prevents them from manually specifying the local folder in which Work Folders stores files. By default, Work Folders is stored in the "%USERPROFILE%\Work Folders" folder. If this option is not specified, users must use the Work Folders Control Panel item on their computers to set up Work Folders.
-
- Enables the use of Token Broker for AD FS authentication
- This policy specifies whether Work Folders should use Token Broker for interactive AD FS authentication instead of its own OAuth2 token flow used in previous versions.
- Enable (recommended)
- Disable
- User choice
-
-
-
-
-
-
-
-
-
-
-
- On-demand file access preference:
-
- Force automatic setup
-
-
-
-
diff --git a/policy_templates/en-US/WorkplaceJoin.adml b/policy_templates/en-US/WorkplaceJoin.adml
deleted file mode 100644
index 448cd36..0000000
--- a/policy_templates/en-US/WorkplaceJoin.adml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Register domain joined computers as devices
- This setting lets you configure how domain joined computers become registered as devices.
-
-
- Device Registration
- This setting lets you configure how domain joined computers become registered as devices.
-
-When you enable this setting, domain joined computers automatically and silently get registered as devices with Azure Active Directory.
-
-Note: Additional requirements may apply on certain Windows SKUs. Refer to Azure Active Directory Device Registration Overview.
-
-http://go.microsoft.com/fwlink/?LinkId=307136
-
- Register domain joined computers as devices
-
-
-
diff --git a/policy_templates/en-US/access16.adml b/policy_templates/en-US/access16.adml
deleted file mode 100644
index ef39172..0000000
Binary files a/policy_templates/en-US/access16.adml and /dev/null differ
diff --git a/policy_templates/en-US/appv.adml b/policy_templates/en-US/appv.adml
deleted file mode 100644
index e0807d2..0000000
--- a/policy_templates/en-US/appv.adml
+++ /dev/null
@@ -1,287 +0,0 @@
-
-
-
-
-
-
-
- App-V
- Contains settings for Microsoft App-V.
- Streaming
- Publishing
- Reporting
- Publishing Server 1 Settings
- Publishing Server 2 Settings
- Publishing Server 3 Settings
- Publishing Server 4 Settings
- Publishing Server 5 Settings
- Client Coexistence
- Scripting
- Integration
- CEIP
- Virtualization
- PackageManagement
- PowerManagement
- True
- False
- Hour
- Day
- Package Installation Root
- Specifies directory where all new applications and updates will be installed.
- Specify what to load in background (aka AutoLoad)
- Specifies how new packages should be loaded automatically by App-V on a specific computer.
- Autoload Options
- None
- Previously Used
- All
- Package Source Root
- Overrides source location for downloading package content.
- Reestablishment Retries
- Specifies the number of times to retry a dropped session.
- Reestablishment Interval
- Specifies the number of seconds between attempts to reestablish a dropped session.
- Location Provider
- Specifies the CLSID for a compatible implementation of the IAppvPackageLocationProvider interface.
- Certificate Filter For Client SSL
- Specifies the path to a valid certificate in the certificate store.
- Verify certificate revocation list
- Verifies Server certificate revocation status before streaming using HTTPS.
- Shared Content Store (SCS) mode
- Specifies that streamed package contents will be not be saved to the local hard disk.
- Allow First Time Application Launches if on a High Cost Windows 8 Metered Connection
- This setting controls whether virtualized applications are launched on Windows 8 machines connected via a metered network connection (e.g. 4G).
- Require Publish As Admin
- Requires admin privileges to publish and unpublish packages and connection groups.
- Enable Support for BranchCache
- If enabled, the App-V client will support BrancheCache compatible HTTP streaming. If BranchCache support is not desired, this should be disabled. The client can then apply HTTP optimizations which are incompatible with BranchCache
- Enable Migration Mode
- Migration mode allows the App-V client to modify shortcuts and FTA's for packages created using a previous version of App-V.
- Enable Package Scripts
- Enables scripts defined in the package manifest of configuration files that should run.
- Roaming File Exclusions
- Specifies the file paths relative to %userprofile% that do not roam with a user's profile. Example usage: /FILEEXCLUSIONLIST='desktop;my pictures'.
- Roaming Registry Exclusions
- Specifies the registry paths that do not roam with a user profile. Example usage: /REGISTRYEXCLUSIONLIST=software\classes;software\clients.
- Integration Root User
- Specifies the location where symbolic links are created to the current version of a per-user published package. Shortcuts, file type associations, etc. are created pointing to this path. If empty, symbolic links are not used during publishing. Example: %localappdata%\Microsoft\AppV\Client\Integration.
- Integration Root Global
- Specifies the location where symbolic links are created to the current version of a globally published package. Shortcuts, file type associations, etc. are created pointing to this path. If empty, symbolic links are not used during publishing. Example: %allusersprofile%\Microsoft\AppV\Client\Integration.
- Reporting Server
- Reporting Server URL: Displays the URL of reporting server.
-
- Reporting Time: When the client data should be reported to the server. Acceptable range is 0~23, corresponding to the 24 hours in a day. A good practice is, don't set this time to a busy hour, e.g. 9AM.
-
- Delay reporting for the random minutes: The maximum minutes of random delay on top of the reporting time. For a busy system, the random delay will help reduce the server load.
-
- Repeat reporting for every (days): The periodical interval in days for sending the reporting data.
-
- Data Cache Limit: This value specifies the maximum size in megabytes (MB) of the XML cache for storing reporting information. The default value is 20 MB. The size applies to the cache in memory. When the limit is reached, the log file will roll over. When a new record is to be added (bottom of the list), one or more of the oldest records (top of the list) will be deleted to make room. A warning will be logged to the Client log and the event log the first time this occurs, and will not be logged again until after the cache has been successfully cleared on transmission and the log has filled up again.
-
- Data Block Size: This value specifies the maximum size in bytes to transmit to the server at once on a reporting upload, to avoid permanent transmission failures when the log has reached a significant size. The default value is 65536. When transmitting report data to the server, one block at a time of application records that is less than or equal to the block size in bytes of XML data will be removed from the cache and sent to the server. Each block will have the general Client data and global package list data prepended, and these will not factor into the block size calculations; the potential exists for an extremely large package list to result in transmission failures over low bandwidth or unreliable connections.
-
- Publishing Server Display Name: Displays the name of publishing server.
-
- Publishing Server URL: Displays the URL of publishing server.
-
- Global Publishing Refresh: Enables global publishing refresh (Boolean).
-
- Global Publishing Refresh On Logon: Triggers a global publishing refresh on logon (Boolean).
-
- Global Publishing Refresh Interval: Specifies the publishing refresh interval using the GlobalRefreshIntervalUnit. To disable package refresh, select 0.
-
- Global Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, Day 0-31).
-
- User Publishing Refresh: Enables user publishing refresh (Boolean).
-
- User Publishing Refresh On Logon: Triggers a user publishing refresh on logon (Boolean).
-
- User Publishing Refresh Interval: Specifies the publishing refresh interval using the UserRefreshIntervalUnit. To disable package refresh, select 0.
-
- User Publishing Refresh Interval Unit: Specifies the interval unit (Hour 0-23, Day 0-31).
-
- Microsoft Customer Experience Improvement Program (CEIP)
- The program collects information about computer hardware and how you use Microsoft Application Virtualization without interrupting you. This helps Microsoft identify which Microsoft Application Virtualization features to improve. No information collected is used to identify or contact you.
-
-For more details, read about the program online at http://go.microsoft.com/fwlink/?LinkID=184686.
- Virtual Component Process Allow List
- Specifies a list of process paths (may contain wildcards) which are candidates for using virtual components (shell extensions, browser helper objects, etc). Only processes whose full path matches one of these items can use virtual components.
- Enable Dynamic Virtualization
- Enables Dynamic Virtualization of supported shell extensions, browser helper objects, and ActiveX controls.
- Enable automatic cleanup of unused appv packages
- Enables automatic cleanup of appv packages that were added after Windows10 anniversary release.
- Enable background sync to server when on battery power
- Enables background sync to server when on battery power.
- Enable Publishing Refresh UX
- Enables a UX to display to the user when a publishing refresh is performed on the client.
- Enable App-V Client
- This policy setting allows you to enable or disable Microsoft Application Virtualization (App-V) feature. Reboot is needed for disable to take effect.
-
-
-
-
-
- Autoload Options
-
-
-
-
-
-
-
-
-
- %programdata%\App-V
-
-
-
-
- Reestablishment Retries:
-
-
-
- Reestablishment Interval:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Reporting Time
- Delay reporting for the random minutes
- Repeat reporting for every (days)
- Data Cache Limit
- Data Block Size
-
-
-
-
-
-
- Server 1
-
-
-
-
- Global Publishing Refresh
- Global Publishing Refresh On Logon
- Global Publishing Refresh Interval
- Global Publishing Refresh Interval Unit
- User Publishing Refresh
- User Publishing Refresh On Logon
- User Publishing Refresh Interval
- User Publishing Refresh Interval Unit
-
-
-
-
-
- Server 2
-
-
-
-
- Global Publishing Refresh
- Global Publishing Refresh On Logon
- Global Publishing Refresh Interval
- Global Publishing Refresh Interval Unit
- User Publishing Refresh
- User Publishing Refresh On Logon
- User Publishing Refresh Interval
- User Publishing Refresh Interval Unit
-
-
-
-
-
- Server 3
-
-
-
-
- Global Publishing Refresh
- Global Publishing Refresh On Logon
- Global Publishing Refresh Interval
- Global Publishing Refresh Interval Unit
- User Publishing Refresh
- User Publishing Refresh On Logon
- User Publishing Refresh Interval
- User Publishing Refresh Interval Unit
-
-
-
-
-
- Server 4
-
-
-
-
- Global Publishing Refresh
- Global Publishing Refresh On Logon
- Global Publishing Refresh Interval
- Global Publishing Refresh Interval Unit
- User Publishing Refresh
- User Publishing Refresh On Logon
- User Publishing Refresh Interval
- User Publishing Refresh Interval Unit
-
-
-
-
-
- Server 5
-
-
-
-
- Global Publishing Refresh
- Global Publishing Refresh On Logon
- Global Publishing Refresh Interval
- Global Publishing Refresh Interval Unit
- User Publishing Refresh
- User Publishing Refresh On Logon
- User Publishing Refresh Interval
- User Publishing Refresh Interval Unit
-
-
-
-
-
-
-
-
-
-
- Software\Classes
-
-
-
-
-
- %localappdata%\Microsoft\AppV\Client\Integration
-
-
-
-
-
- %allusersprofile%\Microsoft\AppV\Client\Integration
-
-
-
-
-
-
-
-
-
diff --git a/policy_templates/en-US/chrome.adml b/policy_templates/en-US/chrome.adml
deleted file mode 100644
index 51e8409..0000000
Binary files a/policy_templates/en-US/chrome.adml and /dev/null differ
diff --git a/policy_templates/en-US/excel16.adml b/policy_templates/en-US/excel16.adml
deleted file mode 100644
index 7825d03..0000000
Binary files a/policy_templates/en-US/excel16.adml and /dev/null differ
diff --git a/policy_templates/en-US/feeds.adml b/policy_templates/en-US/feeds.adml
deleted file mode 100644
index 057c07c..0000000
--- a/policy_templates/en-US/feeds.adml
+++ /dev/null
@@ -1,13 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- News and interests
- Enable news and interests on the taskbar
- This policy setting specifies whether news and interests is allowed on the device.
-
-
-
diff --git a/policy_templates/en-US/firefox.adml b/policy_templates/en-US/firefox.adml
deleted file mode 100644
index 941473d..0000000
--- a/policy_templates/en-US/firefox.adml
+++ /dev/null
@@ -1,1425 +0,0 @@
-
-
-
-
-
-
- Microsoft Windows XP SP2 or later
- No longer supported.
- Firefox 60 or later, Firefox 60 ESR or later
- Firefox 62 or later, Firefox 60.2 ESR or later
- Firefox 63 or later
- Firefox 64 or later, Firefox 60.4 ESR or later
- Firefox 66 or later, Firefox 60.6 ESR or later
- Firefox 67 or later, Firefox 60.7 ESR or later
- Firefox 68 or later, Firefox 68 ESR or later
- Firefox 68.0.1 or later, Firefox 68.0.1 ESR or later
- Firefox 60 ESR or later
- Firefox 68.5 ESR or later
- Firefox 69 or later, Firefox 68.1 ESR or later
- Firefox 70 or later, Firefox 68.2 ESR or later
- Firefox 71 or later, Firefox 68.3 ESR or later
- Firefox 72 or later, Firefox 68.4 ESR or later
- Firefox 73 or later, Firefox 68.5 ESR or later
- Firefox 74 or later, Firefox 68.6 ESR or later
- Firefox 75 or later, Firefox 68.7 ESR or later
- Firefox 75 or later
- Firefox 76 or later, Firefox 68.8 ESR or later
- Firefox 76 or later
- Firefox 77 or later, Firefox 68.9 ESR or later
- Firefox 77 or later
- Firefox 78 or later
- Firefox 79 or later, Firefox 78.1 ESR or later
- Firefox 80 or later, Firefox 78.2 ESR or later
- Firefox 81 or later, Firefox 78.3 ESR or later
- Firefox 82 or later, Firefox 78.4 ESR or later
- Firefox 83 or later, Firefox 78.5 ESR or later
- Firefox 84 or later, Firefox 78.6 ESR or later
- Firefox 85 or later, Firefox 78.7 ESR or later
- Firefox 86 or later, Firefox 78.8 ESR or later
- Firefox 88 or later, Firefox 78.10 ESR or later
- Firefox 89 or later, Firefox 78.11 ESR or later
- Firefox 90 or later, Firefox 78.12 ESR or later
- Firefox 91 or later
- Firefox 95 or later, Firefox 91.4 ESR or later
- Firefox 96 or later, Firefox 91.5 ESR or later
- Firefox 96 or later
- Firefox 97 or later, Firefox 91.6 ESR or later
- Firefox 98 or later
- Firefox 99 or later, Firefox 91.8 ESR or later
- Firefox 100 or later, Firefox 91.9 ESR or later
- Firefox 101 or later, Firefox 91.10 ESR or later
- Firefox 102 or later
- Firefox 104 or later, Firefox 102.2 ESR or later
- Firefox 105 or later, Firefox 102.3 ESR or later
- Firefox 106 or later, Firefox 102.4 ESR or later
- Firefox 107 or later, Firefox 102.5 ESR or later
- Firefox 108 or later, Firefox 102.6 ESR or later
- Firefox 109 or later, Firefox 102.7 ESR or later
- Firefox 110 or later, Firefox 102.8 ESR or later
- Firefox 112 or later
- Firefox 113 or later
- Firefox 114 or later, Firefox 102.12 ESR or later
- Firefox 118 or later, Firefox 115.3 ESR or later
- Firefox
- Permissions
- Camera
- Microphone
- Location
- Notifications
- Autoplay
- Virtual Reality
- Authentication
- Bookmarks
- Certificates
- Popups
- Cookies
- Addons
- Extensions
- Flash
- Home page
- Search
- Preferences (Deprecated)
- User Messaging
- Disabled Ciphers
- Encrypted Media Extensions
- PDF.js
- Picture-in-Picture
- Proxy Settings
- Security Devices
- Firefox Suggest (US only)
- Allowed Sites
- Allowed Sites (Session Only)
- Blocked Sites
- Application Autoupdate
- If this policy is enabled, Firefox is automatically updated without user approval.
-
-If this policy is disabled, Firefox updates are downloaded but the user can choose when to install the update.
-
-If this policy is not configured, the user can choose whether not Firefox is automatically updated.
- Custom Update URL
- If this policy is enabled, you can set a URL to an update server other than the default. This could be helpful if you run your own update server on your network.
-
-If this policy is disabled or not configured, the default update URL is used.
- SPNEGO
- If this policy is enabled, the specified websites are permitted to engage in SPNEGO authentication with the browser. Entries in the list are formatted as mydomain.com or https://myotherdomain.com.
-
-If this policy is disabled or not configured, no websites are permitted to engage in SPNEGO authentication with the browser.
-
-For more information, see https://developer.mozilla.org/en-US/docs/Mozilla/Integrated_authentication.
- Delegated
- If this policy is enabled, the browser may delegate user authorization to the server for the specified websites. Entries in the list are formatted as mydomain.com or https://myotherdomain.com.
-
-If this policy is disabled or not configured, the browser will not delegate user authorization to the server for any websites.
-
-For more information, see https://developer.mozilla.org/en-US/docs/Mozilla/Integrated_authentication.
- NTLM
- If this policy is enabled, the specified websites are trusted to use NTLM authentification. Entries in the list are formatted as mydomain.com or https://myotherdomain.com.
-
-If this policy is disabled or not configured, no websites are trusted to use NTLM authentification.
-
-For more information, see https://developer.mozilla.org/en-US/docs/Mozilla/Integrated_authentication.
- Allow Non FQDN
- If this policy is enabled (and the checkboxes are checked), you can always allow SPNEGO or NTLM on non FQDNs (fully qualified domain names).
-
-If this policy is disabled or not configured, NTLM and SPNEGO are not enabled on non FQDNs.
- Allow Proxies
- If this policy is disabled, SPNEGO and NTLM will not authenticate with proxy servers.
-
-If this policy is enabled (and the checkboxes are checked) or not configured, NTLM and SPNEGO will always authenticate with proxies.
- Do not allow authentication preferences to be changed
- If this policy is disabled, authentication preferences can be changed by the user.
-
-If this policy is enabled or not configured, authentication preferences cannot be changed by the user.
- Allow authentication in private browsing
- If this policy is enabled, integrated authentication is used in private browsing.
-
-If this policy is disabled or not configured, integrated authentication is not used in private browsing.
- Block Add-ons Manager
- If this policy is enabled, the user cannot access the Add-ons Manager or about:addons.
-
-If this policy is disabled or not configured, the user can access the Add-ons Manager and about:addons.
- Block about:config
- If this policy is enabled, the user cannot access about:config.
-
-If this policy is disabled or not configured, the user can access about:config.
- Block about:profiles
- If this policy is enabled, the user cannot access about:profiles.
-
-If this policy is disabled or not configured, the user can access about:profiles.
- Block Troubleshooting Information
- If this policy is enabled, the user cannot access Troubleshooting Information or about:support.
-
-If this policy is disabled or not configured, the user can access Troubleshooting Information and about:support.
- Disable Set Desktop Background
- If this policy is enabled, the user cannot set an image as their desktop background.
-
-If this policy is disabled or not configured, users can set images as their desktop background.
- Captive Portal
- If this policy is disabled, captive portal support is disabled.
-
-If this policy is enabled or not configured, captive portal support is enabled.
- Import Enterprise Roots
- If this policy is enabled, Firefox will read certificates from the Windows certificate store.
-
-If this policy is disabled or not configured, Firefox will not read certificates from the Windows certificate store.
- Install Certificates
- If this policy is enabled, Firefox will install the listed certificates into Firefox. It will look in %USERPROFILE%\AppData\Local\Mozilla\Certificates and %USERPROFILE%\AppData\Roaming\Mozilla\Certificates.
-
-If this policy is disabled or not configured, Firefox will not install additional certificates.
- Default Download Directory
- If this policy is enabled, you can set the default directory for downloads. ${home} can be used for the native home path.
-
-If this policy is disabled or not configured, the default Firefox download directory is used.
- Download Directory
- If this policy is enabled, you can set and lock the directory for downloads. ${home} can be used for the native home path.
-
-If this policy is disabled or not configured, the default Firefox download directory is used and the user can change it.
- DNS Over HTTPS
- Enabled
- If this policy is disabled, DNS over HTTPS is disabled.
-
-If this policy is enabled or not configured, DNS Over HTTPS is enabled.
- Provider URL
- If this policy is enabled, the URL specified is used as the provider URL.
-
-If this policy is disabled or not configured, the default provider is used.
-
- Locked
- If this policy is enabled, DNS over HTTPS settings cannot be changed by the user.
-
-If this policy is disabled or not configured, DNS over HTTPS settings can be changed by the user.
- Excluded Domains
- If this policy is enabled, the specified domains are excluded from DNS over HTTPS.
-
-If this policy is disabled or not configured, no domains are excluded from DNS over HTTPS.
- Configure DNS Over HTTPS (Moved)
- If this policy is enabled, the default configuration for DNS over HTTPS can be changed.
-
-If this policy is disabled or not configured, DNS Over HTTPS uses the default Firefox configuration.
- Disable Master Password Creation
- If this policy is enabled, users cannot create a master password.
-
-If this policy is disabled or not configured, users can create a master password.
- Disable Update
- If this policy is enabled, the browser does not receive updates.
-
-If this policy is disabled or not configured, the browser receives updates.
- Disable Built-in PDF Viewer (PDF.js)
- If this policy is enabled, PDF files are not viewed within Firefox.
-
-If this policy is disabled or not configured, PDF files are viewed within Firefox.
- Disable the default browser agent
- If this policy is enabled, the default browser agent is disabled.
-
-If this policy is disabled or not configured, the default browser agent is enabled.
-
-For more information about the default browser agent, see https://firefox-source-docs.mozilla.org/toolkit/mozapps/defaultagent/default-browser-agent/index.html
- Disable Developer Tools
- If this policy is enabled, web developer tools are not available within Firefox.
-
-If this policy is disabled or not configured, web developer tools are available within Firefox.
- Disable Feedback Commands
- If this policy is enabled, the "Submit Feedback" and "Report Deceptive Site" menuitems are not available from the help menu.
-
-If this policy is disabled or not configured, the "Submit Feedback" and "Report Deceptive Site" menuitems are available from the help menu.
- Disable Firefox Accounts
- If this policy is enabled, Firefox Accounts is disabled which includes disabling Sync.
-
-If this policy is disabled or not configured, Firefox Accounts and Sync are available.
- Disable Firefox Screenshots
- If this policy is enabled, Firefox Screenshots is not available.
-
-If this policy is disabled or not configured, Firefox Screenshots is available.
- Disable Firefox Studies
- If this policy is enabled, Firefox will never run SHIELD studies or do Heartbeat surveys.
-
-If this policy is disabled or not configured, the user can choose to enable SHIELD studies or Heartbeat surveys.
-
-For more information, see https://support.mozilla.org/en-US/kb/shield and https://wiki.mozilla.org/Firefox/Shield/Heartbeat
- Disable Forget Button
- If this policy is enabled, the "Forget" button is not available.
-
-If this policy is disabled or not configured, the "Forget" button is available.
- Disable Form History
- If this policy is enabled, Firefox will not remember form or search history.
-
-If this policy is disabled or not configured, Firefox will remember form and search history.
- Do not allow passwords to be revealed in saved logins
- If this policy is enabled, users cannot show passwords in saved logins.
-
-If this policy is disabled or not configured, users can show passwords in saved logins.
- Disable Pocket
- If this policy is enabled, Pocket is not available.
-
-If this policy is disabled or not configured, Pocket is available.
- Disable Private Browsing
- If this policy is enabled, private browsing is not allowed.
-
-If this policy is disabled or not configured, private browsing is allowed.
- Disable Profile Import
- If this policy is enabled, the "Import data from another browser" option is not available in the bookmarks window.
-
-If this policy is disabled or not configured, the "Import data from another browser" option is available.
- Disable Profile Refresh
- If this policy is enabled, the "Refresh Firefox" button is not available on the about:support page or on support.mozilla.org.
-
-If this policy is disabled or not configured, the "Refresh Firefox" button is available.
- Disable Safe Mode
- If this policy is enabled, the user cannot restart the browser into safe mode.
-
-If this policy is disabled or not configured, safe mode is allowed.
- Prevent overriding certificate errors
- If this policy is enabled, the "Add Exception" button is not available when a certificate is invalid. This prevents the user from overriding the certificate error.
-
-If this policy is disabled or not configured, certificate errors can be overridden.
- Prevent overriding safe browsing errors
- If this policy is enabled, a user cannot bypass the warning and visit a harmful site.
-
-If this policy is disabled or not configured, a user can choose to visit a harmful site.
- Disable System Addon Updates
- If this policy is enabled, new system add-ons will not be installed and existing system add-ons will not be updated.
-
-If this policy is disabled or not configured, system add-ons are installed and updated.
- Disable Telemetry
- If this policy is enabled, telemetry is not uploaded.
-
-If this policy is disabled or not configured, telemetry is collected and uploaded.
-
-Mozilla recommends that you do not disable telemetry. Information collected through telemetry helps us build a better product for businesses like yours.
- Display Bookmarks Toolbar (Deprecated)
- If this policy is enabled, the bookmarks toolbar is displayed by default. The user can still hide it.
-
-If this policy is disabled or not configured, the bookmarks toolbar is not displayed by default.
- Display Bookmarks Toolbar
- If this policy is enabled, the default bokmarks toolbar display can be configured.
-
-If this policy is disabled or not configured, the bookmarks toolbar is displayed on the new tab page by default.
- Always
- Never
- New Tab
- Display Menu Bar (Deprecated)
- If this policy is enabled, the menu bar is displayed by default. The user can still hide it.
-
-If this policy is disabled or not configured, the menu bar is not displayed by default.
- Display Menu Bar
- If this policy is enabled, you can choose whether or not the menu bar is displayed and whether or not the user can show and hide the menu bar.
-
-If this policy is disabled or not configured, the menu bar is not displayed by default.
- Always
- Never
- On by default
- Off by default
- Don't Check Default Browser
- If this policy is enabled, Firefox does not check to see if it is the default browser at startup.
-
-If this policy is disabled or not configured, Firefox checks to see if it is the default browser at startup.
- Extensions to Install
- If this policy is enabled, you can specify a list of extension URLs or paths that will be installed when Firefox is started.
-Anytime this list is changed, the extensions will be reinstalled.
-
-If this policy is disabled or not configured, no extensions are installed.
- Extensions to Uninstall
- If this policy is enabled, you can specify a list of extension IDs that will be uninstalled.
-Anytime this list is changed, the extensions will be uninstalled.
-
-If this policy is disabled or not configured, no extensions are uninstalled.
- Prevent extensions from being disabled or removed
- If this policy is enabled, you can specify a list of extension IDs that the user will be unable to uninstall or disable.
-
-If this policy is disabled or not configured, no extensions are locked
- Extension Update
- If this policy is disabled, extensions will not be updated automatically.
-
-If this policy is enabled or not configured, extensions will be updated automatically.
- Extension Management
- If this policy is enabled, you can use JSON to describe the extension management policy.
-
-If this policy is disabled or not configured, extensions will not be managed.
-
-For detailed information on creating the policy, see https://github.com/mozilla/policy-templates/blob/master/README.md#extensionsettings.
- Extension Management (JSON on one line)
- Hardware Acceleration
- If this policy is disabled, hardware acceleration is disabled and cannot be enabled.
-
-If this policy is enabled or not configured, hardware acceleration is enabled.
- Legacy Profiles
- If this policy is enabled, Firefox will not try to create different profiles for installations of Firefox in different directories. This is the equivalent of the MOZ_LEGACY_PROFILES environment variable.
-
-If this policy is disabled or not configured, Firefox will create a new profile for each unique installation of Firefox.
- Revert to legacy SameSite behavior
- If this policy is enabled, Firefox will revert to the legacy behavior of SameSite. This means that cookies that don't explicitly specify a SameSite attribute are treated as if they were SameSite=None.
-
-If this policy is disabled or not configured, Firefox will enforce SameSite=lax.
- Revert to legacy SameSite behavior on specific domains
- If this policy is enabled, Firefox will revert to the legacy behavior of SameSite for the specified domains. This means that cookies that don't explicitly specify a SameSite attribute are treated as if they were SameSite=None.
-
-If this policy is disabled or not configured, Firefox will enforce SameSite=lax for all domains.
- Local File Links
- If this policy is enabled, you can specify origins where linking to local files is allowed.
-
-If this policy is disabled or not configured, websites can't link to local files.
- Network Prediction
- If this policy is disabled, network prediction (DNS prefetching) will be disabled.
-
-If this policy is enabled or not configured, network prediction (DNS prefetching) will be enabled.
- New Tab Page
- If this policy is disabled, the new tab page will be blank.
-
-If this policy is enabled or not configured, the new tab page will be the default.
- Offer to save logins
- If this policy is enabled or not configured, Firefox will offer to save website logins and passwords.
-
-If this policy is disabled, Firefox will not offer to save website logins and passwords.
- Offer to save logins (default)
- If this policy is enabled or not configured, Firefox will offer to save website logins and passwords.
-
-If this policy is disabled, Firefox will not offer to save website logins and passwords.
-
-In either case, the user will be able to change the value (it is not locked).
- If this policy is enabled, pop-up windows are always allowed for the origins indicated. If a top level domain is specified (http://example.org), pop-up windows are allowed for all subdomains as well.
-
-If this policy is disabled or not configured, the default pop-up policy is followed.
- Block pop-ups from websites
- If this policy is disabled, pop-up windows are allowed from websites by default.
-
-If this policy is not configured or enabled, popups are not allowed from websites.
- Do not allow preferences to be changed
- If this policy is enabled, pop-up preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change their pop-up preferences.
- If this policy is enabled, add-ons are always allowed for the origins indicated unless add-on install is disabled. If a top level domain is specified (http://example.org), add-ons are allowed for all subdomains as well.
-
-If this policy is disabled or not configured, the default add-on policy is followed.
- Allow add-on installs from websites
- If this policy is disabled, add-ons cannot be installed.
-
-If this policy is not configured or enabled, add-ons can be installed.
- If this policy is enabled, cookies are always allowed for the origins indicated. If a top level domain is specified (http://example.org), cookies are allowed for all subdomains as well.
-
-If this policy is disabled or not configured, the default cookie policy is followed.
- If this policy is enabled, cookies are allowed for the origins indicated, but removed at the end of the session. If a top level domain is specified (http://example.org), cookies are allowed for all subdomains as well.
-
-If this policy is disabled or not configured, the default cookie policy is followed.
- If this policy is enabled, cookies are blocked for the origins indicated. If a top level domain is specified (http://example.org), cookies are blocked from all subdomains as well.
-
-If this policy is disabled or not configured, cookies are not blocked by default.
- Accept cookies from websites (Deprecated)
- If this policy is disabled, cookies are not accepted from websites by default.
-
-If this policy is not configured or enabled, cookies are accepted from websites.
- Accept third-party cookies (Deprecated)
- If this policy is enabled and cookies are allowed, you can set when to accept third-party cookies.
-
-This setting is ignored if this policy is disabled or not configured or if cookies are not allowed.
- Always
- Never
- From visited
- Keep cookies until Firefox is closed
- If this policy is enabled and cookies are allowed, they will expire when Firefox is closed.
-
-This setting is ignored if this policy is disabled or not configured or if cookies are not allowed.
- Reject trackers (Deprecated)
- If this policy is enabled and cookies are allowed, Firefox will reject tracker cookies by default.
-
-This setting is ignored if this policy is disabled or not configured or if cookies are not allowed.
- Do not allow preferences to be changed
- If this policy is enabled, cookie preferences cannot be changed by the user.
- Cookie Behavior
- If this policy is enabled, you can configure cookie behavior.
-
-If this policy is not configured or disabled, cookies are rejected for known trackers.
- Cookie Behavior in private browsing
- If this policy is enabled, you can configure cookie behavior in private browsing.
-
-If this policy is not configured or disabled, in private browsing, cookies are rejected for known trackers and third-party cookies are partitioned.
- Accept all cookies
- Reject third party cookies
- Reject all cookies
- Reject third party cookies for sites you haven't visited
- Reject cookies for known trackers
- Reject cookies for known trackers and partition third-party cookies (Total Cookie Protection)
- If this policy is enabled, access to the camera is always allowed for the origins indicated.
-
-If this policy is disabled or not configured, the default camera policy is followed.
- If this policy is enabled, access to the camera is blocked for the origins indicated.
-
-If this policy is disabled or not configured, access to the camera is not blocked by default.
- Block new requests asking to access the camera
- If this policy is enabled, sites that are not in the Allow policy will not be allowed to ask permission to access the camera.
-
-If this policy is disabled or not configured, any site that is not in the Block policy can ask permission to access the camera.
- Do not allow preferences to be changed
- If this policy is enabled, camera preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change their camera preferences.
- If this policy is enabled, access to the microphone is always allowed for the origins indicated.
-
-If this policy is disabled or not configured, the default microphone policy is followed.
- If this policy is enabled, access to the microphone is blocked for the origins indicated.
-
-If this policy is disabled or not configured, access to the microphone is not blocked by default.
- Block new requests asking to access the microphone
- If this policy is enabled, sites that are not in the Allow policy will not be allowed to ask permission to access the microphone.
-
-If this policy is disabled or not configured, any site that is not in the Block policy can ask permission to access the microphone.
- Do not allow preferences to be changed
- If this policy is enabled, microphone preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change their camera preferences.
- If this policy is enabled, access to location is always allowed for the origins indicated.
-
-If this policy is disabled or not configured, the default location policy is followed.
- If this policy is enabled, access to location is blocked for the origins indicated.
-
-If this policy is disabled or not configured, access to location is not blocked by default.
- Block new requests asking to access location
- If this policy is enabled, sites that are not in the Allow policy will not be allowed to ask permission to access location.
-
-If this policy is disabled or not configured, any site that is not in the Block policy can ask permission to access location.
- Do not allow preferences to be changed
- If this policy is enabled, location preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change location preferences.
- If this policy is enabled, notifications can always be sent for the origins indicated.
-
-If this policy is disabled or not configured, the default notification policy is followed.
- If this policy is enabled, notifications are always blocked for the origins indicated.
-
-If this policy is disabled or not configured, notifications are not blocked by default.
- Block new requests asking to send notifications
- If this policy is enabled, sites that are not in the Allow policy will not be allowed to ask permission to send notifications.
-
-If this policy is disabled or not configured, any site that is not in the Block policy can ask permission to send notifications.
- Do not allow preferences to be changed
- If this policy is enabled, notification preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change their notification preferences.
- If this policy is enabled, autoplay is always enabled for the origins indicated.
-
-If this policy is disabled or not configured, the default autoplay policy is followed.
- If this policy is enabled, autoplay is always blocked for the origins indicated.
-
-If this policy is disabled or not configured, the default autoplay policy is followed.
- Default autoplay level
- If this policy is enabled, you can choose the default autoplay level.
-
-If this policy is disabled or not configured, audio is blocked by default.
-
-Note: Blocking audio and video does not work on the ESR.
- Do not allow preferences to be changed
- If this policy is enabled, autoplay preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change autoplay preferences.
- Allow Audio and Video
- Block Audio
- Block Audio and Video
- If this policy is enabled, access to virtual reality devices is always allowed for the origins indicated.
-
-If this policy is disabled or not configured, the default virtual reality policy is followed.
- If this policy is enabled, access to virtual reality devices is blocked for the origins indicated.
-
-If this policy is disabled or not configured, access to virtual reality devices is not blocked by default.
- Block new requests asking to access virtual reality devices.
- If this policy is enabled, sites that are not in the Allow policy will not be allowed to ask permission to access virtual reality devices.
-
-If this policy is disabled or not configured, any site that is not in the Block policy can ask permission to virtual reality devices.
- Do not allow preferences to be changed
- If this policy is enabled, virtual reality preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change their virtual reality preferences.
- Customize Firefox Home
- If this policy is enabled, you can choose the sections displayed on Firefox Home and prevent the user from changing them.
-
-If this policy is disabled or not configured, the default sections are displayed and the user can change them.
- If this policy is enabled, Flash is activated by default for the origins indicated unless Flash is completely disabled. If a top level domain is specified (http://example.org), Flash is allowed for all subdomains as well.
-
-If this policy is disabled or not configured, the default Flash policy is followed.
- If this policy is enabled, Flash is blocked for the origins indicated. If a top level domain is specified (http://example.org), Flash is blocked from all subdomains as well.
-
-If this policy is disabled or not configured, the default Flash policy is followed.
- Activate Flash on websites
- If this policy is enabled, Flash is always activated on websites.
-
-If this policy is disabled, Flash is never activated on websites, even if they are in the specified in the Allow list.
-
-If this policy is not configured, Flash is click to play.
- Do not allow preferences to be changed
- If this policy is enabled, Flash preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change their Flash preferences.
- Override the first run page
- If this policy is enabled, you can specify a URL to be used as the first run page. If you leave the URL blank, no first run page will be shown.
-
-Starting with Firefox 83, Firefox ESR 78.5, you can also specify multiple URLS separated by a vertical bar (|).
-
-If this policy is disabled or not configured, the first run page is displayed.
- Override the upgrade page
- If this policy is enabled, you can specify a URL to be displayed after Firefox is updated. If you leave the URL blank, no upgrade page will be shown.
-
-If this policy is disabled or not configured, the upgrade is displayed.
- Clear data when browser is closed (Moved)
- If this policy is enabled, you can choose data to be cleared when Firefox is closed.
-
-If this policy is disabled or not configured, data is not cleared when the browser is closed.
- Clear data when browser is closed
-
- Cache
- If the policy is enabled, the cache is cleared when the browser is closed.
-
-If this policy is disabled or not configured, the cache is not cleared when the browser is closed.
- Cookies
- If the policy is enabled, cookies are cleared when the browser is closed.
-
-If this policy is disabled or not configured, cookies are not cleared when the browser is closed.
- Download History
- If the policy is enabled, download history is cleared when the browser is closed.
-
-If this policy is disabled or not configured, download history is not cleared when the browser is closed.
- Form & Search History
- If the policy is enabled, form data is cleared when the browser is closed.
-
-If this policy is disabled or not configured, form data is not cleared when the browser is closed.
- Browsing History
- If the policy is enabled, browsing history is cleared when the browser is closed.
-
-If this policy is disabled or not configured, browsing history is not cleared when the browser is closed.
- Active Logins
- If the policy is enabled, sessions cleared when the browser is closed.
-
-If this policy is disabled or not configured, sessions not cleared when the browser is closed.
- Site Preferences
- If the policy is enabled, site preferences are cleared when the browser is closed.
-
-If this policy is disabled or not configured, site preferences are not cleared when the browser is closed.
- Offline Website Data
- If the policy is enabled, offline application storage is cleared when the browser is closed.
-
-If this policy is disabled or not configured, offline application storage is not cleared when the browser is closed.
- Locked
- If this policy is disabled, all shutdown preferences can be changed by the user.
-
-If this policy is enabled, any shutdown preferences explicitly set via policy cannot be changed by the user.
-
-If this policy is not configured, no shutdown preferences can be changed by the user (previous behavior).
- Blocked websites
- If this policy is enabled, you can specify match patterns that indicate sites to be blocked. The match patterns are documented at https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Match_patterns. There is a 1000 entry limit.
-
-If this policy is disabled or not configured, no websites are blocked.
- Exceptions to blocked websites
- If this policy is enabled, and the website filter is enabled, you can specify match patterns for sites you do not want to block. The match patterns are documented at https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Match_patterns. There is a 1000 entry limit.
-
-If this policy is disabled or not configured, there are no exceptions to the website filter.
- Website Filter (JSON on one line)
- Website Filter (JSON)
- If this policy is enabled, you can specify blocked sites and exceptions via JSON.
-
-If this policy is disabled or not configured, websites are not filtered.
- Bookmark 01
- Bookmark 02
- Bookmark 03
- Bookmark 04
- Bookmark 05
- Bookmark 06
- Bookmark 07
- Bookmark 08
- Bookmark 09
- Bookmark 10
- Bookmark 11
- Bookmark 12
- Bookmark 13
- Bookmark 14
- Bookmark 15
- Bookmark 16
- Bookmark 17
- Bookmark 18
- Bookmark 19
- Bookmark 20
- Bookmark 21
- Bookmark 22
- Bookmark 23
- Bookmark 24
- Bookmark 25
- Bookmark 26
- Bookmark 27
- Bookmark 28
- Bookmark 29
- Bookmark 30
- Bookmark 31
- Bookmark 32
- Bookmark 33
- Bookmark 34
- Bookmark 35
- Bookmark 36
- Bookmark 37
- Bookmark 38
- Bookmark 39
- Bookmark 40
- Bookmark 41
- Bookmark 42
- Bookmark 43
- Bookmark 44
- Bookmark 45
- Bookmark 46
- Bookmark 47
- Bookmark 48
- Bookmark 49
- Bookmark 50
- If this policy is enabled, you can configure a bookmark be added to Firefox. Due to a bug, you must select the location. Note that you must specify the bookmarks in order.
-
-If this policy is disabled or not configured, a new bookmark is not added.
- Toolbar
- Menu
- No Default Bookmarks
- If this policy is enabled, the default bookmarks and Smart Bookmarks (Most Visited, Recent Tags) are not created.
-
-If this policy is disabled or not configured, default bookmarks and Smart Bookmarks (Most Visited, Recent Tags) are created.
-
-Note: this policy is only effective if used before the first run of the profile.
- URL for Home page
- If this policy is enabled, you can set a default home page. You can also lock the home page.
-
-If this policy is disabled or not configured, the user can set and change the home page.
- Additional Homepages
- If this policy is enabled, you can have additional home pages. They are opened in multiple tabs.
-
-If this policy is disabled or not configured, there is only one home page.
- Start Page
- If this policy is enabled, you can change what is displayed when Firefox starts. It can be the homepage, the previous session, or a blank page.
-
-If this policy is disabled or not configured, the start page defaults to the previous session.
- None
- Homepage
- Previous Session
- Homepage (Locked)
- Show Home button on toolbar
- If this policy is enabled, the home button will appear on the toolbar by default.
-
-If this policy is disabled, the home button will not appear on the toolbar by default.
-
-If this policy is not configured, Firefox will determine whether or not the home button appears on the toolbar by default.
- Password Manager
- If this policy is disabled, the password manager is not available via preferences.
-
-If this policy is enabled or not configured, the password manager is available via preferences.
- Password Manager Exceptions
- If this policy is enabled, you can specify sites where Firefox won't offer to save passwords.
-
-If this policy is disabled or not configured, Firefox will offer to save passwords on all sites.
- Prompt for download location
- If this policy is disabled, the user is not prompted for a download location.
-
-If this policy is enabled, the user is always prompted for a download location.
-
-If this policy is not configured, the user is prompted for a download location, but can change the default.
- Proxy Settings (Moved)
- If this policy is enabled, you can configure and lock network settings.
-
-Select the connection type and then fill in the appropriate sections. Due to a bug, you must select a value for the SOCKS proxy version.
-
-If this policy is disabled or not configured, the default network settings are used and user can change them.
- SOCKS v4
- SOCKS v5
- Automatic proxy configuration URL
- These should only be set if you selected autoConfig
- Proxy bypass URLs
- These should only be set if you selected manual proxy
- Connection Type
- No Proxy
- Use system proxy settings
- Manual proxy configuration
- Auto-detect proxy settings
- Automatic proxy configuration
- Tracking Protection (Moved)
- If this policy is not configured, tracking protection is not enabled by default in the browser but it is enabled by default in private browsing and the user can change it.
-
-If this policy is disabled, tracking protection is disabled and locked in both the browser and private browsing.
-
-If this policy is enabled, private browsing is enabled by default in both the browser and private browsing and you can choose whether or not to prevent the user from changing it.
- Tracking Protection
- Enabled
- If this policy is enabled, tracking protection is enabled.
-
-If this policy is disabled, tracking protection is disabled and cannot be changed by the user.
-
-If this policy is not configured, standard tracking protection is used and the user can change it.
- Cryptomining
- If this policy is enabled, scripts that use cryptomining are blocked.
-
-If this policy is disabled or not configured, scripts that use cryptomining are not blocked.
- Fingerprinting
- If this policy is enabled, scripts that use fingerprinting are blocked.
-
-If this policy is disabled or not configured, scripts that use fingerprinting are not blocked.
- Exceptions
- If this policy is enabled, you can specify origins where tracking protection is not enabled.
-
-If this policy is disabled or not configured, tracking protection is enabled for all websites.
- Do not allow tracking protection preferences to be changed
- If this policy is enabled, tracking protection preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change tracking protection preferences.
- Email Tracking
- If this policy is enabled, hidden email tracking pixels and scripts on websites are blocked.
-
-If this policy is disabled or not configured, hidden email tracking pixels and scripts on websites are not blocked.
- Requested locale
- Requested locale (string)
- If this policy is enabled, you can specify a list of requested locales for the application in order of preference. It will cause the corresponding language pack to become active.
-
-If this policy is disabled or not configured, the application will use the default locale.
- Security Devices
- If this policy is enabled, you can specify a list of PKCS #11 modules to be installed. Modules are specified as a name and a fully qualified path.
-
-If this policy is disabled or not configured, no additional PKCS #11 modules will be installed.
- Add
- Delete
- If this policy is enabled, you can specify the names of PKCS #11 modules to be deleted.
-
-If this policy is disabled or not configured, no PKCS #11 modules will be deleted.
- Search bar location
- If this policy is enabled, you can set whether the search bar is separate from the URL bar.
-
-If this policy is disabled or not configured, new users get a unified search bar, users upgrading from Firefox 56 and below get a separate search bar.
- Search Engine One
- Search Engine Two
- Search Engine Three
- Search Engine Four
- Search Engine Five
- If this policy is enabled, you can configure a search engine to be added to Firefox. Use {searchTerms} to indicate where the search term is placed. Due to a bug, you must select the method (usually GET). Note that you must specify the search engines in order.
-
-If this policy is disabled or not configured, a new search engine is not added.
- Unified
- Separate
- GET
- POST
- Default Search Engine
- If this policy is enabled, you can set the name of a search engine to be used as the default.
-
-If this policy is disabled or not configured, the Firefox default engine is used.
- Prevent Search Engine Installs
- If this policy is enabled, the user cannot install search engines from web page.
-
-If this policy is disabled or not configured, search engines can be installed from web pages.
- Remove Search Engines
- If this policy is enabled, you can specify the names of engines to be removed or hidden.
-
-If this policy is disabled or not configured, search engines will not be removed or hidden.
- Search Suggestions
- If this policy is disabled, search suggestions will be disabled.
-
-If this policy is enabled, search suggestions will be enabled.
-
-If this policy is not configured, search suggestions will be enabled, but the user can turn them off.
- Minimum SSL version enabled
- If this policy is enabled, Firefox will not use SSL/TLS versions less than the value specified.
-
-If this policy is disabled or not configured, Firefox defaults to a minimum of TLS 1.2.
- Maximum SSL version enabled
- If this policy is enabled, Firefox will not use SSL/TLS versions greater than the value specified.
-
-If this policy is disabled or not configured, Firefox defaults to a maximum of TLS 1.3.
- TLS 1.0
- TLS 1.1
- TLS 1.2
- TLS 1.3
- Support Menu
- If this policy is enabled, a new menuitem is added to the help menu with support information.
-
-If this policy is disabled or not configured, no menuitem is added.
- What's New
- If this policy is disabled, the What's new icon and menuitem will not be displayed.
-
-If this policy is enabled or not configured, the What's New icon and menuitem will be displayed.
- Extension Recommendations
- If this policy is disabled, extensions will not be recommended as the user visits websites.
-
-If this policy is enabled or not configured, extensions will be recommended as the user visits websites.
- Feature Recommendations
- If this policy is disabled, Firefox features will not be recommended as the user uses Firefox.
-
-If this policy is enabled or not configured, Firefox features will be recommended as the user uses Firefox.
- Urlbar Interventions
- If this policy is disabled, actions will not be recommended based on what the user types in the URL bar.
-
-If this policy is enabled or not configured, actions will be recommended based on what the user types in the URL bar.
- Skip Onboarding
- If this policy is enabled, onboarding messages will not be shown on the new tab page.
-
-If this policy is disabled or not configured, onboarding messages will be shown on the new tab page.
- More from Mozilla
- If this policy is disabled, the More from Mozilla section will not be shown in preferences.
-
-If this policy is enabled or not configured, the More from Mozilla section will be shown in preferences.
- Do not allow user messaging preferences to be changed
- If this policy is disabled, user messaging preferences can be changed by the user.
-
-If this policy is enabled or not configured, user messaging preferences cannot be changed by the user.
- TLS_DHE_RSA_WITH_AES_128_CBC_SHA
- TLS_DHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_RSA_WITH_AES_128_CBC_SHA
- TLS_RSA_WITH_AES_256_CBC_SHA
- TLS_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_AES_128_GCM_SHA256
- TLS_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256
- If this policy is enabled, the corresponding cipher is disabled.
-
-If this policy is disabled, the corresponding cipher is enabled.
-
-If this policy is not configured, the corresponding cipher is enabled or disabled based on the default in Firefox.
- Enable Encrypted Media Extensions
- If this policy is disabled, encrypted media extensions (like Widevine) are not downloaded by Firefox unless the user consents to installing them.
-
-If this policy is enabled or not configured, encrypted media extensions (like Widevine) are downloaded automatically and used by Firefox.
- Lock Encrypted Media Extensions
- If this policy is enabled and EncryptedMediaExtensions are disabled, Firefox will not download encrypted media extensions (like Widevine) or ask the user to install them.
-
-If this policy is not disabled or not configured, it has no effect.
- Enable PDF.js
- If this policy is disabled, the built-in PDF viewer is not used.
-
-If this policy is enabled or not configured, the built-in PDF viewer is used.
- Enable Permissions
- If this policy is enabled, the built-in PDF viewer will honor document permissions like preventing the copying of text.
-
-If this policy is not disabled or not configured, document permissions are ignored.
- Enabled
- If this policy is disabled, the Picture-in-Picture toggle does not appear on videos.
-
-If this policy is enabled or not configured, the Picture-in-Picture toggle is available on videos.
- Locked
- If this policy is enabled, Picture-in-Picture settings cannot be changed by the user.
-
-If this policy is disabled or not configured,Picture-in-Picture settings can be changed by the user.
- Primary (Master) Password
- If this policy is enabled, a primary password is required.
-
-If this policy is disabled, users cannot create a primary password.
-
-If this policy is not configured, users can choose to create a primary password.
- Handlers (JSON on one line)
- Handlers
- If this policy is enabled, you can use JSON to configure default application handlers.
-
-If this policy is disabled or not configured, Firefox defaults are used.
-
-For detailed information on creating the policy, see https://github.com/mozilla/policy-templates/blob/master/README.md#handlers.
- Preferences (JSON on one line)
- Preferences
- Note: In order to use this policy, you must clear all settings in the old Preferences (Deprecated) section.
-
-If this policy is enabled, you can use JSON to configure preferences.
-
-If this policy is disabled or not configured, preferences are not modified.
-
-For detailed information on creating the policy, see https://github.com/mozilla/policy-templates/blob/master/README.md#preferences.
- Bookmarks (JSON on one line)
- Bookmarks (JSON)
- If this policy is enabled, you can use JSON to configure bookmarks, including [] to clear all bookmarks.
-
-If this policy is disabled or not configured, the individual bookmark policies are used.
-
-If this policy is enabled along with individual bookmarks, those bookmarks will not be added.
-
-This policy has no effect on Managed Bookmarks.
-
-For detailed information on the JSON, see https://github.com/mozilla/policy-templates/blob/master/README.md#bookmarks.
- Managed Bookmarks (JSON on one line)
- Managed Bookmarks
- If this policy is enabled, you can use JSON to configure managed bookmarks.
-
-If this policy is disabled or not configured, managed bookmarks are not added.
-
-For detailed information on creating the policy, see https://github.com/mozilla/policy-templates/blob/master/README.md#managedbookmarks.
- Define domains allowed to access Google Workspace
- If this policy is enabled, users can only access Google Workspace for the specified domains (separated by a comma). To allow access to Gmail, you can add consumer_accounts.
-
-If this policy is disabled or not configured, users can access any account on Google Workspace as well as Gmail.
- Background updater
- If this policy disabled, the application will not try to install updates when the application is not running.
-
-If this policy is enabled or not configured, application updates may be installed (without user approval) in the background, even when the application is not running. The operating system might still require approval.
- Auto Launch Protocols From Origins (JSON on one line)
- Auto Launch Protocols From Origins
- If this policy is enabled, you can define a list of external protocols that can be used from listed origins without prompting the user.
-
-If this policy is disabled or not configured, any site that invokes an external protocol will ask the user for permission.
-
-For detailed information on creating the policy, see https://github.com/mozilla/policy-templates/blob/master/README.md#autolaunchprotocolsfromorigins.
- Windows SSO
- If this policy is enabled, Firefox will use credentials stored in Windows to sign in to Microsoft, work, and school accounts.
-
-If this policy is disabled or not configured, credentials must be entered manually.
- Use System Print Dialog
- If this policy is enabled, Firefox will use the system print dialog instead of showing print preview before printing.
-
-If this policy is disabled or not configured, Firefox will show print preview before printing.
- Disable warnings based on file extension for specific file types on domains (JSON on one line)
- Disable warnings based on file extension for specific file types on domains
- If this policy is enabled, you can define a list of domains and file type extensions that will be exempt from executable warnings.
-
-If this policy is disabled or not configured, warnings are shown for all executable file types.
-
-For detailed information on creating the policy, see https://github.com/mozilla/policy-templates/blob/master/README.md#exemptdomainfiletypepairsfromfiletypedownloadwarnings.
- Start Downloads in Temporary Directory
- If this policy is enabled, Firefox will start downloads in a temporary directory and automatically deleted when you close the browser.
-
-If this policy is disabled or not configured, Firefox will to the download folder and will not be automatically deleted when you close the browser.
- Force direct intranet site navigation on single word entries in the address bar
- If this policy is enabled, typing single word entries in the address bar will attempt to navigate to intranet sites first, falling back to search if the DNS request fails.
-
-If this policy is disabled or not configured, typing single word entries in the address bar will search.
- Pin updates to a specific version
- If this policy is enabled, you can specify a Firefox version as xx. or xx.xx. and Firefox will not be updated beyond that major or minor version.
-
-If this policy is disabled or not configured, Firefox will update normally.
- Do not allow proxy settings to be changed
- If this policy is enabled, proxy settings cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change their proxy settings.
- Connection Type
- If this policy is enabled, you can set the connection type.
-
-If this policy is disabled or not configured, Firefox defaults to using the system proxy.
- HTTP Proxy
- If this policy is enabled, you can set the HTTP Proxy used when manual proxy configuration is specified.
-
-If this policy is disabled or not configured, Firefox does not use an HTTP Proxy.
- Use HTTP proxy for HTTPS
- If this policy is enabled, the HTTP Proxy is used for HTTPS when manual proxy configuration is specified.
-
-If this policy is disabled or not configured, Firefox does not use an HTTPS Proxy unless specified.
- HTTPS Proxy
- If this policy is enabled, you can set the HTTPS Proxy used when manual proxy configuration is specified.
-
-If this policy is disabled or not configured, Firefox does not use an HTTPS Proxy.
- SOCKS Host
- If this policy is enabled, you can set the SOCKS Host and version used when manual proxy configuration is specified.
-
-If this policy is disabled or not configured, Firefox does not use a SOCKS Host.
- Automatic proxy configuration URL
- If this policy is enabled, you can set the automatic proxy configuration URL.
-
-If this policy is disabled or not configured, Firefox does not use an automatic proxy configuration URL.
- Proxy Passthrough
- If this policy is enabled, the proxy settings are bypassed for the locations specified.
-
-If this policy is disabled or not configured, Firefox does not bypass the proxy.
- Do not prompt for authentication if password is saved
- If this policy is enabled, Firefox will not prompt for proxy authentication when a password is saved.
-
-If this policy is disabled or not configured, Firefox will always prompt for proxy authentication.
- Proxy DNS when using SOCKS v5
- If this policy is enabled, DNS is proxied when using SOCKS v5.
-
-If this policy is disabled or not configured, DNS is not proxied when using SOCKS v5.
- Disable Third Party Module Blocking
- If this policy is enabled, users are not allowed to block third-party modules from the about:third-party page.
-
-If this policy is disabled or not configured, users users are allowed to block third-party modules from the about:third-party page.
- Containers (JSON on one line)
- Containers
- If this policy is enabled, you can use JSON to configure the default containers.
-
-If this policy is disabled or not configured, the built-in defaults are used.
-
-For detailed information on creating the policy, see https://github.com/mozilla/policy-templates/blob/master/README.md#containers.
- Suggestions from the web
- If this policy is enabled, you will get suggestions from Firefox related to your search.
-
-If this policy is disabled, you will not get these suggestions.
-
-If this policy is not configured, , you will get suggestions from Firefox related to your search.
- Suggestions from sponsors
- If this policy is enabled, you will support the development of Firefox with occasional sponsored suggestions.
-
-If this policy is disabled, you will not get these suggestions.
-
-If this policy is not configured, you will get occasional sponsored suggestions.
- Improve the Firefox Suggest experience
- If this policy is enabled, you will help create a richer search experience by allowing Mozilla to process your search queries.
-
-If this policy is disabled or not configured, you do not allow Mozilla to process your search queries.
- Do not allow preferences to be changed
- If this policy is enabled, Firefox Suggest preferences cannot be changed by the user.
-
-If this policy is disabled or not configured, the user can change their Firefox Suggest preferences.
- If this policy is enabled, the preference is locked to true. If this policy is disabled, the preference is locked to false.
-
-For a description of the preference, see:
-
-https://github.com/mozilla/policy-templates/blob/master/README.md#preferences
- If this policy is enabled, the preference is locked to the string entered. If this policy is disabled, it has no effect.
-
-For a description of the preference, see:
-
-https://github.com/mozilla/policy-templates/blob/master/README.md#preferences
- If this policy is enabled, the preference is locked to the value selected. If this policy is disabled, it has no effect.
-
-For a description of the preference, see:
-
-https://github.com/mozilla/policy-templates/blob/master/README.md#preferences.
- This preference is no longer support on Windows. We are investigating creating a policy.
- Auto (0)
- Always Off (1)
- Ask Every Time
- Select Automatically
- accessibility.force_disabled
- app.update.auto (Deprecated)
- browser.bookmarks.autoExportHTML
- browser.bookmarks.file
- browser.bookmarks.restore_default_bookmarks
- browser.cache.disk.enable
- browser.fixup.dns_first_for_single_words
- browser.places.importBookmarksHTML
- browser.safebrowsing.phishing.enabled
- browser.safebrowsing.malware.enabled
- browser.search.update
- browser.tabs.warnOnClose
- browser.cache.disk.parent_directory
- browser.slowStartup.notificationDisabled
- browser.taskbar.previews.enable
- browser.urlbar.suggest.bookmark
- browser.urlbar.suggest.history
- browser.urlbar.suggest.openpage
- datareporting.policy.dataSubmissionPolicyBypassNotification
- dom.allow_scripts_to_close_windows
- dom.disable_window_flip
- dom.disable_window_move_resize
- dom.event.contextmenu.enabled
- dom.keyboardevent.keypress.hack.dispatch_non_printable_keys.addl
- dom.keyboardevent.keypress.hack.use_legacy_keycode_and_charcode.addl
- dom.xmldocument.load.enabled
- dom.xmldocument.async.enabled
- extensions.blocklist.enabled
- geo.enabled
- extensions.getAddons.showPane
- intl.accept_languages
- media.eme.enabled (Deprecated)
- media.gmp-gmpopenh264.enabled
- media.gmp-widevinecdm.enabled
- network.dns.disableIPv6
- network.IDN_show_punycode
- places.history.enabled
- print.save_print_settings
- security.default_personal_cert
- security.ssl.errorReporting.enabled
- security.mixed_content.block_active_content
- ui.key.menuAccessKeyFocuses
- browser.newtabpage.activity-stream.default.sites
- extensions.htmlaboutaddons.recommendations.enabled
- media.peerconnection.enabled
- media.peerconnection.ice.obfuscate_host_addresses.whitelist (Deprecated)
- media.peerconnection.ice.obfuscate_host_addresses.blocklist
- security.osclientcerts.autoload
- security.tls.hello_downgrade_check
- widget.content.gtk-theme-override
-
-
-
-
-
-
-
-
-
-
-
- Always allow NTLM on non FQDNs
- Always allow SPNEGO on non FQDNs
-
-
- Allow NTLM to automatically authenticate with proxy servers
- Allow SPNEGO to automatically authenticate with proxy servers
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Allow popups for websites
-
-
-
-
-
-
-
-
-
-
-
-
-
- Don't allow tracking protection preferences to be changed.
- Block cryptomining scripts.
- Block fingerprinting scripts.
- Exceptions:
-
-
-
-
-
-
-
-
-
-
-
- URL:
-
-
-
- Don't allow the homepage to be changed.
-
-
- Additional homepages
-
-
-
-
-
- Title:
-
-
-
- URL:
-
-
-
- Favicon URL:
-
-
-
- Placement:
-
- Folder name:
-
-
-
-
-
-
-
-
-
-
-
- Method:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Don't allow proxy settings to be changed.
- Connection Type:
-
- HTTP Proxy:
-
-
-
- Use this proxy server for all protocols.
- SSL Proxy:
-
-
-
- FTP Proxy:
-
-
-
- SOCKS Host:
-
-
-
- SOCKS Version:
-
- No proxy for
-
-
-
- Example: .mozilla.org, .net.nz, 192.168.1.0/24
- Automatic proxy configuration URL:
-
-
-
- Do not prompt for authentication if password is saved.
- Proxy DNS when using SOCKS v5.
-
-
- Provider URL:
-
-
-
- Enable DNS over HTTPS.
- Don't allow DNS over HTTPS preferences to be changed.
-
-
-
-
-
-
-
-
- Title:
-
-
-
- URL:
-
-
-
- Access key:
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Cache
- Cookies
- Download History
- Form & Search History
- Browsing History
- Active Logins
- Site Preferences
- Offline Website Data
-
-
- Search
- Top Sites
- Sponsored Top Sites
- Download History
- Recommended by Pocket
- Sponsored Pocket Stories
- Snippets
- Don't allow settings to be changed
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Host including port:
-
-
-
- SOCKS Version:
-
-
-
-
-
-
-
-
- No proxy for
-
-
-
- Example: .mozilla.org, .net.nz, 192.168.1.0/24
- Connections to localhost, 127.0.0.1/8, and ::1 are never proxied.
-
-
-
-
diff --git a/policy_templates/en-US/fthsvc.adml b/policy_templates/en-US/fthsvc.adml
deleted file mode 100644
index a45eae2..0000000
--- a/policy_templates/en-US/fthsvc.adml
+++ /dev/null
@@ -1,25 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Fault Tolerant Heap
- Configure Scenario Execution Level
- This policy setting permits or prohibits the Diagnostic Policy Service (DPS) from automatically resolving any heap corruption problems.
-
-If you enable this policy setting, the DPS detects, troubleshoots, and attempts to resolve automatically any heap corruption problems.
-
-If you disable this policy setting, Windows cannot detect, troubleshoot, and attempt to resolve automatically any heap corruption problems that are handled by the DPS.
-
-If you do not configure this policy setting, the DPS enables Fault Tolerant Heap for resolution by default.
-
-This policy setting takes effect only if the diagnostics-wide scenario execution policy is not configured.
-
-This policy setting takes effect only when the Diagnostic Policy Service is in the running state. When the service is stopped or disabled, diagnostic scenarios are not executed. The DPS can be configured with the Services snap-in to the Microsoft Management Console.
-
-No system restart or service restart is required for this policy setting to take effect: changes take effect immediately.
-
-
-
diff --git a/policy_templates/en-US/grouppolicy-server.adml b/policy_templates/en-US/grouppolicy-server.adml
deleted file mode 100644
index cbf6b76..0000000
--- a/policy_templates/en-US/grouppolicy-server.adml
+++ /dev/null
@@ -1,22 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Allow asynchronous user Group Policy processing when logging on through Remote Desktop Services
-
- This policy setting allows Microsoft Windows to process user Group Policy settings asynchronously when logging on through Remote Desktop Services. Asynchronous user Group Policy processing is the default processing mode for Windows Vista and Windows XP.
-
-By default, Window Server processes user Group Policy settings synchronously.
-
-If you enable this policy setting, Windows applies user Group Policy settings asynchronously, when logging on through Remote Desktop Services.
-
-If you disable or do not configure this policy setting, Windows Server applies user Group Policy settings synchronously.
-
-Note: This policy setting applies only to computers running Remote Desktop Services.
- Group Policy
-
-
-
diff --git a/policy_templates/en-US/grouppolicypreferences.adml b/policy_templates/en-US/grouppolicypreferences.adml
deleted file mode 100644
index 962ea8d..0000000
--- a/policy_templates/en-US/grouppolicypreferences.adml
+++ /dev/null
@@ -1,1332 +0,0 @@
-
-
-
- Group Policy Preference Policies
-
-
-
- Permit use of Application snap-ins
- This policy setting allows you to permit or prohibit use of Application snap-ins (Application preference item types). When prohibited, no Application preference item types appear when you attempt to create a new Application preference item, and you are unable to do so. This policy setting does not affect existing Application preference items.
-
-If you enable or do not configure this policy setting, you permit use of Application snap-ins. Enabling this policy setting does not override policy settings that restrict the use of preference extensions.
-
-If you disable this policy setting, you prohibit use of Applications snap-ins, and new Application preference items cannot be created.
-
- Permit use of Applications preference extension
- This policy setting allows you to permit or prohibit use of the Applications preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
- Permit use of Control Panel Settings (Computers)
- This policy setting allows you to permit or prohibit use of the Control Panel Settings item and all preference extensions listed in the Group Policy Management Editor window of the GPMC under Computer Configuration\Preferences\Control Panel Settings. When the Control Panel Settings item or a preference extension is prohibited, it does not appear in the Group Policy Management Editor window.
-
-If you enable this policy setting, you permit use of the Control Panel Settings item and all preference extensions under Control Panel Settings for Computer Configuration. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting for the Control Panel Settings item, but not for its children. Enabling this policy setting does not override any "Permit use of <extension name> preference extension" policy settings that are disabled.
-
-If you disable this policy setting, you prohibit use of preference extensions under Control Panel Settings for Computer Configuration. Disabling this policy setting overrides any "Permit use of <extension name> preference extension" policy settings.
-
-If you do not configure this policy setting, you permit use of preference extensions under Control Panel Settings for Computer Configuration unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting or any "Permit use of <extension name> preference extension" policy settings.
-
- Permit use of Data Sources preference extension
- This policy setting allows you to permit or prohibit use of the Data Sources preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Computers)" or "Permit use of Control Panel Settings (Users)" policy settings. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins," "Permit use of Control Panel Settings (Computers)," or "Permit use of Control Panel Settings (Users)," policy settings.
-
- Permit use of Devices preference extension
- This policy setting allows you to permit or prohibit use of the Devices preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Computers)" or "Permit use of Control Panel Settings (Users)" policy settings. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins," "Permit use of Control Panel Settings (Computers)," or "Permit use of Control Panel Settings (Users)," policy settings.
-
- Permit use of Drive Maps preference extension
- This policy setting allows you to permit or prohibit use of the Drive Maps preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
- Permit use of Environment preference extension
- This policy setting allows you to permit or prohibit use of the Environment preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
- Permit use of Files preference extension
- This policy setting allows you to permit or prohibit use of the Files preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
- Permit use of Folder Options preference extension
- This policy setting allows you to permit or prohibit use of the Folder Options preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Computers)" or "Permit use of Control Panel Settings (Users)" policy settings. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins," "Permit use of Control Panel Settings (Computers)," or "Permit use of Control Panel Settings (Users)," policy settings.
-
- Permit use of Folders preference extension
- This policy setting allows you to permit or prohibit use of the Folders preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
- Permit use of Ini Files preference extension
- This policy setting allows you to permit or prohibit use of the Ini Files preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
- Permit use of Internet Settings preference extension
- This policy setting allows you to permit or prohibit use of the Internet Settings preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Users)" policy setting. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" or "Permit use of Control Panel Settings (Users)" policy settings.
-
- Permit use of Local Users and Groups preference extension
- This policy setting allows you to permit or prohibit use of the Local Users and Groups preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Computers)" or "Permit use of Control Panel Settings (Users)" policy settings. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins," "Permit use of Control Panel Settings (Computers)," or "Permit use of Control Panel Settings (Users)," policy settings.
-
- Permit use of Network Options preference extension
- This policy setting allows you to permit or prohibit use of the Network Options preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Computers)" or "Permit use of Control Panel Settings (Users)" policy settings. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins," "Permit use of Control Panel Settings (Computers)," or "Permit use of Control Panel Settings (Users)," policy settings.
-
- Permit use of Network Shares preference extension
- This policy setting allows you to permit or prohibit use of the Network Shares preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
- Permit use of Power Options preference extension
- This policy setting allows you to permit or prohibit use of the Power Options preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Computers)" or "Permit use of Control Panel Settings (Users)" policy settings. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins," "Permit use of Control Panel Settings (Computers)," or "Permit use of Control Panel Settings (Users)," policy settings.
-
- Permit use of Printers preference extension
- This policy setting allows you to permit or prohibit use of the Printers preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Computers)" or "Permit use of Control Panel Settings (Users)" policy settings. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins," "Permit use of Control Panel Settings (Computers)," or "Permit use of Control Panel Settings (Users)," policy settings.
-
- Permit use of Regional Options preference extension
- This policy setting allows you to permit or prohibit use of the Regional Options preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Users)" policy setting. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" or "Permit use of Control Panel Settings (Users)" policy settings.
-
- Permit use of Registry preference extension
- This policy setting allows you to permit or prohibit use of the Registry preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
- Permit use of Scheduled Tasks preference extension
- This policy setting allows you to permit or prohibit use of the Scheduled Tasks preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Computers)" or "Permit use of Control Panel Settings (Users)" policy settings. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins," "Permit use of Control Panel Settings (Computers)," or "Permit use of Control Panel Settings (Users)," policy settings.
-
- Permit use of Services preference extension
- This policy setting allows you to permit or prohibit use of the Services preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Computers)" policy setting. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" or "Permit use of Control Panel Settings (Computers)" policy settings.
-
- Permit use of Shortcuts preference extension
- This policy setting allows you to permit or prohibit use of the Shortcuts preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
- Permit use of Control Panel Settings (Users)
- This policy setting allows you to permit or prohibit use of the Control Panel Settings item and all preference extensions listed in the Group Policy Management Editor window of the GPMC under User Configuration\Preferences\Control Panel Settings. When the Control Panel Settings item or a preference extension is prohibited, it does not appear in the Group Policy Management Editor window.
-
-If you enable this policy setting, you permit use of the Control Panel Settings item and all preference extensions under Control Panel Settings for User Configuration. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting for the Control Panel Settings item, but not for its children. Enabling this policy setting does not override any "Permit use of <extension name> preference extension" policy settings that are disabled.
-
-If you disable this policy setting, you prohibit use of preference extensions under Control Panel Settings for User Configuration. Disabling this policy setting overrides any "Permit use of <extension name> preference extension" policy settings.
-
-If you do not configure this policy setting, you permit use of preference extensions under Control Panel Settings for User Configuration unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" policy setting or any "Permit use of <extension name> preference extension" policy settings.
-
- Permit use of Start Menu preference extension
- This policy setting allows you to permit or prohibit use of the Start Menu preference extension. When a preference extension is prohibited, it does not appear in the Group Policy Management Editor window of the GPMC.
-
-If you enable this policy setting, you permit use of the preference extension unless restricted by the "Permit use of Control Panel Settings (Users)" policy setting. Enabling this policy setting overrides the "Restrict users to the explicitly permitted list of snap-ins" policy setting.
-
-If you disable this policy setting, you prohibit use of the preference extension.
-
-If you do not configure this policy setting, you permit use of the preference extension unless restricted by the "Restrict users to the explicitly permitted list of snap-ins" or "Permit use of Control Panel Settings (Users)" policy settings.
-
- Permit use of Preferences tab
- This policy setting allows you to permit or prohibit use of the Preferences tab. When prohibited, the Preferences tab does not appear when you view a preference extension in the Group Policy Management Editor window of the GPMC. The Extended and Standard tabs are unaffected, and you can still create and manage preference items.
-
-If you enable this policy setting, you permit use of the Preferences tab. Enabling this policy setting does not override policy settings that restrict the use of preference extensions.
-
-If you disable this policy setting, you prohibit use of the Preferences tab.
-
-If you do not configure this policy setting, you permit use of the Preferences tab.
-
- Configure Applications preference extension policy processing
- This policy setting allows you to configure when preference items in the Applications preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Application preference items.
-
-If you disable or do not configure this policy setting, Application preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Applications preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Applications preference extension, and to turn on tracing for the Applications extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Applications extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
-
- Configure Data Sources preference extension policy processing
- This policy setting allows you to configure when preference items in the Data Sources preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Data Sources preference items.
-
-If you disable or do not configure this policy setting, Data Sources preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
-
- Configure Data Sources preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Data Sources preference extension, and to turn on tracing for the Data Sources extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Data Sources extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Devices preference extension policy processing
- This policy setting allows you to configure when preference items in the Devices preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Device preference items.
-
-If you disable or do not configure this policy setting, Device preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
-
- Configure Devices preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Devices preference extension, and to turn on tracing for the Devices extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Devices extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Drive Maps preference extension policy processing
- This policy setting allows you to configure when preference items in the Drive Maps preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Drive Maps preference items.
-
-If you disable or do not configure this policy setting, Drive Maps preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
-
- Configure Drive Maps preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Drive Maps preference extension, and to turn on tracing for the Drive Maps extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Drive Maps extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Environment preference extension policy processing
- This policy setting allows you to configure when preference items in the Environment preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Environment Variable preference items.
-
-If you disable or do not configure this policy setting, Environment Variable preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged
-preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Environment preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Environment preference extension, and to turn on tracing for the Environment extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Environment extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Files preference extension policy processing
- This policy setting allows you to configure when preference items in the Files preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for File preference items.
-
-If you disable or do not configure this policy setting, File preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Files preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Files preference extension, and to turn on tracing for the Files extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Files extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Folder Options preference extension policy processing
- This policy setting allows you to configure when preference items in the Folder Options preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Folder Options, Open With, and File Type preference items.
-
-If you disable or do not configure this policy setting, Folder Options, Open With, and File Type preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Folder Options preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Folder Options preference extension, and to turn on tracing for the Folder Options extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Folder Options extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Folders preference extension policy processing
- This policy setting allows you to configure when preference items in the Folders preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Folder preference items.
-
-If you disable or do not configure this policy setting, Folder preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Folders preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Folders preference extension, and to turn on tracing for the Folders extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Folders extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Ini Files preference extension policy processing
- This policy setting allows you to configure when preference items in the Ini Files preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Ini Files preference items.
-
-If you disable or do not configure this policy setting, Ini Files preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Ini Files preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Ini Files preference extension, and to turn on tracing for the Ini Files extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Ini Files extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Internet Settings preference extension policy processing
- This policy setting allows you to configure when preference items in the Internet Settings preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Internet preference items.
-
-If you disable or do not configure this policy setting, Internet preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Internet Settings preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Internet preference extension, and to turn on tracing for the Internet extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Internet extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Local Users and Groups preference extension policy processing
- This policy setting allows you to configure when preference items in the Local Users and Groups preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Local User and Local Group preference items.
-
-If you disable or do not configure this policy setting, Local User and Local Group preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Local Users and Groups preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Local User and Local Group preference extension, and to turn on tracing for the Local User and Local Group extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Local User and Local Group extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Network Options preference extension policy processing
- This policy setting allows you to configure when preference items in the Network Options preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for VPN Connection and DUN Connection preference items.
-
-If you disable or do not configure this policy setting, VPN Connection and DUN Connection preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Network Options preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Network Options preference extension, and to turn on tracing for the Network Options extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Network Options extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Network Shares preference extension policy processing
- This policy setting allows you to configure when preference items in the Network Shares preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Network Shares preference items.
-
-If you disable or do not configure this policy setting, Network Shares preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Network Shares preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Network Shares preference extension, and to turn on tracing for the Network Shares extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Network Shares extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Power Options preference extension policy processing
- This policy setting allows you to configure when preference items in the Power Options preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Power Options and Power Scheme preference items.
-
-If you disable or do not configure this policy setting, Power Options and Power Scheme preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Power Options preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Power Options preference extension, and to turn on tracing for the Power Options extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Power Options extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Printers preference extension policy processing
- This policy setting allows you to configure when preference items in the Printers preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Shared Printer, TCP/IP Printer, and Local Printer preference items.
-
-If you disable or do not configure this policy setting, Shared Printer, TCP/IP Printer, and Local Printer preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Printers preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Printers preference extension, and to turn on tracing for the Printers extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Printers extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Regional Options preference extension policy processing
- This policy setting allows you to configure when preference items in the Regional Options preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Regional Options preference items.
-
-If you disable or do not configure this policy setting, Regional Options preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Regional Options preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Regional Options preference extension, and to turn on tracing for the Regional Options extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Regional Options extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Registry preference extension policy processing
- This policy setting allows you to configure when preference items in the Registry preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Registry preference items.
-
-If you disable or do not configure this policy setting, Registry preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Registry preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Registry preference extension, and to turn on tracing for the Registry extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Registry extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Scheduled Tasks preference extension policy processing
- This policy setting allows you to configure when preference items in the Scheduled Tasks preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Scheduled Task and Immediate Task preference items.
-
-If you disable or do not configure this policy setting, Scheduled Task and Immediate Task preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Scheduled Tasks preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Scheduled Tasks preference extension, and to turn on tracing for the Scheduled Tasks extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Scheduled Tasks extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Services preference extension policy processing
- This policy setting allows you to configure when preference items in the Services preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Service preference items.
-
-If you disable or do not configure this policy setting, Service preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Services preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Services preference extension, and to turn on tracing for the Services extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Services extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Shortcuts preference extension policy processing
- This policy setting allows you to configure when preference items in the Shortcuts preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Shortcut preference items.
-
-If you disable or do not configure this policy setting, Shortcut preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Shortcuts preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Shortcuts preference extension, and to turn on tracing for the Shortcuts extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Shortcuts extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Configure Start Menu preference extension policy processing
- This policy setting allows you to configure when preference items in the Start Menu preference extension are updated.
-
-If you enable this policy setting, you can configure processing options for Start Menu preference items.
-
-If you disable or do not configure this policy setting, Start Menu preference items are allowed to process across a slow network connection, to be applied during background processing, and to process even if the Group Policy objects (GPOs) are unchanged. By default, background processing priority is "Idle."
-
-Notes:
-
-1. The "Allow processing across a slow network connection" option updates preference items even when the update is transmitted across a slow network connection, such as a telephone line. Updates across slow connections can cause significant delays.
-
-2. The "Do not apply during periodic background processing" option prevents the system from updating affected preference items in the background while the computer is in use. When background updates are disabled, preference item changes do not take effect until the next user logon or system restart.
-
-3. The "Process even if the Group Policy objects have not changed" option updates and reapplies the preference items even if the preference items have not changed. Many policy implementations specify that they are updated only when changed. However, you might want to update unchanged preference items, such as reapplying a desired preference setting in case a user has changed it.
- Configure Start Menu preference logging and tracing
- This policy setting allows you to configure the level of detail recorded by event logging for the Start Menu preference extension, and to turn on tracing for the Start Menu extension. Logging and tracing provide diagnostic information for troubleshooting.
-
-If you enable this policy setting, you can configure event logging and turn on tracing for the Start Menu extension for client computers.
-
-If you disable or do not configure this policy setting, by default event logging for this extension includes only warnings and errors, and tracing for this extension is turned off.
-
-Notes:
-
-1. User Configuration tracing: To perform tracing for items in this preference extension listed under User Configuration, you must provide a path in the "User trace" box to the location where a user trace file can be created on the client computer, and you must turn on the "Tracing" option. If there are no preference items under User Configuration in this extension, no user trace file is created.
-
-2. Computer Configuration tracing: This preference extension is available under User Configuration only, so computer configuration tracing is not applicable.
-
-3. Group Policy Modeling query tracing: To perform tracing for items in this preference extension when you perform a Group Policy Modeling query, you must provide a path in the "Planning trace" box to the location where a planning trace file can be created on the computer where you run modeling, and you must turn on the "Tracing" option. If you are not performing Group Policy Modeling or there are no preference items in this extension, no planning trace file is created.
- Process even if the Group Policy objects have not changed
- Do not apply during periodic background processing
- Allow processing across a slow network connection
- Tracing
- User trace
- Computer trace
- Trace file
- Planning trace
- Maximum size of trace file (KB)
- Off
- On
- Background priority
- Normal
- Below Normal
- Lowest
- Idle
- Event logging
- Informational, Warnings and Errors
- Warnings and Errors
- Errors Only
- None
- Preference snap-in extensions
- Allows you to permit and prohibit the use of Group Policy Object Editor (GPOE) Preference snap-in extensions.
- Logging and tracing
- Allows you to configure the logging and tracing for Preference components.
-
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Computer.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
- Allow processing across a slow network connection
- Do not apply during periodic background processing
- Process even if the Group Policy objects have not changed
- Background priority
-
-
- Event logging
- Tracing
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\User.log
-
-
-
- %COMMONAPPDATA%\GroupPolicy\Preference\Trace\Planning.log
-
- Maximum size of trace file (KB)
-
-
-
-
diff --git a/policy_templates/en-US/hotspotauth.adml b/policy_templates/en-US/hotspotauth.adml
deleted file mode 100644
index 0de4fed..0000000
--- a/policy_templates/en-US/hotspotauth.adml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- Hotspot Authentication Group Policy Settings
- Hotspot Authentication Group Policy Settings
-
-
- Hotspot Authentication
- Enable Hotspot Authentication
- This policy setting defines whether WLAN hotspots are probed for Wireless Internet Service Provider roaming (WISPr) protocol support.
-
-If a WLAN hotspot supports the WISPr protocol, users can submit credentials when manually connecting to the network. If authentication is successful, users will be connected automatically on subsequent attempts. Credentials can also be configured by network operators.
-
-If you enable this policy setting, or if you do not configure this policy setting, WLAN hotspots are automatically probed for WISPR protocol support.
-
-If you disable this policy setting, WLAN hotspots are not probed for WISPr protocol support, and users can only authenticate with WLAN hotspots using a web browser.
-
-
-
-
diff --git a/policy_templates/en-US/iSCSI.adml b/policy_templates/en-US/iSCSI.adml
deleted file mode 100644
index d1d8e30..0000000
--- a/policy_templates/en-US/iSCSI.adml
+++ /dev/null
@@ -1,37 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- iSCSI
- iSCSI Target Discovery
- Do not allow manual configuration of iSNS servers
- If enabled then new iSNS servers may not be added and thus new targets discovered via those iSNS servers; existing iSNS servers may not be removed. If disabled then new iSNS servers may be added and thus new targets discovered via those iSNS servers; existing iSNS servers may be removed.
- Do not allow manual configuration of target portals
- If enabled then new target portals may not be added and thus new targets discovered on those portals; existing target portals may not be removed. If disabled then new target portals may be added and thus new targets discovered on those portals; existing target portals may be removed.
- Do not allow manual configuration of discovered targets
- If enabled then discovered targets may not be manually configured. If disabled then discovered targets may be manually configured. Note: if enabled there may be cases where this will break VDS.
- Policy settings controlling the discovery of iSCSI targets.
- Do not allow adding new targets via manual configuration
- If enabled then new targets may not be manually configured by entering the target name and target portal; already discovered targets may be manually configured. If disabled then new and already discovered targets may be manually configured. Note: if enabled there may be cases where this will break VDS.
- General iSCSI
- Do not allow changes to initiator iqn name
- If enabled then do not allow the initiator iqn name to be changed. If disabled then the initiator iqn name may be changed.
- Policy settings controlling the iSCSI node name and session logins.
- Do not allow additional session logins
- If enabled then only those sessions that are established via a persistent login will be established and no new persistent logins may be created. If disabled then additional persistent and non persistent logins may be established.
- iSCSI Security
- Do not allow changes to initiator CHAP secret
- If enabled then do not allow the initiator CHAP secret to be changed. If disabled then the initiator CHAP secret may be changed.
- Policy settings controlling the security (authentication, encryption, etc) of iSCSI sessions.
- Do not allow connections without IPSec
- If enabled then only those connections that are configured for IPSec may be established. If disabled then connections that are configured for IPSec or connections not configured for IPSec may be established.
- Do not allow sessions without mutual CHAP
- If enabled then only those sessions that are configured for mutual CHAP may be established. If disabled then sessions that are configured for mutual CHAP or sessions not configured for mutual CHAP may be established.
- Do not allow sessions without one way CHAP
- If enabled then only those sessions that are configured for one-way CHAP may be established. If disabled then sessions that are configured for one-way CHAP or sessions not configured for one-way CHAP may be established. Note that if the "Do not allow sessions without mutual CHAP" setting is enabled then that setting overrides this one.
-
-
-
diff --git a/policy_templates/en-US/inkwatson.adml b/policy_templates/en-US/inkwatson.adml
deleted file mode 100644
index eabe2e1..0000000
--- a/policy_templates/en-US/inkwatson.adml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off handwriting recognition error reporting
- Turns off the handwriting recognition error reporting tool.
-
-The handwriting recognition error reporting tool enables users to report errors encountered in Tablet PC Input Panel. The tool generates error reports and transmits them to Microsoft over a secure connection. Microsoft uses these error reports to improve handwriting recognition in future versions of Windows.
-
-If you enable this policy, users cannot start the handwriting recognition error reporting tool or send error reports to Microsoft.
-
-If you disable this policy, Tablet PC users can report handwriting recognition errors to Microsoft.
-
-If you do not configure this policy Tablet PC users can report handwriting recognition errors to Microsoft.
-
-
-
diff --git a/policy_templates/en-US/lync16.adml b/policy_templates/en-US/lync16.adml
deleted file mode 100644
index fa9b9b8..0000000
Binary files a/policy_templates/en-US/lync16.adml and /dev/null differ
diff --git a/policy_templates/en-US/mmcsnapins2.adml b/policy_templates/en-US/mmcsnapins2.adml
deleted file mode 100644
index 1cc2437..0000000
--- a/policy_templates/en-US/mmcsnapins2.adml
+++ /dev/null
@@ -1,35 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Storage Manager for SANs
- Storage Manager for SANS Extension
- File Server Resource Manager
- File Server Resource Manager Extension
- Disk Management Extension
- DFS Management
- DFS Management Extension
- Share and Storage Management
- Share and Storage Management Extension
- Group Policy Management
- Group Policy Starter GPO Editor
- Group Policy Management Editor
- This policy setting permits or prohibits the use of this snap-in.
-
-If you enable this policy setting, the snap-in is permitted and can be added into the Microsoft Management Console or run from the command line as a standalone console.
-
-If you disable this policy setting, the snap-in is prohibited and cannot be added into the Microsoft Management Console or run from the command line as a standalone console. An error message is displayed stating that policy is prohibiting the use of this snap-in.
-
-If this policy setting is not configured, the setting of the "Restrict users to the explicitly permitted list of snap-ins" setting determines whether this snap-in is permitted or prohibited.
-
--- If the policy setting "Restrict users to the explicitly permitted list of snap-ins" is enabled, users cannot use any snap-in except those explicitly permitted. To explicitly permit use of this snap-in, enable this policy setting. If this policy setting is not configured or disabled, this snap-in is prohibited.
-
--- If the policy setting "Restrict users to the explicitly permitted list of snap-ins" is disabled or not configured, users can use any snap-in except those explicitly prohibited. To explicitly prohibit use of this snap-in, disable this policy setting. If this policy setting is not configured or enabled, the snap-in is permitted.
-
-When a snap-in is prohibited, it does not appear in the Add/Remove Snap-in window in MMC. Also, when a user opens a console file that includes a prohibited snap-in, the console file opens, but the prohibited snap-in does not appear.
-
-
-
diff --git a/policy_templates/en-US/mozilla.adml b/policy_templates/en-US/mozilla.adml
deleted file mode 100644
index 90e0698..0000000
--- a/policy_templates/en-US/mozilla.adml
+++ /dev/null
@@ -1,10 +0,0 @@
-
-
-
-
-
-
- Mozilla
-
-
-
diff --git a/policy_templates/en-US/msched.adml b/policy_templates/en-US/msched.adml
deleted file mode 100644
index 585c9ad..0000000
--- a/policy_templates/en-US/msched.adml
+++ /dev/null
@@ -1,57 +0,0 @@
-
-
-
- Maintenance Scheduler Policies
- Maintenance Scheduler Group Policies
-
-
- Maintenance Scheduler
- Automatic Maintenance Activation Boundary
-
- This policy setting allows you to configure Automatic Maintenance activation boundary.
-
- The maintenance activation boundary is the daily schduled time at which Automatic Maintenance starts
-
- If you enable this policy setting, this will override the default daily scheduled time as specified in Security and Maintenance/Automatic Maintenance Control Panel.
-
- If you disable or do not configure this policy setting, the daily scheduled time as specified in Security and Maintenance/Automatic Maintenance Control Panel will apply.
-
- Automatic Maintenance Random Delay
-
- This policy setting allows you to configure Automatic Maintenance activation random delay.
-
- The maintenance random delay is the amount of time up to which Automatic Maintenance will delay starting from its Activation Boundary.
-
- If you enable this policy setting, Automatic Maintenance will delay starting from its Activation Boundary, by upto this time.
-
- If you do not configure this policy setting, 4 hour random delay will be applied to Automatic Maintenance.
-
- If you disable this policy setting, no random delay will be applied to Automatic Maintenance.
-
- Automatic Maintenance WakeUp Policy
-
- This policy setting allows you to configure Automatic Maintenance wake up policy.
-
- The maintenance wakeup policy specifies if Automatic Maintenance should make a wake request to the OS for the daily scheduled maintenance. Note, that if the OS power wake policy is explicitly disabled, then this setting has no effect.
-
- If you enable this policy setting, Automatic Maintenance will attempt to set OS wake policy and make a wake request for the daily scheduled time, if required.
-
- If you disable or do not configure this policy setting, the wake setting as specified in Security and Maintenance/Automatic Maintenance Control Panel will apply.
-
-
-
-
-
-
- 2000-01-01T02:00:00
-
-
-
-
-
- PT4H
-
-
-
-
-
diff --git a/policy_templates/en-US/nca.adml b/policy_templates/en-US/nca.adml
deleted file mode 100644
index d7532fa..0000000
--- a/policy_templates/en-US/nca.adml
+++ /dev/null
@@ -1,125 +0,0 @@
-
- DirectAccess Client Experience Settings Group Policy Template
- This admx file describes policy template for DirectAccess Client NCA component
-
-
- DirectAccess Client Experience Settings
- This is the group policy template for DirectAccess Client Experience Settings. Please read the DirectAccess deployment guide for more information.
- Support Email Address
- Specifies the e-mail address to be used when sending the log files that are generated by NCA to the network administrator.
-
-When the user sends the log files to the Administrator, NCA uses the default e-mail client to open a new message with the support email address in the To: field of the message, then attaches the generated log files as a .html file. The user can review the message and add additional information before sending the message.
-
- Friendly Name
- Specifies the string that appears for DirectAccess connectivity when the user clicks the Networking notification area icon. For example, you can specify “Contoso Intranet Access” for the DirectAccess clients of the Contoso Corporation.
-
-If this setting is not configured, the string that appears for DirectAccess connectivity is “Corporate Connection”.
-
- User Interface
- Specifies whether an entry for DirectAccess connectivity appears when the user clicks the Networking notification area icon.
-
-Set this to Disabled to prevent user confusion when you are just using DirectAccess to remotely manage DirectAccess client computers from your intranet and not providing seamless intranet access.
-
-If this setting is not configured, the entry for DirectAccess connectivity appears.
-
- DirectAccess Passive Mode
- Specifies whether NCA service runs in Passive Mode or not.
-
-Set this to Disabled to keep NCA probing actively all the time. If this setting is not configured, NCA probing is in active mode by default.
-
- Prefer Local Names Allowed
- Specifies whether the user has Connect and Disconnect options for the DirectAccess entry when the user clicks the Networking notification area icon.
-
-If the user clicks the Disconnect option, NCA removes the DirectAccess rules from the Name Resolution Policy Table (NRPT) and the DirectAccess client computer uses whatever normal name resolution is available to the client computer in its current network configuration, including sending all DNS queries to the local intranet or Internet DNS servers. Note that NCA does not remove the existing IPsec tunnels and users can still access intranet resources across the DirectAccess server by specifying IPv6 addresses rather than names.
-
-The ability to disconnect allows users to specify single-label, unqualified names (such as “PRINTSVR”) for local resources when connected to a different intranet and for temporary access to intranet resources when network location detection has not correctly determined that the DirectAccess client computer is connected to its own intranet.
-
-To restore the DirectAccess rules to the NRPT and resume normal DirectAccess functionality, the user clicks Connect.
-
-Note
-If the DirectAccess client computer is on the intranet and has correctly determined its network location, the Disconnect option has no effect because the rules for DirectAccess are already removed from the NRPT.
-
-If this setting is not configured, users do not have Connect or Disconnect options.
-
- IPsec Tunnel Endpoints
- Specifies the IPv6 addresses of the endpoints of the Internet Protocol security (IPsec) tunnels that enable DirectAccess. NCA attempts to access the resources that are specified in the Corporate Resources setting through these configured tunnel endpoints.
-
-By default, NCA uses the same DirectAccess server that the DirectAccess client computer connection is using. In default configurations of DirectAccess, there are typically two IPsec tunnel endpoints: one for the infrastructure tunnel and one for the intranet tunnel. You should configure one endpoint for each tunnel.
-
-Each entry consists of the text PING: followed by the IPv6 address of an IPsec tunnel endpoint. Example: PING:2002:836b:1::836b:1.
-
-You must configure this setting to have complete NCA functionality.
-
- Corporate Resources
- Specifies resources on your intranet that are normally accessible to DirectAccess clients. Each entry is a string that identifies the type of resource and the location of the resource.
-
-Each string can be one of the following types:
-
-- A DNS name or IPv6 address that NCA pings. The syntax is “PING:” followed by a fully qualified domain name (FQDN) that resolves to an IPv6 address, or an IPv6 address. Examples: PING:myserver.corp.contoso.com or PING:2002:836b:1::1.
-
-Note
-
-We recommend that you use FQDNs instead of IPv6 addresses wherever possible.
-
-Important
-
-At least one of the entries must be a PING: resource.
-
-- A Uniform Resource Locator (URL) that NCA queries with a Hypertext Transfer Protocol (HTTP) request. The contents of the web page do not matter. The syntax is “HTTP:” followed by a URL. The host portion of the URL must resolve to an IPv6 address of a Web server or contain an IPv6 address. Examples: HTTP:http://myserver.corp.contoso.com/ or HTTP:http://2002:836b:1::1/.
-
-- A Universal Naming Convention (UNC) path to a file that NCA checks for existence. The contents of the file do not matter. The syntax is “FILE:” followed by a UNC path. The ComputerName portion of the UNC path must resolve to an IPv6 address or contain an IPv6 address. Examples: FILE:\\myserver\myshare\test.txt or FILE:\\2002:836b:1::1\myshare\test.txt.
-
-You must configure this setting to have complete NCA functionality.
-
-
- Custom Commands
- Specifies commands configured by the administrator for custom logging. These commands will run in addition to default log commands.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Corporate Resources
-
-
-
-
-
-
-
-
- DTEs
-
-
-
-
-
-
-
-
-
- CustomCommands
-
-
-
-
diff --git a/policy_templates/en-US/office16.adml b/policy_templates/en-US/office16.adml
deleted file mode 100644
index 605d5b3..0000000
Binary files a/policy_templates/en-US/office16.adml and /dev/null differ
diff --git a/policy_templates/en-US/onent16.adml b/policy_templates/en-US/onent16.adml
deleted file mode 100644
index 5374d05..0000000
Binary files a/policy_templates/en-US/onent16.adml and /dev/null differ
diff --git a/policy_templates/en-US/outlk16.adml b/policy_templates/en-US/outlk16.adml
deleted file mode 100644
index f1cac18..0000000
Binary files a/policy_templates/en-US/outlk16.adml and /dev/null differ
diff --git a/policy_templates/en-US/pca.adml b/policy_templates/en-US/pca.adml
deleted file mode 100644
index 113620a..0000000
--- a/policy_templates/en-US/pca.adml
+++ /dev/null
@@ -1,65 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
-
-
-
- Application Compatibility Diagnostics
-
-
-
- Detection, Troubleshooting and Resolution
- Detection and Troubleshooting Only
-
-
-
- Notify blocked drivers
- Detect application failures caused by deprecated Windows DLLs
- Detect application failures caused by deprecated COM objects
- Detect application install failures
- Detect applications unable to launch installers under UAC
- Detect application installers that need to be run as administrator
- Detect compatibility issues for applications and drivers
-
-
-
- This setting exists only for backward compatibility, and is not valid for this version of Windows. To configure the Program Compatibility Assistant, use the 'Turn off Program Compatibility Assistant' setting under Computer Configuration\Administrative Templates\Windows Components\Application Compatibility.
- This setting exists only for backward compatibility, and is not valid for this version of Windows. To configure the Program Compatibility Assistant, use the 'Turn off Program Compatibility Assistant' setting under Computer Configuration\Administrative Templates\Windows Components\Application Compatibility.
- This setting exists only for backward compatibility, and is not valid for this version of Windows. To configure the Program Compatibility Assistant, use the 'Turn off Program Compatibility Assistant' setting under Computer Configuration\Administrative Templates\Windows Components\Application Compatibility.
- This setting exists only for backward compatibility, and is not valid for this version of Windows. To configure the Program Compatibility Assistant, use the 'Turn off Program Compatibility Assistant' setting under Computer Configuration\Administrative Templates\Windows Components\Application Compatibility.
- This setting exists only for backward compatibility, and is not valid for this version of Windows. To configure the Program Compatibility Assistant, use the 'Turn off Program Compatibility Assistant' setting under Computer Configuration\Administrative Templates\Windows Components\Application Compatibility.
- This setting exists only for backward compatibility, and is not valid for this version of Windows. To configure the Program Compatibility Assistant, use the 'Turn off Program Compatibility Assistant' setting under Computer Configuration\Administrative Templates\Windows Components\Application Compatibility.
-
- This policy setting configures the Program Compatibility Assistant (PCA) to diagnose failures with application and driver compatibility.
-
-If you enable this policy setting, the PCA is configured to detect failures during application installation, failures during application runtime, and drivers blocked due to compatibility issues. When failures are detected, the PCA will provide options to run the application in a compatibility mode or get help online through a Microsoft website.
-
-If you disable this policy setting, the PCA does not detect compatibility issues for applications and drivers.
-
-If you do not configure this policy setting, the PCA is configured to detect failures during application installation, failures during application runtime, and drivers blocked due to compatibility issues.
-
-Note: This policy setting has no effect if the "Turn off Program Compatibility Assistant" policy setting is enabled. The Diagnostic Policy Service (DPS) and Program Compatibility Assistant Service must be running for the PCA to run. These services can be configured by using the Services snap-in to the Microsoft Management Console.
-
-
-
-
-
-
- Scenario Execution Level
-
-
- Scenario Execution Level
-
-
- Scenario Execution Level
-
-
- Scenario Execution Level
-
-
-
-
diff --git a/policy_templates/en-US/performanceperftrack.adml b/policy_templates/en-US/performanceperftrack.adml
deleted file mode 100644
index d054aa0..0000000
--- a/policy_templates/en-US/performanceperftrack.adml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Windows Performance PerfTrack
- This policy setting specifies whether to enable or disable tracking of responsiveness events.
-
-If you enable this policy setting, responsiveness events are processed and aggregated. The aggregated data will be transmitted to Microsoft through SQM.
-
-if you disable this policy setting, responsiveness events are not processed.
-
-If you do not configure this policy setting, the DPS will enable Windows Performance PerfTrack by default.
-
- Enable/Disable PerfTrack
-
-
-
diff --git a/policy_templates/en-US/ppt16.adml b/policy_templates/en-US/ppt16.adml
deleted file mode 100644
index 0e47029..0000000
Binary files a/policy_templates/en-US/ppt16.adml and /dev/null differ
diff --git a/policy_templates/en-US/proj16.adml b/policy_templates/en-US/proj16.adml
deleted file mode 100644
index df93c9a..0000000
Binary files a/policy_templates/en-US/proj16.adml and /dev/null differ
diff --git a/policy_templates/en-US/pub16.adml b/policy_templates/en-US/pub16.adml
deleted file mode 100644
index aa1da08..0000000
Binary files a/policy_templates/en-US/pub16.adml and /dev/null differ
diff --git a/policy_templates/en-US/sam.adml b/policy_templates/en-US/sam.adml
deleted file mode 100644
index 6f3891a..0000000
--- a/policy_templates/en-US/sam.adml
+++ /dev/null
@@ -1,47 +0,0 @@
-
-
-
- SAM Settings
- Configuration settings for the Security Account Manager
-
-
- SAM
- Security Account Manager
- Configure validation of ROCA-vulnerable WHfB keys during authentication
- Ignore ROCA-vulnerable WHfB keys
- Audit ROCA-vulnerable WHfB keys on use
- Block ROCA-vulnerable WHfB keys on use
- This policy setting allows you to configure how domain controllers handle Windows Hello for Business (WHfB) keys that are vulnerable to the "Return of Coppersmith's attack" (ROCA) vulnerability.
-
-For more information on the ROCA vulnerability, please see:
-
-https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-15361
-
-https://en.wikipedia.org/wiki/ROCA_vulnerability
-
-If you enable this policy setting the following options are supported:
-
-Ignore: during authentication the domain controller will not probe any WHfB keys for the ROCA vulnerability.
-
-Audit: during authentication the domain controller will emit audit events for WHfB keys that are subject to the ROCA vulnerability (authentications will still succeed).
-
-Block: during authentication the domain controller will block the use of WHfB keys that are subject to the ROCA vulnerability (authentications will fail).
-
-This setting only takes effect on domain controllers.
-
-If not configured, domain controllers will default to using their local configuration. The default local configuration is Audit.
-
-A reboot is not required for changes to this setting to take effect.
-
-Note: to avoid unexpected disruptions this setting should not be set to Block until appropriate mitigations have been performed, for example patching of vulnerable TPMs.
-
-More information is available at https://go.microsoft.com/fwlink/?linkid=2116430.
-
-
-
-
- Options for handling ROCA-vulnerable WHfB keys:
-
-
-
-
diff --git a/policy_templates/en-US/sdiageng.adml b/policy_templates/en-US/sdiageng.adml
deleted file mode 100644
index 94d7b32..0000000
--- a/policy_templates/en-US/sdiageng.adml
+++ /dev/null
@@ -1,36 +0,0 @@
-
-
-
- Scripted Diagnostics
- Scripted Diagnostics
-
-
- Scripted Diagnostics
- Configure Security Policy for Scripted Diagnostics
- This policy setting determines whether scripted diagnostics will execute diagnostic packages that are signed by untrusted publishers.
-
-If you enable this policy setting, the scripted diagnostics execution engine validates the signer of any diagnostic package and runs only those signed by trusted publishers.
-
-If you disable or do not configure this policy setting, the scripted diagnostics execution engine runs all digitally signed packages.
-
- Troubleshooting: Allow users to access and run Troubleshooting Wizards
- This policy setting allows users to access and run the troubleshooting tools that are available in the Troubleshooting Control Panel and to run the troubleshooting wizard to troubleshoot problems on their computers.
-
-If you enable or do not configure this policy setting, users can access and run the troubleshooting tools from the Troubleshooting Control Panel.
-
-If you disable this policy setting, users cannot access or run the troubleshooting tools from the Control Panel.
-
-Note that this setting also controls a user's ability to launch standalone troubleshooting packs such as those found in .diagcab files.
-
-
- Troubleshooting: Allow users to access online troubleshooting content on Microsoft servers from the Troubleshooting Control Panel (via the Windows Online Troubleshooting Service - WOTS)
- This policy setting allows users who are connected to the Internet to access and search troubleshooting content that is hosted on Microsoft content servers. Users can access online troubleshooting content from within the Troubleshooting Control Panel UI by clicking "Yes" when they are prompted by a message that states, "Do you want the most up-to-date troubleshooting content?"
-
-If you enable or do not configure this policy setting, users who are connected to the Internet can access and search troubleshooting content that is hosted on Microsoft content servers from within the Troubleshooting Control Panel user interface.
-
-If you disable this policy setting, users can only access and search troubleshooting content that is available locally on their computers, even if they are connected to the Internet. They are prevented from connecting to the Microsoft servers that host the Windows Online Troubleshooting Service.
-
-
-
-
-
diff --git a/policy_templates/en-US/sdiagschd.adml b/policy_templates/en-US/sdiagschd.adml
deleted file mode 100644
index f40042f..0000000
--- a/policy_templates/en-US/sdiagschd.adml
+++ /dev/null
@@ -1,32 +0,0 @@
-
-
-
- Scheduled Diagnostics
- Scheduled Diagnostics
-
-
- Scheduled Maintenance
- Configure Scheduled Maintenance Behavior
- Determines whether scheduled diagnostics will run to proactively detect and resolve system problems.
-
-If you enable this policy setting, you must choose an execution level. If you choose detection and troubleshooting only, Windows will periodically detect and troubleshoot problems. The user will be notified of the problem for interactive resolution.
-
-If you choose detection, troubleshooting and resolution, Windows will resolve some of these problems silently without requiring user input.
-
-If you disable this policy setting, Windows will not be able to detect, troubleshoot or resolve problems on a scheduled basis.
-
-If you do not configure this policy setting, local troubleshooting preferences will take precedence, as configured in the control panel. If no local troubleshooting preference is configured, scheduled diagnostics are enabled for detection, troubleshooting and resolution by default.
-
-No reboots or service restarts are required for this policy to take effect: changes take effect immediately.
-
-This policy setting will only take effect when the Task Scheduler service is in the running state. When the service is stopped or disabled, scheduled diagnostics will not be executed. The Task Scheduler service can be configured with the Services snap-in to the Microsoft Management Console.
- Regular
- Troubleshooting Only
-
-
-
- Execution Level
-
-
-
-
diff --git a/policy_templates/en-US/shapecollector.adml b/policy_templates/en-US/shapecollector.adml
deleted file mode 100644
index 929a58c..0000000
--- a/policy_templates/en-US/shapecollector.adml
+++ /dev/null
@@ -1,20 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Turn off handwriting personalization data sharing
- Turns off data sharing from the handwriting recognition personalization tool.
-
-The handwriting recognition personalization tool tool enables Tablet PC users to adapt handwriting recognition to their own writing style by providing writing samples. The tool can optionally share user writing samples with Microsoft to improve handwriting recognition in future versions of Windows. The tool generates reports and transmits them to Microsoft over a secure connection.
-
-If you enable this policy, Tablet PC users cannot choose to share writing samples from the handwriting recognition personalization tool with Microsoft.
-
-If you disable this policy, Tablet PC user writing samples from the handwriting recognition personalization tool will automatically be shared with Microsoft.
-
-If you do not configure this policy, Tablet PC users can choose whether or not they want to share their writing samples from the handwriting recognition personalization tool with Microsoft.
-
-
-
diff --git a/policy_templates/en-US/srm-fci.adml b/policy_templates/en-US/srm-fci.adml
deleted file mode 100644
index e01291d..0000000
--- a/policy_templates/en-US/srm-fci.adml
+++ /dev/null
@@ -1,93 +0,0 @@
-
-
- File Classification Infrastructure Group Policy Definitions
-
-
-
- Access-Denied Assistance
- File Classification Infrastructure
- File Classification Infrastructure: Display Classification tab in File Explorer
- Enable access-denied assistance on client for all file types
- This Group Policy Setting should be set on Windows clients to enable access-denied assistance for all file types
- This policy setting controls whether the Classification tab is displayed in the Properties dialog box in File Explorer.
-
-The Classification tab enables users to manually classify files by selecting properties from a list. Administrators can define the properties for the organization by using Group Policy, and supplement these with properties defined on individual file servers by using File Classification Infrastructure, which is part of the File Server Resource Manager role service.
-
-If you enable this policy setting, the Classification tab is displayed.
-
-If you disable or do not configure this policy setting, the Classification tab is hidden.
- File Classification Infrastructure: Specify classification properties list
- This policy setting controls which set of properties is available for classifying files on affected computers.
-
-Administrators can define the properties for the organization by using Active Directory Domain Services (AD DS), and then group these properties into lists. Administrators can supplement these properties on individual file servers by using File Classification Infrastructure, which is part of the File Server Resource Manager role service.
-
-If you enable this policy setting, you can select which list of properties is available for classification on the affected computers.
-
-If you disable or do not configure this policy setting, the Global Resource Property List in AD DS provides the default set of properties.
- Customize message for Access Denied errors
- This policy setting specifies the message that users see when they are denied access to a file or folder. You can customize the Access Denied message to include additional text and links. You can also provide users with the ability to send an email to request access to the file or folder to which they were denied access.
-
-If you enable this policy setting, users receive a customized Access Denied message from the file servers on which this policy setting is applied.
-
-If you disable this policy setting, users see a standard Access Denied message that doesn't provide any of the functionality controlled by this policy setting, regardless of the file server configuration.
-
-If you do not configure this policy setting, users see a standard Access Denied message unless the file server is configured to display the customized Access Denied message. By default, users see the standard Access Denied message.
-
- Customize message for File Not Found errors
- This policy setting specifies the message that users see when they receive a File Not Found error. You can customize the File Not Found message to include additional text and links. You can also provide users with the ability to send an email to request help. This enables an administrator to help with File Not Found errors caused by a user not having Read permissions to a folder with access-based enumeration enabled.
-
-If you enable this policy setting, users receive a customized File Not Found message from the file servers on which this policy setting is applied.
-
-If you disable this policy setting, users see a standard File Not Found message that doesn't provide any of the functionality controlled by this policy setting, regardless of the file server configuration.
-
-If you do not configure this policy setting, users see a standard File Not Found message unless the file server is configured to display the customized File Not Found message. By default, users see the standard File Not Found message.
-
-
-
-
-
-
-
-
-
- Display the following message to users who are denied access:
-
- Enable users to request assistance
- Add the following text to the end of the email:
-
-
- Email recipients:
- Folder owner
- File server administrator
-
-
-
-
- Email settings:
- Include device claims
- Include user claims
- Log emails in Application and Services event log
-
-
- File Not Found Message Settings
- File Not Found Message Supplemental Text:
-
- Enable users to request assistance
- File Not Found Email Supplemental Text:
-
-
- Email Recipients
- Folder owner
- File server administrator
-
-
-
-
- Email Settings
- Include device claims
- Include user claims
- Log emails in Applications and Services Logs
-
-
-
-
diff --git a/policy_templates/en-US/tcpip.adml b/policy_templates/en-US/tcpip.adml
deleted file mode 100644
index 52b2694..0000000
--- a/policy_templates/en-US/tcpip.adml
+++ /dev/null
@@ -1,216 +0,0 @@
-
-
-
- TCPIP Group Policy Template file
- This admx file describes policy template for TCPIP components
-
-
- TCPIP Settings
- IPv6 Transition Technologies
-
- Set ISATAP State
- Set ISATAP Router Name
- Set 6to4 State
- Set 6to4 Relay Name
- Set 6to4 Relay Name Resolution Interval
- Set Teredo State
- Set Teredo Server Name
- Set Teredo Refresh Rate
- Set Teredo Client Port
- Set Teredo Default Qualified
-
- Default State
- Enabled State
- Disabled State
- Client
- Enterprise Client
- Set IP-HTTPS State
- IP-HTTPS Url
-
- This policy setting allows you to configure Intra-Site Automatic Tunnel Addressing Protocol (ISATAP), an address-to-router and host-to-host, host-to-router and router-to-host automatic tunneling technology that is used to provide unicast IPv6 connectivity between IPv6 hosts across an IPv4 intranet.
-
-If you disable or do not configure this policy setting, the local host setting is used.
-
-If you enable this policy setting, you can configure ISATAP with one of the following settings:
-
-Policy Default State: No ISATAP interfaces are present on the host.
-
-Policy Enabled State: If the ISATAP name is resolved successfully, the host will have ISATAP configured with a link-local address and an address for each prefix received from the ISATAP router through stateless address auto-configuration. If the ISATAP name is not resolved successfully, the host will have an ISATAP interface configured with a link-local address.
-
-Policy Disabled State: No ISATAP interfaces are present on the host.
-
-
-
- This policy setting allows you to specify a router name or Internet Protocol version 4 (IPv4) address for an ISATAP router.
-
-If you enable this policy setting, you can specify a router name or IPv4 address for an ISATAP router. If you enter an IPv4 address of the ISATAP router in the text box, DNS services are not required.
-
-If you disable or do not configure this policy setting, the local host setting is used.
-
-
-
-
- This policy setting allows you to configure 6to4, an address assignment and router-to-router automatic tunneling technology that is used to provide unicast IPv6 connectivity between IPv6 sites and hosts across the IPv4 Internet. 6to4 uses the global address prefix: 2002:WWXX:YYZZ::/48 in which the letters are a hexadecimal representation of the global IPv4 address (w.x.y.z) assigned to a site.
-
-If you disable or do not configure this policy setting, the local host setting is used.
-
-If you enable this policy setting, you can configure 6to4 with one of the following settings:
-
-Policy Default State: 6to4 is turned off and connectivity with 6to4 will not be available.
-
-Policy Enabled State: If a global IPv4 address is present, the host will have a 6to4 interface. If no global IPv4 address is present, the host will not have a 6to4 interface.
-
-Policy Disabled State: 6to4 is turned off and connectivity with 6to4 will not be available.
-
-
-
- This policy setting allows you to specify a 6to4 relay name for a 6to4 host. A 6to4 relay is used as a default gateway for IPv6 network traffic sent by the 6to4 host. The 6to4 relay name setting has no effect if 6to4 connectivity is not available on the host.
-
-If you enable this policy setting, you can specify a relay name for a 6to4 host.
-
-If you disable or do not configure this policy setting, the local host setting is used, and you cannot specify a relay name for a 6to4 host.
-
-
-
- This policy setting allows you to specify the interval at which the relay name is resolved. The 6to4 relay name resolution interval setting has no effect if 6to4 connectivity is not available on the host.
-
-If you enable this policy setting, you can specify the value for the duration at which the relay name is resolved periodically.
-
-If you disable or do not configure this policy setting, the local host setting is used.
-
-
-
- This policy setting allows you to configure Teredo, an address assignment and automatic tunneling technology that provides unicast IPv6 connectivity across the IPv4 Internet.
-
-If you disable or do not configure this policy setting, the local host settings are used.
-
-If you enable this policy setting, you can configure Teredo with one of the following settings:
-
-Default: The default state is "Client."
-
-Disabled: No Teredo interfaces are present on the host.
-
-Client: The Teredo interface is present only when the host is not on a network that includes a domain controller.
-
-Enterprise Client: The Teredo interface is always present, even if the host is on a network that includes a domain controller.
-
-
-
- This policy setting allows you to specify the name of the Teredo server. This server name will be used on the Teredo client computer where this policy setting is applied.
-
-If you enable this policy setting, you can specify a Teredo server name that applies to a Teredo client.
-
-If you disable or do not configure this policy setting, the local settings on the computer are used to determine the Teredo server name.
-
-
-
- This policy setting allows you to configure the Teredo refresh rate.
-
-Note: On a periodic basis (by default, every 30 seconds), Teredo clients send a single Router Solicitation packet to the Teredo server. The Teredo server sends a Router Advertisement Packet in response. This periodic packet refreshes the IP address and UDP port mapping in the translation table of the Teredo client's NAT device.
-
-If you enable this policy setting, you can specify the refresh rate. If you choose a refresh rate longer than the port mapping in the Teredo client's NAT device, Teredo might stop working or connectivity might be intermittent.
-
-If you disable or do not configure this policy setting, the refresh rate is configured using the local settings on the computer. The default refresh rate is 30 seconds.
-
-
-
- This policy setting allows you to select the UDP port the Teredo client will use to send packets. If you leave the default of 0, the operating system will select a port (recommended). If you select a UDP port that is already in use by a system, the Teredo client will fail to initialize.
-
-If you enable this policy setting, you can customize a UDP port for the Teredo client.
-
-If you disable or do not configure this policy setting, the local host setting is used.
-
-
-
- This policy setting allows you to set Teredo to be ready to communicate, a process referred to as qualification. By default, Teredo enters a dormant state when not in use. The qualification process brings it out of a dormant state.
-
-If you disable or do not configure this policy setting, the local host setting is used.
-
-This policy setting contains only one state:
-
-Policy Enabled State: If Default Qualified is enabled, Teredo will attempt qualification immediately and remain qualified if the qualification process succeeds.
-
-
- This policy setting allows you to configure IP-HTTPS, a tunneling technology that uses the HTTPS protocol to provide IP connectivity to a remote network.
-
-If you disable or do not configure this policy setting, the local host settings are used.
-
-If you enable this policy setting, you can specify an IP-HTTPS server URL. You will be able to configure IP-HTTPS with one of the following settings:
-
-Policy Default State: The IP-HTTPS interface is used when there are no other connectivity options.
-
-Policy Enabled State: The IP-HTTPS interface is always present, even if the host has other connectivity options.
-
-Policy Disabled State: No IP-HTTPS interfaces are present on the host.
-
-
-
- Parameters
- Set Window Scaling Heuristics State
- This policy setting allows you to configure Window Scaling Heuristics. Window Scaling Heuristics is an algorithm to identify connectivity and throughput problems caused by many Firewalls and other middle boxes that don't interpret Window Scaling option correctly.
-
-If you do not configure this policy setting, the local host settings are used.
-
-If you enable this policy setting, Window Scaling Heuristics will be enabled and system will try to identify connectivity and throughput problems and take appropriate measures.
-
-If you disable this policy setting, Window Scaling Heuristics will be disabled and system will not try to identify connectivity and throughput problems casued by Firewalls or other middle boxes.
-
-
-
- Set IP Stateless Autoconfiguration Limits State
- This policy setting allows you to configure IP Stateless Autoconfiguration Limits.
-
-If you enable or do not configure this policy setting, IP Stateless Autoconfiguration Limits will be enabled and system will limit the number of autoconfigured addresses and routes.
-
-If you disable this policy setting, IP Stateless Autoconfiguration Limits will be disabled and system will not limit the number of autoconfigured addresses and routes.
-
-
-
-
-
-
-
-
- Select from the following states:
-
-
-
-
-
-
-
-
-
- The setting allows you to customize the 6to4 Relay Name Resolution interval
- Minutes:
-
-
-
-
-
-
-
-
-
- The setting allows you to customize the Teredo client refresh rate
- The range is 1 to 86400 seconds (1 day).
- Seconds:
-
-
-
- The setting allows you to customize the Teredo client port
- The range is 0 to 65535. Default (recommended) is 0 which is to let the local system pick the port.
-
-
-
-
-
-
-
- Select Interface state from the following options:
-
-
-
-
-
-
diff --git a/policy_templates/en-US/teams16.adml b/policy_templates/en-US/teams16.adml
deleted file mode 100644
index 942badd..0000000
Binary files a/policy_templates/en-US/teams16.adml and /dev/null differ
diff --git a/policy_templates/en-US/terminalserver-server.adml b/policy_templates/en-US/terminalserver-server.adml
deleted file mode 100644
index e790c70..0000000
--- a/policy_templates/en-US/terminalserver-server.adml
+++ /dev/null
@@ -1,213 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Application Compatibility
- Controls application compatibility settings on an RD Session Host server
- Allow time zone redirection
- This policy setting allows you to specify whether the client computer redirects its time zone settings to the Remote Desktop Services session.
-
-If you enable this policy setting, clients that are capable of time zone redirection send their time zone information to the server. The server base time is then used to calculate the current session time (current session time = server base time + client time zone).
-
-If you disable or do not configure this policy setting, the client computer does not redirect its time zone information and the session time zone is the same as the server time zone.
-
-Note: Time zone redirection is possible only when connecting to at least a Microsoft Windows Server 2003 terminal server with a client using RDP 5.1 or later.
-
-
- Do not allow Clipboard redirection
- This policy setting specifies whether to prevent the sharing of Clipboard contents (Clipboard redirection) between a remote computer and a client computer during a Remote Desktop Services session.
-
-You can use this setting to prevent users from redirecting Clipboard data to and from the remote computer and the local computer. By default, Remote Desktop Services allows Clipboard redirection.
-
-If you enable this policy setting, users cannot redirect Clipboard data.
-
-If you disable this policy setting, Remote Desktop Services always allows Clipboard redirection.
-
-If you do not configure this policy setting, Clipboard redirection is not specified at the Group Policy level.
-
-
- Remove remote desktop wallpaper
- This policy setting allows you to specify whether desktop wallpaper is displayed to clients when they are connected to a remote server using RDP.
-
-You can use this setting to enforce the removal of wallpaper during a Remote Desktop Services session.
-
-If you enable this policy setting, wallpaper is not displayed in a Remote Desktop Services session.
-
-If you disable this policy setting, wallpaper is displayed in a Remote Desktop Services session, depending on the client configuration.
-
-If you do not configure this policy setting, Windows Vista displays wallpaper to remote clients connecting through Remote Desktop, depending on the client configuration (see the Experience tab in the Remote Desktop Connection options for more information). Servers running Windows Server 2008 do not display wallpaper by default to Remote Desktop Services sessions.
-
-
- Always show desktop on connection
- This policy setting allows you to specify whether the desktop is always displayed after a client connects to a remote computer or whether an initial program can run. It can require that the desktop be displayed after a client connects to a remote computer, even if an initial program is already specified in the default user profile, Remote Desktop Connection, or through Group Policy.
-
-If you enable this policy setting, the desktop is always displayed when a client connects to a remote computer. This policy setting overrides any initial program policy settings.
-
-If you disable or do not configure this policy setting, an initial program can be specified that runs on the remote computer after the client connects to the remote computer. If an initial program is not specified, the desktop is always displayed on the remote computer after the client connects to the remote computer.
-
-Note: If this policy setting is enabled, then the "Start a program on connection" policy setting is ignored.
-
-
- Allow remote start of unlisted programs
- This policy setting allows you to specify whether remote users can start any program on the RD Session Host server when they start a Remote Desktop Services session, or whether they can only start programs that are listed in the RemoteApp programs list.
-
-You can control which programs on an RD Session Host server can be started remotely by using the RemoteApp Manager on Windows Server 2008 R2 and Windows Server 2008. If you are using Windows Server 2012, you can configure this in the Collection properties sheet by using Server Manager.
-
-By default, only programs in the RemoteApp Programs list can be started when a user starts a Remote Desktop Services session.
-
-If you enable this policy setting, remote users can start any program on the RD Session Host server when they start a Remote Desktop Services session.
-For example, a remote user can do this by specifying the program's executable path at connection time by using the Remote Desktop Connection client.
-
-If you disable or do not configure this policy setting, remote users can only start programs that are listed in the RemoteApp programs list when they start a Remote Desktop Services session.
-
-
- Allow desktop composition for remote desktop sessions
- This policy setting allows you to specify whether desktop composition is allowed for remote desktop sessions. This policy setting does not apply to RemoteApp sessions.
-
-Desktop composition provides the user interface elements of Windows Aero, such as translucent windows, for remote desktop sessions. Because Windows Aero requires additional system and bandwidth resources, allowing desktop composition for remote desktop sessions can reduce connection performance, particularly over slow links, and increase the load on the remote computer.
-
-If you enable this policy setting, desktop composition will be allowed for remote desktop sessions. On the client computer, you can configure desktop composition on the Experience tab in Remote Desktop Connection (RDC) or by using the "allow desktop composition" setting in a Remote Desktop Protocol (.rdp) file. In addition, the client computer must have the necessary hardware to support Windows Aero features.
-
-Note: Additional configuration might be necessary on the remote computer to make Windows Aero features available for remote desktop sessions. For example, the Desktop Experience feature must be installed on the remote computer, and the maximum color depth on the remote computer must be set to 32 bits per pixel. Also, the Themes service must be started on the remote computer.
-
-If you disable or do not configure this policy setting, desktop composition is not allowed for remote desktop sessions, even if desktop composition is enabled in RDC or in the .rdp file.
-
-
- Use RD Connection Broker load balancing
- This policy setting allows you to specify whether to use the RD Connection Broker load balancing feature to balance the load between servers in an RD Session Host server farm.
-
-If you enable this policy setting, RD Connection Broker redirects users who do not have an existing session to the RD Session Host server in the farm with the fewest sessions. Redirection behavior for users with existing sessions is not affected. If the server is configured to use RD Connection Broker, users who have an existing session are redirected to the RD Session Host server where their session exists.
-
-If you disable this policy setting, users who do not have an existing session log on to the first RD Session Host server to which they connect.
-
-If you do not configure this policy setting, you can configure the RD Session Host server to participate in RD Connection Broker load balancing by using the Remote Desktop Session Host Configuration tool or the Remote Desktop Services WMI provider.
-
-Note: If you enable this policy setting, you must also enable the Join RD Connection Broker, the Configure RD Connection Broker farm name, and the Configure RD Connection Broker server name policy settings.
-
-
- Redirect only the default client printer
- This policy setting allows you to specify whether the default client printer is the only printer redirected in Remote Desktop Services sessions.
-
-If you enable this policy setting, only the default client printer is redirected in Remote Desktop Services sessions.
-
-If you disable or do not configure this policy setting, all client printers are redirected in Remote Desktop Services sessions.
-
-
- Set time limit for logoff of RemoteApp sessions
- This policy setting allows you to specify how long a user's RemoteApp session will remain in a disconnected state after closing all RemoteApp programs before the session is logged off from the RD Session Host server.
-
-By default, if a user closes a RemoteApp program, the session is disconnected from the RD Session Host server, but it is not logged off.
-
-If you enable this policy setting, when a user closes the last running RemoteApp program associated with a session, the RemoteApp session will remain in a disconnected state until the time limit that you specify is reached. When the time limit specified is reached, the RemoteApp session will be logged off from the RD Session Host server. If the user starts a RemoteApp program before the time limit is reached, the user will reconnect to the disconnected session on the RD Session Host server.
-
-If you disable or do not configure this policy setting, when a user closes the last RemoteApp program, the session will be disconnected from the RD Session Host server but it is not logged off.
-
-Note: This policy setting appears in both Computer Configuration and User Configuration. If both policy settings are configured, the Computer Configuration policy setting takes precedence.
-
-
- 1 minute
- 5 minutes
- 10 minutes
- 15 minutes
- 30 minutes
- 1 hour
- 2 hours
- 3 hours
- 6 hours
- 8 hours
- 12 hours
- 16 hours
- 18 hours
- 1 day
- 2 days
- 3 days
- 4 days
- 5 days
- Immediately
-
- Do not allow font smoothing
- This policy setting allows you to specify whether font smoothing is allowed for remote connections.
-
-Font smoothing provides ClearType functionality for a remote connection. ClearType is a technology for displaying computer fonts so that they appear clear and smooth, especially when you are using an LCD monitor. Because font smoothing requires additional bandwidth resources, not allowing font smoothing for remote connections can improve connection performance, particularly over slow links.
-
-By default, font smoothing is allowed for remote connections. You can configure font smoothing on the Experience tab in Remote Desktop Connection (RDC) or by using the "allow font smoothing" setting in a Remote Desktop Protocol (.rdp) file.
-
-If you enable this policy setting, font smoothing will not be allowed for remote connections, even if font smoothing is enabled in RDC or in the .rdp file.
-
-If you disable or do not configure this policy setting, font smoothing is allowed for remote connections.
-
-
- Turn on Remote Desktop IP Virtualization
- This policy setting specifies whether Remote Desktop IP Virtualization is turned on.
-By default, Remote Desktop IP Virtualization is turned off.
-
-If you enable this policy setting, Remote Desktop IP Virtualization is turned on. You can select the mode in which this setting is applied. If you are using Per Program mode, you must enter a list of programs to use virtual IP addresses. List each program on a separate line (do not enter any blank lines between programs). For example:
-
-explorer.exe
-mstsc.exe
-
-If you disable or do not configure this policy setting, Remote Desktop IP Virtualization is turned off.
-
-
- Per Session
- Per Program
- Select the network adapter to be used for Remote Desktop IP Virtualization
- This policy setting specifies the IP address and network mask that corresponds to the network adapter used for virtual IP addresses. The IP address and network mask should be entered in Classless Inter-Domain Routing notation; for example, 192.0.2.96/24.
-
-If you enable this policy setting, the specified IP address and network mask are used to select the network adapter used for the virtual IP addresses.
-
-If you disable or do not configure this policy setting, Remote Desktop IP Virtualization is turned off. A network adapter must be configured for Remote Desktop IP Virtualization to work.
-
-
- Do not use Remote Desktop Session Host server IP address when virtual IP address is not available
- This policy setting specifies whether a session uses the IP address of the Remote Desktop Session Host server if a virtual IP address is not available.
-
-If you enable this policy setting, the IP address of the RD Session Host server is not used if a virtual IP is not available. The session will not have network connectivity.
-
-If you disable or do not configure this policy setting, the IP address of the RD Session Host server is used if a virtual IP is not available.
-
-
- Turn off Fair Share CPU Scheduling
- Fair Share CPU Scheduling dynamically distributes processor time across all Remote Desktop Services sessions on the same RD Session Host server, based on the number of sessions and the demand for processor time within each session.
-
-If you enable this policy setting, Fair Share CPU Scheduling is turned off.
-
-If you disable or do not configure this policy setting, Fair Share CPU Scheduling is turned on.
-
-
- Turn off Windows Installer RDS Compatibility
- This policy setting specifies whether Windows Installer RDS Compatibility runs on a per user basis for fully installed applications. Windows Installer allows one instance of the msiexec process to run at a time. By default, Windows Installer RDS Compatibility is turned on.
-
-If you enable this policy setting, Windows Installer RDS Compatibility is turned off, and only one instance of the msiexec process can run at a time.
-
-If you disable or do not configure this policy setting, Windows Installer RDS Compatibility is turned on, and multiple per user application installation requests are queued and handled by the msiexec process in the order in which they are received.
-
-
- Remote Desktop Virtualization Host
- Controls configuration of an RD Virtualization Host server
-
-
-
-
-
- RemoteApp session logoff delay:
-
-
-
-
-
- The format is [IP address]/[network mask]. For Example:192.0.2.96/24
-
-
- Turn on Remote Desktop IP Virtualization mode:
- Assign virtual IP addresses to these programs:
- If you are listing more than one program, list each program on a separate line (do not enter any blank lines between programs). For example:
- explorer.exe
-mstsc.exe
-
-
-
-
diff --git a/policy_templates/en-US/visio16.adml b/policy_templates/en-US/visio16.adml
deleted file mode 100644
index 2f53c3d..0000000
Binary files a/policy_templates/en-US/visio16.adml and /dev/null differ
diff --git a/policy_templates/en-US/windowsmediadrm.adml b/policy_templates/en-US/windowsmediadrm.adml
deleted file mode 100644
index d1a534d..0000000
--- a/policy_templates/en-US/windowsmediadrm.adml
+++ /dev/null
@@ -1,19 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Prevent Windows Media DRM Internet Access
- Prevents Windows Media Digital Rights Management (DRM) from accessing the Internet (or intranet).
-
-When enabled, Windows Media DRM is prevented from accessing the Internet (or intranet) for license acquisition and security upgrades.
-
-When this policy is enabled, programs are not able to acquire licenses for secure content, upgrade Windows Media DRM security components, or restore backed up content licenses. Secure content that is already licensed to the local computer will continue to play. Users are also able to protect music that they copy from a CD and play this protected content on their computer, since the license is generated locally in this scenario.
-
-When this policy is either disabled or not configured, Windows Media DRM functions normally and will connect to the Internet (or intranet) to acquire licenses, download security upgrades, and perform license restoration.
- Windows Media Digital Rights Management
-
-
-
diff --git a/policy_templates/en-US/windowsmediaplayer.adml b/policy_templates/en-US/windowsmediaplayer.adml
deleted file mode 100644
index 877cb9d..0000000
--- a/policy_templates/en-US/windowsmediaplayer.adml
+++ /dev/null
@@ -1,267 +0,0 @@
-
-
-
- enter display name here
- enter description here
-
-
- Autodetect
- Configure HTTP Proxy
- This policy setting allows you to specify the HTTP proxy settings for Windows Media Player.
-
-If you enable this policy setting, select one of the following proxy types:
-
-- Autodetect: the proxy settings are automatically detected.
-- Custom: unique proxy settings are used.
-- Use browser proxy settings: browser's proxy settings are used.
-
-If the Custom proxy type is selected, the rest of the options on the Setting tab must be specified because no default settings are used for the proxy. The options are ignored if Autodetect or Browser is selected.
-
-The Configure button on the Network tab in the Player is not available for the HTTP protocol and the proxy cannot be configured. If the "Hide network tab" policy setting is also enabled, the entire Network tab is hidden.
-
-This policy is ignored if the "Streaming media protocols" policy setting is enabled and HTTP is not selected.
-
-If you disable this policy setting, the HTTP proxy server cannot be used and the user cannot configure the HTTP proxy.
-
-If you do not configure this policy setting, users can configure the HTTP proxy settings.
-
- Configure MMS Proxy
- This policy setting allows you to specify the MMS proxy settings for Windows Media Player.
-
-If you enable this policy setting, select one of the following proxy types:
-
-- Autodetect: the proxy settings are automatically detected.
-- Custom: unique proxy settings are used.
-
-If the Custom proxy type is selected, the rest of the options on the Setting tab must be specified; otherwise, the default settings are used. The options are ignored if Autodetect is selected.
-
-The Configure button on the Network tab in the Player is not available and the protocol cannot be configured. If the "Hide network tab" policy setting is also enabled, the entire Network tab is hidden.
-
-This policy setting is ignored if the "Streaming media protocols" policy setting is enabled and Multicast is not selected.
-
-If you disable this policy setting, the MMS proxy server cannot be used and users cannot configure the MMS proxy settings.
-
-If you do not configure this policy setting, users can configure the MMS proxy settings.
- Configure RTSP Proxy
- This policy setting allows you to specify the RTSP proxy settings for Windows Media Player.
-
-If you enable this policy setting, select one of the following proxy types:
-
-- Autodetect: the proxy settings are automatically detected.
-- Custom: unique proxy settings are used.
-
-If the Custom proxy type is selected, the rest of the options on the Setting tab must be specified; otherwise, the default settings are used. The options are ignored if Autodetect is selected.
-
-The Configure button on the Network tab in the Player is not available and the protocol cannot be configured. If the "Hide network tab" policy setting is also enabled, the entire Network tab is hidden.
-
-If you disable this policy setting, the RTSP proxy server cannot be used and users cannot change the RTSP proxy settings.
-
-If you do not configure this policy setting, users can configure the RTSP proxy settings.
- Custom
- Default
- Prevent Automatic Updates
- This policy setting allows you to turn off do not show first use dialog boxes.
-
-If you enable this policy setting, the Privacy Options and Installation Options dialog boxes are prevented from being displayed the first time a user starts Windows Media Player.
-
-This policy setting prevents the dialog boxes which allow users to select privacy, file types, and other desktop options from being displayed when the Player is first started. Some of the options can be configured by using other Windows Media Player group policies.
-
-If you disable or do not configure this policy setting, the dialog boxes are displayed when the user starts the Player for the first time.
- Hide Network Tab
- Do Not Show First Use Dialog Boxes
- This policy setting allows you to prevent the anchor window from being displayed when Windows Media Player is in skin mode.
-
-If you enable this policy setting, the anchor window is hidden when the Player is in skin mode. In addition, the option on the Player tab in the Player that enables users to choose whether the anchor window displays is not available.
-
-If you disable or do not configure this policy setting, users can show or hide the anchor window when the Player is in skin mode by using the Player tab in the Player.
-
-If you do not configure this policy setting, and the "Set and lock skin" policy setting is enabled, some options in the anchor window are not available.
- Prevents the anchor window from being displayed when Windows Media Player is in skin mode.
-
-This policy hides the anchor window when the Player is in skin mode. In addition, the option on the Player tab in the Player that enables users to choose whether the anchor window displays is not available.
-
-When this policy is not configured or disabled, users can show or hide the anchor window when the Player is in skin mode by using the Player tab in the Player.
-
-When this policy is not configured and the Set and Lock Skin policy is enabled, some options in the anchor window are not available.
- Do Not Show Anchor
- Prevent Video Smoothing
- This policy setting allows you to prevent video smoothing from occurring.
-
-If you enable this policy setting, video smoothing is prevented, which can improve video playback on computers with limited resources. In addition, the Use Video Smoothing check box in the Video Acceleration Settings dialog box in the Player is cleared and is not available.
-
-If you disable this policy setting, video smoothing occurs if necessary, and the Use Video Smoothing check box is selected and is not available.
-
-If you do not configure this policy setting, video smoothing occurs if necessary. Users can change the setting for the Use Video Smoothing check box.
-
-Video smoothing is available only on the Windows XP Home Edition and Windows XP Professional operating systems.
- Allow Screen Saver
- This policy setting allows a screen saver to interrupt playback.
-
-If you enable this policy setting, a screen saver is displayed during playback of digital media according to the options selected on the Screen Saver tab in the Display Properties dialog box in Control Panel. The Allow screen saver during playback check box on the Player tab in the Player is selected and is not available.
-
-If you disable this policy setting, a screen saver does not interrupt playback even if users have selected a screen saver. The Allow screen saver during playback check box is cleared and is not available.
-
-If you do not configure this policy setting, users can change the setting for the Allow screen saver during playback check box.
- This policy setting allows you to prevent Windows Media Player from downloading codecs.
-
-If you enable this policy setting, the Player is prevented from automatically downloading codecs to your computer. In addition, the Download codecs automatically check box on the Player tab in the Player is not available.
-
-If you disable this policy setting, codecs are automatically downloaded and the Download codecs automatically check box is not available.
-
-If you do not configure this policy setting, users can change the setting for the Download codecs automatically check box.
- This policy setting allows you to hide the Network tab.
-
-If you enable this policy setting, the Network tab in Windows Media Player is hidden. The default network settings are used unless the user has previously defined network settings for the Player.
-
-If you disable or do not configure this policy setting, the Network tab appears and users can use it to configure network settings.
- Hide Privacy Tab
- This policy setting allows you to hide the Privacy tab in Windows Media Player.
-
-If you enable this policy setting, the "Update my music files (WMA and MP3 files) by retrieving missing media information from the Internet" check box on the Media Library tab is available, even though the Privacy tab is hidden, unless the "Prevent music file media information retrieval" policy setting is enabled.
-
-The default privacy settings are used for the options on the Privacy tab unless the user changed the settings previously.
-
-If you disable or do not configure this policy setting, the Privacy tab is not hidden, and users can configure any privacy settings not configured by other polices.
- Hide Security Tab
- This policy setting allows you to hide the Security tab in Windows Media Player.
-
-If you enable this policy setting, the default security settings for the options on the Security tab are used unless the user changed the settings previously. Users can still change security and zone settings by using Internet Explorer unless these settings have been hidden or disabled by Internet Explorer policies.
-
-If you disable or do not configure this policy setting, users can configure the security settings on the Security tab.
- Configure Network Buffering
- This policy setting allows you to specify whether network buffering uses the default or a specified number of seconds.
-
-If you enable this policy setting, select one of the following options to specify the number of seconds streaming media is buffered before it is played.
-
-- Custom: the number of seconds, up to 60, that streaming media is buffered.
-- Default: default network buffering is used and the number of seconds that is specified is ignored.
-
-The "Use default buffering" and "Buffer" options on the Performance tab in the Player are not available.
-
-If you disable or do not configure this policy setting, users can change the buffering options on the Performance tab.
- Prevent Codec Download
- Prevent CD and DVD Media Information Retrieval
- This policy setting allows you to prevent media information for CDs and DVDs from being retrieved from the Internet.
-
-If you enable this policy setting, the Player is prevented from automatically obtaining media information from the Internet for CDs and DVDs played by users. In addition, the Retrieve media information for CDs and DVDs from the Internet check box on the Privacy Options tab in the first use dialog box and on the Privacy tab in the Player are not selected and are not available.
-
-If you disable or do not configure this policy setting, users can change the setting of the Retrieve media information for CDs and DVDs from the Internet check box.
- Prevent Media Sharing
- This policy setting allows you to prevent media sharing from Windows Media Player.
-
-If you enable this policy setting, any user on this computer is prevented from sharing digital media content from Windows Media Player with other computers and devices that are on the same network. Media sharing is disabled from Windows Media Player or from programs that depend on the Player's media sharing feature.
-
-If you disable or do not configure this policy setting, anyone using Windows Media Player can turn media sharing on or off.
- Prevent Music File Media Information Retrieval
- This policy setting allows you to prevent media information for music files from being retrieved from the Internet.
-
-If you enable this policy setting, the Player is prevented from automatically obtaining media information for music files such as Windows Media Audio (WMA) and MP3 files from the Internet. In addition, the Update my music files (WMA and MP3 files) by retrieving missing media information from the Internet check box in the first use dialog box and on the Privacy and Media Library tabs in the Player are not selected and are not available.
-
-If you disable or do not configure this policy setting, users can change the setting of the Update my music files (WMA and MP3 files) by retrieving missing media information from the Internet check box.
- Prevent Quick Launch Toolbar Shortcut Creation
- This policy setting allows you to prevent a shortcut for the Player from being added to the Quick Launch bar.
-
-If you enable this policy setting, the user cannot add the shortcut for the Player to the Quick Launch bar.
-
-If you disable or do not configure this policy setting, the user can choose whether to add the shortcut for the Player to the Quick Launch bar.
- Prevent Radio Station Preset Retrieval
- This policy setting allows you to prevent radio station presets from being retrieved from the Internet.
-
-If you enable this policy setting, the Player is prevented from automatically retrieving radio station presets from the Internet and displaying them in Media Library. In addition, presets that exist before the policy is configured are not be updated, and presets a user adds are not be displayed.
-
-If you disable or do not configure this policy setting, the Player automatically retrieves radio station presets from the Internet.
- Prevent Desktop Shortcut Creation
- This policy setting allows you to prevent a shortcut icon for the Player from being added to the user's desktop.
-
-If you enable this policy setting, users cannot add the Player shortcut icon to their desktops.
-
-If you disable or do not configure this policy setting, users can choose whether to add the Player shortcut icon to their desktops.
- Set and Lock Skin
- This policy setting allows you to set and lock Windows Media Player in skin mode, using a specified skin.
-
-If you enable this policy setting, the Player displays only in skin mode using the skin specified in the Skin box on the Setting tab.
-
-You must use the complete file name for the skin (for example, skin_name.wmz), and the skin must be installed in the %programfiles%\Windows Media Player\Skins Folder on a user's computer. If the skin is not installed on a user's computer, or if the Skin box is blank, the Player opens by using the Corporate skin. The only way to specify the Corporate skin is to leave the Skin box blank.
-
-A user has access only to the Player features that are available with the specified skin. Users cannot switch the Player to full mode and cannot choose a different skin.
-
-If you disable or do not configure this policy setting, users can display the Player in full or skin mode and have access to all available features of the Player.
- Windows Media Player 11 for Windows XP or Windows Media Player 11 for Windows Vista or later.
- Windows Media Player for Windows XP and later.
- Windows Media Player 9 Series and later.
- Use browser proxy settings
- Streaming Media Protocols
- This policy setting allows you to specify that Windows Media Player can attempt to use selected protocols when receiving streaming media from a server running Windows Media Services.
-
-If you enable this policy setting, the protocols that are selected on the Network tab of the Player are used to receive a stream initiated through an MMS or RTSP URL from a Windows Media server. If the RSTP/UDP check box is selected, a user can specify UDP ports in the Use ports check box. If the user does not specify UDP ports, the Player uses default ports when using the UDP protocol. This policy setting also specifies that multicast streams can be received if the "Allow the Player to receive multicast streams" check box on the Network tab is selected.
-
-If you enable this policy setting, the administrator must also specify the protocols that are available to users on the Network tab. If the administrator does not specify any protocols, the Player cannot access an MMS or RTSP URL from a Windows Media server. If the "Hide network tab" policy setting is enabled, the entire Network tab is hidden.
-
-If you do not configure this policy setting, users can select the protocols to use on the Network tab.
-
-If you disable this policy setting, the Protocols for MMS URLs and Multicast streams areas of the Network tab are not available and the Player cannot receive an MMS or RTSP stream from a Windows Media server.
- Windows Media Player
- Playback
- User Interface
- Networking
-
-
-
- Proxy type
- The following options apply only to custom proxies.
-
-
-
- Proxy port
- Bypass proxy for local addresses
-
-
-
-
-
- Proxy type
- The following options apply only to custom proxies.
-
-
-
- Proxy port
- Bypass proxy for local addresses
-
-
-
-
-
- Proxy type
- The following options apply only to custom proxies.
-
-
-
- Proxy port
- Bypass proxy for local addresses
-
-
-
-
-
- Buffering Time
- Everything below this line applies to Custom network buffering only.
- Configure Network Buffering
-
-
-
-
-
-
-
- Protocols
- Multicast
- UDP
-
-
-
- TCP
- HTTP
-
-
-
-
diff --git a/policy_templates/en-US/windowsserver.adml b/policy_templates/en-US/windowsserver.adml
deleted file mode 100644
index 463d71e..0000000
--- a/policy_templates/en-US/windowsserver.adml
+++ /dev/null
@@ -1,15 +0,0 @@
-
-
-
- Windows Server 2008 base categories and supported component definitions
- This file contains all the base categories and supported component definitions used by server components.
-
-
-
- At least Windows Server 2008
- At least Windows Server 2003 R2
- Server Components
- Contains settings for server operating system components.
-
-
-
diff --git a/policy_templates/en-US/wlansvc.adml b/policy_templates/en-US/wlansvc.adml
deleted file mode 100644
index b39e88c..0000000
--- a/policy_templates/en-US/wlansvc.adml
+++ /dev/null
@@ -1,62 +0,0 @@
-
-
-
- WLAN Service Group Policy Settings
- WLAN Service Group Policy Settings
-
-
- WLAN Service
- WLAN Media Cost
- WLAN Settings
- Set Cost
- This policy setting configures the cost of Wireless LAN (WLAN) connections on the local machine.
-
-If this policy setting is enabled, a drop-down list box presenting possible cost values will be active. Selecting one of the following values from the list will set the cost of all WLAN connections on the local machine:
-
-- Unrestricted: Use of this connection is unlimited and not restricted by usage charges and capacity constraints.
-
-- Fixed: Use of this connection is not restricted by usage charges and capacity constraints up to a certain data limit.
-
-- Variable: This connection is costed on a per byte basis.
-
-If this policy setting is disabled or is not configured, the cost of Wireless LAN connections is Unrestricted by default.
-
- Unrestricted
- Fixed
- Variable
- Wireless Display
- Require PIN pairing
- This policy applies to Wireless Display connections. This policy means that the use of a PIN for pairing to Wireless Display devices is required rather than optional.
-
-Conversely it means that Push Button is NOT allowed.
-
-If this policy setting is disabled or is not configured, by default Push Button pairing is allowed (but not necessarily preferred).
-
- Prefer PIN pairing
- This policy applies to Wireless Display connections. This policy changes the preference order of the pairing methods.
-
-When enabled, it makes the connections to prefer a PIN for pairing to Wireless Display devices over the Push Button pairing method.
-
-If this policy setting is disabled or is not configured, by default Push Button pairing is preferred (if allowed by other policies).
-
- Allow Windows to automatically connect to suggested open hotspots, to networks shared by contacts, and to hotspots offering paid services
- This policy setting determines whether users can enable the following WLAN settings: "Connect to suggested open hotspots," "Connect to networks shared by my contacts," and "Enable paid services".
-
-"Connect to suggested open hotspots" enables Windows to automatically connect users to open hotspots it knows about by crowdsourcing networks that other people using Windows have connected to.
-
-"Connect to networks shared by my contacts" enables Windows to automatically connect to networks that the user's contacts have shared with them, and enables users on this device to share networks with their contacts.
-
-"Enable paid services" enables Windows to temporarily connect to open hotspots to determine if paid services are available.
-
-If this policy setting is disabled, both "Connect to suggested open hotspots," "Connect to networks shared by my contacts," and "Enable paid services" will be turned off and users on this device will be prevented from enabling them.
-
-If this policy setting is not configured or is enabled, users can choose to enable or disable either "Connect to suggested open hotspots" or "Connect to networks shared by my contacts".
-
-
-
-
- Please select a wlan connection cost value to set:
-
-
-
-
diff --git a/policy_templates/en-US/word16.adml b/policy_templates/en-US/word16.adml
deleted file mode 100644
index 9f6c9d2..0000000
Binary files a/policy_templates/en-US/word16.adml and /dev/null differ
diff --git a/policy_templates/en-US/wwansvc.adml b/policy_templates/en-US/wwansvc.adml
deleted file mode 100644
index 6c37d4e..0000000
--- a/policy_templates/en-US/wwansvc.adml
+++ /dev/null
@@ -1,89 +0,0 @@
-
-
-
- WWAN Service Group Policy Settings
- WWAN Service Group Policy Settings
-
-
- WWAN Service
- WWAN Media Cost
- Set 3G Cost
- This policy setting configures the cost of 3G connections on the local machine.
-
-If this policy setting is enabled, a drop-down list box presenting possible cost values will be active. Selecting one of the following values from the list will set the cost of all 3G connections on the local machine:
-
-- Unrestricted: Use of this connection is unlimited and not restricted by usage charges and capacity constraints.
-
-- Fixed: Use of this connection is not restricted by usage charges and capacity constraints up to a certain data limit.
-
-- Variable: This connection is costed on a per byte basis.
-
-If this policy setting is disabled or is not configured, the cost of 3G connections is Fixed by default.
-
- Set 4G Cost
- This policy setting configures the cost of 4G connections on the local machine.
-
-If this policy setting is enabled, a drop-down list box presenting possible cost values will be active. Selecting one of the following values from the list will set the cost of all 4G connections on the local machine:
-
-- Unrestricted: Use of this connection is unlimited and not restricted by usage charges and capacity constraints.
-
-- Fixed: Use of this connection is not restricted by usage charges and capacity constraints up to a certain data limit.
-
-- Variable: This connection is costed on a per byte basis.
-
-If this policy setting is disabled or is not configured, the cost of 4G connections is Fixed by default.
-
- Unrestricted
- Fixed
- Variable
- WWAN UI Settings
- Set Per-App Cellular Access UI Visibility
- This policy setting configures the visibility of the link to the per-application cellular access control page in the cellular setting UX.
-
-If this policy setting is enabled, a drop-down list box presenting possible values will be active. Select "Hide" or "Show" to hide or show the link to the per-application cellular access control page.
-If this policy setting is disabled or is not configured, the link to the per-application cellular access control page is showed by default.
-
- Hide
- Show
- Cellular Data Access
- User is in control
- Force Allow
- Force Deny
- Let Windows apps access cellular data
- This policy setting specifies whether Windows apps can access cellular data.
-
-You can specify either a default setting for all apps or a per-app setting by specifying a Package Family Name. You can get the Package Family Name for an app by using the Get-AppPackage Windows PowerShell cmdlet. A per-app setting overrides the default setting.
-
-If you choose the "User is in control" option, employees in your organization can decide whether Windows apps can access cellular data by using Settings > Network - Internet > Cellular on the device.
-
-If you choose the "Force Allow" option, Windows apps are allowed to access cellular data and employees in your organization cannot change it.
-
-If you choose the "Force Deny" option, Windows apps are not allowed to access cellular data and employees in your organization cannot change it.
-
-If you disable or do not configure this policy setting, employees in your organization can decide whether Windows apps can access cellular data by using Settings > Network - Internet > Cellular on the device.
-
-If an app is open when this Group Policy object is applied on a device, employees must restart the app or device for the policy changes to be applied to the app.
-
-
-
-
- Please select a 3G connection cost value to set:
-
-
- Please select a 4G connection cost value to set:
-
-
- Please select one option to set:
-
-
- Default for all apps:
- Put user in control of these specific apps (use Package Family Names):
-
- Force allow these specific apps (use Package Family Names):
-
- Force deny these specific apps (use Package Family Names):
-
-
-
-
-