Ana içeriğe atla


2010 tarihine ait yayınlar gösteriliyor

PowerShell Commands for SharePoint 2010

Here are some (over 400) PowerShell™ commands for SharePoint 2010! These can be run remotely (Powershell 2.0). Stsadm will still be functional in SharePoint 2010. Powershell is not DOS based. Its .NET based. Windows PowerShell™ is the new command-line interface and scripting language specifically designed for system administrators that will be used for Microsoft® SharePoint® Server 2010 administration. Although both Cmd.exe and Stsadm.exe environments will be maintained for backward compatibility, SharePoint Server 2010 command-line administration will use Windows PowerShell. For practical purposes, you can view Windows PowerShell as complementing Cmd.exe in the Windows administration context and superseding Stsadm.exe for SharePoint administration. You might ask yourself, What’s so unique about Windows PowerShell? Well, unlike most command-line systems that accept and return text, Windows PowerShell supports and uses XML and objects. XML and object support is a pretty major change

SharePoint 2010 Performance and Capacity planning

For those wanting to dig deeper into SharePoint 2010 products performance and Capacity planning, Microsoft has published some very good documents on performance tests, results and recommendations. Again, this is for those Admins who want to dig deeper into SharePoint 2010. It could help if you are creating design documents or archtecture for SharePoint 2010 for your organisation. Even if you arent looking yet, I suggest you book mark this page. One day you may need it! I know I have and would like to share it with you! These documents contain scenario based testing of various SharePoint 2010 Service Applications and features. They discuss recommendations by Microsoft on hardware resources, architecture and configuration to maximise and enhance the SharePoint 2010 experience. AccessServicesCapacityPlanningDoc.docx BCSCapacityPlanningDoc.docx DesigningLargeListsMaximizingListPerformance.docx ExcelServicesCapacityPlanningDoc.docx InfoPath2010CapacityPlanningDoc.docx

SharePoint 2010 - Important StatusStatus: This page has been declared a record or placed on hold and is locked as read-only

In SharePoint 2010 , you may experience this message on your page that you are trying to edit/view: Important StatusStatus: This page has been declared a record or placed on hold and is locked as read-only Solution: 1. Ensure that no other users have checked-in the page. You may have to ensure that the page has been Checked-out for you to to edit the page. 2. Ensure you have the appropriate permissions to edit the page.

SharePoint 2010 Search issue Internal server error exception. Troubleshoot issues Correlation ID

When you search in SharePoint 2010 , you may get the following error: Error Internal server error exception Troubleshoot issues with Microsoft SharePoint Foundation. Correlation ID: de2996f1-a6c9-42fb-a6da-e5fc7d769069 Solution : You will have to install the following hotfix For Windows Server 2008 R2, Hotfix for.NET Framework 3.5 SP1 that provides a method to support the token authentication without transport security or message encryption in WCF ( ).

Remote BLOB Storage – RBS SharePoint 2010

Microsoft SharePoint 2010 caters for farms with large storage needs. SharePoint 2010 has implemented RBS – Remote Storage BLOB. With RBS, you can store BLOBs from the all_docs table and customised pages in the database stored in different location from the database, such as a file system in your network! This reduces the amount of database storage in SQL. To use RBS, a “provider” is required. The RBS provider architecture is ‘plug n play’ with SharePoint 2010. This means that third-party vendors can create and sell their own RBS provider products commercially with specific capabilities. (idea!). For example, a third party backup vendor can use an RBS provider as part of their backup and restore capability. The RBS architecture provides another degree of freedom for the storage of content. Its intention is to be used natively by SharePoint during the upgrade process and by third party vendors that provide storage benefits as a service.

SharePoint 2010 error when trying to delete a managed account: An object in the SharePoint administrative framework, SPManagedAccount Name=managed-account could not be deleted because other objects depend on it. Update all of these dependants to point to null or different objects and retry this operation.

