SharePoint 2010 Content Free Training & VPC from MSDN

- You can download the SharePoint 2010 Virtual Machine
http://www.microsoft.com/downloads/details.aspx?FamilyID=0c51819b-3d40-435c-a103-a5481fe0a0d2&displaylang=en
- Check out the What's New in SharePoint 2010 for Developers clinic; a free 2-hour e-learning course
>> https://www.microsoftelearning.com/eLearning/courseDetail.aspx?courseId=160329&tab=overview
- Check out the What's New in SharePoint 2010 for IT Pros clinic; it's a 2-hour free e-learning course!
>> http://www.microsoft.com/learning/elearning/course/10279ae.mspx

Publishing an Service Application in SharePoint 2010

I have installed 2 different SharePoint 2010 Farms with all service applications installed.

- The Publishing Farm: That’s the farm that Publish the Service Application.

- Consuming Farm: That’s the farm that Connects to the Remote Service Application.

First off all i create a Trust between the 2 Different Farms so that I can publish the Search Service Application. You must provide two trust certificates to the publishing farm: a root certificate and a security token service (STS) certificate and the publishing farm must provide a root certificate to the consuming farm.

Export the root certificate from the consuming farm:

1. Start SharePoint 2010 PowerShell

2. I have typed 2 PowerShell Commands to export the root certificate from the consuming farm. I have created the certificate on the C drive for example.

- $rootCert = (Get-SPCertificateAuthority).RootCertificate

- $rootCert.Export("Cert") | Set-Content C:\ConsumingFarmRoot.cer -Encoding byte

Export the STS certificate from the consuming farm:

1. Again I typed 2 PowerShell commands:

- $stsCert = (Get-SPSecurityTokenServiceConfig).LocalLoginProvider.SigningCertificate

When you enter this command you will see this error. So what you can do is remove the Config command from the Powershell commando (Get-SPSecurityTokenConfig) So then you Type (Get-SPSecurityTokenService) and it works fine!

- I typed the second command: $stsCert.Export("Cert") | Set-Content C:\ConsumingFarmSTS.cer -Encoding byte

Export the root certificate from the publishing farm

1. Click SharePoint 2010 Management Shell.

2. Typed again the 2 following Commands:

- $rootCert = (Get-SPCertificateAuthority).RootCertificate

- $rootCert.Export("Cert") | Set-Content C:\PublishingFarmRoot.cer -Encoding byte

copy the certificates

1. I Copy the root certificate and the STS certificate from the server in the consuming farm to the server in the publishing farm.
2. The I Copy the root certificate from the server in the publishing farm to the a server in the consuming farm.

Import the root certificate and create a trusted root authority on the consuming farm

1. At the Windows PowerShell command prompt on a server in the consuming farm, I typed the following commands, and then press ENTER after each command

o $trustCert = Get-PfxCertificate C:\PublishingFarmRoot.cer

o New-SPTrustedRootAuthority PublishingFarm -Certificate $trustCert

Import the root certificate and create a trusted root authority on the publishing farm

1. To establish trust on the publishing farm, you must import the root certificate that was copied from the consuming farm and create a trusted root authority. You must then import the STS certificate that was copied from the consuming farm and create a trusted service token issuer.

I used the following 2 commands to import the root certificate:

o $trustCert = Get-PfxCertificate C:\ConsumingFarmRoot.cer

o New-SPTrustedRootAuthority ConsumingFarm -Certificate $trustCert

import the STS certificate and create a trusted service token issuer on the publishing farm

1. An the Last PowerShell command to import the STS certificate:

o $stsCert = Get-PfxCertificate c:\ConsumingFarmSTS.cer

o New-SPTrustedServiceTokenIssuer ConsumingFarm -Certificate $stsCert

As you can see I have created an Trust between 2 different farms.

So after that you can publisch you Service Application. In my cas I hav choosing for the Search Service Application.

- Verify that the user account that is performing this procedure is a member of the Farm Administrators SharePoint group.

- On the SharePoint Central Administration Web site, click Application Management, and then click Manage service applications.

- Click the row that contains the service application that you want to publish. Commands on the ribbon become available.

- On the ribbon click Publish.

So as you can see you must selected the option Publish this Service Application to other farms.

