Set up Enterprise Mode logging and data collection
Using Group Policy, you can turn on Enterprise Mode for Internet Explorer and then you can turn on local user control using the Let users turn on and use Enterprise Mode from the Tools menu setting, located in the Administrative Templates\Windows Components\Internet Explorer category path. After you turn this setting on, your users can turn on Enterprise Mode locally, from the Internet Explorer Tools menu.
The Let users turn on and use Enterprise Mode from the Tools menu setting also lets you decide where to send the user reports (as a URL).
|We recommend creating a custom HTTP port 81 to let your incoming user information go to a dedicated site. A dedicated site is important so you can quickly pick out the Enterprise Mode traffic from your other website traffic.|
Getting these reports lets you find out about sites that aren’t working right, so you can add them to your Enterprise Mode site list, without having to locate them all yourself. For more information about creating and using a site list, see Add multiple sites to the Enterprise Mode site list using a file and Enterprise Mode Site List Manager.
Using ASP to collect your data
When you turn logging on, you need a valid URL that points to a server that can be listened to for updates to a user’s registry key. This means you need to set up an endpoint server for the incoming POST messages, which are sent every time the user turns Enterprise Mode on or off from the Tools menu.
To set up an endpoint server
Configure an IIS server to work with your Enterprise Mode data collection process. If you’re unsure how to set up IIS, see the IIS installation webpage.
Open Internet Information Services (IIS) and turn on the ASP components from the Add Roles and Features Wizard, Server Roles page.
This lets you create an ASP form that accepts the incoming POST messages.
Open the Internet Information Services (IIS) Manager, click Bindings, highlight Port 81, click Edit, and then change the website information to point to Port 81 so it matches your custom-created port.
Open the Logging feature, pick W3C for the format, and click Select Fields to open the W3C Logging Fields box.
Change the WC3 logging fields to include only the Date, Client IP, User Name, and URI Query standard fields, and then click OK.
Using only these fields keeps the log file simple, giving you the date, client IP address, and the website URI information for any site changed by your users.
Apply these changes to your default website and close the IIS Manager.
Put your EmIE.asp file into the root of the web server, using this command:
This code logs your POST fields to your IIS log file, where you can review all of the collected data.
IIS log file information
This is what your log files will look like after you set everything up and at least one of your users has turned on Enterprise Mode locally from the Tools menu. You can see the URL of the problematic website and client IP address of the user that turned on Enterprise Mode.
Using the GitHub sample to collect your data
Microsoft has created the EMIE-Data_Collection_Sample that shows how to collect your Enterprise Mode reports. This sample only shows how to collect data, it doesn’t show how to aggregate the data into your Enterprise Mode site list.
This sample starts with you turning on Enterprise Mode and logging (either through Group Policy, or by manually setting the EnterpriseMode registry key) so that your users can use Enterprise Mode locally. For the steps to do this, go to the Turn on local control and logging for Enterprise Mode topic.
If you decide to manually change the registry key, you can change the Enable setting to
Setting up, collecting, and viewing reports
For logging, you’re going to need a valid URL that points to a server that can be listened to for updates to a user’s registry key. This means you need to set up an endpoint server for the incoming POST messages, which are sent every time the user turns Enterprise Mode on or off from the Tools menu. These POST messages go into your database, aggregating the report data by URL, giving you the total number of reports where users turned on Enterprise Mode, the total number of reports where users turned off Enterprise Mode, and the date of the last report.
To set up the sample
Set up a server to collect your Enterprise Mode information from your users.
Go to the Internet Explorer/EMIE-Data_Collection_Sample page on GitHub and tap or click the Download ZIP button to download the complete project.
Open Visual Studio 2013 with Update 2, and then open the PhoneHomeSample.sln file.
On the Build menu, tap or click Build Solution.
The required packages are automatically downloaded and included in the solution.
To set up your endpoint server
Right-click on the name, PhoneHomeSample, and click Publish.
In the Publish Web wizard, pick the publishing target and options that work for your organization.
Important Make sure you have a database associated with your publishing target. Otherwise, your reports won’t be collected and you’ll have problems deploying the website.
After you finish the publishing process, you need to test to make sure the app deployed successfully.
To test, deploy, and use the app
Open a registry editor on the computer where you deployed the app, go to the HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Internet Explorer\Main\EnterpriseMode key, and change the Enable string to:
Where <deploy_URL> points to your deployment URL
After you’re sure your deployment works, you can deploy it to your users using one of the following:
Turn on the Let users turn on and use Enterprise Mode from the Tools menu Group Policy setting, putting your <deploy_URL> information into the Options box.
Deploy the registry key in Step 3 using System Center or other management software.
- Turn on the Let users turn on and use Enterprise Mode from the Tools menu Group Policy setting, putting your <deploy_URL> information into the Options box.
Get your users to visit websites, turning Enterprise Mode on or off locally, as necessary.
To view the report results
Go to http://<deploy_URL>/List to see the report results.
If you’re already on the webpage, you’ll need to refresh the page to see the results.
Troubleshooting publishing errors
If you have errors while you’re publishing your project, you should try to update your packages.
To update your packages
From the Tools menu of Visual Studio, click NuGet Package Manager, and click Manage NuGet Packages for Solution.
Click Updates on the left side of the tool, and click the Update All button.
You may need to do some additional package cleanup to remove older package versions.