MuttleyMc

Hi,

I am struggling to get WDS 3.01 to index my Mapped drives when configuring the include list in group policy.

Our Home drives are on drive H:\, and the server is different for users in different countries. I don't want to have to specify the server names and paths for all servers, I just want to add H:\, so that it maps up that drive.

Is this possible

MuttleyMc




Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

Duncan Dewar

I am also having an issue searching mapped drives. But in my case we don't have a consistent location so the users need to be able to provided that location.

I have enabled or disable the appropriate policies but still no luck.

We don't see the option to add any location but a local folder on the C drive.





Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

Gerald Haslhofer

Sorry, that's not supported at the moment. You need to push different policies to different machines.

Gerald - Microsoft






Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

Gerald Haslhofer

You need to go index options, advanced options, tab "Add UNC location" to add unc shares.

Gerald - Microsoft






Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

MuttleyMc

Are there plans to implement indexing of drives that are mapped to letters

We are a globally distributed company so for us its unrealistic to create policies, or include drives for the 200 sites that we have around the world. One include entry for H: would be a much better way of doing this.

I recommend that you update the admin guide to specifically say that this is not currently supported, rather than letting us try all the various combinations of H:\ , file:///H:\ , otfs://localhost/H ....... only to find that it doesn't work.





Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

Gerald Haslhofer

I forwarded the issue to its appropriate owner; we'll take a look at this in our next release. Again, thanks for reporting the issue!

Gerald






Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

Gerald Haslhofer

We verified this actually works. You need to use the following group policy default rule:

otfs:\\{*}\z:\

-Gerald






Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

Gunnalag

Hi Gerald,

Thanks for your post.

I tried exactly
otfs:\\{*}\z:\ and found that it's not working as expectedly.

My expected behavior is to disallow users from indexing a network drive Z: and for this I
- added
otfs:\\{*}\z:\ under paths sections of 'Prevent Indexing Certain Paths' Group policy
- ran gpupdate /force and rebooted the workstation.
And still the users have access to index the network drive Z:, which is unintended.

Question: What exactly otfs: stands for can you please elaborate each element in
otfs:\\{*}\z:\

Looking forward for your response (hopefully soon).

Thanks,
Govardhan





Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

Ari Polsky - MSFT

Try this syntax:

otfs://{*}\z\*





Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

Gunnalag

Yes, this worked fine.

FYI. similar issue can be found in http://forums.microsoft.com/MSDN/ShowPost.aspx PostID=1286930&SiteID=1

Thanks,

Govardhan






Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

TMQ

I am using this syntax to prevent users indexing certain locations, In my wds index locations I get 2 instances for the same drive as below:

App_PP on 'msserver' (iSmile and I:\(winad\myuser)

I:\(winad\myuser) - this one is greyed out and unavailable by adding otfs://{*}\i\* to the GPO

but the App_PP on 'msserver' (iSmile can be selected and indexed

Is there a way to disable this so users cannot chosse to index this network drive





Re: Windows Desktop Search Development Indexing Mapped Drives - Group Policy Settings

Ari Polsky - MSFT

Sorry, I made a mistake in my previous post. The correct syntax is otfs://{*}/i/* (all forward-slashes). Or you can just set the exclusion directly to the share on the server, which would work regardless of what drive letter the mapping happens to use: otfs://{*}/server/share/*