For those of you considering implementing service pack 2 on your SharePoint servers, remember to test out the upgrade packages on your development and staging environments prior to deployment on your production system. For links to the downloads and instructions, check out the SharePoint Product Team blog entry at http://go.spdan.com/sp2
This weekend I undertook the fun of building out a medium sized farm on my personal development hardware with my trusty MSDN license that I bought for my own personal use to begin testing a few pieces of code I’ve been working on as well as to have a play ground to work through occasional architectures, web part testing and diagnosing issues. Oh, and the fact that I’ve not had the opportunity to work with Windows Server 2008 all that much, so I figured why not go ahead and build out an environment to get my hands dirty and learn the ins and outs?
So the first part to the madness that should be understood is that IIS 7 (standard for Windows Server 2008) is a lot more granular in nature than IIS 6 which is the standard web publishing application on Windows Server 2003. From even when you’re starting your installation of the Web Server role to installing the individual components, it’s far more granular and modular, and probably confusing to some administrators that are used to just clicking “IIS” from Add/Remove Program in Server 2003.
So where to begin, well, once you’ve got your Windows Server 2008 box up, operational, patched, service packed, sysprepped (if you’re using Virtuals, you end up requiring that you have different SIDs and computer names right?), IP’d and joined to a domain, the fun begins in installing just the framework prior to SharePoint.
Step 1 – Open up the Server Manager, this typically appears when you power on the server, but if not, you should be able to find it fairly easily from the start menu. Select and expand the roles label from the tree in the left pane, then select “Add Roles” from the right pane.
Step 2 – If this is your first time installing a role, this would probably be helpful to read “Before You Begin”. Definitely read through it at least once, after that, feel free to click the check box to skip it in all future instances. Click on Next.
Step 3 – Select the Web Server role from the list of server roles. Note that you will be prompted to select additional features for the Web Server role to operate properly. Select “Add Required Features” else turn and back away, and perhaps reconsider what you’re looking to do.
Step 4 – Once you’ve accepted the need for additional “required” features to be installed, you should see something like the below stating that you have selected the “Web Server (IIS)”. Click on Next.
Step 5 – The role installation wizard presents an overview of the Web Server (IIS) role which again is fairly useful for an administrator to read through the first time. Click Next.
Step 6 – Select the individual server roles that you require for your SharePoint installation. I’ve found that the basic role services that are installed with IIS 7 are barebones, which from a security posture is fairly helpful so as to not have to remove several roles, but it will make you stop and think through what roles you do indeed to make the system operational.
Step 7 – The first thing to select of course to make your platform usable by SharePoint is the ASP.NET development platform. Once you’ve selected this, you will be prompted to add additional roles that are required for ASP.NET. Select the “Add Required Role Services” else, much like before, be prepared to have a difficult time installing SharePoint services on your server.
Step 8 – Select the additional roles that will assist in your SharePoint implementation, in my case this also includes “Logging Tools” to diagnose issues that may come up.
9 – Select the appropriate authentication providers that you wish to be able to utilize. For me, I’m going with a fairly vanilla SharePoint installation and configuration, so I’ll select “Windows Authentication”.
10 – Additionally, so as to not bother with going back and installing later, I’ve selected the “IIS Management Scripts and Tools”.
11 – Lastly, the “Management Service” to be able to better manage the IIS 7 instance on the server from the server or remotely.
12 – After selecting the roles that are appropriate to support your SharePoint services installation, click on Next, which then will bring you to a page that lists all of the components that you are looking to install. Do a quick read through to ensure that you’ve got the components, roles and features that you require and click on Install.
13 – Observe the installation process as can be seen here:
14 – After a few minutes, the installation progress bar will complete and an installation results page similar to this will be presented. Click on Close after you’ve observed that your installation results were successful.
15 – After you’ve completed your IIS 7 installation, you’ll see that there are 24 installed role services related to IIS running and operational on the server through the Service Manager roles summary.
Next on Tap:
- SharePoint on Windows Server 2008 – Installing and Configuring SQL Server 2005 on a single node
- SharePoint on Windows Server 2008 – Installing and Configuring Microsoft Office SharePoint Server 2007 Standard Edition
- SharePoint on Windows Server 2008 – Configuring Kerberos based Windows Integrated Authentication
I was reading through Itay Shakury’s blog this evening, specifically his article pertaining to “Copied folders are not indexed bug”. Definitely an eye opening article pertaining to the fact that when a folder is copied to a new location, it is no longer indexed by the index server without dumping the index and starting a full crawl.
Similarly, I have found that junior admins inadvertently cause indexing follies of sorts doing migrations. If the junior admin is completing a migration of data through the method of moving a content database from one SharePoint farm to another, there seems to be a high frequency of not defining the indexer for the database in question. In as such, the content database’s site collections are not indexed and search results continue to return not full results.
Other indexing follies that continue to persist:
- Microsoft Office 2007 File Format – http://go.spdan.com/yhupm
- Adobe PDF iFilter 9 for x64 – http://go.spdan.com/mazed