SharePoint 2016 more delicious with cinnaMINROLES; Now with FP1

13 06 2017

If you have been following Dojo for the last few weeks, you may have noticed that I have been riding the Sp2016 Ship lately. Not sure if that came across or not.

One of the most talked about new features in 2016 is the new MinRole topology. I could point you to the official Microsoft documentation, but instead, you should all go to Spencer Harbar’s blog. His indepth knowledge is quite invaluable.

So why MinRole you ask? 3 words…ZERO DOWNTIME PATCHING (maybe its 4?). Well, that’s the best thing for someone like me, but there are tons of other reasons why you want MinRoles. Spencer has 2 great articles that you should read before you continue here:


Ok, now that I am done brownosing that English dude, the reason for this post was to enlighten you on some not so obvious things, specifically around Feature Pack 1.

Feature Packs are like the new old Service Packs and they come in a few flavors:

  1. language independant
  2. language dependant

In November of 2016 Microsoft released the first Feature Pack for SharePoint 2016. You can read all about the cool new features it comes here : Feature Pack 1.

Today’s post is about MinRoles and the difference between pre and post FP1 topologies.

Before FP1 your minimum supported MinRole configuration had to be 4 SharePoint Servers:

  1. search
  2. application
  3. web front end
  4. distributed cache – yup, you heard right.

For High availability  you needed 8 servers:

  1. 2 search
  2. 2 applications
  3. 2 wfe
  4. 2 distributed cache…ugh

But, after FP1 that all changed as Microsoft introduced the concept of shared roles. This means you can now combine, application with search, distributed cache with front ends, and custom anything  you want.

The minimu supported MinRole config is now just 2 servers:

  1. application + search
  2. wfe + distributed cache.

For full HA all you need now are 4 SharePoint Servers.

  1. 2 app searches
  2. 2 WFE + Distributed Cache.

Not bad Microsfot, not bad at all!

Just thought I would let yall know. If you didn’t already. WHich you probably did, but just in case.



Ignite bound: The Age of SharePoint. 

3 05 2015

They said SharePoint 2016 was coming so I decided to go check it out.  Stay tuned to the dojo for highlights. 


View HTML pages in SharePoint Online.

23 07 2014

Did someone in your organization save an entire website in a document library?
Did they complain they couldn’t open the start.html page?
Do you have users that want to view html pages inside SharePoint online?
If you answered yes to any of these questions (i am aware of the irony of this post), then I have a solution for you!
Simply open your html files in your library using explorer view and change the extension from HTML to ASPX. It even works with Flash content.
Yup, its that easy (and confusing at the same time, but for other reasons).


SharePoint 2013 and office web apps; the hidden truth about how to install!

23 07 2013

I make it a habit to write about things that trip me up about SharePoint and almost always, I have had a pretty good idea as to why. But, this time I have come across something that I do not understand.

Yes ladies and gentlemen, installing office web apps 2013 on the d: drive will not fully work. Word Web app will start to work and then hang for 5 minutes and tell you that the service is busy.

The only known fix that i have come across is to uninstall owa, unbind, then reinstall on the c drive, rebind and bingo it works.

Why? I have no idea.

Hope this helps you guys out.


SP 2010 Disabling site Publishing Feature = Fail

14 06 2012

So here I am, trying to figure out how to create a page template. Of course SharePoint doesn’t like you to save things as templates if you have the publishing feature turned on ( i knew why, but the momentary laps in judgement due to my add, made me forget). So what do I do? Like a total noob, i go and disable publshing feature.
No Suup forrr JU! – soup nazi.
Errors all over the place. So naturally I said oops and tried to re enable it. It doesn’t scream at me.
But alas, the New Page Button is gone from the site actions menu.
Minor inconvenience i guess…but no it isn’t. There is more. I navigate to the Pages library to confirm its still there and it is. So i decide to create a new page and it does. But when i try to check it in i get:
-Invalid SPListItem. The SPListItem provided is not compatible with a Publishing Page.- And a bunch of red /.

Panic starts to set it.

But then I remembered something Yoda once said. Ok there are many things Yoda said that apply here, but none rang more true than:

May the Force be with you.

Powershell is a life saver. I did a quick search on syntax and ran these very commands:

PS C:\Users\spfarmadmin>Disable-spfeature Publishing -url http://yoursite/subsite -force

PS C:\Users\spfarmadmin> Enable-spfeature Publishing -url http://yoursite/subsite -force


Everything is back to normal. New Page button is back.

Now if i can only -force myself to stop doing stupid things in SharePoint, I would be set.

But then you guys wouldn’t have anything to read about.





What is the Matrix…err…SharePoint?

15 11 2010

“Unfortunately nobody can be told what The SharePoint is. Only be shown…” – Morpheous to Neo before he took the red pill.

This question comes up quite often and thanks to Dilbert, we now have a definitive answer…well sort of.

The wisdom of dilbert is upon us.

Now. If we can only have a quick and easy way to tell people what it is, our lives will be so much better.
Do you guys have an Idea?
Lets have a what is sharepoint contest. Simplest answer wins.

Leave your ideas.

Sharepoint 2010 loves Powershell

23 09 2010

As i dive deep into the bowels of sharepoint 2010 (or as I like to call it, Awesomeness 2010), I am seeing that the powershell is a vital and very useful administration component. The Scripting Guys have put up some tutorials that I think will be very useful for all you 2010 admins. Here they are:

Hope you guys like them.

Happy sharepointing.