Alexander’s Blog

Microsoft has posted the following comparison of various Microsoft SharePoint 2010 editions on their Web site. For more information, including licensing details and pricing, click here.

You can permanently register the SharePoint PowerShell commands into PowerShell ISE so you don’t always have to manually add the command Add-PSSnapIn Microsoft.SharePoint.PowerShell every time you start PowerShell ISE. Here’s the step-by-step procedure.

1. Activate PowerShell Integrated Scripting Environment (ISE). By default, PowerShell ISE is installed on Windows Server 2008/R2 but not activated. To activate it you can use the Add Features wizard in Server Manager. The reason I prefer PowerShell ISE over PowerShell is because it is much nicer and offers a multi-line editor and additional help for scripting.
2. Start PowerShell ISE from Start, All Programs, Accessories, Windows PowerShell, Windows PowerShell ISE.
   CAUTION: Make sure that you start Windows PowerShell ISE, which is 64-bit, rather than Windows PowerShell ISE (x86) which is 32-bit.

1. Start PowerShell ISE and enter the command test-path $profile. This will either return a True or a False.
2. If it returns False then you can create a profile for yourself using the following command.
   if (!(test-path $profile)) {new-item -type file -path $profile -force}

   

3. The path to the profile is provided, e.g. C:\Users\SP_Admin\Documents\WindowsPowerShell. The name of the file is also provided, e.g. Microsoft.PowerShellISE_profile.ps1.
4. Open the .ps1 file in Notepad. The file will be blank. Enter the following command and then save the file (File, Save). Make sure that the file is saved with the original .PS1 extension and not .txt.
   Add-PSSnapIn Microsoft.SharePoint.PowerShell
5. Close and restart the PowerShell ISE. Your SharePoint PowerShell commands should now be available to you. Verify this by typing the following command. You should get a listing of all your sites.
   Get-SPSite
6. If you want to see all the SharePoint PowerShell commands that are available to you, type the following command.
   Get-Command -PSSnapIn Microsoft.SharePoint.PowerShell
7. For more details you can use the pipe symbol with the Format-List option (fl).
   Get-Command -PSSnapIn Microsoft.SharePoint.PowerShell | fl
8. You have over 500 cmdlets available to you. You can verify the total count by using the following command.
   (Get-Command -PSSnapIn Microsoft.SharePoint.PowerShell).count

Content Organizer is a new feature in SharePoint Server 2010. If you enable the Content Organizer feature it adds a library called “Drop Off Library” to the site. The idea is that after you fill out the properties of a file, the file can be automatically moved to another library or folder according to rules created by the site owner. In other words, this is a document routing feature available in SharePoint Server 2010. In Microsoft Office SharePoint Server (MOSS) 2007 the routing feature was available for records routing in the Record Center site. In SharePoint Server 2010 it is available for all the sites.

Due to a bug, or some people may consider this a “feature”, once you activate the Content Organizer feature the Drop Off Library cannot be deleted because the option “Delete this document library’ is not available under Permissions and Management.

Obviously, you can hide the Drop Off Library under Navigation but that won’t delete the library itself. I am not sure why the option to delete is not available in the Library Settings but there are a couple of ways to work around this problem. You can either use SharePoint Manager 2010 from CodePlex or you can use the PowerShell. I recommend the PowerShell option.

Option 1: SharePoint Manager 2010

SharePoint Manager 2010 is an object model explorer. You can open the site and set the AllowDeletion property to true and then save the setting. You can download the SharePoint Manager 2010 here.

Option 2: PowerShell Script (recommended)

The second method is to use a PowerShell script. I prefer this method because in my opinion this option is much safer and easier than installing additional software on the server. Here are the steps.

1. In Windows Server 2008 go to Start, All Programs, Accessories, Windows PowerShell, Windows PowerShell ISE. DO NOT start the 32-bit version (x86), make sure you are starting the 64-bit version.
2. Register the SharePoint PowerShell commands by using the following command. If you used the 32-bit version of PowerShell ISE the command will fail.
   Add-PSSnapIn Microsoft.SharePoint.PowerShell
3. Now one-by-one run the following four commands.

