310 likes | 523 Views
DM300. Scripted Farm Install. Ben Curry Sr. Instructor Mindsharp. Agenda. Why use scripted installs? Prerequisites Use setup.exe to Install Binaries Overview of config.xml Use PSConfig.exe to provision Farm Use stsadm.exe to build out Web apps and Shared Services Fun with stsadm.exe!.
E N D
DM300 Scripted Farm Install Ben Curry Sr. Instructor Mindsharp
Agenda • Why use scripted installs? • Prerequisites • Use setup.exe to Install Binaries • Overview of config.xml • Use PSConfig.exe to provision Farm • Use stsadm.exe to build out Web apps and Shared Services • Fun with stsadm.exe!
Why Use Scripted Installs? • Repeatable results for enterprise deployment • Rapid Deployment • Disaster Recovery • Just to be cool!
My Farm Setup • SharePoint Server 2007 • SQL Server 2005 • SQL Client on App2 • Windows Server 2003 R2 WFE1 (query) WFE2 (query) APP2 Central Admin Index APP1 SQL Server
Preparing For Installation • Add farm account to SQL Server with Security Administrator and DB Creator rights • Alternatively assign appropriate SQL permissions to pre-created databases • Run scripts as Installer/Farm account • Reporting Services requires farm admin/installer • Scaling to Query services is much easier • Need SQL Administrator rights during install • Installer account needs local admin during installation
Create Scripts • Scripts will be available for free download at http://www.mindsharp.com (Premium Content) • Install on Index Server first • App2 In our Demo • Copy adsutil.vbs from inetpub\Adminscripts directory to install directory • Take your time, and don’t make it difficult • Test, test, test • Get ready to go!
Lay Down the Bits • Don’t be afraid of the XML! • Config.xml files on the installation media • Standalone, Farm, Upgrade, Silent • Copy and edit • Setup.exe /config %location%\config.xml
Config.xml • Detailed TechNet Reference • Must install sts • Windows SharePoint Services 3.0 • Must also install spswfe • SharePoint Server 2007 • Display Level should be none or basic • Basic for this demo so you can see what is going on • If none, wait for setup.exe to disappear from taskmgr.exe before continuing • SERVERROLE should be APPLICATION
Examining Config.xml demo
Create Farm Databases • Use sqlcmd.exe to create databases • In SQL Server program files\90\Tools\BINN • Secure with additional script if you do not want SharePoint accounts to be security administrator and DB Creator • Take your time editing the DB Create Script! • Copy and paste for additional databases • Collation MUST be Latin1_General_CI_AS_KS_WS • Don’t ask me why, I don’t know
Create Databases • CREATE DATABASE SharePoint_Config_Contoso • ON • ( • NAME = SharePoint_Config_Contoso_data, • FILENAME = 'c:\MSSQL\Data\SharePoint_Config_Contoso.mdf' • ) • LOG ON • ( • NAME = SharePoint_Config_Contoso_log, • FILENAME = 'c:\MSSQL\Log\SharePoint_Config_Contoso.ldf' • ) • COLLATE Latin1_General_CI_AS_KS_WS
Provision the Farm • Use PSConfig.exe • It’s in the ‘12 Hive’ • Detailed TechNet Command-line reference • Psconfig.exe –cmdconfigdb <options> • Uses pre-created configuration database • Attaches server to farm (configDB) • Provision Central Admin • Create Web application (psconfig.exe –cmdadminvs –provision <options>) • Uses pre-created Central Admin content database • Prevents database GUID naming convention
Provision the Farm • psconfig.exe -cmdconfigdb -create -server app1 -database SharePoint_Config_Contoso -user contoso\mossfarm -password P@ssw0rd -admincontentdatabaseCentral_Admin_Content
Creating the farm and provisioning Central Administration demo
Start Farm Services and Build the Shared Services Provider • Use stsadm.exe to start farm services • –o osearch to start SharePoint Search • -o spsearch to start Windows SharePoint Services 3.0 Search • Create My Site Provider • Use –o extendvsto create Web applications • Uses pre-created content databases • Create Shared Services Provider Web App • Uses pre-created content database
Build supporting SSP Web applications, create the SSP, configure the SSP demo
Create and Configure Portal • Create Web applications by using –o extendvs • Apply Collaboration Portal template (spsportal) • Add Host Headers • http://my and http://my.contoso.msft • http://portal and http://portal.contoso.msft • Allows access via either URL • MSDN ‘translate.js’
Adding Host Headers • script.exe //nologo translate.js "Contoso Portal" > siteid.txt • for /f %%I in (siteid.txt) do SET SITEID=%%I • cscript.exe Adsutil.vbs set w3svc/%SITEID%/serverbindings ":80:portal.contoso.msft" ":80:portal" • Del siteid.txt
Configure Farm Operations • Logging Levels • Be smart • SMTP Server • Global outbound setting • Add Farm administrators • Remove local administrators • Best Practice
Configure Farm Application Settings • Enable Recycle Bin • Change Recycle Bin retention period to 90 days • Change Recycle Bin 2nd stage to 20% • Change max upload size • Add managed paths • Create HR embedded managed path site • Much, much more
Add Servers to the Farm • Lay down the same bits • Use the same config.xml • Change psconfig.exe settings • Start Services • Start Search – no roles • Then start Query • Will fail without psconfig.exe –cmdsecureresrouces! • Don’t forget the Host Headers • Copy 12 Hive and inetpub customizations • Could use solutions
Add Servers to the Farm • psconfig.exe -cmdconfigdb -connect -server app1 -database SharePoint_Config_Contoso -user contoso\mossfarm -password P@ssw0rd • IMPORTANT!! • Psconfig.exe –cmdsecureresources
SUBMIT AN EVALUATION For a chance to win an 8GB ZUNE! Submit evaluations on MySPC www.MicrosoftSharePointConference.com
© 2008 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries. The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.