I’m Done with SharePoint

• When I tried to do a multiple-file upload, this option was disabled by default. After considerable research (via Google) I found that I had to install Office 2010 on my server to be able to get the ActiveX DLL installed that supported this feature. Why wasn’t this included with SharePoint’s (copious) install? And why should I have to load up my server with client software?
• I started dragging the files over for uploading and discovered that it would only take 100 at a time. Why? Why not point to a root folder and tell it to import the lot. If it has to take smaller sets, then it should do so. It should also produce an error log that says why some files were uploaded and some not.
• It turns out that not all of the files were uploaded. For some reason, there is a 100MB cap on the files. Excuse me? I have lots of graphics-laden Word and PowerPoint docs that are larger than 100MB. I also have demo AVIs larger than that. While this is (theoretically) configurable, doing so takes a PhD in SharePoint to figure out. IMHO, when it finds that you’re uploading a large file, it should give you a link to the instructions to increase the capacity.
• When I had issues with SharePoint along the line I tried to push the “click here for more help” link. Most (by far) led me to a generic page—not to specific help on the issue.
• When I discovered that I had loaded a directory in the wrong place, I found no way to simply relocate the folder to another tree. This should be a drag-and-drop feature.
• Back in my Word, I used to be able to drop a link to the SharePoint path where I was currently working. With SP2010 this no longer works.
• Still fighting terrible performance (it took 6-10 seconds to reference anything on SP), I decided to update the OS on the server to WS 2008 R2 from 2008. This went very smoothly except for one little thing—SharePoint did not get upgraded and would not launch. There were no indications by the WS upsizing wizard that warned of issues. SQL Server was left untouched but it seems the IIS linkages were all pooched. So on advice from a trusted SP expert I uninstalled and tried to reinstall. At this point I discovered that the SP uninstall leaves giant shards of broken glass lying around that confused the reinstall. I had to manually uninstall IIS, the SQL Server SP database and far to many other bits left over post uninstall.

All in all, not a pleasant experience and a total waste of time. I did a final uninstall and scrubbed off the last remnants of SharePointless from my system. Never again. I only wished I had installed it in a hyper-v which would have made it a lot easier to maintain but since the perf was awful I expect that would have made matters worse.