Also in this option you will see a Published URL. Copy this Url to Notepad and keep it Safe!

So Click on Ok an your Service Application has been published.

connect to a service application on a remote farm by using Central Administration

- On the SharePoint Central Administration Web site, click Application Management, and then click Manage service applications.

- On the ribbon, click Connect.

- On the Connect drop-down menu, click the kind of service application to which you want to connect.

- Then I have chosen for the Search Service Proxy.

- Copy the Published Url that you copied Farm or Service Application address.

- Click on OK

- The new Connect to a Remote Service Application dialog box displays the service applications that match the URL that you typed in the earlier Step. Click the row that contains the name of the service application, and then select the check box to add the service application connection to the farm’s default list of service application connections (default proxy group). Click OK

- You are prompted to change the connection name. Type a new name into the Connection Name text box or leave the default name, and then click OK.

- After the new connection is created, you must click OK to complete the procedure.

- You must associate the new service application connection with a local Web application

-

- Finish. Its Easy!!

Download SharePoint 2010 Beta 2 Virtual Machine

The SharePoint 2010 Beta 2 Virtual Machine aka 2010 Information Worker Demonstration Virtual Machine (Beta) is now available for everyone!  This is one day after Microsoft released the SharePoint 2010 Beta 2 virtual machine for SDPS Partners Only

Microsoft has been kind to release a two Virtual Machine set for evaluating and demonstrating Office 2010 and SharePoint 2010. Go ahead and download the SharePoint 2010 Beta 2 VHD

Virtual Machine Contents

Virtual machine "a" contains the following pre-configured software:

• Windows Server 2008 SP2 Standard Edition x64, running as an Active Directory Domain Controller for the “CONTOSO.COM” domain with DNS and WINS
• Microsoft SQL Server 2008 SP2 Enterprise Edition with Analysis, Notification, and Reporting Services
• Microsoft Office Communication Server 2007 R2
• Visual Studio 2010 Beta 2 Ultimate Edition
• Microsoft SharePoint Server 2010 Enterprise Edition Beta 2
• Microsoft Office Web Applications Beta 2
• FAST Search for SharePoint 2010 Beta 2
• Microsoft Project Server 2010 Beta 2
• Microsoft Office 2010 Beta 2 10. Microsoft Office Communicator 2007 R2

Virtual machine "B" contains the following pre-configured software:

• Windows Server 2008 R2 Standard Evaluation Edition x64, joined to the “CONTOSO.COM” domain
• Microsoft Exchange Server 2010 Active directory has been preconfigured over 200 “demo” users with metadata in an organizational structure.

All of these user profiles have been imported and indexed for search within SharePoint Server 2010, with “contoso\administrator” granted administrator permissions. SharePoint Server 2010 has been configured in a “Complete” farm using Kerberos authentication and the default SQL Server 2008 instance for data, and has a site collection created using the Team Site template at http://intranet.contoso.com/ and a FAST Search Center at http://intranet.contoso.com/search/.

Performance Considerations

