Answer:

Step 1: Install Windows Server 2008 R2 (with or without SP1) 180 days trail software.

Step 2: After a successful installation, when “Configure your Server” windows opens, click on Activate Windows or open Windows Activation.

Step 3: At the “Enter the Product Key” leave the Product Key field blank and click ‘Next’.

Step 4: Click Yes on the Confirmation Dialog box. The wizard connects to the Windows Activation service and shows “Activation was successful” messege as shown below:

The Office Professional Plus subscription allows customers to purchase monthly licenses for each of their users. Each user license allows five concurrent installations. Both 32- and 64-bit versions of Office Professional Plus are available in Office 365. However, Microsoft recommends that you install the 32-bit version. You download and manage Office Professional Plus for Office 365 from the Office 365 portal. After you download Office Professional Plus for Office 365, you can make the Office suite available to users in your organization, based on the number of user licenses that you sign up for.

Office Professional Plus for Office 365 and volume licensed product comparison

Office Professional Plus components and interactions

Office Professional Plus for Office 365 includes new activation technology that enables a monthly subscription model. Every month, Office Professional Plus automatically verifies the status of a user’s subscription. The validation process requires Internet access.

• If a user has a valid subscription, Office Professional Plus is activated for another 30 days.
  

• If the user’s subscription cannot be verified, Office Professional Plus enters a 30 day grace period.

During the 30 day grace period, Office Professional Plus tries to verify a user’s subscription every 24 hours. If, by the end of the 30 grace period, Office Professional Plus still has not been able to verify the status of a user’s subscription, Office Professional Plus will enter Reduced Functionality Mode (RFM)

Activation Components and Process

Office Professional Plus for Office 365 includes activation components that automatically obtain a product key and activate it. Office Professional Plus includes the following client components and services:

• Office Professional Plus client suite
  
• Subscription activation components:
  
  • Office Subscription Agent
    
  • OSA Notifier
    
  • Office Software Protection Platform (OSPP)
    
  • Office Subscription Service (OSS)
    

Office Professional Plus for Office 365 also uses Microsoft Office 365 Desktop Setup, an additional component that is downloaded from the Office 365 Portal. Microsoft Office Desktop Setup is an installer service that checks for and provides important software updates for Office 365.

Subscription activation components

Office Subscription Agent (OSA) is part of the Office Professional Plus for Office 365 download. OSA manages the client-side subscription experience and performs the following tasks:

• Completes initial subscription provisioning.
  
• Interacts with the Office Subscription Service that is described later in this article and the Office Software Protection Platform to manage subscription status and license state, and provides state messages to the subscription notification applications.
  
• Manages all licensing actions by using the Office Software Protection Platform.
  

Office Subscription Agent coordinates with Office Subscription Service and Office Software Protection Platform to apply business rules on the client computer for activation, renewal, deprovision, and reprovision of user subscriptions. OSA also notifies users about important subscription states and prompts for any input required for user account validation.

Office Subscription Agent includes two components:

• OSA core service: runs on the client computer as a network service. This service enforces business rules for the user subscription.
  
• OSA Notifier: runs in user context, notifies users about error conditions, and authenticates the user ID account. The OSA Notifier uses Microsoft Identity Client Runtime Library (IDCRL), a dynamic link library (DLL) file that is used by applications such as smart clients to authenticate user ID credentials.
  

Office also uses Office Software Protection Platform (osppsvc), which is a system service on the client that brokers the license state for installed Office software.

Office Subscription Service is a cloud-based service that manages subscriptions, users, and computers for use with Office Subscription Agent. In addition to interfacing with OSA, OSS obtains computer-specific product keys from the Sell keys service and manages Time Based Licensing parameters through the Activation Verification System (AVS), an Office Software Protection Platform system that manages activation licenses that are based on Time Based Licensing (TBL) parameters set by OSS.

There are four Office license states:

Activation process

