Home > Microsoft, SharePoint > Adventures in SharePoint 2010 1

Adventures in SharePoint 2010 1


Purpose: To set up a SharePoint 2010 development environment for Proof of concepts. SharePoint 2010 is a new product for our shop. We elected to not go from 2003 to 2007 to 2010 but went directly to 2010. This decision was made after coming to the 2007 party late and hearing the good reports about 2010. In taking this approach, I decided to create our sites from scratch rather than trying to coerce the 2003 set up through. This seemed to bo the best way to go. From the research into the problem, starting from scratch was a smaller effort than trying to migrate from 2003. Primary information has been gleaned from Sahil Malik’s book “Microsoft SharePoint 2010 Building Solutions for SharePoint”, Noel Spence’s book “Microsoft SharePoint 2010 – Unleashed”, TechNet and MSDN.

This blog starts after a lot of trial and effort. These are the items I found most useful in this process. The first is setting up a prototype environment to both try new things and blow some up in a safe environment. The only thing I really lost was time. On the other hand, learned a lot.

Δ Do’s and Don’ts: Stay away from trying this on a machine with only 4g of memory and an external hard drive running on USB unless you have the patience of a mountain.

Setup – started with Windows 2008 R2 Standard server on VM Workstation with 2g allocated memory and 60g allocated space. Fully patched and updated.

  1. Cloned to a new machine by creating a full standalone clone. Pro’s, back up instance of the w2k8r2 box. Con’s, two systems to apply updates to
  2. Opened up the new server destined to be SharePoint and made it more workstation like by using Sowa’s tool from win2008workstation.com
  3. Since this is not a “production” system,running the tool under Administrator, I removed the shutdown tracker on “Visual Tweaks” tab
  4. Not into verbose, so I disabled the start up/shutdown messages
  5. The rest of the controls on this tab enables the desktop experience. My preference is to enable them. At this point I ran into some errors with the converter tool. It would install the first option but failed to enable themes service. <–to be determined later.
  6. On the general tab, enables audio, optimized for programs, turned off the IE Enhanced Security, added the .Net Framework
  7. Discovered that Servermanagercmd.exe is no longer favored…
  8. Changed the computer name from WIN-74580DE9GUT to w2k8r2spsa (Win 2008 R2 SharePoint StandAlone)
  9. Stopped ignoring the reboot now commands and restarted the computer

Active Directory Domain service role needs to be activated on the server.

  1. From the Initial Configuration Tasks Screen Click on “Add roles” link and read the “Before You Begin”
  2. From the Selected Server Roles Page, check Active Directory Domain Services
    1. .NET FrameWork 3.5.1 Challenge dialog opens, click on “Add Required Features”
    2. Click Next
  3. On the Intro – you can click the links for additional information and/or click “Next”
  4. On the next screen you get some messages with a notice of possible restart, click “Install” This will take a minute or two
    1. If automatic updates are not activated, a warning will appear
    2. Look for the Green check marks indicating success
    3. Click on the link “Close this wizard and launch the Active Directory Domain Service Installation Wizard (dcpromo.exe)”
  5. The new wizard starts, leave “Use advanced mode installation” unchecked and click next
  6. Read through the Operating System Compatibility for addition information. Does not apply to this stand alone environment. Click “Next”
  7. Select “Create a new Domain in a new forest”
  8. enter the FQDN of the forest root Ex: t5s.corp –> the system will check and see if the name is already in use
  9. select Windows Server 2003 functional level. –> this is a good clone point for future consideration to split to 2008 r2 domain controller
  10. same with the next page. After a few minutes, the “Additional Domain Controller Options” page will open. Leave “DNS server” checked and click next.
  11. A warning message will appear. For a development system, DHCP is fine, so click “Yes…”
  12. Another warning message “A delegation for the DNS server cannot…” At this point, we want to continue so pick “Yes”
  13. On the next screen accept the default file folder locations
  14. Finally, provide a strong but memorable password (this is a development environment) like sh@rePoint2011 or fr@meWork1!
  15. click “Next: and wait…click “Finish” once the wizard has completed and perform obligatory restart –> might be a good time to check for updates before restarting (enable automatic updates – there were 50 at this point).
  16. Config File

Configure this server as the first Active Directory domain controller in a new forest.

The new domain name is “t5s.corp”. This is also the name of the new forest.

The NetBIOS name of the domain is “T5S”.

Forest Functional Level: Windows Server 2003

