Showing posts with label SharePoint. Show all posts
Showing posts with label SharePoint. Show all posts

Tuesday, January 30, 2018

AvePoint Takes Fire for Unethical Marketing

Having worked in the Microsoft SharePoint space for many years, I know that it's unusual for SharePoint Independent Software Vendors (ISVs) to get much mainstream press coverage, so I was surprised to see a Washington Business article about an AvePoint marketing campaign. The article, All's fair in sales and marketing? Competitor blogs that Metalogix is for sale, tries to poach customers, highlights a shady marketing tactic recently employed by AvePoint against my former employer, Metalogix.

(Update: The Metalogix response, "Metalogix is Forever" has been posted now.)


Others have written about this dishonourable marketing move (for example: An Open Letter to AvePoint | An Unethical Marketing Campaign), and I can understand their frustration. The SharePoint partner community used to be a pretty tight-knit group focused on "coopetition." Sure, we were competing, but we also worked together to raise the profile of SharePoint--which BTW was a great strategy that paid off for everyone. As they say, 'a rising tide raises all boats.'

But that's just not the case anymore, as money poured into the situation, investors took notice and the atmosphere changed. A win at all costs mentality emerged from some companies and the whole situation was a lot less interesting for many of us who started in content management before the SharePoint era. I suspect this marketing ploy will backfire.




Wednesday, July 08, 2015

Office 365 Message Shows Openness at Microsoft

I was quite surprised to see this message in an Office 365 help page:

Why isn't my Office 365 app launcher working as expected?
If you're using Internet Explorer when you visit a team site or other SharePoint Online page in Office 365, the app launcher may not show customizations you've made, like resized tiles or apps pinned to the navigation bar.

What can you do?
## Try this first! Use a different browser. We recommend using Microsoft Edge on Windows 10, and if you don't have Windows 10, try using the latest versions of Mozilla Firefox or Google Chrome.

Everyone has been hacking on IE forever, but to see this level of openness from Microsoft itself is quite telling. Yes, they're promoting Microsoft Edge, but nothing wrong with that. There was a time when people at MS were saying silly things like "don't call it a bug, it's an unintended feature." I was at an event when Steve Ballmer called out that behaviour and told the audience to be open with customers. "If it's a bug, call it a bug." That was around 2002. It's good to see the openness continues.


Wednesday, April 22, 2015

5 Tips to Make SharePoint Easier for Non-SharePoint People

Here are some quick SharePoint document library tips to help people who aren’t familiar with SharePoint have an easier time.

#1 Simplify Versioning

A quick and easy way to help your users avoid pitfalls is to simplify the version settings for their document libraries. You may have some complicated process in mind that requires specific settings, but if that process is confusing your users, you should consider simplifying the version options. For example, if you don't need versioning, just turn it off completely. If you don't need minor versions, turn them off. People new to SharePoint usually don't know that there minor versions are only visible to them by default.
geeklit sharepoint versioning
One easy way to prevent conflicting changes is to enforce check out before documents are edited. This is a simple radio button in the version settings.

You would use this if you’re worried about your users making conflicting edits. Requiring that they check out documents before editing will eliminate the problem of conflicting changes, but you’ll need to educate them on checking in the docs when they’re done.

To add the column, go to the doc lib's settings page and find the "Columns" section. From there, choose the "Add from existing site columns" link and then select the "Checked Out To" column from the list.

#2 Add the “checked out to” Column

Since I just mentioned enforcing check-out before editing, the next tip has to be one of my favourites—adding the “Checked Out To” column to the default view. This simple change can make life so much easier for people new to SharePoint.

image

If you add this column to the default view, it's obvious to everyone which documents are checked out and who has them checked out.

#3 Show draft documents by default

Another option that is related to simplifying versioning is to show draft documents by default. This way you can allow people to see draft documents before they have been checked in. If a user sees a draft, he or she can talk to the person working on the document before making changes that would potentially conflict with the existing draft.

This saves lots of hassle because it's common for users to forget to check in new docs, or simply not understand why it has to be done before other people can see that a file has been added.

image

#4 Keep the permission model simple and manageable

This one is straightforward. If you want to save yourself some hassle. Use an inherited permissions model that uses groups instead of individual users and is flexible enough for everyone to do their job without going to the SharePoint admin regularly to extend their credentials. 

#5 Show your users how to sync their document libraries to their local folders

Note: You may need to install the install the SharePoint 2013 OneDrive Pro client to get this to work.

Many users feel more comfortable working in the Windows file system. They can do this with their SharePoint document libraries by choosing the "Sync" options or the "Open with Explorer" link. Once you have the SharePoint library syncing to a local folder, you can easily do things like paste files into the doc lib to upload them to SharePoint.

image

#6 Bonus Tip For Admins and Power Users

If you go to the library settings, you can use the "Managed checked out files" option to see all the checked out files and from there, you can even take ownership of them by choosing the "Take Ownership of Selection" option.

This is great when a document isn't showing because it only has a draft version and you're not sure who has it checked out.

SNAGHTML23a30039
image

Thursday, January 30, 2014

The Mystery of Why People Use SharePoint

I had to laugh when I read this blog post from the Calgary Herald: Is SharePoint a pain point? Maybe it’s time to ditch it. They used the image below (slightly modified here) to distance themselves from the "righteous" supporters of SharePoint.

