Setting maximum upload size in SharePoint 2010

By default SharePoint has a limit of 50MB per uploaded file. This value can be changed via the SharePoint Central Administration console.

Select Start | All Programs | Microsoft SharePoint 2010 Products | SharePoint 2010 Central Administration. Right mouse click on the program and select Run as Administrator from the menu that appears.

Accept the User Account Control dialog that appears by pressing the Yes button.

When the SharePoint Central Administration is display select Manage Web Applications from under the Application Management section in the top left.

Select the Web Application you wish to change by clicking on it once so it is highlighted. From the Ribbon menu select the pull down arrow below the General Settings button. From the menu that appears select the General Settings option.

Scroll down the window that is displayed until you locate the Maximum Upload Size section.

Adjust maximum file upload size to the desired amount. Scroll down to the bottom of the window and select OK to save the changes.

Exit the SharePoint Central Administration.

April release of CIAOPS SharePoint Guide

The April 2011 version of my SharePoint Operations Guide is now available for subscribers. In this month’s edition you’ll find out how to change the passphrase on a SharePoint farm which is really important if you are now using SBS 2011 Standard. Why? Because it is installed with a random passphrase and if you need to repair the installation of SharePoint Foundation 2010, and you don’t know the passphrase then you’ll have no option but to uninstall and reinstall SharePoint Foundation 2010. Yuk!

You’ll also find some information about Office365, especially in regards to SharePoint online.

I’m also please to welcome along a number of new subscribers who have received my Guide after signing up to my upcoming SharePoint bootcamp. When you sign up you’ll get a whole days hands on training PLUS a 12 month subscription to my Guide. Even better, if you sign up now the subscription won’t start till May, so you’ll get 13 months of the Guide.

Would you believe that next month marks 3 years of the Guide? Who’d thought, all those years ago that it would grow to what it has become today? Not me that’s for sure. So I take this opportunity to thank all my subscribers for their continued support.

SBS 2011 Companyweb upgrade gotcha

Hopefully people know that Companyweb content databases on SBS 2011 Standard are limited to 10GB in size total because SBS 2011 Standard uses SQL Express 2008 R2 as its storage mechanism. What you may not appreciate is that there is NOT a 1:1 conversion process during a migration.

This means that if you are migrating your content databases from SBS 2008 or SBS 2003 Companyweb they may end up being significantly bigger in SBS 2011 Standard. This is something I didn’t appreciate until recently. I was working on a migration of a 7GB Companyweb site to SBS 2011 when I uncovered the issue. I had successfully migrated the databases to WSS v3 from WSS v2 but during the migration to SharePoint Foundation 2010 on SBS 2011 Standard I received the following error part way through the conversion process:

Action 4.0.98.0 of Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence failed

After a bit of Googling it would seem that this error is due to lack of free space on the source drive. That wasn’t the issue for me but when I looked at the Companyweb content databases they had grown to almost 10GB in size. Given that 10GB is the limit of the version of SQL that SBS 2011 Standard uses I had no option but to use a full blown version of SQL, which doesn’t have the database size limitation, to at least complete the migration process.

After completing the migration process I found the databases had grown from their original 7GB to over 16GB. This raises an important gotcha when migrating old Companyweb content. Even though your existing databases are less than the 10GB limit imposed by SQL 2008 Express R2 on SBS 2011 Standard you need to allow for the databases to grow substantially during the migration process. This would indicate that you can’t comfortably convert databases that are greater than 4GB without the risk of the conversion process exceeding the database limitations.

I can’t say for certain if different types of content (i.e. files versus lists) makes any difference and whether coming from Companyweb on SBS 2003 via WSS v3 or Companyweb on SBS 2008 directly makes any difference during the conversion process. I do however suggest that if you are looking at conversions of Companyweb data around the 4GB mark or more you test to ensure that the conversion process will run within the 10GB limit that you are restricted to on SBS 2011 Standard.

Microsoft SharePoint 2010 Administration Cookbook

I have recently completed providing technical feedback for the book :

Microsoft SharePoint 2010 Administration Cookbook from Packt Publishing

Which covers:

The book starts off by demonstrating the various upgrading and post-upgrading tasks to be performed in SharePoint 2010. Next come recipes for managing SharePoint service-level applications and for monitoring the SharePoint environment. The book introduces one of the best new tools that should be in your arsenal, PowerShell, and the commands you will need to script your tasks with Powershell.

You can purchase the book from :

https://www.packtpub.com/microsoft-sharepoint-2010-administration-cookbook/book

