Adjusting Container Configuration and Advanced Settings

The Configure page allows you to adjust the main settings for your Containers. If the Container was created singularly, you might have provided it with a name and a description. If the Container was one of Containers created as a group, providing names and descriptions were not available. In the General Configuration group you can change the name or description of a Container created singularly, or assign a name and a description to a mass-produced Container.

Expand the Advanced group to:

• Have the Container start disabled by selecting the Disable this Container checkbox (may be caused by business requirements).
• Make the Container automatically boot at the Hardware Node startup. For this purpose, select the Start on the Hardware Node boot checkbox.
• In the Capabilities group you can:
  • switch on/off the network browsing for the Container. The Windows 2003 browser service allows the Container on a Windows 2003 network to view all the network environment available. The browser service maintains a list (called the browse list) of all available domains and computers. The browse list can be viewed using Windows 2003 Explorer and is provided by a browser in the Container. The default for the feature is the off status. You can learn more on the option from the Network Places overview article of the Windows 2003 Help system invoked by selecting Help and Support on the Windows Start menu.
  • enable/disable the packet QoS scheduler for the Container. This is one of the Quality of Service components in MS Windows 2003 Server that enable differentiation and preferential treatment for subsets of data transmitted over the network. The packet scheduler is the traffic control module that regulates how much traffic various applications are allowed, essentially enforcing the QoS parameters that are set for each particular application. For instance, you can use the feature to restrict a web site throughput to a certain maximum bandwidth value or differentiate between the data transmitted by critical applications (e.g. Plesk) and excessive data (e.g. multimedia applications), and allow preferential treatment for the important web sites or critical applications. The option is disabled by default. For additional information on the packet scheduler, address the MSDN Library > Win32 and COM Development > Network Protocols > Quality of Service (QOS) ( http://msdn.microsoft.com/library/default.asp?url=/library/en-us/qos/qos/qos_start_page.asp ) .

    Note: The concept of Quality of Service in MS Windows 2003 Server differs from that of Virtuozzo Quality of Service used to provide a fair share of the main system resources (disk space, CPU time, etc.) among Containers.

  • let you know at a glance the ID of the Container to which you have connected by means of RDP. This ID is displayed in the upper right corner of the remote desktop.
  • enable/disable the Microsoft Cluster Server (MSCS) software to run inside the Container. The MSCS software integrated into the Windows Server 2003 operating system is designed to allow servers to work together as one server, thus, providing greater reliability for your applications and services. Running one and the same application on two or more servers in the cluster helps ensure high application availability if one of the servers fails. The clustering software controls the failover process so that the application continues running on the second server without any loss of data and without interruption in service. The Virtuozzo Containers software allows you to include Containers in a server cluster so that they can act as full participants (nodes) in the cluster. To learn more about the MSCS software, address MSDN Library > Servers and Enterprise Development > Windows Server > Windows Server 2003 > Technical Articles > Introducing Microsoft Cluster Service (MSCS) in the Windows Server 2003 Family ( http://msdn2.microsoft.com/en-us/library/ms952401.aspx ).

The options in the Capabilities group are enabled/disabled by selecting/clearing the corresponding checkboxes.

The Terminal Services group allows you to define in which one of the two standard Windows TS modes (Remote Desktop for Administration and Terminal Server) the created Containers will operate. By default, any Container is automatically set to work in the Remote Desktop for Administration mode during its creation. So, you do not need to perform any additional operations to start connecting to Containers using this mode. Like in any other system with Windows Server 2003 installed, the Remote Desktop for Administration mode allows you to simultaneously open no more than two remote sessions and a console session to any Container on the Hardware Node.

If you are planning to have more than 2 remote sessions to a Container at the same time, you should enable the Terminal Server mode for this Container. You may also need to switch on this mode in case some of the Container applications require Terminal Server for their functioning. While set in the Terminal Server mode, the Container starts using the same Terminal Server License (TSL) server as the Hardware Node does. So, you can log in to the Container in this mode provided the TSL server for the Node is accessible by the Container and has a number of free client access licenses (CALs) installed. You can also redefine the TSL server to be used by the Container or set additional TSL servers for it in the License Server Address field.

The Offline Management group allows you to set the offline management options by selecting the appropriate radio button. Offline management of the corresponding Container ensures the Container manageability by means of one or more offline services from any browser at its own IP address. After offline management is enabled for the Container, one port of its IP address becomes permanently active whatever the Container state. The currently supported services are vzpp and plesk (for managing Containers with the Plesk control panel installed in them). You can:

• Disable the offline management of the Container.
• Enable the offline management of the Container via the offline management settings operating on the Hardware Node. Whenever you need to manage the Container offline, its offline management settings will be brought into synchronization with those in effect on the Node. Should any service be removed from the default services list, the Container will be unable to be managed via the service off the list. This option subscribes the Container to the default offline services.
• Manually compose the Container offline services list. You can select the service(s) you would like the Container to be subscribed to in the corresponding checkbox(es).

Press the Submit button to save the changes.

Please send us your feedback on this help page