SharePoint Foundation 2013 customize Stand-alone server installation

SharePoint installs have two server type install options; either Complete, or Stand-alone.

The Complete option lets you specify SQL server, accounts, and a couple other options. The problem with this option is that it requires a domain.
The Stand-alone option doesn't let you specify anything and will install and configure the Service Apps using the built-in SQL Express 2008.

What if you want to setup a Single Server, specify a local SQL Server, say SQL 2012 Dev edition and manually configure the service apps?

1. Select Complete.
2. Wait for it to finish, but don't launch SharePoint Products Configuration Wizard 
3. Run the SharePoint 2013 Management Shell: C:\Windows\System32\WindowsPowerShell\v1.0\PowerShell.exe  -NoExit  " & ' C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\CONFIG\POWERSHELL\Registration\\sharepoint.ps1 ' "
4. Paste the following command using names appropriate for your environment: New-SPConfigurationDatabase -DatabaseName "SPF2013_Config" -DatabaseServer "SPF2013SQL" -AdministrationContentDatabaseName "Content_CA"
5. Run the SharePoint Products Configuration Wizard: "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\BIN\psconfigui.exe"
6. Let it complete.
7. Now the problem is you will not be able to add any Managed Accounts through the UI, to fix this you need to edit the following registry key: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\15.0\WSS]
8. Change "ServerRole"="APPLICATION" to "ServerRole"="SINGLESERVER". Making this change will also break anything that uses psconfig, unless you have setup the SQL server to have a SharePoint instance, eg: server\SharePoint, that's how the Stand-alone SQL instance is configured so the psconfig checks if that instance is running. You'll only need psconfig to repair SP or install new service packs, and it's easy to change ServerRole back.

This should also work with SPF 2010.

Top 20 Replies by Programmers when their programs don't work

20. That's weird... 
19. It's never done that before. 
18. It worked yesterday.
17. How is that possible? 
18. It must be a hardware problem. 
15. What did you type in wrong to get it to crash? 
14. There has to be something funky in your data. 
13. I haven't touched that module in weeks! 
12. You must have the wrong version. 
11. It's just some unlucky coincidence. 
10. I can't test everything! 
9. THIS can't be the source of THAT. 
8. It works, but it hasn't been tested. 
7. Somebody must have changed my code. 
6. Did you check for a virus on your system? 
5. Even though it doesn't work, how does it feel? 
4. You can’t use that version on your system. 
3. Why do you want to do it that way? 
2. Where were you when the program blew up? 
1. It works on my machine.