I am doing a Farm installation of SP 2010 in a VirtualBox instance for the purpose of local development. I am using Server 2008 R2, SQL Server 2008 R2. Since the instance of SQL server is local and not remote, there is common workaround that involves creating the database using New-SPConfigurationDatabase.
However, this approach is failing, as you see in the screen shot below. What is odd is that I never get prompted for the database instance or database name. Once I het enter in the script, I get a credential prmpt into which I enter the SQL credentials for the user in this format:
u: SERVERNAME\username p: userspassword
I enter a new passphrase, which I understand is the farm Administrative passphase to be used later. I surmise that this is the case since it is the Configuration Wizard that we are stepping out of here.
The local user account that I am using when running the PowerShell script has access to the database server and has the following roles: public, db creator and securityadmin. AD is not installed on the server. I have fully tested my SQL Server installation and it is operating properly.