SharePoint 2010 HR Site Setup and Configuration

Documenting setup of our departments for others and future needs. As the title states this is the setup of our Human Resource Departments site.

1. Access Main Site Collection site [http://intranet]
2. Site Actions > New Site
3. Select Publishing Site
• Title: Human Resources
• URL: hr
4. Wait for site to be created
5. Update features for Human Resources site
• Site Actions > Site Settings
• Site Actions > Manage Site Features
• Team Collaboration Lists > Activiate
6. For our site we will be using the following parts:
1. Welcome
• Static welcome message from HR team
2. Announcements
• HR Accounements (Template: Announcement)
3. Document Library
• HR Document Library (Template: Document Library)
4. Training Schedule
• HR Training Schedule (Template: Calendar)
5. Helpful Links
• HR Helpful Links (Template: Links)
7. Setup HR Announcements
1. Site Actions > More Options
2. Select Announcements from list in right pane
1. Name: HR Announcements 
3. Click Create
8. Setup HR Document Library
1. Site Actions > More Options
2. Select Document Library from list in right pane
1. Name: HR Document Library 
3. Click Create
9. Setup HR Training Schedule
1. Site Actions > More Options
2. Select Calendar from list in right pane
1. Name: HR Training Schedule
3. Click Create
10. Setup HR Helpful Links
1. Site Actions > More Options
2. Select Links from list in right pane
1. Name: HR Helpful Links
3. Click Create

SharePoint 2010: Aggregate Calendars

If you receive the following error:

• Could not establish trust relationship for the SSL/TLS secure channel with authority 'Exchange_mail_server'. (87ed56e6-5b15-41ad-8672-72afdeb45460)

Check out this KB for help. http://support.microsoft.com/kb/982982
We completed Method 2 with best success.

SharePoint 2010: Content Query and Announcement's Body

So recently was asked to make our homepage announcements more informational.  As you can see from below not much in detail.

Currently the items above are pulled from each departments site using Content Query Webpart and SharePoint 2010: Aggregating Announcements (http://cleeit.blogspot.com/2013/08/sharepoint-2010-aggregating-annoucements.html).

So first thing I tried was just to display the Body of the announcement.  Well as you can see below that didn't work.

Content Query does not understand HTML.  So how to escape HTML in Content Query, well off to Google I went. It did not take long to locate Kappa Solutions Technology Blog (at the time rated number 3).

The exact article can be found at:  http://blog.kappasolutions.ca/blog/post/2010/09/12/How-to-Display-HTML-in-Content-Query-Web-Part.aspx

Spiceworks How-To write up: http://community.spiceworks.com/how_to/show/62085-sharepoint-2010-content-query-and-announcement-s-body

As there write up is quite nice I will only link to them for now.

End Results

Bamboo SharePoint Solutions

****Warning*****

Something I just learned after I tried to remove a Bamboo SP Calendar Solution from our farm.  It changes webconfig to reference new/updated Telerik command/extension.

The removal of their solution cripples your SharePoint rendering all sites outside of Central Admin unreachable.

Solution is to re-install their core wsp from trail solution.

If you wish to remove completely without crippling your SP check out their write up:

http://community.bamboosolutions.com/blogs/sharepoint-2010/archive/2012/08/23/how-to-remove-a-web-config-modification-using-powershell.aspx

http://store.bamboosolutions.com/KB/article.aspx?id=12486&query=Telerik.Web.UI

SharePoint 2010: Setup Document Library to accept emails

To better utilize our SharePoint setup and reduce strain on end users I needed to set up processing of incoming emails for a couple of document libraries (Quotes and Shipping Labels).  Below are the steps I used to complete.

Check out my How-to with screen shots on SpiceWorks at:
http://community.spiceworks.com/how_to/show/54771-sharepoint-2010-setup-document-library-to-accept-emails

Ensure your SharePoint Server has SMTP feature installed and configured.

---

First we need to configure some farm level features:

1. Access Central Administration > System Settings
2. Configure Incoming email settings
3. Enable Incoming E-Mail
1. Enable: Yes
2. Mode: Automatic
• Automatic for email
• Advanced for drop folder (need to validate permission's on folder)
4. Directory Management Service
1. Directory Management Service: Yes
• No - will have to manually create any needed groups and contacts
• Yes - SharePoint will create groups and contacts as needed
• Remote - Seperate server configured to manage the creation of groups and contacts
2. Container: Enter container info
• We setup a seperate OU for all our SharePoint Accounts and Groups during setup so we just added an OU with in called Contacts
3. SMTP mail server: SharePoint Server with SMTP service running
4. Accept messages from authenticated users only
• Yes for internal use only
• No to allow outside emails to be processed
5. Distrubution group creation
• Yes Allow creation of Distribution groups
• No Deny creation of Distrubution groups
6. Distrubution group settings - Limit settings allowed with SharePoint if groups can be created
• Create new distribution group
• Change distribution group e-mail address 
• Change distribution group title and description
• Delete distribution group
5. Incoming E-Mail Server Display Address
• Set to something user friendly / your domain
6. Safe E-Mail Servers
• You can limit what email servers to process email from or leave it open to all.

---

Next we need to setup the feature on desired Document Library.

1. Navigate to desired Document Library you wish to add feature to.
2. On the ribbon click"Library"
3. Click "Library Settings"
4. Click "Incoming e-mail settings" under Communications
5. Complete the following:
1. Incoming E-Mail
1. Allow: Yes
2. E-mail address: [Enter email address to use]
2. E-Mail Attachments
1. Group: Select process that works for you
2. Overwrite: Decide if overwrite is allowed or not
3. E-Mail Message
1. Decide if the email message needs to be saved also
4. E-Mail Meeting Invitations
1. Decide if the email message needs to be saved also
5. E-mail Security
1. Decide how you want to control who can add to library
1. If allowing outside emails in you may see SPAM

SharePoint 2010 People Search Filtering

Working on our internal Phone book in SharePoint using the Enterprise Search: People Search Feature. I had to ensure none of our service accounts or other non-company users were being displayed.

---

First I setup Connection filters.

• Central Administration > Application Management > Service Applications > 
• Manage Service Applications > User Profile Service > Synchronization > 
• Configure Synchronization Connections > [Your AD Connection] > Edit Connection Filters

Used the Any apply (OR) for the following rules:

         Attribute                         Operator                               Filter

sAMAccountName                 Contains                            Calendar 

sAMAccountName                 Contains                            Privileged 

sAMAccountName                 Contains                                   _ 

userAccountControl                Bit on equals                            17

This takes care of the accounts we have for department calendars [deptcalendar], any elevated management accounts [username Privileged], service accounts [System_Service] and any account that has a non-expiring password.

No even with all of this I was still seeing a service account sneaking in creating its own profile and for the life of me I could not stop it.  I don't care if it has a mySite I just don't want it to show up in our Phone book. 

After about a day and a half of searching finally came across the process to resolve this issue.  I needed to set up an exclusion on the People Search Core Results > Results Query Options > Append Test To Query.

-prefrerredname:"[enter format here]" in our case I setup -preferredname:"SP_*".  Ensure you do this to any pages that contain the People Search Core Results web app in our case we have two pages: People-Directory and peopleresults.

I hope this helps others out there.

Check out my How-to write ups with images on SpiceWorks

SharePoint 2010: People Search Core Results web part: http://community.spiceworks.com/how_to/show/53409-sharepoint-2010-people-search-core-results-web-part

SharePoint 2010: Filter User Profile Service (UPS)
http://community.spiceworks.com/how_to/show/53408-sharepoint-2010-filter-user-profile-service-ups

---

References:
Technet: http://social.technet.microsoft.com/Forums/sharepoint/en-US/b32db0e0-22cb-4d1d-8e49-4c020dffd1cc/how-to-exclude-users-from-people-search-results?forum=fastsharepoint

SharePoint 2010: Adding back deleted User Profile Property

So recently playing with SharePoint User Profiles.  Noticed we were getting duplicate Office/Office Values.  This was being caused by our Sync with AD as SP would pull the Office Field and SP also has an Office Location (that for use was the same).  I attempted to reuse the SP Office Location but could not make it accept the values I wanted.  I just deleted it, oops now profile pages wouldn't load.  Did some searching and found this article to be the most help full.


Adding back deleted User Profile Property
http://social.technet.microsoft.com/Forums/sharepoint/en-US/47f6e479-fad0-456f-ba93-f24c6f1212f0/adding-back-deleted-user-profile-property

Most specifically found Modulacht's response to be the best:

------------------Begin Quote------------------

Create a new Property with name like "SPSLocation" (leave the '-' after 'SPS'). In this way the propertyname will be accepted. Now just start your SQL-Server Management Studio, select and edit the appropriate record in you profile database.

In my case I used the following SQL: Using this SQL to select the appropriate record (Ensure that you only get 1 result-line!!!):

SELECT *
FROM PropertyList
WHERE PropertyName='SPSLocation'

Using this SQL to edit the appropriate record:

UPDATE PropertyList
SET PropertyName='SPS-Location'
WHERE PropertyName='SPSLocation'

------------------End Quote------------------

Followed above steps and within 10 minutes had my Profiles back working.

SharePoint 2010: Hide Recently Modified

For our internal SharePoint each of our departments have a page.  Since we are using the Team Site template the pages are Wikis.  As this does not look professional I had to find a way to block on several pages (10-12 pages).

I did some searching and found you could do this two ways.

First way is per page and requires the Content Manager, following site provided the directions below: http://blog.drisgill.com/2010/09/sp2010-branding-tip-12-hiding-quick.html
This process works good for a few sites (1-3).

1. Navigate to desired site
2. Click Page > Site Actions > Edit Page
3. Click Insert > Web Part
4. Under Media and Content > Content Editor > Add
5. Select the new webpart
6. From ribbon click Format Text > HTML > Edit HTML Source
7. Enter the following and Click Ok:

                  <style type="text/css">          
                         body #s4-leftpanel { display: none; }            
                        .s4-ca { margin-left: 0px; }          
                  </style>

     8.   Hiding the Content Editor

• Webpart Tools Options > Web Part Properties
• Expand Appearance 
• Modify Chrome Type to None
• Click OK
• Save and Close page

Second way is to modify the site collections master page.  Following site provided directions:

http://howididit-sharepoint.blogspot.com/2012/06/sharepoint-2010-hide-recetly-modified.html

1. Navigate to Site with pages
2. Click Page > Site Actions > Edit in SharePoint Designer
3. Select Master Pages from Site Objects
4. Select your master page to edit
• Default is v4.master
5. Click Edit file
• Check out if prompted
6. In code window scroll up till in the <head></head> section
7. Enter following code somewhere between the <head></head> tags
• <style type="text/css">.s4-recentchanges{display:none;}</style>
8. Save the file
9. Navigate back to Master pages
10. Right click on page just edited and select Check In
• Select Publish a major version
• If prompted for content approval click yes
• Browser will open
• Select file Pending Approval
• From drop down click Approve/Reject
• Select approved and add comments if desired, click OK
• Until approved changes will not take affect

Refresh the page and verify changes applied.

SharePoint 2010: Create new Site Collection

Quick run through on how to create a Site Collection on SharePoint 2010 for future reference.

For more details check out:

• SharePoint 2010 Server: http://technet.microsoft.com/en-us/library/cc263094(v=office.14).aspx
• SharePoint 2010 Foundation: http://technet.microsoft.com/en-us/library/cc263165(v=office.14).aspx

1. Access Central Administration site
• Typically server name on port 9999 but will vary with installation.  On server shortcut located at: Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Central Administration
2. Application Management > Create site collections
3. Complete following:
1. Web Application
1. Select Web Application from drop down
2. Ex: Test
2. Title and Description
1. Title: What you want displayed above Ribbon
2. Description: Describe the site for future reference 
• **DO NOT LEAVE BLANK** future admins will HATE you
3. Web Site Address
1. Select if Root (/) or Sites (/sites/) address
4. Template Selection
1. Select desired Template: 
• Good sources for template definitions: 
• http://office.microsoft.com/en-us/sharepoint-help/default-site-templates-HA010174491.aspx
• http://office.microsoft.com/en-us/sharepoint-server-help/a-preview-of-the-sharepoint-server-2010-site-templates-HA101907564.aspx
5. Primary Site Collection Administrator
1. Enter User Name:
• I define Farm Admin as primary
6. Secondary Site Collection Administrator
1. Enter User Name
• Define my privileged account as secondary
• Can add more SC admins later if needed
7. Quota Template
1. Define quota if required
8. Click OK; Wait for processing
4. Completed screen provides hyperlink to new site collection 

Check out the How-To on Spiceworks: 

http://community.spiceworks.com/how_to/show/47536-sharepoint-2010-create-new-site-collection

SharePoint 2010: Creating New Web Application

Little write up on process of creating Web Applications for future referencing on later posts, avoid having to duplicate data over and over.

I will not be explaining all the options for those details check out:

• SharePoint 2010 Server: http://technet.microsoft.com/en-us/library/cc261875(v=office.14).aspx
• SharePoint 2010 Foundation: http://technet.microsoft.com/en-us/library/cc288705(v=office.14).aspx

1. Access Central Administration site
• Typically server name on port 9999 but will vary with installation.  On server shortcut located at: Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Central Administration
2. Application Management > Manage web applications
3. Click New
4. Complete following:
1. Authentication
• Classic Mode Authentication
2. IIS Web Site
• Create a new IIS web site: SharePoint - Test
• Scheme I use is SharePoint - [SiteSubject]
• SharePoint - HR / SharePoint - My Sites / etc
• Port: Typically 80 unless known issues
• Host Header: what you want the URL to be
• http://[hostheader]:port
• Path: Leave as defualt
3. Security Configuration
• Leave all as default unless you know you are using Kerberos/SSL or want to allow Anonymous (Public Sites)
4. Public URL
• URL: Leave default unless want different from Host Header
• Zone: Can't change
5. Application Pool
• Create new: I just double check to make sure scheme is being applied: SharePoint - [hostheader][port]
• Security Account: Leave as defualt (Typically Farm Account)
6. Database Name and Authentication
• Database server: [Enter Database Server DNS Name]
• Database Name: Modify to following scheme
• WSS_Content_[IIS Web site Name]
• Ex: WSS_Content_Test (makes easier to find in SQL database
• Database Authentication: Leave default unless your network requires it
7. Failover Database Server: Enter Server name if you have mirrored SQL servers
8. Search Server: Select desired Server if available
9. Service Application Connections
• Leave as default unless new web application does not require Service Application
10. Customer Experience Improvement Program: No
5. Click Okay; Wait for processing to complete
6. Application Created Should Appear

Check out How-To on SpiceWorks:

http://community.spiceworks.com/how_to/show/47537-sharepoint-2010-creating-new-web-application

SharePoint 2010: My Site Root Deletion/Restoration

So playing around in our My Sites and discovered a My Site for SP_Farm.  Went in and deleted as a typical site collection.  BIG MISTAKE.  Apparently when browsing other My Sites you are view a layered root site (/).  By deleting this I broke My Sites for everyone.  To resolve I had to recreate the Site Collection (followed post at Jerry Orman's Blog SharePoint My Site link stops redirecting users to their Personal Site)

1. Browse Central Administration > Application Management 
1. Click Create Site Collection 
2. Select the My Site Web Application 
3. Set the Title to My Site
4. For URL, select the "/" option for the root 
5. Select the My Site Host site template on the Enterprise tab 
6. Set the SharePoint System account as the owner. 
7. Click OK

That fixed it (whew thought I would have to recreate all the My Sites from a backup last week).

If you want to remove those service account My Sites there are two ways (GUI /  PS):

1. GUI (Central Administration)
1.  Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Central Administration
2. Application Management
3. Delete Site Collection
4. Select Site from Drop Down
5. Delete
2. PS (Power Shell)
1. Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell
2. STSAdm.exe command-line (stsadm -o deletesite -url http://mysite/personal/bobsmith)

Check out How-To write up on SpiceWorks:
http://community.spiceworks.com/how_to/show/47509-sharepoint-2010-my-site-root-deletion-restoration 

SharePoint 2010: Aggregating Announcements

As part of our SharePoint Setup we decided we wanted the ability to aggregate / bubble up / consolidate announcements from multiple sites to our Main Page.  The following is how we accomplished this task while installing simple way for users to control what is displayed.

To start we added custom site columns to top level site that added controls of what was displayed on main page, when and for how long.

1. Launch browser to top level site (in our case http://intranet/)
2. Site Actions > Site Settings
3. Galleries > Site content types
4. List Content Types > Announcement
5. Columns > Add from new site column
1. Name and Type
1. Name: Display on Home Page (Y/N)
2. Type: Yes/No
2. Group
1. Group: Custom Columns or create a new one
3. Additional Column Settings
1. Description: Option to have announcement display on Main Page
2. Default Value: No
• This requires users to select Yes for announcement to be displayed on Home Page otherwise it only displays on their site
4. Update List and Site Content Types
1. Update All content types inheriting: Yes
• This is how we populate this to all child sites
5. Click Okay
6. Columns > Add from new site column
1. Name and Type
1. Name: Display Start Date
2. Type: Date and Time
2. Group
1. Group: Custom Columns or create a new one
3. Additional Column Settings
• Description: Date to Start Display on Main Page
• Required: No
• Enforce Unique: No
• Format: Date Only
• Default value: (None)
4. Update All content types inheriting: Yes
• This is how we populate this to all child sites
5. Click Okay
7. Columns > Add from new site column
1. Name and Type
1. Name: Display End Date
2. Type: Date and Time
2. Group
1. Group: Custom Columns or create a new one
3. Additional Column Settings
• Description: Date to End Display on Main Page
• Required: No
• Enforce Unique: No
• Format: Date Only
• Default value: (None)
4. Update All content types inheriting: Yes
• This is how we populate this to all child sites
5. Click Okay

Now we will setup the home page to display items from other sites.  To accomplish this we will use a Web Part: Content Query.  

1. Move back to top level site
2. Sites Actions > Edit Page
3. Click Add Web Part in desired location (for use we chose the left space)
4. Categories > Content Rollup > Web Parts > Content Query > Add
5. Click open the tool pane or Drop Down > Edit Web Part
6. Expand Query and set the following:
1. Source: Show items from all sites in this
2. List Type: Announcements
3. Content Type: 
1. Group: List Content Types
2. Item: Announcements
4. Audience Targeting: Apply as needed
5. Click Apply
7. Set filters (if desired)
1. Query > Additional Filters:
1. Display on Home Page (Y/N)
• is equal to
• [Yes]
2. Display Start Date
• is less then or equal to
• [Today]
3. Display End Date
• is greater then or equal to
• [Today]
2. Click Apply
8. Expand Appearance
1. Set Title to desired name (we used Current Announcements)
2. Click Apply > Click OK

That is it.  Now when a user creates an announcement they will have the option to set for homepage display.

For How-To write up with steps and images visit post on SpiceWorks: http://community.spiceworks.com/how_to/show/46775-sharepoint-2010-aggregating-annoucements

SharePoint 2010: Install Updates

Quick how-to to update SharePoint 2010.

**Note it is highly recommended to test all updates in test environment before deploying to your production network**

**Note Ensure you plan downtime for each update the longer between updates you wait the longer your downtime: SP2 took roughly 20-25 mins followed by restart**

1. Determine current Version and build with following SharePoint 2010 Management Shell command:
• (Get-SPFarm).buildversion
2. Review what updates need to be applied via following link:
• http://blogs.technet.com/b/sharepointjoe/archive/2011/02/01/sp2010-sharepoint-2010-build-level-and-version-numbers.aspx
3. Download update (s) for your version of SharePoint 2010
4. Move file to location accessible from SharePoint Server
5. Login to SharePoint Server to be updated
6. Browse to location of downloaded file
7. Double-Click to start installation
8. Read and Accept MS Software Licence Terms > Continue
9. Sit back and wait for installation
10. Review output
1. Some updates fail to start ProfileSynchronizationServiceInstance and will need to be manually restarted.
2. Restart if needed
11. Run following SharePoint 2010 Management Shell command as Farm Admin Account:
• Start > All Programs > Microsoft SharePoint 2010 Products > SharePoint 2010 Management Shell
• Press Shift and Right Click > Select Run as different user
• Enter Farm Admin credentials
• psconfig -cmd upgrade -inplace b2b -wait
• wait for it to complete then restart
• Review output
1. If account not correctly permissioned ProfileSynchronizationServiceInstance will fail to start and will need to be manually restarted.
12. Verify update by repeating step 1.

Steps to Start ProfileSynchronizationServiceInstance

1. Access Central Administration
2. System Settings > Services on Server
3. User Profile Synchronization Service > Start
1. Select User Profile Application: [User Profile Service]
2. Enter password for Service Account: [We save them in KeePass]
3. Click Okay

That is all there is.  Biggest thing is to remember to plan for downtime and alert your users when the system will be down.

SharePoint 2010: Importing and Using imported templates

Recently we talked internally about SharePoint and begining to roll it out mainstream.  This involves working with each department and building out their sites.  One department (HR) found a few templates they wanted to work with.  Following is my experience importing and generating a test site from this template: http://www.techsolutions.net/EmployeeTraining.aspx

1. Download and extract your template until you can access the .wsp file
2. Verify the following service is running on SharePoint servers/farm: Microsoft SharePoint Foundation Sandboxed Code Service
• Check out this site for step details (both CA and PS): http://technet.microsoft.com/en-us/library/ff535775(v=office.14).aspx
3. Decide if deploying to new Web Application or existing. 
• New
1. Create a new Web Application 
2. Create a new Site Collection against that new Web Application (Select template "Team Site" while creating this Site Collection)
3. Goto 'Site Settings' of that new Web Application
4. Goto 'Solutions' 
5. Upload Application Template ".wsp" file, and "Activate" that when upload completes
6. Create a new "Site" in the newly created "Site Collection" (in step 2), and select the newly uploaded solution in "Template" section
• Existing
1. Goto Site Collection to apply template to
2. Goto 'Site Settings'
3. Goto 'Solutions' 
4. Upload Application Template ".wsp" file, and "Activate" that when upload completes
5. Create a new "Site" in the newly created "Site Collection" (in step 2), and select the newly uploaded solution in "Template" section

Pretty simple but took me a while as services were not running.

Check out my How-To write up on SpiceWorks: http://community.spiceworks.com/how_to/show/46419-sharepoint-2010-importing-templates

SharePoint 2010: Install Microsoft Productivity Hub 2010 SP1

As we are expanding our SharePoint I decided to play with MS Productivity Hub 2010 SP1 (http://www.microsoft.com/en-us/download/details.aspx?id=28178) to see if it may help my users become more familiar with SharePoint (and other MS tools).

Requirements:

• Windows XP or later 
• 2007 Office System or later
• SharePoint (SP) Server 2010 SP1 with August 2011 CU 
• Silverlight 4
• Farm Administrator privileges

1. Navigate to http://www.microsoft.com/en-us/download/details.aspx?id=28178 and download all files saving them to location accessible from SharePoint (SP) Server(s)
• CoreInstall2010SP1.exe 14.0 MB
• ContentPack2010SP1-1.exe 460.0 MB
• ContentPack2010SP1-2.exe 441.4 MB
• ContentPack2010SP1-3.exe 470.4 MB
• ContentPack2010SP1-4.exe 718.8 MB
2. Unpack all downloads to a directory on one of the servers in your SP farm.
• Created folder called MS Productivity Hub 2010 SP1
3. Verify Administrative rights to User Profile Service Application (By default only SP installation account does)
• Open the Central Administration site. The Central Administration site can be found under the Start menu, in the Microsoft SharePoint 2010 Products folder. 
• Within the Central Administration site, navigate to Service Applications under Application Management > Manage Service Applications. 
• Find the User Profile Service Application in the list. Highlight the row by clicking on the row to the right of the link (do not click the link as this will take you to another page). 
• With the User Profile Service Application row highlighted, click the Permissions button in the ribbon toolbar.
• In the Permissions dialog, verify that your account (or the account being used to install the Productivity Hub) is specified with Full Control before proceeding with Productivity Hub installation. 
• Click OK once you have verified and / or added your account with Full Control permissions.
4. Decide where you want the Productivity Hub site to reside within your existing SharePoint Server 2010 farm. 
• You can choose to deploy the site to a new site collection or to an existing site collection. The installation process will attempt to create or replace the chosen site collection with a new Productivity Hub site collection.
• I choose to install in new web application and site collection.
• Web Application
• Authentication: Classic
• IIS Web Site
• IIS Web Site: MSPHUB
• Port: 80
• Host Header: [name for address]
• Ex: internal / training /etc
• Path: [Change only if needed]
• Security Configuration
• Authentication provider: MTLM
• Allow Anonymous: No
• SSL: No
• Public URL
• URL: http://sptraining:80
• Zone: Default
• Application Pool
• Pool Name: SharePoint - MSPHUB
• Security Account: Configuarable (Predefined SP_Farm)
• Database Name and Authentication
• Database server: [Enter Database Server Name]
• Database Name: WSS_Content_MSPHUB
• Database Authentication: Windows authentication
• Failover Server: [Enter if available]
• Search Server: SharePoint Server Search
• Service Application Connections: Default
• CEI Program: No
• Site Collection
• Central Administration > Create Site Collection
• Web Application: [Select Web Application created above]
• Title: MS Productivity Hub
• Description: MS Productivity Hub Repository
• URL: [web application]/
• Template: Blank Site
• Primary Site Collection Administrator: [Desired User]
• Secondary Site Collection Administrator (if needed): [Desired User]
• Quota Template: No Quota
5. Once you have determined which site collection to use, open the SharePoint 2010 Management Shell from one of the SharePoint front end web servers.
• The SharePoint 2010 Management Shell can be found under the Start menu, in the Microsoft SharePoint 2010 Products folder. 
6. From within the management shell, change directory to where you’ve placed the Productivity Hub installation files.
• cd "C:\MS Productity Hub 2010 SP1" (remove " if typeing)
7. Run the following command from the management shell prompt: .\install [sitecollectionURL] 
• Example: .\install http://myhubsite/  or .\install http://sptraining/
• Select Y to overwrite
8. Monitor the management shell window to answer any prompts and to ensure success (this may take a few minutes). Once the install process completes, the initial site collection will be deployed to target URL. If you chose to install the default content packs during the installation process, you now have those content packs installed. If there are other content packs you wish to install, please do so now before proceeding to the next step. 
9. Next, open the Central Administration site to initiate a full crawl of the new site collection. The Central Administration site can be found under the Start menu, in the Microsoft SharePoint 2010 Products folder. 
1. Within the Central Administration site, navigate to your default Search Service Application instance under Application Management > Manage Service Applications. 
2. From the Search Administration page, click Content Sources from the left navigation menu 
3. Find the relevant Content Source that encompasses the new site collection and choose Start Full Crawl from within its drop-down menu. If you only have “Local SharePoint Server Sites” listed as a content source, perform a full crawl on it. 
• NOTE: The full crawl process may take a few minutes to a several hours depending on the size of your SharePoint server farm. This step is necessary to index the content of the Productivity Hub site collection. 
10. Installation is now complete. You can now navigate to the Productivity Hub site in Internet Explorer and set permissions for your end users and coaches who will need access to the Productivity Hub. Permissions are controlled from the home page. Use Site Actions > Site Settings > People and Groups. Add the relevant users and Active Directory groups to the following SharePoint security groups based on role: 
1. Hub 2010 Members – most users should be placed here. They will be able to view, tag, and rate content, and participate in forums. 
2. Hub 2010 Coaches – same access level as Members, but with access to the Coach Help and the ability to manage content of the Productivity Hub site. 
3. Hub 2010 Owners – Administrators should be registered here. They will have full access to manage content and forum posts, view Site Admin Help, SA Benefits Help, and Coach Help pages; and modify site permissions.
4. Hub Visitors – users who need read-only access to content and forums should be added to this group. Tagging and ratings will still work for these users.