Starting last October and ever since — October, November and December — the Cumulative Updates for SharePoint 2013 break federated search and break the cloud search service app.
That's not new information, but it bears repeating.
If you're using federal search or the cloud service app and you need those things to work, do not put the October, November or December cumulative updates for SharePoint 2013 on your farm.
It will be nothing but sadness and suffering.
The good news is that this past Tuesday — you know what happens the second Tuesday of the month. That's right. Our benevolent overlords at Microsoft release us those tasty CU bits. And I have reason to believe that that search error is now fixed in the January 2016 update.
So if you've fallen victim to that patch and things are broken, get your test environments ready as we can do some due diligence on the newly released January 2016 CU.
OK, SharePoint 2016: the latest public beta has a similar bug. I haven't checked lately but I think that bug is still out there.
Oh Boy Oh Boy
Speaking of SharePoint2016, of course, that will be coming out sometime this half of this year so make sure you're out there testing. The public beta is out there. You can play with that.
And that brings up another thing that I wanted to talk to you guys about. If you want to get these patches that I've talked about the January 2016 CU and all that, you can go out to ToddKlindt.com/SP2013builds.
It has all the builds. Go to the bottom get the most recent one.
I am in the process now putting together my SharePoint 2016 builds page and I would like your input so if you've got things you like or don't like about my SharePoint 2010 or SharePoint 2013 pages, let me know.
Let me know what I can do better for 2016. I've got some ideas. I've been brainstorming about that.
There are some things won't change but this is your chance to tell me what you think. I'm democratizing the SharePoint 2016 builds list, so email me Todd.Klindt@rackspace.com or hit me up on Twitter and let me know what you like.
I've been kind of slacking on my PowerShell tips and I wanted to bring this one up. This is one from PowerShell.com, a great SharePoint resource, obviously. It's not going to be cooking tips or anything like that with a URL like PowerShell.com.
This is blog post on how to create creating color-coded Excel Reports. Now the example they give here is about running services on a Windows box. But I always end up doing it for drive space on SharePoint machines and things like that.
What I want is some kind of easy visual indicator that something has crapped the bed. And bread lines are a great example for that. So I always forget how to do that because you gotta build HTML.
So what I've been doing for the reports that I've built is walk through the machines, walk through drives, look for the error case, build the HTML that has a red line of drive space below 10 percent or something and then I email that HTML file to a bunch of people and I use the send email cmdlet for that.
I've been doing that for a few years now but every once in a while I need to revisit that. I just I don't do HTML that much but this is a good easy way to code color-coded reports and you can schedule the job to run and do whatever.
That's a good thing if you've got a manager: managers like color and managers like getting emails.
I don't know what it is about managers. I don't know if when you become a manager they take you in a room and hit you on the head with something. I don't know. But something happens because managers love worthless automated emails with colors and graphs, so this is a great way to get that to your boss.
Title image by Jarren Simmons