Reset Internet Explorer Settings (REIS) Feature

As our users, or us, browse the Internet and freely click away, we may inadvertently install many different add-ons into Internet Explorer. I was volunteering for an organization this past weekend that provided the volunteer with a desktop. This desktop had:

Bing Search
Google Search
Yahoo Search
Lexmark Status
Amazon.com Search
And something else that I never heard of.

With all these add-ons (and what else I did not see) performance of IE can start to become an issue. One way to get a clean slat for IE to work on is to use the REIS feature. REIS will reset the following IE components to their default settings:

Home Pages
Search scopes
Browsing history
Form data
Password
Appearance settings
Toolbars
ActiveX controls.

Doing this procedure will help provide a more stable browsing experience for your users and prevent messages such as “Internet Explorer has encountered a problem and needs to close.” Here is who you do it.
Exit all programs
Launch just one instance of Internet Explorer
In Internet Explorer, click Tools \ Internet Options.

Click the Advanced tab.
In the Reset Internet Explorer settings at the bottom of the Internet Options window, click Reset.

Click Reset
Click Close
Click OK.
Now close IE and then open IE again. You should be at the default configuration.
You can set Internet Explorer to clean even more information. Before you clicked reset above, you were presented with the option to Delete personal settings. This option Resets home pages, search providers and Accelerators to default settings. Deletes temporary Internet files, history, cookies, web form information, passwords and InPrivate Filtering data.

Comments

How to list all the AD LDS instances on a server

AD LDS allows you to provide directory services to applications that are free of the confines of Active Directory. To list all the AD LDS instances on a server, follow this procedure: Log into the server in question Open a command prompt. Type dsdbutil and press Enter Type List Instances and press Enter . You will receive a list of the instance name, both the LDAP and SSL port numbers, the location of the database, and its status.

How to run GPResult on a remote client with PowerShell

In the past, to run the GPResult command, you would need to either physically visit this client, have the user do it, or use and RDP connection. In all cases, this will disrupt the user. First, you need PowerShell remoting enabled on the target machine. You can do this via Group Policy . Open PowerShell and type this command. Invoke-Command –ScriptBlock {GPResult /r} –ComputerName <ComputerName> Replace <ComputerName> with the name of the target. Remember, the target needs to be online and accessible to you.

Where did a User’s Account Get Locked Out?

Updated: May 15, 2015 When this article was originally published, two extra carriage returns were add causing the code to malfunction. The code below is correct. My client for this week’s PowerShell class had a really interesting question. They needed to know where an account is being locked out at. OK, interesting. Apparently users hop around clients and forget to log off, leading to eventual lock out of their accounts. The accounts can be unlocked, but are then relocked after Active Directory replication. This problem is solved in two parts. The first one is to modify the event auditing on the network. The second part is resolved with PowerShell. The first part involves creating a group policy that will encompass your Domain Controllers. In this GPO, make these changes. Expand Computer Configuration \ Policies \ Windows Settings \ Security Settings \ Advanced Audit Policy Configuration \ Audit Policies \ Account Management Double click User Account Management C...

Jason Yoder, MCT

Search This Blog