What’s gone on before…
In creating the labs 1 & 2, a domain controller was set up, services accounts added to active directory and the developer edition of sql server was installed. Because of the requirements that the lab be a private network, access to the internet is disabled and automatic updates are not available. The update apps for SQL were downloaded previously and will be applied now. Here’s a quick overview of the lab so far:
2 Windows 2008 r 2 Servers
The first one is the domain controller was was set up with the following (virtual) hardware:
Pretty nominal but more than sufficient for a DC
Updating SQL Server
The SQL server is a little more robust but way under where it should be:
The two files downloaded are:
The plan is to apply the server update first then the update to management studio.
Applying the Updates
First, need to run as administrator…
Again with the Passing… this is fine by me…
Accepted the license terms and then got this…
Everything was already selected so it was on to NEXT and the next check…clicked next past the FILES in Use check and then it was time to UPDATE… so CLICK
That’s done, now to update Management Studio..
New installation or add features?
Upgrade from SQL Server 2000, 2005 or 2008?
Search for products?
Shoot, all I wanted to do was process an update to management studio. Well, the next menu item is Maintenance…
Edition Upgrade or Report…
At this point, I don’t think that SQLManagementStudio_x64_ENU was the correct file. I’ll do some searching for KBs later if there are issues.
So, what if…
- Disabled the network connection (I don’t want to lose it)
- Shut Down the server
- Changed back to NAT
- Started the Server
- Ran Updates..
- Shutdown the server
- Changed networks
- Started it back up…
Ya, that worked pretty well. There were 21 updates to apply. Of course, taking this route also pulled in the latest Windows updates (lot of security fixes)
Server 3 SharePoint 2010
Starting from VMWare Workstation 8
Made sure that Windows Server 2008 R2 SP1 was in the drive.
With the disk in the drive, I can use the first option. That and the ISO option are the two used most often.
Two things to note about this screen, fist the product key (no mystery there) and the second is the Version to Install. This is easy to overlook.
Lot’s of cool versions
For now, I’m going with the full enterprise version. With more practice with PowerShell, tackling one of the CORE versions would be cool.
Next a descriptive name and VHD location, so far so good. NEXT
Drive Size…hmmm for now, bump it up to 80g.
I left the default option of splitting the disk up into multiple files. Finally, customize the hardware. This is also easy to overlook.
For the SharePoint box, bump up the memory to 4g. To take advantage of updates, the Network Adaptor will be left set to NAT. Updated the Processor Cores to 2.
Now the settings show up n the wizard. Wahoo…FINISH. Wait… a new challenge box…
Staying with Enterprise…loaded and stable, now for the updates…
Ok, just one or two updates…
with the SharePoint Server offline, resources look like:
Now to start the SharePoint install…first switch over to the private network…toggled the network connection n VMWare and restarted, then set some network properties…
Add the computer to the network
Joined the domain and changed the name…
Got the welcome message:
Restarted…now it’s time to jump over to the Domain controller and add some more accounts.
The SQL Set
To this, I’ll need to add the SharePoint Set…for full details see Plan for Administrative and Service Accounts SP2010
|Service or Purpose||What it does||comments||Account Name Used|
|SetUp and Admn user account||Used to install sharepoint Bits||Runs setup and PSCONFIG||svcSPAdmin|
|Server Farm Account||Manages the SharePoint farm||Used to manage the farm and run timer services. Only used on SP Admin site||svcSPFarm|
|SharePoint Service Applications||AppPool account used for the various services in SharePoint||This account can be one or many accounts depending on the size of the SharePoint Farm and if separation is desired||svcSPApps|
So, starting with these…
Get to hop over to SQL Server and add some access…logged in as administrator…opened up Management Studio, Connected to the Local Server and went to security…
Then it was off to search…add svcSPAdmn to the security Admn and dbcreator roles:
Now install the SharePoint bits on the WFE starting with the pre-reqs
Accept the terms, etc. and move along…if you’re not connected to the internet, the prereqs will fail. I’m not sure which is faster, downloading installs for SQL Client and .Net and installing them or, taking the WFE off the private net, putting it back on so it has access to the internet and running the prereqs that way. The latter certainly means that you catch all the necessary ones defined in the install. At any rate, that’s how I chose to handle it…I prefer easy.
Here’s the list of prereqs…
NOTE: Remembering to change the network connector is quite important… a “no duh” moment. If you don’t you’ll end up fussing ‘round here and there to fix something that ain’t broke.
Now back to the regularly schedule program of installing SharePoint.
Here’s the first trick question. You would think, “OK, this is a single server right now, I’ll go ahead and do Standalone. I can always upgrade it later, right?” This is a very bad assumption. You cannot, ah say, cannot upgrade the standalone later without a lot of effort. So, while I don’t know ‘bout you, I’m going with Server Farm….
What? I just selected FARM, now it’s coming at me again with the Standalone message? Not to worry, here, I’ll be using the complete install. I’ve branched at this point and gone with the standalone for a dev instance. But since I’ve already gone to the trouble of setting up a DC and SQL box, going with Standalone would be pointless…
The binaries are loaded, so now it’s time to set up the admin portal… so you leave the little box check and click…CLOSE? Ya, not really intuitive. Maybe it should say, if you want to use PowerShell to complete your SharePoint install, uncheck the box. Blah blah blah…since this is for a lab, I’ll let the wizard do its thing…sites, I’ll use powershell…
Again with the warning boxes…YES of course
No farm exists yet, so it’s time to CREATE…
Specify my new minted SQL Server and away we go…
Next, enter passphrase…Th3 P@ssphr@se!…Next..Kerberos!
One reason (among several) to use PowerShell at this stage is that you have better control over the names of the databases. Here, we get:
Everything was going well, then IE struck or rather the routing through the network failed to find the webserver. Could it be that there needs to be a DNS entry? http://localhost:<<port#>> works just fine. So off to DNS world seems likely but not really. The mapping is there in DNS, SharePoint just doesn’t know how to react. I’ve only run into this using the wizard on a network install. A standalone (of course) doesn’t run into the same issue and typically when setting up a single server, that’s also not an issue.
NOTE: When the install is complete and the challenge dialog will bring up the site using either the FQDN and a local system login or LocalHost with a network login, something gets lost in connecting to the server.
So, it’s time to stop and I’ll pick this up with Alternate Access mapping…