Scripting

If it is not an MSI, then when you capture the application, you will get the services in the ServiceInstall and ServiceControl table.

Also you can check the services.msc to see what all services were there before and now after installation.

You can see your base machine where you have not installed the application and see if there is a service which is different.

Capture the setup (in case of legacy setup)..Open the Wsi (or picture taker)...Check the registry HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services. If found related enteries it is part of your package.

If the application is MSI, then you can check the ServiceInstall and Servicecontrol Table to check if there are any entries.

Capture the source using any capturing tool like PictureTaker, InControl etc..

See any application related entries are there under following registry

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services

If the entry is having "ImagePath" key in it and if it is pointing to any .exe, .386 and .vxd then it can be configured through ServiceInstall and ServiceControl table.. These Services can be seen in Services.msc, otherwise you have to add them in registry table.

If the ImagePath is pointing to .sys (Kernal Driver). This will not be listed in Services.msc. This can be seen in only MSInfo32. There is a way to configure this Kernal Drivers through ServiceInstall and ServiceConfigure tables but still, it is better to add this type of Kernel Driver through registry table..

Taq jagadish and i didn't get what u r saying. I'll check in services.msc and if the application is having a service and what i have to do. I didn't understand what is image path and what is .386 nad what is .vdx