SharePoint Foundation and Search Server 2010: installation order

Sometimes we wonder in what order to install SharePoint Server and all its components. Here's an order I tested and works.

1. Deactivate Windows UAC
2. Install Search Server Express 2010 (it automatically installs Foundation and SQL 2008 Express)
3. Run SharePoint 2010 Products Configuration Wizard
4. If needed, install Sharepoint Language Pack
5. Install the SP1 of SharePoint Foundation
6. Install the SP1 of Search Server Express
7. If Sharepoint Language Pack were installed in point 3, install Sharepoint Language Pack SP1
8. Run SharePoint 2010 Products Configuration Wizard
9. Upgrade SQL instance from MSSQL 2008 Express to MSSQL 2008 R2 SP1 Express, so you will be able to store 10 GB per database instead of  4 GB
10. Up to now, if we go to Central Admin in "Manage web applications", we already see a web application using the port 80. This is the Search Server Express web application. If you want to reserve the port 80 to the future SharePoint site, you must change the Search Server Express port:
    
    Pay attention, the procedure in the table bellow is not ok. work-around is to delete the Search Server web application and then create a new web application with the port 80.
    

    - open IIS7, right click on the "SharePoint 80" site and edit binding - change 80 by 12345 (for instance) - open SharePoint 2010 Management Shell, copy paste the following code to rename the Search Server Express web application: $a=Get-SPWebApplication | where {$_.Name -match "SharePoint - 80"} $a.Name $a.Name="Search Server Express - 12345" $a.Update() Get-SPWebApplication | where {$_.Name -match "Search Server Express - 12345"} - back to IIS7: rename the site called "SharePoint - 80" by "Search Server Express - 12345" - restart the server

11. In Central Admin, Create a new site collection (your SharePoint Foundation site).  If access also needed for non AD users, do not forget to select "Claims Based Authentication" (FBA)
12. If "Claims Based Authentication" has been choosen: modify web.config files of web application and security token, create the aspnet tables
13. Create a user called "MegaFarmAccount" and add this user in "Managed Account" in Central Admin, change the Farm Service Account to this user (see my post "Search Service Application: Access Denied ")
14. If "Claims Based Authentication" has been choosen: create in IIS a new website dedicated to the FBA user management, copy-paste it the web page allowing the users FBA management (these pages are not included in SharePoint), DB connexion in this web.config
15. Install Ifilter to allow searches in pdf files
16. Configure outgoing emails in Central Admin
17. Configure incoming emails:
1. Configure in Central Admin
2. Install SMTP server in IIS6
3. Create a "Send Connector" in your exchange server
4. If users send email from outside the LAN: add the SharePoint sub domain in the "Accepted Domains" (External Relay) in your exchange server and create the SharePoint sub domain in the public DNS
18. Fine tuning:
1. Browser File Handling
2. Custom FBA login page
3. ReIndexing Database Tables
4. Web Applications and Sites Regional settings
5. Portal SuperUser & SuperReader Accounts for cache optimization
6. Set a warm up tool
19. Configure alternate access mappings in Central Admin
20. Configure Backup
21. If needed, install appropriate updates, for instance kb2553117 related to lists grouping issues when using languages packages