I Have Uninstalled SharePoint for Good

C’mon, you’re not falling for that again, are you?

Do you use cloud VMs for your development? Would you like to?

I uninstalled my last local SharePoint machine about four years ago. That’s right, I don’t have SharePoint locally installed and haven’t had for years.

Instead, I use EC2 to host my SharePoint labs. It’s quite simply an amazing difference and it’s actually much cheaper than maintaining a laptop powerful enough to run the stuff locally. On average, when I’m working actively with SharePoint, I spend somewhere between $100 and $150 on VMs per month. That includes having and storing 10+ VMs that spin up in a matter of seconds, have virtually unlimited storage and performance, and can be scaled up and down at a click of a button. I really can run SharePoint 2013 with 244 GB of RAM or 32 CPUs, and I can do so with my workstation that I built in 2007.

Here’s the thing… It can be a hassle to get started. Lots of new stuff to learn.

I want to help!

If you’re interested in learning about how to work with cloud VMs, let me know. I’m contemplating releasing some of my existing tools that I use to manage my VM environment too, such as the four hour project I built a couple of days ago.

15-04-2014 06-36-37

Maybe I’ll run a few webinars or a recorded one-on-one session with someone and show how to set everything up and some tips and tricks for keeping everything running smoothly.

Heck, if there’s interest, I may even release the code for USPJA Labs, which is an immensely elaborate and powerful environment that we used to run hundreds of VMs during the USPJA years.

Leave me message, like, or otherwise let me know that you would be interested.

Found this article valuable? Want to show your appreciation? Here are some options:

a) Click on the banners anywhere on the site to visit my blog's sponsors. They are all hand-picked and are selected based on providing great products and services to the SharePoint community.

b) Donate Bitcoins! I love Bitcoins, and you can donate if you'd like by clicking the button below.
Donate Bitcoins

c) Spread the word! Below, you should find links to sharing this article on your favorite social media sites. I'm an attention junkie, so sharing is caring in my book!

Pin It
Read full story Comments { 1 }

Microsoft: Help Spread the Word that SharePoint On-Premises is NOT Dead

There’s been this rumor lately that SharePoint on-premises is dead. It is not, and I’ve told you so before, so you’re kinda stupid if you still think so. Anything I say is always correct. Just live with it.

Don’t want to take my word for it? Fine, I’ll show you evidence, but first, let me quickly recap what’s happened.

SharePoint 2016: Another Brief History of Nearly Everything

Back in the spring of 2012, Microsoft made the now famous comment of “cloud first” in their strategy for SharePoint. Then, when SharePoint 2013 came out, it seemed that there were few, if any, on-premises news at all. Few new features, still many of the same caveats; it could be seen and by some was seen as a sign that the on-premises version was now a red-haired step-child in Redmond.

A few months later, and I’m leaving names out to protect the innocent or ignorant, someone apparently reputable in the community had overhead parts of a conversation during the MVP summit, where someone else, who was in a position to know these things, stated that the on-premises version was going away.

Note: Yeah, this is all “he said, she said” and you should start to catch on right about now.

This lead to an uproar in the SharePoint community. Participants expressed everything from “Finally, the witch is dead” to “You’ll have to pry SharePoint on-premises from my cold, dead fingers”.

Of more concern to Microsoft, however, was that customers started getting nervous. With no clear message about the future, customers were hesitant to invest in SharePoint on-premises, and for those that couldn’t move to Office364.67, there were no offerings from Microsoft at all.

To put people’s minds at ease, Jeff Teper stated in no uncertain terms that there will be another version of SharePoint for on-premises clients, and for a while, there was great rejoice in the kingdom.

But it wasn’t enough. Even though Jeff confirmed an upcoming version during the SharePoint conference in Las Vegas in March 2014, the speculation turned away from whether there would be a new version at all to whether the upcoming version would be the last.

It’s not. And, if you actually know how to read, Microsoft has been saying that all along.

That’s What She Said

In case you haven’t bothered reading the initial confirmation from Jeff Teper, let me restate what he said: “We are committed to on-premises releases of SharePoint and Exchange on a comparable cadence to past server releases. “, with my emphasis added.

This public statement was from November 2013.

You could argue that the use of “releases” as opposed to “a release” could be a simple typo, but you can hardly argue that “comparable cadence to past server releases” is a simple slip of the fingers.

That didn’t stop anyone from speculating, though, and in recent weeks (I know, relative time references, right?) “someone” had overheard “someone else” saying that the next version would be the definite final on-premises version.

And we’re back to the “he said, she said” level. It’s not more trustworthy this time around, in case you’re not getting the implicit sarcasm.

Microsoft Needs Your Help!

So, this week, after continued discussion in SPYam, Jeff Teper clarified. It shouldn’t be necessary, but hey, he’s turning into an awesome guy, so he did anyway.

Here’s the quote he quipped:

I don’t know how to say this more clearly. We plan to do future server releases. We committed to a timeframe for the next one. We never have communicated or contemplated that its the last one and I’d ask you guys help correct people who might make that up. Just we’re not getting ahead of ourselves and talking about plans we’ve not made yet for n + 2 which we’ve never done in the history of the product.

This pretty much sums up everything that reasonable people (read: me) have been saying all along, and it makes a lot of sense. The fact that Microsoft isn’t announcing SharePoint 2019 doesn’t mean it won’t come; just that they’re focusing on SharePoint 2016 first. For the same reason, you’re not focused on next year’s vacation until you’ve completed the vacation this year, at least not nearly in the same amount.

