MOSS 2007 & PDF Search

[Mark Pfeifer]

It appears most links point to:
http://blogs.msdn.com/ifilter/archive/2007/03/29/indexing-pdf-documents-with-adobe-reader-v-8-and-moss-2007.aspx

Is this the recommended approach - Adobe Reader 8.1?

Also, I assume I would need to perform the steps on the portal server(s) and
the sql server to get both WSS and MOSS searching to work?

Thanks
Mark

[Peter Lawton]

We use the foxit PDF filter as they do a 64bit version:-

http://www.foxitsoftware.com/pdf/ifilter/

Peter Lawton

"Mark Pfeifer" <mpfe...@online.nospam> wrote in message
news:ui3UnLJ...@TK2MSFTNGP05.phx.gbl...

[tlyczko]

Does Adobe Reader have to be installed on the Web Front End (WFE) or
on the SQL 2005 Database Backend???

This is for WSS 3.0.

I've been looking all over for how to set up PDF IFiltering in a small
farm setup with a WFE and a separate SQL backend.

99% of everything says "the server," but WHICH server??

Mike Walsh's FAQ first states the IFilter is installed to the database
server, then further down it says the IFilter can be installed to the
Web Front End.

The above-mentioned blog does not help either by not being too clear
about which server either, see the complaints during August and
September about the lack of clear, unambiguous instructions.

Which server, Web Front End Server or SQL 2005 Backend Server??

Thank you, Tom

On Sep 6, 10:36 am, "Mark Pfeifer" <mpfei...@online.nospam> wrote:
> It appears most links point to:http://blogs.msdn.com/ifilter/archive/2007/03/29/indexing-pdf-documen...

[Peter Lawton]

The ifilter has to be installed on the box running the search, if you have
two a web front end and a separate sql backend it'll usually be the web
front end server. In this case the ifilter doesn't need to be installed on
the SQL server.

Peter Lawton

"tlyczko" <tly...@gmail.com> wrote in message
news:1189097854.2...@50g2000hsm.googlegroups.com...

[tlyczko]

On Sep 6, 1:21 pm, "Peter Lawton" <du...@dummy.domain> wrote:
> The ifilter has to be installed on the box running the search, if you have
> two a web front end and a separate sql backend it'll usually be the web
> front end server. In this case the ifilter doesn't need to be installed on
> the SQL server.

I will wait till tomorrow to see if I get additional replies on this
topic, since the search/index stuff is in the SQL database...

Thank you, Tom

[Peter Lawton]

"tlyczko" <tly...@gmail.com> wrote in message

news:1189099962....@r34g2000hsd.googlegroups.com...

I'm not sure what lead you to believe that

[Marco van Schagen]

You may want to look in your central administration to see which
server is performing the indexing task. I believe there will be only
one content indexing server, no matter how big your farm is.

At http://www.dwgifilter.com/ we have started a support web for
IFilter issues. You will find some information on installing your
IFilters with MOSS and WSS, and I am trying to get the information
more up-to-date.
The support site focusses on our DWG IFilter 2007 version that
supports for the AutoCAD DWG and DXF file type. It works well with
MOSS and WSS. Most information also applies to other IFilters for
other filetypes. I don't mind to add more information to support the
IFilter/SharePoint communities.

As I'd like to create a better description of IFilter installation and
support issues; please send your suggestions, info, screenshots, to
ifi...@cadcompany.nl

[Sundar Narasiman]

Mark Pfeifer,

Adobe V8.1 is no way enforced by any one. you can even install Adobe V6
Ifilters. I've done the same and i've shared my experiences under the
following url

http://dotnetbuzz.spaces.live.com/blog/cns!F3599E60D988EEB0!384.entry.

You don't need to do work on the SQL server for the pdf search

--
Thanks & Regards,
Sundar Narasiman, MCAD
Blog: http://dotnetbuzz.spaces.live.com/

[Sundar Narasiman]

tlyczko,

You need to install the Ifilters on the indexing server. It's mandatory to
go for IFiler V8.1. I've even enable PDF search for MOSS 2007 with IFilter V6.

I've shared my experiences in the following link
http://dotnetbuzz.spaces.live.com/blog/cns!F3599E60D988EEB0!384.entry

It's also not mandatory to install Acrobat Reader on the indexing server.
IFilter component only would suffice