Office Professional Plus for Office 365 offers a pay-as-you-go, per user licensing model. When a user’s Office Professional Plus subscription is canceled, Office enters reduced-functionality mode (RFM or read-only mode). In contrast to the traditional Office 2010 client activation, which requires that the user enter the 25 character product key, Office Professional Plus for Office 365 includes Office Subscription Agent. It is an add-on component that automatically obtains a product key and activates it. The user only has to enter a user ID and password one time to validate the subscription. A user can have up to 5 concurrent installations by using the same user ID and password.

OSA is installed during the Office Professional Plus for Office 365 installation. OSA is the mechanism through which Office Professional Plus full functionality is enabled or disabled, depending on the status of the user’s subscription. When installation is complete, the OSA system service and the OSA Notifier are started. These two processes are necessary for the correct functioning of an Office Professional Plus for Office 365 subscription.

The following graphic shows how OSA takes a user ID and password as input, contacts OSS to retrieve a 30-day product key, and then loads the key into OSPP. The key only licenses Office for 30 days. OSA contacts OSS once every 30 days to revalidate the subscription and extend the license period for an additional 30 days.

To verify the licensing state of the Office 365 clients, the clients must have reliable Internet access every 30 days.

SCCM 2007 HOL

• Driver support: Linux Integration Services supports the network controller and the IDE and SCSI storage controllers that were developed specifically for Hyper-V.
• Fastpath Boot Support for Hyper-V: Boot devices now take advantage of the block Virtualization Service Client (VSC) to provide enhanced performance.
• Timesync: The clock inside the virtual machine will remain synchronized with the clock on the virtualization server with the help of the pluggable time source device.
• Integrated Shutdown: Virtual machines running Linux can be shut down from either Hyper-V Manager or System Center Virtual Machine Manager by using the “Shut Down” command.
• Symmetric Multi-Processing (SMP) Support: Supported Linux distributions can use up to 4 virtual processors (VP) per virtual
  machine.

 Note -SMP support is not available for 32-bit Linux guest operating systems running on Windows Server 2008 Hyper-V or Microsoft Hyper-V Server 2008.

• Heartbeat: Allows the virtualization server to detect whether the virtual machine is running and responsive.
• KVP (Key Value Pair) Exchange: Information about the running Linux virtual machine can be obtained by using the Key Value
  Pair exchange functionality on the Windows Server 2008 virtualization server.

Supported Guest Operating Systems

This version of Linux Integration Services supports the following guest operating systems and virtual CPU (vCPU) configurations:

• Red Hat Enterprise Linux 6.0 and 6.1 x86 and x64 (Up to 4 vCPU)
• CentOS 6.0 x86 and x64 (Up to 4 vCPU)

Other supported operating systems (including SUSE Linux Enterprise Server 10 and Red Hat Enterprise Linux 5) should use the version of
Linux Integration Services available at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=eee39325-898b-4522-9b4cf4b5b9b64551

How to Install Linux Integration Services Version 3.1 on Red Hat Enterprise Linux 6

To install Linux Integration Services Version 3.1:

1. Open Hyper-V Manager: Click Start, point to Administrative Tools, and then click Hyper-V Manager.
2. Create a new virtual machine where you will install Linux: In the Actions menu, click New, and then click Virtual Machine.
3. Specify the Linux installation media:
   Right-click the virtual machine that you created, and then click Settings. In IDE Controller, specify one of the following:
1. An image file in ISO format that contains the files required for installation
2. A physical CD/DVD drive that contains the installation media
4. Turn on the virtual machine: Right-click the virtual machine that you created, and then click Connect.
1. Begin installing Linux.
2. When prompted, restart the virtual machine and complete any first-boot configuration tasks.

Note: Unless a legacy network adapter was added during the virtual machine’s initial configuration, the virtual machine will not have any network support.

1. Log on to the virtual machine.
2. In Hyper-V Manager, configure LinuxIC v30.ISO (located in the directory where you extracted the downloaded files) as a physical CD/DVD drive on the virtual machine.
3. As the root user, mount the CD in the virtual machine by issuing the following command at a shell prompt:

# mount /dev/cdrom /media

4. As the root user, run the following command to install the synthetic drivers. A reboot is required after installation.

For 32-bit versions:

 # rpm –ivh /media/x86/kmod-microsoft-hyper-v-rhel6-60.1.i686.rpm

