You can check the current mode by using the SPContext.Current object:
if (SPContext.Current.FormContext.FormMode == SPControlMode.Edit)
{
}
If you want implement a custom WebControl you can use Microsoft.SharePoint.WebControls.SPControlMode.Display to determine if your custom WebControl is in display or edit mode.
Create a new custom template with a unique Name attribute in your working copy of AlertTemplates.xml (You can copy paste the entire section with Name SPAlertTemplateType.GenericList, change the name and modify the sections you want to). Modify the template as necessary. After restarting IIS, write object model code to set the list alert template.
SPAlertTemplateCollection ats = new SPAlertTemplateCollection((SPWebService)(WebApplication.Parent)); //give appropriate values for WebApplication
list.AlertTemplate = ats["name from above"];
list.Update();
<PropertySchema> <Fields> <Field Name="RegEx" DisplayName="Regular Expression" MaxLength="255" DisplaySize="15" Type="Text"> </Field> <Field Name="MaxLen" DisplayName="Maximum length" MaxLength="3" DisplaySize="3" Type="Integer"> <Default>255</Default> </Field> <Field Name="ErrMsg" DisplayName="Validation message" MaxLength="255" DisplaySize="30" Type="Text"> <Default>The value does not match the regular expression</Default> </Field> </Fields> </PropertySchema> |
<?xml version="1.0" encoding="utf-8" ?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/"> <Field ID="{54634385-A8AC-4898-BF24-E533EB23444F}" Name="RegExField" DisplayName="RegExField" StaticName="RegExField" Group="Grepton Fields" Type="SPFieldRegEx" Sealed="FALSE" AllowDeletion="TRUE" SourceID="http://schemas.microsoft.com/sharepoint/v3/fields" Description="This is the RegEx field" RegEx="[0-9]" MaxLen="20" ErrMsg="Error!"/> </Elements> |
Feature definition with Id 6fd6ca04-3ac3-490f-b22f-4461a2253001 failed validation, file 'feature_definition2.xml', line 5, character 299: The 'RegEx' attribute is not allowed. |
<xs:complexType name="FieldDefinition" mixed="true"> ... <xs:attribute name="Decimals" type="xs:int" /> <xs:attribute name="Description" type="xs:string" /> ... <xs:attribute name="DisplayName" type="xs:string" /> ... <xs:attribute name="FillInChoice" type="TRUEFALSE" /> ... <xs:attribute name="Hidden" type="TRUEFALSE" /> ... <xs:attribute name="Max" type="xs:float" /> <xs:attribute name="Min" type="xs:string" /> ... <xs:attribute name="Name" type="xs:string" use="required"/> ... <xs:attribute name="ReadOnly" type="TRUEFALSE" /> ... <xs:attribute name="Required" type="TRUEFALSE" /> ... <xs:attribute name="Title" type="xs:string" /> <xs:attribute name="Type" type="xs:string" use="required" /> ... <xs:attribute name="ID" type="UniqueIdentifier" /> <xs:attribute name="Group" type="xs:string" /> <xs:attribute name="MaxLength" type="xs:int" /> <xs:attribute name="SourceID" type="xs:string" /> <xs:attribute name="StaticName" type="xs:string" /> ... <xs:anyAttribute namespace="##other" processContents="lax" /> </xs:complexType> |
<?xml version="1.0" encoding="utf-8" ?> <Elements xmlns="http://schemas.microsoft.com/sharepoint/" > <Field ID="{54634385-A8AC-4898-BF24-E533EB23444F}" Name="RegExField" DisplayName="RegExField" StaticName="RegExField" Group="Grepton Fields" Type="SPFieldRegEx" Sealed="FALSE" AllowDeletion="TRUE" SourceID="http://schemas.microsoft.com/sharepoint/v3/fields" Description="This is the RegEx field" xmlns:RegEx="[0-9]" xmlns:MaxLen="20" xmlns:ErrMsg="Error!"/> </Elements> |
But I faced another problem. Although this XML passed schema Validation, It didn't update extended attributes. After investigations I found only way to do that create event receiver for activation.
public class LookupFeatureEvents : SPFeatureReceiver |
To verify your name has changed look at the Welcome message. It should say 'Welcome Your Name' instead of your domain\username.
This tip is not for Moss 2007 but for WSS v3 ! It won't work with Moss !With Moss, you have 2 ways to modify profile information:
Custom Active Directory Filter
To limit the search to a custom AD filter use the STSADM property peoplepicker-searchadcustomfilter
This property is new in SP1 and when a people search is executed it will return results that only match the combination of the built in query and the custom filter that is defined for the site collection.
To create a custom filter which will only return users with a title of Vice President run the following command for their site collection.
stsadm -o setproperty -url http://server/sites/vp-site -pn peoplepicker-searchadcustomfilter -pv ((Title=Vice President))
There is also a similar property with slightly different functionality called peoplepicker-searchadcustomquery. This command is also available pre-SP1 however you should ensure that the Active Directory attribute that is being queried is indexed; otherwise there may be performance problems.
Search only within a site collection
This option is suitable to a classic extranet environment where the internal and external user accounts are in the active directory however you do not want the extranet users to be able to search and browse the directory listing. Note that this is not 100% secure, users can still search Active Directory using a fully qualified logon name, regardless of this property setting. To only list users who have been added to a site collection use the property - peoplepicker-onlysearchwithinsitecollection. As an example:
stsadm -o setproperty –url http://extranet.company.com/sites/project1 –pn peoplepicker-onlysearchwithinsitecollection –pv yes
Consider for this site collection there is an AD user account: 'Gavin Adams COMPANY\gadams)' who is not a member of the site collection and the user 'John Doe (COMPANY\jdoe)' is already a member of the site collection. The behaviour that the users will see when they add a user to the site is as follows.
Search only within an AD OU
To limit the search to a path with AD (ie an OU) use the operation setsiteuseraccountdirectorypath
This operation is new in SP1. Once this is set for a site collection no other users can be added to the site collection that are not within that OU. Note that only one OU path can be specified per site collection. An example of this command is:-
stsadm -o setsiteuseraccountdirectorypath -path "OU=Employees,DC=Company,DC=com" –url http://server/sites/teamsite
Often administrative user accounts are in a different OU from the users for a site collection, therefore after the above operation has been applied to a site collection, the property peoplepicker-serviceaccountdirectorypaths is used to define the location of the administrator accounts. For example:-
stsadm -o setproperty -url http://server/sites/teamsite -pn peoplepicker-serviceaccountdirectorypaths -pv " OU=MOSS-Gods,DC=Company,DC=com
Non Windows Accounts only via FBA
If you have a web application that is configured to use forms based authentication and the account and membership provider is not Active Directory (eg a SQL database), then the property peoplepicker-nowindowsaccountsfornonwindowsauthenticationmode can be set against the web application or zone so that the people search will not return any active directory user accounts.
An example of the command with a web application https://extranet.company.com would be:
stsadm -o setproperty -url https://extranet.company.com -pn peoplepicker-nowindowsaccountsfornonwindowsauthenticationmode -pv yes
Note:
To use peoplepicker-searchadforests with credentials, which you need to specify if you don’t have two-way trusts in place, you must first set an encryption key:
stsadm.exe -o setapppassword -password key
This sets a key that will be used to encrypt/decrypt the password in the content database. Failure to do this results in a “command line error” message.
Secondly, the peoplepicker runs under the credentials of the application pool the site is running in(password of this credential user). Make sure the application pool identity is a domain account with the right permissions.
The databaserepair operation uses the following parameters:
The syntax that the Stsadm.exe command-line tool and the databaserepair operation uses is as follows:
It summarizes the most-common issues with SharePoint, how to avoid them, and how
to fix them. Here is a list of topics:
The first recommendation is to make sure that you have SP1 installed. SP1 has
over 2500 fixes, and can go a long way to helping you avoid issues.
One of the most common issues with SharePoint farms is runaway transaction logs
associated with the SQL Server databases. This is really not a SharePoint issue,
but a SQL Server issue. This issue is caused by the fact that most SharePoint
databases are created in Full-Recovery mode. This means that SQL Server retains
a log of every transaction that occurs on the database since the last database
backup. If you never backup your SharePoint databases, then the transaction log
will continue to grow until all the disk space is used up.
Step 1: Backup the Transaction Log manually from the UI. This will truncate
the log, but not shrink it.
From
http://support.microsoft.com/kb/873235
When the transaction logs grow to an unacceptable limit, you must immediately
back up your transaction log file. While the backup of your transaction log
files is created, SQL Server automatically truncates the inactive part of the
transaction log. The inactive part of the transaction log file contains the
completed transactions, and therefore, the transaction log file is no longer
used by SQL Server during the recovery process. SQL Server reuses this
truncated, inactive space in the transaction log instead of permitting the
transaction log to continue to grow and to use more space.
Step 2: Manually shrink the log file from the UI.
From
http://support.microsoft.com/kb/873235
The backup operation does not reduce the log file size. To reduce the size of
the transaction log file, you must shrink the transaction log file. To shrink a
transaction log file to the requested size and to remove the unused pages, you
must use the DBCC SHRINKFILE operation. The DBCC SHRINKFILE Transact-SQL
statement can only shrink the inactive part inside the log file.
Option 1: Switch to Simple recovery Mode for non-production SharePoint
databases.
This will prevent the transaction log from growing because simple recovery mode
does not keep transaction history. Use the following SQL Statement:
USE Master
SELECT Name, Recovery_Model_Desc FROM Sys.Databases
ALTER DATABASE [name] SET RECOVERY SIMPLE WITH NO_WAIT
Option 2: Create a database maintenance plan for all SharePoint databases
Creating the Database Maintenance Plan
1. Open SQL Server Management Studio
2. Right click the SQL Server Agent and select Start from the context menu.
3. Expand the tree and select Management►Maintenance Plans
4. Right click the Maintenance Plans folder and select Maintenance Plan Wizard
from the context menu.
5. On the Welcome screen, click the Next button.
6. On the Select Plan Properties screen, name the plan “MOSS Maintenance”
7. Click the Change button
8. Modify the schedule (daily recommended) and click the OK button.
9. Click the Next button
10. On the Select Maintenance Tasks screen, check the following tasks:
- Check Database Integrity
- Reorganize Index
- Update Statistics
- Clean Up History
- Backup Database (Full)
11. Click the Next button.
12. On the Select Maintenance Task Order screen, click the Next button.
13. On the Define Database Check Integrity Task screen, drop the list and select
all of the SharePoint databases.
14. Check the Include Indexes box.
15. Click the Next button.
16. On the Define Reorganize Index Task screen, drop the list and select all of
the SharePoint databases.
17. Check the Compact Large Objects box.
18. Click the Next button.
19. On the Define Update Statistics Task screen, drop the list and select all of
the SharePoint databases.
20. Select the All Existing Statistics option.
21. Select the Full Scan option.
22. Click the Next button.
23. On the Define History Cleanup Task screen, click the Next button.
24. On the Define Back Up Database (Full) Task screen, drop the list and select
all of the SharePoint databases.
25. Check the box titled “Create a subdirectory for each database”.
26. Change the backup location, if desired.
27. Click the Next button.
28. On the Select Report Options screen, click Next.
Creating the Transaction Log Maintenance Plan
If this installation is not a production environment, consider changing the
recovery mode for all databases to SIMPLE using the following
ALTER DATABASE [name] SET RECOVERY SIMPLE WITH NO_WAIT
1. Open SQL Server Management Studio
2. Right click the SQL Server Agent and select Start from the context menu.
3. Expand the tree and select Management►Maintenance Plans
4. Right click the Maintenance Plans folder and select Maintenance Plan Wizard
from the context menu.
5. On the Welcome screen, click the Next button.
6. On the Select Plan Properties screen, name the plan “MOSS Log Maintenance”
7. Click the Change button
8. Under the Frequency section, Select Daily from the Occurs drop-down list
9. Under the Daily frequency section, select the Occurs Every option.
10. Set the Start Time to 9:00:00 AM.
11. Set the End Time to 5:30:00 PM
12. Click the OK button.
13. Click the Next button.
14. On the Select Maintenance Tasks screen, check Backup Database (Transaction
Log)
15. Click the Next button.
16. On the Select Maintenance Task Order screen, click the Next button.
17. On the Define Back Up Database (Transaction Log) Task screen, drop the list
and select all of the SharePoint content databases.
SSP, WSS Search and MOSS Search databases are set to simple recovery model, so
their transaction logs will not grow.
18. Check the box titled “Create a subdirectory for each database”.
19. Change the backup location, if desired.
20. Click the Next button.
21. On the Select Report Options screen, click Next.
Another area where disk space can be used up quickly is through the SharePoint
Unified Logging Service (ULS). The ULS writes text-file logs to the LOGS folder
in the System Directory (\Program Files\Common Files\Microsoft Shared\web server
extensions\12).
Many large text files located in the LOGS directory
Delete old files to regain space as necessary
This error shows itself as several different errors in the Event Log all saying
that SharePoint attempted to read or write protected memory.
In the Event Log, you see the following:
Type: Error
Source: DCOM
Category: None
Event ID: 10017
Description:
The application-specific permissions settings do not grant Local Activation
permission for the COM Server application with CLSID {CLSID} to the user
DomainName\UserName SID {SID}. This security permission can be modified using
the Component Services administration tool.
1. Click Start, click Run, type dcomcnfg in the Open box, and
then click OK.
2. Expand Component Services, expand Computers, expand My
Computer, and then click DCOM Config.
3. Right-click IIS WAMREG admin Service, and then click
Properties.
4. Click the Security tab.
5. Under Launch and Activation Permissions, click Edit.
6. In the Launch Permission dialog box, click Add.
7. In the Select Users, Computers, or Groups dialog box, type
the domain user account that you specified as the Windows SharePoint Services
3.0 service account, click Check Names, and then click OK.
8. In the Permissions for UserName list, click to select the
Allow check box that is next to Local Activation, and then click OK two times.
Here are some additional references:
http://support.microsoft.com/kb/920783
http://blogs.vertigo.com/personal/steventap/Blog/Lists/Posts/Post.aspx?ID=21
There are two timer services in SharePoint that are responsible for running
various jobs that keep the farm healthy. If you have issues with these services,
then you may see these jobs fail.
Recovery
To prevent these issues, create a batch file that periodically recycles the
services.
1. Open NotePad and add the following lines:
NET STOP "Windows SharePoint Services Timer"
NET START "Windows SharePoint Services Timer"
NET STOP "Windows SharePoint Services Administration"
NET START "Windows SharePoint Services Administration"
STSADM -o ExecAdmSvcJobs
2. Save the file as "C:\Program Files\Common Files\Microsoft Shared\web server
extensions\12\ISAPI\RecycleSharePointServiceTimer.bat"
3. Select Control Panel►Scheduled Tasks►Add Scheduled Task.
4. In the Schedule Task Wizard, click the Next button.
5. Click the Browse button and locate the file "C:\Program Files\Common
Files\Microsoft Shared\web server
extensions\12\ISAPI\RecycleSharePointServiceTimer.bat."
6. Select to perform the task daily and click the Next button.
7. Schedule the task to start at 4:00 AM Every Day and click the Next button.
8. Enter credentials for executing the task and click the Next button.
9. Check the box to open the Advanced Properties and click the Finish button.
10. Click the Schedule tab and then click the Advanced button.
11. Check the Repeat Task box.
12. Schedule the task to repeat every 4 hours.
13. Select the Time option and enter 3:00AM.
14. Click the OK button.
15. Click the OK button.
Whenever you update SharePoint system passwords, you can have issues with
SharePoint being able to access databases and run jobs.
In the Event Log, you see the following error:
An update conflict has occurred, and you must re-try this action. The object
SPApplicationPool Name=SharePoint Central Administration v3 Parent=SPWebService
Name=WSS_Administration is being updated by {...}, in the STSADM process, on
machine {...}. View the tracing log for more information about the
conflict.
Clear the File System cache on the SharePoint front end servers using this
procedure: (From
http://support.microsoft.com/kb/939308).
1. Stop the Timer service. To do this, follow these steps:
a. Click Start, point to Administrative Tools, and then click
Services.
b. Right-click Windows SharePoint Services Timer, and then click
Stop.
2. Delete or move the contents of the following folder:
%ALLUSERSPROFILE% \Application Data\Microsoft\SharePoint\Config\GUID
3. Start the Timer service. To do this, follow these steps:
a. Click Start, point to Administrative Tools, and then click
Services.
b. Right-click Windows SharePoint Services Timer, and then click
Start.
Note The file system cache is re-created after you perform this procedure. Make
sure that you perform this procedure on all servers in the server farm on which
the Timer service is running.
Here's a great article on password changes for SharePoint:
http://blogs.msdn.com/joelo/archive/2006/08/22/712945.aspx
Various performance issues like slow page loads.
<BlobCache location="C:\blobCache"
path="\.(gifjpgpngcssjs)$" max enabled="true"
/>
<compilation batch="false" debug="true">
<customErrors mode="Off" />
<SafeMode MaxControls="200" CallStack="true" DirectFileDependencies="10"
TotalFileDependencies="50" AllowPageLevelTrace="false">
Request for the permission of type
'Microsoft.SharePoint.Security.SharePointPermission,
Microsoft.SharePoint.Security, Version=12.0.0.0, Culture=neutral,
PublicKeyToken=71e9bce111e9429c' failed
Adjust security policy in web.config file as follows:
<trust level="WSS_Medium"
originUrl="" />
Implement custom security policies on all web parts. Start with Dan Larson's
blog entry on the topic.
Download SharePoint Manager 2007
Download Fields Explorer
So recently I have been working on two small MOSS features:
SharePoint Object Model:
there are a couple of properties of the SPWeb object which we will be using:
These values are read/write, so you can set the values to your own strings and the values in the database will be changed accordingly.
Note: all of the following is done within the FeatureActivated function of a custom class inheriting from the SPFeatureReceiver class. Now let’s dive into some code (these are all different methods I tried to no avail)
Created some variables and hard coded the locations within the feature:
string MasterUrl = "/_layouts/custom.master";
string CustomMasterUrl = "/_layouts/custom.master";
string AlternateCssUrl = "/StyleLibrary/Custom/CSS/stylesheet.css";
SPWeb web = (SPWeb)properties.Feature.Parent;
try {
web.MasterUrl = MasterUrl;
web.CustomMasterUrl = CustomMasterUrl;
web.AlternateCssUrl = AlternateCssUrl;
web.Update();
}catch { }
Set the values of the current site to the values from the root site:
SPWeb web = (SPWeb)properties.Feature.Parent;
try {
web.MasterUrl = web.Site.RootWeb.MasterUrl;
web.CustomMasterUrl = web.Site.RootWeb.CustomMasterUrl;
web.AlternateCssUrl = web.Site.RootWeb.AlternateCssUrl;
web.Update();
}catch { }
Set the values of the current site to the values from it’s parent site:
SPWeb web = (SPWeb)properties.Feature.Parent;
try {
web.MasterUrl = web.ParentWeb.MasterUrl;
web.CustomMasterUrl = web.ParentWeb.CustomMasterUrl;
web.AlternateCssUrl = web.ParentWeb.AlternateCssUrl;
web.Update();
}catch { }
None of these methods, upon going to the “Site Master Page Settings” page within a browser, showed the little radio button next to “Inherit site master page from parent of this site” as being checked. They did correctly set the master page and stylesheet links, but if I went to a parent site and changed the master page, the master page did not get changed on the site *unless* the “inherit” radio button was selected.
I decided to take this to the Content Database for the portal in which I was working. Looking in the dbo.Webs table, I found that if the “Inherit” radio button is selected, there are still values in the DB for AlternateCssUrl, MasterUrl, and CustomMasterUrl. Running the above code, would put the same values in these fields, but the “Inherit” radio button would not be selected. I then performed the following steps:
I then moved the side-scroll-bar all the way to the right (to confirm something in each lines was different) and they did not end at the same character, so I went to the beginning and compared vertically until I found different characters. There were a total of 3 instances of different characters (all 3 instances had the same characters) all within the same field, ‘MetaInfo’. These values were:
Going back to the SharePoint Object Model, I discovered that there are two member properties to the SPWeb object which seem to correlate to site properties: Properties and AllProperties. I then tossed together a quick console app to output all Key/Value pairings for these two collections, and this is what came out:
Fancy that, there are three properties which interest me most at this point (indicated in red).
I simply set these values to “True” (note, that is a string of “True” and not a 1 or C# true)
However, it did not pull the correct values to begin with. Therefore, it would appear that SharePoint uses these settings for when the parent’s master pages/css are changed, and not relying on these settings for everytime the site is accessed.
All in all, here is the final code I came up with for my Feature (inside FeatureActivated function):
SPWeb web = (SPWeb)properties.Feature.Parent;
Hashtable hash = web.AllProperties;
try {
web.MasterUrl = web.ParentWeb.MasterUrl;
hash["__InheritsMasterUrl"] = “True”;
web.Update();
}catch { }
try {
web.CustomMasterUrl = web.ParentWeb.CustomMasterUrl;
hash["__InheritsCustomMasterUrl"] = “True”;
web.Update();}catch { }
try {
web.AlternateCssUrl = web.ParentWeb.AlternateCssUrl;
hash["__InheritsAlternateCssUrl"] = “True”;
web.Update();
}catch { }
We are getting error “Value does not fall within the expected range” when try to change the “Page Setting” in MOSS 2007. Yes, again same error message as in here (In fact, this error occurs is various scenarios). This error only happens when you copy an aspx page using SharePoint designer from one server to another severs (development server to production server). Once you try to edit the Page Setting, the error will occurs. We did some googling around but no luck. Some sites mention that the page is link to the old Page Layout’s URL and we are not able to change it since we cannot access the page setting. But, there are a workaround where you can solve it! Here are the steps:
That’s all. You should able to change the page setting without any error. Do note that if you are using reporting services in the aspx page, you can replace all the report’s URLs too. In that case, you do not need to reconfigure all the web parts again. This saves us a lot of effort since our aspx page contains more than 25 web parts. It will take us hours to reconfigure the report URL and parameters.
People alway ask how to use their own 404 file not found error page vs. the generic one from IE in MOSS environment. The following example catches the 404 error and sends users to a redirect page.
Here's the steps:
System.Uri webApplicationUri = new Uri(http://MyMOSSServer/);
SPWebApplication webApplication = SPWebApplication.Lookup(webApplicationUri);
webApplication.FileNotFoundPage = "my404.html"; //*note
webApplication.Update();
*Note: By default this is set to null. FileNotFoundPage needs to point to a html file that lives in %systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033. The file needs to be html only.
6. Now when you browse to a page that doesn't exist, you should expect to be brought to the redirected page.
*Another note:
In IE there's a "Show friendly HTTP error messages" setting which is ON by default in Internet Options->Advanced. With this setting on, sometimes your custom error page is not displayed. In order to override this setting, both my404.html and /errors/my404redirect.aspx from the above steps need to be larger than 512 bytes in size. Refer to the following KB about this setting: http://support.microsoft.com/kb/218155
* This seems to be working within a site collection context only, i.e. http://MyMOSSServer/sites/siteA if sites is a wildcard inclusion managed path and siteA doesn't exist in MOSS then this URL will NOT trigger the custom 404 error page set to SPWebApplication.FileNotFoundPage property.
Also look at SharePoint Smart 404 Feature in codeplex
http://www.codeplex.com/sharepointsmart404
It will give you advanced features
The new version of the Visual Studio extensions for Windows SharePoint Services 3.0 were announced: it’s now finally here, a version compatible with Visual Studio 2008. This version brings the same functionalities as v1.1 for Visual Studio 2005, among others:Full Debugging with Microsoft Office SharePoint Server
Now that I’m doing this post, it’s worth mentioning the latest additions to my SharePoint Resources page:
Controlling What Files to Index
When the indexing process is running, the Gatherer process will open the files found in the content sources. But exactly what file types will it open? This is controlled by a list of file types that you can manage by the link File types on the Configure Search Settings page. The information in this list shows two things:
If you are missing one file type, you can add it now by clicking New File Type. But this will not be enough; the Gatherer also needs the specific IFilter for this file type. You can install these IFilters from third Parties, or Microsoft IFilter Pack.
Common IFilters| File Type | Download Source |
| http://www.adobe.com/support/downloads/detail.jsp?ftpID=2611 | |
| ZIP | http://www.citeknet.com |
| RAR | http://www.citeknet.com |
| HLP | http://www.citeknet.com |
| CHM | http://www.citeknet.com |
| MHT | http://www.citeknet.com |
| CAB | http://www.citeknet.com |
| EXE | http://www.citeknet.com |
| DWF | http://ifiltershop.com |
| StarOffice | http://www.ifilter.org |
| Inventor | http://ifiltershop.com |
| SHTML | http://ifiltershop.com |
| vCard | http://ifiltershop.com |
| OpenOffice | http://www.ifilter.org |
| MindManager | http://www.ifiltershop.com |
| MS Project | http://www.ifiltershop.com |
| MS Visio | http://www.microsoft.com/downloads |
| OneNote | Install MS OneNote on the SharePoint server |
| Audio/Video files: MP3, WMA, WMV, ASF | http://www.aimingtech.com |
| DWG oCad | http://www.cadcompany.nl |
