View Complete Post
Question: What is the best practice configuration for StandAlone install? Here is my scenario: client does not own SQL Server therefore they want to use the OOB version in StandAlone mode. Most likely this will be fine for their goals for a couple years.
Anyhow, so I install in as Server Farm - first option, then StandAlone - second option, and select the location to store the data files. It installs great. Now reading the best practices for a typical farm (non-standalone) install, a domain account should
be used for the services. During the install of standalone it assignes the NETWORK SERVICE account to all of the services.
Can I create the SP_Farm account - per best practices - and get this account to work for the Farm service in standalone setup? Do I have to add this account to SQL Server Express first, add it as a managed account in SharePoint, then assign it to the Farm
Curious if anyone has done this. Or is the best practice when using SharePoint Foundation 2010 standalone configuration, to use the default accounts and settings as it was setup?
Thank you any responses.
I've made a few Sharepoint installations and solutions in my time and have been toying with the new 2010 iteration in my spare time on my super powerful quad-core laptop in a couple virtual spaces. I recently come across a request from a colleague
who asked me a question on which is the most recommended MOSS - SP2010 configuration - single server or separate SQL box and SP Box. I replied with the non-committal "It depends on what you want to do" generality. But, it got me thinking...
I've always recommended to my clients to separate the database from the front-end application with earlier SP versions and SQL Server instances. I also tend to stay away from the smaller SMB crowd...
This was before there was anything like the Express editions of things.
I'm thinking about a small Mom-n-Pop organization who have say 10 or so employees and has something like a publishing business or a non-profit organization with a magazine or something where they have a terabyte or so of archived scanned documents or a library
of a sort along with some third-party hosted open-sourced CMS for a public web "storefront" (think Drupal or some other LAMP/WAMP) as well as some business forms needing a little automation where a workflow solution would be a godsend in streamlining
some business processes. Most organizatio