Category: At least Windows Server 2008 R2 or Windows 7

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.

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.

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.

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.

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.

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. ps1GPO C: C. cmd C. ps1Assume 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. cmdWithin 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. ps1Within GPO C: C. cmd C. ps1Note: 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) -> LogonUser Configuration -> Policies -> Windows Settings -> Scripts (Logon/Logoff) -> LogoffThis 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.

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. ps1GPO C: C. cmd C. ps1Assume 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. cmdWithin 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. ps1Within GPO C: C. cmd C. ps1Note: 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) -> StartupComputer Configuration -> Policies -> Windows Settings -> Scripts (Startup/Shutdown) -> Shutdown

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.

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.