December 2013 CU for SharePoint 2013 has been released

Be aware that all Update for SharePoint 2013 require March 2013 PU for SharePoint 2013 to be installed first.

Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled.

ATTENTION:

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into two separate downloads. One contains the executable file (identified as ubersrv2013kb2850024fullfilex64glb), while the other contains the .CAB file (identified as ubersrv_1). Both are necessary and must be extracted to the same folder to successfully install the update. Both are available by clicking the same Hotfix Download Available link in the KB article for the release.

See the KB article of the SharePoint Server CU for more details.

KNOWN ISSUE:

After installing the SharePoint 2013 Server December 2013 CU PerformancePoint Dashboard Designer no longer loads. When you try to open Dashboard Designer in SharePoint 2013, you receive an error message. You should not install the SharePoint Server 2013 CU listed below if you need PerformancePoint Dashboard Designer.

See the KB article of the SharePoint Server CU for more details.

For More Info:

http://blogs.technet.com/b/stefan_gossner/archive/2013/12/20/december-2013-cu-for-sharepoint-2013-has-been-released.aspx

 

Advertisements

SharePoint 2013 Workflows – Requirements

If you are interested in SharePoint 2013 Workflows. I can say SharePoint 2013 workflows has never been powerful as before. Which is come us with a tremendous improvement and completely new architecture. As every new System and new architecture brings new problems as always been , thats the nature of the new releases , so before going into dark side , you have to sure that you have working with last updates.

For the overview of SharePoint 2013 Workflows you can find more info from MSDN:

Workflow Manager 1.0:
http://msdn.microsoft.com/en-us/library/windowsazure/jj193528(v=azure.10).aspx

Windows Workflow Foundation:
http://msdn.microsoft.com/en-us/vstudio/jj684582.aspx

I would like to share some important upgrade and suggestions that may prevent your pains when you try to adapting the new SharePoint 2013 workflows.

First thing is the prerequisites ;

-> Bold Lines extra requirements and fixes many issues

*Workflow Manager 1.0 RTM (Shipped with SP2013 RTM)
*Workflow Manager 1.0 Service Pack 1
*Workflow Manager 1.0 Client for SharePoint 2013 Servers .
(If you installing Workflow Manager 1.0 via Web Platform installer it is automattically installs if your machine already installed SharePoint 2013)

*Service Bus 1.0
*Service Bus 1.0 Service Pack 1

I would suggest to use Web Platform Installer for install and setup and tracking for new upgrades for Workflow Manager and Service Bus.

*SharePoint 2013
*SharePoint 2013 and at least March PU update.
http://www.andrewconnell.com/blog/Workflow-Improvements-Changes-SP2013-March-PU-and-RTM-Developer-Tools
*I have suggested that Install Latest Current CU (Currently October 2013 CU for SharePoint 2013)

 *.Net FrameWork 4.5 (It is also SharePoint 2013 prerequisites)
*Always check the .Net FrameWork 4.5 Hotfixes.

For Developers :

*Visual Studio 2012 with latest Upgrade
*Office Developer tools for Visual Studio 2012 RTM (Again use Web Platform Installer for tracing new updates)
*Worflow Manager Tools 1.0 for VS 2012 (
If you installing Workflow Manager 1.0 via Web Platform installer it is automattically installs if your machine already installed VS2012)

 

Here Some other Suggestions;

* When after you register your workflow service as below command:

Register-SPWorkflowService -SPSite “http://blog.bugrapostaci.com” -WorkflowHostUri “http://workflow.bugrapostaci.com:12291” -Scope “Workflows” -AllowOAuthHttp
Make sure that you are using -WorkflowHostUri as full FQDN name , otherwise you may face some funcy Access denied issues.

*When you are using developing or testing don’t use System account. You may face also some System.Unauthorize exceptions which is also described technet it is not supported.

*Sometimes when you are working with Visual Studio you may face your latest build doesn’t deployed to the farm. That is a VS Caching problem. Always use latest VS bits. (Restarting VS or killing vshost exe can fixes that issue on next deployment)

Self-Service Site Creation is not working in SharePoint 2013

Assume that you have installed SharePoint 2013 and configured your MySite Host Application  . And Enabled Self-Service Site Creation feature on your MySite Host Application as described following article :
http://technet.microsoft.com/en-us/library/ee624362.aspx#enableselfsvc

To enable self-service site creation for the web application
1.Verify that you have the following administrative credentials:
To enable self-service site creation, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website.
2.In Central Administration, in the Application Management section, click Manage Web applications.
3.On the Web Applications page, select the web application that you created to host My Sites.
4.On the Web Applications tab, in the Security group, click Self-Service Site Creation.
5.In the Self-Service Site Creation Management dialog box, in Site Collections, select On. Optionally, in Quota template to apply, select a quota template.
6.In Start a Site, choose one of the following options:
a.Prompt users to create a team site under so users can create team sites from their My Site to use site feeds.
b.Be hidden from users if you do not want users to create team sites from their My Sites to use site feeds.
7.Click OK to finish.

Perform these additional steps to configure permissions for users to create team sites from their My Sites to use site feeds.
1.In the Policy group, click Permission Policy.
2.On Manage Permission Policy Levels dialog box, click Add Permission Policy Level.
3.Type a name for the permission policy.
4.Under Permissions, in Site Permissions, select the Grant option for Create Subsites – Create subsites such as team sites, Meeting Workspace sites, and Document Workspace sites.
5.Click Save.
6.In the Policy group, click User Policy.
7.On Policy for Web Application dialog box, click Add Users.
8.On Add Users, in Zones select (All Zones), then click Next.
9.In Choose Users, enter the user names of the users that you want to create team sites from their My Site to use site feeds. If all users can create team sites from their My Site to use site feeds, click the Browse icon. In Select People and Groups, click All Users, then click Everyone. Click Add, and then click OK.
10.In the Choose Permissions section, select

But the problem is even you did the configuration is correct , Still that the users doesnt use their mysite without their personal sites and looks the Self-Service Site Creation is not working. When you click Sites, Skydrive, NewsFeed links you have facing a blank page for it.

When you checked the ULS logs , you are facing following error ;

Skipping creation of personal site from MySitePersonalSiteUpgradeOnNavigationWebPart::CreatePersonalSite() because one or more of the creation criteria has not been met. [SPWeb Url=http://blog.bugrapostaci.com/Person.aspx?accountname=MyDomain\bugra]  http://blog.bugrapostaci.com/Person.aspx?accountname=MyDomain\bugra] Self-Service Site Creation == True  Can Create Personal Site == False  Is user licensed == False  Storage&Social UPA Permission == True  Site or Page or Web Part is in design mode == False

If you facing this , Looks that you have a problem with User License.

“In Office SharePoint Server 2007 and SharePoint Server 2010, when companies purchased a SharePoint Server Enterprise client access license (CAL) and deployed a server running SharePoint Server Enterprise, all users who accessed that server could use the full enterpr ise feature set. There was no way to determine the CAL that a specific user had. The only way to ensure that only users who had an Enterprice CAL accessed Enterprise features was to have separate Enterprise and Standard server deployments.

In SharePoint 2013, farm administrators now can assign licenses to users and enable license checks. WIth this new functionality, you can ensure that only users with the appropriate license can use a specific feature. This SharePoint Server license implementation is managed by using new Windows PowerShell cmdlets. By default, licensing is disabled in SharePoint Server. Administrators can opt to enable it by using Windows PowerShell.”
http://technet.microsoft.com/en-us/library/jj219627.aspx

if in your system new licensing feature of SharePoint 2013 was enabled but not configured. (In that article also contains how to configure licensing feature) You may probably facing this issue.

For resolving this you have two options.(You must use Windows PowerShell to create mappings for license types and to return user license types. There is no user interface for this feature.)

1) Configure Licensing feature correctly.

Get-SPUserLicense
$a = New-SPUserLicenseMapping -SecurityGroup <yoursecuritygroup> –License Enterprise
$a | Add-SPUserLicenseMapping
Enable-SPUserLicensing

2) Disable Licensing feature
Disable-SPUserLicensing

 

Office 2013 & SharePoint 2013 is RTM now

For more detail:
http://blogs.msdn.com/b/microsoft_business_intelligence1/archive/2012/10/11/time-to-celebrate-office-2013-amp-sharepoint-2013-released-to-manufacturing.aspx