In the process of determining which SharePoint 2013 edition you need? Microsoft has provided a TechNet article containing all SharePoint 2013 features compared to the on-premise and online editions. This article lists the feature availability across Office 365 plans, SharePoint Online standalone plans and on-premise.
Comparing SharePoint 2013 editions is a bit hidden in the SharePoint Online Service Description, so I provided an overview and deep links below.
SharePoint 2013 on-premise
- SharePoint Foundation 2013
- SharePoint Server 2013 Standard CAL
- SharePoint Server 2013 Enterprise CAL
Office 365 plans
- Office 365 Small Business
- Office 365 Small Business Premium
- Office 365 Midsize Business
- Office 365 Enterprise E1
- Office 365 Education A2
- Office 365 Government G1
- Office 365 Enterprise E3
- Office 365 Education A3
- Office 365 Government G3
- Office 365 Enterprise E4
- Office 365 Education A4
- Office 365 Government G4
- Office 365 Enterprise K1
- Office 365 Government K1
- SharePoint Online Enterprise External Users
SharePoint Online standalone plans
- SharePoint Online Plan 1
- SharePoint Online Plan 2
Source: SharePoint Online Service Description, http://technet.microsoft.com/en-us/library/jj819267.aspx
Posted by Bram de Jager on May 20, 2013
Last week I presented at the Microsoft TechDays 2013 in The Hague, Netherlands. I want to thank the attendees for joining my session on Developing SharePoint 2013 Apps with Visual Studio 2012. The last session before the weekend after 2 days filled with sessions, big shout out to them!
You can find my slides and demo source code on Bram de Jager on TechDays on www.macaw.nl.
Other colleague speakers are Arie Leeuwesteijn with Async and parallel patterns and application design (level 200 in Dutch) and Dion Olsthoorn with Bouw cross-platform mobiele apps met PhoneGap (level 200 in Dutch).
Posted by Bram de Jager on March 14, 2013
Workflow Manager 1.0 (a.k.a. Azure Workflow) is the new workflow engine to support workflow in SharePoint 2013. This allows for a more scalable workflow engine which can be hosted on a separate (workflow) farm. The other option is hosting the workflow engine on the same server where SharePoint 2013 is hosted.
To deploy my environment(s) I use PowerShell. This is the same with configuring Workflow Manager 1.0. When running the Workflow Manager Configuration it generates the PowerShell command for you (see sample script).
Add-WFHost exception when configuring Workflow Manager
Although I use PowerShell scripts, it’s very likely to have the same issue and errors when running the Workflow Manager Configuration. When running my, slightly adjusted, script I got this error:
Add-WFHost : Could not successfully create management Service Bus entity 'WF_Management/WFTOPIC' with multiple retries within a timespan of 00:02:05.7093984..
The exception of the last retry is: The token provider service was not avaliable when obtaining a token for 'https://vm-sp-01.contoso.com:9355/WorkflowDefaultNamespace/$STS/Windows/'..
At C:\SPInstall\McwModules\mcwspinstall.wfm1.0\Ensure-WorkflowManager.ps1:117 char:19
+ $wfHost = Add-WFHost -WFFarmDBConnectionString "Data Source=$wfDBServer; ...
+ CategoryInfo : OperationStopped: (:) [Add-WFHost], TimeoutException
+ FullyQualifiedErrorId : WFRuntimeSettingFailed,Microsoft.Workflow.Deployment.Commands.AddWFHost
Solution to “token service provider not available” issue
It seems the service bus is not available, which is a local server address. I tried disabling the loopback adaptor, but that didn’t work out. After digging around some more I realized my environment has a proxy server. The checkbox “Bypass proxy server for local addresses” was unchecked in the Internet Settings (Control Panel » Internet Options » Connections tab » LAN settings).
After ensuring the local addresses are bypassed, the PowerShell script worked as a charm!
Posted by Bram de Jager on February 25, 2013
To play around with SharePoint 2013 I need a decent setup of a Domain Controller, SQL Server 2012 and SharePoint 2013 Server. To achieve this I use Hyper-V and want to reuse as much as possible, but it has it limits…
Every machine, virtual of physical, has it’s own SID. This can be retrieved via PsGetSid.exe from Sysinternals.com. The thing is, it seems that the Domain Controller needs to have an unique SID within the domain. Although the domain members are allowed to have similar SIDs.
When I setup my topology I use a base image for every machine. Meaning these all have the same SID. After I installed my Domain Controller and second machine which I wanted to join to the domain I got this error “The domain join cannot be completed because the SID of the domain you attempted to join was identical to the SID of this machine”.
The solution to this is renewing the SID of the member machine. I needed to run sysprep.exe to change the SID of my base image, which I use to create the SQL Server 2012 and SharePoint 2013 machines. After running sysprep everything worked as expected!
Posted by Bram de Jager on February 21, 2013
This week I was looking for the Dutch language pack for SharePoint 2013 Server. Most bits are available and I was surprised I couldn’t find the language packs for Server. The language pack for Foundation is easy to find on Microsoft Download Center: Language Packs for SharePoint Foundation 2013.
It seems Microsoft has named the Language Pack for SharePoint: Office Server 2013 Language Pack. Without any reference to SharePoint at all!
For now it’s only available via MSDN, TechNet and Volume License Center, try searching for “Office Server 2013 Language Pack”.
TIP: Make sure you select the preferred language before clicking the Download-button!
Posted by Bram de Jager on January 12, 2013
Installing SharePoint Server 2010 with a trial license is something that doesn’t happen often. Since we did install SharePoint trial edition we ran into an issue which I wasn’t aware of:
Trial editions and licensed editions of SharePoint, Project Server, and Office Web Apps products may not be installed on the same server.
The screenshot below shows the error message you get, directly after running the setup.exe.
For those who are wondering how to work around this, you can’t. The only solution is getting a license key and upgrade the Trial license to a Standard or Enterprise license. Afterwards you can install Office Web Apps.
Tip: Being aware of this I strongly recommend using the Standard or Enterprise license during installation instead of afterwards.
Posted by Bram de Jager on July 10, 2012