Conf’SharePoint 2013 : sessions plénières AvePoint : Gouvernance et Migration
•Télécharger en tant que PPTX, PDF•
0 j'aime•838 vues
Présentations sur la gouvernance SharePoint et la migration vers SharePoint 2013 (on premise ou online) jouées en session plénière de la Conf'SharePoint 2013
Recommandé
Recommandé
Contenu connexe
Similaire à Conf’SharePoint 2013 : sessions plénières AvePoint : Gouvernance et Migration
Similaire à Conf’SharePoint 2013 : sessions plénières AvePoint : Gouvernance et Migration (20)
Conf’SharePoint 2013 : sessions plénières AvePoint : Gouvernance et Migration
- 1. 1/ Gouvernance SharePoint 2/ Migration vers SharePoint 2013 Antoine Driard, Country Manager, AvePoint France antoine.driard@avepoint.com, 07 86 51 52 96
- 2. Gouvernance SharePoint* *: librement inspiré d’une présentation de Jeremy Thake
- 3. Une histoire parallèle : AvePoint… 2001 : Création d’AvePoint à Jersey City 2002 : Sauvegarde 2003 : Migration 2006 : Haute disponibilité, optimisation 2007 : Offre IBM et NetApp 2008 : Plateforme complète d’administration et sécurité 2010 : Migration depuis Lotus Notes Bureau à Paris 2011 : Support d’Office 365 2012 : Automatisation de la gouvernance 2013 : Conformité, Apps SharePoint, Dynamics CRM…
- 5. Qu’est-ce que la gouvernance ? La gouvernance IT est l’ensemble des règles, rôles, responsabilités et processus qui guident et contrôlent la façon dont le métier et l’IT collaborent pour atteindre les objectifs métier Microsoft - http://bit.ly/nmNSbj
- 6. Trouver l’équilibre Besoins métier et productivité Adoption Technique et réglementation Contrôle
- 7. Qualité
- 8. Sécurité
- 9. Technologie
- 10. Processus
- 11. Suivi
- 12. Pertinence
- 13. “Disponibilité”
- 14. Accessibilité
- 15. Conformité
- 16. Formation
- 17. Adoption
- 19. « UN GRAND POUVOIR IMPLIQUE DE GRANDES
- 20. Conservation
- 21. Prolifération
- 23. Cycle de vie
- 24. Galeries
- 25. Cloud
- 28. Nos approches
- 29. Offre de service: Catalogue prêt à l’emploi Copie ou déplacement de contenu Gestion des permissions Provisioning Modification de contact, paramètres… Gestion du cycle de vie Déploiement de solutions Restauration depuis la corbeille
- 30. Démo
- 31. Migration vers SharePoint 2013 (online ou on premise)
- 32. SharePoint 2013 : comment y aller ? Préparation de la source Préparation de la cible La migration Retours d’expérience Témoignage
- 33. Avant la migration : analyse et préparation Analyse Inventaire Volumétrie Typologie Qualité et pertinence des données Personnalisations Charte graphique Web Parts … Préparation Nettoyage Documents Versions Droits Personnalisations Restructuration Lotissement
- 34. Migrations prévues depuis… Source : Etude AvePoint réalisée fin 2012 auprès de 707 répondants en Europe
- 35. La cible de la migration Cloud On premise ou online? Les deux ? Gouvernance ! (C’est le moment ou jamais) Personnalisations Annuaire Sécurité Architecture logique Offre de service …
- 36. Migration de toutes les métadonnées et propriétés La migration avec DocAve en pratique Outils d’analyse et de “migration à blanc” Mapping de sécurité et de templates, filtrage, restructuration En direct ou planifiée, directe ou hors ligne Migration vers SharePoint 2010, 2013, on premise ou Online Reporting centralisé et audit de TOUTES les actions de migration
- 37. Démo
- 38. Retours d’expérience Fixez les attentes des utilisateurs finaux Analysez le contenu Structurez l’information Évaluez la conformité Réévaluez la sécurité Testez la performance Archivez ou supprimez Tendez vers plus de standard Étudiez les alternatives à la migration
- 39. Démo
- 40. Témoignage:
- 41. Merci
Notes de l'éditeur
- QualityAlong with accountability, quality is also an important factor throughout the content lifecycle.Often content is created, never ever published to version 1.0 or sits at a minor version forever.Regularly content reviews.
- RestrictionsNot all content is created with the expectation it will be visible by everyone in the organization. This is typical for Human Resources department content or Financial data on the company. Having the correct restrictions in place for content is very important.
- A deuxniveaux : les choix pour la plateforme collaborative, et la façon de faire appliquer les directivesCan’t create policies unless you can enforce themTechnical limitations SLAs Complexity of building Platform built in particular way
- Content OwnershipNot just on creation, but for the entire content lifecycle.People come and go in organizations and also transfer roles and therefore are no longer accountable for content in their current role.Responsabilité du responsable métier
- AppropriatenessAlong with ownership and accuracy comes appropriateness. It is an extremely common concern on what content “should” be in SharePoint. Big concerns I hear frequently now are personal documents in users My Sites, Personal Information such as social security numbers in documents, personal photos, boozy Christmas photos…How much trouble would your organization get into if someone posted that on SharePoint? Does everyone have the moral compass in the right place?
- SearchContent needs to be discoverable within the system and technical decisions should not reduce this discoverability.Plusieursfermes, SharePoint, Yammer, Dynamics CRM…
- ComplianceCompliance is a “big” area to cover when it comes to the content lifecycle. Some of the biggest concerns within organizations is social content at the moment. The ability to add status messages to your profile, post comments on profile note boards (facebook walls) or update your user profile without content approval or auditing is a major risk.
- TrainingAdoption is heavily linked to Training. If you want to empower your people, train them first then unlock the keys to the kingdom.
- AdoptionSo with all these requirements, organizations still expect adoption. There is a fine line between how open or closed to make this system. Keeping an system open will technically raise adoption as people don’t feel trapped, but o the other side of the coin it means you cannot enforce your requirements.
- Site Collection Owner and Site Owner essentially are “god mode” within SharePoint Site Collection or Site respectively with no change management or workflow approval.http://en.wikiquote.org/wiki/Stan_Lee 1962 Spiderman
- StorageStorage costs are a big concern to organizations who do not wish to pay for large amounts of expensive SQL specialized SAN storage. The ability to treat content with different priorities of cost is important.
- ProliferationBeing too open can often lead to madness within SharePoint and you’ll end up with Sites upon Sites where the content could have been placed in existing areas.SharePoint URLs are long and hard to remember, everyone has their own naming standard for site URLs.NavigationBuild in some basic pillars for people to create content in and make it obvious where sub sites should be created.
- Geeks are usually the custodian of content. More strategic planning is required up front and locking down areas of SharePoint helps keep this under control. Typically done by Records Managers.Being too open with metadata can cause havoc depending on the culture of the organization. In most cases, there are different types of content creation that apply to different policies e.g. Team project collaboration may not need Content Types but may requireManaged MetadataSome thrive on the Folksonomy approach. More conservative organizations will want to stick to a predefined taxonomy instead.Content TypesCan reduce discoverability but also encourage innovation within content.
- Lifecycle ManagementProliferation of Sites is obviously a key issue, but on top of this Ownership, Accuracy and Retention of content is important.Questions such as:Are you still using this site?Do you still own the site?Are there regulated users using this site?
- GalleriesSite Collection Owners or Root Site Owners will have access to uploading artifacts to the Galleries in the Root Site. This can give Users the ability to customize SharePoint a little too much.Site Template GalleryOften Users create one site and them make a template from it and then create more based on this. This is fine until they want to make a change across 500 already existing sites based on the template. Changing that template does not reflect the instances. Expectations are better set up front on these types of things to ensure these templates are 95% there before provisioning 500 of them.Web Part GalleryList Template GallerySandboxed Solutions GallerySite Collection Owners can upload Sandboxed Solutions in the gallery. These aren’t as powerful as Farm Solutions, but can have significant impact on the customizations that users can perform in SharePoint. Be wary of unlocking this floodgate in your organization without clear vision here.
- SharePoint DesignerBy default, SharePoint Designer is available to all Users if they have appropriate permissions. SPD potentially allows you to do a lot of collateral damage to Page Layouts and Master Pages.Bon pour la personnalisation de workflows,mais à éviter pour la chartegraphique.
- Group ManagementSharePoint Groups can also be controlled by Site Collection Owners and all Site Owners by default. This allows Users to create all sorts of mess and without standards in place potentially thousands of sites with different naming standards and memberships that need to be maintained. SharePoint Group permissions will dictate what members with in these can see and often can lead to users getting access to restricted content.
- Automatiser pour trouver l’équilibre entre contrôle et adoptionMinimiser le code customOffrir des services packagés automatisésReporting et contrôleToday, IT departments must commit to providing collaboration as a fundamental service to the business. Users do not feel inhibited from finding the right platform for collaboration regardless of who is providing the capability (such as Box.net, Dropbox, Office 365, and Google Docs). IT is competing to provide this service first for users, and similar to implementing governance standards for SharePoint, IT needs to support grass-roots collaboration with ease-of-use wherever it may begin. AvePoint is focused on getting your users excited and collaborating quickly, so get ahead of the problem by making our governance solutions part of your rollout or existing collaboration strategy.(Click)Utilize DocAve for Semi-automated SharePoint Governance Enforcement:For organizations looking to simplify and streamline the deployment, monitoring, and enforcement of SharePoint governance policies, AvePoint's DocAve Software Platform helps organizations: Data Protection to Provide information technology (IT) assurance by improving quality of services and minimizing business disruptions Enable security and compliance for business content by helping standardize and enforce corporate IT policies End to end SharePoint Content Lifecycle Management solutions to:Increase business productivity by delivering high-performance global collaboration. Improve operational efficiency while reducing total cost of ownership (TCO) ReportingUnderstanding how your deployment is being utilized by end-users is vital to efficient management and governance. Having access to accurate and timely answers to the following questions is critical to intelligent decision making: – Who accessed what content, and when?– What are the deployment’s most popular search terms?– Who are the prolific producers of content and who are the consumers of content?– How does Site A activity compare to that of Site B and Site C?– What is the average time necessary for a given workflow to complete?(Click)Comprehensive governance solution with Governance Automation by provide SharePoint as a Service and Automating your Governance Policy Enforcement:DocAve Governance Automation allows organizations to provide SharePoint as a service to business users, encouraging the adoption of SharePoint by automating the way users provision, manage, and modify sites and permissions. Through an intuitive service catalog, which can be accessed from a browser-based management console or directly through SharePoint, Governance Automation helps to ensure all requests are fulfilled within established governance policies by providing a fully auditable business approval process.Service Requests:Encourage end users to adopt SharePoint and enable them to request resources, such as a SharePoint site or site collection, by exposing all available options through an intuitive service catalog that can be accessed directly through SharePoint. Governance Automation resolves ambiguity around provisioning, managing, and archiving sites and site collections and simplifies the way business users interact with IT.Policy Driven:Governance Automation can limit the available options and service levels for site availability, storage allotment, and lease expiration by associating backup, storage, archiving, permissions, and auditing configurations with a policy level (e.g. bronze, silver, and gold), and associate each of those options with charge back to the business departmentROI and Chargeback:Governance Automation enables chargeback calculations to functional business units or departments through the generation of insightful analytics detailing the accountable-business users, classification, and storage usage of site collections and sites for SharePoint assets.
- Provisioning/ Sites, Collections, Mysite, BibliCycle de vieAdmin : modifier contacts, paramètres, métadonnéesDéplacement de contenuSécuritéajout, suppression, clonageWithin the Governance Automation Service Catalog, there will be various Services available for business users to request. At launch, the Site collection request and Site request services were available. In service pack 1, policies will be available for the Auditing rules and Storage Manager rules for Remote BLOB Storage.[CLICK]In subsequent service packs, scheduled every quarter, more services will be made available which have been prioritized based on feedback by our customers’ demands.Each of these services policies leverage our underlying DocAve 6 platform components.To illustrate this, as part of our Site collection services, you can define a policy to configure which Granular Backup plan and Archiver Rules the site collection should adhere to.
- 2010 vers 2013 considérablement amélioré OOTB
- Installing an agent allows us to utilize additional APIs, and speed up the migration process
- Gouvernance / Centre de services