Deploy Internet Explorer 11 today as from January 2016 only the latest version of IE will be supported on the currently supported OS’s such as Windows 7 – 8.1 – 10. You should really deploy IE11 today and start working with compatibility testing for your web applications.
For deploying IE11 you will need a lot of prerequisites fulfilled and you will need to do a lot of work to get it deployed successfully. More or less you will need to do it in four steps:
1. Deploy about 9 prerequisites! You must deploy KB2834140, KB2670838, KB2639308, KB2533623, KB2731771, KB2729094, KB2786081, KB2888049, KB2882822 to be able to install IE11 without any issues. Make sure you download the latest updates!
2. Reboot
3. Deploy IE11 itself. If you need the Google search provider, the only way is to repackage IE11 with IEAK.To customize Internet Explorer 11, first things first: download the Internet Explorer Administration Kit 11 here.
4. Force a reboot here
5. Make sure if you want to use IE11 Enterprise mode, you will need to deploy KB 2929437 after the installation of IE11.
6. Reboot
7. Deploy all security updates thru CM12/WSUS
8. Reboot
Luckily for us we have ConfigMgr 2012 and the fantastic Application model to handle that.
IE11 Enterprise Mode?
Enterprise Mode in IE11 is a compatibility mode that runs web apps in IE8 mode to make them work on IE11. Enterprise Mode is turned on by IT Pro using Group Policy settings for specific domains or pages. It’s much like the compatibility view settings, but provides Internet Explorer 8 compatibility. WebPages that work in Internet Explorer 8 work seamlessly in Enterprise Mode.
More on IE11 Enterprise Mode and Enterprise Mode Site List Manager.
Using the Internet Explorer Site Discovery Tool?
What do you say ??
Not so long ago Microsoft released a little tool that will inventory all the web sites a user visits to provide means to get a grip on web app compatibility. The inventory can be used for all or only some specific clients. The data is collected via WMI and inventoried with System Center Configuration Manager. There are pre-made reports included that can be imported and used in ConfigMgr.
You will find more information here on Enterprise Site Discovery Toolkit for Internet Explorer 11.
Collect data using Internet Explorer Site Discovery
Internet Explorer Site Discovery overview
You can use Internet Explorer to collect data on computers running Internet Explorer 11 on either Windows 8.1 or Windows 7. This inventory information helps you build a list of websites used by your company so you can make more informed decisions about your Internet Explorer deployments, including figuring out which sites might be at risk or require overhauls during future upgrades.
By default, Internet Explorer doesn’t collect data; you have to turn this feature on if you want to use it. You must make sure that using this feature complies with all applicable local laws and regulatory requirements.
What data is collected?
Data is collected on the configuration characteristics of Internet Explorer and the sites it browses, as shown here.
|
Data point
|
Description
|
|
URL
|
URL of the browsed site, including any parameters included in the URL.
|
|
Domain
|
Top-level domain of the browsed site.
|
|
ActiveX GUID
|
The GUID of the ActiveX controls loaded by the site.
|
|
Document mode
|
Document mode used by Internet Explorer for a site, based on page characteristics.
|
|
Document mode reason
|
The reason why a document mode was set by Internet Explorer.
|
|
Browser state reason
|
Additional information about why the browser is in its current state. Also called, browser mode.
|
|
Hang count
|
Number of visits to the URL when the browser hung.
|
|
Crash count
|
Number of visits to the URL when the browser crashed.
|
|
Most recent navigation failure (and count)
|
Description of the most recent navigation failure (like, a 404 bad request or 500 internal server error) and the number of times it happened.
|
|
Number of visits
|
The number of times a site has been visited.
|
|
Zone
|
Zone used by Internet Explorer to browse sites, based on browser settings.
|
Where is the data stored and how do I collect it?
The data is stored locally, in an industry-standard WMI class, Managed Object Format (.MOF) file. This file remains on the client computer until it’s collected. To collect the file from your client computers, we recommend using Microsoft System Center 2012 R2 Configuration Manager. However, if you don’t use System Center, you can collect the file using any agent that can read the contents of a WMI class on your computer.
Requirements
Before you start, you need to make sure you have the following:
Setup and configuration package, including:
- Configuration-related PowerShell scripts
- IETelemetry.mof file
- Sample System Center 2012 report templates
Both the PowerShell script and .mof file need to be copied to the same location on the client computer, before you run the scripts.
Setting up your client computers for data collection
On your test computer, run the provided PowerShell script (IETelemetrySetUp.ps1) to compile the .mof file, update security privileges for the new WMI classes, and to set the registry key.
To set up your computers:
- Create a Package/Program in Configmgr 2012 that runs the IETElemetrySetUp.ps1
- Restart your computer to start collecting your WMI data.
Using System Center 2012 R2 Configuration Manager to collect your data
After you’ve collected all of the data, you’ll need to get the local files off of your computers. To do this, use the hardware inventory process in System Center Configuration Manager, in one of the following ways.
Collect your hardware inventory using the MOF Editor while connecting to a computer
You can collect your hardware inventory using the MOF Editor, while you’re connected to your client computers.
To collect your inventory
1. From the System Center Configuration Manager, click Administration, click Client Settings, double-click Default Client Settings, click Hardware Inventory, and then click Set Classes.
![clip_image002]( "clip_image002")
2. Click Add, click Connect, and connect to a computer that has completed the setup process and has already existing classes.
3. Change the WMI Namespace to root\cimv2\IETelemetry, and click Connect
![clip_image004]( "clip_image004")
4. Select the check boxes next to the following classes, and then click OK:
· IESystemInfo
· IEURLInfo
· IECountInfo
5. Click OK to close the default windows.
Your environment is now ready to collect your hardware inventory and review the sample reports.
Collect your hardware inventory using the MOF Editor with a MOF import file
You can collect your hardware inventory using the MOF Editor and a MOF import file.
To collect your inventory:
1. From the System Center Configuration Manager, click Administration, click Client Settings, double-click Default Client Settings, click Hardware Inventory, and then click Set Classes.
2. Click Import, choose the MOF file from the downloaded package we provided, and click Open.
3. Pick the inventory items to install, and then click Import.
4. Click OK to close the default windows.
Your environment is now ready to collect your hardware inventory and review the sample reports.
Collect your hardware inventory using the SMS_DEF.MOF file
You can collect your hardware inventory using the using the Systems Management Server (SMS_DEF.MOF) file.
To collect your inventory:
1. Using a text editor like Notepad, open the SMS_DEF.MOF file, located in your <Config_Manager_install_location>\inboxes\clifiles.src\hinv directory.
2. Add this text to the end of the file:
[SMS_Report (TRUE),
SMS_Group_Name ("IESystemInfo"),
SMS_Class_ID ("MICROSOFT|IESystemInfo|1.0"),
Namespace ("root\\\\cimv2\\\\IETelemetry") ]
Class IESystemInfo: SMS_Class_Template
{
[SMS_Report (TRUE), Key ]
String SystemKey;
[SMS_Report (TRUE) ]
String IEVer;
};
[SMS_Report (TRUE),
SMS_Group_Name ("IEURLInfo"),
SMS_Class_ID ("MICROSOFT|IEURLInfo|1.0"),
Namespace ("root\\\\cimv2\\\\IETelemetry") ]
Class IEURLInfo: SMS_Class_Template
{
[SMS_Report (TRUE), Key ]
String URL;
[SMS_Report (TRUE) ]
String Domain;
[SMS_Report (TRUE) ]
UInt32 DocMode;
[SMS_Report (TRUE) ]
UInt32 DocModeReason;
[SMS_Report (TRUE) ]
UInt32 Zone;
[SMS_Report (TRUE) ]
UInt32 BrowserStateReason;
[SMS_Report (TRUE) ]
String ActiveXGUID[];
[SMS_Report (TRUE) ]
UInt32 CrashCount;
[SMS_Report (TRUE) ]
UInt32 HangCount;
[SMS_Report (TRUE) ]
UInt32 NavigationFailureCount;
[SMS_Report (TRUE) ]
UInt32 NumberOfVisits;
[SMS_Report (TRUE) ]
UInt32 MostRecentNavigationFailure;
};
[SMS_Report (TRUE),
SMS_Group_Name ("IECountInfo"),
SMS_Class_ID ("MICROSOFT|IECountInfo|1.0"),
Namespace ("root\\\\cimv2\\\\IETelemetry") ]
Class IECountInfo: SMS_Class_Template
{
[SMS_Report (TRUE), Key ]
String CountKey;
[SMS_Report (TRUE) ]
UInt32 CrashCount;
[SMS_Report (TRUE) ]
UInt32 HangCount;
[SMS_Report (TRUE) ]
UInt32 NavigationFailureCount;
};
3. Save the file and close it to the same location.
Your environment is now ready to collect your hardware inventory and review the sample reports.
Viewing the sample reports
The sample reports, SCCM Report Sample – ActiveX.rdll and SCCM Report Sample – Site Discovery.rdl, work with System Center 2012, so you can review your collected data.
SCCM Report Sample – ActiveX.rdl
Gives you a list of all of the ActiveX-related sites visited by the client computer.
![clip_image006]( "clip_image006")
SCCM Report Sample – Site Discovery.rdl
Gives you a list of all of the sites visited by the client computer.
![clip_image008]( "clip_image008")
Turning off data collection on your client computers
After you’ve collected all of your data, you’ll need to turn this functionality off.
To stop collecting data:
|
On your test computer, start PowerShell in elevated mode and run IETElemetrySetUp.ps1 using this command: powershell .\IETElemetrySetUp.ps1 -IEFeatureOff. ![clip_image009]( "clip_image009")
|
|
Turning off data collection only disables the Internet Explorer Site Discovery feature – all data already written to WMI stays on the client computer.
|
Deleting already stored data from client computers
You can completely remove the data stored on your client computers.
To delete existing data:
On the client computer, start PowerShell in elevated mode (using admin privileges) and run these commands:
Remove-WmiObject -Namespace root/cimv2/IETelemetry IEURLInfo Remove-WmiObject -Namespace root/cimv2/IETelemetry IESystemInfo Remove-WmiObject -Namespace root/cimv2/IETelemetry IECountInfo Remove-Item -Path 'HKCU:\Software\Microsoft\Internet Explorer\WMITelemetry'
Hope it Helps ,
Kenny Buntinx
MVP Enterprise Client Management
) image in Configmgr 2012 and use that image as a base to deploy it in your company. I will be outlining not necessarily pointing out every click. Hopefully others will find this helpful. This assumes an understanding of Configmgr 2012 and uses what is referred to as a “Hybrid Image Strategy”.
. Luckily we have an excellent PowerShell scripter in our team and all credits for creating this script goes to Bart Serneels. He has written a PowerShell script to do all the work . He was happy to share this with you guys.