# rpm –ivh /media/x86/microsoft-hyper-v-rhel6-60.1.i686.rpm

# reboot

 For 64-bit versions:

 # rpm –ivh /media/x86_64/kmod-microsoft-hyper-v-rhel6-60.1.x86_64.rpm

# rpm –ivh /media/x86_64/microsoft-hyper-v-rhel6-60.1.x86_64.rpm

# reboot

Verifying Linux Integration Services Version 3.1 Functionality

Linux Integration Services provides support for the modinfo command. To get module information for each installed kernel module, run
the following command:

# /sbin/modinfo hv_vmbus

filename: /lib/modules/2.6.32-71.el6.i686/extra/hv_vmbus.ko

version: 3.1

license: GPL

srcversion: 56F00728DAE99444BE1FD9B

alias: acpi*:VMBus:*

alias: acpi*:VMBUS:*

depends:

vermagic: 2.6.32-71.el6.i686 SMP mod_unload modversions 686

parm: vmbus_loglevel:int

This command can be repeated for all kernel modules (hv_vmbus, hv_netvsc, hv_storvsc, hv_blkvsc, and hv_utils).

To verify that all subcomponents are running,, as the root user, issue the following command at a shell prompt:

# /sbin/lsmod | grep hv

The output should include lines similar to the following example:

hv_utils 4747 0

hv_netvsc 57832 0

hv_timesource 0 [permanent]

hv_storvsc 50288 0

hv_blkvsc 54032 3

hv_vmbus 70120 3
hv_netvsc,hv_storvsc,hv_blkvsc,hv_utils,hv_timesource,[permanent]

 Note : Your file system type or other local factors might result in different file sizes in your deployment.

• “hv_netvsc” provides support for the synthetic network card.
• “hv_storvsc” provides support for the synthetic SCSI controller and disks.
• “hv_blkvsc” provides support for synthetic IDE  disks and fastpath boot.
• “hv_timesource” is the pluggable time source module to assist in accurate timekeeping in the virtual machine.
• “hv_vmbus” is the fast communication channel between the server running Hyper-V and the virtual machine.
• “hv_utils” provides integrated shutdown, key value pair data exchange, and heartbeat.

What is an Enterprise Wiki

An Enterprise Wiki is a publishing site for sharing and updating large volumes of information across an enterprise. If an organization needs a large, centralized knowledge repository that is designed to both store and share information on an enterprise scale, consider using an Enterprise Wiki. Organizations can create a company-wide Enterprise Wiki where employees can find and contribute the latest, most comprehensive information about corporate activities, benefits, and services. The Enterprise Wiki enables employees to use social tags and notes to help other employees find content.

Why to use it

Enterprise wikis help organizations collect, organize, and distribute information. Enterprise wikis often become repositories for an organization’s unstated knowledge, which otherwise might not be stored anywhere. Enterprise wikis can encourage informal learning and sharing tips with other users, which can reduce the need for formal training or continuous IT support.

How does an Enterprise Wiki differ from a Team Site

The Team Site template provides a flexible way to create content. This template includes a cross-browser Rich Text editor and in-line auto-completion. The Team Site template enables collaboration across teams within an organization or across organizations. Team Sites address two key concerns for anyone responsible for ensuring the integrity of an organization’s content.

• Editorial control   Administrators of a Team Site, or anyone with Full Control permissions on a Team Site, can allow a subset of users to edit entries and allow all users to read the entries.
• Version control    Users can view previous versions of an entry and see when and by whom changes were made. If the changes were incorrect or inappropriate, the entry could be rolled back to an earlier version.

In SharePoint Server 2010, the Team Site template home page is a wiki page. The Enterprise Wiki template uses the publishing features of SharePoint Server 2010 to add page ratings, managed metadata, and customization capabilities. Integration with Microsoft SharePoint Designer 2010 makes it easy to modify the display of content by changing page layouts and implement consistent branding by changing master pages

The following table compares the features of an Enterprise Wiki with those of a Team Site.

 Note:
Enterprise Wiki pages cannot be converted or migrated to pages on a Team Site without using custom code. Because Enterprise Wikis are used with the publishing feature in SharePoint Server 2010, there are significant differences between an Enterprise Wiki site and a Team Site.

