This exam is intended to validate the configuration skills needed to administer a SharePoint 2010 installation.
Candidates for this exam typically have more than one year of experience configuring SharePoint and related technologies, including Internet Information Services (IIS), Windows Server 2008, and Active Directory, and networking infrastructure services.
+Is proficient with the infrastructure and security of Windows Server 2008.
+ Has experience with business operations for IT, including data backup, restoration, and high availability.
+ Has experience with Windows PowerShell 2.0 and command-line administration.
The following are the course blueprint
#Installing and Configuring a SharePoint Environment
-Deploy new installations and upgrades:
This objective may include but is not limited to: running Visual Upgrade, performing an in-place upgrade, performing a database attach upgrade, analyzing a PreUpgradeCheck report, installing language packs, and scripting installations; analyzing ULS logs, installation error logs, and event logs to identify installation problems; and repairing installation errors
#Configure SharePoint farms.
-This objective may include but is not limited to: configuring inter-server communications, server roles, high availability, InfoPath Forms Services (IPFS), Alternate Access Mappings (AAM), external sites, host headers, and applying and managing patches
#Configure service applications.
-This objective may include but is not limited to: configuring service applications such as Business Connectivity Services (BCS), Access Services, Visio Services, Microsoft Office PerformancePoint Server 2007, user profiles, Microsoft Office Excel services, Managed Metadata Services (MMS), and IPFS
#Configure indexing and search.
-This objective may include but is not limited to: configuring FAST Search for SharePoint, crawl schedules, iFilters, crawl rules, content sources, scopes, managed properties, content types, search components, index partitioning, and federated search locations
Managing a SharePoint Environment
#Manage operational settings.
-This objective may include but is not limited to: configuring logging, quotas, monitoring levels, health reports, security, and SQL Server Reporting Services (SSRS) integration
- Manage accounts and user roles.
This objective may include but is not limited to: managing user accounts, group accounts, managed accounts, computer accounts, and service accounts; and delegating site collection administration
-Manage authentication providers.
This objective may include but is not limited to: managing NTLM, Kerberos, claims-based, and forms-based authentication; and configuring Secure Store Service (SSS) and Active Directory Federation Services (AD FS).
#Deploying and Managing Applications
-Manage Web Applications.
-This objective may include but is not limited to: managing databases, Web Application settings, security, and policies.
-Manage site collections.
This objective may include but is not limited to: managing site collection policies, features, caching, and auditing; configuring site collection security; configuring multi-tenancy; and configuring site collection quotas and locks.
-Deploy and manage SharePoint solutions.
This objective may include but is not limited to: deploying and managing SharePoint solution packages, managing sandbox solutions, and managing user solutions
#Maintaining a SharePoint Environment
-Backup and restore a SharePoint environment.
This objective may include but is not limited to: configuring backup settings; backing up and restoring content, search, and service application databases; detaching and attaching databases; and exporting lists and sites
-Monitor and analyze a SharePoint environment.
This objective may include but is not limited to: generating health, administrative, and Web analytics reports; interpreting usage and trace logs; identifying and resolving health and performance issues
Please let me know in case of any queries or questions, Thanks...
Microsoft SharePoint Foundation 2010 uses Microsoft SQL Server 2008 databases to store configuration settings and most of the content for the Microsoft SharePoint Foundation Web site.
For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server. SharePoint Foundation 2010 uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name or password (domain name and password), or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.
This error indicates that Microsoft SharePoint Foundation could not connect to the SQL Server database.
One or more of the following symptoms might appear:
• Attempts to communicate with SQL Server fail and no content from databases hosted on the SQL Server can be accessed.
• This event appears in the event log: Event ID: 3355 Cannot connect to SQL Server. not found. Additional error information from SQL Server is included below.
One or more of the following might be the cause:
1. The SQL Server might be offline.
2. The SharePoint Foundation database access account might not have the necessary permissions to communicate with the SQL Server.
3. A firewall that runs on either the local server or on SQL Server might be blocking network communications.
Troubleshooting Steps:
Grant correct permissions to the database access account:
You must be a member of the Farm Administrators group to perform this task.
Assign the database access account:
a. On the Central Administration home page, click Security and in the General Security section click Configure service accounts.
b. On the Service Accounts page, in the Credential Management section, in the upper dropdown list click the correct Web application pool for your Web application.
c. In the Select an account for this component drop-down list, click the domain account that you want to associate with this Web application pool, or click Register new managed account to associate a new domain account with this application pool.
d. Click OK to save changes.
Verify that the account has correct permissions in SQL Server:
a. Connect to the computer that runs SQL Server by using an account that has Administrator permissions.
b. In SQL Server Management Studio, Object Explorer navigation pane, expand the Security node, and then expand the Logins node. The name of the database access account indicates that it is a SQL login.
c. If the account exists, in the Object Explorer navigation pane, expand the Databases node, expand the configuration database node, expand the Security, and then click Roles.
d. Expand the Database Roles node, right-click db_owner role and select Properties.
e. In the Database Role Properties dialog box, check whether the database access account is in the Members of this role list. If the account is not listed, click Add.
If you have any queries or questions regarding the above mentioned info then please let me know, Thanks...
Alert Name: ULS not enough free disk space
Event ID: 6457
The Microsoft SharePoint Foundation Tracing (SPTracev4) service is used by Microsoft SharePoint Foundation 2010 to manage trace message output. When trace logging is turned on,administrators can specify the path that is to be used to store the trace logs. This log file is used by many applications that are built on top of SharePoint Foundation. The trace log contains information that is useful for diagnosing server problems. SharePoint Foundation 2010 could not write to the trace
log. This event occurs when not enough free space is available for logging.
The following symptoms might appear:
• The trace log shows no new data.
• This event appears in the event log: Event ID: 6457 Description: Not enough free disk space available. The tracing service has temporarily stopped outputting trace messages to the log file. Tracing will resume when more than <# of MBs needed to resume logging> MB of disk space
becomes available.
Possible Cause:
The configured log location does not have sufficient free disk space for logging.
Troubleshooting steps:
Free up disk space
1. Use Disk Cleanup to free up disk space where the trace logs are stored.
2. Verify that the trace log has enough disk space to run properly.
3. If the trace log does not have enough disk space, clean up the Temp folders on the drive.
4. If this procedure does not solve the problem, it is also possible to relocate the trace log file to a partition that has more drive space.
Relocate the log file
1. On the SharePoint Central Administration Web site, click Monitoring and in the Reporting section, click Configure diagnostic logging.
2. On the Diagnostic Logging page, in the Trace Log section, type the new location for the trace log files in the Path text box.
3. Click OK.
If you have any queries/questions regarding the above mentioned info then please let me know, Thanks..
Alert Name: E-mail service cannot deliver e-mail
Event ID: 6873
The Microsoft SharePoint 2010 Products e-mail service processes e-mail destined for insertion into SharePoint lists. The service processes mail that the Windows Simple Mail Transfer Protocol (SMTP) service added to a drop folder.
One or more of the following symptoms might appear:
• SharePoint lists do not receive e-mail.
• This event appears in the event log: Event ID: 6599 Description: an error occurred while processing incoming email
One or more of the following might be the cause:
• There is no corresponding SharePoint list for the recipient of an e-mail.
• The sender does not have sufficient permissions to add content to the SharePoint list.
Troubleshooting Steps:
Verify that the list is configured to receive e-mail:
1. In the list provided in the event details, on the List menu, click List Settings.
2. On the List Settings page, under Communications, click Incoming e-mail settings.
3. Verify the following:
• The correct e-mail address is entered in the E-mail address box.
• The Yes option is selected under Allow this document library to receive e-mail?
Grant the sender the appropriate permissions to the recipient list:
1. In the list provided in the event details, on the List menu, click List Settings.
2. On the List Settings page, under Permissions and Management, click Permissions for this list.
3. Verify that the user account provided in the event details has at least Contributor permissions to the list.
If you have any queries/questions regarding the above mentioned information then please let me know, Thanks..
