--- title: "Running an Inedo Product’s Services Interactively" order: 3 hidden: true ---

The example screenshots are from BuildMaster, but the process will be exactly the same no matter which one of our products you're using.

Refer to this table - depending on which product you are using, enter the coinciding name, or abbreviation, into each space that has a red [product's name], [service], or [XX].

The Inedo Product You're Using | [product's name] | [service] | [XX] abbreviation
| BuildMaster | bmservice | BM
| ProGet | ProGet.Service | PROGET
| Otter | Otter.Service | OTTER

#### BuildMaster & Otter

Depending on how they're configured, there will be two services configured:

- BuildMaster Service – coordinates build executions, scheduled builds, agent updates, etc.
- BuildMaster Web Server (optional) – hosts the BuildMaster web application instead of IIS
- Otter Service
- Otter Web Server (optional) – hosts the Otter web application instead of IIS

Both of these services point to the same executable (`[service].exe`), and it’s possible to run that very same service from the command-line to see everything that’s going on as it’s happening.

#### ProGet

ProGet will not have a separate web service by default:

- ProGet Service

This service points at the executable (`ProGet.Service.exe`), and it’s possible to run that very same service from the command-line to see everything that’s going on as it’s happening.

## Step 1: Stop the Services

By default, the BuildMaster & Otter services will be named INEDO[XX]SVC and INEDO[XX]WEBSRV. ProGet will be named only INEDOPROGETSVC. You can control these services a number of different ways, but the most common is to use the Services snap in.
Just navigate to Control Panel > Administrative Tools > Services, and stop the Service(s).

## Step 2: Command Line

Once the service(s) have been stopped, open up a command prompt or PowerShell (you probably want to Run As Administrator), then navigate to the [product's name] root folder (default is `C:\[product's name]\`). Next, navigate to the Service subdirectory (`cd Service`), and then type in `[service] run`.

The run command instructs the `[service].exe` to run in interactive mode. You can quit by hitting CTRL-C at any time.

## Step 3: Use and Ignore Service Warnings

From here, you can log in to the web application as you normally would. Expect to see “service not running” warnings in a number of places including the header, but everything should still work in exactly the same way.

Do not start the service while running interactively as it will likely result in several UnauthorizedAccessExceptions.