Bill Baer /bɛːr/

Microsoft Ignite will open the window to our vision, strategy, and future for SharePoint and provide a first look at most recent developments with SharePoint Server 2016. From the business value for organizations looking to modernize their workplace and infrastructure to the technical value it will deliver to IT Professionals and Developers as well as new hybrid investments for those customers looking to enrich their existing investments with cloud innovation. With Microsoft Ignite just around the corner, it’s time to look back and provide a little historical SharePoint information.

December 2009 Cumulative Updates are available for download for Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0. For additional download information and detailed descriptions of the December 2009 Cumulative Update visit the Updates Resource Center for SharePoint Products and Technologies at http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx. Additional Resources Update Center for Microsoft Office, Office Servers, and Related Products

The Microsoft SharePoint Administration Toolkit contains functionality to help administer and manage Microsoft Office SharePoint Server 2007 and Windows SharePoint Services version 3.0. http://www.microsoft.com/downloads/details.aspx?FamilyID=263cd480-f6eb-4fa3-9f2e-2d47618505f2&DisplayLang=en

The Microsoft SharePoint Products and Technologies Infrastructure Update has been officially released. The update includes both improvements in core functional scenarios such as Office SharePoint Server Search with the introduction of S2 in addition to management enhancements resolving core customer issues such as scalability and performance improvements to support search incremental crawl (WSS), patch and upgrade of WSS server farms where a large number of host header-based site collections are implemented, support for Kerberos authentication to access SSP Web services, and more…

I was just browsing Mike Fitzmaurice’s blog and I’m glad to see he continues to dissuade direct database access with Microsoft SharePoint Products and Technologies. All too often I’ve seen what was conceptually a good idea, result in performance, scalability, and manageability problems long term. While initially an otherwise simple SELECT statement, yes, even read, may be perceived as non-intrusive, problems later down the road may be compounded by what was offered as a “simple means” to getting a particular task accomplished.

The Microsoft SharePoint Administration Toolkit contains functionality to help administrateer (good catch A Mondale) and manage Office SharePoint Server 2007 and Windows SharePoint Services version 3.0. This toolkit contains two new functions - the ability to perform bulk operations on site collections and a Stsadm operation to update alert emails after a Web application has changed URLs. Download x86 | x64

The SharePoint Products and Technologies Protocol Documentation has been recently published to MSND which includes technical specifications for Microsoft proprietary protocols that are implemented in SharePoint Products and Technologies. Read more…

.tnemnorivne tenartxe na nihtiw srevres rof stnemeriuqer gninedrah eht dna 7002 revreS tnioPerahS eciffO dna 0.3 secivreS tnioPerahS swodniW rof detroppus era taht seigolopot tenartxe eht tuoba nraeL 0.3 secivreS tnioPerahS swodniW 7002 revreS tnioPerahS eciffO tfosorciM

I’ve spent the past several days in Portland, Oregon speaking at a SharePoint Products and Technologies governance event and completely neglected to post any information on the now released Windows SharePoint Services 3.0 and Microsoft Office SharePoint Server 2007 Service Pack 1. For more information visit: http://blogs.msdn.com/sharepoint/archive/2007/12/11/announcing-the-release-of-wss-3-0-sp1-and-office-sharepoint-server-2007-sp1.aspx.

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.

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.

Problem: web.config is Read-only Isolation: Check upgrade.log at %commonprogramfiles%Microsoft SharedWeb Server Extensions12BINLOGS, looking for the following error: [IisWebSiteSequence] [ERROR] [10/17/2007 11:38:22 AM]: Access to the path ‘C:InetpubwwwrootwssVirtualDirectories5003web.config’ is denied. Cause: Insufficient user rights on the file (ACL); this can happen if the read-only flag is actively set the for the web.config and/or if using a source code management system to maintain web.config. Solution: Ensure that Everyone has write access to web.

A solution is available to administrators of SharePoint Products and Technologies deployments experiencing the following application event after introducing WSS October public update KB934525. Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Topology Event ID: 6800 Date: 10/17/2007 Time: 8:09:40 PM User: NA Computer: HOME Description: The database WSS_Content on HOMEMicrosoft##SSEE is not accessible to missing Windows Internal Database signatures. 1. Run the following STSADM operations to stop and start the SPWebService:

