tailieunhanh - Thủ thuật Sharepoint 2010 part 14

Triển khai kiểm soát SharePoint 2010 tàu với hơn một số ít các công cụ sẽ giúp bạn để giữ nó trong tầm kiểm soát - từ các công cụ ngăn chặn và / hoặc phát hiện lừa đảo để triển khai xây dựng trong điều tiết khả năng đó sẽ giúp ngăn chặn dữ liệu bị mất và phá hủy các danh sách quá khổ từ nông trại của bạn . | 80 CHAPTER 3 ARCHITECTURE AND CAPACITY PLANNING CONTROLLING DEPLOYMENTS SharePoint 2010 ships with more than a handful of tools that will help you to keep it under control from tools that block and or discover rogue deployments to built-in throttling capabilities that will help to prevent lost data and oversized lists from destroying your farm. Blocking Rogue Deployments SharePoint especially Foundation is sneaking into more and more enterprises. Business units who don t want to go through the proper channels have been caught standing up their own SharePoint servers in alarming numbers. That wouldn t be so horrible but these rogue servers often house business-critical data but have no backups and no redundancy. IT generally doesn t find out about them until it is too late and someone has already lost critical data. To help prevent this SharePoint 2010 has implemented a new registry key HKLM Software policies microsoft SharePoint blocksharepointinstall If you set the dword blocksharepointinstall equal to 1 the installation of SharePoint is blocked. The key challenge is getting this registry key added to all of the machines in your farm in time as it is not there by default. It will not affect servers that already have SharePoint installed. Also you need to keep this key a secret between you and this page. If a user knows to look for it they can remove it from the registry and then install SharePoint anyway. If you are considering using this key it is probably easiest to create a group policy object that adds it to all the machines in your domain. Registering SharePoint Servers in Active Directory Rogue SharePoint servers have become an issue in many large enterprises but sometimes blocking them as described in the previous section is considered too drastic. Wouldn t it be great if you could keep track of every server in your Active Directory that someone installed SharePoint on so you could find the culprits and smack them on the hand with a ruler With a little