Multiple Instances of One Windows Service for MMC RRS feed

  • Question

  • Hope I'm in the right forum for this.

    If not, feel free to move or recommend a forum.

    I have one Windows Service, say GatherData.  I want to have one installation for this service that creates multiple instances with different names and Instrumented namespaces for MMC, all on one machine.

    For example:

    • GatherData 9111
    • GatherData 9112
    • GatherData 9113
    • etc.

    The Instrumented namespaces can have the same names.

    I'm thinking an app.config containing the following section:

        <Installer BaseService="GatherData">
          <!-- Multiple versions of the service, adjust as required -->
          <!-- Adjust before running InstallUtil -->
          <!-- InstallUtil will use this to install one or more service(s) -->
          <!-- If you only want one GatherData service, remove the <Extensions> section-->
            <add Extension="9111" />
            <add Extension="9112" />
            <add Extension="9113" />

    Then, perhaps a ProjectInstaller that can read through the extensions, and install the instance of each service and set up the snap-in for MMC?

    Trying to avoid many manual steps for the person that would actually install these, not me.

    InstallUtil is not necessary, just thought I would need to go that route.

    Tuesday, March 3, 2020 3:51 PM


All replies

  • Hi Lanis Ossman,
    This is a forum for handling desktop software publication and installation. It does not involve Windows Service. I will move it to "where is the forum for" forum and someone in this forum will move the case to the correct forum.
    Thank you for your understanding.
    Best Regards,
    Daniel Zhang

    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, March 4, 2020 1:35 AM
  • Noticed this hadn't moved, so I wrote it up in the forum you mentioned.
    Wednesday, March 4, 2020 11:57 AM