And since Jeff is a nice guy (or has been replaced by aliens) let me do what he says and do Microsoft a favor.

SharePoint On-Premises is NOT Dead!

It isn’t dead now, it won’t be dead after the next version, and you can put that on a t-shirt.

SharePointIsNotDead

.b

Pin It
Read full story Comments { 6 }

A Modest Proposal. Jeff, Un-Gag the MVPs!

I’m going to propose something to Microsoft, specifically my new rising hero Jeff Teper, and the SharePoint community. I think this proposal may quell a lot of the complaints we’ve heard during the recent releases.

Before I make my proposal, and to introduce new readers to the issue at hand, let me give you the TL;DR (too long; didn’t research) version of the issue at hand.

A Brief History of Nearly Everything

During both the previous releases of SharePoint, meaning SharePoint 2010 and SharePoint 2013, Microsoft has been extremely strict on what information people should have. This has lead to community complaints that they’re not getting enough information to make proper decisions about which version to target for new developments, what features they can safely use and that will remain supported, and whether new features will make current development efforts worthwhile or redundant.

Part of the issue has been that a secret club of community participants (MVPs) have been given this information in advance, under the provision that they don’t say anything to anyone (NDA).

A typical example of how this can turn out is the removal of design view in SharePoint Designer 2013; the MVPs knew months in advance but couldn’t warn their customers that what they were implementing wouldn’t be as easily maintainable in the next version of SharePoint. The NDA forced the MVPs to give their customers bad advice. They couldn’t suddenly stop recommending using design-view based solutions when they learned about the inevitable end of the support because customers would ask why and “I can’t really tell” doesn’t work well when explaining business solution decisions to customers.

Yeah, I said TL;DR. It’s more complex than this.

How Can Microsoft Solve This?

Now, Microsoft itself may not be capable of producing enough information to satisfy the thirst for details and information about new versions. After all, they barely have time to keep their existing content up to speed, and with information changing at a rapid pace during development, staying on top of every update in every article, providing insights and analysis, commenting on possible usages, and so on will overwhelm any team of content authors.

Except one. The MVPs.

You see, the MVPs already write this information. They keep up to date. They know the upcoming features. They have access to the code earlier than most. They often have more extensive experience with SharePoint than technical writers at Microsoft.

You can see this if you look at what I call the MVP verbal diarrhea happening on release day for any public beta of SharePoint. Virtually every MVP will publish tons of content that is reasonably up-to-date (although there are certainly exceptions). Much of it is similar in nature because, you know, everyone has to break the news that SharePoint 2013 will have an app store, but it is usually of good quality and at least not any worse than a lot of the other content out there.

This verbal diarrhea happens because of the gag-order from Microsoft. By preventing the MVPs from writing anything until a certain date, they are creating a dam of content that will flood over the landscape when the gates open.

Of course, because Microsoft has a formal and strict policy on publishing any content, and in any case wouldn’t be even close to keep up with the demand for information, the market, the community, and the users are left with another problem: Should we do something in the current version of SharePoint or wait for the next? Without proper information, making that decision is impossible, so mistakes are made and money is lost.

Finally, Microsoft misses out on a lot of customer feedback. MVPs aren’t users, at least not in any statistically significant manner, and the customer early access programs are largely a joke in terms of both scope and detail.

During the pre-launch phases, where I’ve been staying ahead of most of the crowd in having information and opinions, I usually get more questions about upcoming features from Microsoft’s early access customers than I get from others because the official information is lacking, the MVPs aren’t talking, and Microsoft doesn’t have capacity to follow up in a proper way.

Tear Down the Wall!

So, here’s a chance to kill both birds with one stone: Un-gag the MVPs. That’s right, take away the NDA for any announced version of SharePoint. Let them write about anything that is in the new version, is possibly in the new version, or maybe just a pipe dream of a new version.

I mean, the content will be out there in any case. Non-MVPs get as much and often more information than MVPs. We, and by we I mean the rest of the non-gagged community, will write whatever we damn well please, which is often wrong, too speculative, slightly hopeful, or plan lies (at least according to some lesser beings).

By allowing the MVPs to write about the stuff, at least Microsoft has a group of well-informed individuals that they can give directions more accurate than what ‘we’ can deduce from our various sources. MVPs can be told to mark clearly any information as ‘speculative rambling’ or ‘refers to possibly vaporware features’ or something more politically correct. They can say “Based on what we know at this point, XXXXX, but know that this may change at any time” without being threatened to lose their hard-begged three-letter adornments.

A non-gag policy allows MVPs to work better with the existing content base as well. MVPs can create better content and not have to rush out the door or have to compete with a hundred “SharePoint Designer is Free!” posts at the same time. The content base will likely have less duplicate content and possibly more cumulative information if MVPs build on each other’s information instead.

Sure, there will still be a lot of content, some of it wrong due to changing features, but it will satisfy the community’s and users’ need for information and quench the attention thirst from MVPs on release day. Microsoft gets more feedback from a broader user base and can allow customers to better prepare for what’s coming and not lose money on bad decisions.

This doesn’t even preclude Microsoft from putting time-sensitive information under specific NDA. It’s as easy as marking an email specifically as “Keep your bread hole shut until XX/XX/XXXX”. The press does this all the time and deals with it well, knowing that their information advantage goes away if they break the trust.

So, I think it’s time to stop the secrecy policy for MVPs. It will benefit Microsoft, the MVPs, the community, and the users.

It won’t hurt anyone.

What do you say, Jeff. Will you be my and the community’s hero once more?

.b

Pin It
Read full story Comments { 2 }