1 / 19

MOSS Configuration

belle
Download Presentation

MOSS Configuration

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. MOSS Configuration September 2007

    3. Server Farm Topology Slide Title: Choosing the Topology Keywords: Topology, single server, small farm, medium farm, large farm Key Message: How to choose the right topology. Slide Builds: 4 Slide Script: There are some factors to consider when choosing the right topology. These include data composition, user load, long-running operations, performance, availability and reliability and other network considerations. Let us spend some time looking briefly at the options, before we look more closely at each scenario. [BUILD1] The first option is a single-server topology. In this case, you will have a single server with all the necessary components to run SharePoint Services. [BUILD2] Next, you may choose to have a small farm topology. This topology will involve dividing roles among more than one server. [BUILD3] As your performance needs increase, you will want to increase the size of your farm. The next step is the medium farm. With a medium farm, you will divide the roles among even more servers. [BUILD4] Finally, you many choose a large farm topology. This farm topology will provide the greatest performance. You also have the option for a multi-farm topology. The advantages of a multi-farm topology include security and process isolation, which may be necessary due to business demands. Content management within a multi-farm topology allows for authoring in the intranet with Active Directory authorization and production in a premier network with forms authorization. Content deployment copies content between networks, because the path connects source and destination site collection. There is also a Quick Deploy feature that allows authors to expedite specific articles. Keep in mind that with this topology there is the advantage of interfarm Shared Services. Slide Title: Choosing the Topology Keywords: Topology, single server, small farm, medium farm, large farm Key Message: How to choose the right topology. Slide Builds: 4 Slide Script: There are some factors to consider when choosing the right topology. These include data composition, user load, long-running operations, performance, availability and reliability and other network considerations. Let us spend some time looking briefly at the options, before we look more closely at each scenario. [BUILD1] The first option is a single-server topology. In this case, you will have a single server with all the necessary components to run SharePoint Services. [BUILD2] Next, you may choose to have a small farm topology. This topology will involve dividing roles among more than one server. [BUILD3] As your performance needs increase, you will want to increase the size of your farm. The next step is the medium farm. With a medium farm, you will divide the roles among even more servers. [BUILD4] Finally, you many choose a large farm topology. This farm topology will provide the greatest performance. You also have the option for a multi-farm topology. The advantages of a multi-farm topology include security and process isolation, which may be necessary due to business demands. Content management within a multi-farm topology allows for authoring in the intranet with Active Directory authorization and production in a premier network with forms authorization. Content deployment copies content between networks, because the path connects source and destination site collection. There is also a Quick Deploy feature that allows authors to expedite specific articles. Keep in mind that with this topology there is the advantage of interfarm Shared Services.

    4. Server Farm Topology NOTE: Stand Alone installations should be done for testing or demonstration purposes only. This type of installation can’t be expanded or developed into a server farm configuration. Only way to develop into server farm is to manually move the databases to new SQL server and reinstall MOSS into server farm configuration. NOTE: All server farm installations of SharePoint should be configured to use Kerberos authentication. Any external access should be done using SSL.

    5. Server Farm Topology Medium Server farm configurations

    6. Server Farm Topology Medium Server farm configurations

    7. Server Farm Topology MOSS standard services with Project Server installed

    8. Server Farm Topology Search Service Configuration Screen

    9. Server Farm Topology Example of Medium Server Farm Configuration Front End Web Servers Windows SharePoint Services Web Application Service Windows SharePoint Services Incoming E-mail Service Office SharePoint Server Search (Query Component) Application Server(s) Central Administration Document Conversions Launcher Service Document Conversions Load Balancer Service Excel Calculation Services *Project Application Service Windows SharePoint Services Help Search

    10. Benefits of previous Configuration Front End Servers return search results quickly Search continues to function if indexer is down Indexer can be configured to maximum performance with out affecting user experience Redundancy to user if one front-end server is down Gotcha If the index server also has the query server component configured it will never propagate indexes to any other query servers.

    11. Server Farm Topology Central Administration Redundancy Install Central Administration service on 2nd application server in farm. Configure Alternate Access mappings to allow access to the site. If Central Administration application server goes down without 2nd configured you can recover by installing new server into the farm and selecting the option to install Central Administration.

    12. Server Farm Roles Farm Administrator Administers the Central Administration Application SSP Administrator Administers the SSP application Search Administrator Can administer all search settings in the SSP User Profile Manager Can add import connections, manage user profiles, and configure MySite settings Audience Manager Can manage audiences settings in the SSP

    13. Server Farm Roles BDC Manager Can import application definitions to the Business Data Catalog BDC Permission Manager Can manage permissions for the Business Data Catalog Profile Services Permission Manager Can manage permissions for profile services Excel Services Administrator Can administer all Excel Services settings in the SSP Usage Reporting Manager Can administer usage reporting settings in the SSP

    14. Server Farm Roles Single Sign-on Administrator Setup, configure, and manage SSO accounts Enterprise application definition administrator Create, delete, and manage enterprise application definitions Server-level Administrators Local server administrators group are automatically added to the Farm Administrators SharePoint group and can perform all farm administrator actions.

    15. SSP Configuration Shared Service Providers Factoids One index server per SSP 50 Million documents per Index server including BDC 20 SSP’s per farm limit Note: An SSP can be associated with only one index server and one content index. However, an index server can be associated with multiple SSPs and have a content index for each SSP.

    16. Shared Services Multiple SSPs? Vast majority of installs = 1 SSP Use cases for multiple SSPs Secure isolation of services and service data Hosted environments Restricted sites Organizational / Political concerns

    17. SSP Configuration Inter Farm Shared Services (IFSS)

    18. SSP Configuration Parent/Child relationship. Parent and child must exist within the same Active Directory Forest Parent and child must have same features and cals Child farms share Search, Audience, Profile, and BDC IFSS not supported across WAN links

    19. Useful Links Plan for Security Roles http://technet2.microsoft.com/Office/en-us/library/f07768d4-ca37-447a-a056-1a67d93ef5401033.mspx?mfr=true Plan for administrative and service accounts http://technet2.microsoft.com/Office/en-us/library/f07768d4-ca37-447a-a056-1a67d93ef5401033.mspx?mfr=true Plan for software boundaries http://technet2.microsoft.com/Office/en-us/library/6a13cd9f-4b44-40d6-85aa-c70a8e5c34fe1033.mspx?mfr=true

More Related