mirror of
https://github.com/MicrosoftDocs/windows-itpro-docs.git
synced 2025-06-15 10:23:37 +00:00
fixed broken links
This commit is contained in:
Patti Short
@ -33,7 +33,7 @@ You can add individual sites to your compatibility list by using the Enterprise
|
||||
1. In the Enterprise Mode Site List Manager (schema v.1), click **Add**.
|
||||
|
||||
2. Type the URL for the website that’s experiencing compatibility problems, like *<domain>.com* or *<domain>.com*/*<path>* into the **URL** box.<p>
|
||||
Don't include the `http://` or `https://` designation. The tool automatically tries both versions during validation.
|
||||
Don't include the `https://` or `https://` designation. The tool automatically tries both versions during validation.
|
||||
|
||||
3. Type any comments about the website into the **Notes about URL** box.<p>
|
||||
Administrators can only see comments while they’re in this tool.
|
||||
|
||||
@ -33,7 +33,7 @@ You can add individual sites to your compatibility list by using the Enterprise
|
||||
1. In the Enterprise Mode Site List Manager (schema v.2), click **Add**.
|
||||
|
||||
2. Type the URL for the website that’s experiencing compatibility problems, like *<domain>.com* or *<domain>.com*/*<path>* into the **URL** box.<p>
|
||||
Don't include the `http://` or `https://` designation. The tool automatically tries both versions during validation.
|
||||
Don't include the `https://` or `https://` designation. The tool automatically tries both versions during validation.
|
||||
|
||||
3. Type any comments about the website into the **Notes about URL** box.<p>
|
||||
Administrators can only see comments while they’re in this tool.
|
||||
|
||||
@ -52,7 +52,7 @@ After adding the `FEATURE\AUTOCONFIG\BRANDING` registry key, you can change your
|
||||
|
||||
- **Automatic Configuration URL (.INS file) box:** Type the location of your automatic configuration script.
|
||||
|
||||
- **Automatic proxy URL (.JS, .JVS, or .PAC file) box:** Type the location of your automatic proxy script.<p> **Important**<br>Internet Explorer 11 no longer supports using file server locations with your proxy configuration (.pac) files. To keep using your .pac files, you have to keep them on a web server and reference them using a URL, like `http://share/test.ins`.
|
||||
- **Automatic proxy URL (.JS, .JVS, or .PAC file) box:** Type the location of your automatic proxy script.<p> **Important**<br>Internet Explorer 11 no longer supports using file server locations with your proxy configuration (.pac) files. To keep using your .pac files, you have to keep them on a web server and reference them using a URL, like `https://share/test.ins`.
|
||||
|
||||
If your branding changes aren't correctly deployed after running through this process, see [Auto configuration and auto proxy problems with Internet Explorer 11](auto-configuration-and-auto-proxy-problems-with-ie11.md).
|
||||
|
||||
|
||||
@ -40,7 +40,7 @@ To use automatic detection, you have to set up your DHCP and DNS servers.<p>**No
|
||||
|
||||
3. In your DNS database file, create a host record named, **WPAD**. This record has the IP address of the web server storing your automatic configuration (.js, .jvs, .pac, or .ins) file.<p>**-OR-**<p>Create a canonical name (CNAME) alias record named, **WPAD**. This record has the resolved name (not the IP address) of the server storing your automatic configuration (.pac) file.<p>**Note**<br>For more information about creating a **WPAD** entry, see [Creating a WPAD entry in DNS](https://go.microsoft.com/fwlink/p/?LinkId=294651).
|
||||
|
||||
4. After the database file propagates to the server, the DNS name, `wpad.<domain>.com` resolves to the server name that includes your automatic configuration file.<p>**Note**<br>Internet Explorer 11 creates a default URL template based on the host name, **wpad**. For example, `http://wpad.<domain>.com/wpad.dat`. Because of this, you need to set up a file or redirection point in your web server **WPAD** record, named **wpad.dat**. The **wpad.dat** record delivers the contents of your automatic configuration file.
|
||||
4. After the database file propagates to the server, the DNS name, `wpad.<domain>.com` resolves to the server name that includes your automatic configuration file.<p>**Note**<br>Internet Explorer 11 creates a default URL template based on the host name, **wpad**. For example, `https://wpad.<domain>.com/wpad.dat`. Because of this, you need to set up a file or redirection point in your web server **WPAD** record, named **wpad.dat**. The **wpad.dat** record delivers the contents of your automatic configuration file.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -30,7 +30,7 @@ You can use your Internet settings (.ins) files to set up your standard proxy se
|
||||
|
||||
- **Automatic Configuration URL (.INS file) box:** Type the location of the .ins file you want to use for automatic configuration. For more information about setting up **Automatic Configuration**, see [Auto configuration settings for Internet Explorer 11](auto-configuration-settings-for-ie11.md).
|
||||
|
||||
- **Automatic proxy URL (.JS, .JVS, or .PAC file) box:** Type the location of your automatic proxy script. This script runs whenever IE11 makes a network request and can include multiple proxy servers for each protocol type.<p>**Important**<br>IE11 no longer supports using file server locations with your proxy configuration (.pac) files. To keep using your .pac files, you have to keep them on a web server and reference them using a URL, like `http://share/test.ins`.
|
||||
- **Automatic proxy URL (.JS, .JVS, or .PAC file) box:** Type the location of your automatic proxy script. This script runs whenever IE11 makes a network request and can include multiple proxy servers for each protocol type.<p>**Important**<br>IE11 no longer supports using file server locations with your proxy configuration (.pac) files. To keep using your .pac files, you have to keep them on a web server and reference them using a URL, like `https://share/test.ins`.
|
||||
|
||||
## Locking your auto-proxy settings
|
||||
You have two options to restrict your users' ability to override the automatic configuration settings, based on your environment.
|
||||
|
||||
@ -50,7 +50,7 @@ Employees assigned to the Requester role can create a change request. A change r
|
||||
|
||||
- **Business impact (optional).** An optional area where you can provide info about the business impact of this app and the change.
|
||||
|
||||
- **App location (URL).** The full URL location to the app, starting with http:// or https://.
|
||||
- **App location (URL).** The full URL location to the app, starting with https:// or https://.
|
||||
|
||||
- **App best viewed in.** Select the best browser experience for the app. This can be Internet Explorer 5 through Internet Explorer 11 or one of the IE7Enterprise or IE8Enterprise modes.
|
||||
|
||||
|
||||
@ -41,7 +41,7 @@ Deploying pinned websites in MDT 2013 is a 4-step process:
|
||||
Pinned websites are immediately available to every user who logs on to the computer although the user must click each icon to populate its Jump List.
|
||||
|
||||
**Important**<br>
|
||||
To follow the examples in this topic, you’ll need to pin the Bing (http://www.bing.com/) and MSN (http://www.msn.com/) websites to the taskbar.
|
||||
To follow the examples in this topic, you’ll need to pin the Bing (https://www.bing.com/) and MSN (https://www.msn.com/) websites to the taskbar.
|
||||
|
||||
### Step 1: Creating .website files
|
||||
The first step is to create a .website file for each website that you want to pin to the Windows 8.1 taskbar during deployment. A .website file is like a shortcut, except it’s a plain text file that describes not only the website’s URL but also how the icon looks.
|
||||
|
||||
@ -28,7 +28,7 @@ If you don't want to use the Enterprise Mode Site List Manager, you also have th
|
||||
The following is an example of the Enterprise Mode schema v.1. This schema can run on devices running Windows 7 and Windows 8.1.
|
||||
|
||||
**Important**<br>
|
||||
Make sure that you don't specify a protocol when adding your URLs. Using a URL like `<domain>contoso.com</domain>` automatically applies to both http://contoso.com and https://contoso.com.
|
||||
Make sure that you don't specify a protocol when adding your URLs. Using a URL like `<domain>contoso.com</domain>` automatically applies to both https://contoso.com and https://contoso.com.
|
||||
|
||||
``` xml
|
||||
<rules version="1">
|
||||
@ -135,7 +135,7 @@ This table includes the elements used by the Enterprise Mode schema.
|
||||
<path exclude="true">/products</path>
|
||||
</domain>
|
||||
</emie></pre><p>
|
||||
Where http://fabrikam.com doesn't use IE8 Enterprise Mode, but http://fabrikam.com/products does.</td>
|
||||
Where https://fabrikam.com doesn't use IE8 Enterprise Mode, but https://fabrikam.com/products does.</td>
|
||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
||||
</tr>
|
||||
</table>
|
||||
@ -167,7 +167,7 @@ This table includes the attributes used by the Enterprise Mode schema.
|
||||
<path exclude="true">/products</path>
|
||||
</domain>
|
||||
</emie></pre><p>
|
||||
Where http://fabrikam.com uses IE8 Enterprise Mode, but http://fabrikam.com/products does not.</td>
|
||||
Where https://fabrikam.com uses IE8 Enterprise Mode, but https://fabrikam.com/products does not.</td>
|
||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -203,7 +203,7 @@ For example, say you want all of the sites in the contoso.com domain to open usi
|
||||
|
||||
### What not to include in your schema
|
||||
We recommend that you not add any of the following items to your schema because they can make your compatibility list behave in unexpected ways:
|
||||
- Don’t use protocols. For example, `http://`, `https://`, or custom protocols. They break parsing.
|
||||
- Don’t use protocols. For example, `https://`, `https://`, or custom protocols. They break parsing.
|
||||
- Don’t use wildcards.
|
||||
- Don’t use query strings, ampersands break parsing.
|
||||
|
||||
|
||||
@ -38,7 +38,7 @@ You can continue to use the v.1 version of the schema on Windows 10, but you wo
|
||||
The following is an example of the v.2 version of the Enterprise Mode schema.
|
||||
|
||||
**Important**<br>
|
||||
Make sure that you don't specify a protocol when adding your URLs. Using a URL like `<url="contoso.com">`, automatically applies to both http://contoso.com and https://contoso.com.
|
||||
Make sure that you don't specify a protocol when adding your URLs. Using a URL like `<url="contoso.com">`, automatically applies to both https://contoso.com and https://contoso.com.
|
||||
|
||||
``` xml
|
||||
<site-list version="205">
|
||||
@ -198,7 +198,7 @@ The <url> attribute, as part of the <site> element in the v.2 versio
|
||||
<site url="contoso.com/travel">
|
||||
<open-in allow-redirect="true">IE11</open-in>
|
||||
</site></pre>
|
||||
In this example, if http://contoso.com/travel is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer.</td>
|
||||
In this example, if https://contoso.com/travel is encountered in a redirect chain in Microsoft Edge, it will be opened in Internet Explorer.</td>
|
||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
||||
</tr>
|
||||
<tr>
|
||||
@ -210,14 +210,14 @@ In this example, if http://contoso.com/travel is encountered in a redirect chain
|
||||
<td>url</td>
|
||||
<td>Specifies the URL (and port number using standard port conventions) to which the child elements apply. The URL can be a domain, sub-domain, or any path URL.
|
||||
<br><b>Note</b><br>
|
||||
Make sure that you don't specify a protocol. Using <site url="contoso.com"> applies to both http://contoso.com and https://contoso.com.
|
||||
Make sure that you don't specify a protocol. Using <site url="contoso.com"> applies to both https://contoso.com and https://contoso.com.
|
||||
<p><b>Example</b>
|
||||
<pre class="syntax">
|
||||
<site url="contoso.com:8080">
|
||||
<compat-mode>IE8Enterprise</compat-mode>
|
||||
<open-in>IE11</open-in>
|
||||
</site></pre>
|
||||
In this example, going to http://contoso.com:8080 using Microsoft Edge, causes the site to open in IE11 and load in IE8 Enterprise Mode.</td>
|
||||
In this example, going to https://contoso.com:8080 using Microsoft Edge, causes the site to open in IE11 and load in IE8 Enterprise Mode.</td>
|
||||
<td>Internet Explorer 11 and Microsoft Edge</td>
|
||||
</tr>
|
||||
</table>
|
||||
@ -286,7 +286,7 @@ Saving your v.1 version of the file using the new Enterprise Mode Site List Mana
|
||||
### What not to include in your schema
|
||||
We recommend that you not add any of the following items to your schema because they can make your compatibility list behave in unexpected ways:
|
||||
|
||||
- Don’t use protocols. For example, http://, https://, or custom protocols. They break parsing.
|
||||
- Don’t use protocols. For example, https://, https://, or custom protocols. They break parsing.
|
||||
- Don’t use wildcards.
|
||||
- Don’t use query strings, ampersands break parsing.
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@ Windows Server Update Services (WSUS) lets you download a single copy of the Mic
|
||||
|
||||
**To import from Windows Update to WSUS**
|
||||
|
||||
1. Open your WSUS admin site. For example, `http://<wsus_server-name>/WSUSAdmin/`.<P>
|
||||
1. Open your WSUS admin site. For example, `https://<wsus_server-name>/WSUSAdmin/`.<P>
|
||||
Where `<wsus_server_name>` is the name of your WSUS server.
|
||||
|
||||
2. Choose the top server node or the **Updates** node, and then click **Import Updates**.
|
||||
|
||||
@ -21,7 +21,7 @@ IE11 works differently with search, based on whether your organization is domain
|
||||
|
||||
- **Non-domain-joined computers.** A single word entry is treated as an intranet site. However, if the term doesn't resolve to a site, IE11 then treats the entry as a search term and opens your default search provider.
|
||||
|
||||
To explicitly go to an intranet site, regardless of the environment, users can type either a trailing slash like ` contoso/` or the `http://` prefix. Either of these will cause IE11 to treat the entry as an intranet search. You can also change the default behavior so that IE11 treats your single word entry in the address bar as an intranet site, regardless of your environment.
|
||||
To explicitly go to an intranet site, regardless of the environment, users can type either a trailing slash like ` contoso/` or the `https://` prefix. Either of these will cause IE11 to treat the entry as an intranet search. You can also change the default behavior so that IE11 treats your single word entry in the address bar as an intranet site, regardless of your environment.
|
||||
|
||||
**To enable single-word intranet search**
|
||||
|
||||
@ -29,7 +29,7 @@ To explicitly go to an intranet site, regardless of the environment, users can t
|
||||
|
||||
2. Click **Advanced**, check the **Go to an intranet site for a single word entry in the Address bar** box, and then click **OK**.
|
||||
|
||||
If you'd like your entire organization to have single word entries default to an intranet site, you can turn on the **Go to an intranet site for a single word entry in the Address bar** Group Policy. With this policy turned on, a search for `contoso` automatically resolves to `http://contoso`.
|
||||
If you'd like your entire organization to have single word entries default to an intranet site, you can turn on the **Go to an intranet site for a single word entry in the Address bar** Group Policy. With this policy turned on, a search for `contoso` automatically resolves to `https://contoso`.
|
||||
|
||||
|
||||
|
||||
|
||||
@ -115,7 +115,7 @@ Out-of-date ActiveX control blocking is turned off in the Local Intranet Zone an
|
||||
|--------|--------------|-------------|----------|
|
||||
|Turn on ActiveX control logging in IE |`Administrative Templates\Windows Components\Internet Explorer\Security Features\Add-on Management` |Internet Explorer 8 through IE11 |This setting determines whether IE saves log information for ActiveX controls.<p>If you enable this setting, IE logs ActiveX control information (including the source URI that loaded the control and whether it was blocked) to a local file.<p>If you disable or don't configure this setting, IE won't log ActiveX control information.<p>Note that you can turn this setting on or off regardless of the **Turn off blocking of outdated ActiveX controls for IE** or **Turn off blocking of outdated ActiveX controls for IE on specific domains** settings. |
|
||||
|Remove the **Run this time** button for outdated ActiveX controls in IE |`Administrative Templates\Windows Components\Internet Explorer\Security Features\Add-on Management`|Internet Explorer 8 through IE11 |This setting allows you stop users from seeing the **Run this time** button and from running specific outdated ActiveX controls in IE.<p>If you enable this setting, users won't see the **Run this time** button on the warning message that appears when IE blocks an outdated ActiveX control.<p>If you disable or don't configure this setting, users will see the **Run this time** button on the warning message that appears when IE blocks an outdated ActiveX control. Clicking this button lets the user run the outdated ActiveX control once. |
|
||||
|Turn off blocking of outdated ActiveX controls for IE on specific domains |`Administrative Templates\Windows Components\Internet Explorer\Security Features\Add-on Management` |Internet Explorer 8 through IE11 |This setting allows you to manage a list of domains on which IE will stop blocking outdated ActiveX controls. Outdated ActiveX controls are never blocked in the Intranet Zone.<p>If you enable this setting, you can enter a custom list of domains for which outdated ActiveX controls won't be blocked in IE. Each domain entry must be formatted like one of the following:<ul><li>**"domainname.TLD".** For example, if you want to include `*.contoso.com/*`, use "contoso.com".</li><li>**"hostname".** For example, if you want to include `http://example`, use "example".</li><li>**"file:///path/filename.htm"**. For example, use `file:///C:/Users/contoso/Desktop/index.htm`.</li></ul><p>If you disable or don't configure this setting, the list is deleted and IE continues to block specific outdated ActiveX controls on all domains in the Internet Zone. |
|
||||
|Turn off blocking of outdated ActiveX controls for IE on specific domains |`Administrative Templates\Windows Components\Internet Explorer\Security Features\Add-on Management` |Internet Explorer 8 through IE11 |This setting allows you to manage a list of domains on which IE will stop blocking outdated ActiveX controls. Outdated ActiveX controls are never blocked in the Intranet Zone.<p>If you enable this setting, you can enter a custom list of domains for which outdated ActiveX controls won't be blocked in IE. Each domain entry must be formatted like one of the following:<ul><li>**"domainname.TLD".** For example, if you want to include `*.contoso.com/*`, use "contoso.com".</li><li>**"hostname".** For example, if you want to include `https://example`, use "example".</li><li>**"file:///path/filename.htm"**. For example, use `file:///C:/Users/contoso/Desktop/index.htm`.</li></ul><p>If you disable or don't configure this setting, the list is deleted and IE continues to block specific outdated ActiveX controls on all domains in the Internet Zone. |
|
||||
|Turn off blocking of outdated ActiveX controls for IE |`Administrative Templates\Windows Components\Internet Explorer\Security Features\Add-on Management` |Internet Explorer 8 through IE11 |This setting determines whether IE blocks specific outdated ActiveX controls. Outdated ActiveX controls are never blocked in the Intranet Zone.<p>If you enable this setting, IE stops blocking outdated ActiveX controls.<p>If you disable or don't configure this setting, IE continues to block specific outdated ActiveX controls. |
|
||||
|Remove the **Update** button in the out-of-date ActiveX control blocking notification for IE |This functionality is only available through the registry |Internet Explorer 8 through IE11 |This setting determines whether the out-of-date ActiveX control blocking notification shows the **Update** button. This button points users to update specific out-of-date ActiveX controls in IE. |
|
||||
|
||||
@ -145,8 +145,8 @@ Here’s a detailed example and description of what’s included in the VersionA
|
||||
|
||||
|Source URI |File path |Product version |File version |Allowed/Blocked |Reason |EPM-compatible |
|
||||
|-----------|----------|----------------|-------------|----------------|-------|---------------|
|
||||
|`http://contoso.com/test1.html` |C:\Windows\System32\Macromed\Flash\Flash.ocx |14.0.0.125 |14.0.0.125 |Allowed |Not in blocklist |EPM-compatible |
|
||||
|`http://contoso.com/test2.html` |C:\Program Files\Java\jre6\bin\jp2iexp.dll |6.0.410.2 |6.0.410.2 |Blocked |Out of date |Not EPM-compatible |
|
||||
|`https://contoso.com/test1.html` |C:\Windows\System32\Macromed\Flash\Flash.ocx |14.0.0.125 |14.0.0.125 |Allowed |Not in blocklist |EPM-compatible |
|
||||
|`https://contoso.com/test2.html` |C:\Program Files\Java\jre6\bin\jp2iexp.dll |6.0.410.2 |6.0.410.2 |Blocked |Out of date |Not EPM-compatible |
|
||||
|
||||
**Where:**
|
||||
- **Source URI.** The URL of the page that loaded the ActiveX control.
|
||||
|
||||
@ -111,7 +111,7 @@ The required packages are automatically downloaded and included in the solution.
|
||||
|
||||
1. 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:
|
||||
|
||||
``` "Enable"="http://<deploy_URL>/api/records/"
|
||||
``` "Enable"="https://<deploy_URL>/api/records/"
|
||||
```
|
||||
Where `<deploy_URL>` points to your deployment URL.
|
||||
|
||||
@ -125,7 +125,7 @@ The required packages are automatically downloaded and included in the solution.
|
||||
|
||||
**To view the report results**
|
||||
|
||||
- Go to `http://<deploy_URL>/List` to see the report results.<p>
|
||||
- Go to `https://<deploy_URL>/List` to see the report results.<p>
|
||||
If you’re already on the webpage, you’ll need to refresh the page to see the results.
|
||||
|
||||
|
||||
|
||||
@ -176,7 +176,7 @@ Using the IIS Manager, you must restart both your Application Pool and your webs
|
||||
After you've created your database and website, you'll need to register yourself (or another employee) as an administrator for the Enterprise Mode Site List Portal.
|
||||
|
||||
**To register as an administrator**
|
||||
1. Open Microsoft Edge and type your website URL into the Address bar. For example, http://emieportal:8085.
|
||||
1. Open Microsoft Edge and type your website URL into the Address bar. For example, https://emieportal:8085.
|
||||
|
||||
2. Click **Register now**.
|
||||
|
||||
@ -184,7 +184,7 @@ After you've created your database and website, you'll need to register yourself
|
||||
|
||||
4. Click **Administrator** from the **Role** box, and then click **Save**.
|
||||
|
||||
5. Append your website URL with `/#/EMIEAdminConsole` in the Address bar to go to your administrator console. For example, http://emieportal:8085/#/EMIEAdminConsole.
|
||||
5. Append your website URL with `/#/EMIEAdminConsole` in the Address bar to go to your administrator console. For example, https://emieportal:8085/#/EMIEAdminConsole.
|
||||
|
||||
A dialog box appears, prompting you for the system user name and password. The default user name is EMIEAdmin and the default password is Admin123. We strongly recommend that you change the password by using the **Change password** link as soon as you're done with your first visit.
|
||||
|
||||
|
||||
@ -46,9 +46,9 @@ Besides turning on this feature, you also have the option to provide a URL for E
|
||||
|
||||
Your **Value data** location can be any of the following types:
|
||||
|
||||
- **URL location (like, http://www.emieposturl.com/api/records or http://localhost:13000)**. IE sends a POST message to the URL every time a change is made to Enterprise Mode from the **Tools** menu.<p>**Important**<br>
|
||||
The `http://www.emieposturl.com/api/records` example will only work if you’ve downloaded the sample discussed in the [Set up Enterprise Mode logging and data collection](set-up-enterprise-mode-logging-and-data-collection.md) topic. If you don’t have the sample, you won’t have the web API.
|
||||
- **Local network location (like, http://*emieposturl*/)**. IE sends a POST message to your specified local network location every time a change is made to Enterprise Mode from the **Tools** menu.
|
||||
- **URL location (like, https://www.emieposturl.com/api/records or https://localhost:13000)**. IE sends a POST message to the URL every time a change is made to Enterprise Mode from the **Tools** menu.<p>**Important**<br>
|
||||
The `https://www.emieposturl.com/api/records` example will only work if you’ve downloaded the sample discussed in the [Set up Enterprise Mode logging and data collection](set-up-enterprise-mode-logging-and-data-collection.md) topic. If you don’t have the sample, you won’t have the web API.
|
||||
- **Local network location (like, https://*emieposturl*/)**. IE sends a POST message to your specified local network location every time a change is made to Enterprise Mode from the **Tools** menu.
|
||||
- **Empty string**. If you leave the **Value data** box blank; your employees will be able to turn Enterprise Mode on and off from the **Tools** menu, but you won’t collect any logging data.
|
||||
|
||||
For information about how to collect the data provided when your employees turn Enterprise Mode on or off from the **Tools** menu, see [Set up Enterprise Mode logging and data collection](set-up-enterprise-mode-logging-and-data-collection.md).
|
||||
|
||||
Reference in New Issue
Block a user