After deleting a Service Application, you may want to clear up the corresponding managed account that you created for the Service Application. You may run into this error when attempting to delete the managed account in SharePoint Central Administration: An object in the SharePoint administrative framework, SPManagedAccount Name=managed-account could not be deleted because other objects depend on it.  Update all of these dependants to point to null or different objects and retry this operation. Solution: Remove the dependency, which is a Service Application Pool that may depend on this managed account. Get-SPServiceApplicationPool (to get a list of the Application Pools, you will need to take note of the name for the next powershell cmdlet). Remove-SPServiceApplicationPool (then enter the name of the Application Pool). Remove the Managed account via Powershell or through the GUI Get-SPManagedAccount Remove-SPManagedAccount

SharePoint 2010 - Send Notification on Item Approved/Rejected (when Content Approval Status is changed)

In SharePoint 2010 new improvements are made for better event receiving management. Few new event handlers are added for site, web, list, listitems etc. However, One thing that I think badly needed was the content approval events  for list items. Nowadays content approval has become an integral part of content management system. Requirements has come up to do more work on content approval/reject. But unfortunately, SharePoint list/library doesn’t have events like ContentApproved, ContentRejected, ContentRequestedForReview so that user can tap the events to do their own work on content approval status changes. So it seems we need to do a lot of works manually to send notifications on content approval status changes. Problem: Approving Status change events Missing One of my client wanted to get notification on the following scenarios: 1. On Item Add/Update: If a user edit an item and item goes to pending status as the item needs approval, the approving teams need to be notified

Move SharePoint Site/Web From One Development Server to Another

Sometimes, we need to move the site from one server to another, usually in development environment. In that case its required few steps to make sure you have moved your site in new server. I have successfully move my sites and I’m pointing here the exact steps that worked for me. Backup the site or export the web First of all you need to take backup of the site (if you want to move site collection). If you want to move a single site then export the web contents. For site backup use the following command: Backup-SPSite -Identity -Path "C:\Backup\BackupFile.bak" -Confirm:$false For exporting web use the following command. Export-SPWeb –Identity –Path “C:\Backup\BackupFile.cmp” –Confirm:$False For more on these commands follow MSDN link . Create Dummy site or web on the destination server to overwrite Before restoring or importing site/web you need to create a dummy site/web on the destinati

SharePoint Error: The exported site is based on the template STS#1 but the destination site is based on the template STS#0

Today I was trying to export one of my site from one Virtual machine to another. First I took a export of the web from my source server and then I tried to import the content in the destination server. And then the import failed with the error “ The exported site is based on the template STS#1 but the destination site is based on the template STS#0 ”. I couldn’t remember the template with which I created the source site but I took for granted from the error message that the source and destination web are not created from the same template. After googling I finally found import will only work if source and destination web are created from the same template. In my case the source site was created from Blank Site template (STS#1) but the destination site was created from Team site template (STS#0). So I deleted the destination site and recreated with the source template and the import was successful. For full lists of web site templates you can follow Aravindhan’s   posts.

SharePoint 2010 - Rename Site Url

Sometimes in development environment and even in production you may need to rename a site url. For example you have planned a site with URL in Development or in Production. Later you have decided to rename the site url to . There’s no shortcut way to do that in SharePoint. You need to delete the existing web application for url and create a new one with url . 1. Backup the site collection first Run the following powershell command to backup site. Backup-SPSite –Identity SiteUrl –Path BackupLocation 2. Delete the existing site from central admin. Navigate to central admin and delete the web application including database and IIS site as shown below: 3. Create the a new site with new Url (say ) Now create a new web application with the new url in host header as shown below: 4. Restore the backup on the new site Finally restore the backup taken on step 1 overwriting the new sit

Linq to SharePoint

SharePoint 2010 has added new Linq extension called Linq-to-SharePoint similar like Linq-to-Sql. In Linq to Sql, when you Visual Studio generate classes based on your database schema, under the hood a tool called SqlMetal is used. Though VS generates classes for you, you can use SqlMetal outside of VS for your own purpose. Linq to SharePoint is new extension which allows to generate DataContext (having classes representing lists) based on your sharepoint lists using SPMetal and you can use the DataContext for manipulating SharePoint list in an object-oriented fashion. So you don’t need to worry about CAML or SharePoint Object Model. The steps to work with Linq-to-SharePoint is easy. Let’s dig it deeper. Generate Linq-to-SharePoint DataContext class : To use Linq to SharePoint you need to use SPMetal to generate Linq-To-SharePoint class. You can find the SPMetal in the location “C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN”. You can run the command fr