When to use an Enterprise Wiki

An Enterprise Wiki is a good solution when a business need requires multiple users to contribute to a knowledge repository. However, if you need a way to set up one-to-many communication about a project or area of interest, you should use a Team Site. Consider the following questions while deciding to use an Enterprise Wiki :

Q1. What purpose will the Enterprise Wiki serve?   

Example 1: It might address a specific business goal or it might be a centralized body of knowledge about a specific topic, process, or business problem. The goal is to provide a space where members of a virtual community can create, change, or remove content, which might include content that previous authors created.
Example 2: You might want to use an Enterprise Wiki to enable employees to contribute content to Tips and Tricks pages about the business applications that an organization uses.

However, if you determine that that you must have a more structured way to exchange knowledge, and that most communication will be one-to-many instead of the more free-form wiki behavior, you should consider using either a team site with Web Edit or a blog.

Q2. How many users should be allowed to contribute?   

Example 1: Will you be able to support increasing growth and a need for increased network and server capacity?
Example 2: Should you determine key contributors from each business area who will become the primary contributors?
Example 3: Are there legal considerations about who can contribute?

Q3. How can we control who has access to the Enterprise Wiki?

In theory, all members of an organization can be granted access to contribute, edit, and update content in an Enterprise Wiki for the organization.

If you have to separate information by group, consider using either a team site with Web Edit or a blog.

Q4. How much control should be implemented over the content?

Unlike blogs, which are designed for a more structured knowledge exchange, a wiki encourages informal contributions. However, an organization might have guidelines or requirements for handling specific kinds of content or content about a specific subject. You should also consider how to address inappropriate or inaccurate entries.

Where to host an Enterprise Wiki

Because an Enterprise wiki can generate a high level of network traffic, you might find it necessary to configure a single site collection and a single, dedicated Microsoft SQL Server database. If the Microsoft SQL Server database is shared, users might experience slower performance. Because Enterprise Wikis can grow quickly, the location that you select for hosting must be able to handle increased performance and capacity requirements. For example, although an Enterprise Wiki generally contains pages with low storage requirements, it is typically edited by a greater percentage of users than is common for Team Sites.

For more information and recommendations on How to Secure Business Information, download the Securing Business Information Work Smart Guide from Microsoft IT.

Because of this, the Office team has engineered new protection and threat mitigation technologies into Word 2010, Excel 2010 and PowerPoint 2010. Two of these new technologies, known as Office File Validation and Protected View, are designed to help protect an organization’s resources by mitigating potentially harmful effects that can result from Office binary file format exploits. A third new feature in Office 2010 called Trusted Documents can work together with these two protection technologies to provide users with an improved experience that requires them to make fewer security decisions when working with documents that contain active content such as macros or ActiveX controls.

With Word 2010 for example, when a user attempts to open a .doc file, instead of having Word itself load the file into memory and display its contents, the file is first passed to a DLL that thoroughly validates the file against the XML specification for.doc files that was created using the results of the intensive distributed fuzzing preformed during the Office 2010 security engineering process. If the .doc file passes validation, this DLL passes the file to Winword.exe which then opens it and displays its contents with full editing capability enabled. If the file fails validation however, there is the possibility that the file may be harmful to the user’s computer. In this case, the file is then opened within an isolated “sandbox” environment called Protected View that allows the user to scroll through the document and view its contents but disables all editing functionality and any active content in the document. At this point it is a special low-privilege sandbox Winword.exe process that renders the document, not the Winword.exe host process.

Once the user has examined the contents of the document and has determined that it is from a legitimate source, the user then has the option of enabling editing for the document by responding to a prompt displayed in the Message Bar. At that point the Protected View sandbox process terminates and the document is reopened using the Winword.exe host process with full editing capability enabled, and if the document contains any active content a second Message Bar prompt will be displayed that presents the user with the choice of enabling the active content. If the user then chooses to enable active content within the document, a new feature of Office 2010 called Trusted Documents can now remember the user’s trust decision. This means that when the user later reopens the trusted document, the active content in it is automatically enabled without prompting the user again. This behavior is different to that for Word 2007 where the user was prompted to enable active content each time they tried to open a document that contained macros or ActiveX controls.

