Article ID: 1007, created on Oct 6, 2008, last review on May 10, 2014

  • Applies to:
  • Virtuozzo for Windows 3.5.1 SP1
  • Virtuozzo for Windows 3.5.1

Resolution

The default Virtuozzo setting only starts the minimal set of Windows services required for the VE (Virtual Private Server) to function. It is possible to configure which Windows services are started automatically in a new VE.

The vzsyscfg.exe utility allows you to control the set of Windows services to be started automatically in a new VE.

For example, to configure the default Windows 2003 services configuration, run this command on the Virtuozzo Host server:

vzsyscfg set --vpstype ent


After you have executed this command, each new VE will have the same set of started services as a default Windows Server 2003 installation.

For example, Server and Remote Registry will be started.

To see the list of available Windows services configurations, run this command:

vzsyscfg set --vpstype list


In general, there are two types:

Enterprise type with maximum set of standard services:

vzsyscfg set --vpstype ent 


Minimal type with minimum set of services:

vzsyscfg set --vpstype min


Services configuration will not be changed for existing VEs after you run vzsyscfg.exe. You can configure services individually for each VE using a standard Windows tool, e.g., Computer Management, services.msc, or a command line tool called sc.

To configure the Server service (which enables network sharing) for automatic startup in all running VEs, run the below commands (copy each line without the line breaks to execute it properly):

1. Configure Server service for automatic startup in each VE:

for /F "skip=3 usebackq tokens=*" %i in (`cmd /c "vzlist -o veid"`) do vzctl exec %i  sc config lanmanserver start= auto


2. Start Server service in each VE:

for /F "skip=3 usebackq tokens=*" %i in (`cmd /c "vzlist -o veid"`) do vzctl exec %i  net start lanmanserver


Steps 1 and 2 can be combined in a single batch, e.g., for Server service:

for /F "skip=3 usebackq tokens=*" %i in (`cmd /c "vzlist -o veid"`) do vzctl exec %i "cmd /c net start lanmanserver &sc config lanmanserver start= auto"


For Remote Registry:

for /F "skip=3 usebackq tokens=*" %i in (`cmd /c "vzlist -o veid"`) do vzctl exec %i "cmd /c net start remoteregistry &sc config remoteregistry start= auto"


Please note that the internal Service name as opposed to the Display name should be used for the configuration tool sc. You can determine the internal Service name from services.msc. Double-click a service in the list and note the “Service name” property.

Note: These actions can be applied on running VEs only.

965b49118115a610e93635d21c5694a8 d02f9caf3e11b191a38179103495106f a06f7889a0f0293c5c75e7ee47fa3d96 1348db476c8a5844ffbef8d503db9c15 2897d76d56d2010f4e3a28f864d69223

Email subscription for changes to this article
Save as PDF