Recovered: The MOSS 2007 Install
Let's review the MOSS 2007 Install
Great!
I've got a copy of a virtual machine that's already had a newSID installed and now it's been renamed and has SQLServer 2005 installed. It's also got reporting services and Visual Studio on it.
The trick here is that there another virtual server that's a domain controller and I want to bring this server up so that it's in that domain and not in the LAN domain on which all the virtual hosts run.
So I add the new server to the domain, enter the static IP address and the domain controller as the DNS server but use our LAN DNS as the alternate DNS.
I see reporting services is installed in IIS under the Default Web Site. I'm curious what will become of that after the SharePoint install.
So, I'm running the Office12 cd and here goes.
I enter the product key and then select the Advanced option.
Then, for server type, I select Complete and I click Install now.
The progress bar rolls across the screen and I get a dialog box telling me to run the configuration wizard and a close button. I leave the box checked and click close.
The configuration wizard opens with a Welcome…
I want to create a new server farm.
I point my database to my local server name and my user is a domain service account I added to the local machine's Power User group.
And I get the Red X
Failed to connect to the database server or the database name does not exist. Ensure that the database server exists, is a SQL Server, and that you have the appropriate permissions to access the database server. To diagnose the problem, review the extended error information located at C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions12LOGSPSCDiagnostics_2_21_2007_…log Please consult the SharePoint Products and Technologies Congifuration Wizard help for additional information regarding database server security configuration and network access.
So I correct the typo in the server name and try again.
This time it takes me to the next page. Great. One could note, however, that my database user is a Power User on the box but was not added to the database server at all.
This second page wants a port number for Central Admin and an Authentication option. I've only ever run NTLM so I'll choose it again and click next.
I review the setting and click next and get the flying green boxes that count off tasks 1 through 9. I'm particularly fearful of step 4.
Success! I love that…
So I start up Central Admin and I have to enter my username and password. Now, I'm a domain admin so I enter my name and password.
I have to add the CA site to my list of trusted sites.
This takes a while but CA eventually comes up with the ugly red warning:
! Server Farm Configuration Not Complete !
Now this is not as esy as it was with 2003. You've got this Shared Services thing to worry about. So I look through the administrative tasks.
The first one is to look through the administrative tasks so I make that one done.
I'm not adding any servers to the farm so I mark that one done.
Now, Assign Services to Servers…
So you can select from one of five options and they are:
-
Single server or small farm web server
-
Medium farm web server.
-
Search Indexing server
-
Excel Calculations
-
Custom
When you check Custom you see that you then get all the options in the service list below:
-
Central Admin
-
Document Conversions Launcher
-
Document Conversion Load Balancer
-
Excel Calculations
-
OSS Search
-
WSS Incoming eMail
-
WSS Search
-
WSS Web Application
I really want all these services running on this machine so I'll start them all.
First, start the Document Conversions Load Balancer Service.
Next, start the Launcher Service and choose the server and port number.
Start Excel.
Start Search. Check Use this server for indexing… and Use this server for serving search queries… Enter an eMail address and provide a search account and password. I select Maximum ondexing performance. The Web Front End Crawling option is moot. I click Start.
Oh! Crap! I get the error:
An unhandled exception occurred in the user interface.Exception Information: OSearch (fn18spsvc)
With the dreaded:
Fortunately, our friends at Microsoft have seen this one before and give us this:
http://web.archive.org/web/20070516160637/http://support.microsoft.com/kb/928620
Where they explain that the problem arises from not distinguishing the user name with the appropriate domain prefix.
That done, I start the WSS search.
I use the same acount, this time, wary enough to add the domain name for both the search account and the database account.
All services running… Great! I mark that item done.
All that remains is to configure the farm's shared services.
I click the action link.
Shared services requires it's own web application so I click Create New Application.
So, I don't like this. The Create New Application link takes me to the Create New Application page where it wants me to create a new web application called SharePoint – 80 on port 80 which, I expect will kill my report server. I kind of wanted that to be my portal space but this acts like it will make it my SSP. No sweat, i roll along with it.
NTLM, Anonymous, No SSL and set my app pool to my service account.
So I wait while my changes are processed.
It takes me back to the Create SSP page and says there's an error because I never added a user name and password for the SSP but, sure enough, it's going to create it on my port 80. In the words of Darryll Hall, I can't go for that. no, no can do.
I'm going to click Create New Web Application again, hoping I can create a web app that I can give to my SSP and then still have the port 80 app where I can run my MOSS site.
So, this time I assign a unique port, NTLM, Anonymous and no SSL. Map the app pool to my same service account, restart IIS automatically and wait while my changes are processed.
I end up back at the Create SSP page. This may, in fact, solve another problem. Now, it's good with my SSP on they second web app I made but it's says it's going to let me put my My Sites on my main site using port 80. That would be cool but I do extend the relative url out to /MySites/.
I have to enter my service account password one more time, click OK and wait till my changes are processed.
Shared Service Provider Successfully Created! I love that. Now, I can mark that item done and the ugly red warning is replaced by about ten new tasks. One of them is incoming eMail settings which requires the Windows SMTP service. I'll wait on that one.
The next is Outbound SMTP settings. Since I'm in my own domain, I can't use our internal mail server. So we're going to set up SMTP on the domain controller and so I'll set that later.
Workflow settings is easy.
InfoPath Forms is easy. I'm not requiring SSL and I am allowing all those authentication options.
The rest of the administrative tasks can wait.
I still have the SharePoint – 80 site but it's all populated with Sharepoint stuff so I'm going to have to delete it. Problem is, my MySite stuff is attached to it. Let's see what happens.
I delete the SharePoint – 80 site and then I create a new web application, put it on port 80 and wait while my changes are processed.
I get the application create page. So I click on Create Site Collection.
I give it a name and select the Collaboration Portal from the Publishing Templates tab and wait while my changes are processed.
I get the "Top Level Site Created" and my url. I click it and I have to log in.
Then I wait, and wait…
and wait, and then…
EEEKKK!!! DORKSSSS!!!
Where do they get those dorks? You gotta wonder.
The first thing I do is change the photo. The second is in central admin where I allow all sites to use enterprise features.
-robot
Tags: