A colleague (@BurggraafW) and I are setting up a SharePoint 2010 portal for our unit. I installed Windows Server 2008 R2, SQL Server 2008 SP1 and all the pre-requisites to install SharePoint Server 2010 beta 2. SharePoint is configured to be in a farm, and not as a standalone server. The installation went smoothly, no errors occurred!
Creating the Web Application
After the installation I created a web application for the portal. As a preparation I created several user accounts that I probably needed for the application pool(s) and service applications.
From Central Administration, click on Manage Web Application and from the Ribbon click New. The following popup screen appears:
Fill in you’re desired settings and click OK. However, there’s an issue here (I suppose beta’s do not have bugs, right?). If you change the path from the default c:inetpubwwwroot… to, let’s say, d:VirtualDirectories, SharePoint will ignore that. The web application will always be located at the default location.
Creating Service Applications
Managed Metadata and taxonomy is awesome in SharePoint 2010. We definitely want to experience it ourselves, so we need to create a new Managed Metadata Service Application. From Central Administration select Manage Service Application and from the Ribbon select the New button and the option Managed Metadata Service. The following popup screen appears. Besides the server name, the form is completely empty.
While the popup screen for the Search Service Application looks like this and is suggesting some names and accounts.
Some suggestions I find doubtful if their are useful names, such as the database names in the User Profile Service Application:
If you have created the Service Application providing it a proper name for the Application Pool, you think it can be found opening the IIS Manager:
Nope. You will find GUIDs (?) instead of the given names.
Let’s wait for the Release Candidate and see what’s improved. For now, it works just fine to set up a new portal in a single farm environment.