Similar DLLs to that for Word 2010 have also been included for Excel 2010 and PowerPoint 2010. These are used for validating .xls and .ppt files, and both Excel 2010 and PowerPoint 2010 also display files using Protected View if the file fails validation. Administrators can also configure Office 2010 to submit information concerning files that fail validation via the Watson error reporting channel so the Microsoft Security Response Center (MSRC) can investigate them. When new Office binary file format vulnerabilities are discovered, updates to the XML specifications are released and automatically downloaded by Office 2010 so they can be utilized by Office File Validation. A key benefit of this approach is that provides a faster response to addressing newly discovered file format vulnerabilities than the traditional software patching process.

Office 2010 – Defense In Depth

By implementing multiple, redundant security controls at different levels of an information system, security threats are able to penetrate one defensive layer can still be stopped by another layer. Office 2010 leverages this strategy by providing four defensive layers to safeguard users against threats involving maliciously crafted Word documents, Excel spreadsheets or PowerPoint presentations. Each security layer in Office 2010 implements specific countermeasures that are designed to initiate the moment a user tries to open a file using an Office 2010 application and which continue in effect until the file has been successfully opened for editing. As shown in diagram, these four layers of Office security perform the following functions:

• Harden the attack surface through improved security engineering together with key Windows operating system security features integrated into Office 2010. Support for Data Execution Protection/No Execute (DEP/NX), robust and agile cryptography, and other technologies provide a strong, first layer of defense against threats posed by malicious Office data files.
• Reduce the attack surface by limiting the types of files applications can open and by preventing the execution of certain types of embedded code. Office File Validation is a key technology at this layer, as are two other Office 2010 features file block settings and the Office ActiveX kill bit. Together these technologies reduce the number and variety of possible attack vectors that managed to get through the first defensive layer.
• Mitigate exploits so that any attack that gets through the first two defensive layers can have its impact minimized. The key Office 2010 technology at this layer is Protected View, which allows dangerous Office files to be displayed and examined without any harm to the user’s computer or the wider network.
• Improve the user experience by reducing the number of security decisions the user needs to make and by helping the user make better security decisions. The new Trusted Documents feature of Office 2010 is key here as it prevents “prompt fatigue” a condition that can afflict most users when they are faced with too many, repeated security warnings and results in them basically ignoring future warnings.

Defense in depth for Office 2010.

How Office 2010 Helps Mitigate Exploits

Sequence of steps that occurs when a user attempts to open a file using Word 2010, Excel 2010 or PowerPoint 2010.

To learn more about New Security Features in Office 2010, download this white paper on Keeping Enterprise Data Safe with Microsoft Office 2010

Parts of a SharePoint Server 2010 Site

A site is a group of related intranet Web pages where an organization can work on projects, conduct meetings, and share information. For example, a team might have its own site where it stores schedules, files, and procedural information. A team site might be part of a larger organizational portal site, where departments post information and resources for the rest of the organization.

All SharePoint sites have common elements, including: lists, libraries, Web Parts, and views.

Lists

Lists are a Web site component that allows your organization to store, share, and manage information. For example, you can create a task list to track work assignments or team events on a calendar. You can also conduct surveys, or host discussions on a discussion board.

Libraries

Libraries are a special type of list that stores files as well as information about files. You can control how files are viewed, tracked, managed, and created, in libraries.

Web Parts

Web Parts are a modular unit of information that forms a basic building block of most Web pages on an intranet Web site. If you have permission to edit pages on your Web site, you can use Web Parts to customize your site to display pictures and charts, portions of other Web pages, lists of documents, customized views of business data, and more.

Views

Views allow you to see the items in a list or library that are most important to you, or that best fit a purpose. For example, you can create a view of all the items in a list that apply to a specific department, or to highlight particular documents in a library. You can also create multiple views of a list or library that people can select from. Finally, you can use a Web Part to display a view of a list or library on a separate page of your site.

SharePoint 2010 Server Site Specifics

