Finally, the last session of the day with Todd Klindt showing his magic with stsadm, the command-line administration tool for SharePoint.
The slides? You guessed it, attached to this post as usual [8-|]
My notes during the session:
Template picker: ever wanted to have your users select the website template themselves the first time they connect to the site collection? Well you can. All you need to do is create the site collection using stsadm without specifying a template. This way the first time you connect to the site collection you will get the same dialog you get for creating a new site, allowing you to specify a site template.
Site Delete Capture tool: captures sites to disk before they are deleted from the Content Database
Always restore sites into a empty site. The restore operation does not overwrite content already present in the site, causing duplicate entries, etc.
when exporting sites, the files are actually CAB files. So, rename them to cab files and you can simply double-click the file to open it and view / export data directly
And now for Todd’s famous ‘Grand Finale’: move a site collection from one contentdb to another contentdb in a single command:
stsadm -o mergecontentdbs -> this new command was snuk in in one of the last hotfixes by Microsoft and allows you move a site collection to a different contentdb.
Explore it and test – test – test !
There is another great article out there: powerful command line administration for SharePoint @ http://www.microsoft.com/technet/technetmag/issues/2007/01/CommandPrompt/
HP has made a tool available to do some sizing for a MOSS environment. I have seen this tool in action on TechEd and I must say that it is a pretty neat piece of software. It asks you some questions about your environment (number of users, expected load, do you want high availability, etc.) and it comes up with a MOSS configuration that can be saved and updated later on. In addtition to that, being a HP tool, it gives you an overview of the necessary hardware you will need with current HP prices. This way you can easily show any manager what their requested configuration will cost very quickly, when they come to you with their big dreams of SharePoint, slamming them right back to reality [:D].The tool can be downloaded from: http://h71019.www7.hp.com/activeanswers/Secure/548230-0-0-0-121.html (login required)The description that is published on the site for this tool is:
The HP ProLiant Sizer for Microsoft Office SharePoint Server 2007 is an automated tool that provides a quick and consistent methodology to determine a “best-fit” server for your individual needs and enables you to both quickly compare different solution configuration (what-if scenario) and also to obtain a highly detailed, customizable server and storage solution complete with bill of materials and pricing. · It also addresses one of the most critical areas of Office SharePoint Server 2007 server design, performance and capacity planning for the storage subsystem. The storage sizing and configuration capabilities provide detailed best-practice storage volume and RAID recommendations to support the database and content storage needs, using HP direct-attach storage, HP StorageWorks MSA, or EVA Storage SAN solutions. · The tool solicits data or uses built-in defaults to determine the optimum solution, based on the Office SharePoint Server 2007 best-practice configurations and supported growth paths. The default configurations that can be selected include an entry level solution, highly available solution, and an application optimized solution. The tool’s “what if” feature allows very rapid comparison of the effects of workload changes, platform choices with respect to solution deployment, server capacity utilization, estimated network traffic. You will be allowed to select a configuration and customize for your particular environment, by adding or substituting components. · The HP ProLiant Sizer for Microsoft Office SharePoint Server 2007 was developed based on knowledge gained during extensive performance characterization of Microsoft Office SharePoint Server 2007 in the HP Solution Alliances Engineering performance labs in Nashua NH. It builds on HP’s collaboration with Microsoft and the Office SharePoint Server performance whitepapers available from HP Active Answers.
It’s always good to learn from others and that’s exactly what I was thinking when attending this TechEd session. The reason I am posting it on my blog is that the slides of this session show the migration cycle and the different steps that HP took. This information can help you if you are facing a migration towards MOSS in the near future.
This session also mentionned a sizing tool for Moss, which I will put on a separate blog post.
So, download the slides and review them. They are attached to this post
I was told in one of the session at TechEd that one of the most important things to configure in MOSS is enabling the output blob cache and set it to 24 hours. Not exactly knowing what the sepaker was referring to, I went looking for this and came across a post on th Microsoft Enterprise Content Management Team Blog.
This article goes through the various caching setting you can enable and configure to improve performance.
Go read it at http://blogs.msdn.com/ecm/archive/2006/11/08/how-to-make-your-moss-2007-web-site-faster-with-caching.aspx
If you are serious about SharePoint and want to get certified, then here are the exams you should take:
For IT PROs:
– Windows SharePoint Services 3.0 – Configuring
– Office SharePoint Server 2007 – Configuring
– Microsoft Windows SharePoint Services 3.0 – Application Development
– Microsoft Office SharePoint Server 2007 – Application Development
You can find more Microsoft Office SharePoint Server 2007 Learning resources on te following site: http://technet.microsoft.com/en-us/office/sharepointserver/bb310627.aspx
There are a few tools that have been posted on codeplex, that are worth using or at least exploring:
- Microsoft IT Site Delete Capture 1.0 – Simply captures sites that are deleted by end users and backs them up to disk using the event model. You have a recycle bin, but this is basically a site recycle bin (available only to administrators). (Works with WSS 3.0 and Office SharePoint Server 2007)
- MS IT Site Life Cycle Management 1.0 – Notify, Backup then Delete Unused Unneeded sites (Works with WSS 3.0 and Office SharePoint Server 2007)
- MS IT Usage Reporting Framework 2.0 – Simple reporting framework to gather usage and storage metrics on WSS 3.0, MOSS 2007 and works with multiple farms. Note the caveats with SQL read queries listed on the framework homepage (direct select statements against the database).
As mentionned , these tools can be found on codeplex @ http://www.codeplex.com/governance
Okay, here are some notes to remeber that I took out of the OFF209_SharePoint Governance and Information Architecture Guidance session presented by Joel Oleson and Shane Young.
The slides are attached to this post [:D]
Quotas: only apply to Site Collections. Do not apply to individual sites
Site Directory: do not use automtic listing of new sites. The reason for that is quite simple: the newly created sites are empty! So use the Approval workflow for adding new sites to the Site Directory after it has been reviewed for valid and usefull content.
While attending TechEd’s session OFF209_SharePoint Governance and Information Architecture Guidance by Joel Oleson and assisted by Shane Young there was a talk and demo for the SharePoint Asset Inventory Toolkit. This product was announced in Beta.
Basically, this product can be installed on a standalone laptop that you can connect to a customer network to scan the existing SharePoint infrastructure in place.
After check Jole’s blog, there are apparently 3 new tools for SharePoint that are announced in Beta.
Read all about them on Joel’s Blog @ http://blogs.msdn.com/joelo/archive/2007/08/18/three-new-sharepoint-solution-accelerator-programs.aspx