Following up on the Windows Search 4.0 Preview release, I will be writing several posts about some of the new features and changes enabled by this release. One such feature, and this first one I will dive into here, is the capability to remotely search the index of another Windows PC.
This features isn’t entirely new. Windows Vista shipped nearly a year and a half ago with the ability to query the index of another Vista machine when searching file shares. The same capability extends to and from Windows Server 2008.
Windows Search 4.0 brings this capability to Windows XP machines, as well as Server 2003 - and perhaps more importantly, Windows Home Server.
So how does it work? First let’s take a look at how the user sees it. Let’s say I have a folder on Machine A called “Cool Stuff” that I want to share out. One simple way to do that is to browse to the folder in Explorer, select it, and click “Share.”
You’ll then get a friendly dialog that asks you who you’d like to share with.
“Everyone” is a simple answer for information you want to be accessible to everyone. Select it from the drop-down and click “Add” to add Everyone to the list of people the folder is shared with.
What else do I have to do on Machine A? Nothing! Windows Search 4.0 will automatically index any folders you share out, on both XP and Vista.
On Machine B, you simply navigate to the share as you normally would. That could mean typing a UNC like \\MachineA\Cool Stuff\ or it could mean using a mapped drive, redirected User folders, the Network browser, etc. Once there, just type a query in the Search box (or on XP, click the “Search” button to bring up the Search Pane) and you’re off!
Unfortunately I don’t have any XP machines to get a screenshot from, but I’ll try to add one soon.
Today we made available the WS 4.0 preview release for Windows XP, Vista, and Server 2003/2008. You can read details about WS 4.0 at the following sites:
Vista Team Blog - Announcing the Windows Search 4.0 Preview
KB Article describing Windows Search 4.0 (with download links)
This release is mainly an update to the Windows Search indexer, and provides countless performance improvements, bug fixes, and reliability / recoverability features.
The XP/2003 version has been updated with more features previously exclusive to Vista - such as the ability to search remote indexes for network shares, and the ability to host Vista-style preview handlers in the preview pane.
WS4 also provides some cool new query capabilities for developers, which I will describe and give some examples of in future posts.
The most noticeable difference is probably how fast it is. Those geniuses down the hallway in indexer land really pulled off some impressive feats with this release.
Since there are six different downloads depending on your OS, I’ll just refer you to the KB article for downloading the preview release.
Let us know what you think!
Let’s say you want to optimize your system by only indexing certain data. For example, a reader recently e-mailed me and said “I only want to index my media files.” Seems like a valid choice. At first glance, it might seem like you could achieve this by telling Windows to only index files with extensions like .mp3 and .avi. Ultimately, this is a very bad idea.
First, let me tell you why this is a bad idea. Second, I’ll tell you the right way to achieve what you want.
Let’s begin by looking at how the Windows Vista shell and the indexer work together.
The indexer maintains a list of “start paths” - which are locations in the shell namespace that it cares about. By default, it is set up to index the x:\Users directory - and thus all of the default Documents / Music / Pictures folders of all user accounts on the system. When you install Outlook, it sets up a start path for your mail accounts. OneNote sets one up for your OneNote data. And so on. This means that the indexer will try to index all items under that path*, and ignore everything else.
When you browse to a folder in Explorer, the shell asks the indexer if the current path is covered by the index. If it is, Explorer will use the index exclusively for search / filter / grouping operations against that location. It does not ask the index if it covers all the file types in that location. It assumes the index is the authoritative source for information about that part of the namespace.
On the other hand, if the path is not covered by the index, Explorer walks the entire namespace starting at that location (so, the current folder and all subfolders) and enumerates every single item, performing all operations like filtering / sorting / grouping in-memory. By default, it does not crack open any files being enumerated - so all filtering operations happen only against the basic properties like file name. You can then click the “Search in File Contents” button (what some of us call the “try harder” button), and it will repeat the operation - stopping at every file and cracking it open with the appropriate IFilter and property handlers, doing essentially the same thing that happens when a file is indexed. It loads the file, cracks it open, extracts all the properties and content, checks to see if it matches the current filter, and then decides whether or not to add that item to the view or ignore it. If you change the filter, the whole process starts over again. Needless to say, this is rather slow if you have to do it for more than a few files. That’s why the “Search in File Contents” button is there, since in most unindexed locations (like C:\windows) you are probably only searching for a filename.
Armed with this information, let’s take another look at the original question. Let’s say you go into the Advanced options for the indexer and tell it not to index .doc files at all. Then you go save a new document called Something.doc inside of your Documents folder, which is still indexed. The indexer will be notified that a new file was created there, but since you disabled indexing of that extension, it will ignore it. Then when you go to your user folder or the Documents folder and search for “something” - you don’t find the document. Even though it’s right there in the name. The folder said “Hey, I’m indexed” and the file is not in the index, so as far as Explorer is concerned, it doesn’t exist.
A much better approach, if you really don’t care about indexing your .doc files, is to tell Windows not to index the Documents folder (or wherever you keep your .doc files). That way it will fall back to slow GREP search when you look there, which will at least find what you’re looking for, albeit more slowly.
You can do this from the Indexing Options control panel, and it’s pretty easy to do. Only want your music and videos indexed? Then tell the indexer to only crawl the places where you store those files. That it’s, mission accomplished.
The end result is the same. The indexer isn’t doing any additional work, unless you mix .doc files and media files in the same folder. And even then, at least you’ll be able to find them.
Another option available to you is to set certain extensions to “Index File Properties only.” That way you’ll at least be able to find the item by its name. Why would you want to do that? I have no idea. It’s not like indexing files incurs a significant overhead on any reasonably modern PC. The option is mainly there because there are some file types the indexer can’t search inside. So instead it indexes all the basic stuff that applies to every file (like name, date modified, and size).
* = It’s actually more complicated than that, as there can be nested inclusion/exclusion rules, files or folders excluded based on attributes, etc. But that’s not particularly relevant to this discussion
Seriously Yahoo, what were you thinking?
Today Yahoo announced their “Open Search Platform” - saying that it will “allow third parties to enhance the Yahoo Search experience.”
You might assume that this means they’re doing something cool with OpenSearch - the set of open standards once established by A9 and later embraced by IE / FireFox to hook up search providers, and recently used by Microsoft’s SharePoint and Search Server products as the means by which to support federated search results.
But you’d be wrong. Apparently Yahoo thinks that by adding a space between “Open” and “Search” nobody will be confused that their offering is not, in fact, OpenSearch compatible.
A commenter I know on TechCrunch even asks if we’ll soon see “Yahoo announced a Really Simple Syndication Platform” that isn’t RSS based?
Change the name, Yahoo. This attempt to co-opt the OpenSearch label is distasteful at best. And we’re trying to buy you why?
The new Windows Search SDK for Windows Vista and Windows Desktop Search 3.x is now available on MSDN!
We’ve also released a new set of code samples to go along with it.
I’ll be digging in and writing more about building on the SDK very soon!
Today we’ve released Windows Desktop Search 3.01 for Windows XP and Windows Server 2003. This release includes many bug fixes and improvements based on user feedback received since the release of WDS 3.0 last fall. Some users noticed the lack of UNC / network share indexing support in WDS 3.0 and insisted we put it back. So we did! The UNC / network share add-in is no longer a seperate downloaded and is included in WDS 3.01.
WDS 3.01 also brings back full Group Policy support (previously available in the WDS 2.6 Enterprise releases).
Special congratulations to the indexer team, many of whom worked some pretty heavy hours through January to make sure this release had that extra layer of polish on it. Thanks guys! Now go home already!
Download links:
Group policy ADM file is included in the package. Run the installer with the /extract parameter to extract the contents directly.
There’s also an updated Advanced Query Reference for 3.x / Vista.
The WDS website and related docs are in the process of being updated as I write this.
Since Steve Wiseman’s post (”The 5 sins of Vista“) doesn’t have a place for comments - I’m responding here. Let’s go through his issues one-by-one.
1) The new File Open dialog.
Personally, I’m a big fan. The XP dialog had some basically hard-coded “Favorite Places” on the left-hand side, but to really customize or extend them you had to use a Stardock add-in. There was also no functional Search capability - whereas now you can type a few characters into the Search box and find exactly what you’re looking for.
Steve’s problem? The lack of a regular folder “tree view” - which, oddly, didn’t exist in the XP dialog either. But wait, Vista does have it! Just click the “Folders” header (by default, it is collapsed) and voila! You can even resize it to be exactly how you want it.
Personally, I’m much happier with the Favorites bar, but that’s just me. His other gripe? Clicking the down-arrow by the address bar shows him the standard address bar history (which probably includes websites as well). But if he would just look a couple inches to the left, he could expand one of the breadcrumbs in the breadcrumb bar and see exactly what he’s look for - in a far more useful fashion than you ever could in XP!
Also, why have an “up” button when you have a breadcrumb bar? You can go up a level just the same, by clicking on the parent breadcrumb, or (depending on the width of the window) you can jump multiple levels higher with a single click. It takes a few minutes to get used to, but it makes so much more sense and really is one of my favorite improvements to file browsing in Vista.
2) The new Start menu.
Steve complains that typing “C:” into the start menu doesn’t open that folder, but “C:\” does. He suggests that we should check to see if what was entered is a valid path before launching the first search result. But that is what we do! The problem is, “C:” isn’t a qualified path. In fact, because the colon is a word-breaking character, it’s basically the same as just typing “C” into that field. Could drives have been special-cased? I suppose. But really, if typing that extra slash is one of your top 5 gripes with Vista, I think we’re doing pretty well =)
Legacy functionality is also retained by pressing “Windows Key + R”, or by re-enabling the classic “run” box from the Start Menu advanced options.
3) Windows Networking
I’ll agree with Steve that on first glance, you might be a bit lost in trying to figure out how to change your IP address from the Networking control panel. Of course, going to Control Panel and typing “ip address” in the search box would get you there a lot faster =)
However, I really like the new Networking capabilities in Vista. For one, Vista finally addressed one of my biggest desires when it comes to networking, especially for my laptop - it actually remembers settings on a per-network basis, in ways that previously required third-party software (which never seemed to do a good enough job). In Vista, I set up a network once, and never worry about it again. When I go to a friend’s house that I’ve been to before, the wireless connection just works. Same when I go to Panera, or use any of the Seattle public hotspots. Not only do I never have to be asked about connecting to a network I’ve already established as trusted, but all my network discoverability and sharing settings are remembered. And believe it or not, the “diagnose problem” functionality in the new Network and Sharing center is really nice. As are the yellow-band prompts that remind me I have sharing or network discovery turned off for a particular network, and give me a one-click option to enable them.
4) Windows Search
This entire section of Steve’s post makes no sense to me. First of all, I’m not aware of any changes made to Windows XP’s built-in search in XP SP2. I really can’t be sure if he’s talking about Windows Desktop Search or not, but his points don’t seem to apply either way.
He says: “I want a simple search program that will search for a file on my hard drive (Hint to Microsoft - Every file, not just the types you know about like Word and Excel files) that contains a specific string of letters.”
Well, fortunately, Windows Search has never been limited to Microsoft formats like Word and Excel. In fact, Windows Search will index (or grep-search) the filenames and metadata of any files on your system, and will index the content of hundreds of filetypes out of the box. What’s more, files can be indexed (or have their content cracked on-demand for non-indexed locations) using the standard IFilter interface, for which filters are available for most popular formats - including Adobe’s PDF format.
It’s true that Windows Search doesn’t index your entire hard drive(s) by default. This is done to improve performance and the quality of search results, as very, very few users want to be searching for a document and see random system DLLs show up. However, both the indexed locations and the filetypes that are excluded are fully configurable.
More importantly, though, is how well Vista will handle non-indexed locations seamlessly. If you initiate a search in a non-indexed location, the same IFilters used for indexing can be used to search the contents of non-indexed files (if you click the “Search in File Contents” button).
The problem for Steve might be that he’s searching in “Indexed Locations” for items that aren’t indexed. However, by selecting a different location in the Location drop-down, it’s easy to search anywhere and find what you’re looking for.
5) File copying
Steve says “I absolutely hate it when my 5000 file copy gets killed half way through because 1 single file can’t be opened.”
Lucky for him then that this exact problem was addressed in Vista! Now, when you copy a large number of files/folders - Vista will prompt you for any permissions, overwrite requests, etc - at the start of the operation, for everything in the copy list. It will also copy as much as it can and save any errors for the end of the operation, so that you don’t walk away and come back later to find that one little error has stopped your entire copy operation.
It also has replaced the “Yes / Yes To All / No” style options, with more descriptive options and a “Do this for all” checkbox - thus ending cries of “Where is No To All!?!?!” (which secretly could be achieved in older version of Windows by holding down the SHIFT key while pressing No).
I fully expect it to take some time before long-time Windows users adapt to the changes in Vista. This happens every time a major OS revision occurs, especially one on such a large scale. It is my hope, though, that people will give it a try instead of assuming that things don’t work, as it seems Steve did in a few cases. An unprecedented amount of thought and testing went into Vista’s design changes. Will everyone be happy with 100% of the changes? Of course not. But taken in aggregate, I think the net effect is an overwhelming improvement.
I can say for my part that using an XP machine is decidedly less pleasant since I switched to using Vista on all of my machines. I’ve already started to take some of the improvements I mentioned above for granted, and sorely missing them when they’re gone! I’d be happy to respond to concerns from Steve or other users about how to accomplish tasks in the new shell, or about what to expect from certain features (particularly around Search) wherever I am able to. So post your comments, concerns, and questions below!
Today we released updated Add-ins for Windows Desktop Search. Most notable among the changes is that they now support Windows Vista. This includes the UNC Protocol Handler which allows you to index remote network shares (without using Offline Files).
Add-in for Files on Microsoft Networks (UNC and mapped drives)
Adobe has finally made available a beta release of Adobe Reader 8.0 - including an updated IFilter which fixes the bug the prevented it from working with WDS 3.0 / Windows Vista.
Is the holiday season here early or what? IE, Defender, Firefox, WDS… and I hear more are on the way!
Download Windows Desktop Search 3.0 for Windows XP (32-bit)
Download WDS 3.0 for Windows Server 2003 (32-bit)
Download WDS 3.0 for Windows XP/2003 (AMD64)
This release represents a HUGE amount of work across multiple teams and we’re all proud to be delivering the first WDS release that runs as a Windows service, supports 64-bit systems, and unifies our Desktop Search platform and APIs across Windows XP, 2003, and Vista.
As always, post comments with your feedback! Or head to the official forum.
[powered by WordPress.]
Hi. I'm Brandon. I'm a geek, and I work on Search technology for Windows at Microsoft. This is my blog.
The views expressed within my blog are my own - and are not in any way indicative of those of the company I work for, Microsoft, or it's employees. No warranties or other guarantees will be offered as to the quality of the opinions or anything else offered here.
Most popular searches that brought people here today:
search (11)start++ (9)an expression
contains an inva (2)windows desktop
search rebuild (2)trackpad driver
macbook pro (2)brandon live (2)itunes 64 bit
download (2)brandontools.com (2)Paths regedit wds (2)windows desktop
search shared (2)