- Course Summary of TrainSignal’s Course "SharePoint Server 2013 Administration" - Part 1
- Course Summary of TrainSignal’s Course "SharePoint Server 2013 Administration" - Part 2
- Course Summary of TrainSignal’s Course "SharePoint Server 2013 Administration" - Part 3
Lesson 3: Installing SharePoint
Bill starts lesson 3 by explaining SharePoint Server Roles- basically this hasn’t changed in the big picture: there is a Web Server, Application Server and Database Server.
Next he goes into Server or Server Farm Topologies and explains a Single Server or Stand-Alone Deployment.
(I actually have a disagreement with Bill in that there is a difference between a Stand-Alone Install and a Single-Server Farm Install. What he is referring to in this example is a Stand-Alone Install.
The Single-Server Farm Install is scalable where the Stand-Alone Install is not. The Single-Server Farm is actually a Farm install on one actual physical server but is configured as a farm. I have been doing this install for all my development systems. Bill uses the term Stand-Alone later when he shows a Single-Sever. This was vetted with Chirag Mehta, ( a friend on SharePoint-Community.net)
Next he starts the basic install. After the Install completes, Bill chooses the option to run the SharePoint Products Configuration Wizard when it comes up and of course, we want to run it.
Even though Bill hasn’t used the terms “Grey Wizard” and “White Wizard” to refer to the SharePoint Products Configuration Wizard and the Central Admin’s Farm Configuration Wizard, I will be using this terminology as they are useful to point out some specific scenarios in Bill’s installation. Since the background of the next screens are grey, hence “Grey Wizard”:
Mysterious "Grey Wizard" or SharePoint Product Configuration Wizard
After this configuration wizard finishes, Bill Launches into the “White Wizard” or the Central Admin Farm Configuration Wizard:
Screen to Initiate the "White Wizard"
(At this point many people including me are yelling “Please Bill don’t do the configuration with the wizard!!” Alas, all to no avail. Bill even notes these sentiments. There are other ways to go through and configure farm services via PowerShell Scripts. But there is method to Bill’s going this route; basically, this course is an intro SharePoint Administration on 2013.
Actually this is not as bad as it seems: Bill’s methodology with the major services, like “Search” and “User Profile Administration”, is to initially delete the configured service; then, to reconfigure them.
His simple actions give the student confidence to do the same. This is exactly how I finally got my Profile Administration Services for SharePoint 2013 launched.)
Much Maligned "White Wizard"
Bill does a good job in explaining the basic services and deselecting the ones for a more advanced session.
(Note Bill actually restarts the installation from before the “White Wizard” was run in the next lesson. So that he can go through the wizard again. This means that the majority of services and databases just created will go “bye-bye” and be recreated in the next lesson.)
Lesson 4: Farm Configuration
At this point, Bill takes a step back. He actually picks up from before the “White Wizard” ran, just to see if everyone was awake. (I failed twice.) Some of the services and databases that we configured in the last lesson are gone.
He notes that there is only one Web Application present and that is for “SharePoint Central Administration v4” and then examines the IIS Manager and the SharePoint Central Administration Website.
Next after initiating the Farm Wizard, Bill sets up the “SPSvc” Service Account, Services Account, in Configure Managed Accounts to use an account other than the Farm Account. Bill also spends time discussing password synchronization and how to use the Register Managed Account to see what services are being run by which account.
After the end of the Farm Configuration Wizard, he creates the “Globomantics Main” Site Collection as a Team Site.
Then Bill shows the Services being managed by SPSVC after the Farm Configuration Wizard has been run under Configure Managed Accounts
Register Managed Account after Configuration
(Get any 10 Administrators in a room and there will be 10 ways of doing permissions. This screen under Managed Accounts is helpful to find out who actually has what.)
Finally Bill views the Site Collection in Central Admin and from the URL he opens the site created – you know, the Standard Blue and White SharePoint 2013 “Hello World” Screen. Bill concludes the lesson by showing the new databases created by the “White Wizard”:
Databases – Surprise! Now you see um again-Note Ugly Database Names!
(Note: When the databases are created by the Farm Configuration Wizard, the wizard tacks an ugly guid at the end of the name.)
Lesson 5: The Logical Architecture of SharePoint
If you’ve been doing SharePoint for any length of time this was a “snooze puppy”
Logical Structure of SharePoint
If you have knowledge of what the following terms are: a Farm, a Web Application, an App Pool, a Site Collection and a Site/Web — feel free to move to Lesson 6. If you are really new to SharePoint, the lesson is a good overview.
Lesson 6: Creating Web Applications
Bill walks through the creation of two web sites: the Globomantics Intranet Site and the Globomantics My Sites. But first he examines the Health Monitor. He notes that most of the warnings are because the installation is not complete.
Next he registers SPAdmin, the install account, for the security account of the App Pool he is about to create in the new Web Application. Then he creates the new Web Application from Central Admin:
Creating a Web Application
Bill provides a good explanation of Host Headers, which are needed to give descriptive and unique web directories for applications in IIS.
Next he fills in the information in the Create New Web Application Page so that a new App Pool will be built when the web application is created:
Basic Creation Screen-Bill will change the Ugly Database Name
(Note: See the ugly name for the Database Name with the long guid. This gets renamed to “Globomantic_Intranet” (Yeah Bill!) to make it more understandable and easier to locate.
Next Bill explains the concepts of Service Application Connections:
Web Application Services Hookup
He explains the use of a “Custom Connection Group” when not all default services need to be associated with a particular web application. This might be a web app to do some specific set of tasks.
After creating the Application, Bill is not yet ready to create the Site Collections, so he moves on to create the My Sites Web Application. Basically this is a “Rinse and Repeat” of the first Application created.
Next Bill configures the DNS on the Domain Controller:
Configuring Domain Controller to Configure DNS-Go Bill Go!
(To me this is where Bill really excels doing off-roading. These little side trips can, and do, cost technical people complete days of searching and Googling because not everyone doing these tasks has mastery of all the disciplines involved.)
Next Bill creates a new Host Record in DNS for our Globomantics Intranet Sites (the site will not be accessed from the outside, so only one record is needed to locate the site internally.)
Bill creates another Host Header for the My Sites App. Then briefly reviews the IIS Configuration.