Hi @nicks8850 ,
Instead of trying to classify the process, you can make the Windows Service itself the entry point for your application pattern. Think of it like saying: *“Whenever Discovery finds this service running, that’s my application.”*
1. Create a new application pattern (don’t just extend the OS server one).
2. In the Identification section, tell the pattern to look for the Windows Service CI (`cmdb_ci_win_service`).
- Match it by service name (e.g., `MyServiceName`).
3. Use that service as the anchor for your application.
4. Add any dependencies you need (ports, related processes, connections).
5. Run Discovery on a server where the service is running to test it.
6. Check that the application service record is created and linked to the Windows Service CI.
- You bypass the process classifier entirely.
- You’re using the fact that Discovery already populates Windows Service records.
- You’re telling Service Mapping: *“This service = my application.”*
- If your app depends on other components (databases, web ports, etc.), add those relationships in the pattern.
- Always test in sub‑prod first, because pattern changes can ripple across your CMDB.
- If you want the service to be recognized consistently, you may also need to tweak Identification & Reconciliation rules so the service is tied to the right application record.
Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for
Kind Regards,
Pavani P
