Re: External content security

Tech-Archive recommends: Speed Up your PC by fixing your registry



Will try and answer each one for you Bradley

1. windows sharepoint services does not index file shares , this is a Portal
server feature in V2 and V3

2. Whne you create a content source in V2 or V3 that account used to crawl
the NTFS shared must have at least read permissions of all content you want
to crawl

3. If the user who is doing the search does not have NTFS read on that
content it should not appear in their search results. SharePoint may have
indexed the content but it is security trimmed when users search for the
content. This applies to V2 and V3.

4. The indexing Engine has been improved a lot in V3 and WSS and MOSS both
share the same Engine now.

There is a live webcast by Bill English on Search in Moss2007 from Teched
tomorrow morning if you can make it. It is at 8am Eastern Time.

Steve Smith
www.combined-knowledge.com


"Bradley Crockett" <BradleyCrockett@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:A21869E9-7AFF-4706-BB56-D46488FB53BA@xxxxxxxxxxxxxxxx
I don't have the SharePoint terminology figured out yet so I may mis-label
things.

We're considering implementing SharePoint Portal Server v3.0 (when it
comes
out) to make some existing content searchable. The content is stored on
network drives and protected by NTFS permissions. Some of the network
drives
are Windows 2003 file servers. Others are file server appliances that do
not
run the Windows OS but that do support NTFS (including permissions). We
will
likely be adding network attached storage in the future.

I understand that Windows SharePoint Services uses Indexing Service to
index
content, is that correct? It is our experience that Indexing Service does
NOT
index NTFS security unless the content resides on the server. This results
in
documents that the user does not have permission to see appearing in
search
results.

I also understand that SharePoint Portal Server uses a version of Indexing
Services that is different or 'extended' from that provided with Windows
and
used by stand-alone WSS. Is that correct? Is it able to index NTFS
security
across the network? If so, is it true for Portal v2 and v3?

Will documents to which a user does not have access appear in Portal
search
results in any of the above file storage scenarios?



.



Relevant Pages

  • Re: Client PCs and NAS not visible on server
    ... Windows SharePoint Services 2.0 RTM version installed. ... Server 2003. ... The NAS is also connected directly to the network and is allocated an IP ... The printers on the server cannot be accessed by the client pc (This is ...
    (microsoft.public.windows.server.sbs)
  • Re: Old question about NTFS
    ... >> readable by the server process. ... > the office network (NTFS) didn't. ... It's because he hasn't got his network set up right. ...
    (microsoft.public.windowsxp.general)
  • Re: Client PCs and NAS not visible on server
    ... Windows SharePoint Services 2.0 RTM version installed. ... Server 2003. ... The NAS is also connected directly to the network and is allocated an IP ... The printers on the server cannot be accessed by the client pc (This is ...
    (microsoft.public.windows.server.sbs)
  • Re: Encryption solution wanted for P2P network
    ... network that consists of 1 Windows 2003 server, ... You own a server to adding AD and a CA is fairly trivial. ... Encrypted (NTFS) files. ... encryption or the original is encrypted AND you use a Certificate ...
    (microsoft.public.windows.server.general)
  • WSS FAQ additions and corrections - 4th to 10th November 2007
    ... Non-MS Articles below were valid at the time I added them to the WSS FAQ ... After you install SharePoint Server 2007 Service Pack 1, the maximum disk space that is used on a query server or on an index server increases to 2.85 times the physical size of the index ... You cannot create a new document or check out an existing document in a Windows SharePoint Services 3.0 document library when you have multiple versions of Office installed ...
    (microsoft.public.sharepoint.windowsservices)