--
Thanks & Regards,
Sundar Narasiman, MCAD
Blog: http://dotnetbuzz.spaces.live.com/

[joshharbert]

Make sure you have it installed on the SQL server in a small farm environment. I just ran into this issue. I first installed on web server and no luck. Then index server...still no luck. Once I installed Adobe 8.01 reader on the SQL server it worked without an issue.

And make sure you start a full crawl after you install to reindex the pdf files.

EggHeadCafe - .NET Developer Portal of Choice
http://www.eggheadcafe.com

[Marco van Schagen]

Hi,
I have the feeling that where to install the IFilter does not depend
on the IFilter, more on your scenario.
Can anyone confirm the following statements:

- With WSS, single server, with built-in SQL: Install on the single
server and register with WSS to enable indexing of all applicable
content.
- With WSS, multi server, using built in SQL, one of the servers is
the indexer, many can be a front-end. Install only on the Indexing
server and register with WSS to enable indexing of all applicable
content.
- With WSS, single or multi server, and database in SQL 2005 (...) ,
SQL server may actually be used to index the content, I am not sure??

- With MOSS, single server, with built-in SQL: Install on the single
server and register with MOSS to enable indexing of all applicable
content.
- With MOSS, multi server, using built in SQL, one of the servers is
the indexer, many can be a front-end. Install only on the Indexing
server and register with MOSS to enable indexing of all applicable
content.
- With MOSS, single or multi server, and database in SQL 2005 (...) ,
SQL server is to index the content that is stored here in the site
(=in SQL). Indexing server is used in indexing all other content on
file shares, exchange, other HTTP, other sharepoint sites crawled as
HTTP. Install on indexing server and register with MOSS, also install
on SQL server and register with SQL 2005.

- Any desktop scenario with WDS (on XP or Vista): Install, register as
default with the system (indexing services 3.0 method) and optionally
register with WDS. This should support search in your local folders,
and outlook, and any network resources you have configured. First
thing to check is which folders and filetypes are addtessed by WDS.
- Any desktop scenario based on Indexing service: Install and register
as default with the system (indexing services 3.0 method)
- Scenario with Exchange server, install on the exchange server and
register with Microsoft Exchange. This should support server side
Search in outlook.

- Oh, built-in SQL for MOSS is limited in size, for WSS seems to be
unlimited. So for MOSS you'd like to use an installed SQL Server.

Please, anyone to confirm or correct any of these statements? I'd like
to build an overview on our support site.
Until this is confirmed, probably the safest way to check this is to
install in all locations and check the logs to see which one picks up
the work. Try storing the file in all locations possible.
I expect in future releases of Microsoft products, you may need to
also install the IFilter on your exchange server if you need this to
have the filetypes in content source added to your MOSS search .

Note: Registering with WDS, MOSS, WSS, SQL 2005 requires adding some
registry settings and executing some commands. Our DWG IFilterr comes
with a configurator tool that should take care of this in most
scenario's. I have documented some details on our support site
www.dwgifilter.com and I'd like to add more; also our product download
contains some testing tools to see if the IFilter can be found
correctly on the system; you can easily adjust this test to check your
favorite file type. The DWG IFilter has a 60 day trial period to allow
you to figure out what is best in your scenario.

My apologies for the big post, I hope my thoughts are going into the
right direction. Just looking to gather some validated answers for our
how-to questions on our support site.

Regards,
Marco van Schagen / CAD & Company / ifil...@cadcompany.nl / www.dwgifilter.com

[Mike Walsh]

Note that if you are going to quote this text anywhere else, you'd
better add "3.0" to WSS everywhere - because, as you know, where to put
the IFilter is different for WSS 2.0 installations.

(Yes I know it was in the title, but ...)

P.S. I would question most of this sentence

> - With WSS, multi server, using built in SQL, one of the servers is
> the indexer, many can be a front-end. Install only on the Indexing
> server and register with WSS to enable indexing of all applicable
> content.

1. You can't have multi-server and use the built-in SQL. The built-in
SQL is only available for a single-server installation.
2. Can you really have an Indexing server for WSS 3.0?

No doubt there are other things I might query, but the above is all I
have time for at the moment,

Mike Walsh
WSS FAQ www.wssfaq.com / wss.collutions.com
no private e-mail questions please