While scanning a few blogs today – something that I haven’t taken the time to do frequently enough, it seems, I ran across Veronique Palmer’s blog entry which was a recap of her visit to SPC12 last week. (
I had the good fortune to run into Veronique at lunch one of the days and it was good to see her again. She has a huge source of energy running through her, and anyone who strays too close to her can’t help but feel the energy that she brings to SharePoint and, I can only imagine, the passion that she brings to her clients.
First, there was a lot of confusion and frustration about how Microsoft and SharePoint decided to release information about SharePoint 2013 (SP13) during this release cycle. Veronique was not the only one who complained about the seemingly targeted approach to the release of product information.
It seemed that the SharePoint team was following the lead from the Windows 8 team and keeping things as quiet as possible to avoid competitive product offerings as well as to maximize the “Wow” effect on the day of launch.
It might also have been the opinion of the SharePoint marketing team that with SharePoint 2010 doing so well in the marketplace, that the need for pre-launch buzz generated from conversations in the ecosystem about the product was minimal.
The potential downside of this is a reduction in the number of end-to-end product reviews that SharePoint could have received from partners and developers about the product, when each different type of developer or user was shown only the pieces of the product that were most necessary for them.
Another potential problem, which Veronique pointed out, was that time was “lost” in allowing consultants to be up to speed with the product at the time of launch. This had an impact on partners, as well, as many partners and consultants had a difficult time predicting the launch date, and many products had their timing set for post-January 2013, instead of being able to be ready for a November 2012 release date.
I can only imagine that Microsoft decided that it was, in fact, getting a good amount of feedback, and that these negatives were manageable.
The next set of points that Veronique makes in her blog entry apply to all users of SharePoint who are considering a SharePoint deployment.
It’s important to consider the following when considering/planning a SharePoint deployment:
- Do the research and go into your project with your eyes open about the possible alternatives.
- Make sure that you are listening to multiple sources for your information. Microsoft, consultants, partners, blogs, analysts, and other community sources for SharePoint are useful in rounding out your strategy.
- Understand that different SharePoint versions have different user interfaces and have different user expectations. Your training and procedures may have to regularly go through modifications as you move from version to version, so plan accordingly.
- Don’t cause yourself to feel too much pressure to move to a specific SharePoint version just because it is newer. By understanding the features of each SharePoint version, combined with the capabilities and experience of your teams, your developers/consultants, and partner solutions, combined with the lifetime of your expected deployment and when you might be ready for an upgrade, you will be able to select the right version for your current deployment and plan ahead for future releases.
- It should be understood that your users are going to resist change. Build this into your operations and training plans.
Thanks, Veronique, for getting the conversation started, and for giving me the impetus to write a blog entry again… (I really need to do this more often.)
One of my favorite weeks of the year is coming up – the Microsoft WorldWide Partner Conference. One of the best meet-ups of the week has always been the SharePint event. This year should be no exception.
This year, the Microsoft SharePoint Marketing Group has worked with Pingar and 3 other software companies, Axceler, Rackspace, and Idera, to host a meet-up for partners that work within the SharePoint ecosystem during the week of WPC12.
You know what they say… SharePoint by Day, SharePINT by Night!
This year SharePint will be on Tuesday, July 10, from 6-8PM at the Madison Avenue Pub, in Toronto.
WPC is a huge event, and while there are some important sessions for SharePoint partners, the real significant effort at WPC should be about meeting with other partners and working to grow your company’s network and connections. I think this is why the WPC Connect portion of WPC has grown to be (at certain times of the week) the busiest part of the conference. While it can be hard to find open time to meet with specific partners, at least SharePoint partners understand where they can meet their SharePoint peers and enjoy some good conversation.
If you haven’t already registered for WPC12, please do so at
I’ll be meeting with partners at WPC Connect, attending a couple of the sessions, and hoping to meet everyone at SharePint! If I haven’t already reached out to meet you, please reach out to me and let’s meet at WPC12!
I’m certainly looking forward to an amazing week in Toronto.
The SHARE 2012 Conference is coming up (April 23-26, Atlanta), and Pingar is a sponsor. I’m looking forward to it because of the focus on business solutions and applications that SHARE has as its primary focus.
It is well past time, in my opinion, for a SharePoint conference that is focused strictly on business-oriented solutions. The speakers and sessions have been selected by a committee of users, and have been curated by The Eventful Group, who has many years of solid conference experience.
As much as I love my SharePoint infrastructure and development friends, I think that the surface area for business solutions on SharePoint is very large and should be recognized as a significant and valuable contribution to SharePoint customer implementations.
I’ll be watching the keynotes and sessions to see how many SharePoint business “Roles” are introduced or discussed. I’m not enough of an expert to enumerate the roles that I think should exist for SharePoint business solutions, because I have a feeling that there are many more than I can describe right now. Excluding all developer, IT Pro, and infrastructure roles, I could probably describe 3 or 4 business user roles that need to exist for a “best practices” SharePoint implementation. However, I fear that there really should be 8 or more roles identified and explained. Perhaps, after SHARE 2012, I will be able to put more description behind these roles.
I notice that the folks at Bamboo have proposed a sample schedule for attending SHARE 2012. Niice!
There are so many incredible speakers, however, it would be hard to list all of the sessions that I would like to attend.
I’d just like to add that the Pingar booth/kiosk in the exhibitors area will be a great place to talk about business user roles in SharePoint, as well as how business users can benefit from rich information about documents. Yes, the magic that Pingar provides to SharePoint.
I hope to see you there!
SQL Server 2012 now requires processor core-based licensing for SQL Server 2012 enterprise edition, and core-based licensing is one of two types of licensing available for SQL Server 2012 standard edition.
For about 6-7 years now, ever since Oracle started charging for processor core, Microsoft enjoyed an easier licensing conversation because they licensed per processor, and not per core. I used to sell Microsoft technology, and had to answer licensing questions often about how their products were licensed, and was glad that Microsoft was only charging per processor, and not per core. It felt, at the time, that Microsoft wasn’t trying to penalize people for using the latest and greatest CPUs (which then were arriving with 2 cores, or 4 – of course, now, there are many more cores).
How times change. Apparently, Microsoft isn’t concerned about competitive licensing scenarios with Oracle any longer. I think that is probably a good thing for Microsoft. It probably also means that Microsoft’s internal models probably identify that they have been leaving money from customers on the table, and that moving to a per-core license will be able to extract a little bit more from customers than the per-server licensing model. All’s fair in product licensing?
Redmond.mag quotes Wes Miller, an analyst with Directions on Microsoft, as saying that a single Enterprise core for SQL Server 2012 will have a list price of $6,874 per core. These are only sold in two-core packs. A server can be partially licensed or fully licensed. A fully licensed server requires a minimum purchase of 4 cores. Of course, volume licensing customers and customers with an Enterprise Agreement and Software Assurance will have significant discounts off of the list price.
I do like the flexibility of the licensing model to allow customers to move licensed cores from on-premise to hosted cloud providers and back again.
I was pleased to see the analysis on thelowercasew.com:
The actual cost for EE is roughly the same as if you licensed 2 sockets of SQL 2008 R2 Enterprise Edition as long as it had 4 cores per CPU. The cost goes up as soon as you start using 6 core processors and above. The prevalence of 4 core processors means this likely won’t change much for many organizations.
Compared to SQL 2008 R2 Datacenter, however, there is a large cost difference. Datacenter costs $54,990 per processor or over $100,000 to license a 2 CPU system. You can now essentially get the benefits of Datacenter Edition (unlimited virtualization rights, etc.) for half the cost you would pay in SQL 2008 R2.
Even with this new licensing model there are still huge cost savings to be had by licensing all cores of a server and virtualizing your SQL 2012 workloads. It’s hard to argue with unlimited virtualization rights especially for those lightly loaded SQL workloads.
I wonder if this model will also fall through on the upcoming next version of SharePoint Server licensing that will be out sometime this year or early next year. My guess is that this will also apply to the next version of SharePoint Server. (I have no insider knowledge of this, this is just a guess.)
I miss PR. I was good at it. Hell, there was a time when both Fast Company and PR News declared me one of the best. Not because I liked working a billion hours a week, which is what it would have taken to rise to the top of my profession, but because I have some weird instinctual ability to know how people want a story told to them.
I had an interesting conversation the other day with a colleague, – a colleague who is from a Central European country. I’m not sure which one, exactly, but we were speaking about some new business ideas for SharePoint Directions, and she asked me if I was still wondering what to do. The thing is, though, that due to her accent, I wasn’t sure if she used the word “Wondering”, or the word “Wandering”. Even to hear her say the two words separately a few minutes later, my untrained and Western USA-educated ears had a difficult time trying to tell the difference What a difference one letter makes.
It started me thinking, though, about my journey with SharePoint Directions. – or in a bigger sense, with our journey in life.
To wonder is to envision, to question your direction, to question your efforts, your capabilities and your talents. To wonder is also to read, to study, to pray, to ask, to listen, to watch, to reason, to make plans. We must wonder before we can grow. Are we too busy to find time to wonder? Do we make the time to wonder regularly? Do you wonder how good you can be? Wonder regularly and wonder often. It’s good for you.
Wandering is the activity component to Wondering. Where To Wonder is to work from your chair, To Wander is management by walking around. Wandering is experimentation. Wandering is experiential. To wander is to try out your ideas, to practice that speech, to give that interview, to spend that extra hour with the client. To wander is to move into different circles and to expand into unknown areas that might be new and strange – until one wanders into them.
To wander is to act on your ideas, and to put your plan into practice.
I started asking myself if the time that I was spending on different tasks was time spent wondering or time spent wandering. It became easier and easier to make that judgment about what I was spending my time on. I did find, interestingly enough, that I was spending too much time wondering, and not enough time wandering. I don’t really know why it surprised me, or why I was a little saddened to realize that I hadn’t been wandering as much as I could have been.
I was struck by the simplicity of the concept between wondering and wandering. I was struck by how much time one could spend wondering, without reaching conclusions. It is only when wondering is followed by wandering that great achievements are made. And it is only when wandering is preceeded by wondering that people achieve at close to their capacity.
So, I will be trying to wander a bit more often. I will still be wondering – there is too much to learn. I wonder if this bit of inspiration is only for me, or if it also applies to others. I think that it might apply to others, but in this case, it only applies to me.
All because of one little letter. Are you Wondering? Or Are you Wandering?
I think that you are seeing right now why my blog is still being published under the
domain, and not under www.SharePointDirections.com. One of these days I’ll get around to putting the SharePoint Directions blog on-line, and that will be a work-only blog. But for now, you get work mixed in with personal reflections…
I’m participating in a SharePoint in the Cloud roundtable event (#FocusRT21) later this week (Thursday, July 21, 11AM PT), that should be very informative. There are some great experts on the roundtable, which will be available for the public to call into. I do hope that you can join us.
SharePoint 2010 also introduced a service application infrastructure that enabled service applications to be subscribed to by different SharePoint farms, enabling different farms to stay in synch by accessing centralized resources. This can be useful in a cloud environment – think of SharePoint farms at different plant facilities that are all leveraging a centralized product catalog, or business services. SharePoint can be a client, in this way, as well as a server. All that we have to do is to think about designing SharePoint applications from a broader perspective.
Office 365 is another example of SharePoint in the Cloud. In this regard, Microsoft is offering SharePoint as a Service. This is a little bit different than we have traditionally thought of SharePoint farms. Office 365 will bring the collaboration and information sharing attributes of SharePoint to the world, but it won’t bring the application platform characteristics to the environment. This will force SharePoint application developers to move to alternative ways of delivering their functionality. It will be interesting to see if Microsoft decides that they do want to offer platform capabilities on Office 365 or if they will be satisfied simply adding functionality to their “SharePoint as a Service” offering.
Richard Harbridge (@rharbridge) has collected a good group of experts for the roundtable. I hope that you can join us on Thursday!
I was exploring a little bit with my video camera while at MSFT Wordwide Partner Conference 2011 (#WPC11), and I ran into Martin Fifield of Nomadic Software. Kind of ironic that he was in a booth with his companies name on it, as if he had planned on being there, but perhaps his family isn’t constantly nomadic, but only periodically.
Nomadic Software provides middleware to being information and data to mobile devices. The also create mobile applications, but they’re real magic is in the connections to line of business systems.
We spoke for just a few minutes, and it seems to me that he is approaching the confusion and the dynamic nature of the mobile device market from a good position.
NetConnect sells a product called Team Portal, which is a hosted version of SharePoint that is dedicated per customer. One element that I really liked about Team Portal is that NetConnect has integrated an application marketplace within the SharePoint instances that they provide to customers. From this application marketplace, customers can rapidly install project management apps, workflow apps, crm apps, etc. Team Portal also has an iPhone client and a desktop client to make accessing and browsing SharePoint sites even more convenient in specific scenarios.
I am not a customer yet, but I will probably need to give this a try. It’s exciting to see that they are including solutions on top of SharePoint in this way.
I know that they are looking for additional solutions to add to their marketplace, and so if you are a software company (ISV) that is interested, please reach out to Lars.
While at Microsoft Worldwide Partner Conference 2011 (WPC 2011) this past week, I ran into Erica Toelle (@ericatoelle) and she shared that she had just that day changed roles at Fpweb.net, and has become a SharePoint evangelist for Fpweb.net’s great hosting services and offerings. We recorded a brief video about her role and about what she was expecting from WPC 2011, and here it is. Congratulations, Erica, on your new role, and Good Luck!