How you install and configure SharePoint 2010 Server will affect what you see, and what options are available to you on your site.

Permissions

If you are assigned the default Full Control permission level, you have the full range of options to manage the site. If you are assigned to the Contribute or Read permission level, your options and access to site content are more limited. Many of the options discussed here are not available to users with the Reader permission level, which allows users to only read content, but not make changes to it. Because permissions are designed to be flexible and customizable, your organization may have its own unique settings.

Create a New SharePoint Site

You can go to the SharePoint Services webpage at http://sharepoint/Pages/hosting.aspx and follow the appropriate link to create a new SharePoint site in your region.

Adding Content to a SharePoint Site

You can add items to lists, and files to libraries, by using a Web browser. The buttons you use to perform the most common actions are located on the ribbon, which is near the top of the page on most site pages.

Buttons on the ribbon may be grayed out for any of the following reasons:

• The action is not applicable, or is dependent on some other action. For example, you must select the check box for a document before the Check Out button will become available.

• You do not have permission to complete the task.

• The feature is not enabled for this site. For example, workflows may not be enabled on this site.

You can also save files to a library from some client programs that are compatible with SharePoint Server 2010. For example, you can save a Microsoft Office Word document to a library on a SharePoint Server 2010 site while you are working in Office Word.

To add an item to a list, or a file to a library, you must have permission to contribute to the list or library. For more information about how your organization uses permissions and permission levels, ask your site owner or administrator.

When you add the item or file, other people who have permission to read the list can view the item or file, unless it requires approval. If the item or file requires approval, then it is stored in a pending state in the list or library, until someone with the appropriate permissions approves it. If you are already viewing the list or library when an item or file is added, you may need to refresh your browser to see the new item or file.

Lists and libraries can also take advantage of e-mail features, if incoming or outgoing e-mail is enabled on your site. Some lists, such as calendars, announcements, blogs, and discussion boards, can be set up so that people can add content to them by sending e-mail. Other lists, such as tasks and issue-tracking, can be set up to send e-mail to people when items are assigned to them.

In addition to adding content to existing lists and libraries, you may have permission to create new lists and libraries. The list and library templates give you a head start. Depending on your permission level, you can also create and customize new pages and sites.

Lists

Although there are different types of lists, the procedure for adding items to them is similar. This means you do not need to learn several new techniques to work with different list types. A list item contains text in a series of columns, but some lists may allow attachments to be added to the item as well.

Create a List

On many sites, some lists are already created for you. These default lists range from a discussion board, to a calendar list. If you have permission, you can also create lists from several types of list templates, which provide structure and settings to help you start.

To create a list:

1 Click Site Actions, and then click More Options

Important

If you do not see the Site Actions menu, you may not have permission to create a list.

2 On the Create page, click the type of list you want to create. For example, if you want to create a list of Links, then click Links.

3 Type a Name for the list, complete any other fields you want to complete, and then click Create.

Add an Item to a List

1 In the list where you want to add the item, click the Items tab on the ribbon. (It’s the Events tab for a calendar.)

2 Click New Item (New Event for a calendar).

Tip

You can also quickly add an event to a calendar by pointing to the date on the calendar, clicking Add, and then completing the fields in the dialog box that appears.

3 Complete the required fields and any others that you want to complete, and then click Save.

Edit or Delete an Item in a List

1 Point to an item, and then select the check box that appears next to the item.

Tip

You can perform actions on multiple items by selecting multiple check boxes.

2 On the Items tab on the ribbon, click either Edit Item or Delete Item, as required.

Libraries

A library is a location on a site where you can create, collect, update, and manage files with other team members. Each library displays a list of files and key information about the files, which helps people to use the files to work together.

You can add a file to a library by uploading it from your Web browser. After you add the file to the library, other people with the appropriate permission can see the file. If you are already viewing the library when someone adds a file, you may need to refresh your browser to see the new file.

If you are using a program that is compatible with SharePoint Server 2010, you can create a new file based on a template, while you are working in the library.

Create a Document Library

3 To create a document library, click Site Actions, and then click New Document Library.

Important

If you do not see the Site Actions menu, you may not have permission to create a library.