Domain Functional Level: Windows Server 2003

Site: Default-First-Site-Name

Additional Options:

Read-only domain controller: “No”

Global catalog: Yes

DNS Server: Yes

Create DNS Delegation: No

Database folder: C:\Windows\NTDS

Log file folder: C:\Windows\NTDS

SYSVOL folder: C:\Windows\SYSVOL

The DNS Server service will be installed on this computer.

The DNS Server service will be configured on this computer.

This computer will be configured to use this DNS server as its preferred DNS server.

The password of the new domain Administrator will be the same as the password of the local Administrator of this computer.

…by the way, this install, set up and all is for a standalone SETUP of SharePoint 2010 for the purpose of proto-typing, sandbox and learning environment. These instructions and observations are not intended for production use.

  • The server is still in a defaulted state but now has the dns set up and the 50 most recent required updates installed. Of the 24 remaining optional updates, 22 are recommended updates. Being the adventurous soul, I took a snapshot of the server then installed the 22 recommended updates.
  • Snapshot Updated Server with DNS installed

This took no time so it was time to power back on the system and install the updates. Why a snapshot instead of a full clone? Snapshots take up very little space and are quick. Like a restore point, are easy to roll back to. Now that the server is fully updated, it’s time to move onto the next step and add an application server.

Next steps:

  1. Add the application server role to the system
    1. From the Initial Configuration Tasks screen click on “Add Roles”
    2. Now check the “Skip this page by default” box if you land on the “Before You Begin” page
    3. Clicking on the “Application Server” box brings up the Add Roles Wizard.
    4. Click on “Add Required Features”
    5. Click “Next” when returned to the Select Server Roles screen
    6. Read the “Things to Note” and check out the additional information links then click “Next”
    7. Select IIS Support (This will autocheck http activation after the warning screen).
    8. Click “Next” and accept defaults. Keep “Nexting” until the confirm screen and click “Install”
    9. Validate that the installtion completed with Green Checks.
    10. Click close
  2. Add Visual Studio
    1. Go through the VS Set Screens
    2. Install the full version (Default Install)
    3. This would be a good time to go read some email, write some coce, VS takes a bit of time to install
    4. If you want, install the documentation. Because this is a limited space VM, I chose to skip that step.
    5. This is a good place to visit the Visual Studio Galllery and maybe get the Visual Studio 2010 SharePoint Power Tools
  3. Check for updates – by now you’ve added more “stuff” to your install
    1. Service Pack 1 for W2008 R2 64 is available
    2. Note, VS 2010 SP1 is also available

At this point, you make want to clone this install or checkpoint it. I would clone here if I was going to branch and create different servers to develop against.

Other links of interest: http://www.harbar.net/archive/2010/03/31/sharepoint-2010-and-kerberos.aspx

…by the way, this install, set up and all is for a standalone SETUP of SharePoint 2010 for the purpose of proto-typing, sandbox and learning environment. These instructions and observations are not intended for production use.

<thinking> Title is getting old…oh well, it’s already there.

Server Summary:

Roles and Features installed

Roles and Features installed

So far the, what’s been installed:

Installed Programs

Depending on your preferences, set up your environment how you want it.

For example:

  1. Open Libraries
  2. Click on Organize
  3. Click on Folder and Search Options
  4. Review the settings on General, View and Search and change them to your personal preference.

Back to SharePoint Setup

  1. 64 bit all the way (office, designer)
  2. First along the path is SQL Server. When Visual Studio installed, SQL Express was installed.
  3. SqlServer 2008 R2 Developer Version
      1. If Autorun doesn’t start, Open Default.HTM
      2. Choose the SQL Server 2008 RD Developer Edition Link
      3. Click on Setup.exe
      4. Run the System Configuration Checker from the Planning page to make sure you’re ready to go
        1. Warning: Installing SQL … on a Domain Controller is not recommended. Since this is a stand alone VM environment for development, this is not a concern.
        2. Warning: Rule “Microsoft .NET Applicaton Security” generated a warning. The firewall configuration is not correct.
          1. In a browser, goto http://crl.microsoft.com/pki/crl/products/MicrosoftRootAuthority.crl
          2. Click on Open
          3. Click on Allow
          4. Click on OK
          5. Rerun the validation and there should only be the domain warning which can be ignored
      5. Review any of the other links on the planning page that apply or are of interest
      6. Click on the Installation Link
      7. Go with the New Installation… link
      8. Once the Setup Support Rules completes, review and fix any failed rules (they should all pass but just in case :))
      9. Click OK
      10. Product key is pulled in from the MSDN DVD, Click Next
      11. Review then accept the license terms and click next
      12. Install Support Files
      13. You may get a warning to modify the FireWall. Goto http://go.microsoft.com/fwlink/?LinkId=94001 and walk through all the operations for DB, Analysis and Report Server Access
      14. Install All Features with Defaults

    1. Click Next Accept the Default Instance and click next
    2. Click passed the Disk Space Requirements
    3. Specify Service accounts and Collation (Change if the default is not your standard) Also See: http://msdn.microsoft.com/en-us/library/cc281953.aspx
    4. Specify Mixed Mode authentication – if this were a production environment, you would also specify the data and log directories as well
    5. Add the current user to the Analysis Services Account Provisioning
    6. Install the SharePoint Reporting Services
    7. Click “Next” until you reach “Install” then Click “Install”
  4. Run updates, patch and snapshot server