If possible, unpack and run the VM image on a separate, fast hard drive (7200 RPM or better) from the operating system of the host machine. If this is being done on a laptop, a second internal drive or external eSATA drive works best, though USB 2.0 (make sure it's 2.0, 1.1 is too slow) or Firewire is acceptable. For absolute best performance use a second internal SSD drive.

Operating System Requirements of SharePoint 2010

SharePoint 2010 will support only 64-bit (x64) versions of Windows Server 2008 SP2 and Windows Server 2008 R2.  SharePoint will not install at all on 32 bit Windows, or any earlier version of Windows  such as Windows Server 2000 or Windows Server 2003.

SharePoint is not supported on 'Server Core' installations of Windows Server 2008 and R2. The Server Core installations of Windows server do not contain some of the components required for SharePoint to be configured or run.

To make developing for SharePoint 2010 easier, it is possible to install SharePoint on 64-bit versions of Windows Vista SP2  and Windows 7. Note that running production environments on these OSes are not supported and it will not be possible to upgrade deployments running on client versions of Windows to future versions of SharePoint.  Instructions on installing SharePoint 2010 on client versions of Windows are a bit more involved and we recommend reading the instructions at http://msdn.microsoft.com/en-us/library/ee554869(office.14).aspx.

 
 

Windows version/edition (64 bit only)	SharePoint 2010 support
Windows Server 2008 R2 Foundation	No
Windows Server 2008 R2 Standard	Yes
Windows Server 2008 R2 Enterprise	Yes
Windows Server 2008 R2 Datacenter	Yes
Windows Web Server 2008 R2	No
Windows HPC Server 2008	No
Windows Server 2008 R2 for Itanium-based systems	No
Windows Server 2008 Standard	Yes
Windows Server 2008 Enterprise	Yes
Windows Server 2008 Datacenter	Yes
Windows Web Server 2008	No
Windows Storage Server 2008	No
Windows Small Business Server 2008	Yes*
Windows Essential Business Server 2008	Yes*
Windows Server 2008 for Itanium-based systems	No
Windows Server 2008 Foundation	No
Windows Vista	Developer-only**
Windows 7	Developer-only**

* Small and Essential Business Server editions of Windows install SharePoint as an optional component.

** Support for specific editions of Windows 7/Vista are yet to be finalized, but are likely to be 'Business'/'Professional' editions and above.

 
 

The list above is meant for informational purposes only. The official list of system requirements for SharePoint 2010 is located at http://technet.microsoft.com/en-us/library/cc262485(office.14).aspx and includes additional details on prerequisites and other optional components.

SharePoint 2010 Multi-Tenant Hosting Part 2 “Configuring”

Part 2 - Configuring Hosting​

Configuring hosting requires powershell so the steps are all based off of using it.

1. Create a subscription and assign sites to it:

$sub = new-spsitesubscription

$sub  

2. Pulling the site collection or set of site collections you wish to join to the site group:

​ get-spsite

$site = get-spsite | where {$_.url -eq "http://contoso"}

$site

​

​Now you have two variables.  Variable 1 $sub object contains a new spsitesubscription.  Variable 2 $site contains a site collection.

​3. Add  the site collection $site, to the newly created site subscription $sub.

set-spsite -identity $site -sitesubscription $sub

Check whether it has been added correctly by doing the following:

get-spsitesubscription

If a database ID exists, then you can type the following

get-spdatabase | where-object {$_.id -match "full or partial guid"}

Will output the results of the associated site collection.

​

4. Create a secondary subscription and associate a different site collection within same web application for demonstration purposes using the steps above.

5. Create a SubscriptionSettings Service Application and Proxy

​A.  Start the WSS Subscription Settings Service

B. Create Service Application and Proxy via PowerShell

$appPool  =  New-SPIISWebServiceApplicationPool -Name SettingsServiceApppool -Account domain\use

$sa = new-spsubscriptionsettingsserviceapplication –Name SubscriptionSettingsServiceApplication –Databasename SubscriptionSettingsServiceApplicationDB –applicationpool $appPool

$sap = new-SPSubscriptionSettingsSericeApplicationProxy –ServiceApplication $sa

6. Creating the Tenant Admin Site for each site group

​$sub = get-spsitesubscription –identity “http://server”

$tasite = new-spsite –url “http://test/sites/tasite1” –template “tenantadmin#0” –owneralias domain\username –sitesubscription $sub

7. Provision a search service application in hosting mode.  Please see the Configure Search Service application using Powershell blog.

8. Feature's and hosting

Once a feature has been installed into the farm, it's available to all sites and can be activated through manage features pages.  The way to control this in a hosting scenario is you only provide the features available to a given site group through various PowerShell commands.  Any features not listed are excluded and not available for all site collections that belong to the corresponding site group.  Steps are below:

Create a feature set: 

$fs =New-SPFeatureSet

Adding features to a feature set:  

​$farm = Get-SPFarm

$feature1 =$farm.FeatureDefinitions | where{$_.ID -eq "02464c6a-9d07-4f30-ba04-e9035cf54392"}

Add-SPFeatureSetMember -Identity $fs -FeatureDefinition $feature1

Adding feature set to subscription:

Set-SPSiteSubscriptionConfig -Identity $sub -FeatureSet $fs

SharePoint 2010 Multi-Tenant Hosting Part 1

Hosting 101 Part 1

​It's now simple to setup hosting on the site collection level.

For Example:

• Tenant "customer 1" on site collection 1 is hosted on web application A
• Tenant "customer 2" on site collection 2 is hosted on web application A

Each tenant would only have full administrator rights on his/her assigned site collection. Customer 2 and users accessing site collection 2 wouldn't be able to access Customer 1's site.

Also, service applications that are in hosting mode would keep each tenants data separate from another tenants. For example, one shared search service application could service customer 1\site collection 1's data and customer 2/site collection 2's data while keeping them separate from each other.

For Example: Users searching in site collection 1 will not be able to search and find content that resides in site collection 2. Users searching in site collection 2 will not be able to search and find content that resides in site collection 1. They will be able to search and locate data within the site collection they are searching from.

Site Groups

The segmentation is possible through the use of site groups also known as site subscriptions. In the example above, customer 1's site collection belongs to site group 1 and customer 2's site collection belongs to site group 2.

Things to know about site groups:

1. Sites can belong to only one site group at a time.

2. Sites cannot join a site group that contains sites that exists on a different web application.

3. A site group can span across more than one content database

4. No GUI interface for managing site groups. PowerShell is required to create/manage/remove site groups.

Tenant Admin Site

A hosted customer is referred to as a tenant. You can provision a tenant admin site which gives the tenant full administrator rights over the site collection. The tenant admin site can be used to create additional sites for example after self service site creation is enabled.

Service Applications and Hosting

Be default, a service application is consumed at the web application level. So all sites, under a web application would consume from the same service application and data would be shared. In hosting mode, a shared service application partitions data where every site group has its own partition. The partition isn't shared meaning other site groups wouldn't be able to see this data even though all sitegroups are using the same service application. Configuring hosted service applications may differ based on the type of service application that is being deployed.

For Example: Deploying a Shared search service application requires you to use PowerShell with addition of -partitioned switch

Features

It's also possible to deploy features in an "a la carte" manner to site groups. So one site group can have more features available than another. This is configurable from PowerShell.

Hosting Part 2 provides a step by step walk though using PowerShell

Office SharePoint Search Service hangs does not start

Hi All,
I have faced one strange problem i was restarting Office SharePoint Search Service on my farm environment and suddenly it got hanged it is showing me in starting state there is no stop,start or restart option in services.msc console. I have restarted my machine but still error was as it is.
I tried following command also

stsadm -o osearch -action start
stsadm -o osearch -action stop
net stop oSearch
net start oSearch
nothing was working for me it shows me operation time out as osearch service is in starting state.

I fixed it by
psconfig -cmd services -install
and configure SharePoint search again and it works for me.

warning: follow above instruction at your risk on production environment :)

