Windows Service Manager (SrvMan)

Windows Service Manager is a small tool that simplifies all common tasks related to Windows services. It can create services (both Win32 and Legacy Driver) without restarting Windows, delete existing services and change service configuration. It has both GUI and Command-line modes. It can also be used to run arbitrary Win32 applications as services (when such service is stopped, main application window is closed automatically).

Features

Here is a list of SrvMan’s key features:

Allows creating driver and Win32 services without restarting.

Supports both GUI and Command Line.

Supports all modern 32-bit and 64-bit versions of Windows

Allows running arbitrary Win32 applications as services.

Allows installing & running legacy driver services in a single command line call.

SrvMan — Command Line Options

You can use SrvMan’s Command Line interface to perform the following tasks:

Install & start a legacy driver with a single call

Note that when you run SrvMan with command-line arguments from non-console application (for example, from a Run dialog box), it displays the «Press any key to continue. » message and pauses just before exiting. This does not happen, when SrvMan is run from a console application (such as cmd.exe). To override this behavior, use the /pause:no switch.

Creating services

Use the following command line to create services using SrvMan (parameters in brackets are optional):

Service name is an internal name used by Windows to reference the service. Display name is the name displayed in Windows Services snap-in. By default, both names are generated from the .exe or .sys file name, however, you can override it by specifying names explicitly.

Service type can be one of the following:

• drv — Create a kernel driver (selected by default for .sys files)
• exe — Create a Win32 service (selected by default for .exe files)
• sharedexe — Create a Win32 service with shared executable file
• fsd — Create a file system driver service
• app — Create a service running ordinary windows application (such as taskmgr.exe)

Start mode is one of the following:

• boot — The service is started by OS loader
• sys — The service is started by IoInitSystem() call
• auto — The service is started by Service Control Manager during startup
• man — The service is started manually (net start/net stop)
• dis — The service cannot be started

Win32 services are created as interactive by default. To create a non-interactive service, you should specify the /interactive:no parameter. Normally, if a specified service already exists, SrvMan reports an error and stops. However, if you specify the /overwrite:yes parameter, an existing service will be overwritten instead.

Deleting services

Deleting services using SrvMan command line is quite obvious:

Note that you need to specify the internal service name (same as used for net start command), not the display name.

Starting/stopping/restarting services

You can control all types of services using SrvMan command line:

Normally, SrvMan waits for the service to start. However, if you specify the /nowait parameter, SrvMan will return control immediately after the start/stop request was issued. Note that if you need SrvMan to wait before starting/stopping the service (for example, to switch to real-time log viewer window), you can use the /delay: parameter.

Testing legacy drivers

You can easily test your legacy driver by using the following command line:

This command creates (or overwrites) a service for a given legacy driver file and starts it. If you have specified the /copy:yes switch, the driver file will be copied to system32\drivers directory. If /overwrite:no is specified, DbgMan will return an error if the service (or the driver file in system32\drivers) already exists. If /after: is specified, the driver will be stopped msec milliseconds after successful start. You can use this switch to test driver load/unload cycle.

Downloading

The latest version of SrvMan for both x86 and x64 systems (including sources) can be downloaded here. Note that you need BazisLib library to build the sources.

How to open Windows Services Manager in Windows 10

At times you may need to open and manage your Windows Services. You may want to stop some service, start it, disable the service, delay its start-up or resume or pause the Windows Service. At such time, the Services Manager, which is a built-in tool in the Windows operating system, will help you. This post will show you how to open your Windows Services, using Services Manager as well as the Command Prompt.

Windows Services are applications that typically start when the computer is booted and run quietly in the background until it is shut down. Strictly speaking, a service is any Windows application that is implemented with the services API and handles low-level tasks that require little or no user interaction.

How to open Windows Services Manager

To open the Windows Services Manager on your Windows 10 computer, do the following:

1. Right-click on the Start button to open the WinX Menu
2. Select Run
3. Type services.msc in the Run box which opens
4. Windows Services Manager will open.

Here you will be able to start, stop, disable, delay Windows Services.

Let us see how to do this in a bit more detail.

Right-click on your Start button to open the WinX Menu. Select Run. This opens the Run box. Now type services.msc in it and hit Enter to open the Services Manager.

Here, under the Name column, you will see the list of Services running on your system, along with their description. You will also be able to see their Status -whether they are running or stopped, along with the Startup types.

Types of Windows Services startup

Windows 10 offers four start-ups types:

1. Automatic
2. Automatic (Delayed Start)
3. Manual
4. Disabled.

Start, stop, disable Windows Services

To start, stop, pause, resume or restart any Windows Service, select the Service and right-click on it. You will be offered these options.

If you wish to manage more options, double-click on the Service to open its Properties box.

Here, under the Startup type drop-down menu, you will be able to select the startup type for the Service.

Under Service status, you will see buttons to Start, Stop, Pause, Resume the Service.

In the Properties box, you will also see other tabs like Log On, Recovery & Dependencies, which offer additional options and information.

Once you have made your changes, you will have to click on Apply and restart your computer, for the changes to take effect.

Read: What does Automatic (Trigger Start) and Manual (Trigger Start) mean for Windows Services?

Manage Services using Command Line

You can also use the Command Prompt to start, stop, pause, resume service. To use it, from the WinX Menu, open Command Prompt (Admin) and execute one of the following commands:

To start a service:

To stop a service:

To pause a service:

To resume a service:

To disable a service:

It is recommended that you not change the default settings unless you know what you are doing, as this can cause some parts of your operating system to stop working. When you stop, start, or restart a service, any dependent services are also affected, so you want to be careful here.

Настройка и использование командлетов Service Manager для Windows PowerShell Configure and use Service Manager cmdlets for Windows PowerShell

Эта версия Service Manager достигла конца поддержки, рекомендуется выполнить обновление до Service Manager 2019. This version of Service Manager has reached the end of support, we recommend you to upgrade to Service Manager 2019.

В этой статье приводятся общие сведения о командлетах Service Manager для интерфейса командной строки Windows PowerShell. This article provides an introduction to the Service Manager cmdlets for the Windows PowerShell command-line interface.

Перед выполнением любой команды в интерфейсе командной строки Windows PowerShell в Service Manager необходимо задать для политики выполнения значение RemoteSigned. Before you can run any command in the Windows PowerShell command-line interface in Service Manager, you must set execution policy to RemoteSigned. Перед запуском командлетов хранилища данных необходимо вручную импортировать модуль командлетов хранилища данных. Before you can run data warehouse cmdlets, you must manually import the data warehouse cmdlets module.

Командлеты Service Manager реализуются в следующих двух модулях: The Service Manager cmdlets are implemented in the following two modules:

System. Center. Service. Manager. System.Center.Service.Manager. Этот модуль импортируется автоматически при каждом открытии Service Manager сеанса Windows PowerShell. This module is imported automatically every time a Service Manager Windows PowerShell session is opened.

Microsoft. EnterpriseManagement. Warehouse. командлеты. Microsoft.EnterpriseManagement.Warehouse.Cmdlets. Этот модуль необходимо импортировать вручную. This module must be imported manually.

Начало работы с командлетами Service Manager Get started with Service Manager cmdlets

Windows PowerShell — это оболочка командной строки Windows с поддержкой интерактивной командной строки и среды сценариев. Windows PowerShell is a Windows command-line shell that includes an interactive prompt and a scripting environment. Windows PowerShell использует командлеты для управления объектами Windows PowerShell. Windows PowerShell uses cmdlets to manipulate the Windows PowerShell objects. Service Manager включает множество командлетов, которые можно использовать для выполнения различных задач, связанных с Service Manager, без использования консоли Service Manager. Service Manager includes many cmdlets that you can use to perform various Service Manager-related tasks without using the Service Manager console. Например, с помощью командлета Import-SCSMManagementPack можно импортировать пакет управления. For example, you can use the Import-SCSMManagementPack cmdlet to import a management pack.

Командлеты Service Manager доставляются в два модуля, которые перечислены ниже. The Service Manager cmdlets are delivered in two modules that are listed below. В Service Manager эти модули командлетов не устанавливаются в стандартном пути, указанном в переменной $env:P Смодулепас. In Service Manager, these cmdlet modules are not installed in the typical path that is listed in the $env:PSModulePath variable. Поэтому при выполнении Get-Module -List командлета модули Service Manager не перечисляются. Therefore, if you run the Get-Module -List cmdlet, the Service Manager modules are not listed.

Командлеты администратора: Модуль System. Center. Service. Manager, который содержит командлеты, необходимые для общих административных задач. Administrator cmdlets: The System.Center.Service.Manager module which contains the cmdlets that are needed for common administrative tasks.

Командлеты хранилища данных. модуль Microsoft. EnterpriseManagement. Warehouse. командлеты, который содержит командлеты, необходимые для работы в хранилище данных Service Manager. Data warehouse cmdlets: The Microsoft.EnterpriseManagement.Warehouse.Cmdlets module which contains the cmdlets that are needed for operating on the Service Manager data warehouse.

