SharePoint 2010 RTM in April 2010

Sunday, March 7, 2010

As the Microsoft Office product development group announced on their blog, that starting today if you purchase and activate Office 2007 you will be able to download Office 2010 at no additional cost when it becomes available in June 2010. 

In addition to the Office 2010 Technology Guarantee, were excited to confirm that Office 2010, SharePoint 2010, Visio 2010 and Project 2010 are on schedule and will release to manufacturing (RTM) next month.

May 12, Microsoft is launching the next wave of productivity. TIl then, go and Get Office for Today or Tomorrow.

Go to http://sharepoint.microsoft.com/2010launch to join the launch and share your thoughts.

Upgrade

Upgrading from SharePoint 2010 Beta to RTM is not supported.  SharePoint Technical Program Manager Jie Li points out in this MSDN Forum post Upgrading SharePoint 2010 from Beta 2 to RC or RTM:

Upgrade from SharePoint Server Public Beta to RTM (in-place, or database attach) for general public will be blocked. For exceptions, we will support those who hold a "Go Live" license, they were clearly communicated, signed a contract, and should know their upgrade process would be supported by CSS.

If you need to know how to install SharePoint 2010, then either Download SharePoint 2010 Beta 2 Virtual Machine or SharePoint 2010 Beta Installation Roundup.

SharePoint manifest error

Thursday, February 11, 2010

Today I had the following error (in an english SharePoint farm with dutch language pack) when I clicked the help icon in SharePoint:

“HC niet gevonden. (MS.OSS.manifest , 1043)” (in English: HC not found … )

After some searching I found that I had to check the HelpFold in the Central Administration site. In the Content folder (<CAsite>/HelpFold/Forms/AllItems.aspx) there was no 1043 folder so the help text couldn’t be found. To solve this follow these steps:

1.Click Start, click Run, type cmd, and then click OK.
2.At the command prompt, type the following command, and then press ENTER:
cd %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\BIN
3.At the command prompt, type the following command, and then press ENTER:
Hcinstal.exe /act InstallAllHCs

Read more: http://www.information-worker.nl/2008/11/20/sharepoint-manifest-error/#ixzz0fDa6fRp6

SQL Server 2008 Evaluation Edition Expiration Problem

Wednesday, February 10, 2010
 

With SQL Server 2008 passing its 6 months since RTM date, a common problem is popping up in the forums and is now listed on Connect.  When an install of Evaluation Edition Expires, the services stop functioning until an upgrade is made to a full version of SQL Server 2008.  This is normal.  The problem is that during the Edition Upgrade, SQL Server Management Studio is not upgraded, and a persistent popup will occur stating that the evaluation version has expired.

image

There is currently a workaround that can be done to resolve this problem.  Open RegEdit and change the value of the CommonFiles REG_DWORD under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\100\ConfigurationState registry from 1 to 3 and then rerun the Edition Upgrade.  This will allow the Upgrade to Management Studio to complete properly.

image

Microsoft Forefront Protection 2010 for SharePoint RC is Available

Monday, February 8, 2010

Microsoft Forefront Protection 2010 for SharePoint prevents users from uploading or downloading documents containing malware, out-policy content, or sensitive information to SharePoint libraries.

System Requirements
  • Supported Operating Systems: Windows Server 2003; Windows Server 2008; Windows Server 2008 R2

Forefront Protection 2010 for SharePoint* minimum server requirements
Important: Due to a difference in system resources, FPSP performs significantly better on a 64-bit operating system (OS) than on a 32-bit OS. If your organization expects to have large capacity requirements on SharePoint server, it is recommended that you install the 64-bit OS and a 64-bit SharePoint front-end server before installing FPSP.
  • Microsoft Windows Server 2003 SP2 (Standard, Enterprise, Datacenter, or Web Edition), Microsoft Windows Server 2008, or Microsoft Windows Server 2008 R2.
  • Microsoft .NET Framework 3.5.
  • Microsoft XML Core Services (MSXML) 6.0 SP1.
  • Internet Information Services (IIS) in IIS 6.0 worker process isolation mode.
  • Microsoft Chart Controls for Microsoft .NET Framework 3.5. If these controls are not already present, they will be installed during the FPSP installation process.
  • Windows PowerShell 1.0.
  • NTFS file system.
  • Microsoft Office SharePoint Server 2010, Microsoft Office SharePoint Server 2007 SP1, or Microsoft SharePoint Foundation version 3 SP1.
  • Microsoft Filter Pack 2.0
  • 2 gigabytes (GB) of free memory** in addition to that required to run SharePoint server. For more information about the memory requirements for running SharePoint server, consult your SharePoint server planning documentation.
  • 2 GB of available disk space. This is in addition to the disk space required for SharePoint server. Utilizing a server as a redistribution server for updates requires additional disk space.
  • A four core server with 2.0 GHz or higher processors is recommended. Lower performing servers are supported, but file latency times may increase.


* If both the Exchange and SharePoint products are installed on the same server, only Forefront for Exchange Server can be installed, to protect Exchange.
** Less memory is required if Intelligent Engine Management (IEM) is not enabled and fewer than 5 engines are selected (approximately 250 MB of memory per engine).

Forefront Protection 2010 for SharePoint Release Candidate (RC) is available for download here.

SharePoint 2010 Content Free Training & VPC from MSDN

Saturday, January 30, 2010

- 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

clip_image002

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.

clip_image004

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.

clip_image006

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

clip_image008

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.

clip_image010

- Then I have chosen for the Search Service Proxy.

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

clip_image012

- 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

clip_image014

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

clip_image016

- 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

- clip_image018

- Finish. Its Easy!!

Download SharePoint 2010 Beta 2 Virtual Machine

Wednesday, January 27, 2010

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.