Category SharePoint

Spencer Harber has a new article on Technet, and it’s a fantastic explanation of how (and more importantly when) to use host named site collections.  I won’t repeat any of what he has already said, as it’s very well described.

Go read it:

http://technet.microsoft.com/en-us/library/cc424952.aspx

Office Web Apps Server is a new Office server product that delivers browser-based versions of Word, PowerPoint, Excel, and OneNote. It compliments SharePoint 2013 very well, but if your unfamilair with it, there is a fair bit of learning to go with it.  Office Web Apps can be used on devices such as Windows Phones, iPhones, iPads, Windows 8 tablets, and Android devices.

Ddeploying OWA takes some complex planning.  Microsoft has deployed Office Web Apps Server by using a topology that can support 200,000 users and based on our performance tests, an Office Web Apps Server, with two Intel Xeon processors (8 cores), 8 GB of RAM, and a 60 GB hard disk, should support up to 10,000 users where most of the usage is viewing...

Been having an issue with mysite themes in a demo rig I have configured.  Oddly the ribbon is showing no color, therefore the links to skydrive etc. are showing as white on white (took me a while to spot it was there at all).

Anyway – it is possible to re-theme the mysite by manually activating design gallery (I was logged in as administrator but you can change that to any mysite user name) via the following URL and pick a new theme

http://servername/mysitehost/personal/administrator/_layouts/15/designgallery.aspx

Got it I thought, silly me!

Whats odd is, that the newsfeed doesn’t adopt the changed theme, so I’m stuck with a partially working and mis-themed 2013 setup and I have no idea how it got broken to begin with.

One to file as a bug with Microsoft methinks!.

The new site policy options in SharePoint 2013 ar a vast step towards better and enforcable governance.by allowing retention policies to be applied, or even retrospectively applied to sites and site collections.  This means automatic site deletion or closure (technically read only mode) on a defined retention schedule similar to what you can usually do with a document or record.

This is going to become one of my favourite blog posting to refer to about this subject and I love the positive way it’s written:

http://blogs.technet.com/b/tothesharepoint/archive/2013/03/28/site-policy-in-sharepoint.aspx

Remember, it doesn’t excuse you from having to formalise this policy opportunity as part of a wider governance requirement with the business and ensure it is what you want to see happening autom...

A new set of conceptual videos that describe SharePoint 2013 authentication processes are now available:

• Windows claims authentication in SharePoint 2013
• Forms-based claims authentication in SharePoint 2013
• SAML-based claims authentication in SharePoint 2013

These videos step you through the details of claims-based authentication for user access to a secure SharePoint resource.

Got to be worth a watch given how darned confusing this space can be!

The entire blog post about them and a whole set of test guides is here:

http://blogs.technet.com/b/tothesharepoint/archive/2013/04/16/new-sharepoint-2013-authentication-process-and-test-lab-guide-overview-videos.aspx

At the preview release of SharePoint, stretched farms were not supported.

http://technet.microsoft.com/en-us/library/cc262485(v=office.15).aspx#hwLocServers

This is set to change with recent announcements from MS at least allowing limited support for a stretched farm.  MS it would seem have been doing some testing on performance and capacity boundaries and will support a limited set of stretch farm topologies under the definition of distributed topologies. All of these topologies are based on a prerequisite of minimal (< 1ms) latency between components of the farm.

This is important, as it means:

• No support for geographical stetched farms, so you cannot span cities and geographies with single farm topology elements
• Recognition of Support if the logical data center is comprised of one or ...

If you do not  have access to an account manager at MS, then you have to best guess licensing for SharePoint 2013.  If you do that, then you need to base your guesstimates on the Microsoft Open License without software assurance.

http://www.microsoft.com/licensing/software-assurance/

It is usually more cost effective to have software assurance but only if you want to maximise all the benefits of the Assurance programme.

So, for on-premise SharePoint 2013 without assurance, you need to start by considering what your user base looks like and consider a few standard architecture questions?

• How many users will you have?
• What does their profile look like (heavy search, light collaboration for example)?
• How many are internal?
• How many are external?
• What features do I need to exploit?

This is...

I was recently asked an interesting question in response to Office 2013 going to RTM, and I thought it would be worth sharing my thoughts.

The question is “has anyone internal come up with a “key reasons” to upgrade”

2013 is a game changer, it’s moved the product firmly into the realms of holistic strategy and should be thought about in line with a wider services organisational strategy. If you didn’t already know this, then you need to start rethinking the market value of this product set. There is no one compelling reason to upgrade – there are many reasons, however it all depends on the client, their internal and external environment and what their roadmap looks like and how it can be influenced by people like us.

I’d be looking at better SaaS opportunities, ROI from lower...

So, MVP Wictor Willen has discovered a nice flaw in the performance capability of personal sites, in that a farm can only create about 300 sites per hour.  My latest client has 170,000 or so users, that’s a challenge waiting for a solution and destined to create a number of late nights and some nifty powershell scripting.

Read Wictors excellent post here:

http://www.wictorwilen.se/sharepoint-2013-personal-site-instantiation-queues-and-bad-throughput

What a mess is emerging around Keywords, tags and hash-tags in SharePoint 2013.  I’m not going to repeat what others have so nicely already said so will direct you to a first rate post by Jasper Oosterveld that explains it so well.

Quodos to Jasper for putting the time in to thrash this post put, I would have given up and thrown in a support call to MS.

http://www.jasperoosterveld.com/2013/03/sharepoint-2013-keywords-tags-and-hash.html