image

Of course SharePoint isn't perfect, but if you require some features that SharePoint provides, then you should run a pilot and try it out; base your decision on your actual use cases. This quote from a white paper that I co-wrote with Colin Spence (he wrote this particular text) sums it up nicely:

“If end users already know how to use SharePoint and have received training on the key tools provided by SharePoint the organization can be more ambitious in the implementation. On the other hand if end users are completely unfamiliar with SharePoint and in general not open to change and not willing to take training, IT should carefully control the complexity of the SharePoint configuration. Projects can be seen as “failures” if a few important end users complain that the SharePoint solution is ‘too complicated,’ or ‘too time consuming.’”

It's a classic case of people believing that there is a perfect system out there and all they need to do is pick the right one. It's simply not reality.

Monday, September 23, 2013

Changing Site Access Request Email in SharePoint 2013 (Office 365)

The option to set the email address for any SharePoint site access requests has moved around in the last few versions, so I thought I’d post this for those searching through old posts looking for one about SharePoint 2013.

This setting determines who will receive an email when a user requests access to a particular site—usually when the user tries to access the site and is denied. The tricky part is that the email address for this request is not related to the site owner permissions, it’s just a string.

To find the setting, navigate to:

Site Settings (Gear icon on top-right) > Site permissions > Access Request Settings (in the ribbon)

First use the gear icon in the top-right corner to get to the Site Settings page. If you don’t see the Site Settings link, you probably don’t have sufficient rights to make this change.

image

Once there, click on Site permissions.

SNAGHTMLf46205b

This will open the “Permissions: <site name>” page where you can access the Access Request Settings option from the ribbon at the top of the screen. The option you’re changing is “Send all access requests to the following e-mail address.”

SNAGHTMLf4595d8

Simply enter the email address you’d like to use for access requests and you’re done.

Tuesday, August 06, 2013

Enable SharePoint Document Sets in Office 365

This still requires a number of steps, so here’s the rundown:

This first key point is that this feature is only available to Office 365 Enterprise plans. If you’re not sure which plan you’re on, check with an admin.

Note: You must be a Site Collection Administrator or a Site Owner to create or configure Document Set content types.

image
- Creating a new document set

1. Enable Document Sets for a site collection

2. Create a new Document Set content type

Note: you don’t need to worry about the “Configure or customize a Document Set content type” unless you actually want to customize something.

3. Create a new instance of a Document Set

image

After you create and configure a Document Set content type, you must add it to the library where you want users to create their Document Sets.

To do this, go to Library Settings > Content Types (section) > Add from existing site content types

image
- adding the new content type to the site

Tuesday, May 21, 2013

SharePoint 2013: Quick Launch Heading Without a URL

There are occasions when you’d want to create a heading in the SharePoint Quick Launch navigation without your heading being navigable. In the past, I believe it was possible to create a heading without specifying a URL, but in SharePoint 2013, the URL field is mandatory—at least from the Site Settings interface. (See below for update.)

Option 1: enter “#” as the URL from Site Settings > Look and Feel > Quick Launch

Option 2: Use the “EDIT LINKS” option under the Quick Launch and leave the URL field empty. Although, the URL field is mandatory from Site Settings, you can leave it blank from this interface.

image

Both of these options create a link to the site’s home page, but they allow you to create a heading without using an absolute URL to some random page.

Update: Option 3:

There is actually a way to do it the old fashioned way; it’s just not that intuitive if you happen to try the UI for editing the Quick Launch above. Go to Site Settings > Navigation and then scroll down to the Structural Navigation: Editing and Sorting section.

image

Wednesday, February 20, 2013

SharePoint Pro Magazine Article–So you want to be a SharePoint author?

An article I wrote about becoming a SharePoint author has been published on the SharePoint Pro magazine blog. Thanks go to Dan Holme for letting me fill in for him!

image

The article is called So You Want to be a SharePoint Author? Here’s a snippet:

“With the release of the SharePoint 2013 Preview, a great content machine has been switched to high gear. Articles, blog posts, training material, and documentation are all being crafted at a furious pace. And we can’t forget the books—lots and lots of books.

A quick search on Amazon reveals that a single stack of all the SharePoint-related books would be well over 100 feet high. If you’re one of the people thinking about writing your first SharePoint book, my advice to you is...”

Now you’ll just have to follow the link.  :P

Wednesday, January 09, 2013

SPC12: Developing apps for SharePoint 2013 with Visual Studio 2012

Speakers: Mike Morton, Sean Laberee

This session was an introduction to the new App model for SharePoint and Office. The room accommodated about 3500 people and it was packed.

  • loud cheers from the large crowd for new app dev model experience (e.g., just save and refresh instead of redeploying)
  • the new app model uses 'modern' web dev techniques such as JQuery and knockout.js
  • funny moment: during a demo, a presenter forget to close a quote and many people yelled out from the audience
  • creating web parts is even easier than 2010 visual web parts. (inc. client web parts for office 365)
  • cool that you can 'appetize' existing web apps
  • apps have events
  • use OAuth for security
  • apps can be MVC not just web forms
  • really cool that you can locally debug using a local DB and then deploy to Azure an it will automatically provision SQL Azure DB for you. This uses dacpac under the hood
  • debug uses iisexpress and no app registration is required
  • apps for Office can be packaged somehow to be apps for SharePoint—details pending