I was recently asked by one of our Premier Field Engineers in Charlotte, NC about the versioning information displayed in SharePoint 3.0 Central Administration after installing recent Windows SharePoint Services 3.0 security updates and decided it would be beneficial to expand the audience for others seeking an answer to this question. Question: In relation to the October patches for MOSS/WSS – should the database version show up correctly in CA? or is it expected that it would should up like this:

I’ve come across a handful of posts regarding KB934525 for Windows SharePoint Services and failure to start the Windows SharePoint Services Administration service. I’ve attached some basic troubleshooting steps that may provide resolution to issues where psconfig fails with Cannot start service SPAdmin on computer ‘.’. For those who have installed the KB and have experienced issues where the service has failed to start, Option 4 is the recommended solution. UPDATE Oct.

A coworker recently came to me asking how to change the SharePoint 3.0 Central Administration URL where two or more Web front-end servers host the Central Administration Web application, for example, where two WFEs are deployed, both will leverage the URL of the first server provisioned with the Central Administration Web application. As many may have noticed, the path cannot be changed via the shortcut properties on the server, the reason is because the URL is Registry-based.

Web applications are the foundation of a SharePoint Products and Technologies server farm and host the root site collection, root and subordinate webs. SharePoint Portal Server 2003 and Windows SharePoint Services 2.0 used the term Virtual Server to designate a Web application also known as a Web site in Internet Information Services. A root site [collection] is the term commonly applied to the what is the uppermost site collection within a server farm or otherwise referred to as the top-level site collection or alternatively portal site collection.

Of the many benefits of Windows SharePoint Services 3.0/Microsoft Office SharePoint Server 2007, often overlooked is the native support of mobile devices through embedded mobile site URLs and mobile views. Mobile views permit both viewing and updating Lists and Document Libraries from a mobile device. When considering leveraging mobile views, you should carefully consider the restrictions on length and size of some parts of a list or library. Limitations Rendering and performance are considered in mobile views, therefore it is important to understand the limitations imposed by these considerations when implementing Lists and/or Document Libraries, for instance many common fields should have a character limitation of no greater than 20 applied, these include List and Document Library titles and names, and List and column name titles.

When preparing to deploy an Internet accessible Microsoft Office SharePoint Server 2007 web farm security is the forefront of discussion and planning. To provide a brief insight into securing SharePoint Products and Technologies, I’ve decided to finally consolidate, compile and make available some of my notes. Hopefully this will be of benefit in helping others understand the method by which SharePoint Products and Technologies communicate and a high-level security overview. Internet Information Services (IIS) is the obvious first candidate for preparation and discussion –we’ve concluded IIS will be configured to use both basic and Integrated Windows authentication methods, basic allows credentials to be transmitted unencrypted and secured by SSL.

A short, but exciting post - Windows SharePoint Services 3.0 is now available to users of Windows Server 2003! For information and download availability visit http://www.microsoft.com/technet/windowsserver/sharepoint/download.mspx. Microsoft Windows SharePoint Services is a versatile technology that organizations and business units of all sizes can use to increase the efficiency of business processes and improve team productivity. With tools for collaboration that help people stay connected across organizational and geographic boundaries, Windows SharePoint Services gives people access to information they need.

Technical Library Product Overview Discover what’s new in Windows SharePoint Services 3.0 and locate product information. Help & How-to Get help and answers to frequently asked questions and common scenarios. Planning & Architecture Get planning and architecture information for implementing Windows SharePoint Services 3.0 in your own environment. Development Find SDK’s, screencasts, and blogs. Deployment & Upgrade Guides Find installation and configuration resources to include recommended topologies and scenarios. Operations

Technical Library Product Overview Discover what’s new in Microsoft Office SharePoint Server 2007 and locate product information. Help & How-to Get help and answers to frequently asked questions and common scenarios. Resource Kit Resource kit for Microsoft Office SharePoint Server 2007 Supplemental Documentation Download supplementation documentation for Microsoft Office SharePoint Server 2007. Planning & Architecture Get planning and architecture information for implementing Microsoft Office SharePoint Server 2007 in your own environment.

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.

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.