There are four versions of SharePoint Server 2010 as specified in following URL :
http://technet.microsoft.com/en-us/evalcenter/ee388573.aspx
SharePoint Server 2010 Enterprise Client Access License features
For organizations looking to expand their business collaboration platform to enable advanced scenarios. Use the Enterprise capabilities of SharePoint to fully interoperate with external line-of-business applications, Web services, and Microsoft Office client applications; make better decisions with rich data visualization, dashboards, and advanced analytics; and build robust forms and workflow-based solutions.
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. This provides full SharePoint Enterprise functionality and no other technical limits.
SharePoint Server 2010 Standard Client Access License features
For organizations looking to deploy a business collaboration platform across all types of content. Use the core capabilities of SharePoint to manage content and business processes, find and share information and expertise, and simplify how people work together across organizational boundaries.
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.
Friday, May 14, 2010
SharePoint 2010 Product key
Here goes product keys for SharePoint 2010 Release Version:
SharePoint Server 2010 Enterprise Client Access License Features: GGDG8-JCMXH-8KG8C-RJYYX-3Y33H
SharePoint Server 2010 for Internet Sites, Enterprise: 9FPGB-W6QTT-G68T4-TBX7M-R624H
SharePoint Server 2010 Standard Client Access License Features: KB443-F7CJV-J2RP4-QYQJ7-6PBB3
SharePoint Server 2010 for Internet Sites, Standard: H4P2T-CYKM7-9FKKD-DTQ7X-W69GG
http://technet.microsoft.com/en-us/evalcenter/ee391660.aspx
HAPPY SHAREPOINTING!!!!
SharePoint Server 2010 Enterprise Client Access License Features: GGDG8-JCMXH-8KG8C-RJYYX-3Y33H
SharePoint Server 2010 for Internet Sites, Enterprise: 9FPGB-W6QTT-G68T4-TBX7M-R624H
SharePoint Server 2010 Standard Client Access License Features: KB443-F7CJV-J2RP4-QYQJ7-6PBB3
SharePoint Server 2010 for Internet Sites, Standard: H4P2T-CYKM7-9FKKD-DTQ7X-W69GG
http://technet.microsoft.com/en-us/evalcenter/ee391660.aspx
HAPPY SHAREPOINTING!!!!
Tuesday, May 04, 2010
Retrieve Solution file from SharePoint Farm
Situation :
Developer created .wsp file and installed in SharePoint farm . We need install these solution files to new farm and we have no clue where developer has saved these files.It's not in Visual Source safe too.
Disaster Recovery :
Pull the .wsp from the existing farm using code below :
SPSolutionCollection solutions = SPFarm.Local.Solutions;
foreach (SPSolution solution in solutions)
{
SPPersistedFile wspFile = solution.SolutionFile;
wspFile.SaveAs("c:\\Temp\\Solutions\\" + solution.Name);
}
Make sure directory exists .
Enjoy!
Developer created .wsp file and installed in SharePoint farm . We need install these solution files to new farm and we have no clue where developer has saved these files.It's not in Visual Source safe too.
Disaster Recovery :
Pull the .wsp from the existing farm using code below :
SPSolutionCollection solutions = SPFarm.Local.Solutions;
foreach (SPSolution solution in solutions)
{
SPPersistedFile wspFile = solution.SolutionFile;
wspFile.SaveAs("c:\\Temp\\Solutions\\" + solution.Name);
}
Make sure directory exists .
Enjoy!
Subscribe to:
Posts (Atom)
Gray Failures: What is it and how to detect one?
If you are reading this article , i guess you are curious to know about gray failures and different methods to detect gray failures. Hopefu...
-
Note : In below scenario jenkins was deployed in Linux container Scenario: Jenkins build failed with error. java.io.IOException: error...
-
SharePoint Capacity Planning Tool on Microsoft Download Center: http://go.microsoft.com/fwlink/?LinkID=93029 System Center Capacity Planner:...
-
Simple concept but still pain in head if unable to figure out :) Response.Redirect("#");