Saturday, December 01, 2012

Friday, November 30, 2012

SharePoint 2013 Conference–Upgrade Deep Dive

Speaker: Sean Livingston (Senior Program Manager, Microsoft)

Developing a solid foundation for your users is critical to the success of your SharePoint Server 2013 deployment - in this session we'll share the major changes in how upgrade works in SharePoint Server 2013 and how to best take advantage of new capabilities to enable and deliver a smooth upgrade experience to your users.

This was a 400 level session that described in detail the various out of the box upgrade options that are available for SharePoint administrators. The fundamental message of the session was upgrade is “safer and faster.”

image

This session was in a huge room and it was almost full. In fact, the session was actually moved to a larger room and there were still people standing in the back. Here are my notes:

· Deferred site collection upgrade is the main new feature. I wrote a post about the deferred site collection upgrade option when the SharePoint 2013 preview was first released. My message in that post was that it’s a good feature, but don’t confuse “deferred” with “incremental.” This is not a feature that allows you to take, for example, one site out of a site collection and migrate it to 2013 while leaving the rest of the content on a 2010 server.

· In short, the deferred site collection upgrade allows SharePoint 2010 customers to “upgrade’ to SharePoint 2013 but still run site collections under the SharePoint 2010 code base. In other words, you have to upgrade the DB schema, but you can run 2010 site collections in 2013. This means--in principle--that custom code for SharePoint 2010 should just work and continue to work until you’re ready to upgrade the site collection. Once you do that, you’ll be running on the 2013 code base.

· Note that this is all at the site collection level—not on a sub-site by sub-site basis.

· Upgrade preview creates a copy. default is 100MB mac. that copy will actually be used is the site collection is upgrades. The size is configurable.

· Upgrade queue is used to control how many upgrade actions are happening at the same time. upgrade throttling. PowerShell upgrade commands will honour the upgrade queue unless you explicitly override it.

· Performance is about 5mins for a small site collection and can be as quick as 45 seconds. However, Sean was clear that, if your site collections were slow to upgrade last time; they will be slow to upgrade again. The “more stuff you have” the longer it will take. This includes features, numbers of sub-sites. it could take hours to upgrade (for “big and gnarly site collections”).

· You can run PowerShell commands to get all the site collections and pipe them into the upgrade queue so that they are all upgrades.

· get-spsite is now shown by default  shows compatibility level in PowerShell commands

· get-spsiteupgradesessions info will show what’s going on the in queue on the server

· get-spsite | upgrade spsite is the basic upgrade command

· Sending email updates when site collections are queue and/or completed is an option. The default is to send mail if upgrade was UI initiated.

· Evaluation site collection creation uses SQL Server snapshots. if mirroring is being used, it won’t work.

· This process snapshots the whole DB regardless of how many site collections are in the DB. Then the site collection is cloned (in the original DB) with -eval added to the URL.

· Expiration date is set for evaluation copy. You can optionally added it to the upgrade queue. Then the snapshot is cleaned up.

· If you don’t have snapshot, a different process is used—a site collection backup. 85GB is the recommended max size for this option. Then backup is restored to a -eval URL. Then the backup is cleaned up.

· SharePoint 2013 does not support partially trusted code solutions. It still supports sandbox. Bin directory is full trust only.

· Claims authentication is now default for new web applications. The recommendation is to use claims mode exclusively. Existing 2010 claims providers would just work.

