When you want to run SharePoint 2010 on either Windows Server 2012 or Windows Server 2012 R2 make sure your SharePoint 2010 is at least running Service Pack 2 (SP2)!Although Hardware and software requirements (SharePoint Server 2010) does not make a note about Windows Server 2012, the KB article 2724471 does outline the support for Windows Server 2012 and Windows Server 2012 R2.
Before the release of Service Pack 2 (SP2) for Microsoft SharePoint Server 2010, Microsoft did not support SharePoint Server 2010 in a Windows Server 2012 or Windows Server 2012 R2 environment.
However, SharePoint Server 2010 with SP2 has now been released, and this configuration is supported in Windows Server 2012 and Windows Server 2012 R2.
So, it’s supported to run SharePoint 2010 on Windows Server 2012, check out the KB article 2724471 and the description of SharePoint 2010 Service Pack 2. Enjoy all new goodies from Windows Server 2012!
[Update: SharePoint 2013 is not supported on Windows Server 2012 R2 for now. This will be supported when Service Pack 1 is released. Check KB article 2891274 .]
[Update: SharePoint 2013 Service Pack 1 is released, check Announcing the release of Service Pack 1 for Office 2013 and SharePoint 2013. Resulting in SharePoint 2013 being supported on Windows Server 2012 R2]
Posted by Bram de Jager on December 3, 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
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
Trying to install a WSP solution via scripting and wanting to wait for the solution to be installed? This is a common scenario I’m facing quite a lot. Every time trying to find the script again, made me decide to blog about it.
This PowerShell script checks if the solution exists in the Solution Store and waits for it to finish its deployment job.
Posted by Bram de Jager on April 13, 2012