Environmental Specifications

vsmStudio

vsmStudio is the core component of a VSM installation and is operated 24/7/365. Each vsmStudio instance must be operated on a dedicated server, that matches the official server specifications as listed below. The user-account requires admin rights to run vsmStudio as administrator.

vsmGadgetserver, vSNMP

vsmGadgetserver and vSNMP are components operated 24/7/365 and directly connected with vsmStudio. They must be operated on servers separated from the vsmStudio servers. It is recommended to install and operate vsmGadgetServer and vSNMP on machines following the official server specifications as listed below.

Server Hardware Specifications

Please refer to Current Hardware Specifications

Purchasing Servers

You can order any of the Servers listed above directly from Lawo, or buy Servers from your preferred supplier following the specifications above:

  • Lawo-supplied Servers: when you buy your server directly from Lawo it will be fully built, pre-configured and tested, and VSM will be licensed. Lawo-supplied servers will follow the latest specifications.
  • Customer-supplied Servers: if you buy a Server directly from your supplier following the specifications above, then Lawo provides a download link to an installation image. The image contains all officially supported drivers for the relevant platforms.

Restrictions applying with the use of Server Hardware

  • Servers as specified in this documentation are mandatory. Alternative HP models or servers or different manufacturers are not supported. Lawo does not supply images for other server types and only maintains servers of the specified types in its lab.
  • Using the provided ISO-Images from Lawo is mandatory. The ISO Images as provided by Lawo not only installs the required component (vsmStudio), but also set the system partitions as recommended by Lawo and manages performance settings. Furthermore, the images provide the compatible drivers.

A Windows Server® EN/DE standard license and product key must be provided by the customer either way.

It is mandatory to use the installation image OR purchase a pre-configured Server directly from Lawo. Lawo cannot be held liable for any fault caused by not supported hardware. This includes servers. Furthermore, product support might be limited.

Server Administration

For a proper operation and support, the following server administration rules apply:

  • VSM is compatible with Windows® Server® versions, which are officially supported by Microsoft. Microsoft will announce their products "end of support" and will stop providing updates.
  • The customer is responsible to keep Windows® Server® on his machines "up-to-date" (see OS patches and updates). Only up-to-date platforms can be analyzed deeply in case of support.
  • VSM components should be kept up-to-date. Lawo is providing component updates and upgrades through various software releases, so we recommend to run the latest public update (patch) of a major release. Please find the latest releases in the Lawo Downloadcenter.

Visit www.lawo.com and register for our product newsletter for latest news and announcements around VSM.

Server Virtualization

For the operation in live production environments, it is not generally permitted to run vsmStudio on virtualized systems but may be approved on project basis. VSM components, like vsmGadgetServer, vSNMP, etc. may be operated on virtual machines, but must not be operated within a shared resource environment. In any case, CPU, Memory, etc. must be exclusively available for the specific VSM component.

Teaming NICs

Teaming in general is not recommended. If you plan to use Teaming on your server, configure your network Team to NFT (Network fault tolerance only; with or without preferred order). It is recommended to use Teaming for network connection redundancy purposes only. Teaming to enable link aggregation is not required in regular vsmStudio environments.

Do not use any other teaming mode like Smart load balancing or similar.


The following settings for NFT Teaming are recommended:

  • Use the integral Windows Server Teaming functionality
  • Team size: max. 2 adapters
  • Teaming mode: switch independent Teaming mode
  • Load balancing mode: Address hash
  • Choose 1 adapter to be standby adapter
  • Ideally, connect both adapters to separate switches

LAN Adapters

If you need to connect to several subnets on your server, configure the routing on your switch or router. Do not use more than one of your server's LAN adapters, unless it is member of a Team.
Also, do not use the other LAN-Adapters to connect your server to the internet, e.g. for maintenance reasons. Instead, configure the routing on your switch or router accordingly.
Multihoming (e.g. to use several NICs to connect to multiple Subnets) is not supported for vsmStudio Servers. This is no restriction of the vsmStudio application as such, but due to protocols used for remote control. Multihoming may be used for vsmGadgetServer in combination with "Binding" Consumer Ports to a specific NIC.

Operation of Concurring Software

No concurring software, neither from Lawo or 3rd party, must run in parallel to vsmStudio or vsmGadgetServer. Both services require full availability of the specific server performance at any time. Concurring applications will co-use the same hardware and reduce the overall performance available for VSM, in worst case during peak operations. Lawo cannot be held liable for any fault caused by concurring applications operated on a VSM Server in parallel to vsmStudio or vsmGadgetServer services.

For security reasons, Virus scanners and firewall software may be installed on the servers. In the case virus detection software and/or firewall software is operated in parallel, the customer must make sure, that no automatic or scheduled systems scans occur. Antivirus Network Filter Drivers must not be installed.

Server OS Patches and Updates

Keeping the operating systems of your servers up to date is one of the most important measures for the operational security of your system.

The customer is responsible to keep the VSM Server OS up to date. OS patches and updates should be manually installed when available (see chapter LAN Adapters to learn more about connecting the server to the internet for downloading patches).

Do not configure servers to download and install Windows® Server® updates automatically. Make sure, the process of keeping Windows® Server® up-to-date is completely under your control.

As some patches and updates require the system to restart, make sure to schedule downtimes properly.

OS Upgrades may cause incompatibilities. Before planning an upgrade, please make sure to check if vsmStudio is compatible with the upgrade version → check the Changelog of vsmStudio. It is strongly recommended to install all Windows OS updates before doing a vsmStudio update or upgrade.

Running VSM Servers in Domains

It is generally possible to have VSM Servers under domain control – but it is mandatory to follow some rules.

  • When a server or a PC is managed within a domain, then it is going to be assigned to an OU (Organizational Unit). For each OU, the administrator defines a set of policies which applies to the grouped gear.  This includes rules such as virus scans, update policies, etc. OUs heritage their settings to child OUs.
  • It is strongly recommended to manage VSM servers in a separate, dedicated OU containing just specific VSM related policies. They must be no child from other, existing OUs. Alternatively, heritance must be switched "off"!
  • Any policy within the VSM OU should be defined according to the runtime specifics of a VSM Server. These are defined exclusively by the production/operation schedule, and not primarily by any IT regulations. For example, high performance virus scans during live productions must be avoided. OS updates should never be loaded and must never be installed when available, if there is a potential risk to affect production. Necessary update installations must be synchronized with the production schedule to ensure reliable and proper operation at any time necessary. Make sure to define service windows in sync with production. Always do updates manually, never automatically.
  • VSM works with a standard user account. During runtime, this user is logged in via Auto Login. In a domain, the account may be different from default, and it also may follow password rules. In case the default VSM user and password will be changed, it is recommended to share the credentials with the Lawo Service team, in case there is need for emergency remote support.
  • If domain-controlled servers are causing issues during production caused by domain policy settings, Lawo will not take responsibility. If you are not sure about your domain control settings, remove any policy from your VSM OU or skip domain control for VSM Servers.