4 Type a name for the library, complete any other fields you want to complete, and then click Create.

Note

To see the other types of libraries you can create, click Site Actions, and then click More Options. Point to a library option to read a descriptor for that option.

Add a File to a Library

To add a file to a library:

1 In the library where you want to add the file, click the Documents tab on the ribbon.

2 Click Upload Document.

3 Browse to the document, and then click OK.

Note

If you are using a program that is compatible with SharePoint Server 2010, such as Office Word, you can drag and drop documents from the Windows Explorer window into the Upload Document dialog box.

Edit or Delete a File in a Library

To edit or delete a file in a library:

1 Point to a file, and then select the check box that appears next to the file.

2 On the Documents tab on the ribbon, click either Edit Document or Delete Document, as required.

When you create many types of sites, a default library called Shared Documents is created for you. Shared Documents is a document library that you can use for storing several types of files. You can create more libraries if you have permission to manage lists, such as a picture library for storing images.

Sites and Pages

A site can serve a general purpose, such as storing schedules, guidelines, files, and other information that your team frequently refers to. A site can serve a more specific purpose, such as keeping track of a meeting, or hosting a blog, where a member of your organization frequently posts news and ideas.

Your organization can use top-level sites, sub-sites, and pages, to divide site content into distinct, separately manageable sites.

A top-level site is at the top of the hierarchy in a site collection, from which you can manage site collection features. A top-level site can have multiple sub-sites.

A sub-site is a complete Web site stored in a named subdirectory of the top-level Web site. Each sub-site can have administration, authoring, and browsing permissions that are independent from the top-level Web site and other sub-sites.

For example, each department in your organization may have its own team sub-site that is part of a larger portal site.

You can add content to sites by adding lists and libraries. You may consider adding Web Part pages, which enable you to use Web Parts to quickly add dynamic content.

A Web Part page is a special type of Web page that contains one or more Web Parts. A Web Part page consolidates data—such as lists and charts— and Web content —such as text and images —into a dynamic information portal built around a common task.

Create a Site

If you need to create new sites, you can choose from several site templates to give you a head start on creating a new site. Whether you can create sites and sub-sites depends on how your organization has set up its sites, and its permissions to create them.

1 To create a site, click Site Actions, and then click New Site.

Important

If you do not see the Site Actions menu, you may not have permission to create a site.

2 Type a Title and URL name for the site.

3 Under Template Selection, select a site template.

4 Choose any other options you want, and then click Create.

Managing and Working with Site Content

There are several ways that you can manage and extend content in lists, libraries, and sites.

Navigating to Content

Navigation elements help people browse through the content that they need. Two navigation items that you can customize are the top link bar, and the Quick Launch.

By using the settings pages for each list or library, you can choose which lists and libraries appear on the Quick Launch. You can also change the order of links, add or delete links, and add or delete the sections into which the links are organized.

For example, if you have too many lists in the List section, you can add a new section for Tasks Lists, where you can include links to your tasks lists. You can make all of these changes to the Quick Launch from within a browser that is compatible with SharePoint Server 2010. You can also add links to pages outside the site.

The top link bar displays a row of tabs at the top of every page in the site, which allows users of your site to access other sites in the site collection. When you create a new site, you can choose whether to include your site on the top link bar of the parent site, and whether to use the top link bar from the parent site.

If your site is using a unique top link bar, you can customize the links that appear on the top link bar for the site. Any sub-sites that are created within the parent site can also be displayed on the top link bar, provided that the sub-sites are configured to inherit the top link bar of the parent site. You can also include links to other sites outside of your site collection.

Managing Access to Content

A site owner or administrator can grant permission levels to users, and to SharePoint groups that contain users. The permissions can be applied to a site, the lists and libraries on a site, and the items within the lists and libraries.

You can assign different permission levels for different objects, such as a specific site, list, library, folder within a list or library, list item, or document.

Organizing Lists

There are many ways to organize lists, such as using different views or adding new folders to your lists.

Some features help your team create and manage list items efficiently across several lists. For example, you can create a column that provides information about list items, and then share it across other lists.

Organizing Libraries

