The page URL of a pinned site is http://www.contoso.com/page1, and the Pinned Site notifications are generated from http://machine1.contoso.com/page2. The FQDN that is associated with the URL is www.contoso.com, and the FQDN that is associated with the notification page is machine1.contoso.com. In this scenario, because the FQDNs do not match, the SiteMode APIs on the page2 site are not permitted to send notifications to the taskbar.
You have a server farm, and the entry point into the site is http://www.contoso.com/. The entry point URL is a redirection page to a server farm from http://machine1.contoso.com/ to http://machineN.contoso.com. The StartURL for the pinned site is http://www.contoso.com, but the tasks are generated from http://machineN.contoso.com. In this scenario, because the pinned URL does not contain the meta-tag definitions for the SiteMode tasks, no tasks are displayed.
Using the example that was mentioned in Scenario 1, the top-level domain for http://www.contoso.com/page1 and for http://machine1.contoso.com/page2 is contoso.com. The name of the meta-tag is "msapplication-allowDomainApiCalls." This is the syntax:
To avoid the Pinned Site URL task problem, we introduced a new meta-tag that allows for Tasks that are defined in other pages on the same top-level domain to be read and applied to the Taskbar Tasks. Using the example in Scenario 2, the top-level domain for http://www.contoso.com and for http://machine1.contoso.com is contoso.com. The name of the meta-tag is “msapplication-allowDomainMetaTag.” This is the syntax:
Security update informationTo resolve this problem, install the most recent cumulative security update for Windows Internet Explorer. To do this, visit the following Microsoft website:
Note This update was first included in security update 2530548 (MS11-050). For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Artikelnummer: 2555542 – Letzte Überarbeitung: 20.06.2011 – Revision: 1