Командлеты хранилища данных работают с базой данных хранилища данных, и их можно запускать как на сервере управления Service Manager, так и на сервере управления хранилища данных. The data warehouse cmdlets operate on the data warehouse database, and you can run them on both the Service Manager management server or the data warehouse management server.

Данные, возвращаемые командой Windows PowerShell, могут содержать сведения, которые не удается отобразить в стандартном окне командной строки Windows PowerShell. Data returned from Windows PowerShell command might contain more information than can be displayed in a default Windows PowerShell command window. Рекомендуется увеличить ширину окна командной строки: щелкните правой кнопкой мыши строку заголовка, выберите пункт Свойства, а затем на вкладке Макет задайте для параметра Размер буфера экрана значение 120. We recommend increasing the width of the command window: Right-click the title bar, click Properties, and in the Layout tab, set the Screen Buffer Size width to 120.

Следующие процедуры помогут приступить к работе с командлетами Service Manager. The following procedures help you to get started with Service Manager cmdlets.

Открытие Service Manager сеанса Windows PowerShell из консоли Service Manager To open a Service Manager Windows PowerShell session from the Service Manager console

В консоли Service Manager щелкните элемент Администрирование. In the Service Manager console, click Administration.

В области задачи щелкните запустить сеанс PowerShell. On the Tasks pane, click Start PowerShell Session.

Модуль командлета администратора автоматически импортируется в этом сеансе. The administrator cmdlet module is automatically pre-imported in this session.

Открытие Service Manager сеанса Windows PowerShell из Windows To open a Service Manager Windows PowerShell session from Windows

На компьютере, на котором размещен сервер управления Service Manager, на панели задач нажмите кнопку Пуск, укажите пункт все программы, а затем выберите пункт Microsoft System Center. On the computer that hosts the Service Manager management server, on the taskbar, click Start, point to All Programs, and then click Microsoft System Center.

Щелкните **Service Manager **и выберите Service Manager Shell (оболочка). Click Service Manager , and then click Service Manager Shell.

Модуль командлета администратора автоматически импортируется в этом сеансе. The administrator cmdlet module is automatically pre-imported in this session.

Вывод списка всех командлетов Service Manager To list all Service Manager cmdlets

Откройте Service Manager сеанс Windows PowerShell. Open a Service Manager Windows PowerShell session.

Чтобы получить список командлетов, которые включены в модуль администратора, в Service Manager сеансе Windows PowerShell введите следующую команду и нажмите клавишу ВВОД: To list the cmdlets that are included in the administrator module, in the Service Manager Windows PowerShell session, type the following, and then press ENTER:

Чтобы получить список командлетов, которые включены в модуль хранилища данных, в Service Manager сеансе Windows PowerShell введите следующую команду и нажмите клавишу ВВОД: To list the cmdlets that are included in the data warehouse module, in the Service Manager Windows PowerShell session, type the following, and then press ENTER:

Справка по командлетам To get Help for a cmdlet

Откройте Service Manager сеанс Windows PowerShell. Open a Service Manager Windows PowerShell session.

Теперь можно получить доступ к интерактивной справке или использовать -online параметр для доступа к самой последней справке в Интернете: You can now access the on-the-box Help, or you can use the -online parameter to access the most up-to-date online Help:

Встроенная справка: введите следующую команду. On-the-box Help: Type the following command. Замените Командлет-Name именем командлета, для которого требуется получить справку, например Import-SCSMManagementPack: Replace cmdlet-name with the name of the cmdlet that you want to get help for, for example, Import-SCSMManagementPack:

Оперативная справка: введите следующую команду и нажмите клавишу ВВОД: Online, up-to-date Help: Type the following command, and then press ENTER:

Эта команда использует -online параметр для доступа к последней интерактивной справке для командлета. This command uses the -online parameter to access the latest online Help for a cmdlet. Он открывает веб-браузер и отображает справку в Интернете, доступную для командлета Name. It opens a web browser and displays the online Help that is available for cmdlet-name.

Список командлетов Service Manager List of the Service Manager cmdlets

Service Manager поддерживает следующие командлеты Windows PowerShell, которые реализуются в двух модулях: модулем администратора и модулем хранилища данных. Service Manager supports the following Windows PowerShell cmdlets, which are implemented in two modules: the administrator module and the data warehouse module.