During the installation of SP2, a product expiration date is improperly activated. This means SharePoint will expire as though it was a trial installation 180 days after SP2 is deployed. The activation of the expiration date will not affect the normal function of SharePoint up until the expiration date passes. Furthermore, product expiration 180 days after SP2 installation will not affect customer’s data, configuration or application code but will render SharePoint inaccessible for end-users.
Microsoft working to release a hotfix to automatically fix this issue. A manual work-around is currently available and involves customers re-entering their Product ID number (PID) on the Convert License Type page in Central Administration. For more information and detailed steps please read this KB article. (The KB link is not currently active, it will be available within the next 48hrs)
original article: Attention: Important Information on Service Pack 2
Microsoft SharePoint Product Group announce (and confirm) some preliminary system requirements for SharePoint Server 2010 in Announcing SharePoint Server 2010 Preliminary System Requirements
main points of this announce are
server requirements
- SharePoint Server 2010 will be 64-bit only.
- SharePoint Server 2010 will require 64-bit Windows Server 2008 or 64-bit Windows Server 2008 R2.
- SharePoint Server 2010 will require 64-bit SQL Server 2008 or 64-bit SQL Server 2005.
client requirements
- Internet Explorer 7, Internet Explorer 8 and Firefox 3.x.
what can you do today to get into the best shape for SharePoint Server 2010
SharePoint Central Administration: High Availability, Load Balancing, Security & General Recommendations
Running Central Administration on more than one server in the farm is 100% supported, and indeed a recommended best practice.
Load Balancing Central Administration is 100% supported. And even if it wasn’t it wouldn’t matter as you can simply take load balancing out of the equation and hit one of the machines directly.
Implementing Kerberos Authentication for load balanced Central Administration is 100% supported.
Implementing Central Administration on Port 80 or 443 is 100% supported.
Vedant Kulshreshtha about FAST ESP:
FAST and SharePoint 2007
For some time, I have been working on pre-sales engagements for FAST search based solutions. I get lot of queries from SharePoint developers/architects – what is “FAST” and how it works with SharePoint etc. I am sharing some information below. The links Read More…
FAST ESP: The Product and its Roadmap
This is the first post from a planned series on the FAST ESP platform to increase product awareness in the SharePoint community. This post builds on the basic FAST information I shared in my blog post – “ FAST and SharePoint 2007 ” last month. Target Read More…
FAST ESP: Architecture
FAST ESP is built on a distributed system architecture that enables any type of information to be accessed through core search and filter engines. Incoming content is fed through a number of processors that automatically extract information, generate Read More…
FAST ESP: Feature Snapshot
FAST ESP is a feature rich search platform; no doubt about that. To give my readers, especially SharePoint 2007 developers/architects, an idea of what it provides, given below are some of FAST ESP features in an alphabetical order: Capability Description Read More…
FAST ESP: Linguistics Processing Features
FAST ESP performs linguistic processing: at the document level – during document processing, and at the query level – during query and result processing This helps it provide more relevant search results to users. On the query side, linguistic processing Read More…
FAST ESP: How Relevancy works?
Relevancy is the measure of how well a set of documents (results) answers or addresses the intent of a given query. When there are many query matches, the search engines must rank the results by relevance score, sorting the results listing so that the Read More…
FAST ESP: Different ways to retrieve Content
Content retrieval is done very differently in FAST then in SharePoint 2007. FAST ESP may retrieve content from the data sources using two broad approaches: 1) Content Pull : this approach leverages content connectors to retrieve the information via standard Read More…
SharePoint Content and Resources announced SharePoint SDK 1.5 (April 2009) Released!
The April 2009 (1.5) Update is available both online and as a download.
What’s New in this release?
The SDK updates in 1.5 include: