Commented Unassigned: New Install fails to install key webparts [21424]

I completed the installation and have separated the Application from the Front End servers and the default installation reveals a Missing server side dependencies.
* Microsoft.SharePoint.Portal.WebControls.MicroFeedWebPart
* Microsoft.SharePoint.Portal.WebControls.SiteDocuments
* Microsoft.SharePoint.Portal.WebControls.TaggedPeopleListWebPart
* Microsoft.SharePoint.Portal.WebControls.MySiteFirstRunExperienceWebPart
* Microsoft.SharePoint.Portal.WebControls.MySitePersonalSiteUpgradeOnNavigationWebPart
* Microsoft.SharePoint.Portal.WebControls.TaggedUrlListWebPart
* Microsoft.SharePoint.Portal.WebControls.SocialCommentWebPart
* Microsoft.Office.Server.Search.WebControls.AnalyticsHashTagWebPart
* Microsoft.SharePoint.Portal.WebControls.PublishedFeedWebPart
* Microsoft.SharePoint.Portal.WebControls.FollowedCountsWebPart
* Microsoft.SharePoint.Portal.WebControls.ProfileInfoWebPart
* Microsoft.SharePoint.Portal.WebControls.BlogView
* Microsoft.SharePoint.Portal.WebControls.ProfileManages
* Microsoft.SharePoint.Portal.WebControls.MySharedContext
* Microsoft.SharePoint.Portal.WebControls.TagInformationWebPart
* Microsoft.SharePoint.Portal.WebControls.PeopleWebPart
* Microsoft.SharePoint.Portal.WebControls.AskMeAboutWebPart

All of these are from the Content_Mysites_SC database.

These are so obscure there isn't even a reference to the installables. There seems to be some disconnect during the installation process.
I install the App Server, Query/Index/DistCache Server and then the Web Front End servers.

I think there is an issue when portal/mysites are created before there are web front ends to host them.

I also get a dumb message about the "Application pools recycle when memory limits are exceeded" that I cannot solve because of this. Or at least I think it stems from a similar cause.

Installing using the script about dozen times, these two messages come up every time.

Daren
Comments: ** Comment from web user: brianlala **

You may be on to something with "I think there is an issue when portal/mysites are created before there are web front ends to host them" - try changing the installation order perhaps, or maybe tweak the farm/service topology a bit.

The message "Application pools recycle when memory limits are exceeded" happens when you have a dedicated App server that isn't running the Foundation Web Application service (which is indeed the correct config for a true App server). I believe I've fixed this in the past simply by dumb-copying the \inetpub\wwwroot\wss\VirtualDirectories\<content web app> folder(s) to the same path on the app server. Or, simply delete the HA rule instance and disable the rule, if you're feeling bold.

Brian