Home > Uncategorized > Creating the lab 3

Creating the lab 3


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:

image

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:

image

The two files downloaded are:

SQLServer2008R2SP1-KB2528583-x64-ENU

SQLManagementStudio_x64_ENU

The plan is to apply the server update first then the update to management studio.

Applying the Updates

First, need to run as administrator…

image

Again with the Passing… this is fine by me…

image

Accepted the license terms and then got this…

image

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.. 

Started the app and got the choice screen:
image

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…

  1. Disabled the network connection (I don’t want to lose it)
  2. Shut Down the server
  3. Changed back to NAT
  4. Started the Server
  5. Ran Updates..
  6. Shutdown the server
  7. Changed networks
  8. 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

image

Made sure that Windows Server 2008 R2 SP1 was in the drive.

SNAGHTML66651d8

With the disk in the drive, I can use the first option.  That and the ISO option are the two used most often.

SNAGHTML667b5e7

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.

SNAGHTML6693aee

Lot’s of cool versions

image

For now, I’m going with the full enterprise version.  With more practice with PowerShell, tackling one of the CORE versions would be cool.

SNAGHTML66d9b75

Next a descriptive name and VHD location, so far so good.  NEXT

Drive Size…hmmm  for now, bump it up to 80g.

SNAGHTML6709cdc

I left the default option of splitting the disk up into multiple files.  Finally, customize the hardware.  This is also easy to overlook.

SNAGHTML6714af5

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.

image

Now the settings show up n the wizard.  Wahoo…FINISH.  Wait… a new challenge box…

image

Staying with Enterprise…loaded and stable, now for the updates…

image

Ok, just one or two updates…

with the SharePoint Server offline, resources look like:

SNAGHTML75bd5cb

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…

image

Add the computer to the network

image

Joined the domain and changed the name…

image

Got the welcome message:

image

Restarted…now it’s time to jump over to the Domain controller and add some more accounts.

The SQL Set

image

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…

image

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…

image

Then it was off to search…add svcSPAdmn to the security Admn and dbcreator roles:

image

Now install the SharePoint bits on the WFE starting with the pre-reqs

image

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…

image
Now it’s “exit” the in stall, change back the ipconfig and reconnect to the private network…

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. 

image

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….

image

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… Smile

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…

image

Again with the warning boxes…YES of course

image

No farm exists yet, so it’s time to CREATE…

image

Specify my new minted SQL Server and away we go…

image

Next, enter passphrase…Th3 P@ssphr@se!…Next..Kerberos!

image

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:

image

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#>&gt; 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…

Categories: Uncategorized
  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: