Office SharePoint Server 2007 Enterprise CAL > SharePoint Server 2010 Enterprise CAL

I’ll go through this in a little more detail.

InfoPath Forms Services (Updated): InfoPath was easily one of my favourite 2007 features. With 2010, while the experience has not changed too much for the client or the browser, Forms Services has been revitalized to handle the load that many organizations are willing to throw at it.

Special note: The InfoPath Web Part gets my gold star for best new out-of-the-box feature. The ability to include a form on a styled page makes Forms Services a much more desirable component to a solution.

Excel Services (Updated): By now, I think that many people are familiar with the updates to Excel 2010, and Excel Services has been updated to match the improvements. I think the improvements to Excel Services, namely in the areas of the REST and Web Services APIs, will hopefully encourage developers to make use of the technology in larger solutions, or in composite applications.

Access Services (New): Yes, it can be said that I am generally most excited about this new addition to the enterprise feature set. It’s simple: publish Access to SharePoint. Make it management, and universally accessible. Awesome.

Business Connectivity Services (Updated, but really - New): Many organizations tried and failed with 2007’s Business Data Catalogue, but from first proof of concepts, BCS has been redeveloped from the group up to truly be useful for developers and partners to implement powerful connections into line of business data.

Visio Services (New): Okay, I lied. I might be most excited about this feature. Visio is my favourite tool in the Microsoft stack, and has been for a while. Why is this exciting? The ability to link workflows to process diagrams, and then publish them to a SharePoint site is going to change how organizations look at SharePoint workflows as an effective tool for enterprise. Previously, this required a very qualified partner and a 3rd party toolset - now, it comes part and parcel with the Enterprise CAL (See some screenshots on the SharePoint 2010 website).

PerformancePoint Services (Updated, but New to SharePoint): They really upped the value of the Enterprise CAL with 2010, and this includes the addition of PerformancePoint. While the dashboarding and BI capabilities of 2007 were very powerful (and generally underused), PP Services allows for the creation of dashboards and scorecards that enable users to get to the right information, at the right time. In 2010, the PP features have been improved from previous versions as well, with elements such as decomposition tree, visualizations and improved filtering.

As well, there are a few other enterprise features, including web analytics and Enterprise-only search features.

Stay tuned for Part 4, SharePoint for Internet Sites.

Office SharePoint Server 2007 CAL > SharePoint Server 2010 Standard CAL

The standard suite of tools is a pretty standard mapping, however there are additional features to be delivered in 2010 that were obviously not in the 2007 release. From my standpoint, some of the most exciting features revolve around ECM, and the inclusion of document sets and metadata management.
The document set feature allows for the management of a group of related enterprise content as a single element. Document sets support grouped version history and metadata, as well as set-based workflow. This feature will enable organizations to manage content in a more enterprise-ready fashion.

Managed metadata, on the other hand, fulfills a feature that was largely missed in the 2007 release, where the gap was filled with custom solutions and some 3rd party tools that didn’t necessarily fit the bill. Effectively, the management of metadata will allow for a collection of centrally managed terms (for both taxonomy and folksonomy) which can then be attributed to items in SharePoint (If you want to learn more about this feature, read this blog post for an excellent review). Tagging, as well, has been added to the mix, but I’m not sure if this is as popular as it was a few years ago.

Overall, many of the features that made SharePoint 2007 so popular have been improved as well, including search, making an upgrade from 2007 very attractive for many organizations.

One feature that I do want to call out that is mainly for developers and partners would be Word Automation Services. This is a feature that, as solution developer, we could have used many times over the past three years. Basically, it is an engine that enables the creation and manipulation of Microsoft Word documents on the server, from SharePoint or other business systems. For example, a use case would be the development of contracts based on data collected from lists or InfoPath forms. Granted, this is made more powerful with the Enterprise feature set (see below), but still is available in the Standard edition.

Tomorrow: Part 3, Enterprise Features.

