You are currently reviewing an older revision of this page.
Go to current version

Nel lavoro quotidiano con SharePoint, si può avere la necessità di installare SharePoint 2010 su una macchina che non appartiene ad un dominio e di gestire il database tramite un'installazione di SQL Server Standard o Enterprise. In questa situazione, un'installazione standalone non è la scelta migliore, poichè si basa sulla versione Express di SQL Server.
 So, if you try to install SharePoint 2010 in advanced mode and begin the configuration of a new farm, the utility "SharePoint Products Configuration Wizard" will stop you immediately saying that the users with whom we have decided to run all the SharePoint services and thath will access to various databases, is a local account and that you can not create a new farm using a non-domain account.
 The error message in detail is:

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.

Revert to this revision