If my user has wants to use the indexing service is it normal for cisvc.exe
to eat up cpu cycles all the time? I just upgraded him to office 2007 and he
complained about speed issues but says that now they are not as bad.

Is this a byproduct of the indexing service indexing all of the files and
now that it is complete it is ok?

Not only is it normal, that's why many people turn off indexing altogether.

XP's built-in indexing service is not even that good at indexing -- it
is, after all, almost 7 years old.

There are many better indexibg utilities -- including ones available
from Microsoft -- but I am not able to offer a suggestion since I do not
use file indexing myself.
---
Leonard Grey
Errare humanum est

bluestar76 wrote:
> If my user has wants to use the indexing service is it normal for cisvc.exe
> to eat up cpu cycles all the time? I just upgraded him to office 2007 and he
> complained about speed issues but says that now they are not as bad.
>
> Is this a byproduct of the indexing service indexing all of the files and
> now that it is complete it is ok?