This is going to be several articles, focusing on Foundation, Standard, Enterprise, Internet Sites and Online.

Windows SharePoint Services v.3 > SharePoint Foundation 2010

From Introducing SharePoint Foundation 2010: “Windows SharePoint Services is now Microsoft SharePoint Foundation—the essential starting point for organizations that want the business benefits of Web-based collaboration combined with the value and security of an enterprise solution.”

As before, SP Foundation is going to be the free version of SharePoint that is arguably one of the most hated/loved in the Microsoft ecosystem. Features are generally the same as WSS, and is centered on collaboration with peers (through blogs, wikis, team workspaces and basic document management).

Personally, I think WSS was overlooked by many IT pros and business decision makers as a very powerful tool at the compelling price of free, and Foundation continues to be an important element in that space.

Just like WSS, Foundation is will still form the underlying architecture for the full server suite.

Important across all the SharePoint editions, the 2010 release is going to be supporting accessibility standards, ensuring that any solutions delivered with SharePoint 2010 comes with out of the box support for WCAG 2.0.

Tomorrow: Part 2, Standard Features.

Like in Joel Johnson’s article at Gizmodo, I too am most disappointed about the fact that the thinking behind the device isn’t going to make it to production. EAVB_IBGIEFKRHF

The Look and Hardware Interface

The device, as per every photo floating around the web, looks very similar to an iPhone. Roughly the same size, and perhaps 3-4 mm thicker, it’s definitely a good looking device. I suspect that the metallic plastic bevel will begin to show age faster than the rest of the device. The screen is large, and fairly crisp. For indoor use, the contrast is great, however outside, I did find glare to be a bit of a problem.

The hardware buttons also make a lot of sense. The standard “phone” and “end call/home” buttons, coupled with the Microsoft-mandated Windows button and a “back” button make for easy back and forth within the main functions of the phone. Hitting the Windows button brings up the TouchFlo interface for the Start Menu, which is very iPhone-similar, and finger navigable.

An interesting hardware feature of the device is the built-in zoom slider. It’s great for mobile browsing and for Google Maps, to quickly resize the view. Not exactly precise, or smooth, it does act as a great shortcut.

The one majorshortcoming of the device is the USB connector. This device uses the HTC ExtUSB connector, a proprietary USB format. It’s almost MicroUSB, but not quite. This, coupled with the fact that the headphones use a ExtUSB connector might be deal-breaker for some consumers. Maybe I’ll just get a Bluetooth headset (just kidding).

The slide-out keyboard is great, although, I am a little worried about the hinge. I’m hoping that it can stand the test of time, since I tend to be pretty rough with my devices. I think I once kicked a BlackBerry underneath a bus. It survived. I guarantee the Touch Pro2 wouldn’t.

The low-down: People are probably going to ask if I have an iPhone. I’m okay with that, because then I can make a clever comment like “Of course, there’s an app for that.” The hardware keyboard is well spaced and comfortable.

Power Consumption

Probably the number one reason why I didn’t go with an iPhone was battery life. Some of the Apple fans around the office here suggested a number of different options, like “Get a battery pack” or “Always keep it plugged in”, but as a mobile user, I need something that will last at least a day. The benchmark was my Palm Treo 750 with Windows Mobile 5.5/6.0; I would get 2-3 days of battery life with moderate voice usage and heavy data usage (I send ~1,500 e-mails and texts per month).

The verdict:We’re one day in on initial charge, and the battery indicator is hovering around 40%. It was a standard day of usage, plus a lot of time on WiFi. It won’t last the weekend, but it will last a heavy workday.

TouchFlo 3D

I thought I would be crazy about TouchFlo. I’ve seen it on other phones, and I’ve been jealous. It looks amazing on the web. People rave about it. Maybe I’m just old fashion, but I don’t think I need an additional layer between myself and my data. After using WinMo for the past 3 years (and being on a BlackBerry for years before that), I guess I’m okay with a simple user interface for a mobile device.

