In SharePoint 2010, the Managed Metadata Service provides the ability to publish content types from a central location called a hub. In my tip "Publishing Content Types with the Managed Metadata Service", I demonstrated how to configure content type publishing through the SharePoint User Interface. In this companion tip, I will demonstrate how to automate the configuration of the Managed Metadata Service hub, and the publishing of content types through PowerShell.
In a previous tip on Configuring Alternate Access Mapping in SharePoint 2010, we've seen how to configure alternate access mapping for a SharePoint 2010 site using the Central Administration page. How do we do this task using Windows PowerShell instead?
As SharePoint Developers and Administrators take advantage of PowerShell support in SharePoint 2010 to automate configuration and maintenance tasks they inevitably begin to run into issues. These include managing larger, more complex scripts, and sharing and managing of snippets and functions they want to reuse across the team.
Lately, there has been growing demand for information about Windows Powershell. The reason is because it is so powerful and easy to use. The built-in commands can handle administrative tasks that are just not possible through Central Administration. Although, Powershell can be used for different technologies we will concentrate on the usage of Windows Powershell for SharePoint starting with a brief introduction.
When we try to open PDF files from a SharePoint 2010 library using IE 8 or above, we get prompted to Save the file and it does not open in the browser directly. In a vanilla SharePoint implementation the browser always prompts the user to save the PDF file rather than opening it.
This behavior can be very annoying for end users and a bigger concern is that such behavior promotes saving the files on the local computer even if the document is designed for view only.
SharePoint has never provided an easy way for Administrators to recover a deleted site, or site collection. The recycle bin, introduced in SharePoint 2007 and supported on SharePoint 2010, has only supported recovery of list and list items. If a site or site collection was accidently deleted, the only way to recover was to restore the site or site collection from a database backup.
SharePoint 2010 introduced Site Workflows; workflows that can be manually started by a Site Administrator and are not bound to a specific list or library. Site Workflows can be useful for automating periodic administrative jobs, or extending business workflows with periodic batch processes. I like to think of them of being sort of like a timer job, but for a specific Site. The problem with Site workflows is that there is no out-of-box ability to schedule them.
Your Boss tells you that the budget has been freed up and new capital for upgrades will be available next year. Thus we will be purchasing SQL 2008R2 and SharePoint 2010. He wants you to determine an upgrade plan and any initial tips on performing the upgrade. He wants you to confirm what versions need to be purchased and see if we can run through a test upgrade over the next few weeks on a test box that is currently not being used.
SharePoint administrators need to run regular backups using PowerShell, the STSADM tool or in Central Administration. There is no "built in" way to automate these backups. Wouldn't it be great to devise a method to automated these jobs?