Early this week on site deploying SharePoint 2010, the client wanted to create few site collections for their development team. He tried to create using the Central Administration and could not see any options for creating SharePoint site collections in their own databases!
Well, that’s not news to all of us in the SharePoint World! Is it?
Continue reading “How To Create SharePoint 2010 Site Collection In Its Own DB”
I apologise for not getting this done earlier. This is the index of all the posts I did to install MOSS from command line. I am planning to create a pdf document for this, not this week though. If you are a SharePoint blogger and would like to advertise in the pdf, please contact me. I have learnt a lot along the way and this method is just indicative of how you can use command line to install and configure SQL and MOSS. I have used these in testing, development and production environments with modifications as needed. For our project requirements I had to find this kind of solution! I could not imagine installing 1300 standalone MOSS instances manually!
At that time, there wasn’t much available on the web, just bits and pieces. These days, you will find many. I am sure this will benefit many. On a side note, I will share some screenshots of the final installation package that has been done – later next week or thereafter.
We go to pilot next week! I will be on the road for 3 months…. maybe…
SQL Server 2005 and MOSS Command Line Installation
1 Unattended SQL Server 2005 Installation
2 Configure MOSS using STSADM CLI
SQL Server 2005 Express Edition and MOSS Command Line Installation
1 SQL Server 2005 Downloads for MOSS
2 SQL Server 2005 Express Edition Downloads for MOSS
3 SharePoint config.xml
4 Script to install MOSS with SQL Express
5 Howto configure sql express to allow remote connections
6 How to enable SQL Browser Service using a script
7 SharePoint: Config XML and PSConfig
8 SharePoint: Let PSConfig and STSADM setup your MOSS
I can add this to my arsenal of SharePoint Scripts. Just perfect.
FULL_BACKUP.BAT – Use Control Panel – Scheduler to run once a week. Don’t forget the ‘Run As’ account also needs write access to the backup location, in addition to the Central Admin app pool identity, and the SQL Server Machine account. This command will backup the entire farm to the following file share. Don’t use drive:\directory format.
“c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm.exe” -o backup -directory \\servername\backupshare -backupmethod full
DIFF_BACKUP.BAT – Use Control Panel -Scheduler to run when you want differential backups. Remember the same security as above, but also it will fail if you add a content DB or Web App since the last FULL backup.
“c:\program files\common files\microsoft shared\web server extensions\12\bin\stsadm.exe” -o backup -directory \\servername\sharename -backupmethod differential
IIS_MetaBase_Backup.BAT – This is used to backup your IIS Configs to each IIS server, in their respective ‘metaback’ directories. Just add an additional line for each server you want to backup. It will create a backup of the metabase called ‘WeeklyBackup’ with a version appended. The password doesn’t matter, it just makes the backup portable.
cscript.exe %systemroot%\system32\iisback.vbs /s servername /u domain\username /p userpassword /backup /b WeeklyBackup /v NEXT_VERSION /e password
cscript.exe %systemroot%\system32\iisback.vbs /s servername2 /u domain\username /p userpassword /backup /b WeeklyBackup /v NEXT_VERSION /e password
cscript.exe %systemroot%\system32\iisback.vbs /s servername3 /u domain\username /p userpassword /backup /b WeeklyBackup /v NEXT_VERSION /e password
As Ben says, use at your own risk.
Stay tuned, subscribe via email