and is a worthwhile addition to any IT Professional who administers SharePoint 2010.

Office365 Ignite training – Day 3

Today started off with information around Forefront Online Protection for Exchange. It now has the ability to not only view information but also make changes including things like white listing and creating email signatures. This will be quite handy and makes things more flexible than they currently are.

In Australia there will be an Office365 ‘P’ SKU which is aimed at small business and most likely designed to work with SBS 2011 Essentials. Personally, I can’t see myself ever recommending that option for customers.Why? It is simply too limiting. The ‘P’ SKU for example, doesn’t allow AD synchronization via Dirsync, it doesn’t have the provision for email archiving, it is limited to 50 licenses in total, doesn’t include Office Pro Plus, limits the amount of SharePoint storage and so on. To my mind the biggest appeal of Office365 for end users is going to be the version of Office Pro Plus they can download and install on their machines.

Another major point is the fact that Office 2003 will not be supported. This means Outlook 2003 won’t even be able to connect to Exchange Online under Office365. Given that Office 2003 is approaching almost 10 years I really think it is time people upgrade to Office 2010, but something to be aware of when doing migrations.

Interestingly, Office365 passwords can be 7 to 16 characters in length. We asked why there is an upper limit but no one seemed to know. This is sort of a bummer as many have been schooling customers to use pass phrases or more than 16 characters. Hopefully that will change before Office365 goes public.

As for the SharePoint stuff well there wasn’t too much I hadn’t already seen already having access to the beta. However, there were plenty of interesting questions thrown up by attendees which adds to the knowledge base.

So, was it worthwhile to take 3 days out of my business to learn about Office365? Definitely. Will I have to do more research and testing? Yes, but I happy to do this as I see Office365 being big and there are not many people out there with the skills, especially in the SBS world. Much of the information I learn about Office365 will find its way into my Cloud Guide (currently part of my SharePoint Guide). As Office365 grows so too will this information but focused on the SME market.

Finally, please remember that everything I mention here is still about a product that is yet to be released and is subject to change. However, I am really liking what I see and can’t wait to start tying it into SBS 2011 Essentials for starters.

Office365 Ignite training – Day 2

So the focus of today’s training was all around Microsoft hosted Exchange. It can get pretty complex for people who want to maintain a hybrid configuration. Unfortunately, it seems that SBS configurations are going to be difficult.

Why? Well, most SMB customers have some very large email boxes. This makes a migration completely to the cloud tricky over Australian broadband links. Don’t forget that the ‘A’ in ADSL stands for asynchronous – meaning the speed up to the Internet is generally MUCH slower than the speed down from the Internet. If the email is going to the cloud (i.e. during a migration) it is going UP at the slower speed. Given gigabyte sized mailboxes this could take quite a while.

The problem is that most of the tools don’t allow you to do a staged migration. You can’t generally nominate which mailboxes you wish to transfer, you can’t pause the migration (you can stop and rerun from where it left off I believe), you can’t elect to prioritize current messages and so on. Thus, if you want to move all the mailboxes totally to the cloud (a la SBS 2011 Essentials) you need to be very mindful of the mailboxes sizes and bandwidth limitations.

If you decide on a hybrid strategy (i.e. Exchange on site sync’ed to hosted Exchange) well you’re in for another whole world of pain. Firstly, this rules out SBS 2011 Essentials as there is no on site Exchange. Secondly, you need to install the Dirsync tool to synchronise your AD user details to the cloud. Problem is Dirsync is currently only a 32 bit app (64 bit is coming) AND isn’t supported on a domain controller. This rules out a network with a single SBS 2008 or SBS 2011 Standard server since they are both 64 bit and domain controllers. Thus, you’ll need another members server in your network (hello SBS 2011 Add on pack) on which to run this. Oh yes, Dirsync doesn’t sync passwords from onsite to the cloud. Shall I go on?

Another option with the hybrid strategy is to use federation services via ADFS v2. Although this does provide more benefits over simple Dirsync (i.e. allows AD security groups to replicate) it again requires client software on a non-member server. Oh yes, it also requires Exchange 2010 on site which rules out SBS 2008 and most existing SBS installs since SBS 2011 Standard (which includes Exchange 2010 onsite) has only just become available.

So it would seem that SBS 2011 Essentials is going to be the only domain controller on which cloud syncing tools will be supported on. However, don’t forget that SBS 2011 Essentials is limited to 25 users in total and doesn’t have an upgrade path to SBS 2011 Standard (which would need another member server anyway if was to sync to the cloud). So you are going to have to think real hard about which Windows Server version to use for clients who want to go Office365. But hey, this is no different from in the past right? This is the reason you are the IT Professional, right? This IS the reason your business and skills are not going away with the cloud! Your clients will still need you to advise them. The question I have however is, do YOU have ‘cloud’ skills? Hmmm…?

