Central Repository for Tracking Win Service (and other services) Location
-
I am thinking about the process of tracking Win Services that are developed by the company. The tracking information will go to a central location (database, text file, ...) and would include details such as: Name, location, Start/End DateTime, Current User, and any other details that may come up during the discussion. This is coming from the fact I am working at a company that has several custom Win Services running across several servers and, dare I say, possible, local machines. I have been tasked with modifing a Win Service that monitors an inbox on an Exchange server and process incoming emails. This service eventually moves the email from the inbox to another folder. The service is currently running in the test environment and moving the emails. This keeps me from testing my code, because the emails are being moved by the other service that is running "somewhere" My thought is to create a class library that could be added to a Win Service that would allow this tracking to a central repository. Then create a UI for easy viewing of retime information for ALL custom developed services across the network. Would love some input on this idea. I hope I gave enough details to get my thoughts across.
-
I am thinking about the process of tracking Win Services that are developed by the company. The tracking information will go to a central location (database, text file, ...) and would include details such as: Name, location, Start/End DateTime, Current User, and any other details that may come up during the discussion. This is coming from the fact I am working at a company that has several custom Win Services running across several servers and, dare I say, possible, local machines. I have been tasked with modifing a Win Service that monitors an inbox on an Exchange server and process incoming emails. This service eventually moves the email from the inbox to another folder. The service is currently running in the test environment and moving the emails. This keeps me from testing my code, because the emails are being moved by the other service that is running "somewhere" My thought is to create a class library that could be added to a Win Service that would allow this tracking to a central repository. Then create a UI for easy viewing of retime information for ALL custom developed services across the network. Would love some input on this idea. I hope I gave enough details to get my thoughts across.
At one place where I wrote a bunch of Windows Services I baked that in from the beginning, with a central database table to contain configuration and some runtime info (last start, last stop, etc.); I don't know how you could add it to existing systems, especially if you don't even know which systems are running what to begin with.
-
At one place where I wrote a bunch of Windows Services I baked that in from the beginning, with a central database table to contain configuration and some runtime info (last start, last stop, etc.); I don't know how you could add it to existing systems, especially if you don't even know which systems are running what to begin with.
My thought is to really push this moving forward with new services. As we go back and modify the older services we could add this. If it works out well, maybe they will create a project to go back and modify the older ones. At least the critical ones. :)
-
I am thinking about the process of tracking Win Services that are developed by the company. The tracking information will go to a central location (database, text file, ...) and would include details such as: Name, location, Start/End DateTime, Current User, and any other details that may come up during the discussion. This is coming from the fact I am working at a company that has several custom Win Services running across several servers and, dare I say, possible, local machines. I have been tasked with modifing a Win Service that monitors an inbox on an Exchange server and process incoming emails. This service eventually moves the email from the inbox to another folder. The service is currently running in the test environment and moving the emails. This keeps me from testing my code, because the emails are being moved by the other service that is running "somewhere" My thought is to create a class library that could be added to a Win Service that would allow this tracking to a central repository. Then create a UI for easy viewing of retime information for ALL custom developed services across the network. Would love some input on this idea. I hope I gave enough details to get my thoughts across.
You could use the WMI to scan the network list out all of the services on every machine. Little parsing to figure out a common list of normally installed services to expose the random creatures?
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
-
You could use the WMI to scan the network list out all of the services on every machine. Little parsing to figure out a common list of normally installed services to expose the random creatures?
Common sense is admitting there is cause and effect and that you can exert some control over what you understand.
Good call. I did put together a WMI query to find the services. The goal is to use this to get started with the tracking process. Then use the class library in each service to "register" and/or "unregister" themselves from a central repository.