I received an inquiry this week asking how to migrate an existing Site Collection as a subsite of a new parent Site Collection without having the availability of SMIGRATE in Microsoft Office SharePoint Server 2007/Windows SharePoint Services 3.0. The answer are new STSADM parameters, import and export, which has been made available in STSADM. The import/export feature is based on the new Content Migration APIs; Recycle Bin state and alerts are not included in STSADM -o export - the requirement that the new Site Collection or subsite exists, remains as with previous versions of STSADM when using the restore parameters.
Bill Baer /bɛːr/
Posts
Of the many new features available in both Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0; the questions I most commonly field surround workflow; deployment, implementing, best practices, etc… The attached whitepaper serves as an excellent resource to answer many of these questions.
Understanding Workflow in Windows SharePoint Services and the 2007 Microsoft Office System
Lawrence Liu recently posted his Live Search macro enabling a consolidated search against the SharePoint Community; to add to that capacity I’ve put together a small bookmarklet that will enable you to run this search from your browser without having to navigate away from your current page.
**Download
**https://wbaer.officeisp.net/Shared%20Documents/SharePoint_Community_Search_Bookmarklet.zip
Historically alternate access settings provided a mechanism to identify the different ways in which users access portal sites; in MSIT we’ve taken that practice one step further and leverage alternate access mappings (AAM) as a means to identify problem web front-ends in a NLB cluster. As an example an NLB (network load balancing) cluster may be bound to a VIP (virtual IP address) with a mapping of foo, where the hosts are foo1 and foo2, by leveraging alternate access mappings we can DIP test foo1 and foo2 both independently and through the Microsoft Operations Manager (MOM) Web Sites and Services Management Pack.
Recycle Bin for SharePoint Products and Technologies 2003 (WSS/SPS 2003) 1.2 (Build 29) Released!
952Recycle Bin 1.2 (Build 29) has been released; this release addresses several issues reported in build 26, released in July. Currently this build is offered as independent libraries and will soon have an accompanying Windows Insaller Package. To install this build, stop the World Wide Web Publishing Service (NET STOP W3SVC), replace ReycleBinISAPI.dll and RecycleBinISAPIFilter.dll with build 29 and start the World Wide Web Publishing Service (NET START W3SVC). Download Recycle Bin 1.
Internet Explorer 7 has been released, download it today and experience a new interface that maximizes real estate putting more content in the browser and grouping functions to ease viewing. Other new features include tabbed browsing, enhanced print finishing, RSS feed management, the ability to designate search providers, and enhanced security and phising filters. Get it today.
Recycle Bin for SharePoint Products and Technologies 2003 (WSS/SPS 2003) 1.2 (Build 26) Released!
88I’ve published Recycle Bin 1.2 (Build 26) to SharePoint Tools GotDotNet Workspace, this build addresses two long-standing bugs:
Fixes Explorer View bug:
Unable to delete An error occurred accessing your FrontPage web files. Please contact the server administrator.
Fixes Empty Library archiving:
Document and Picture Libraries that do not contain content will be archived in effort to mirror the directory structure of a Document/Picture Library and its’ subfolders if they exist.
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.
Prior to upgrading to Microsoft Office SharePoint Server 2007/Windows SharePoint Services 3.0 one of the prerequisites some of you may have already noticed is running PRESCAN.EXE from the installation directory. This post will hopefully provide some insight into PRESCAN.EXE as well as best practices on when it should be run.
PRESCAN.EXE has two primary purposes:
It parses and saves List definitions with the associated Lists. SharePoint Portal Server 2003 Service Pack 2 already incorporates this feature whenever a list is modified; however, this process should be completed for all Lists, so prescan calls the SharePoint Portal Server 2003 Service Pack 2 method to persist that data.
Does SharePoint Portal Server support document encryption? SharePoint Portal Server 2003/Microsoft Office SharePoint Server 2007 can be configured to leverage Rights Managenent Service (RMS) which allows for the encryption of documents through RMS policy each time a document is requested from a Document Library, the RMS policy will be applied to documents whether they are requested through the Office client, WebDav or FrontPage - RPC.
- While SQL Server 2005 supports certificate-based encryption within the store, encryption will have to be manually implemented through stored procedures using the new SQL Server 2005 TSQL support and technologies for certificate management and encryption.