Try spautoinstall Sent from my Windows Phone ------------------------------ From: Roger Carran Sent: 17-Aug-12 12:25 PM To: ozMOSS Subject: RE: Database names with GUIDs
In regards to production builds, PowerShell is really the way to go. You can specify nice database names for all of them, as well as any other configuration aspect. If you have deployed some databases already, this article gives a nice way to change things: http://www.bullspit.co.uk/2011/03/19/sharepoint-2010-change-the-name-of-the-administration-content-database. This is also using PowerShell, which I highly recommend for farm deployment (I don’t think I’ve done config/deployment through the UI for a long time now). There are also some good starting points on TechNet with ready built examples: http://technet.microsoft.com/en-us/library/gg983005.aspx Kind Regards, Roger Carran *Sharing Minds* *Knowledge | Communication | Collaboration | Productivity* *Mobile: 0411 598 110* *Web: www.SharingMinds.com.au <http://www.sharingminds.com.au/> * * * *Thinking about upgrading your Intranet? Then think Sharing Minds!* *From:* ozmoss-boun...@ozmoss.com [mailto:ozmoss-boun...@ozmoss.com] *On Behalf Of *Marko Salonen *Sent:* Friday, 17 August 2012 12:11 PM *To:* ozMOSS *Subject:* Database names with GUIDs Hi I am currently building my first production non-stand alone SharePoint 2010 farm. (Yay!) When running install and config I wanted to use a prefix for my databases, something like SP2010_Prod_<database>, which worked great for the _Config database, but after running the wixard the rest of them have the horrible GUID at the end. Not wanting to start all over, is there a clean workable way to rename all the databases, I.E. not just the WSS_Content databases? Cheers all! /marko MORETON BAY REGIONAL COUNCIL (MBRC) PRIVILEGED PRIVATE AND CONFIDENTIAL - The information contained in this e-mail and any attachments is confidential and may attract legal privilege. It is only intended for the named recipient/s. If you are not a named recipient any use of this information including copying, distribution and publication is prohibited. Confidentiality and legal privilege are not waived or lost as a result of mistaken or erroneous delivery. If you are not a named recipient, please delete all copies immediately and contact the sender to advise of the error. It is recommended that you scan this email and any attachment before opening. MBRC does not accept any responsibility or liability for loss or damage arising directly or indirectly from opening this email, opening any attachments or any communication errors. The views expressed in this email and any attachments are the personal views of the sender unless otherwise stated.
_______________________________________________ ozmoss mailing list ozmoss@ozmoss.com http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
