Link to home
Start Free TrialLog in
Avatar of PAGANED
PAGANEDFlag for United States of America

asked on

Windows Search 4.0 XP - UNC locations not adding

I am trying to add the UNC Location :  z:\Warehouse Pictures
.
Windows Search Options
click Advanced
click Add UNC Location
put in :  z:\Warehouse Pictures
Click on Add  :  added successfully
.
Go back to indexing options
--- new location not shown
click on Modify
--- new location not shown
--- z:\  is on the display here but it is 'disabled' ... Mouse Tag = the ability to modify settings for this location has been disabled by the system administrator.
.
.
I checked the Folder :  Warehouse Pictures
Right click :  General tab
Attributes : Advanced button
--- archive and index attributes : for fast searching, allow indexing service to index this folder
Security
--- users have read & execute , List folder contents, read  permissions
.
.
How can I get all the computers in our network  (about 40 workstations) to be able to Index and search this networked drive :  z:\Warehouse Pictures  ?
.
.
Is there a possible settings change necessary ?
Can I use a GPO to do this ?   (win server 2008 as the DC)
.
.
Avatar of Don
Don
Flag of United States of America image

You can use group policy

http://www.networkworld.com/community/node/33396

After you install Windows Search 4.0, you have access to a wide variety of group policies for controlling and managing searches. (The template is SEARCH.ADMX for Vista and Server 2008 and SEARCH.ADM for XP.) Windows Search 3.x only used computer policies, but version 4 supports both computer and user policies for considerable additional flexibility in deploying search customizations and/or restrictions.

http://blogs.technet.com/matthewms/archive/2008/11/13/windows-search-4-0-policy-and-security-overview.aspx
Avatar of PAGANED

ASKER

.
Let me add some more to this inability to Index a UNC location
.
Log into the workstation
run --> gpedit.msc
administrative templates
Windows components
Search
--- All states are Not configured
Default Indexed Paths
--- Add :  z:\Warehouse Pictures
.
Go back to Windows Search Options
--- z:\Warehouse Pictures now exists
Click on Modify
--- you can select various sub folders inside of Warehouse Pictures
.
Go to Windows Search Options
click on Advanced button
--- rebuild the index
the now listed index locations DO NOT  index
... checked the folder via explorer search and states that folder is not indexed but i could add to search options ....
... tried to look for a file in the folder, and it cannot be found with WDS
.
.
Then something strange happens with the GPO default index paths
the WDS search options screen has double listings
---removed the GPO for default index paths and now the single listings stay
---there still is no indexing of the locations however
.
.
Also , unistalled the Windows 4.0 search.
reinstalled the search
same things as above :  no indexing of UNC locations, no adding of UNC locations , z:/ = disable by the system administrator
.
Avatar of PAGANED

ASKER

.
There seems to be a problem with WDS 4.0  and indexing a DFS folder
http://social.msdn.microsoft.com/Forums/de-DE/windowsdesktopsearchhelp/thread/85525c46-1ab5-46e1-a288-e36561a6ffab
.
Indexing a mapped drive (to a dfs folder)  :  problem  _disabled by system administrator
Indexing directly to the server and folder (dfs folder) : problem _disabled by system administrator
.
Avatar of PAGANED

ASKER

this problem remains unresolved...
Avatar of PAGANED

ASKER

I've increased the points to the max of 500 points
.
It seems that this is an 'involved' problem that isnt easily remedied
.
.
ASKER CERTIFIED SOLUTION
Avatar of PAGANED
PAGANED
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Don't find much in terms of alternative options, but perhaps these links will be of some help.
http://www.microsoft.com/windows/products/winfamily/desktopsearch/technicalresources/advquery.mspx

and
Synopsis, and link for more on the Technical Q&Q side for Windows Search 4
Is Windows Search extensible and programmable?
Yes, Windows Search provides a number of extensible and programmable interfaces to help enable these additional scenarios for enterprise customers:
Deploy IFilters to provide users the ability to search file types specific to the company or industry, such as CAD files.
Write and deploy protocol handlers to enable users to search additional content repositories from proprietary applications.
Surface desktop search results within business applications by using the desktop search query API. For example, this can be used provide sales representatives with a complete profile of their client in the CRM system by combining CRM data with information about the client stored on the representative's personal computer.

Source follow which includes additional links for IFilters, Protocol Handlers, etc. - http://www.microsoft.com/windows/products/winfamily/desktopsearch/technicalresources/techfaq.mspx
Next has IT Management and Troubleshooting guides for 4.0 and includes additional links specific to Server2008 and more - http://technet.microsoft.com/en-us/library/cc771203.aspx
Not my area of expertise, but wanted to help, if I could (learning along the way).  ":0)  Asta

When I search on a tag, nothing is found. (found in link below, as well as other troubleshooting possibilities as well as permissions/security)
The property handlers for Windows XP, Windows server 2003, and Windows Home Server do not emit tag values, and therefore the tag values are not indexed. The tags are indexed on Windows Vista.
No workaround available. - http://technet.microsoft.com/en-us/library/cc771814(WS.10).aspx


If you upgrade from WDS 3.x to WS 4, core settings migrate but the index is rebuilt. On Windows XP or Server 2003 machines, if the Add-in for Files on Microsoft Networks (UNC/FAT protocol handler) is installed with WDS 3.x, it is uninstalled and then reinstalled with WS 4 since it is included in WS 4 package itself. Other 3rd-party protocol handlers (like IE History) installed before the upgrade should continue to work as expected. - http://technet.microsoft.com/en-us/library/cc753989.aspx