Bill Baer (ˈbɛər)
Bill Baer (ˈbɛər)
Bill Baer is a Senior Product Manager and Microsoft Certified Master for Microsoft Search, Assistant, and Intelligence at Microsoft in Redmond, Washington.
Understanding PRESCAN.EXE Errors (UPDATED - May 2007)
I’ve updated my post Understanding PRESCAN.EXE Errors to include new errors and solutions. Read more here: http://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx. Excerpt: ““An outbound zone URL is configured for something other than the default zone on virtual server http://fabrikam/, and no default zone outbound URL is defined. This is not supported, and must be corrected before upgrading.””
Code Snippet - How to Locate Host Header-based Site Collections in Windows SharePoint Services 3.0
One of the great features in Windows SharePoint Services 3.0 is the ability to co-host both path-based and host header-based site collections within the same server farm and content databases. Now that you’ve introduced host header-based site collections to your server farm, how do you quickly identify those site collections within a server farm or content database that also hosts your path-based site collections? In this scenario the object model is extremely useful in reporting on those site collections, the Web application, and content database where they reside.
Jingmei Li has put together a great post...
Jingmei Li has put together a great post detailing partner solutions supporting SharePoint Portal Server 2003 to Microsoft Office SharePoint Server 2007 migrations; these solutions are useful in situations where any of the three supported approaches do not fit within the scope of a business' plans for migration and upgrade. Read the entire post here http://blogs.msdn.com/jingmeili/archive/2007/03/13/evaluate-partner-solutions-that-support-migration-from-sps-2003-to-moss-2007.aspx.
Upgrading Windows SharePoint Services 2.0 Scalable Hosting Mode Server Farms
In Windows SharePoint Services 3.0 host header-based Site Collections can coexist with path-based site collections within a Web Application or optionally reside on multiple Web Applications. Gradual, in-place, and database migration upgrade approaches can be applied to Windows SharePoint Services 2.0 server farms in scalable hosting mode. This differs from Windows SharePoint Services 2.0 where a server farm was configured to run in scalable hosting mode preventing the introduction of path-based Site Collections to the server farm.
Co-hosting Collaboration and Personal Site Collections within an Individual Web Application
One of the most common questions I receive is how to co-host traditional “team” and personal Site Collections (My Sites) within an individual Web Application in Microsoft Office SharePoint Server 2007. While possible, there are several important steps that you should be aware of. The public profile page is a document specific to the SPSMSITEHOST site template (My Site Host); unless a My Site Host is defined in the server farm, public profile pages will not be available to users.
Upgrading a Windows SharePoint Services 2.0 farm to Microsoft Office SharePoint Server 2007, supported?
I’ve recently been asked whether Windows SharePoint Services 2.0 can be upgraded to Microsoft Office SharePoint Server 2007; while this is possible, there are several important constraints that should be taken into consideration. Foremost, you should not upgrade Windows SharePoint Services 2.0 to Microsoft Office SharePoint Server 2007 bypassing the Windows SharePoint Services 3.0 upgrade - by attempting to upgrading Windows SharePoint Services 2.0 to Microsoft Office SharePoint Server 2007 you are combining two upgrade methodologies; version to version (WSS 2.
PRESCAN Support and Resources for Windows SharePoint Services and Office SharePoint Server
MSDN Windows SharePoint Services Run the pre-upgrade scan tool (Windows SharePoint Services) http://technet2.microsoft.com/windowsserver/WSS/en/library/035a3024-bd27-4d63-9499-0f15ac00c6e61033.mspx Issues that are reported by the pre-upgrade scan tool http://technet2.microsoft.com/Office/en-us/library/035a3024-bd27-4d63-9499-0f15ac00c6e61033.mspx#section1 Install and run the pre-upgrade scan tool http://technet2.microsoft.com/Office/en-us/library/035a3024-bd27-4d63-9499-0f15ac00c6e61033.mspx#section2 Error message when you try to upgrade Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0: “Upgrade has encountered one or more lists that were not updated by Prescan.exe and must exit” http://support.microsoft.com/kb/923904 Office SharePoint Server Run the pre-upgrade scan tool (Office SharePoint Server)
Understanding PRESCAN.EXE Errors (UPDATED - January 2007)
I’ve made several updates and revisions to my previous post “Understanding PRESCAN.EXE Errors”, I hope this information will be useful in diagnosing and remediating errors generated by PRESCAN.EXE.
Understanding PRESCAN.EXE Errors
*UPDATED 5/22/2007 I put together this post as a follow-up to my initial PRESCAN topic “Understanding PRESCAN.EXE in MOSS 2007"; hopefully, this will provide insight into the most common PRESCAN errors administrators may encounter and remediation steps where available. These solutions may not fit every environment due to the natural differences in topologies, hosting models, versioning, and infrastructure. Error: There is no Web named “//”. The Content Database contains one or more orphaned Webs.
Windows SharePoint Services 3.0 Upgrade Path Defined
A recent change has been communicated for all current Windows SharePoint Services 3.0 B2 (Beta 2) customers. The change will require customers who wish to upgrade their B2 environments to first apply B2 Technical Refresh prior to upgrading to RTM, Windows SharePoint Services will not support B2 to RTM direct upgrades. Previously announced upgrade paths will remain unchanged at this time: B2 Technical Refresh remains planned as a release patch, upgrading to RTM will require the modification of a Registry key, uninstalling B2 Technical Refresh, and then installing RTM.