Поделиться через


HOW TO CONFIGURE TabShutdownDelay USING GROUP POLICY PREFERENCES (GPP) REGISTRY?

In this example, we are using Computer Configuration GPO to target the Internet Explorer TabShutdownDelay registry setting. However, you can perform the same steps at the User Configuration setting from the GPMC console! 

OBJECTIVE: To change the TabShutdownDelay registry key for the computer Group Policy Preferences Registry configuration.

REQUIREMENTS: Be familiar with GPMC.MSC console and Group Policy Preferences.

 

STEPS 1

Open GPMC.MSC console and from the left hand pane, expand: Computer Configuration / Preferences / Windows Settings and Right Click on the Registry object and select New > Collection Item

NOTE: The Collection Item will allow you to better organize the Registry Item Configuration!

STEP 2

Rename the Collection Item to: TabShutdownDelay. Right click and select rename!

STEP 3

Right Click on the newly renamed item and select New > Registry Item

STEP 4

From the New Registry Properties Dialog, mirror the following settings:

Action: Update

Hive: HKEY_LOCAL_MACHINE

Key Path: SOFTWARE\Microsoft\Internet Explorer\MAIN

Value Name: TabShutdownDelay

Value type: REG_DWORD

Value data: 0

 

IMPORTANT: Please note that on 64-Bit Operating Systems, Internet Explorer also uses x86-processes. Therefore you should also include the  Wow6432Node registry-key!

Action: Update

Hive: HKEY_LOCAL_MACHINE

Key Path: SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN

Value Name: TabShutdownDelay

Value type: REG_DWORD

Value data: 0

 

SCREENSHOT:

Apply and OK to configure the policy!

NEXT: Test your GPO

The best way to test the GPO is to go to the client and run the GPUpdate /Force Command and check the Registry key location for changes.[YOU MAY HAVE TO RUN THIS COMMAND USING AN ELEVATED COMMAND PROMPT!]

You should expect to see the following registry entry:

REGISTRY: HKEY_LOCAL_MACHINE\Software\Microsoft\InternetExplorer\Main

NAME: TabShutdownDelay

VALUE: 0 (DECIMAL)

RELATED BLOG POST:  

 

This blog has been provided to you by the IE Support team!