Confused and frustrated? Me too. The cloud stuff ain’t going to be easy on SBS networks. It would seem that the path of least resistance and cost is going to be complete mailbox migration to the cloud. However, you’ll need to probably trim the existing mailbox sizes before migration and keep an eye on bandwidth issues. In this case also you aren’t going to need SBS 2011 Standard unless the customer has more than 25 users or a third party on site app.

There are, however, some nice features. Depending on what online license you get, you are entitled to ‘unlimited’ email archiving. There are plenty of powershell commands available to allow you to script and automate processes. Also there is far more granular control over mailboxes and ability to implement retention and archiving policies (depending if your license allows that). You’ll also get Microsoft Forefront security protection on your email which has an improved web interface allowing you to things like white list domains, release trapped emails, troubleshoot issues, and more although we didn’t see that today.

There is still lots of stuff I need to digest, research and check here, especially in light of SBS, which I will do, however I’m now looking forward to the SharePoint stuff tomorrow. Another update tomorrow.

Office365 Ignite training – Day 1

I’ve just completed the first of three full days of Office365 training.

So here’s a few titbits I learnt today during Office365 Ignite training:

1. All Office365 users will get read only access to SharePoint docs via Office Web Apps. If they want to edit then they need the appropriate SKU.

2. Office365 is ‘highly configurable not customizable’. This means there are limits to what can be done on the admin side.

3. If you purchase a license that includes Office Pro Plus on the desktop you can install that on 5 devices. Very generous. Beware, though this is a special SKU more like retail than volume licensing. There are also NO downgrade rights with this version of Office.

4. Dirsync runs every 3 hours by default but can be manually run if needed, however it is a one way sync from local AD to cloud and the application MUST NOT run on a domain controller. It is also still a 32 bit app (64 bit is coming).

I’m looking forward to more technical in depth training tomorrow as today was billed as more of an ‘overview’. After the third day I feel I’ll be very much up to speed with Office365. Best of all we get our own full beta version for testing. I have an SBS 2011 Essentials RC machine here that is just crying out for Office365 integration.

More updates tomorrow. Follow me on Twitter (@directorcia) as I’ll be posting interesting info from the training day there.

Why Office365

I thought I do a series of posts on why Office365 is such a great option, especially for small businesses. So let’s start with my favourite – SharePoint.

In the current Microsoft Online offering (BPOS) SharePoint is effectively only Windows SharePoint Services v3.0 but in Office365 it is upgraded to SharePoint Server 2010 Enterprise. That is a HUGE step up in functionality for effectively the same price. SharePoint Server 2010 Enterprise costs big bucks and is normally only seen in use with very large corporations, but now with Office365 even a single man business can access these Enterprise tools.

One of the first big bonuses with SharePoint Server over SharePoint Services is the inclusion of My Sites. Think of it like Facebook for the Enterprise (functionality-wise I mean. Perhaps Linkedin is a better analogy for those that know Linkedin). You access it from the top right of the SharePoint screen under then menu for your name as shown above.

My Sites is actually a full blown SharePoint site dedicated individually to each user. In here people can track others, save documents, share documents, keep track of what they are working on in the main SharePoint Portal, and so much more. As you can see from the above screen shot you can keep track of your Colleagues, Interest and Newsfeed (very ‘Facebookie’).

As you can see from the above shot your My Site is a fully blown SharePoint site that you control. Each Office365 user has the full power of SharePoint Server 2010 at their disposal in their own personal area.

The above screen shot gives you and idea of the information you can aggregate in you My Site. Here we are looking at all my Tags and Notes across the portal sites I have access to. I can easily set information about myself that helps others in my business understand what skills I have. Likewise, I can easily find others with the right skills to help me with my job. I can select and track the work that other individuals in my team. In this way you can see exactly what other have been working on across SharePoint quickly and easily.

Here’s some example of what Newsfeed Activities I can elect to follow. As you can see it is pretty extensive and would be exceptionally beneficial to any team. It makes tracking what changes in SharePoint quick and easy which can be important as SharePoint grows.

So the first major benefit of SharePoint in Office365 is the My Sites functionality. I’ll be detailing more in coming post so you can understand why it is such a major upgrade and one that should seriously be considered by ALL organizations.