Sharepoint 2010 ylläpitäjät Webinaari
•Download as PPTX, PDF•
0 likes•963 views
Salcom Webinaari Sharepoint 2010 ylläpitäjille 7.5.2012
Recommended
More Related Content
Viewers also liked
Viewers also liked (13)
Similar to Sharepoint 2010 ylläpitäjät Webinaari
Similar to Sharepoint 2010 ylläpitäjät Webinaari (20)
More from Salcom Group
More from Salcom Group (15)
Sharepoint 2010 ylläpitäjät Webinaari
- 1. Sharepoint 2010 Ylläpitäjille Arsi Savolainen Technology Consultant MCT
- 2. Kouluttajan esittely Arsi Savolainen Kouluttaja/Konsultti MCT Osaamisalueet: • SharePoint • Lync • Quest Sharepoint -tuotteet – Site Admin, Recovery Manager, Migration Manager • Oracle ESSO (single-signon) • Evidian (single-signon) • Entrust IdentityGuard (Vahva tunnistautuminen)
- 3. Roolit ja Topologiat • Roolit – Web Front-End (WFE) – Tietokanta (SQL) – Application Server • Central Administration • Service Applications (SAs) kuten haku • Office Web Apps • Topologiat – Yksi palvelin: kaikki roolit – Yksi WFE, SQL – Kaksi WFE:iä (vikasietoiset sovellukset ja palvelut), SQL (ehkä klusteri) – Useampi palvelin (vikasietoisuus ja suorituskykyoptimointi palveluiden tarpeen mukaan), SQL klusteri
- 4. Arkkitetuuri vaatimukset • CPUs: 4-core, 2.5 GHz, 8GB RAM • Vain 64-bit • Käyttöjärjestelmä – Windows Server 2008 SP2 x64 – Windows Server 2008 R2 x64 • SQL palvelin – SQL Server 2005 SP3, Cumulative Update 3 x64 – SQL Server 2008 SP1, Cumulative Update 2 tai 5+ x64 – SQL Server 2008 R2 x64 • Mirroring, PowerPivot ja Access services reporting • Viimeiset service pack:t ja päivitykset
- 5. SharePoint Infra Microsoft ja ISV - Kustom-ratkaisut (solution) ratkaisut (solution) SharePoint Server SharePoint Foundation Identity SQL IIS Server Services .NET Framework Windows Server 2008/R2
- 6. SharePoint Tuotteen ja teknologiat • SharePoint Foundation 2010 • Kehitystyökalut • SharePoint Server 2010 for Intranet – SharePoint Designer 2010 Scenarios – Visual Studio 2010 – Standard tai Enterprise Client Access • Klientit License – Office client applications • SharePoint Server 2010 for Internet – SharePoint Workspace 2010 Sites, Standard tai Enterprise – SharePoint Mobile • Office Web Apps • Palvelimet • FAST Search for SharePoint 2010 – Duet Enterprise for Microsoft • FAST Search for SharePoint 2010 for SharePoint and SAP Internet Sites – Project Server • Search Server 2010 and Search Server – Dynamics Microsoft ja ISV Kustom ratkaisut Express 2010 ratkaisut (solution) (solution) SharePoint Server SharePoint Foundation
- 7. SharePoint Lisenssöinti • Windows Server 2008 tai Windows Server 2008 R2 – Server license plus client access license (CAL) jokaiselle käyttäjälle – Per-User yleisin • SQL Server Express – ei lisenssiä • SQL Server – Server product lisenssi – Per-processor lisenssi yleisin • SharePoint Foundation 2010 – ei lisenssiä • SharePoint Server 2010 – Server product lisenssi – Standard CAL tai Standard+Enterprise CAL jokaiselle käyttäjälle • Enterprise: Fast haku, Access service, Infopath service, PerformancePoint Services, Visio Services • Muut tarvittavat lisenssit – Microsoft Office 2010
- 8. Service Applications • Service applications host pohjaiset palvelut – Search Service Application – Business Connectivity Service – Managed Metadata Service – User Profile Service • Service app’s application connection (proxy) mahdollistaa yhteyden service applicationiin – Web sovellukset yhdistyvät service app proxyyn (itseasiassa proxy groupin kautta) • Yhteydet on ryhmitelty application connection (proxy) groups kautta – Oletuksena Default
- 9. Kustomointi ja laajennettavuus • Teemat ja branding • Out-of-the box ratkaisut (solutions), pohjat, ja web partit • Kustom ratkaisut (solutions): ilman koodia tai Visual Studio – Workflow, SharePoint Designer, InfoPath Services, Visio Services, Excel Services, Access Services – Microsoft .NET, Silverlight – Business Connectivity Services: Yhteistoiminta Lob sovellusten kanssa – Web services, API (SharePoint ja client object models), REST • ISV ja community solutions – Esim. www.codeplex.com
- 10. Enterprise tason yhteistoiminta • Sivustot/sivut – Omistajuus ja oikeudet – Asetukset: Managed Metadata, Sivustopohjat, dokumentti pohjat (content type)… • Listat ja Kirjastot – Oikeudet – Määritykset: versiointi, työnkulut, Check-in/out… • Hälytykset & RSS – Poisto/(Luonti), määritykset • Business prosessien automatisointi: työnkulut – Out-of-box työnkulut – Dokumenttien reititys – SharePoint Designer 2010 Kaikki yllämainitut SharePoint Foundation SharePoint Foundation
- 11. Identiteetti ja Profiili • My Site – Ongelmien ratkaisu ja palautus – Varmistaminen ja tuhoaminen • Käyttäjäprofiilit – Attribuuttien määritykset: Replikointi, käyttäjien oikeudet – Ongelmien selvitys • Kuva, Läsnäolo ja Kontaktikortti – Enemmänkin Lync asia
- 12. Tietoturvan hallinta ja laajennettavuus • Tietoturva, Yksityisyys & Yhdenmukaisuus – Keskitettyjen liiketoiminta asetusten määrittäminen ja hallinta • Tuhoaminen, käyttöoikeudet, lukitus (records management) – Monitorointi, auditointi ja raportointi • Laajennettavuus – Forefront Identity Manager (FIM) hyväksikäyttö
- 13. Sisältö ja Metadata • Järjestely (sivustot) ja järjestämätön (blogi, wiki) sisältö – Käyttäjien hommaa – Ongelmien selvittäminen; hävinnyt sisältö, linkitykset, sisällönsiirto • Managed Metadata Service – Määritykset – Hallinta pitäisi ulkoistaa eri Business yksiköille – Oikeudet, auditointi – Enterprise content types – jaettavat dokumenttipohjat • Metadatan käyttö – Sivustopohjiin suoraan tarjolle – Metadata ohjattu navigointi – Käyttö hakujen filtteröintiin
- 14. Sisältölähteet, indekstointi ja kysely • Sisältölähteet – Sisältölähteiden määrittely, Sharepoint, Levyjaot, muut web palvelut • indeksointi – Ajastusten määrittely – Blokattu sisältö – Indeksointiongelmien ratkaisu – Federoitu haku • Kysely – Hakulähteet – Thesaurus ja noise words määrittely – Tulosten muokkaus
- 15. Infromaatiolähteet • SharePoint • Business Connectivity Services (BCS): Ulkoiset tietolähteet • PerformancePoint Services: Interaktiivinen scorecard & dashboard • Visio Services: Browser-pohjainen Visio kaavion renderöinti, filtteröinti, yhteistoiminta objektien kanssa ja data yhteydet (esim. Navigointi) • Excel Services: – Luotettujen tallennuspaikkojen määrittäminen – Käytönrajoitukset – Ohjelmallinen hallinta: JavaScript object model ja REST API • PowerPivot, SQL Analysis Services – Raportointi ja analysointi
- 16. Managed Accounts • Managed Accounts – SharePoint voi vaihtaa salasanan haluttuihin tunnuksiin Active Directoryssä ja suoraan palveluun • Hallinta – Rekisteröinti – Salasananvaihto – Salasanan vanheneminen ja automaattinen vaihto
- 17. Sisältötietokannat • Sivustokokoelmat ja sisältötietokannat – Sivustokokoelma yhdessä sisältötietokannassa • Koko, järjestely – Out-of-box varmennustyökalujen yksikkö on sisältötietokanta • Skaalautuvuus – 300 sisältötietokantaa per Web applikaatio • Määrä riippuu SQL serverin muistin määrästä – 200 GB per sisältötietokanta on tuettu – 100 GB per sivustokokoelma – 250,000 Web sivua per sivustokokoelma • Luo sisältötietokanta • Luo sivustokokoelma ko. Tietokantaan – Voit myös siirtää olemassa olevan uutteen kantaan
- 18. web.config tiedosto • XML-pohjainen tiedosto root hakemistossa joka Web applikaatiossa tai virtual hakemistossa • Ryhmitetyt osiot (XML) asetuksille – SafeControls: määrittää mitä kontrolleja saadaan käyttää SharePoint sivuilla. – SafeMode: saadaanko käyttää sharepointiin (esim. Web parttiin) sisällytettyä .NET koodia. – MergedActions: mahdollistaa muutokset web.config tiedostoon ilman itse tiedoston muuttamista, yhdistämällä tietoja toisista tiedostoista. – BlobCache: mahdollistaa eri tiedostojen cachen Web front end palvelimella, ilman että itse dataa tarvitsee aina hakea tietokannasta.
- 19. SharePoint Root • Suurin osta SharePoint tiedostoista sijaitsee yhdessä hakemistossa Web serverssä • C:Program FilesCommon Files Microsoft Sharedweb server extensions14 • Useampi alikansio • TEMPLATE kansio näistä eniten käytetty – esim. kuvat
- 20. SharePoint Rootin synkronointi • Root pidettävä synkassa Web front-end palvelinten välillä • Mikä muuttaa Root hakemistoa: – Sivupohjan lisäys/poisto – Globaali kuva – Sovellus-sivun lisäys – Teeman lisäys/poisto • SharePoint solutions – Paketti jolla jaetaan toimistoja ja tiedostoja – Samantapainen kuin Windows Installer (.msi) tiedosto – Farmi pitää itse huolen että kaikki palvelimet ovat ajan tasalla
- 21. Kustomoitu vs. ei kustoimoitu sivu • Uusi sivu: Sivu pohja (Site definition) luo oletus sisällön – Jotkut sivut ovat jaettu sivujen kesken, esim. DEFAULT.ASPX – Sivu on tallennettu SharePoint root:iin • Ei kustomoitu sivu – Sijaitsee SharePoint root:ssa – Sisältö (esim. Web part näkymä) on tallennettu sisältötietokantaan • Kustomoitusivu – Muokattu sivu, esim. SharePoint Designer 2010:llä – .aspx sivut on tallennettu sisältötietokantaan • HttpModule analysoi URI pyynnön ja hakee sivun sisältötietokannasta, jos se ei ole siellä haetaan SharePoint root • Service packs ylikirjoittaa tiedostoja SharePoint root:ssa
- 22. Administraatio työkalut • Central Administration • Stsadm – C:Program FilesCommon FilesMicrosoft Shared web server extensions14BIN • Windows PowerShell • SharePoint 2010 Management Shell – Tukee Stsadm • Sisältää polun BIN hakemistoon (STSADM) – Esilataa SharePoint snap-in:it Windows PowerShell:iin
- 23. Admin roolit • Farmi Administraattorit – Security Users Manage the Farm Administrators group – Voi tehdä mitä vaan – Ei oletuksena saa sisältöön oikeuksia mutta voi ottaa ownershipin • Paikalliset Administraattorit – Farm Administrators jäseniä – Asennus: Tuotteet, sovellukset, Web Parts, Ominaisuudet (features) • Service application administraattorit – Oikeudet vaan kyseiseen palveluun • Service application feature administrators – Palvelun osan administraattori • Sivustokokoelman administrators ja sivun omistaja – Kaikki oikeudet sivuun
- 24. Jatkuvuuden hallinta • Sivun tuhoaminen eräajona • Varmistus – Asetukset XML tiedostoon – Sisällön backup taas ajastettavissa – Siten ja listan backup Central Administa • Tietokantapeilaustuki • Palautus – Offline tietokanta palautus
- 25. Monitorointi/Logitus • Health Analyzer – Vertaa tilannetta Best Practices Anlyzer tuloksia vastaan • Health Reports – Ongelmien selvitykseen • Web Analystics – Raportointi käytöstä • Developer Dashboard – Kertoo statistiikkaa sivun toiminnasta • Flood Protection – Vähentää rivejä logissa
- 26. Päivittäminen (Patching) • Binäärien päivittäminen • Kannan päivittäminen • Päivityksen ymmärtävät edellisen päivityksen tietokanta scheman • Päivittämiselle on helpompi löytää sopiva aika • Raportointi
- 27. Koulutustarjonta • 521, MCITP: Sharepoint 2010 Administrator –valmennusohjelma • 541, Sharepoint 2010 sisällöntuotannon perusteet
- 28. Koulutustarjonta jatkuu • 10174, Sharepoint 2010, hallinta ja vianselvitys • 10231, Sharepoint 2010, suunnittelu ja käyttöönotto
- 29. Koulutustarjonta jatkuu • 50429, SharePoint 2010 Business Intelligence • 50465, PerformancePoint 2010 Designing and Implementing Scorecards and Dashboards • 50263, Sharepoint, Office 2007 ja SQL Server yhdessä Microsoft Business Intelligence ympäristössä • Kysy kurssimyynnistä
Editor's Notes
- Objective: Provide a high-level overview of SharePoint server roles and topologies.Delivery Tips:Define the roles and topology options.Don’t spend too much time with topologies. Simply introduce the concept of distributing roles.Let students know that later modules, particularly Module 12, will provide detailed coverage of topologies. The goal of this module is to get a single-server farm “up and running” so that students can begin configuring SharePoint.Point out that a very important infrastructural requirement of a SharePoint farm is that each WFE and application server has LAN-speed access to the database role. In other words, it is generally not going to be possible to put a WFE server in Tokyo for a farm whose database role is hosted on a SQL Server in New York, because the latency will be too great.
- 2-core vain testiin tai POCObjective: Detail the infrastructure requirements for SharePoint 2010.Delivery Tips:Discuss the infrastructure requirements. Point out that the guidelines are broad. SharePoint will perform adequately with only 8GB of RAM in certain environments, but needs much more to scale effectively. It might be possible to have a SharePoint server with less RAM in very small environments, particularly if it is configured to host only a small number of application pools, web applications, and services. It could be feasible to deploy a SharePoint server with a dedicated role—for example, a server hosting only a managed metadata service instance—on a server with less RAM.Inform students that upgrade issues, including migration from 32-bit to 64-bit platforms and from Windows Server 2003 to Windows Server 2008 [R2] are detailed in Module 12.Point out that while SharePoint 2010 does not require SQL Server 2008 R2, some features, including failover, PowerPivot and Access services reporting, do require SQL Server 2008 R2.
- ISV = Itegration Software VendorObjective: Help students visualize the “stack” or “layers” of the SharePoint platform. Delivery Tips:Fast reviewDetails:Point out that functionality related to business requirements can be achieved from any one of several of these layers:SharePoint Foundation: Supports core collaboration requirements around lists and librariesSharePoint Server: Rich variety of functionalityMicrosoft solutions: Project Server, Dynamics, FASTISV SolutionsThis diagram will be referred to throughout the course. Some of the points and themes that will be tied to this visualization include:The interrelation between components of the platformWhy it is important to administer “from the top.” For exampleUse SharePoint tools to manage the IIS components of SharePoint, rather than IIS ManagerUse SharePoint tools to manipulate data in SQL Server, rather than manipulating SharePoint databases and tables directly from within SQL ServerHow features work: They add functionality to the underlying platform. How SharePoint Server Standard and Enterprise relate: They each each add features.How ISV and custom solutions can build upon the platform of either SharePoint Foundation or SharePoint Server.Some identity services (e.g. Active Directory Federated Services and Identity Services) rely on the .NET Framework while others (e.g. Active Directory Domain Services) depend only upon Windows Server.Again, these points will be discussed later in the course, but as an instructor it might be helpful for you to know how this visualization will be used throughout the course.
- Duet Enterprise for Microsoft SharePoint and SAP = Ympäristöjossa Office tuotteillapääseekiinni SAP dataanObjective: Impress upon students that there is a deep field of SharePoint Products and TechnologiesDelivery Tips: There is no need to go into detail about each and every product in this list.Other products and technologies you might choose to mentionSilverlightMicrosoft SQL Server Reporting ServicesMicrosoft SQL Server PowerPivot for ExcelSyncFrameworkSharePoint Workspace Mobile Client (Windows Phone 7 Series)SharePoint Online SKUs: Standard and Deskless Worker
- Objective: Provide an overview of licensing.Delivery Tips:Explain that licensing is complex and, in the end, you must verify your licensing with Microsoft.Do not try to cover every scenario (for example, Internet-facing sites).Explain that SQL Server Express does not require a license, but has significant limitations both in database size and manageability. It is appropriate only in limited scenarios.Explain that licensing and keys can be changed as requirements change, except that it is difficult to go “down” (e.g. from SharePoint Server to SharePoint Foundation).Remind students that SharePoint Online reduces this complexity, as well as the total cost, of licensing and supporting a SharePoint infrastructure.
- Application connection = Yhteys Web ApplicationiinModuuli 8* In fact, web applications are associated with an application proxy group, which provides connections (proxies) to one or more service appsDelivery Tips:You will go into great detail about service applications in Module 8, however there are topics between now and then that refer to service applications. Use this topic to give students enough understanding about service applications to allow them to get through until Module 8.There are four slides in this topic. The first-level bullets on this slide correspond to headings in the student handbook. The fourth slide is a diagram and whiteboard that you may optionally use to communicate and reinforce concepts.This is the terminology slide. Introduce the terminology related to service applications.Be very accurate in your use or the terms service application versus service. The service is the machine service instance that runs (or does not run) on each SharePoint server based on what you have configured in the Manage Services on Server page in Central Administration. The service application is a logical, farm-level component that manages the behavior of services.You do not need to provide this level of detail to students now. This is for your information as an instructor.Point out that there are components that have two namesApplication connection (or connection) = proxyApplication connection group (or connection group) = proxy groupThe terminology is inconsistent, even in Microsoft documentation, so it’s up to you, the student, to keep it straight in your head.
- DO NOT PRINTREST =Representational State Transfervähän sama kuin HTTP (2000)Objective: Discuss customization, solutions and extensibility features—SharePoint as a platform.Most of these features (all of the IT Pro related features) and are detailed elsewhere in this course.Emphasize Codeplex. Address students’ concerns about using “open source” solutions. Point out that Codeplex is a Microsoft Web property. Discuss that while there are solutions submitted by the community, there are also solutions posted by the Microsoft product teams that offer important functionality that simply did not get rolled into the current release of the product. In years past, Microsoft released resource kits and support tools that provided important functionality, and enterprises used these tools even though Microsoft did not provide support for the tools. Codeplex is now the main channel through which useful but unsupported tools care released. Enterprises should not discount Codeplex simply because some solutions are submitted by lesser-known community members. Each solution in Codeplex should be evaluated on its own merits—by the functionality it offers, the reputations of the contributors, the reviews of the community, and the performance of the solution in your test environment.If Microsoft has released its Application Templates (the “Fabulous Forty”) for SharePoint 2010, point students to these tools. Inform students that for the rest of this discussion of SharePoint capabilities, it will be implied and assumed that each capability leverages these benefits of sites and can be extended.ResourcesFrom the Communities BrochureInvest in a platform solution: A ‘one size fits all’ collaboration solution does not satisfy the needs of most customers, therefore, SharePoint is designed as a platform that provides a standard, extensible framework for customized solutions to meet specific business needs. Easy-to-use APIs, custom workflows and templates are available to jump-start any solution. SharePoint also benefits from a large partner ecosystem with many custom solutions built on top of the SharePoint platform.Reduce development workload: SharePoint provides a broad range of tools for all levels of customization, allowing developers to build complex, mission-critical business applications using Visual Studio, while also giving end users the flexibility to design their own individual and team solutions with SharePoint Designer. This ability to customize at all levels frees up your developers to focus on more strategic projects. In addition, SharePoint also has a large selection of existing templates, Web parts, and other customized solutions to choose from, making development faster and easier.Maximize efficiencies through an integrated stack: One of the main advantages of the SharePoint plat-form is its ability to seamlessly integrate with the rest of the Microsoft stack—including the Office applications, Exchange, Communications Server, SQL, BizTalk, Visual Studio and Dynamics since all these products were built to work better together. In addition, the standard .NET development plat-form means that your developers don’t have to learn new skills or technologies. As well as integration within the Microsoft stack, SharePoint provides deep Line-of-Business application integration through the Business Connectivity Services and adheres to open standards/protocols making interoperability with other solutions straightforward.
- DO NOT PRINTObjective: Discuss core collaboration capabilities of SharePoint Foundation 2010Delivery Tip:Summarize this slide as representing the broad set of features related to enterprise collaboration. Many of them are identical to SharePoint 2007. The feature listed on this slide that is new to SharePoint 2010 is document routing.Give a bonus tip: SharePoint 2010 supports very large lists and libraries. This will be detailed in Module 4.Emphasize to students that SharePoint Foundation has a broad set of capabilities. In fact, almost everything on this slide is achievable without SharePoint Server. Help students understand that there may be scenarios where they can use a SharePoint Foundation farm, rather than a SharePoint Server farm. For example, while the corporate intranet, enterprise search, and business intelligence functionality may require SharePoint Server and be hosted on a farm in the corporate datacenter, a remote office on the distant side of a slow WAN link that requires support for collaboration between users in that office may be better served by a local SharePoint Foundation farm. Users in that office would still consume the services in the datacenter, but their day-to-day collaboration needs could be met, with better performance, by a locally-placed SharePoint Foundation farm.
- DO NOT PRINTModule 9:ssä käydään nämä läpiDelivery Tips:Summarize this slide by explaining that SharePoint 2010 delivers a broad range of new and improved features and functionality that support defining a user, their organizational relationships, areas of expertise, and other characteristics.Do not detail these features. They are detailed in Module 9.
- DO NOT PRINTObjective: Discuss manageability, extensibility and interoperability in the content capability. Give students confidence that enterprise social networking is manageable.Delivery Tips:Discuss Microsoft’s definition of communities and solicit feedback from students about what communities and social networking means to them. Emphasize that much of this relates to browsing, navigating, or finding (through search) expertise and information that is derived from social relationships, communications, activities and feedback.Resources:From the Communities BrochureTurn your business into a modern, dynamic information workplace with SharePoint 2010 Communities.Achieve higher levels of engagement and participation from your people: SharePoint Communities empower your people to connect with each other and collaborate in dynamic new ways helping you to meet the challenges of a diverse 21st century workforce, attract and retain the best talent, and improve overall productivity.Transform into an agile organization: SharePoint Communities can help your company respond quickly to business challenges and make the most of market opportunities through enhanced transparency across the organization, an improved ability to harness the collective intelligence of your people, and the increased efficiencies of horizontal decision making.Drive innovation from the ground up: Create a sustainable framework for future growth through a platform that enables the collaborative ex-change of ideas among your people at all levels in the organization.
- Objective: Discuss structured versus unstructured content and introduce concepts of content types, metadata, taxonomy, and tagging.Delivery Tips (Summary Discussion):Content types, metadata, tagging, and the MMS are detailed in Module 9. It is recommended that you provide only a very high-level summary here.Mention that SharePoint supports both unstructured content (blogs, wikis, discussions) and highly-structured content.Provide a very high level overview of metadata and tagging. Explain that tags (also called attributes or metadata) are applied to content so that content can be located (searched for) and used more effectively.Delivery Tips (Detailed Discussion):Ensure that students understand the basic concepts and terms related to the MMS that are shown on the slide. Module 6 explores metadata and the MMS in detail, but metadata will make appearances in topics and labs prior to Module 6. This topic should enable students to answer the questions, “What is metadata?” and “Why is it important?” Ensure that students understand that tags help an organizations’ information architecture grow over time, and SharePoint allows an organization to determine the balance of that growth that comes from centrally managed versus user-driven tags.Question: What are the business outcomes supported by the first-level bullets on this slide?Answers:Bullet 1: Increase the information quality and quantity. Remind students of the importance of unstructured content. A challenge faced by many enterprises is that valuable corporate knowledge is locked in the heads of employees, not because they aren’t willing to share it but because there is no system that makes it easy for them to share it. Unstructured content sources such as blogs and wikis and discussions provide a place for users to dump knowledge. While it is unstructured, at least it is there, and is indexed. With more structured content—in other words, content with defined metadata, workflows, rights management and other such attributes—the quality and value of information is increased. Over time, unstructured content can be moved into more structured formats as the value and usage scenarios for such content becomes clear to the enterprise. But the key is to get the information before it disappears.Bullet 2: Increase information value. A drawback of many content management systems is that content is not tagged, or not tagged well. SharePoint makes tagging content easy and manageable, which therefore makes it more likely that metadata will be applied. Bullet 3: Increase productivity. Because tagging is easy, users can focus on higher-value tasks. Additionally, metadata improves users’ ability to locate information, including through metadata-based navigation and search refiners.
- DO NOT PRINTObjective: Discuss how content becomes searchable (content sources and indexing) and how it is searched (query)
- DO NOT PRINTObjective: Communicate that the insights capability features enable an organization to aggregate information from a diverse array of sources.Following are some important points related to information sources: • With self-service access to information, users can discover and manage their aspect of the business with access to the right information. • Business Connectivity Services connects you with external data and systems. • PerformancePoint Services provide interactive scorecards and dashboards. • Visio Services provides browser-based rendering of Visio diagrams and includes filtering, interaction with objects, and connections to data sources. • With Excel Services, you can secure, manage, and use Excel workbooks as interactive reports rendered in the browser. You can embed workbooks in applications, blogs, and wikis and on the desktop. New programmability features include JavaScript object model and REST API. • PowerPivot and SQL Analysis Services provide powerful reporting and analysis of very large data sets.
- Moduuli 8Delivery Tips:Help students answer the question, “What is the security and management challenge with service accounts in an enterprise?” The answer is passwords. When you change the password of a service account in Active Directory, you must change the password on all instances of the service, otherwise the service will fail to log in and start.Explain that managed accounts are meant to solve that challenge.Remind students that one of the configurations made by the Farm Configuration Wizard was the registration of the managed account for the service applications. In the Walkthrough, you registered a new managed account, CONTOSO\\SP_ServiceApps.Explain registration: You provide SharePoint with the user name and password of the account.Explain password change: You use SharePoint administration tools to change managed account passwords. SharePoint makes the change in Active Directory and changes the password of the service.Explain automatic password change: SharePoint can notify administrators of a password that is about to expire and can automatically change the password.Inform students that this topic is an overview. Module 8 provides all of the details about managed accounts.
- Designing content databasesSLA: Recovery Time Objective; Recovery Point ObjectivePerformance
- Objective: Explain that the web.config file makes an IIS Web site a SharePoint Web application.Delivery Tips:Optionally, open the web.config file for the intranet Web application with Notepad, and show the elements described on the slide.Demonstration Steps:In order to perform this demonstration, you must have demonstrated Create a Web Application in Lesson 2.Switch to Windows Explorer and open the folder, c:\\inetpub\\wwwroot\\wss\\virtualdirectories\\intranet.contoso.com80Right-click web.config, then click Open With,.Expand Other Programs and then click Notepad.Click OK.Point out the elements in: Configuration\\ConfigSections\\SectionGroup name=“SharePoint”Commonly configured elements include:SafeControls – this defines what controls can be put on a SharePoint pageSafeMode – controls which pages can execute inline codeMergedActions – makes modifications to the web.config file based on the actions selected (can be viewed by opening the various files - webconfig.spss.xml)BlobCache – will cache various file types in the location specified (will increase performance of your server, but cache your files)Other elements include:RuntimeFilter: provides configuration used with audience Web part filtering.WebPartLimits: limits the number of Web parts that can be on a page, and the size of the properties of a single web part.WebPartCache: specifies how a Web part will be cached.WebPartWorkItem – controls the timeout of Web parts on a pageWebPartControls – The Data Sheet view of a list allows you to change the data sheet view to something customPeoplePickerWildcards – allows you to be able to find users in various membership providers (LDAP, Windows, Adam, etc.)
- DO NOT PRINTObjective: Enforce the importance of making sure that the SharePoint root is synchronized across SharePoint servers.
- Objective: Present an overview of the three major administrative options: Central Administration, Stsadm, and Windows PowerShell.Delivery Tips:This is an introduction/overview only. Keep it very high level.Relate the discussion to students’ previous experience with Central Administration (in previous modules of the course) and Stsadm (in their previous experience with SharePoint).Introduce the concept that the SharePoint 2010 Management Shell supports both command-line options: Stsadm and Windows PowerShell. If students remember how challenging it can be to always navigate to the \\BIN folder before using Stsadm, they will appreciate the fact that SharePoint 2010 Management Shell includes the path to Stsadm in its path variable, so you can open the Management Shell and immediately start to use Stsadm.
- Objective: Define the administrative roles in SharePoint, from farm administration to site ownership.Delivery Tips:Discuss what it means to be an “administrator” of SharePoint.This slide collects new points and some points made in Module 2, “Creating a SharePoint Intranet,” to create a single discussion of SharePoint administrative roles.Demonstration (Optional)In SharePoint 2010 Central Administration Quick Launch, click Security, and then, in the Users section, click Manage the farm administrators group.Discuss the Farm Administrators group.Open Server Manager and open the membership of the local Administrators group.Discuss the local Administrators group.Close Server Manager.In the Central Administration Quick Launch, click Application Management, and then, in the Service Applications section, click Manage service applications.Click the Managed Metadata Service row. Do not click the link.In the Ribbon, click Administrators.Discuss service application administrators.Click Cancel.Click Managed Metadata Service.Point out the fact that you can assign Term Store Administrators. Use this as an example of a service application feature administrator. Do not go into detail about the Term Store or the MMS at this time. It is discussed in Module 4.Remind students that you discussed site collection owners and the Owners group of a site in Module 2.
- Peilaus = palvelimet listattava kun database lisätään
- Timer Jobs
- LOPPUKurssit ->