· If you delete s site and then upgrade the site collection(or apply a CU patch), the site recycle bin can now restore the site (by running the upgrade. This means recycle bin is now much safer.

· Cross farm services compatibility means now that you don’t have to do a big bang upgrade . 2013 federated services can be consumed by 2010 farm.

· Added in RTM is a maintenance window feature. These are called maintenance windows objects. many settings such as start, end, Duration. It also allows you to display a message to users about maintenance; that’s handy.

Sunday, November 18, 2012

Wading into the SharePoint Conference

As part of my SPC as an Attendee blog series, I’ll be publishing some posts about specific sessions. It’s getting late now, so I’ll have to continue with that over the next few days.

image

One definite highlight at the Microsoft SharePoint Conference 2012 was the Jon Bon Jovi concert at the attendee party. The venue (just like the last SPC in Las Vegas) was the Mandalay Bay beach. As you can see in the photo above, the stage is actually across the water from the beach, so the best ‘seat’ available required wading into the pool. I decided that I’d take the plunge and was pleasantly surprised to find that the water was actually warmer than the air.

Yes, they did have lifeguards on duty (lots of them), so you can rest assured that the attendees were safe.

IMG_2483
-
the fireworks at the SPC12 concert were amazing

Monday, November 12, 2012

SharePoint Conference as an Attendee

SPC as an Attendee

I’m writing this post in the first developer session of the Microsoft SharePoint Conference 2012 in Las Vegas. This is the first time I’ve attended SPC and not spent a lot of time either preparing speaker sessions or working booths in the exhibit hall. This year, I’m working the Microsoft booth but most of my time will be spent attending sessions and learning as much about SharePoint 2013 as I can absorb. However, as an MVP, I also want to do something for the SharePoint community at large, so I thought I’d write some posts about SPC as an attendee.

TN7111212124220_1

The first thing to note at SPC12 (aside from coffee costing $4 in my hotel room—if I make it that is!) is that the scale is not just as big as ever, but bigger.

VegasAtNightMix64floor
- the cool thing about this view (Mix on the 64th floor of The Hotel) is that we could actually see bats flying into the Luxor’s beam—presumably to catch insects attracted to the light

There are roughly 10,000 people here at the Mandalay Bay Convention Center. The first SharePoint conference I attended had roughly 400 attendees and last year’s event was about 7500. That’s amazing growth.

IMG_2429
- excellent to see NCompass Labs mentioned in the SharePoint timeline

image
- 10,000 people having breakfast

SharePoint Conference Keynote

#spc12 was the top trending tag on Twitter during the keynote this morning. What’s even more impressive about that is that 10.000 attendees from 85 countries can pretty easily overwhelm the network. I couldn’t even get on.

I was wondering about the strong Yammer content at this show (including the keynote), but now it makes sense to me.  Microsoft is working hard on the SharePoint/Yammer integration, so waiting for the next SharePoint conference would be too long. During the keynote, they showed the current integration, talked about the future and demo’d a Windows 8 app for Yammer. Also, they announced that Yammer will be free with SharePoint online (inc. features you'd have to pay for in the paid Yammer subscription today).

I was impressed with the customer video. It featured a Nationwide SharePoint “Spot” solution that uses Yammer today. It looked great. I was also impressed that the keynote Office 365 videos were run out of one of the European data centers. That was a gutsy move for such important demos and they looked great. Microsoft wanted to make the point that performance doesn’t have to suffer because you move to the cloud and that point was clear.

IMG_2423

The exhibit hall is about 30% larger and boasts 250 partners. I’ll have to write more about the exhibit hall. There are a number of additions to the exhibit hall this year including the community lounge.

image

And here’s a random Vegas image for you…

IMG_2438
- coolest vine rack in Vegas… baby

Tuesday, November 06, 2012

Installing SharePoint 2013 on Windows 8 Client Hyper-V

[Author’s Note: This content has been unlawfully copied and pasted into another blog. I’ve asked the offender to take it down and hopefully he’ll have the common sense to respect my request. Update: after I messed with the thief a bit, he finally took it down. Victory!]

For me, one of the biggest enhancements in Windows 8 is the ability to run Hyper-V in the client O/S. This means I don’t have to have a server O/S running on my laptop; I can simply run virtual machines with whatever I need. For example, the shiny new RTM build of SharePoint Server 2013 that was released recently.

There are already a bunch of useful and detailed posts describing the install process for the SharePoint 2013 Preview. Here’s the short version for people who want a relatively simple RTM setup on a Windows 8 client machine (i.e., not running Windows Server 2012 as the host operating system).

SharePoint working on it from geeklit.com by Stephen Cawood

Caution: Hyper-V will only work if your BIOS/hardware/CPU support Hyper-V. It’s a really good idea to check first before you try to use it and get frustrated. Whenever I order new hardware, I explicitly ask if it supports virtualization and Hyper-V. That way when I get something (e.g., a CPU) that doesn’t work—and that happens—I can return it for something that will work.

First, this setup is “relatively simple” because I chose a particular setup and I repeat it often. I run SharePoint in a Hyper-V virtual machine in a single-server farm. I install SQL Server and the domain controller role on the same virtual machine. This means I can export the VM, import into a different Hyper-V instance and it all just works. Because the whole setup is self-contained and doesn’t require Internet access, it’s great for demos, webinars, conference sessions and other presentations. However, this is not the best practice for a production SharePoint install. For example, you should not install SharePoint on a domain controller.

[Update: By request, here are the hardware specs for my setup: Dell Precision M4600 laptop with 16GB RAM and Intel Core i7-2860QM CPU @ 2,5 GHz. I’m allocating up to 8GB of RAM to the SharePoint VM because it’s self contained and I only have to run the one image.]
Step 1: Install Windows 8 and Add the Hyper-V Feature.

Once you have Windows 8 running, scroll to the top or bottom corner on the right side to open the fly out menu and then choose Settings > Control Panel > Programs and Features > Turn Windows features on or off. Then check the box next to Hyper-V and install it. This will require a reboot.

SharePoint 2013 install from geeklit.com by Stephen Cawood

Step 2: Create a New VHD in Hyper-V
I’m choosing Windows Server 2012 so I’ve downloaded that .ISO file from MSDN and selected it as the O/S when I created the new virtual machine in Hyper-V. I’m going with a 30GB VM with 8GB of RAM (but I can always up these numbers later). If you don’t need Office and/or Visual Studio, you won’t need 30GB of space.

Note: The initial O/S image file will be less than 10GB. After installing SharePoint Server, the VHD is roughly 19GB and the image is using 30GB of the 50GB.
Step 3: Install the O/S (Windows Server 2012) and Name Your Virtual Machine
(Changing the name after installing SharePoint has historically been tricky.) I’m installing W2K12 Datacenter Edition with the GUI. Remember to activate Windows after you install. No one likes a VM with an O/S that hasn’t been activated. After you’ve installed the O/S, run Windows Update.

Note: If you choose Windows Server 2008 as your O/S, it will take a while. The last time I installed it, there were 123 W2K8 updates.

SharePoint 2013 install from geeklit.com by Stephen Cawood

Step 4: Add the Web Server and Active Directory Domain Services Roles
I also add the Wireless LAN Services feature. Once you’ve installed AD, you’ll have the option of promoting the server to a domain controller. After that is finished, create the domain accounts you’ll need. I always add one for myself and another to use as the SharePoint admin account.

Step 4: Install SQL Server
I’m installing SQL 2012 as a stand-alone server (default instance). It’s a simple install process. I install the Engine (obviously) with the client and management tools. If I need more, I’ll add it later.

SharePoint 2013 install from geeklit.com by Stephen Cawood

Note: I often export the virtual machine and save a copy at this point so that I have a base image of the O/S with SQL Server. Since both of them have been released recently, that’s what I did this time. You can also create a snapshot, but I’d rather just export a reusable copy than increase the disk space needs of my base image.

Step 5: Run the SharePoint 2013 Prerequisite Installer

SharePoint 2013 install from geeklit.com by Stephen Cawood

Download the SharePoint RTM ISO from MSDN and launch the default.hta file. The setup file will run the product install, so don’t run that first. You want to first run the prereq install.

Note: I ran into an odd “File Not Found” error when installing the prerequisites. I have a theory, but no hard proof about why it was happening. I think that W2K12 mounting ISOs works differently than it did in W2K8. It seems that when a mounted ISO needs to continue an install after a reboot, it can’t find the files because the mounting doesn’t persist. To get around that, I burned the ISO to disk.

Step 6: Install SharePoint 2013
The actual product installer doesn't really ask any questions—that’s saved for the two configuration wizards.

SharePoint 2013 install from geeklit.com by Stephen Cawood

Note: The first time I ran the installer, it failed. Eventually, I was able to get the install to complete. I manually restarted the VM, manually ran Windows Update and, I also ran the .NET Framework Repair Tool (thanks to Chris O’Brien for that tip).

Step 7: Run the SharePoint 2013 Configuration Wizard

SharePoint 2013 install from geeklit.com by Stephen Cawood

There are lots of questions in the config wizard. I’m not going to go through them here. There are plenty of posts on that topic.

SharePoint 2013 install from geeklit.com by Stephen Cawood

Step 8: Run the Farm Configuration wizard.

After running the SharePoint Configuration Wizard, you’ll be asked to run the farm config. This step includes creating a root site collection and choosing which services will run on the server.

SharePoint 2013 install from geeklit.com by Stephen Cawood

That’s it, you’re done! Now you have a SharePoint 2013 image on Windows 8… so handy.

SharePoint 2013 install from geeklit.com by Stephen Cawood

Note: If you’re still installing the SharePoint 2013 Preview build (I won’t know why you would), don’t forget that the “Working on it…” screen for configuring the SharePoint services will not close—it just keeps going forever.

Tuesday, October 23, 2012

SharePoint Web Services are Deprecated

After telling everyone who would listen (for years) that they should switch to the SharePoint Client-side Object Model (CSOM), there is finally a clear statement for us to use as evidence.

Buried deep in the article, Choose the right API set in SharePoint 2013, you’ll find this text:

“Two API sets are still supported in the SharePoint 2013 Preview framework for backward compatibility, but we recommend that you not use them for new projects: the ASP.NET (asmx) web services, and direct Remote Procedure Calls (RPC) calls to the owssvr.dll file.”

RPC calls are also deprecated, but few were using those, it’s really the native web services that need to be retired. They served a purpose, but they were never complete and they are now based on what could be called ‘old’ technology.

Sure, the CSOM API isn’t complete either, but hopefully the missing power will come eventually. The features that were added in SharePoint 2013 seem to have all gotten appropriate attention in the CSOM API.

Tuesday, October 16, 2012

How do I Become a Microsoft MVP?

Quite regularly, I read this question in a forum, hear it asked at a conference, or someone asks me personally, “How does someone become an MVP?” There is no simple answer, but here’s my stab at it.

Microsoft MVP Banner geeklit.com

First of all, if there is only one thing to remember about the MVP award, it’s this: the Microsoft Most Valuable Professional (MVP) award isn’t a certification.

There are no set criteria or steps that someone can take to become an MVP. As the name implies, it’s an award. However, there are certainly things that you can do to work towards getting a nomination. As I mention below, most people would tell you not to aim for MVP status. It requires significant time and effort, so if you’re not having fun doing community-focused work, it’s probably not worth it.

I think a quick explanation is in order. The MVP award is given out based on specialties. Mine is Microsoft SharePoint Server, so that’s what I’ll be referring to throughout this post, but categories do not have to be products. There are MVPs for development languages (e.g., C#) and there are MVPs for platforms (e.g., ASP.NET or XNA). There are currently about 240 SharePoint MVPs around the world.

“This award is given to exceptional technical community leaders who actively share their high quality, real world expertise with others. We appreciate your outstanding contributions in SharePoint Services technical communities during the past year.”
-
Microsoft

In practical terms, this means helping with community-focused resources such as contributing to the SharePoint newsgroups, speaking at conferences, writing about SharePoint and contributing code to CodePlex (an open source site used by the SharePoint community).

The benefits of being an MVP include a TechNet subscription, a subscription to the Microsoft Developer Network (MSDN), access to MVP/product group forums/distribution lists/Yammer networks, software benefits such as access to Office 365 and TechSmith Camtasia Studio, early access to new product builds, and an invitation to the annual MVP Summit. However, the main benefit is being part of the MVP community. I greatly enjoy spending time with other MVPs. If you have a technical question, they’re the best people to ask, and we share common experiences so I often either commiserate or celebrate with them.

The award is given based on nominations--a panel ultimately decides who receives it. There are no published criteria and the members of the panel aren’t disclosed. Also, one key factor is that Microsoft likes to have representation around the world. If there are already a bunch of MVPs in your area—and for your specialty/product—that could make it harder to get the award. However, there is a surprising number of SharePoint MVPs in Toronto, Canada, so this is isn’t a hard rule.

Microsoft MVP Banner geeklit.com

These are the main things that historically have helped with MVP status:

· Speaking at events, conferences and user groups
· Writing original content (e.g., blog posts, articles and books). You must have a blog.
· Developing community apps (usually posted to CodePlex)
· Taking Microsoft certification courses
· Contributing/organizing/starting user groups
· Contributing to the MSDN forums (mainly answering questions).
· Participate in social media and social events (e.g., Twitter, Yammer and social events such as SharePint). You need to get your name out there as a subject matter expert (SME), so the people on the panel have heard your name and seen your work.

I tell people that trying to get the award should not be their focus; there should be value to the things they’re doing independent of trying to become an MVP. However, if I were to set out to get the award today, this is what I would do:

1. Pick a well-defined audience (end-user, dev or admin) and a well-defined sub-topic within SharePoint (or your area of expertise) to focus your efforts. SharePoint is simply too big a topic to do everything.

2. Talk to MVPs and MVP leads (especially your local lead) to get their insight into what would help you get nominated.

3. Meet in person with the current MVP lead for your region. This can help you figure out what’s most important to Microsoft now.

4. Submit presentation proposals to the biggest conferences you can afford to attend, the Microsoft SharePoint Conference plus some user groups and smaller private shows. For the bigger shows, it’s best to submit more than one session since they get way more proposals than they can accept.

5. Make sure you’re regularly posting original content about your expertise. Blog posts, articles, etc.

6. Take some certification courses. Becoming a Certified Master or Certified Architect is a good (but expensive) way to get ‘street cred.’

7. Answer some questions in the MSDN forums, but keep in mind there’s a new certification (Microsoft Community Contributor Award) that’s meant specially for people who do this a lot. I have a notification that goes off every weekday to remind me to go to the SharePoint forums and answer questions.

8. Regularly participate in social media to ensure that the current MVPs in my area and the Microsoft reps know who I am.

Note that somebody has to nominate you. It’s unlikely that you’ll just get an email one day saying you’ve won an MVP award. You need to be talking to people in the community and from Microsoft so that you have a relationship with them and you have some visibility for the good work you’re doing, Note that I’m not suggesting that it’s just a popularity contest; networking and visibility are only helpful if you’re contributing something that has value.

It’s not easy to win the MVP award, so once again, it’s not a good idea to aim to get one—do the things you love to do and if you win the award, it’s a bonus. I feel fortunate to have received three MVP awards and I certainly make good use of the benefits. But I don’t expect that it will be just handed to me… when it comes to renewal… Microsoft will only consider what you’ve done in the last 12 months, so winning the award once doesn’t mean you’ve reached the end of the journey.

Hope that helps keep it clear as mud.

Monday, October 15, 2012

How to Do Everything SharePoint 2013

My latest book project is an end-user SharePoint 2013 book called How to Do Everything: Microsoft SharePoint 2013. this is, of course, a new edition of my last book, How to Do Everything: Microsoft SharePoint 2010. As with the 2010 version, my good friend, Arpan Shah, Microsoft Senior Director of Office 365, has contributed a section on the history of SharePoint and also written the foreword.

What I set out to do in the first edition was focus on the most important cases for the day-to-day user. I trust readers are conscious of the fact that the “How to Do Everything” series name doesn’t mean that all of SharePoint can be summed up in one book. This book is squarely focused at the end-user.

How to do Everything HTDE SharePoint 2013 Cover by Stephen Cawood

For the second edition, I don’t want to stray too far from my original goal. However, I’ve listened to all the feedback from the first book. Readers wanted an end-user book, but some wanted it to take them a bit further, so that’s what I’m going to do. I’m adding content about SharePoint administration and other topics that aren’t necessarily required for every user, but will be interesting to those who want a bit more.

I’ve worked with McGraw-Hill Osborne Media on other projects and they’re a great publisher to work with—professional and helpful.

Here’s some text from the 2010 book description:

"Written by a former member of the SharePoint development team, this is a step-by-step guide to mastering the latest release of this integrated suite of server capabilities.In How to Do Everything: Microsoft SharePoint 2010, Stephen Cawood—one of the people who helped build SharePoint—offers advice from his many years of working with SharePoint customers, cutting to the core and focusing on key features to get you up to speed quickly. You’ll get easy-to-follow tutorials on blogs, wikis, My Sites, Web parts, taxonomy, document management, workflow, publishing sites, team sites, and much more. Take full advantage of the content management, enterprise search, collaboration, and information-sharing capabilities of SharePoint 2010 with help from this practical guide."

Friday, August 03, 2012

SharePoint 2013: Platform or Application?

I would not have expected the debate about SharePoint as an application vs. a platform to begin again, but that seems to be the case. A number of SharePoint consultants and other SharePoint experts are expressing concern about a few features that have been changed or removed from SharePoint with the SharePoint 2013 Preview release. The most obvious being the SharePoint Designer Design View--which has prompted a hot discussion on the MSDN SharePoint forums. These individual items may be annoying some people, but there’s more going on here. This isn’t just a few items being removed, it’s part of a fundamental shift in the SharePoint messaging. SharePoint has been promoted heavily as a customizable platform, but that message is changing. I posted this reply in the forums:

I believe this is part of a larger discussion. If you read the messaging coming from the SharePoint team, this change is consistent with a move away from SharePoint being such an open and customizable platform. That's not my opinion; here's the supporting quote:

"Use SharePoint as an out-of-box application whenever possible - We
designed the new SharePoint UI to be clean, simple and fast and work great
out-of-box. We encourage you not to modify it which could add complexity,
performance and upgradeability and to focus your energy on working with users
and groups to understand how to use SharePoint to improve productivity and
collaboration and identifying and promoting best practices in your organization." -
Jeff Teper, VP SharePoint - The New SharePoint (SharePoint team blog post)

This forum response, from a user named Intrawebs, gives you an idea of the reaction: “I am a developer, but, when it comes to SP I try and do as much as possible in SP Designer vs. Visual Studio.  It federates responsibility and enables non devs to contribute more easily.  This will be a deal breaker for us, we use SP on our public and intranet sites.  Poor decision from MS…”

When SharePoint first came out, it's primary value was as an application--a quick way to create an Intranet. MCMS at the same time was designed as a platform--build your own site, but build any type of site. The market responded that they wanted both in one product and SharePoint made huge strides as a platform. Now it seems that the SharePoint team has decided that the pendulum has swung too far.

Is this a good change for SharePoint customers? Is it a good change for SharePoint customers? These are hard questions to answer. What is clear is that less SharePoint customization is probably not good for SharePoint consultants. There seems no way around the simple formula that less customization = less work.

Some ISVs could benefit from this change. For example, migration vendors have to work extremely hard to support customizations, so there may be less work in that area. However, one of the reasons customers use third-party migration products (such as my former company, Metalogix) is to deal with customizations, so that’s not clear. Also, this is a preview release.

While the new SharePoint App model does add a new dimension to SharePoint development, I’m sure that most SharePoint devs would say that they expected this to be an additional choice rather than the only choice.

Monday, July 16, 2012

SharePoint 2013 Deferred Site Collection Upgrade

Today, the next generation of Microsoft Office, Microsoft Office 365 Enterprise and SharePoint 2013 were all made available via technical preview. As a SharePoint MVP, I’ve been under the NDA curtain, so it’s great to finally have a bunch of news in out in the wild so we can all talk about the next release.

The differences between SharePoint 2010 and SharePoint 2013 are outlined in this TechNet post: Changes from SharePoint 2010 to SharePoint 2013 Preview. I wanted to clarify something that I believe could be confusing to SharePoint administrators as they first hear about the new “deferred site collection upgrade option.”

Here is the section about SharePoint 2013 upgrade:

Visual upgrade

Description: The visual upgrade feature in SharePoint Server 2010 is not available in SharePoint 2013 Preview. For the upgrade from Office SharePoint Server 2007 to SharePoint Server 2010, you could choose to use the visual upgrade feature to give site collection owners and site owners the opportunity to preserve the previous user interface temporarily while still upgrading the infrastructure and databases, site collections, and features to the latest version. This allowed site collection owners and site owners to update customizations to work in the new user interface. Once the database and site collection upgrade was complete, the user had the option to upgrade the user interface on a more granular level of the website (SPWeb object).

Reason for change: The visual upgrade feature is replaced with deferred site collection upgrade. The site collection upgrade process is not reversible. The deferred site collection upgrade is a more comprehensive upgrade process than visual upgrade.

Visual upgrade preserved only the old master pages, CSS files, and HTML files. Deferred site collection upgrade preserves much more, including SPFeature functionality. To achieve the deferred site collection upgrade, major changes in the architecture were required, including the removal of visual upgrade.

With deferred site collection upgrade, you can continue to use the UI from the previous version (SharePoint Server 2010) more seamlessly than is possible with visual upgrade. The master page, CSS, JScript, and SPFeatures will remain in SharePoint Server 2010 mode. One key difference is that the granularity of upgrading the user interface is per site collection (SPSite) instead of site (SPWeb). Users can still preview their site in the new SharePoint 2013 Preview user interface before committing. However, this is accomplished by creating and upgrading a temporary copy of their site collection instead of a preview in the existing instance of the site collection. The reason for previewing a copy of the site collection is because of the complexity of what occurs during site collection upgrade. Once a site collection is upgraded, it cannot be rolled back. Therefore, performing a preview would not be possible except in a copy of the site collection.

Migration path: Site collection administrators who are using visual upgrade to continue to use SharePoint Server 2007 must move to the SharePoint Server 2010 user interface before upgrading to SharePoint 2013 Preview. After the content database is upgraded, users can use deferred site collection upgrade to continue to use the SharePoint Server 2010 experience for their site collections. Site collection administrators can be notified by their farm administrator when a site collection is ready for upgrade and the site collection administrators can then choose to either perform the upgrade of their site collection or optionally first preview the new functionality in a temporary copy of their site collection.

Any SharePoint user interface might have dependencies on visual upgrade. The main dependency was getting the user interface version and then outputting the correct user interface (new or legacy). The visual upgrade API feature is updated so that the user interface version is remapped to the new site collection compatibility level property. This returns the same information about which version the site uses as before. Therefore, dependent code does not need to change.

--- end snippet ---

There is no doubt that the new deferred site collection upgrade is a great improvement; rather than just the look and feel of the site staying in the previous version (as you could do in SharePoint 2010), the actual schema can be left in the old version of SharePoint and virtually everything (read: customizations) will continue to function as before. This clearly means that less work is done and the upgrade process will be faster; albeit with the requirement to finish the site collection upgrade at some later point.

For anyone looking at this new feature and thinking about their upgrade or migration to SharePoint 2013, it’s important to differentiate deferred upgrade from a gradual or granular upgrade. I’m sure some people will refer to deferred as gradual, and I can see how that could be just a semantic argument. However, it’s clear that there is a difference between a granular migration and a deferred migration. Although the deferred site collection upgrade allows a content database to be upgraded without the underlying schema being upgraded, it is still scoped at the database level. If you are looking to migrate or upgrade part of your SharePoint 2010 implementation to SharePoint 2013, the new deferred upgrade is not meant to enable that scenario.

Monday, March 05, 2012

BPOS Upgraded to Office 365–Why Does it Look the Same?

Obviously, there’s a lot more to Office 365 than SharePoint Online. The Microsoft Online Services offering also includes Exchange Online for email, Lync Online for communication, the Office Web Apps, and some plans even include a copy of Office Professional Plus. But I’ll let others blog about the various pieces—this post is about SharePoint Online.

If you have a Business Productivity Online Suite (BPOS) account, you’ll know that BPOS comes with Microsoft Office SharePoint Server 2007 (MOSS) and Office 365 comes with SharePoint Server 2010. Since I work for a Microsoft Partner, Metalogix Software, my GovernanceHx project is part of the BizSpark program, and I’m a Microsoft MVP, I have a few different SharePoint Online accounts—including both BPOS and Office 365. One of these accounts was recently upgraded from BPOS to Office 365, so I’ve experienced the SharePoint upgrade firsthand.

BPOS Site Upgraded Office 365 geeklit.com stephen cawood
- A BPOS SharePoint site upgraded to Office 365

The funny thing about the SharePoint Online portion of the upgrade is that it’s really hard to tell that anything has happened. Sure, you get an email that advises you that your site is ready for upgrade, but when you actually visit your SharePoint Online site, it looks exactly the same. Well, we all know that looks can be deceiving.

If, however, you enter using the Team Site link from the Office 365 customer portal, you’ll be taken to a spanky new SharePoint Server 2010 site. This is actually a new page; the BPOS content retains the same URL after the upgrade and a link will be added to your new home page.

Office365SharePointOnline_Edit
- The SharePoint “Team Site” home page after BPOS (MOSS 2007) is upgraded to Office 365 (SharePoint 2010)

So why does the BPOS SharePoint Online content still look like MOSS? It’s actually a feature of SharePoint Server 2010. Specifically, the “Visual Upgrade” feature. Visual Upgrade allows MOSS sites to be upgraded to 2010 without changing the look and feel. This is meant to ease the transition to the new version of SharePoint. A site admin can go to the site settings and choose to upgrade to the SharePoint 2010 look and feel. When a BPOS site is upgraded to Office 365, the SharePoint Online content is put in a site collection under the Office 365 account.

To see the site collections, go to the Microsoft Online Services (Office 365) Administration portal and scroll down to SharePoint Online. Once there, click the “Manage” link. This opens the SharePoint Online Administration Center. Next, click on “Site Collections” to see the Office 365 site collections that were provisioned for you during the upgrade.

Office 365 Admin geeklit.com stephen cawood
- The Office 365 administration interface

Here you’ll see that there’s a new site collection under your Office 365 domain name (yes, the Office 365 URLs are much nicer than the old BPOS mouthful), and that there’s one for your MySites (a feature that wasn’t available in BPOS), as well as one for your old BPOS content. If you don’t want to use the new SharePoint 2010 interface, that’s your choice, but personally, I’d go for it.

Office 365 SharePoint Online geeklit.com stephen cawood
- The new SharePoint Online Administration Center interface

I only wanted one site collection, so I used Metalogix Migration Manager for SharePoint, to migrate the old BPOS content to the main Office 365 site collection.

Having my site (and my MySite) on SharePoint 2010 means I can take advantage of great features that are only available in SharePoint 2010. For example, Enterprise Metadata Management (a.k.a. SharePoint taxonomy), the new SharePoint UI with the fluent ribbon and a tighter integration with Microsoft Office.