3. 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!
4. Repeatable results for enterprise
deployment
Rapid Deployment
Disaster Recovery
Just to be cool!
5. 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
6. 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
7. 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 inetpubAdminscripts
directory to install directory
Take your time, and don’t make it difficult
Test, test, test
Get ready to go!
8. 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
9. 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
11. Use sqlcmd.exe to create databases
In SQL Server program files90ToolsBINN
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
12. CREATE DATABASE SharePoint_Config_Contoso
ON
(
NAME = SharePoint_Config_Contoso_data,
FILENAME =
'c:MSSQLDataSharePoint_Config_Contoso.mdf'
)
LOG ON
(
NAME = SharePoint_Config_Contoso_log,
FILENAME =
'c:MSSQLLogSharePoint_Config_Contoso.ldf'
)
COLLATE Latin1_General_CI_AS_KS_WS
17. 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 extendvs to create Web applications
Uses pre-created content databases
Create Shared Services Provider Web App
Uses pre-created content database
19. 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’
20. 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
22. Logging Levels
Be smart
SMTP Server
Global outbound setting
Add Farm administrators
Remove local administrators
Best Practice
23. 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
25. 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 –cmd
secureresrouces!
Don’t forget the Host Headers
Copy 12 Hive and inetpub customizations
Could use solutions