Over the past several weeks myself and Rick Taylor, you may know him from various conferences, MCTs, or as a contributing author to the Microsoft Office SharePoint Server 2007 Administrators Companion, have been engaging the Edge crew to establish a new series - dubbed the R&B Show. Our focus will be an entertaining look into the daily lives of a MSIT technologist and we’ll be covering topics specific to Microsoft SharePoint Products and Technologies such as FBA, BDC, Search, Shared Services design, architecture and engineering, etc.
Master merge compiles all index data comprised of both in-memory and disk-based structures into one disk-based structure to prevent the degradation of the search service. SPS 2001 allowed administrators to manipulate the master merge schedule through HKEY_LOCAL_MACHINESoftwareMicrosoftSearch1.0CatalogNamesSharePointPortalServerworkspace_nameIndexer:ci:MidNightMasterMergeTimeDelta, but only to a limited degree of the specification of minutes past 12:00 A.M. that master merge should occur. Microsoft Office SharePoint Server 2007 does not provide an out of the box mechanism for manipulating the scheduling of the master merge process; however, options are available to script a scheduled master merge operation.
This will be the first of a series focusing on those areas of storage that are commonly overlooked when planning storage for Microsoft SharePoint Products and Technologies. In this post we’ll look at the native Recycle Bin in Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0 to understand its fundamental aspects and impacts on storage.
The Recycle Bin enables end-users to easily recover content deleted within a site collection and is configured in two separate and unique stages referred to as the 1st and 2nd stage each with its own configuration properties.
Moving site collections between domains is not a common operation, but occurs frequently enough to provide some prescriptive guidance. User Accounts
SharePoint maintains the security identifiers of user accounts as opposed to just usernames, as a result, when restoring a site collection to a farm in a domain other than that where the original source site collection was located, those usernames are no longer recognized regardless as to whether or not those usernames were recreated in the target domain.
Internet Information Services 7.0 Application Pool Modes introduces changes in how application pools are managed and process requests that involve managed resources. In Internet Information Services 6.0 worker process isolation mode and in Internet Information Services 5.0, isolation modes are set at the server level. The result is that both isolation modes cannot be run simultaneously. In Internet Information Services 7.0 modes are set at the application pool level allowing applications to be run simultaneously on the same server in application pools with differing process modes (Integrated and ISAPI (Classic).
Slipstream is a common term used at Microsoft to define the merging of patches or updates into the original installation sources of a program.
What are the benefits of slipstreaming….
Creating a slipstream image reduces the operational overhead required to introduce a specific build of software to include Windows SharePoint Services 3.0 and/or Microsoft Office SharePoint Server 2007 into an environment. For example, if an organization has standardized on a specific set of updates and/or patches that will be applied in a given configuration, these updates and/or patches can be included in the original installation sources and subsequently installed with the source application.
On October 29, 2007 we announced that Windows SharePoint Services 3.0 bits will not be included on the Windows Server 2008 media; however, will remain available as a separate download, as a result changing the installation routine. For those who used evaluation and release candidate builds of Windows Server 2008, Windows SharePoint Services 3.0 was included as a server role, adding the role subsequently configured supporting roles and role services - as a clean installation, this configuration must be performed by the server administrator and includes adding the Web Server (IIS)) role and role services.