View Complete Post
The challenge in SharePoint development has always been the balance between creating and deploying solutions that you can trust not to damage or impair a SharePoint farm. A new feature in SharePoint 2010, called Sandboxed Solutions, enables farm administrators to feel comfortable that the SharePoint farm is safe, gives site collection administrators the authority to manage applications in their site collection, and provides developers with the flexibility to create solutions they know will be deployed in a safe and rapid manner.
MSDN Magazine November 2009
I have successfully followed the white paper for upgrading SharePoint Services 3.0 to SharePoint Foundation 2010. Other than an authentication link problem all went smoothly.
I do have two small problems. The Small Business Server console reports that SharePoint is not functioning (it is functioning as I can connect to the site), this is more a nussance as my daily reports are inaccurate and I hope if this is normal there is
or will be a hotfix to repair the reporting. This also comes to the second more serious problem.
In upgrading the process moved the database from it's own drive back to the system drive. I should have payed more attention to the directories in the upgrade process. Live and learn. Since the reporting is wrong in the console the move database wizard
also does not work. Knowing that SBS gets cranky when things aren't done with a wizard or in a super specific order, is there a proper way to move the database? I am beging to get the long list of warnings as the drive fills up.
Any help would be appreciated. Thank you.