Would it be possible to use a central index location for our whole network clients?

Would it be possible to use a central index location for our whole network clients?

• BRS0903

  The standard Microsoft solution for creating a central index of content spread out around a network is Sharepoint. There's even a specific version of MOSS ("Sharepoint for Search" I believe it's called) just for this purpose.

  Alternatively, if your environment uses Windows Vista - Vista clients can remotely query the index of network shares on a server running Windows Vista or Windows Server 2008. However, this is only meant for small organizations or departmental servers, as it will not scale like Sharepoint does.

  
  
  

• Steven Rosenthal

  Paul,

  Any update on this new version that will allow for a centralized index What about with 3.0...is this even possible to accommodate via add-in development

  Thanks!

  ...tod...

  
  

• Duncan_

  Ronald,

  This is not something that would be possible at the moment. As it stands with WDS, the index must be located on the client. In the future, we will be releasing a product that can query the index of content servers (Sharepoint for example). This means that the index can be stored on the server and our new product can pass the query to that index and retrieve the results.

  I'll be updating this forum as soon as the product I'm speaking of is available for preview.

  Paul Nystrom - MSFT

  
  
  

• puffzotty

  themasmer wrote:

  Hi all, We had a similar requirement in our organisation, where the end users needed to search a single server for word documents. Our application uses web services extensively and here's what we have done: 1. Create a remoting application that uses the WDS api to return search results. 2. Create a web service that uses the remoting server to search the index. 3. Invoke the web service from the client end. We tried other solutions as well, but this worked perfectly without any glitch. Regards, Abhishek

  Hello

  I have to develop some application like yours at number 1. How did you do it Could you give me any tip where/how to start

  Thanks a lot.

  
  
  

• El Bruno

  great news...

  we are thinking of putting up a MOSS Search server to index disparate MSFT and other content then have WDSU clients point to that standard repository so we hope thats the go forward strategy you are refering to.

  I am a newbie on this subject so maybe you can point out what WDSU names the INDEX file and where it is located by default and how I can move it to a networked drive

  thx RK

  
  

• StephanTual

  Brandon Paddock MSFT wrote:

  The standard Microsoft solution for creating a central index of content spread out around a network is Sharepoint. There's even a specific version of MOSS ("Sharepoint for Search" I believe it's called) just for this purpose. Alternatively, if your environment uses Windows Vista - Vista clients can remotely query the index of network shares on a server running Windows Vista or Windows Server 2008. However, this is only meant for small organizations or departmental servers, as it will not scale like Sharepoint does.

  Thanks a lot for your time.

  I've already taken a deep look into Microsoft Office SharePoint Server and noticed that it does exactly everything I need in easy way, but due to its really expensive license I've redirected my research to something not so especific that could fulfill my company needs. By reading some texts at the net I think it's possible to WDS to do this like themasmer wrote.

  Thanks again for your atention anyway.

  
  
  

• Xancholy

  WDS is not a feasible solution for this scenario. To fulfill this requirement pls. look at the Microsoft Office SharePoint Server 2007 for Search editions.

  
  
  

• Marshes

  Hi Paul,

  I don't quite understand the resolution. Will there be a central index in the future or will i have to go to sharepoint

  Cheers

  
  

• sqlhiker

  Hello Paul,

  the product for indexing content servers, will it be become part of WDS 3.0
  Do you have any idea about when it will be available, weeks, months more

  We have a Terminal Server environment and our users use thin clients to connect to their own TS desktop (with Citrix and of course RES Powerfuse ). Our users have data on Windows fileservers (W2K and W2K3) and IP SAN. We also are about to archive our exchange e-mail with Zantaz EAS or Symantec Enterprise Vault. Can the new feature index all these locations, including the archived mail

  I'm very curious about the security the new feature will expose. Our fileservers provide data that's not available to all users. When I query the central index of a content server, does it show me results of data that's not mine, data thats classified and not mine to find

  Will there be a limit about the number of files that can be indexed Is SQL/Oracle nessesary or possible

  I have high expectations about this feature, can you ' make my day'

  Thanks,

  Roland

  
  

• chionhhm

  Paul,

  Any updates on the central index We have a small network and most of our pc's do not have a lot of disk space. How much space does the index actually take

  Thank you

  Kathy

  
  

• Munzer Enayah

  Hi all,
  
  We had a similar requirement in our organisation, where the end users needed to search a single server for word documents.
  
  Our application uses web services extensively and here's what we have done:
  
  1. Create a remoting application that uses the WDS api to return search results.
  2. Create a web service that uses the remoting server to search the index.
  3. Invoke the web service from the client end.
  
  We tried other solutions as well, but this worked perfectly without any glitch.
  
  Regards,
  
  Abhishek
  
  
  
  
• Would it be possible to use a central index location for our whole network clients?