Search
Wednesday, January 07, 2009 ..:: Home ::.. Register  Login
Blog roll

Topic search

UsersOnline
Membership Membership:
Latest New User Latest: ginnyihmv
New Today New Today: 1
New Yesterday New Yesterday: 0
User Count Overall: 121

People Online People Online:
Visitors Visitors: 0
Members Members: 0
Total Total: 0

Online Now Online Now:

Blogs
Aug 22

Written by: Justin James
8/22/2008 10:19 AM

Windows Server 2008 has the most broken feature I have seen in a Micrisoft product in a long time: file searching. Like Vista, Server 2008 has some really nice file searching features that make heavy use of the file indexing. Sadly, some idiot decided to make the system search only indexed items by default, and then turned off the indexing by default!

The end result? A hopelessly broken search system that is insanely frustrating to use. You either need to manually tell each search to use non-indexed content, turn on indexing (you may very well not want to do this on a server!), or change the default settings to always use non-indexed content. Whoever set up these defaults is a fool. It's a lot like the problem in Server 2003, where the checkbox for "Search Tape Backups" also seems to regulate whether or not it will actually search on a network drive, even if you've specified a network drive as being where to search.

J.Ja

Tags:

8 comments so far...

Microsoft can't do search, LIVE or otherwise

There are so many other tools that search effectively, such as X1 or the free "Agent Ransack". Search in Windows has been absolute crap since XP debuted, and it is only marginally better. Worse, the newest "Windows Desktop Search 4" stores the indexes in the "All Users" folder where Encrypting File System cannot be used. Note that X1 has allowed search indexes to be stored for EACH USER. So you can use EFS to protect a user's index.

Really, Microsoft WANTS to be a big search company, but I suggest they begin by searching for a clue!!

By B. Goodman on   8/22/2008 11:12 AM

Re: Broken Search in Windows Server 2008

I know that Live Search is wretched... I use it on a daily basis. It's a personal decision, and I have my reasons for using it, but it really isn't great. But the reasons why Live Search is not good is completely different from why their desktop search isn't good. On this note, their search division just got reorged this week, and I am not surprised. Their market share keeps plummeting. I actually think that their search is no worse than Google's or Yahoo!'s search; I think that all three provide equally bad results. But Google has a much better overall package than Live Search, and that counts for a lot.

J.Ja

By jmjames on   8/22/2008 11:55 AM

Microsoft can't do search, LIVE or otherwise

There are so many other tools that search effectively, such as X1 or the free "Agent Ransack". Search in Windows has been absolute crap since XP debuted, and it is only marginally better. Worse, the newest "Windows Desktop Search 4" stores the indexes in the "All Users" folder where Encrypting File System cannot be used. Note that X1 has allowed search indexes to be stored for EACH USER. So you can use EFS to protect a user's index.

Really, Microsoft WANTS to be a big search company, but I suggest they begin by searching for a clue!!

By B. Goodman on   8/22/2008 12:12 PM

Re: Broken Search in Windows Server 2008

The reasons are completely different, I'll grant you. But the end result is that both products are BAD. Poor in concept, poor in design, poor in execution. I've been a fan of X1 for years, but my search needs are probably more modest than yours, so I may not know a great search tool when I see it. But I sure know a BAD one when I see it!

To bastardize a Churchill quote, Google is a terrible search engine, except for all the rest.

By B. Goodman on   8/22/2008 12:12 PM

Re: Broken Search in Windows Server 2008

I think Microsoft's biggest problem (oddly enough), is that they pay *too much* attention to users. It's why you see "featureitis" in their products. They get feedback from thousands of organizations, hundreds of thousands (if not millions) of users of some of their products... and then they try to complete every use case that was generated. It's insane. Google (and many other companies started in the Internet age) have an opposite approach to this. They simply listen to customers, and pick the one or two things that *everyone* wants, or they figure out the one unspoken use case, or figure out the #1 "pain point" and solve it. As a result, these companies have much easier to use products. Like with Web mail, Google figured out that the #1 pain point with Web mail was storage space. GMail's "killer feature" when it lauched was simply having a lot of storage space, nothing revolutionary about that.

So when Microsoft sets themselves to solving the desktop search problem, they come up with a monstronsity that only an engineer could love... endless settings, both permanent and "per-use", and if you don't configure it "just so", not only will it take longer, you might not even get what you need! It's really idiotic.

J.Ja

By jmjames on   8/22/2008 12:35 PM

Bahahahahah

I am sorry, but that is too funny.

Some one was clearly not thinking when they set the defaults for the build. That should be updated for a service pack.

By nuCrash on   8/22/2008 2:23 PM

It's not broken; you need to install Search 4.0

It's not broken.

You need to install Search 4.0 which finalized after 2008 went gold. It will integrate Vista and Server 2008 search apparently.
http://formortals.com/Home/tabid/36/EntryID/89/Default.aspx

You can also install the free enterprise search product http://blogs.zdnet.com/Ou/?p=1033.

By host on   8/22/2008 5:39 PM

Re: It's not broken; you need to install Search 4.0

If you need to install something to make search work, then it is broken.

Your statement is like saying that Ford Pintos weren't dangerous when rear-ended because you could install a bladder in the gas tank.

By The unknown poster on   8/26/2008 8:42 PM

Your name:
Title:
Comment:
Add Comment    Cancel  

Links

Blog_Archive

New_Blog
You must be logged in and have permission to create or edit a blog.

Search_Blog
Print  

Copyright 2008 by George Ou or Justin James   Terms Of Use  Privacy Statement
DotNetNuke® is copyright 2002-2009 by DotNetNuke Corporation