That being said, I don’t mind the TouchFlo interface. I mean, it is pretty, and there are a few features that I don’t think I want to get rid of. The bottom of the TouchFlo interface entertains a sliding bar to move between core applications, like Contacts, Mail, Messages, etc. Once I got the hang of using it, I was sliding all over the place. The Mail layer and the Messaging layer just make it more difficult to get around (I’m become accustomed to clicking Inbox or All Messagesright away. Yes, I know everyone rags on WinMo for not being as pretty as some of its cousins, but she’s functional. And I like that.

My view: I’m hoping that with TouchFlo for WinMo 6.5, they enable a little more control over features. There are some glaring omissions. The thing about a Windows device is that, as a power user, I have control. I can fire up a registry editor and do my thing - HTC should think about that.

Camera and Video

Both are sufficient for a mobile device. There a variety of situations where I use my phone as a camera:

• A car accident;
• A concert; and
• When I don’t actually need a camera, and I want to post something from Twitter.

That being said, my Twitter example can be found here. It isn’t great, but I don’t have a very steady hand either.

The long and short: If you have an expectation that a camera phone is going to produce even point-and-click quality, don’t buy this phone. I mean, really, people - the lens is tiny. It’s good enough to produce grainy photos of [insert band name] at [insert venue name].

A Few Hacks

So, there were a few things that I had to address before I was truly happy, both dealing with some registry edits that I had to take care of. Luckily, I quickly grabbed PHM RegEdit and went at it.

Issue One: There is an annoying dialog that pops up after every successful text message sent. Unfortunately, there isn an interface to manage said dialog. This was solved here.

Issue Two: There is a known issue with Rogers + Windows Mobile 6.1 that has to do with time stamping of text messages. While this isn’t related to the phone, it does make for an annoying, un-threaded text conversation.

This brings me to my last point…

WiFi and Data Speed

I was able to find the fixes, download RegEdit and apply the hacks from the comfort of my couch, in about 10 minutes. I wouldn’t necessarily use a mobile device as my primary internet access, but it did the trick.

From a cellular data standpoint, connectivity is decent. A little slower than I’d like, but fast enough to hit a few websites, or update Facebook in a pinch.

So, these are my impressions after the first 24 hours. I’m thinking that I will enjoy using the device, but it is going to force me to change how I use my mobile device. With the Treo, it was a purely functional play: it did what it had to do, and it did it well. I believe with the Touch Pro2, I may have to give it some slack: it isn’t just a business device, it crosses the line between my professional needs, with a little bit of gadget/toy too. Check back in a few days to see how I’ve fared.

In the mean time, does anyone recommend a good WordPress app for Windows Mobile?

Most appropriate, I think, is the question in regards to whether or not SharePoint is “good enough”. In my experience, many organizations are (a) already licenced for SharePoint, and (b) when implemented, are not using the feature set to its fullest potential. Food for thought, I suppose.

Microsoft SharePoint Social Computing
New MSFT website outling SharePoint’s potential in the realm of social computing, focusing on customer wins and case studies. Bonus: it’s running on SharePoint 2007 for Internet.

There have been a lot of times when I’ve had a client say, after a presentation, “How did you do that in [insert Office product here]?” In this case, I actually had to ask, “How did you do that?”

Recreating the NY Times Cancer Graph

The video (in Quicktime) is not short (and may not be exciting for people who don’t like making pretty graphs in Excel), but it is worth the watch.

Note: I realize this is my first post in 20 months. I will try harder, I promise.

 http://blog.gartner.com/blog/index.php?itemid=1637

For Fun: eboy’s FooBar poster.
Check it out. I just ordered one.

About my links: Should I be posting more links, less frequently, or fewer links, more frequently?

Planning for Performance and Capacity
“In order to provide specific guidance, several configurations were tested that cover the most common usage scenarios for Microsoft Office SharePoint Server 2007 and Microsoft Windows SharePoint Services 3.0.” From Joel Oleson.