SharePoint Server 2010

Four Versions:
1. SharePoint Server 2010 Enterprise Client Access License features
For organizations looking to expand their business collaboration platform to enable advanced scenarios.
2. SharePoint Server 2010 for Internet Sites, Enterprise
For organizations looking to create customer-facing public internet sites and private extranets using the full enterprise capabilities of SharePoint.
3. SharePoint Server 2010 Standard Client Access License features
For organizations looking to deploy a business collaboration platform across all types of content
4. SharePoint Server 2010 for Internet Sites, Standard
For small and mid-sized organizations looking to create public Internet sites or basic extranets using the Standard features of SharePoint Server 2010.

Capability Areas:
1. Sites
• SharePoint Ribbon user interface
• Easy Web editing
• Cross-browser support and improved mobile experience
• SharePoint Workspace 2010
• Office Web Applications
• Personalization
• Standards and Accessibility
2. Communities
• My Sites
• Social feedback
• Wikis
• Blogs
3. Search
4. Content
• Document management
• Records management
• Rich media management
• Web content management
5. Insights
6. Composites

.....To Be Continued

References:

1. Migration
http://www.sharepointproconnections.com/article/sharepoint-server-2010/Migrating-to-SharePoint-2010-104619.aspx
2. http://sharepointgeorge.com/2009/upgrading-content-database-sharepoint-2010-database-attach-method/

Errors/Issues:
1. CabLib Compress ERROR: Could not flush cabinet: Could not create cabinet file [Happens after when u upgraded and deploying the web parts]
Solution: If you encounter this error when building a WSP it could mean that your files are read-only. Most source control tools mark files as read-only when a file is checked in. Either use the source controls tool to make the file writeable or right-click the file (or root folder) select Properties and uncheck Read-Only.
2. Content Database Attach Upgrade Fails
Solution: We cannot have same database content in two databases with different names.
Reason: Same Site It cannot be in two different places.
3. Creating a new web application fails and doesn't give confirmation message.
Solution: Happens when you are trying to create sites on the ports which u used earlier/deleted and application pools still exist for that port.
Delete unused application pools and if problem still persists restart the server (or) create on a new port.
4. Found 1 web(s) using missing web template 75816 (lcid: 1033) in ContentDatabase.
Solution: http://www.microsoft.com/downloads/details.aspx?FamilyId=C1039E13-94DA-4D7D-8CAE-3B96FA5A4045&displaylang=en
http://www.microsoft.com/downloads/details.aspx?FamilyId=CE90D6D7-7B96-47BF-A22F-A7E8C5D40647&displaylang=en
Install.
5. Twitter SharePoint web part
Solution: This can be downloaded from http://www.aidangarnish.net/blog/post/2009/02/Twitter-SharePoint-web-part.aspx
Install the webpart using following steps:
stsadm -o addsolution -filename \Nameofwsp.wsp
You can either use Central Administration > Manage Farm Solutions>Deploy Solution to deploy the solution or use following command:
stsadm -o deploysolution -name Nameofwsp.wsp -allowgacdeployment
(Additional attributes may be required based on your Windows SharePoint Services configuration. For example:
Single Server: [ -local | -time ]
Farm: [ -immediate | -time ]
To see the list of attributes, run stsadm -help deploysolution)
6. Corelation ID: Error Guid after we upgrade to Moss 2010
Solution: Go to /14/Logs Folder and open the last text document and search for that GUID.
It will give some explanation regarding the error.
7. http://www.amrein.com/apps/page.asp?Q=5784
Solution: http://www.amrein.com/apps/page.asp?Q=5784
Install for 2010 and add in web.config or deploy from Central Administration
8. The server instance specified was not found. Please specify the server's address and port...while attaching the db to sharepoint site using stasm -o addcontentdb -url [url] -databasename [dbname]
Solution: While Creating the sharepoint application, create with FQDN.
9. HelpDesk.wsp
Solution: http://technet.microsoft.com/en-us/windowsserver/sharepoint/bb407286.aspx
Download Helpdesk.
a.Before installing a server admin template, you must first install the Application Template Core solution, ApplicationTemplateCore.wsp. (Click here to download). If you have already installed this solution, proceed to Step b.
Via command line, run stsadm -o addsolution -filename <file_path>\ApplicationTemplateCore.wsp
Next, run stsadm -o deploysolution -name ApplicationTemplateCore.wsp -allowgacdeployment -local
Finally, run stsadm -o copyappbincontent
b. Pull the solution file, <template_name>.wsp, from the extracted distribution. The solution file will also be added to the solution store.
Via command line, run stsadm -o addsolution -filename <file_path>\<template_name>.wsp
Next, run stsadm -o deploysolution -name <template_name>.wsp -allowgacdeployment -local