Aucune remarque pour cette diapositive
Pas utilisé ni pour:Le Blob CacheLe Cache d’affichage (Output caching)Ces services existent déjà sur les frontaux
The service is installed and running by default after installing SharePoint. It will be started on all machines in the farm except for SQL Server. You can design a set of servers specifically for running the cache service by turning the service off on some servers and leaving it running on others. However even though you can just stop it from the services on server page, you really should NOT do that. There are several PowerShell cmdlets just for managing the caching service that should be used instead. That will ensure a minimal temporary loss of cached data and reduce the overall load on your farm.******************************Mostly my notes, some from page 6.
The farm account is used as the service account for the distributed cache service; you will see it in the Services applet on the SharePoint server as “AppFabric Caching Service”. Just like the user profile service in SharePoint 2010, the account needs to be a local admin during setup. After you’ve finished installing SharePoint you can reduce those local privileges for the farm account.Pg. 7
These are some general server sizing guidelines to use with servers hosting the distributed cache service. First, cache servers use about 50% of the allocated cache memory for overhead. Second, the maximum amount of RAM we recommend per cache server is 16 GB. You can go higher than that, but if you do when we need to flush the cache it may take so long that the cache will appear to hang. It’s worth noting that by default when you install SharePoint we allocate 5% of the memory on the server to the cache.Next you should allocate 2GB of RAM to the OS. So on a machine that has 16GB of RAM, that leaves 14GB of RAM for the cache. Given that 50% of that is used for overhead, that leaves you 7GB of storage for data. We’ll be working on formulas to help you determine how much storage your farm will need overall for caching. Once you have that, then you can use the formula above to determine how much storage you will have per server, and then divide that by the total storage required in the farm. That will tell you how many cache servers you need in the farm.*************************************
Les donneesetantdivisees entre les serveurs, Si un serveur tombe en panne de façon inattendue, les performances des utilisateurs vont souffrir jusqu'à ce que d'autres serveurs deviennent remplis avec les données qui ont été perdues.Si vous savez que vous allez mettre un serveur cache vers le bas, vous devriez le faire avec élégance avec la cmdlet Stop-SPDistributedCacheServiceInstanceCela permet de copier les données vers d'autres serveurs de cache pour minimiser l'impact sur les performances
Accès à distance et Pare-feu Registre: Vous pouvez rencontrer ce problème si vous avez pare-feu activé et il ya un problème pour l'accès à distance au Registre entre les serveurs SharePoint. Cela signifie, nous devons nous assurer que le "service Registre distant" doit être démarré dans tous les serveurs SharePoint avant de brancher la batterie de serveurs SharePoint pour configurer le cache d'AppFabric. Si vous avez un pare-feu, puis d'autres configurations peuvent être nécessaires car il peut bloquer la connexion.Allocation de mémoire maximum pour le cache: Un minimum de 8 Go et un maximum de 16 Go peut être allouée au cache. Sur un serveur qui possède plus de 16 Go de mémoire physique totale, allouer un maximum de 16 Go de mémoire pour le service de cache distribué. Également la répartition de la taille de mémoire cache doit être inférieure ou égale à 40% de la quantité totale de mémoire sur le serveur. Si vous avez besoin de plus de mémoire, vous pouvez configurer le service de cache distribué pour fonctionner sur plusieurs serveurs d'application.Allocation de mémoire: Vous devez vous assurer que l'allocation de mémoire affecté au service de cache distribué est le même sur tous les serveurs qui exécutent le service de cache distribué. Données mises en cache sont stockées sur un serveur, et non pas les deux serveurs.Autres services: Ne pas faire fonctionner les services suivants sur le même serveur qui exécute le service de cache distribué: SQL Server, Project Server, Excel Services et les services de recherche.Health Monitor: Examen SharePoint Server 2013 Règles de santé pour les questions de service Distributed Cache.
Microsoft has an exciting vision for Enterprise Social: we want to help companies transform their business with Enterprise Social. but in order for that to happen, two things are necessary: First, it can't just be a destination. Social must be a natural part of how we work, it has to be seamlessly woven into the tools you use everyday to get your work done. It has to be easy, frictionless and in-context. Microsoft is in a unique position because we own a fantastic set of assets: social, collaboration, email, and unified communications; and we want to combine these tools to create new experiences that help people get things done. We want to have a tool that will allow you to start a conversation in a newsfeed, ping one of the participants on IM, escalate to voice and video, follow-up over email, and circle back to the original conversation with an update; we want to have the context of those conversations follow you across those tools, and have everyone involved to be able to participate in the interactions regardless of where they are or what device they have with them. Some of it is already possible today and we aim to continue and build this “connected experiences” scenario and make it available to everyone. Microsoft has the depth and breadth of capabilities to realize this vision. Second, in order to be successful, social must be a part of a platform that IT can rely on to manage and secure.The information in a social network is some of the most valuable intellectual property in the company, and their platform needs sophisticated security, management and compliance capabilities that don't get in the way of the users but do allow IT to sleep better at night.
Yammer doesn’t replace SharePoint – and SharePoint doesn’t replace Yammer; together they both provide unique capabilities that will enable Microsoft to transform the way that we get work done.Yammer will help us break down silos in organizations and get people talking - not just having superficial conversations but having conversations that will be crucial to helping business achieve their goals; as social matures so does the way that people use it and the value they get out of it. Yammer helps to drive adoption and get the ball rolling.SharePoint brings a huge amount to the game – it will help organizations plan and organize how work will get done. It will help to bring together information from systems across the enterprise, and then provide BI capabilities that will help IW make better decisions.Combined – SharePoint and Yammer will truly help to transform the way that we get our work done.Land that people should think about SharePoint and Yammer as complementary and better together
What you can do today, what you’ll be able to do in the near future (within the next year), and our vision for the future.Today: customers can connect the two today with the Yammer web parts and Yammer Open Graph capabilities. Tomorrow: We’re working to build a strong foundational platform that will allow us to quickly iterate changes. To do this we’re working on some key areas first that will enable our future vision: integrated document management through SkyDrive Pro, Aggregating the SharePoint and Yammer feeds, and investing in unified identity, ensuring that users have a great single-sign-on experience.Future: After the work on key foundational aspects, we will take advantage of our new, 90-day release cycle for SharePoint Online and Office 365 to add more and more capabilitiesover time to create connected experiences that combine social, collaboration e-mail, unified communications and an enterprise class platform you can rely on for security, management and compliance.
To align with our vision and roadmap, we’ve made changes to Yammer packaging and pricing. First, Yammer standalone. We're committed to maintaining standalone versions of Yammer for customers who just want a best-in-class enterprise social network. Yammer has historically offered four different options, and we've simplified that to two: a free version called Yammer Basic and a paid version called Yammer Enterprise. Second, Yammer and SharePoint Online. We believe that social and collab are two sides of the same coin, and as the roadmap demonstrates we're working toward a future where they're tightly integrated. To reinforce that notion, we will be adding Yammer to SharePoint Online starting March.And finally, Yammer and Office 365. we envision a future where social is everywhere -- and where people work together using new experiences that combine social with collab, email, and unified communications. As a first step in delivering on that vision, we're adding Yammer to all of our Office 365 Enterprise offerings (E1 through E4) for EA customers.