Common Microsoft SharePoint Server 2010 Installation Issues and Resolutions

I've been following the SharePoint 2010 Forums and have noticed several common installation issues.  These issues and possible steps to resolve those issues are included here.

ISSUE #1:  when running the SharePoint 2010 Products Configuration Wizard you may experience the error:

Failed to create the configuration database.
An exception of type System.Security.Cryptography.CryptographicException was thrown.  Additional exception information: The data is invalid.

To resolve the issue you can perform the following steps:

Modify the ACL on the 14 directory under %commonprogramfiles\Microsoft Shared\Web Server Extensions.

1. Right-click on the folder %commonprogramfiles%\Microsoft Shared\Web Server Extensions\14, and then select the Security tab.
   
2. On the 14 Properties dialog under the Security tab, select Edit.
   
3. On the Permissions for 14 dialog click Add… and enter Network Service in the Enter the object names to select and then click OK.
   
4. On the Permissions for 14 dialog select Full Control under Permissions for NETWORK SERVICE and click OK.
   
5. On the 14  Properties dialog click OK.
   

NOTE

The previous steps are applicable only prior to running the SharePoint 2010 Products Configuration Wizard.  If you have run the SharePoint 2010 Products Configuration Wizard, follow the steps below:

1. Open an elevated Command Prompt and change directories to %commonprogramfiles%\Microsoft Shared\Web Server Extensions\14 and enter psconfig –cmd –configdb disconnect to disconnect from the current configuration database.
   
2. Open SQL Server Management Studio or SqlCmd and delete the existing configuration database.
   
