SharePoint 2010 can be easily deployed to a single box with local administrator accounts using the standalone, out-of-the-box install, but this forces you to use SQL Express 2008 (which comes with SharePoint).  What if you want to do a complete farm install on the box, but stick with local accounts?  Then this becomes a lot more tricky.

The complete install, using the configuration dialogs, will not let you enter local accounts, and will force you to use a domain account.  The best practice seems to be to promote the server to a domain controller, and use domain accounts, however this might not be possible or desired if you’re working in a DMZ, or on a development machine.  Also, you might want to do the complete install so that you can leverage the 10 GB data limit and remote BLOB storage in SQL 2008 Express R2, rather than being stuck to the earlier version of SQL Express which comes with SharePoint.   Luckily, there’s some ways to bypass the domain account requirement by using PowerShell scripting to set up the environment.  I found two helpful blog posts below which get you part of the way there, and I’ll help clarify some of the missing pieces.
Continue reading…