- Download the small icon file from adobe. http://www.adobe.com/misc/linking.html#pdficon
- Save the icon in the c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\IMAGES folder.
-You can rename it to match the standard naming convention. - Open (in notepad) the DOCICON.XML file located in the c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\XML folder.
- In ByExtension -->section add the tag >Mapping Key="pdf" Value="icpdf.gif" OpenControl=""/>-Change the direction of the first > (just left to Mapping) to make the markup work right.
- Save.
- Reset IIS.
- You should now see all PDF documents with the correct icon.
Oct 28, 2009
Showing the PDF Icon in a SharePoint Document Library
Out of the box, you won't see the PDF icon in WSS 3.0 document libraries as you see MS Office icons next to office documents.
Oct 17, 2009
How can we explain SharePoint?
I always sympathize with SharePoint professionals when reading articles about their difficulties in answering the question: “What do you do for a living”? After thinking it over and over, I decided to rephrase the question. I asked myself, “What will eventually be the TLR (Three Letter Acronym) for SharePoint-like applications?
I have never been satisfied with my own explanations of SharePoint, even with my latest strategy of asking the person about his or her IT knowledge before formulating my response. I see people nodding their heads, but in most cases I feel I didn’t convey the message well enough.
Thinking about a TLR, the first thing that comes to mind is the equivalent ERP (Enterprise Resource Planning). The name is intuitively perceived as a package of related applications that support end-to-end the enterprises’ operations. But it took 10 to 15 years until this TLR became the standard everyone uses and understands. Previously, there had been MRP, Logistics, Shipping, Financial, HR and other disparate applications.
So what do we package here? SharePoint supports several relatively independent processes. It combines what was previously Portal, EDM (Enterprise Document Management), ECM (Enterprise Content Management), WCM (Web Content Management), team collaboration, activity tracking and even connectivity extensions to backend systems. We will probably see more Social Network support coming soon. Since companies usually need more than one of these applications, why not use the same tool and save on maintenance?
What can be a reasonable common denominator for all these processes? I think that the phrase “Knowledge Sharing” is pretty close to what they do. Prefix it with the E for Enterprise which is important, accurate - and also sells, and you get EKS – Enterprise Knowledge Sharing.
Spread the word…
I have never been satisfied with my own explanations of SharePoint, even with my latest strategy of asking the person about his or her IT knowledge before formulating my response. I see people nodding their heads, but in most cases I feel I didn’t convey the message well enough.
Thinking about a TLR, the first thing that comes to mind is the equivalent ERP (Enterprise Resource Planning). The name is intuitively perceived as a package of related applications that support end-to-end the enterprises’ operations. But it took 10 to 15 years until this TLR became the standard everyone uses and understands. Previously, there had been MRP, Logistics, Shipping, Financial, HR and other disparate applications.
So what do we package here? SharePoint supports several relatively independent processes. It combines what was previously Portal, EDM (Enterprise Document Management), ECM (Enterprise Content Management), WCM (Web Content Management), team collaboration, activity tracking and even connectivity extensions to backend systems. We will probably see more Social Network support coming soon. Since companies usually need more than one of these applications, why not use the same tool and save on maintenance?
What can be a reasonable common denominator for all these processes? I think that the phrase “Knowledge Sharing” is pretty close to what they do. Prefix it with the E for Enterprise which is important, accurate - and also sells, and you get EKS – Enterprise Knowledge Sharing.
Spread the word…
Oct 5, 2009
MOSS and WSS 3.0 Installation on Windows Server 2008 R2
If you want to install SharePoint 2007 on Windows Server 2008 R2, you need to take special actions because SP2, which supports this operation, is a prerequisite. If you try to install with SP1 you will receive an error message.
The way to do this is to use a slipstream, something like concatenating several components together to meet the requirements.
In its Team Blog, Microsoft published KB articles explaining the needed steps.
The slipstream builds can be found here:
Windows SharePoint Services 3.0 with SP2 (x86) http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en
Windows SharePoint Services 3.0 with SP2 (x64) http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en
For SharePoint Server 2007, you can follow Create an installation source that includes software updates (Office SharePoint Server 2007) to create one. Or you can also read on. We will go through the complete steps to create a new slipstream build for SharePoint Server 2007.
You can find the article here:
http://blogs.msdn.com/sharepoint/archive/2009/10/02/install-sharepoint-server-2007-on-windows-server-2008-r2.aspx
And one more tip: If this is a plain vanilla installation, and you have control over the server type, you need to use the X64. SharePoint 2010 will work on X64 only.
The way to do this is to use a slipstream, something like concatenating several components together to meet the requirements.
In its Team Blog, Microsoft published KB articles explaining the needed steps.
The slipstream builds can be found here:
Windows SharePoint Services 3.0 with SP2 (x86) http://www.microsoft.com/downloads/details.aspx?FamilyId=EF93E453-75F1-45DF-8C6F-4565E8549C2A&displaylang=en
Windows SharePoint Services 3.0 with SP2 (x64) http://www.microsoft.com/downloads/details.aspx?familyid=9FB41E51-CB03-4B47-B89A-396786492CBA&displaylang=en
For SharePoint Server 2007, you can follow Create an installation source that includes software updates (Office SharePoint Server 2007) to create one. Or you can also read on. We will go through the complete steps to create a new slipstream build for SharePoint Server 2007.
You can find the article here:
http://blogs.msdn.com/sharepoint/archive/2009/10/02/install-sharepoint-server-2007-on-windows-server-2008-r2.aspx
And one more tip: If this is a plain vanilla installation, and you have control over the server type, you need to use the X64. SharePoint 2010 will work on X64 only.
Subscribe to:
Posts (Atom)
Posts