How you organize your files in a library will depend on the needs of your group, and on how you prefer to store and search for your information. For example, if you want to make a file available in multiple libraries, you can easily copy it to other libraries on your site. You can also request to be prompted for updates if the file changes.

You can also use the same features that you use in lists, such as views, and folders, to help you manage information.

Using Accessibility Features

Sites are designed so that lists, libraries, and other features can be fully accessed by using only keystrokes. A More Accessible Mode enables users of accessible technologies to more easily interact with menus and various controls. Skip to Main Content links enable keyboard users to skip over repetitive navigation links to the more meaningful content on a page.

The markup of headings is designed to better define the structure and improve navigation for people who use screen readers. Images that are uploaded to the site allow for custom alternative text to be defined. For example, you can assign custom alternative text to the image that appears on the home page in the Site Image Web Part, or to a picture that you add to a picture library. For viewing sites, the high contrast options in Windows work well for users with low vision.

Tracking Versions

Your list or library may be set up to track versions, so that you can restore a previous version and view a history of changes. When you track versions, any changes to the items or files and their properties are stored. This enables you to better manage content as it is revised, and even to restore a previous version if necessary. Versioning is especially helpful when several people work together on projects, or when information goes through several stages of development and review.

1 The current published major version is highlighted, and the version number is a whole number.

2 A new version is created when properties or metadata changes.

3 The first version of a file is always minor version number 0.1.

Co-authoring Documents

Two or more users can edit an Office Word document or Office PowerPoint® presentation at the same time. This new SharePoint Server 2010 feature enables you to read and write portions of a file stored in SharePoint Server 2010. For example, you can edit one paragraph in an Office Word document, while a colleague edits another paragraph in the same document and at the same time.

To learn more about document collaboration and co-authoring in SharePoint Server 2010, go to http://office.microsoft.com/en-us/sharepoint-server-help/document-collaboration-and-co-authoring-HA101812148.aspx.

Staying Updated on Changes

You can distribute and receive information, including updates to lists and libraries, in a standardized format by using RSS. A standardized XML file format allows users to use many different programs to view the information. You can also subscribe to lists and libraries by setting alerts, so that you know when content has changed.

A team can use RSS feeds as a way to customize their content for team members who subscribe to their feeds, and to offer links back to their Web sites. You can use RSS Feeds to track team progress and project updates. Instead of browsing multiple team Web sites, you receive the latest news or updates from those sites automatically.

Managing Workflow

Workflows help people to collaborate on documents and manage project tasks, by implementing specific business processes on documents and items in a site. Workflows help organizations to adhere to consistent business processes. Workflows can also improve organizational efficiency and productivity by managing the tasks and steps that are involved in specific business processes. This enables the people who perform these tasks to concentrate on performing the work, rather than managing the workflow.

Workflows can streamline the cost and time required to coordinate common business processes—such as project approval or document review—by managing and tracking the human tasks involved with these processes. For example, an organization can use a predefined Approval workflow or create and deploy a custom workflow to manage another business process.

To learn more about workflow and SharePoint Server 2010, go to http://office.microsoft.com/en-us/sharepoint-server-help/CH010372671.aspx.

Working with Content Types

Your list or library may support multiple content types. Content types enable organizations to organize, manage, and handle large amounts of content more effectively. If your list or library is set up to allow multiple content types, you can add content types from a list of available options that your organization frequently uses, such as Marketing Presentations, or Contracts.

After you add a content type to a list or library, you make it possible for that list or library to contain items of that type. Users can then use the New Item button in that list or library to create new items of that type.

One of the key advantages to content types for lists and libraries is that they make it possible for a single list or library to contain multiple item types or document types, each of which may have unique metadata, policies, or behaviors.

To learn more about working with content types, go to http://office.microsoft.com/en-us/sharepoint-server-help/CH010372670.aspx.

For More Information

· Basic Tasks in SharePoint Server 2010
http://office.microsoft.com/en-us/sharepoint-server-help/basic-tasks-in-sharepoint-server-2010-HA101839175.aspx

· SharePoint Server 2010 Help
http://office.microsoft.com/en-us/sharepoint-server-help/