3. Follow the previous steps to modify the ACL on the 14 directory and run the SharePoint 2010 Products Configuration Wizard to create and configure the server farm.
   

NOTE

In the event the steps above do not immediately resolve the issue, open the Registry Editor and  delete the "SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure\FarmAdmin" Registry key and then run the SharePoint 2010 Products Configuration Wizard.

ISSUE #2:  when running the SharePoint 2010 Products Configuration Wizard you may experience the error:

An exception of type Microsoft.Office.Server.UserProfiles.UserProfileException was thrown.  Additional exception information: Unrecognized attribute 'allowInsecureTransport'. Note that attribute names are case-sensitive. (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\WebClients\Profile\client.config line 56).

To resolve the issue you can perform the following steps:

Download and install KB976462 from http://support.microsoft.com/kb/976462 for Windows Server 2008 R2 or KB971831 from http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=KB971831&DownloadId=7285 for Windows Server 2008 and run the SharePoint 2010 Products Configuration Wizard.

ISSUE #3:  when running Setup.exe for Microsoft SharePoint Server 2010 you may experience the error:

Setup is unable to proceed due to the following error(s):
A system restart from a previous installation or update is pending. Restart your computer and run setup to continue.
For the list of pre-requisites needed to install the product please refer to:
http://go.microsoft.com/fwlink/?LinkId=106209
Correct the issue(s) listed above and re-run setup.

Check the value of the following Registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile - if the value of the UpdateExeVolatile Registry key is anything other than 0 you will see this message.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations - if the PendingFileRenameOperations Registry key has any value you will see this message.

To remove an orphaned UpdateExeVolatile registry key value

1. Open a registry editor, such as Regedit.exe or Regedt32.exe.
   
2. Navigate to HKLM\SOFTWARE\Microsoft\Updates\
   
3. In the right navigation pane, double-click the UpdateExeVolatile key.
   
4. Configure the key with a value of 0
   
5. Close Registry Editor.
   

To delete the orphaned PendingFileRenameOperations registry key

1. Open a registry editor, such as Regedit.exe or Regedt32.exe.
   
2. Navigate to HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\
   
3. In the right navigation pane, right-click the PendingFileRenameOperations key and select Delete.
   
4. Close Registry Editor.
   

ISSUE #4:  when running the SharePoint 2010 Products Configuration Wizard you may experience the error:

Failed to register SharePoint services.
An exception of type System.ServiceProcess.TimeoutException was thrown.  Additional exception information: Time out has expired and the operation has not been completed.
System.ServiceProcess.TimeoutException: Time out has expired and the operation has not been completed.
   at System.ServiceProcess.ServiceController.WaitForStatus(ServiceControllerStatus desiredStatus, TimeSpan timeout)

Run Setup.exe when the steps above have been completed.

To resolve the issue you can perform the following steps:

Download and install KB976462 from http://support.microsoft.com/kb/976462 for Windows Server 2008 R2 or KB971831 from http://code.msdn.microsoft.com/Project/Download/FileDownload.aspx?ProjectName=KB971831&DownloadId=7285 for Windows Server 2008 and run the SharePoint 2010 Products Configuration Wizard.

ISSUE #5:  when running the SharePoint 2010 Products Configuration Wizard you may experience the error:

Error: Cannot add the specified assembly to the global assembly cache: C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\policy\Policy.11.0.Microsoft.SharePoint.dll.

To resolve this issue you can perform the following steps:

Delete the contents of %commonprogramfiles%\Microsoft Shared\Web Server Extensions\14\policy\ and run the SharePoint 2010 Products Configuration Wizard.

ISSUE #6:  when running Setup.exe for Microsoft SharePoint Server 2010 you may experience the following error:

The language of this installation is not supported by your system

This issue is largely caused by corruption of the binaries, you can use the extract command in a Command Prompt and check the log to determine the health of the binaries; otherwise, download a new copy of the binaries and retry setup.

SharePoint 2010: Free End User Training

End-user/site admin training videos for SharePoint 2010. The training is completely free, and configured into a 9-module course at:

http://www.point8020.com/SharePointEndUserTraining.aspx

Each video is focused on one specific task in SharePoint 2010, so they are easily digested. The course is also displayed in the latest version of our Silverlight course-viewer, so the user-experience is engaging.