The specified user [USER NAME] is a local account. Local accounts should only be used in stand alone mode If we think about it, SharePoint is absolutely right, because advanced configuration allows the creation of a farm in which we can then connect other servers, such as for indexing, sending mail or other stuffs .. and of course, a local account on the machine where we are installing the product is not able to "switch" between a server and the other becouse is not a domani account. But if we are sure that our server is the only one of our SharePoint farm, we can still create the farm using Powershell. The command that we have to run is the "New-SPConfigurationDatabase" command. Using it we have to specify the database name, the database server and the user which access this database. The user's choice will be made through the login dialog windows. That Powershell command creates a new configuration database within SQL Server for SharePoint and it will be the basis of our new farm. In fact, starting again the utility "SharePoint Products Configuration Wizard", it will notice the presence of a SharePoint farm and so enable us to proceed with the installation. So, now we have a SharePoint 2010 advanced installation, in a standalone server.
This article is also available in the following languages:
Fernando Lugão Veltem edited Revision 2. Comment: remove en-us from title
Luigi Bruno edited Revision 1. Comment: Added the "How To" Wiki Message Template. Added the "Other Languages" section.
Craig Lussier edited Original. Comment: added en-US to tags and title
Oe, great article, will test it !
Thank you for posting this. I've gone through these steps once or twice to stand up standalone SP servers for testing on the road.
Great post...i had this issue and solved by following same steps.