$spWeb = Get-SPWeb -Identity http://YourDomainName
$spLibrary = $spWeb.GetList(“http://YourDomainName/YourSiteName/DropOffLibrary“)
$spLibrary.AllowDeletion = “True”
$spLibrary.Update()

Replace the domain and site name in the above script, for example.

$spWeb = Get-SPWeb -Identity https://extranet.seattlepro.com/microsoft
$spLibrary = $spWeb.GetList(“https://extranet.seattlepro.com/microsoft/DropOffLibrary“)
$spLibrary.AllowDeletion = “True”
$spLibrary.Update()

As soon as you execute the last step and refresh the Document Library Settings page, you will see the option to delete the Drop Off Library available in the GUI, as shown below. Now you can delete the library.

If you have additional sites that you need to delete the Drop Off Library, you will need to run the scripts for those sites as well.

There is a free Wake-On-LAN GUI tool available that you can use to wake a remote computer up by either using it’s IP address or it’s Fully Qualified Domain Name (FQDN). You can use the Wake-On-LAN feature to start a computer either on the LAN or through the Internet.

You can download the tool here.

In Microsoft Office SharePoint Server (MOSS) 2007 there was a Collaboration Portal template that a lot of us used. Unfortunately, in SharePoint 2010 that template has been removed. That’s not the only template that has been deprecated in SharePoint 201o, there are seven templates that are no longer available in SharePoint 2010. Here’s a listing, in alphabetical order, of the new as well as the old templates that are removed from SharePoint 2010.

New SharePoint Site Templates

1. Assets Web Database
2. Basic Search Center
3. Business Intelligence Center
4. Charitable Contributions Web Database
5. Contacts Web Database
6. Enterprise Search Center
7. Enterprise Wiki
8. FAST Search Center
9. Group Work Site
10. Issues Web Database
11. Projects Web Database
12. Visio Process Repository

Site Templates No Longer Available in SharePoint 2010

1. Collaboration Portal
2. News Site
3. Report Center
4. Search Center
5. Search Center with Tabs
6. Site Directory
7. Wiki Site

Todd Baginski has an excellent blog post that lists in great detail all the new, subsite, deprecated and hidden templates in SharePoint 2010.

Some of the templates that are removed in SharePoint 2010 are simply hidden and you can install them using PowerShell. The Collaboration Portal template is one of those hidden templates. Some of the hidden templates, along with their code, include the following. Check out Todd’s blog for a complete listing.

1. Basic Search Center   (SRCHCENTERLITE#1)
2. Publishing Site            (BLANKINTERNET#0)
3. Report Center             (SPSREPORTCENTER#0)
4. Collaboration Portal  (SPSPORTAL#0)
5. Site Directory              (SPSSITES#0)

Installing Collaboration Portal Site Template

Here’s the method I use to install the hidden Collaboration Portal template in SharePoint 2010. First you need to create a new Site Collection, unless you want to use an existing Site Collection, and then install the Collaboration Portal template using PowerShell. In this article we will first create a new Web Application, then a new Site Collection, and finally install the Collaboration Portal site template in that Site Collection. In this scenario we will be creating the Collaboration Portal at the subsite level.

1. Activate PowerShell Integrated Scripting Environment (ISE). By default, PowerShell ISE is installed on Windows Server 2008/R2 but not activated. To activate it you can use the Add Features wizard in Server Manager. The reason I prefer PowerShell ISE over PowerShell is because it is much nicer and offers a multi-line editor and additional help for scripting.
2. Start PowerShell ISE from Start, All Programs, Accessories, Windows PowerShell, Windows PowerShell ISE.
   WARNING: Make sure that you start Windows PowerShell ISE, which is 64-bit, rather than Windows PowerShell ISE (x86) which is 32-bit.
   
3. Register the SharePoint PowerShell commands by using the following command. If you used the 32-bit version of PowerShell ISE the command will fail.
   Add-PSSnapIn Microsoft.SharePoint.PowerShell
4. If you don’t have a Web Application to work with then create a new Web Application in Central Administration. Go to Application Management -> Web Applications -> Manage web applications -> New Web Application.
5. Let’s assume you have a Web application called Intranet that is using the default port 80 and the URL for the top-level site collection is http://intranet.seattlepro1.com. To create a new site based on the Collaboration Portal template use the following command in PowerShell ISE.
   New-SPSite -URL http://YourSite:PortNumber -OwnerAlias Domain\Administrator -Name “Name of the Portal” -Template “SPSPortal#0”
   For example:
   New-SPSite -URL http://intranet.seattlepro1.com/sites/collabportal -OwnerAlias SeattlePro1\Administrator -Name “CollabPortal” -Template “SPSPortal#0”
   The SPSPortal#0 is the code that you need to create the Collaboration Portal template. Notice that it ends with zero “0″, not the letter O. The quotes are required around the name only if it contains spaces. Also note that if you use the default port number (80) then you don’t need to specify the port number in the above command.
   TIP! If you copy and paste the above command from the browser and the command fails, try deleting the last quote at the end of the line in Windows PowerShell ISE, type it again and then try running the command.
6. If you are not using host headers then specify a port number so the Web site will be accessible using that port number. For example, if your server name is SPserver and you want to use port 8090 then use the following command to create the template.
   New-SPSite -URL http://SPserver:8090 -OwnerAlias SeattlePro1\Administrator -Name “CollabPortal” -Template “SPSPortal#0”
   
7. Once the template is created you can go to the browser and verify that is was created by typing the address http://intranet.seattlepro1.com/sites/collabportal or if you used the port number then http://SPserver:8090.

You can also create the Collaboration Portal at the top-level site in SharePoint 2010. This can be useful when you are creating an intranet site collection. I don’t like to use the Team Site template in SharePoint 2010 for the intranet because it limits me from searching only the intranet site on the home page. You cannot search other site collections, unless you add a Search Center site. To add Search Center to the Team Site tempplate you first have to enable the Publishing feature, which may or may not be a big deal but even then on the homepage of your intranet you can still only search the intranet site. With Collaboration Portal you will be able to search any site, anywhere because when you search it will take you to the Search Center which offers enhacned search functionality.

Creating Collaboration Portal at the Top-Level Site Collection

To add the Collaboration Portal to the top-level site, use the following syntax.

New-SPSite -URL http://YourSite:PortNumber -OwnerAlias Domain\Administrator -Name “Name of the Portal” -Template “SPSPortal#0″

For example, New-SPSite -URL http://intranet.seattlepro1.com -OwnerAlias Domain\Administrator -Name “intranet” -Template “SPSPortal#0″.

This will create a top-level site collection for your intranet.

PowerShell Tip

You can permanently register the SharePoint PowerShell commands into PowerShell ISE so you don’t always have to manually add the command Add-PSSnapIn Microsoft.SharePoint.PowerShell every time you start PowerShell ISE. Here’s the step-by-step procedure.

1. Start PowerShell ISE and enter the command test-path $profile. This will either return a True or a False.
2. If it returns False then you can create a profile for yourself using the following command.
   if (!(test-path $profile)) {new-item -type file -path $profile -force}

   
   

3. The path to the profile is provided, e.g. C:\Users\SP_Admin\Documents\WindowsPowerShell. The name of the file is also provided, e.g. Microsoft.PowerShellISE_profile.ps1.
4. Open the file in Notepad. The file will be blank. Enter the following command and then save the file (File, Save). Make sure that the file is saved with the original .PS1 extension and not .txt.
   Add-PSSnapIn Microsoft.SharePoint.PowerShell
5. Close and restart the PowerShell ISE. Your SharePoint PowerShell commands should now be available to you. Verify this by typing the following command. You should get a listing of all your sites.
   Get-SPSite
6. If you want to see all the SharePoint PowerShell commands that are available to you, type the following command.
   Get-Command -PSSnapIn Microsoft.SharePoint.PowerShell
7. For more details you can use the pipe symbol with the Format-List option (fl).
   Get-Command -PSSnapIn Microsoft.SharePoint.PowerShell | fl
8. You have over 500 cmdlets available to you. You can verify the total count by using the following command.
   (Get-Command -PSSnapIn Microsoft.SharePoint.PowerShell).count