Disable unused Services

[Guest]

Hi,

Because of unintelligibly and deep dependency structures my system contains
services (e.g. Themes, Spooler, Telephony, Wireless Zero Config) i dont
really want.

Is there a way to disable unused services in target designer?
Ok, i resign myself to have them on the system, but how can i disable them?

(By the way, according to the dependencies: just simple Media Player leads
over internet connection wizard, ras, and some more steps to telephony???
wastful of effort, just for playing some media files???
My suggestion for the target designer: resolve dependencies just for a
adjustable deepth)

 

[Andy Allred [MS]]

Hi.
Are these dependencies you don't want from XPe-SP2 or FP07? I ask
because some of the dependencies may be removed or refactored in the
feature pack to reduce footprint.

If the service registration information is in the component and not
being setup during FBA through COM registration, then you could try
changing the start type value in the registry node for the component.
Otherwise you would have to stop the service post FBA ("net stop" for
instance, or editing the registry online or offline with regedit).

 

[JS]

You can also disable services with

sc.exe config <yourservicename> start= disable


note: it is important to have the spacing right.

 

[KM]

Actually it TD it might be easier to change particular component resources than set up new set of commands to launch at run time.
Also, it would be more efficient to have the services created with disabled states than change their states on fly.

For instance, Print Spooler component. Open up its registry section and find
[HKLM\System\CurrentControlSet\Services\Spooler],"Start" dword value and change it from 2 (manual) to 4 (disabled).
For some other components you can do the same in FBA Resource section where a service resource is created (Start value there is
exposed as a field).

And after all, you don't necessarily have to auto-resolve all dependencies in TD. If you turn off the auto-resolve dependency option
there and feel comfortable to have a few unresolved errors you can reduce the image footprint much by not including those components
you mentioned. This is going to work only of course assuming getting rid of those components doesn't break the functionality of the
image you are looking for. This is going to be up for your testing though.