SharePoint Secrets

In this post I just write down some advantages and disadvantages of the group types and let you choose what kind fits better for your needs. SharePoint Group Active Directory Group Members of this group can be added/removed from within SharePoint. The permission to add or remove users from the group can be delegated to SharePoint users. Members of this group can be managed within Active Directory. Only Active Directory administrators have the permission to modify group memberships. Members of this group can be visible to users. Members of this group are not visible to users. Cannot contain another SharePoint group as member. Can contain another Active Directory Group. Must have a unique name on site collection level. The name is the unique identifier of the group Can cause serious problems in lage scale scenarios: A user might only be a member of 1024 Active Directory groups (recoursively). If this number is reached the user is no longer able to log on to Windows. Can contain SharePoin...

The people picker will by default show the users in the forest that the SharePoint farm is installed (that is, the resource forest). According to the documentation Peoplepicker-searchadforests: stsadm property (Office SharePoint Server) – it should also display users in all two way trusted domains and forests but you can still use the stsadm command to be sure. For one way trusted domains (or forests) you will need to do some extra stuff. In a one way trust you will probably need to specify a user name and a password. This requires you to run the setapppassword operation first (For more details see Select users from multiple forest domains ) - STSADM.exe -o setapppassword -password key. The key you specify here is used to encrypt the password you will use to establish the people picker connection. Note: run this on every WFE of your farm. Next you need to add the forests/domains you are going to query using the people picker. stsadm –o setproperty –pn peoplepicker-searchadforests –pv ...

STSADM EXPORT / IMPORT While trying take backup i got following error message 'Failure decompressing data from a cabinet file'. The resolution to this is to use stsadm to do the export (and subsequent import), and specify the attribute -nofilecompression. stsadm -o export -url http://yoururl/youroldsite -includeusersecurity -nofilecompression -filename C:\yourdirectory stsadm -o import -url http://yoururl/yournewsite -includeusersecurity -nofilecompression -filename C:\yourdirectory

when trying to activate "Office Sharepoint Server Publishing Infrastructure" on the site collection features page, I end up with the following error : Exception occurred. (Exception from HRESULT: 0x80020009 (DISP_E_EXCEPTION)) These STSADM commands allowed me to enable the publishing infrastructure on a particular site collection that was generating the error when I tried to activate. - "PublishingPrerequisites" (stsadm -o activatefeature -filename PublishingPrerequisites\feature.xml -url http://MyUrl) stsadm -o activatefeature -filename publishing\feature.xml -url http://URL -force stsadm -o activatefeature -filename publishingresources\feature.xml -url http://URL -force stsadm -o activatefeature -filename publishingSite\feature.xml -url http://URL -force stsadm -o activatefeature -filename publishingweb\feature.xml -url http://URL -force stsadm -o activatefeature -filename publishinglayouts\feature.xml -url http://URL -force stsadm -o activatefeature -filename ...

It doesn’t seem there is a built-in way in MOSS/WSS to delete all list items from a list without deleting the entire list. A workaround is to save the list a a template without content, delete the list and recreate it using the template. However, there is a gl-deletelistitem option in STSADM Custom Extentions that can be used. It works well but it is rather slow so for large lists the template method may still be faster. Here's an example of how to delete a list passing in the force parameter: stsadm –o gl-deletelist -url "http://intranet/Documents/Forms/AllItems.aspx" -force If you receive error Exception from HRESULT 0x81070215 when you open a list or access the SharePoint site manager, a list has not properly been deleted and is in a corrupted state. You can change the corresponding custom list definition after you have deleted the list to fix the problem. Because the SharePoint pages don’t allow you to delete the list, you have to use the STSADM program’s forcedeletel...

When trying to save a site template and move it to another server while retaining the content but the size of the site is limitation to save as template. By default there is a 10MB size limitation built in. If you try to save the list as a template that is larger than 10BM you will get the following error: “ The list is too large to save as template. The size of a template cannot exceed 1048760 bytes “ How to increase template size : Run the following stsadm command (from c:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\Bin directory) replace the propertyvalue to the new maximum size (in bytes) stsadm -o setproperty -propertyname max-template-document-size -propertyvalue 50000000 Note: The above command to increase the max size of both site and list template.