<Grateful Dead playing in the back ground… “Casey Jone’s you better watch your speed…”> What is it with installs and Grateful Dead tunes…by the way, this install, set up and all is for a standalone SETUP of SharePoint 2010 for the purpose of proto-typing, sandbox and learning environment. These instructions and observations are not intended for production use.

A quick check and all the updates and service packs have been applied… It’s time for SharePoint <and the crowd goes wild>

Open the splash

  1. Review Hardware and Software and take a look at the Installation Guide
  2. Prep the system for installing SharePoint
  3. Go to active directory and add a new user
    1. Click on “Start”, “Administrative Tools” and “Active Directory Users and Computers”
    2. In your Domain, right click on “Users” and select “New”
    3. Give it a name like spAdmin@t5s.corp
    4. Click on “Next”
    5. Provide a password you can remember, then set it to No Change and Never Expire
    6. Click on “Next” then “Finish”
  4. Provide the user with SQL Server Access (DBCreator and DBSecurity roles)
    1. Open SQL server management studio
    2. Open the (local) database
    3. Click on the Security Folder
    4. Right Click on the Logins folder and select new login
    5. By login name, click on the “Search Button”
    6. Locate your spAdmin user
    7. Click “OK”
    8. on the Login – New page, click on “Server Roles”
    9. check dbcreator and securityadmin roles and click “OK”
    10. Close Management Studio
  5. Return to Active Directory User and Computers
    1. Right click on your domain name and select “Delegate Control…”
    2. Click “Next” once the wizard starts
    3. Add the spAdmin user
    4. on the next screen choose “Create a custom task to delegate”
    5. Choose “This folder, existing objects in this folder…” option click “Next”
    6. Leave “General” checked and then select “Replicating Directory Changes” in the list below
    7. Click “Next” and “Finish”
  6. Back to SharePoint config <–create a Snapshoot

Install the prerequisites

  1. Log On as spAdmin
    1. The “user” that is logged in will own the farm
    2. Not critical for a sandbox but a good habit to get into
    3. Make sure the DB Access is good
  2. Start the SharePoint DVD
  3. Grant the application authorization to run
  4. <optional> click on the learn link and save the page for later review and click “Next”
  5. Accept the License Terms
  6. Review the final screen and make all prereq’s installed. Click “Finish”
  7. Start the configuration Wizard
  8. Choose “Create a new server farm”
  9. Provide a name for the database and use the spAdmin account for the db access account
  10. Click “next” <–Create a snapshot

