Change the default 10 MB limit for saving a site as template

I bumped upon this 10 MB limit today when trying to save a site as a template. Did some research on the net and found that you can change this limit through the following stsadm command:

stsadm -o setproperty -pn max-template-document-size -pv 524288000

This will set a 500 MB limit instead, which is apparently the maximum value you can specify. 

Forms Based Authentication ( FBA) in WSS 3.0 / MOSS 2007 (by MeySun)

I had an issue this week that I was unable to sign in to my personal WSS site. for some reason the popup login screen never showed. I know that my company laptop is heavily secured as well as the network. So if it was a firewall blocking or my IE settings that did not allow the logon, I didn’t care. All I needed was being able to logon to my site.


This brought me to the idea of implementing FBA for my site. I didn’t want to manage users in a SQL database etc. I just needed FBA to authenticato to Active Directory. I stumbled upon a great blog post by meysun (aka Meyyappan Meenakshisundaram).


Here is what he wrote:


1. Configure SharePoint Central Admin 



  • Login to SharePoint Central Admin
  • Go to Application Management / Application Security / Authentication Providers and Change the Web Application to the one which needs to be configured for Forms Based Authentication
  • Click zone / default, change authentication type to forms and enter ActiveDirectoryMembershipProvider under membership provider name ( for example , “ADMembershipProvider”) and save this change

2.Update the web.config of SharePoint Central admin site
 


under <configuration> node


<connectionStrings>
<add name=”ADConnectionString” connectionString=”LDAP://DynamicsAX.local/CN=Users,DC=DynamicsAX,DC=local” />
</connectionStrings>


under <system.web> node


<membership defaultProvider=”ADMembershipProvider”>
<providers>
<add name=”ADMembershipProvider”
type=”System.Web.Security.ActiveDirectoryMembershipProvider,System.Web,Version=2.0.0.0,Culture=neutral,PublicKeyToken=b03f5f7f11d50a3a” connectionStringName=”ADConnectionString”
connectionUsername=”xxx” connectionPassword=”yyy”
enableSearchMethods=”true”
attributeMapUsername=”sAMAccountName”/>
</providers>
</membership>


replace the connectionstring to the one matching your encvironment and replace”xxx” with domainname\username and “yyy” with password


 


3.Update the web.config of SharePoint Web application



  •  Repeat step 2 for the web.config of the SharePoint webapplication to be configured for Forms Based Authentication
  •  Change the authentication in web.config to
    <authentication mode=”Forms”>
        <forms loginUrl=”/_layouts/login.aspx”></forms>
    </authentication>

For more details
http://technet2.microsoft.com/Office/en-us/library/23b837d1-15d9-4621-aa0b-9ce3f1c7153e1033.mspx?mfr=true
http://msdn2.microsoft.com/en-us/library/ms998360.aspx


So, Thanks meysun for your post. It really helped me out !

Configure PDF IFilter in WSS 3.0 (found on Workerthread Blog)

I am playing with a pure WSS environment these last days for my family site and was trying to configure indexing of PDF files on it. Evidently I looked back at one of mu posts to configure this indexing on a MOSS server. When reading my post I noticed the configuration tasks in the Shared Services Provider, etc. As you may know, this is not available to a WSS installation, so I was a little bit stuck. Knowing that I must not have been the first facing this issue, I looked around on the net and found a post at http://workerthread.wordpress.com/2008/01/03/configure-pdf-ifilter-in-wss-30/


 


Here’s the Article:
There are various posts around on setting up MOSS 2007 to use the PDF IFilter, and some stuff on Windows SharePoint Services 3.0 as well.  I’ve found a method which works for me, so I wanted to put this together in one place – not least of all so I can find it when out on site with a client. 


Out of the box neither WSS 3 nor MOSS 2007 will index content located in Acrobat PDF files, so you need to set up the IFilter.  I’ve also found that that PDF files loaded prior to the installation of the filter won’t be re-crawled automatically, so to be on the safe side you might want to kick off a full crawl.


Here is what I’ve found works for WSS 3.0:



  1. First, you need to download the Adobe PDF IFilter 6.0, which you can find at this URL.  You should also get hold of a suitable Icon to use with PDFs, so that when they are listed in a document library they are easily recognisable.  There is a 17 x 17 one available on the Adobe web site here.
  2. Once you’ve downloaded the IFilter, install it on your WSS 3.0 server, and then follow the instructions on registry settings in Microsoft KB Article 927675.  I’ve always found that providing the Adobe IFilter installed properly, the only setting I need to add is the Search Extensions one listed in step 2.  Also note step 5 re stopping and re-starting the search service.
  3. Now you need to set up the Icon file.  If you downloaded the icon file in step 1 above, you will have a file called pdficon_small.gif.  You need to copy this onto your WSS 3.0 server, into drive:\Program Files\Common FIles\Microsoft Shared\Web Server extensions\12\TEMPLATE\IMAGES.
  4. Next you need to edit the XML file which WSS uses to link file extensions to icons.  This file is called DOCICON.XML and is located at drive:\Program Files\Common FIles\Microsoft Shared\Web Server extensions\12\TEMPLATE\XML.  Navigate to that folder and locate the file.  I would suggest making a backup copy first, then opening the file in NotePad.  You need to add a mapping key for PDFs at the bottom of the file, above the </ByExtension> closing tag.  The new key will be <Mapping Key=”pdf” Value=”pdficon_small.gif” OpenControl=””/>  (note that XML is case sensitive so make sure you use same case as previous entries).  Then save the file.
  5. That’s pretty much it, but if you already have PDFs uploaded to your WSS server I would recommend starting a full crawl.  You can do the with STSAdm, the command syntax is Stsadm -o spsearch -action fullcrawlstart .  More on this on TechNet here.