With PowerShell you can send a test email from within SharePoint.

Run the following code with SharePoint Management Shell

$email = "[email protected]"
$subject = "Test subject"
$body = "Test body"

$site = New-Object Microsoft.SharePoint.SPSite "http://sharepoint"
$web = $site.OpenWeb()
[Microsoft.SharePoint.Utilities.SPUtility]::SendEmail($web,0,0,$email,$subject,$body)

// A True or False will confirm the message has been sent or not

On the interwebz I couldn’t find any way to set multiple Authentication Providers on a Web Application and I need to set the Authentication Providers to NTLM ánd FBA. The examples always show one Authentication Provider. Turns out the solution is very simple:

$NTLM = New-SPAuthenticationProvider -UseWindowsIntegratedAuthentication -DisableKerberos
$FBA = New-SPAuthenticationProvider -ASPNETMembershipProvider "MyMembershipProvider" -ASPNETRoleProviderName "MyRoleProvider"
$webApplication.UseClaimsAuthentication = $true
$webApplication.Update()
$webApplication.MigrateUsers($true)

Set-SPWebApplication -AuthenticationProvider $NTLM,$FBA -Identity $webApplication -Zone "Default"

Audiences in SharePoint Online are as good as useless, because the audiences are compiled once a week. Unless you exactly know what you’re doing you can give it a try, but waiting a week to get your audiences compiled and afterwards finding out that you forgot one property is not very satisfying.

According to this forum, the compiling will be once a day in the future. So, lets wait for that.

http://community.office365.com/en-us/forums/154/p/966/2953.aspx#2953

 

I’m creating a sandboxed web template for Office 365. I’m adding several web parts to a page and it’s working fine until I add Social web parts, like a Note Board or Tag Cloud. When I add one of these to a page I receive the famous “Cannot import Web Part” error upon deploying a site with this template.

The problem is that SharePoint exports the web part definition as a .webpart (v3) file. As it seems, Social Collaboration Web Parts don’t work well together with a v3 web part definition. When you change it to an old v2 (.dwp) definition it works perfectly.

So, this doesn’t work:

<webParts>
 <webPart xmlns="http://schemas.microsoft.com/WebPart/v3">
 <metaData>
 SocialCommentWebPart, Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c" />
 <importErrorMessage>Cannot import this Web Part.</importErrorMessage>
 </metaData>
 <data>
 <properties>
 <property name="Height" type="string" />
 <property name="AllowZoneChange" type="bool">True</property>
 <property name="AllowConnect" type="bool">True</property>
 <property name="ExportMode" type="exportmode">All</property>
 <property name="HelpUrl" type="string" />
 <property name="Hidden" type="bool">False</property>
 <property name="TitleUrl" type="string" />
 <property name="WebPartPropertyDisplayItems" type="int">20</property>
 Enable users to leave short, publicly-viewable notes about this page.
 <property name="AllowHide" type="bool">True</property>
 <property name="ChromeState" type="chromestate">Normal</property>
 <property name="AllowMinimize" type="bool">True</property>
 <property name="Title" type="string">Posts</property>
 <property name="ChromeType" type="chrometype">TitleOnly</property>
 <property name="MissingAssembly" type="string">Cannot import this Web Part.</property>
 <property name="Width" type="string" />
 <property name="WebPartPropertySpecifiedAddress" type="string" null="true" />
 <property name="HelpMode" type="helpmode">Modeless</property>
 <property name="CatalogIconImageUrl" type="string" />
 <property name="AllowEdit" type="bool">True</property>
 <property name="TitleIconImageUrl" type="string" />
 <property name="Direction" type="direction">NotSet</property>
 <property name="AllowClose" type="bool">True</property>
 <property name="WebPartPropertyAllowNewComment" type="bool">True</property>
 </properties>
 </data>
 </webPart>
</webParts>

And this works:

xmlns="http://schemas.microsoft.com/WebPart/v2">
 <Title>Posts</Title>
 <FrameType>TitleBarOnly</FrameType>
 <AllowRemove>true</AllowRemove>
 <AllowMinimize>true</AllowMinimize>
 <Description>Displays a list of your colleagues and their recent changes.</Description>
 <Assembly>Microsoft.SharePoint.Portal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c</Assembly>
 <TypeName>Microsoft.SharePoint.Portal.WebControls.SocialCommentWebPart</TypeName>
</WebPart>

Note the change from “http://schemas.microsoft.com/WebPart/v3” to “http://schemas.microsoft.com/WebPart/v2“. Also note the absence of the <webParts> tag, which isn’t allowed in the v2 web part definition.

In this sample I’ve taken the Note Board Web Part (SocialCommentWebPart), but you can use whatever web part you want by changing the TypeName.

I’ve installed Windows Server 2012 Release Candidate on my VirtualBox today. Everything worked fine till I installed the Guest Additions, it suddenly became slow and unresponsive from time to time, especially when using Internet Explorer. Because it happened after installing the Guest Additions, I thought it had something to do with the 3D acceleration, so I disabled that and now it works fine.

So, just disable 3D acceleration on the video properties and you’re good to go!

I found an article on the internet that could tell me how I can install SharePoint 2013 on a Windows Server 2012 machine. I however, just want to install the new SharePoint 2013 Preview on an a familiar machine, without all the Windows Server 2012 Preview nonsense.

I cloned an existing SharePoint 2010 virtual machine, with AD and SQL Server 2008 r2 already configured, uninstalled SharePoint Server 2010 and SharePoint Designer 2010 and started from there. This will also work on a newly configured machine, keeping in mind that we are using AD and SQL Server 2008 r2.

On the first attempt to install SharePoint 2013 (download link), the  autorun wasn’t working, so I opened the folder and ran setup.exe. Then I got a message telling me I need a few components:

  • This product requires Microsoft Identity Extensions.
  • This product requires  Windows Server Appfabric. Install Windows Server Appfabric and re-run setup.
  • This product requires Cumulative Update Package 1 for Microsoft AppFabric 1.1 for Windows Server (KB2671763)
  • This product requires Microsoft SQL Server 2008 R2 SP1 Native Client.
  • This product requires the Microsoft WCF Data Services 5.0.
  • This product requires Microsoft Information Protection and Control Client (MSIPC)

So, obviously I forgot to launch the pre-requisites installer first, prerequisiteinstaller.exe.

Now I could install SharePoint 2013 successfully and launch the Configuration Wizard afterwards. But upon configuring the database my system tells me that my SQL server has an unsupported version. I need to apply SP1 of SQL Server 2008 r2: http://www.microsoft.com/en-us/download/details.aspx?id=26727

After completing the configuration wizard, it dropped me into the Central Administration. I tried to run the wizard that generates a complete environment, but it failed and resulted in a corrupt web application. So my advice is, just like SharePoint 2010: skip the wizard and do it manually. I created a new web application and site collection and it works like a charm.

Microsoft has released SharePoint Server 2013 Preview this afternoon, or evening at my time. Download it here: http://technet.microsoft.com/en-US/evalcenter/hh973397.aspx?wt.mc_id=TEC_121_1_33

It’s also possible to get yourself an Office 365 setup with the new Office Suite, including SharePoint Online (yes, SharePoint 2013 Preview). With a few clicks you can walk into your own SharePoint 2013 setup: http://www.microsoft.com/office/preview/en/office-365-enterprise

According to a tweet from Maarten Visser about the Microsoft Office roadmap, we can assume a beta of SharePoint 15 will come halfway 2012 and the release early 2013.


Image from Maarten Visser’s Tweet

If you want to know more about the new features of SharePoint 15, read this post.