Install SharePoint Server

  1. Insert the MSDN Key and wait for validation then click “Continue”
  2. Accept the Terms and “Continue”
  3. Accept default locations and click “Install Now”
  4. On the final screen, make sure the “Run the SharePoint Products Configuration Wizard now” is checked. Then click on “Close”
    1. If you installed SharePoint and Did not run the configuration wizard, it can be started as follows
      1. Click on Windows “Start”
      2. Click on “All Programs
      3. Click on “Microsoft SharePoint 2010 Products”
      4. Click on “SharePoint 2010 Products Configuration Wizard”
  5. Click on “Next” then “Yes” on the warning screen
  6. Put in the name of the SQL Server instance : “(local)” will not work
  7. Here you can change the database name or leave it SharePoint_Config
  8. Put in the spAdmin user name and password
  9. Click on “Next”
  10. Provide a “strong” yet memorable 🙂 passphrase
  11. Provide a port and security settings
    1. For an “Admin” port number, you can accept the random generated number or provide your own between 1-65535. I like to use the Year plus 1 (20111) for example (this avoids the range of well know ports 0-1023)
    2. Kerberos is recommended setting for security see http://technet.microsoft.com/en-us/library/cc753173(WS.10).aspx and http://technet.microsoft.com/en-us/library/ee806870.aspx
  12. Click Next
  13. Read the warning and Click Yes
  14. Review the Completing the SharePoint Products… screen and click “Next”
  15. Configurtation Successful is the screen you want. Click on “Finish”* <- create a snap shot
  16. This brings up the Central Admin Configuration Wizard, Click on Start the Wizard
    1. Service Account (for the Standalone use spAdmin, see http://technet.microsoft.com/en-us/library/cc262451.aspx for a wealth of worksheets and info)
    2. Leave the default services checked and click on “Next”
    3. Create a site (You can skip this and come back later)
      1. Provide a Title and Description
      2. Choose a template (for a minimum set up, choose Blank Site)
      3. Click on “OK” <- another great snapshot opportunity
      4. Click on “Finish”
    4. You can re-run the wizard any time.

*If it fails at this point, you may have to remove the database (or roll back to a earlier snapshot) if it was created before re-running the wizard. Also, by the time you’re done, you will be very tired of typing out Strong Passwords and Pass phrases. I found that being consistent made this process a whole lot easier. Especially during the OMG, it freaking failed moments and it was roll back time. If there is one step to take that rises above the rest, snapshot often! It’s very similar to coding. You don’t learn the value of save and save often until you’ve spent all day working on the ultimate masterpiece only to have the computer completely FREEZE when you pressed run. Your only way out was CTRL – ALT -DEL or worse case, the power button…

Time to change up the soundtrack a bit. At first it was Arrowsmith and “Toys in the Attic” followed by Mindi Abair and “It just happens that way” and finally ended with Joe Walsh and “Life’s been good”.

Now, I’m sitting here staring at the SharePoint Central Administration Screen. Good ol’ w2k8r2spsa:20111/default.aspx. Lots of settings to go through.

1st though, let’s look at the “Monitoring Section”. You might want to look at SharePoint Server 2010: Operations Framework and Checklists.

At this point, you will probably not see the yellow or red notification across the screen but it will come!

  1. Click on Monitoring
    1. Click on Health Analyzer’s “Review problems and solutions”. If there were any issues the reports would show up here.
    2. Return to Central Administration
  2. Click on application Management. Your blank site shows up as SharePoint -80 (Port 80)

    1. Now, for grins, click on Configuration Wizards
    2. Launch Farm Configuration Wizard
    3. Go with the defaults on the next page, click “Next”
    4. Notice how the “/” option for sites no longer exists
    5. Click “Cancel”, we’ll add another site in a different fashion
    6. At this point, hopefully you are still logged in as spAdmin
    7. Open up a new tab on your browser
    8. Type in the address for the computer less the port or add port 80 <computername>:80

 

  1. Next click on “Site Actions” then “New Site”

The default template section opens and you have “All Types” and “All Categories” open. The “blog” template is visible. If you click on the “Content” filter type, the templates are reduced to Document Workspace, Blog and Document Center. I’ll add a blog.

  1. Click on “Blog”
  2. Give the Site a title and a URL Name.
  3. Then click on more options (You can also start with this)
  4. Look at “Permissions, Navigation and Navigation Inheritance”
    1. Permissions
      1. If access to this site is the same as the parent, leave the default “Use same permissions…” checked
      2. If the site will have special permissions, select “Use Unique…” simple right?
    2. Navigation – Two options to set
      1. If you want a link on the top only, the default of No, Yes is the setting
      2. If you want a link on the top and side, Yes, Yes is the setting
      3. No links = No No
    3. Navigation Inheritance – I would have made the default “Yes” but it is set to “No”. If you want a consistent connection to the home site, switch this to “Yes”

The settings:

Get You…:

Where:

Adds “My Blog” to the link bar. The bigger deal is the “Home” button that seemed to do nothing before (e.g. Home = My Blog) has changed behavior to “Home = Site Home” and returns you to the main site page.

Ok, enough of playtime. Tomorrow it’s back to serious settings and configuration of SharePoint. It’s nice though to take a break and play with application.

Advertisements
Categories: Microsoft, SharePoint Tags:
  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: