Removing the indexing service

[Guest]

One of the suggestions to reduce footprint size is to remove the indexing
service. It seems that the indexing service depends on the volume shadow
copy service, which in turn depends on WMI core service. Should these be
removed? If I keep removing dependencies, I ultimately have a dependency I
can't remove "class install libraries - netcfgx"

So how can I remove the indexing service and reduce footprint size? And
speed up the boot time?

Thanks,

Jeremy

 

[Guest]

So does anyone know how to do this? If I can't get a faster boot time, I'll
have to switch to a different OS.

Thanks,

Jeremy

 

[Andy Allred [MS]]

Does any other component in your config depend on these other services
you're walking down the chain to the kernel? If so, then you shouldn't
remove it.

An even better question is:
Why was Indexing service in your config, who depends on it? That is the
feature you should be concerned about because you're intentionally removing
a dependency from underneath something else. Disable the indexing component,
turn off autoresolve and run check dependency, which component(s) in the TD
task pane complains about it missing. Make your decisions based on two
things now:
- how critical is this feature i'm disabling (and the features above it ) to
my scenario
- is your device and scenario stable after having removed these dependencies
and broken a chain of dependencies?

Check the blog (linked below), and the newsgroup archives of the last 4-5
years and you will find extensive help answering basic questions.

Take care.

--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Andy Allred [MS]]

Sorry, forgot to mention, if you list the component(s) that brought in
Indexing Service and provide some context as to the type of device this is,
we can probably help you make some good guesses as to what to do here or
what would be too scary to remove <grin>

Thanks

--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Mike Warren]

Does any other component in your config depend on these other services
you're walking down the chain to the kernel? If so, then you shouldn't
remove it.

I think he's having the same problem I (and many others) had. Having
dependency errors makes me nervous about what I may be breaking.

It gets better as I gain more understanding, and of course, heavy testing
is also required.

What you've done with the feature pack appears to be a step in the right
direction. I haven't had a chance to play with it yet as I'm working on
hardware at the moment but will be back to XPE in a few weeks.

-Mike

 

[Guest]

Andy,

Thanks for the info. I'll look at the link in a few days when I get another
chance to work on the configuration. Any other links on speeding up boot
times would be greatly appreciated.

Why was Indexing service in your config, who depends on it?

Nothing, as far as I know. The only dependencies are the ones I listed,
which lead directly to the Kernel: Indexing Service -> Volume Shadow Copy
Service -> WMI Corer Service ... -> netcfgx

-Jeremy

 

[Zirong Wang]

I 'disabled' the indexing service from the beggining and my
XPe application works well.

but with the fantastic feature of Target Designer, you can
NOT just right click on the component and disable it, since
the make dependecy will bring it back again.

so zoom to the component, file, select all, disable
registry, select all, disable
resources, select all, disable.

this will work, but it is a manual operation (shame)

no, the feature pack 2007 does not fix this annoyance.
it keeps bringing this indexing service to my image,
along with outlook express, quality of service, components that
I would like to exclude.

even with my answer, I hope you consider seriously your
other option as you said in your previous post
(I will be banned from this newsgroup if I continue)

Zirong

 

[Andy Allred [MS]]

I dug into the component & file chain of dependencies bringing in Indexing
Svc.

WMI Core has a static dependency on vssapi.dll.

vssapi.dll is owned by the Volume Shadow Copy Svc as you know which in turn
brings in Indexing. I will look into making vssapi.dll a primitive, with
re-cooking of WMI Core and VSC Svc this should break the dependency chain
assuming there's no regression in the behavior of features above it. I'll
try to get this into FP2007.

thanks

--
Andy

Check out the Embedded team blog: http://blogs.msdn.com/embedded/

This posting is provided "AS IS" with no warranties, and confers no rights.