Top
ServerView Resource Orchestrator V3.4.0 Automatic Quarantining Function User's Guide
FUJITSU Software

1.2 System Configuration in which the Automatic Quarantining Function Is Used

The automatic quarantining function provides security measures as a solution for environments in which Citrix XenDesktop, Citrix XenApp, other virtualization software, or antivirus software has been installed.

Therefore, it is assumed that the following components in the example configuration have been configured.

  • A server operated using something other than Resource Orchestrator
  • Management terminals
  • Networks (business network, quarantine network, and management network)

    Note

    Connect only the Resource Orchestrator manager to the management network.
  • SBC environments deployed on physical servers using Citrix XenApp
[VMware]
  • Virtual PC environments deployed on VMware vSphere (VMware ESXi) using Citrix XenDesktop
  • SBC environments deployed on VMware vSphere (VMware ESXi) using Citrix XenApp
[Hyper-V]
  • Virtual PC environments deployed on Hyper-V on Windows Server 2016 using Citrix XenDesktop
  • SBC environments deployed on Hyper-V on Windows Server 2016 using Citrix XenApp
[Citrix Xen]
  • Virtual PC environments deployed on Citrix XenServer using Citrix XenDesktop
  • SBC environments deployed on Citrix XenServer using Citrix XenApp

Virtual PC

In this manual, "virtual PCs" collectively refers to the following:

[VMware]
  • Virtual machines deployed on VMware vSphere (VMware ESXi) using Citrix XenDesktop
  • SBC environment servers deployed on VMware vSphere (VMware ESXi) using Citrix XenApp
[Hyper-V]
  • Virtual machines deployed on Hyper-V on Windows Server 2016 using Citrix XenDesktop
  • SBC environment servers deployed on Hyper-V on Windows Server 2016 using Citrix XenApp
[Citrix Xen]
  • Virtual machines deployed on Citrix XenServer using Citrix XenDesktop
  • SBC environment servers deployed on Citrix XenServer using Citrix XenApp

SBC Servers

In this manual, "SBC servers" refers to the following servers.

  • SBC environment servers deployed on physical servers using Citrix XenApp

Operation Network

In this manual, "operation network" collectively refers to the following networks:

For Virtual PCs
[VMware]
  • Business networks of virtual PCs deployed on VMware vSphere (VMware ESXi) using Citrix XenDesktop
[Hyper-V]
  • Business networks of virtual PCs deployed on Hyper-V on Windows Server 2016 using Citrix XenDesktop
[Citrix Xen]
  • Business networks of virtual PCs deployed on Citrix XenServer using Citrix XenDesktop
For SBC servers
  • Business networks of SBC servers deployed on physical servers using Citrix XenApp
  • Management networks of SBC servers deployed on physical servers using Citrix XenApp

When receiving email notification when a security risk is detected on an L-Server and then performing corrective action, it is possible to set a different administrator to be notified for each group of L-Servers. It is possible to manage a group of L-Servers with the same administrator using a unit referred to as a tenant.

The pools in which resources are managed are each created using a combination of a tenant and a resource type. On the manager, create a pool for resources which are related to L-Servers that do not belong to a tenant.

However, when using this function in large-scale environments where there are large numbers of L-Servers to be managed, refer to "1.3 Configuration for Managing Large-scale Environments".

Note

When using this function, use Virtual Edition. When using a platform provision service other than this function, use Cloud Edition.

  • This function does not support environments in which tenants are used or in which multiple L-Servers are configured with the same IP address.
  • This function supports environments that use folders, but does not support environments containing L-Servers with the same name under different folders.
  • This function cannot be used for L-Servers under L-Platforms.
  • Configured physical servers with UMC enabled cannot be correctly linked with L-Servers. Disable UMC before performing server registration.
  • This function does not support environments in which multiple virtual PCs configured with the same name are deployed on different VM hosts.
[VMware]
  • When using a VDS (distributed virtual switch) in a network configuration with virtual PCs, the following definition procedure must be performed in advance.
    • "E.1.4 Network Preparations" in the "Design Guide CE"
      • When Using Distributed Virtual Switch (VMware vDS)

    When two networks with the same name exist on both a standard switch and a virtual switch, if that network name is specified as the target network for server switchover, then the switchover will be performed targeting the network on the standard switch.

    To perform switchover to a network on a VDS, ensure that the network has a unique name in the system.