Archive for the ‘SharePoint 2010’ Category
Migrating from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 on a server running Windows Small Business Server 2008
!! Blog back in character !!
Follow the steps in this article to migrate your SharePoint websites from Windows SharePoint Services 3.0 to Microsoft SharePoint Foundation 2010 on a server running Windows® Small Business Server 2008.
Migration Steps – Overview
In this section lists the steps necessary to install SharePoint Foundation 2010 on a server running Windows Small Business Server 2008, and then to migrate your WSS 3.0 websites to SharePoint Foundation 2010. Follow the steps in the order listed to migrate successfully.
- Step 1: Install Windows SharePoint Services 3.0 Service Pack 2 (SP2)
- Step 2: Run the pre-upgrade checker for SharePoint Foundation 2010
- Step 3: Back up the existing data on your server
- Step 4: Back up the Windows Internal Database files
- Step 5: Uninstall Windows SharePoint Services 3.0 and edit the Registry
- Step 6: Install Microsoft SharePoint Foundation 2010 in Farm mode
- Step 7: Remove the default Web application in SharePoint Central Administration
- Step 8: Create a new SharePoint application in SharePoint Central Administration
- Step 9: Detach the Windows SharePoint Services 3.0 database from Windows Internal Database
- Step 10: Connect the ShareWebDb database to SQL Server 2008
- Step 11: Remove the existing content database
- Step 12: Connect the ShareWebDb content database
- Step 13: Recreate the original internal website environment
- Step 14: Install Windows Small Business Server 2008 Update Rollup 4
- Step 15: Edit the site bindings for the companyweb site
|File Name:||SBS_MigrateWSS30_to_SPF2010.doc (Size: 216 KB)|
Below is the list of Microsoft Project Server 2010 and Project 2010 demos. I guess this is the best and quick way to learn Microsoft Enterprise Project Management tools for our beginners.
Project 2010—Simple & Intuitive
Project 2010 offers easier and more intuitive experiences to help you select the right resources, collaborate with your team and meet crucial deadlines. Watch this demo to see how Project 2010 can help you effectively manage a wide range of projects and programs.
Project Server 2010—Unified Project and Portfolio Management
Project Server 2010, built on SharePoint Server 2010, delivers tailored work management solutions for individuals, teams, and the enterprise. Watch this demo to learn how Project Server 2010 can help your business deliver better performance.
User Controlled Scheduling and Project Professional 2010
Project Professional 2010 combines the flexibility and ease of Microsoft Excel with the power of the Project scheduling engine. Watch this demo to learn how user-controlled scheduling can help you create plans at any level of detail that’s right for your project.
Team Planner and Project Professional 2010
Whether you need to find a resource or change assigned tasks, the Team Planner View in Project Professional 2010 can help you quickly manage project work. Watch this demo to see how team planner uses simple click and drag to plan, move, or transfer resource assignments.
SharePoint 2010 and Project Professional 2010
Connect Project Professional 2010 with SharePoint Foundation 2010 or SharePoint Server 2010. Watch this demo to learn how the new Task List Synchronization provides a simple and easy-to-use project collaboration environment for project teams.
Finally after a long wait we have got a Recycle Bin for deleted Sites.
The SharePoint Site Recycle Bin is a SharePoint Foundation 2010 solution package that when deployed to a Microsoft SharePoint Foundation 2010 or Microsoft SharePoint Server 2010 server farm enables administrators to create a snapshot of subscriptions, site collections and Webs as they are deleted through the SharePoint user interface, the SharePoint Administration Tool, the SharePoint 2010 Management Shell, SharePoint 2010 Central Administration, or SharePoint Designer.
- Use the Setup and Configuration Guide to deploy the solution, once completed
- Create a Site under Site Collections
- Delete the Site which you created
- This will trigger the solution to create a bak file for the deleted Site in the storage area
- Now create a Blank Site to restore your lost or deleted Site.
- Use the Restore procedure for Sites
- Refresh your Blank Site page and Volla you have successfully restored your deleted Site.
The big question for me is to see how feasible will this solution be for Project Server 2010 Project Workspaces and will it be able to restore all Project Workspace data including Issues, Risks etc and then re-link to Project Schedule published in the Project Server.
This solution is available at Codeplex website
- WSP Soluition
SharePoint Site Recycle Bin (application, 37K)
SharePoint Site Recycle Bin Setup and Configuration Guide
Keep following the blog for more exciting stuff !
This tool is designed to make updates to the web.config files for your FBA web application, central admin, and the STS virtual directory to support FBA.
This post was originally posted at Share-n-dipity > SharePoint 2010 Forms Based Authentication Configuration Manager by speschka
Just downloaded it and going to have try :)
Take complete farm backup of your SharePoint,Its highly recommended by the author.
I am going to deploy this solution onto my test SharePoint HyperV environment and lets see how it goes.
How to configure instructions are included.
The MOSSRAP Scoping Tool verifies connectivity requirements, permissions requirements, and other prerequisites for successful execution of the MOSSRAP toolset. This is done by remotely querying the servers in the SharePoint farm. This information is required before proceeding with the request process.
The tool does NOT make any changes to the environment. It simply uses standard operations such as WMI queries, SQL queries, port queries and so on. It is completely read-only.
The tool is serial in nature and only attempts to perform a single check against a single server at a time. This means there should be relatively minimal network or target system overhead while the tool is running. This also means it may take it several minutes to complete depending upon the size of the farm.
Who should run this tool?
The scoping tool must be run using an account that has:
- Member of the local Administrators group on every SharePoint server in the farm
- Member of the local Administrators group on every SQL server in the farm
- Read permissions to every site in the farm (this can be granted via the web application policy in Central Administration)
- Full permissions to the Central Administration site and the personalisation services for each Shared Services Provider (SSP) in the farm.
- Member of the sysadmin role on every SQL instance used by the farm
What areas it report on?
The scoping tool runs through below areas to collect data and create report:
- Port 135 (Netbios) Check to ensure port 135 is not blocked by a firewall.
- Port 139 (Netbios) Check to ensure port 139 is not blocked by a firewall.
- Port 445 (Microsoft-DS) Check to ensure port 445 is not blocked by a firewall.
- Farm Topology The Farm Topology Check determines the topology and components within the SharePoint farm which will be used to run additional tests.
- Farm Admin The Farm Admin Check verifies that the current logged on user has rights to access the farm which is required during your Risk Assessment from the tools machine
- Metabase Access The Metabase check ensures that the IIS metabase can be queried remotely
- Ping During the Risk Assessment network access to all machines is required. This check attempts to ping the remote machines via the NetBIOS name.
- Remote Registry Access to the remote registry from the tools machine is required during your Risk Assessment. This check attempts to open the HKLM registry hive via the remote registry service.
- Admin Shares Access to administrative shares is required during your Risk Assessment from the tools machine. This check attempts to enumerate through the administrative shares by querying the Win32_Shares WMI class.
- Admin Access Access to the admin shares on the every server in the farm is required during your Risk Assessment.
- Query Logman Logman.exe is used during the Risk Assessment to collect performance counters from the tools machine. This check ensures Logman.exe works against remote machines by running ‘logman.exe /query /s [machine]’.
- Log Parser 2.2 Logparser.exe is used during the Risk Assessment to collect and display information. This check verifies that LogParser 2.2 is installed on the local machine.
- Windows Update Service Running This check verifies that the Windows Update service is running as required by the MBSA component during your Risk Assessment.
- Latest Version of Windows Update Agent Installed The Automatic Updates service is used to ensure consistent application of Security and Critical Updates.
- MBSA Installed Microsoft Baseline Security Assessment (MBSA) is used during the Risk Assessment to determine missing hotfixes. This check verifies that MBSA is installed on the local machine.
- SysAdmin on Databases Checks to verify that the current user is a sysadmin on the content database instances. This is required in order to run the SQL BPA.
- Server Service Running File and Print Services for Microsoft are required during your Risk Assessment for access to resources on the Servers and Nodes being checked. This check verifies that access to the Server Service is successful.
- OS Language (Tools) Determines if the installed operating system Language is English on the computer running the tool. Currently, the tools machine must run an English language Windows Server operating system. Target systems may be non-English OS.
- OS Locale (Tools) Determines if the installed operating system Locale is English (United States) on the computer running the tool. Currently, the tools machine must have Locale set as English (United States). Target systems may have non-English (United States) Locale.
- Correct .NET Libraries Installed .NET Framework version 3.5 SP1 must be installed to ensure Tools are able to perform properly.
- OS and SP Supportability Check Determines if the target operating system is supported or not. A RAP cannot be conducted against environments running unsupported products.
- Separate Tools Computer Verifies that the tools computer is not a member of the farm being evaluated.
- Loopback Check Security Feature Determines whether the loopback check security feature is enabled.
- OS and SP RAP Supportability Check Determines if the target operating system and service pack have been tested for compatibility with the RAP. A RAP can be conducted against untested environments; however the RAP content is not validated or ensured to be functional. The delivery should proceed at the risk of the customer.
Got my test SharePoint 2010 environment checked, surprised with the result 3 failure and 4 warnings not bad lol.
|File Name:||SPRAPScoping.zip (Size 334 KB)|
Well hello everyone, was browsing through PerformancePoint Dashboard Designer 2010 Help and found an excellent article on Scorecards and KPIs which actually help me to better understand the difference between a dashboard and a scorecard. As always wanted to share.
What is the difference between a dashboard and a scorecard?
Many people use the terms “dashboard” and “scorecard” interchangeably, but there is a significant difference between them. A scorecard is a type of report that displays a collection of key performance indicators (KPIs) together with performance targets for each KPI. A dashboard, on the other hand, is a container for a related group of scorecard and report views that are organized together in a SharePoint site. In other words, a dashboard contains a collection of other items such as scorecards, reports, and filters.
What are reports?
A report is the presentation of data transformed into formatted and organized information according to specific business requirements. Examples of the types of reports you can expect to see on a dashboard include analytic charts and grids, Excel Services reports, Web Page reports, and ProClarity Analytics reports. Reports can be simple static images or highly interactive displays of data. You can sort, filter, and drill up, down, or through data in some types of reports.
What is a scorecard?
A scorecard measures performance against goals. Typically, a scorecard displays graphic indicators that visually convey the overall success or failure of an organization in its efforts to achieve a particular goal. The scorecard is based on a collection of key performance indicators (KPIs), each of which represents an aspect of organizational performance. Taken together, these KPIs provide a snapshot of organization performance at a particular point in time. The following screenshot shows a typical scorecard.
What are KPIs?
A KPI is a metric that is tied to a target. The KPI usually represents how far away a metric is from its pre-determined target. The KPI score and its indicator are designed to let a business user know at a glance if results are on target or off target. For example, one commonly-used measure of retail success is same-store sales. If sales in a particular store increase each year, management views it as a solid performer. If the store performs less well than it did in previous years, management is likely to be concerned. A reasonable goal might be a 10% increase in sales each year for each store, and the KPI would be set accordingly.
What are indicators?
Indicators, sometimes called icons, are graphical elements that give visual cues about performance. Traffic light symbols are used—red to indicate a problem, yellow to indicate a potential concern, and green to show that performance is meeting or exceeding its goal. However, other types of indicators, such as check marks or smiley faces, are available, depending on the program that is used to create the scorecard.
What is a dashboard?
A dashboard is a container for various types of reports, including scorecards. It might consist of one or more pages, and it might have more than one module on each page. The modules are called Web Parts. A typical dashboard might contain a scorecard, an analytic report, and an analytic chart, but many variations are possible. Some dashboards provide users with a high level of interactivity, and others display static images. The degree and kind of interactivity depend on the program that is used to create the dashboard.
Each Web Part maintains a connection to its data source. The Web Parts can function independently of one another, or they can be linked together, so that what you click in one determines what you can see in the others. Together, the reports provide a clear picture of current organisation performance.
Hope it was a help article. Thanks to PerformancePoint Dashboard Designer Support site
This document provides you with the information that will help you:
- Understand the concepts of identity in SharePoint 2010 Products
- Learn how Kerberos authentication plays a critical role in authentication and delegation scenarios
- Identify the situations where Kerberos authentication should be leveraged or may be required in solution designs
- Configure Kerberos authentication end-to-end within your environment including scenarios which leverage various service applications in SharePoint Server
- Test and validate that Kerberos authentication is configured correctly and working as expected
- Find additional tools and resources to help you configure Kerberos authentication in your environment
This document is divided in two major sections:
- Overview of Kerberos Authentication In SharePoint 2010 Products
This section provides conceptual information about managing identity in SharePoint Products, the Kerberos protocol, and how Kerberos authentication plays a key role in SharePoint 2010 Solutions
- Step-By-Step Configuration
This section will walk you through the steps required to configure Kerberos authentication and delegation in various SharePoint solution scenarios.
|File Name:||SP2010 Kerberos Guide.docx (Size: 7.2 MB)|
The upgrade guide for Microsoft SharePoint Server 2010.
Personally I am very impressed with this document. This guide helps you plan for and perform an upgrade from Microsoft Office SharePoint Server 2007 to SharePoint Server 2010.
- About the upgrade process (SharePoint Server 2010) Learn about what’s new in upgrade and how the upgrade process works.
- Plan and prepare for upgrade (SharePoint Server 2010) Determine which approach you should take to upgrade to SharePoint Server 2010 and plan your upgrade process.
- Testing and troubleshooting upgrade (SharePoint Server 2010) Learn how to test your upgrade process ahead of time to understand what issues you might face in your actual upgrade, and determine the time and space you will need for upgrade. Also, learn how to troubleshoot issues that come up during the actual upgrade.
- Perform pre-upgrade steps (SharePoint Server 2010) Find out what steps you need to take before upgrading, including information about how to run the pre-upgrade checker.
- Perform an in-place upgrade (SharePoint Server 2010) Follow the steps in this section if you are upgrading in-place to SharePoint Server 2010. When you upgrade in-place, you install SharePoint Server 2010 on the same hardware, and then upgrade the content and settings on the server or server farm as part of a single process.
- Perform a database attach upgrade to SharePoint Server 2010 Follow the steps in this section if you are using the database attach upgrade method to upgrade to SharePoint Server 2010. When you use the database attach upgrade method, you upgrade the content for the environment on a separate farm.
- Perform post-upgrade steps (SharePoint Server 2010) Find out how to tell whether upgrade was completed successfully and what steps you need to perform after the upgrade to get your environment ready for users again.
|Download:||SharePtServUpgrade (3.5 MB)|
Other SharePoint Downloads:
Users lost with 2010 ribbon. Couldn’t find your buttons at the usual place.
Here is the solution I found at Microsoft site.
Interactive Project Ribbon Guide
You will require to rest the mouse pointer over a Project 2007 menu or button to learn its new location in Project 2010 isn’t that cool :) and this interactive thing will show exact command.
Select your command in Microsoft Project 2007 menu.
Interactive Project Ribbon guide will show you where to find the exact command in Microsoft Project 2010 menu.
and more you use it easy it becomes. Also there are complete Office 2010 ribbon reference workbooks downloadable with also SharePoint 2010.
Microsoft Project 2010 ribbon reference workbook: Download
Find the new locations of Project 2007 commands in Project 2010. This Excel workbook contains tables that list the old menu commands and show where in Project 2010 those commands are located.
SharePoint Server ribbon reference workbook: Download
Find the new locations of SharePoint Server 2007 commands in SharePoint Server 2010. The Excel workbook contains tables that list the old commands and show where in SharePoint Server 2010 those commands are located.
Excellent for user’s new to Microsoft 2010 products !!!
Attention SharePoint Administrators… There Is a Better Way to Back Up!
If your company relies on Microsoft Office SharePoint products and technologies to manage and deliver information, who will you trust to maximize its protection and recovery?
SharePoint administrators are looking for a better way to protect and recover their collaboration infrastructures. Microsoft has listened to its customers and has delivered a complete solution with System Center Data Protection Manager (DPM).
System Center Data Protection Manager delivers unified data protection for Windows servers and clients as a best-of-breed backup & recovery solution from Microsoft, for Windows environments. DPM 2010 provides the best protection and most supportable restore scenarios from disk, tape and cloud — in a scalable, manageable and cost-effective way.
You can protect SharePoint 2007 and WSS 3.0 today with DPM 2007 SP1. And as you get ready to deploy SharePoint 2010, DPM 2010 will be there and ready to protect that as well.
What is DPM 2010
Data Protection Manager (DPM) 2010 is part of the System Center family of management products from Microsoft. It delivers unified data protection for Windows servers such as SQL Server, Exchange, SharePoint, Virtualization and file servers — as well as Windows desktops and laptops.
- New in 2010 is the ability for roaming laptops to get centrally managed policies around desktop protection. Your laptop data will be protected whether you are connected to the corporate network or travelling on an airplane.
- DPM also provides native site-to-site replication for Disaster Recovery to either another DPM server or an off-site cloud provider.
- Centrally managed System State and Bare Metal Recovery are also new in DPM 2010.
What DPM 2010 got for SharePoint:
- SharePoint 2010 does not require a Recovery Farm, so happily – neither does DPM 2010 when restoring individual items.
- DPM 2010 has been enhanced for larger enterprises, such that a single DPM server can protect farms with over 25TB of data and over 1 Million items.
- DPM 2007 was aware of Farm topology changes, but required an administrator to approve including new content databases for protection. DPM 2010 adds automation to this by automatically protecting new databases when they are discovered.
- Protection for Office 14 Server, as well as the 2007 and 2003 SharePoint products and technologies
In addition, DPM 2010’s new AutoGrow feature ensures that as your farm grows, the DPM server will dynamically continue to protect it.
Download DPM 2010 datasheet: How to protect Microsoft SharePoint with Microsoft System Center Data Protection Manager 2010
|Version:||DPM 2010 RTM|