Skip to main content

Published intranets in SharePoint Server 2010

A published intranet site is a site that is internal to an organization and uses the publishing features in Microsoft SharePoint Server 2010 to host content for the entire organization. This is usually the main communications site or portal for the organization. Typically, such a site is not available to external users. The site is usually branded and is not a collaboration mechanism, but rather a place to consolidate information that needs to be widely shared with the whole organization.

Get started

Task Map

Click this image to zoom into the Published Intranet task map in full detail with Zoom.it from Microsoft

This task map gives an overview of the tasks you must perform to set up a published intranet site in your organization.

The map is a visual representation of the tasks for each phase of the deployment life cycle. For detailed information, see the Tasks section on this page.

Download | Zoom

 

Key Features and Assumptions

For this solution, the following features are used heavily:

  • Publishing
  • Content approval workflow
  • Branding
  • Custom Web Parts
  • Audiences
  • RSS feeds

For this solution, we made the following assumptions:

Content is managed and must be approved
An editorial team sets the structure, standards, and schedule for content and approves content before it is published.

Content deployment is not required
This solution has a combined authoring and publishing environment and does not need content deployment.

Collaboration sites are not included
Collaboration sites have a different content structure and permission model. Search is used to index and expose content from related collaboration sites.

Tasks

Follow these tasks in the order they are presented to create and operate a published intranet site for your organization.

Evaluate | Plan | Develop | Deploy | Operate

The following downloads are available:

1. Evaluate

This section suggests some typical steps to take during the evaluation phase before a project is planned. An organization might use different steps or perform steps in a different order to meet its unique needs.

1.1 Evaluate organization needs
1.2 Evaluate software capabilities
1.3 Review requirements
1.4 Exit criteria
 

In this step, you determine your high-level needs for an intranet site. Include both technical decision makers and business decision makers in this process. Do not plan your specific implementation, but instead take time to identify requirements and constraints.


1.1.1 Identify business goals
In this step, you work with a project team to define the business goals for the project.  If you don't have an established process for how to envision your project, you can follow the steps in the Microsoft Operations Framework.
Related content: Microsoft Operations Framework 4.0 - Envision Service Management Function

1.1.2 Determine availability, capacity, and performance requirements
Do you have hours in which downtime might be acceptable? How many users are you serving with this site? Do you have any performance benchmarks you need to hit?
Related content: Reliability Service Management Function Process 1: Planning

1.1.3 Identify functional requirements
What specific business and functional requirements need to be met for your intranet site? For example, does the site need to be accessible to users around the world? Will different departments have their own sites or will there be only a central Intranet site?

1.1.4 Determine operations criteria
Are there specific requirements or restraints for operations for your intranet site? For example, are there any physical infrastructure constraints on your environment?

1.1.5 Identify staff and resource constraints
What specific resource constraints will need to be taken into account during planning? For example, do you have a team that includes developers and designers, or will you need to hire employees or consultants to do some of the work?

2. Plan

2.1 Train IT and development staff
2.2 Determine key vision or identity for the site
2.3 Plan information architecture
2.4 Define implementation-wide requirements
2.5 Define content requirements
2.6 Plan site structure
2.7 Define page structure
2.8 Plan style design
2.9 Plan custom development and extensibility
2.10 Plan for browsing and search
2.11 Plan solution architecture
2.12 Plan integration with related solutions
2.13 Create project plan for overall effort
2.14 Verify that site design complies with governance plan and meets organization needs
2.15 Create training plan and gather training materials and resources
2.16 Order hardware
2.17 Exit criteria
 

Before you begin your project, make sure your IT and development staff members are fully trained to use SharePoint Server 2010. Training videos and labs are available on TechNet and MSDN.
Related content:

3. Develop

3.1 Review application lifecycle management (ALM) best practices
3.2 Create proof of concept
3.3 Create custom connectors
3.4 Develop customizations to global layout
3.5 Create publishing page layout
3.6 Test browser support
3.7 Create custom navigation
3.8 Develop custom Web Parts and forms
3.9 Create custom search experience
3.10 Create custom site templates
3.11 Optimize code performance, Validate Solution and fix bugs
3.12 Create strings for multiple locales
3.13 Create the solution package
3.14 Create operations plan and train operations staff
3.15 Exit criteria
 

Plan and implement an application lifecycle management (ALM) process that integrates the SharePoint Server 2010 development tools and capabilities with the specific requirements and needs of your project.
Related content:

4. Deploy

Follow the steps in this section to deploy your published intranet to both test and production environments.

4.1 Run and test a pilot solution
4.2 Prepare the servers
4.3 Deploy the published intranet solution
4.4 Create metadata
4.5 Train content authors and content approvers
4.6 Author and import content
4.7 Grant permissions to site visitors
4.8 Configure monitoring options
4.9 Perform operational maintenance tasks
4.10 Set up and configure regional farms
4.11 Roll out the site
4.12 Exit criteria
 

As a best practice, create a pilot project and test your published intranet solution with representative users to ensure that it works the way you want it to. Then, make any adjustments before deploying to your production environment.
Related content: Process 2: Conduct a Pilot Test

5. Operate

5.1 Farm administrator operations
5.2 Content and site owner operations
5.3 Author and approver operations
5.4 Site visitor operations
 

In this section, you manage your farm to keep all services, servers, and sites running effectively.
Related content: Server and server farm operations


5.1.1 Monitor and tune server farm performance
Keep your servers running in a healthy state, and ensure that your sites are handling requests efficiently.
Related content: Health monitoring

5.1.2 Manage business continuity
Put your backup and restore plans into action and ensure that your farm is available when needed.
Related content:

5.1.3 Install software updates
Keep your servers and sites running well by installing the latest software updates for SharePoint Server 2010, your operating system, SQL Server, and any other software running on your farm. These updates contain important product enhancements and improvements.
Related content: Deploy software updates for SharePoint Server 2010

5.1.4 Update search terms
Evaluate your search terms – are users' searches returning the best results? What can you do to tune the results? Web analytics reports can also help you understand what is working well and what is not.
Related content:

5.1.5 Maintain services
Follow the provided checklists or create your own checklists to manage and maintain your servers and services.
Related content: SharePoint Server 2010 Operations Framework and Checklists (white paper)

Join us: Follow us on Twitter Twitter