D800142X012

August 2022

Virtualizing a DeltaV System With HCI

Architecture
 © Emerson 2022. All rights reserved. The Emerson logo is a trademark and service mark of Emerson Electric Co. The DeltaV logo is
a mark of one of the Emerson family of companies. All other marks are property of their respective owners. The contents of this
publication are presented for informational purposes only, and while every effort has been made to ensure their accuracy, they are
not to be construed as warranties or guarantees, expressed or implied, regarding the products or services described herein or their
use or applicability. All sales are governed by our terms and conditions, which are available on request. We reserve the right to
modify or improve the design or specification of such products at any time without notice.
The Emerson logo is a trademark and service mark of Emerson Electric Co. The DeltaV logo is a mark of one of the Emerson family
of companies.

See the CE statement in the Preface to this manual.

Emerson Automation Solutions

1100 W. Louis Henna Blvd.
Round Rock, TX 78681

2
 Contents
D800142X012 August 2022

Contents
Chapter 1 About this documentation............................................................................................. 7
Chapter 2 Planning the DeltaV Virtual Studio Installation............................................................... 9
2.1 HCI network architecture................................................................................................................. 9
2.1.1 Server cable connection points....................................................................................................11
2.1.2 Server connection plans.............................................................................................................. 11
2.1.3 Network port assignments on the Dell PowerEdge R740xd XL..................................................... 14
2.2 About the DeltaV Virtual Studio client............................................................................................ 16
2.3 Supported operating systems for DeltaV Virtual Studio.................................................................. 17
2.4 Licenses for operating systems....................................................................................................... 17
2.5 DeltaV virtualization templates...................................................................................................... 18
2.6 Reserved DeltaV IP addresses......................................................................................................... 23
2.7 Virtual system resource planning guidelines...................................................................................25
2.8 Recommended system capacities for the Dell PowerEdge R740xd server....................................... 27
2.9 User accounts for the virtualized DeltaV system............................................................................. 27
2.10 DeltaV Smart Switch ports and virtual machines...........................................................................29
2.11 System time in a DeltaV virtual system......................................................................................... 30
2.12 Synchronize DeltaV system time with an external node................................................................33
2.13 Downloads to obtain before starting............................................................................................ 34
2.13.1 Download updates for Dell servers............................................................................................ 34
2.13.2 Download Microsoft updates.....................................................................................................35

Chapter 3 Installing DeltaV Virtual Studio on an HCI system......................................................... 37

3.1 Checklist for installing DVS on an HCI system................................................................................. 37
3.2 The Autorun.Hci interface.............................................................................................................. 39
3.3 Set up a Windows Server host computer........................................................................................ 43
3.4 Configure RDMA.............................................................................................................................44
3.5 Initialize a host................................................................................................................................47
3.6 Configure the S-Series switch......................................................................................................... 49
3.7 Enable or disable S-Series switch ports............................................................................................51
3.8 Configure the N-Series switch.........................................................................................................53
3.9 Setting up domain controllers........................................................................................................ 54
3.9.1 Configure a virtual host domain controller...................................................................................55
3.9.2 Configure a physical host domain controller................................................................................58
Enable or disable Remote Shell access................................................................................................... 60
Configure DNS addressing for host network on domain controllers....................................................... 61
Configure an additional host domain controller as a VM........................................................................ 62
3.10 Join a host to a domain................................................................................................................. 65
3.11 Harden domain controllers...........................................................................................................65

iii
Contents
August 2022 D800142X012

3.12 Create a domain-level account for DVS.........................................................................................66

3.13 Install DeltaV Virtual Studio.......................................................................................................... 67
3.14 Copy the DVS license to the DeltaV Virtual Studio computer........................................................ 70
3.15 Using the virtualization system identifier......................................................................................71
3.15.1 Install the DeltaV Virtualization system identifier...................................................................... 71
3.15.2 Install the DeltaV Virtualization system identifier on a VM......................................................... 72
3.16 Configure hosts for live storage migration.................................................................................... 74
3.17 Start the DeltaV Virtual Studio client............................................................................................ 75
3.18 Set up the hosts............................................................................................................................75
3.19 Copy release-specific files to the host........................................................................................... 76
3.20 Set up host networks.................................................................................................................... 77
3.21 Set up the witness machine.......................................................................................................... 78
3.22 Set up a cluster............................................................................................................................. 79
3.23 Set up virtual networks................................................................................................................. 80
3.24 Installing the DeltaV Remote Desktop Connection (DRDC)...........................................................81
3.24.1 Supported operating systems for the DeltaV Remote Desktop Connection............................... 84
3.24.2 Allowed DeltaV Remote Desktop Connection types.................................................................. 85
3.24.3 Using the DeltaV Remote Desktop Connection commands....................................................... 86
3.25 Additional setup actions following DVS installation...................................................................... 87
3.25.1 Upgrade the N-series switch OS.................................................................................................87
3.25.2 DeltaV Virtual Studio Registration service..................................................................................88
Modify the DeltaV Virtual Studio Registration CONFIG file.....................................................................89
Upload a DeltaV Virtual Studio registration file to the Guardian website................................................89
3.25.3 Create and configure a system of VMs in an IDDC Domain.........................................................89
Create Independent DeltaV Domain Controller VMs..............................................................................90
Configure Independent DeltaV Domain Controller VMs.........................................................................92
Create a ProfessionalPLUS VM............................................................................................................... 93
Configure the ProfessionalPLUS VM.......................................................................................................95
Connect USB to IP Device...................................................................................................................... 97
Create nodes in a DeltaV system and generate DVData File................................................................... 99
Create multiple VMs using the VM Builder Tool..................................................................................... 99
3.25.4 Creating VMs from OS-only templates.....................................................................................101
Create a non-DeltaV Server 2016 or Server 2022 VM........................................................................... 101
Configure the non-DeltaV Server VM...................................................................................................102
Configure a base station VM................................................................................................................ 103
3.25.5 Install software from ISO file onto the virtual machine.............................................................106
3.25.6 Setting up a thin client computer............................................................................................ 107
Thin client redundant network............................................................................................................ 110
Thin client computer security settings.................................................................................................112
Configure the thin client network redundancy.....................................................................................112
3.25.7 Set up a thick client computer................................................................................................. 113

iv
 Contents
D800142X012 August 2022

3.25.8 Connect to the virtual DeltaV Application Station....................................................................115

3.25.9 Host user setup for Connect to console option ....................................................................... 115
Requirements for Connect to Console from a client in a workgroup to a host in a domain................... 116
Using impersonation........................................................................................................................... 118
Network connectivity.......................................................................................................................... 119
Client is in a workgroup and host is in a domain...................................................................................119
Client and host are in the same domain............................................................................................... 121
Set trusted hosts for Connect to Console.............................................................................................121
Create a domain user...........................................................................................................................122
Add a domain user to the Connect to Console group...........................................................................122
Add a domain user to a local group for impersonation.........................................................................124
3.25.10 Using Connect to Console..................................................................................................... 125
Change the DeltaV Virtual Studio service account (VirtualizationAdmin) password.............................126
User Access Control and running the DeltaV virtualization applications...............................................127
Configure a DeltaV node to run DeltaV Virtual Studio or DeltaV Remote Desktop Connection............ 128
3.25.11 DeltaV virtual machine settings.............................................................................................129
3.25.12 Add networks to the virtual DeltaV system manually.............................................................129
3.25.13 Setting up the virtual ProfessionalPLUS workstation type...................................................... 131
3.25.14 Configure DCOM on the DeltaV system for Remote Logoff....................................................133
3.25.15 Enable the DeltaV Screen Saver ............................................................................................ 134
3.25.16 Installing AMS Device Manager on a virtual machine............................................................. 135
3.25.17 Having multiple monitors in a virtual DeltaV system..............................................................135
3.25.18 Configure an additional host domain controller.....................................................................137

Chapter 4 Maintaining an HCI DeltaV Virtual Studio system........................................................141

4.1 Maintenance overview................................................................................................................. 141
4.2 Set the NTP time synchronization................................................................................................. 141
4.3 Replace the witness machine........................................................................................................143
4.4 Replace an HCI switch...................................................................................................................144
4.5 Validate a cluster.......................................................................................................................... 144
4.6 Verify Active Directory and DNS health across the host domain....................................................145
4.7 Replace a server NIC..................................................................................................................... 146
4.8 Update server firmware................................................................................................................ 146
4.9 Install Windows operating system with RAID level verification......................................................147
4.10 Critical functions........................................................................................................................ 148

Chapter 5 Expanding a DeltaV Virtual Studio v4.3 HCI system.....................................................151

5.1 Install a new server....................................................................................................................... 151
5.2 Expanding the storage cluster...................................................................................................... 151
5.2.1 Expand an existing cluster......................................................................................................... 152
5.2.2 Migrate data to an expanded cluster..........................................................................................153
5.2.3 Configure the new Cluster Stored Volume.................................................................................153
5.2.4 Expand a new Cluster Shared Volume virtual disk and partition................................................. 154

v
Contents
August 2022 D800142X012

5.3 Add a new host to the virtualized system......................................................................................155

5.4 Transfer FSMO roles from primary controller to an additional controller....................................... 156
5.5 Join an earlier DVS system to an HCI system................................................................................. 158

Index .................................................................................................................................. 159

vi
 About this documentation
D800142X012 August 2022

1 About this documentation

This manual is designed to help you plan your DeltaV virtual system, set up your hosts, and
install DeltaV Virtual Studio (DVS) v4.3 (used to configure and manage your virtual
machines) on a system built on HCI architecture.
Where necessary, this manual provides limited information about HCI architecture, to help
the user understand how and why to perform actions needed to let the system
communicate properly.
This manual shows tested and supported installation and configuration procedures. If your
system requires a different configuration, contact your Emerson technical support.
The DeltaV Virtualization manuals are available through the Emerson Guardian Support
website at https://guardian.emerson.com/. To find these manuals:
1. Log on the Guardian site and select the Support icon.
2. Select the Document Search option.
3. Click the Browse tab.
4. Set the Product line to DeltaV and Document Type to Product Manuals.
5. Expand DeltaV_Virtualization in the list and select the version you need.
If you do not currently have access to this website, please contact your local Emerson
representative.

Related documentation
The DeltaV Release Notes KBA has important updates for your DeltaV system. Books
Online and the DeltaV application help provide complete DeltaV system documentation.
The Installing Your DeltaV Digital Automation System manual contains complete
information on installing a DeltaV system and the Fieldbus Installations in a DeltaV Digital
Automation System manual contains information about installing a fieldbus system. These
documents are available from your Emerson representative or sales office or you can
access them online in the DeltaV Books Online.

Assumptions
This manual is built on the following assumptions:
• The Windows Server 2022 operating system is installed on all machines used in the HCI
system.
• All procedures described in this document are performed by qualified personnel and
the equipment is used only for the purposes described.
• The people working on the system are familiar with
— HCI architecture
— Fundamentals of virtualization
— Setting up network interface cards (NICs) and workgroups or domains
— Installing the DeltaV software

7
About this documentation
August 2022 D800142X012

CE statement
This manual describes installation and maintenance procedures for products that have
been tested to be in compliance with appropriate CE directives. To maintain compliance,
these products must be installed and maintained according to the procedures described in
this document. Failure to follow the procedures may compromise compliance.

Conventions used in this manual

Note
Notes are used to provide information which is useful in understanding the points being
covered in a topic, but is not absolutely necessary.

Important
Important notes are used to emphasize something which is vital in setting up the system
correctly.

CAUTION
Cautions describe a procedure that must be followed to prevent equipment malfunction.

WARNING
Warnings are used to describe a critical procedure that must be followed to prevent a
safety risk or equipment damage.

Tip
Tips provide pointers on alternate means of doing something, or ways of speeding up a
process.

Terms
Some words used when referring to DVS have particular meanings:

Application This means the user interface that you see when you add, remove, or
manage virtual machines.
Client Another term for the DVS user interface. This term is more often used in
this documentation

Server This is the part of the DVS that runs on the computer which has the DVS
identifier. It can be likened to the DVS backend where the client/UI is the DVS
frontend.

Software "DVS Software" means the entire DeltaV Virtual Studio package, everything
that is installed when you virtualize a DeltaV system.

8
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

2 Planning the DeltaV Virtual Studio

Installation
2.1 HCI network architecture
This section shows how connections between nodes can be made in an HCI system.

DeltaV Online Virtualization of an HCI System With 2 Servers

The following diagram shows connections required between servers and the Witness
device when there are two host servers.

The table below shows a common scheme for dividing node support loads among 2
servers.

Host Server 1 Host Server 2

Cluster DC Cluster DC
Operator Station 1 Operator Station 2
Operator Station 3 Operator Station 4
Operator Station 5 Operator Station 6
Application Station 1 Application Station 2
Operator Station 7 Operator Station 8
Application Station 3 Application Station 4
ProPLUS IDDC
IDDC

9
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

DeltaV Online Virtualization of an HCI system With 4 Servers

This diagram shows that when there are four servers, switches are required between the
host servers.
Note
The diagram shows both N-series and S-series switches. This is a common and
recommended layout, but the types of switches actually used in your system may not
match this.

This table shows a common scheme for dividing node support loads among 4 servers.

Host Server 1 Host Server 2 Host Server 3 Host Server 4

Cluster DC Cluster DC
Operator Station 1 Operator Station 2 Operator Station 3 Operator Station 4
Operator Station 5 Operator Station 6 Operator Station 7 Operator Station 8
ProPLUS Application Station 1 Application Station 2 Operator Station 3
Operator Station 4 IDDC IDDC

Related information
Server cable connection points
Server connection plans
Checklist for installing DVS on an HCI system
Configure the S-Series switch
Configure the N-Series switch
Installing the DeltaV Remote Desktop Connection (DRDC)
Set up the witness machine

10
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

2.1.1 Server cable connection points

This figure shows the points on the backs of Dell PowerEdge R740xd XL servers where
fiber-optic network cables are attached.

Related information
HCI network architecture
Server connection plans

2.1.2 Server connection plans

Means of connecting
The following technologies can be used to network between hosts and switches.

Type Characteristics
DAC - Direct Attach Copper • For distances up to 10m
• Copper cable with SFP ends preinstalled

Multi-mode fiber • For distances up to 100m

• SFP modules for both hosts and switches
• Fiber by others

Single-mode fiber • For distances up to 10km

• SFP modules for both hosts and switches
• Fiber by others

Possible networks
The diagrams below here show the network layouts that can be used. The layouts depend
on the number of hosts in the system.
S-series switches are used for these connections.

Two hosts, with fiber or with DAC:

This layout can be implemented with either fiber-optic cabling or copper cabling.

11
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Two hosts with switches, using both DAC and fiber:

Three hosts with switches, using both DAC and fiber:

12
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

Three hosts with switches, using DAC or fiber:

This network layout can be set up using either copper cabling or fiber-optic cabling.

Four Hosts With Switches in Two Locations, using DAC and Fiber

13
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Related information
HCI network architecture
Server cable connection points
Network port assignments on the Dell PowerEdge R740xd XL

2.1.3 Network port assignments on the Dell PowerEdge

R740xd XL
The figure below shows the port layout that is specific to the PowerEdge 740 series server
configured for the Emerson-designed virtualized DeltaV system.
The network port assignments shown here are only examples. The networks you set up in
your virtual DeltaV system may vary. The basic principle is to distribute the networks
across the ports to minimize potential failures.
Note
In slot 8, ports are numbered left to right. In all other slots, the ports are numbered right to
left.

Server in a production system

14
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

Example NIC assignments in a production system:

Slot Port Assignment

1 StorageAccess network
7 StorageAccess network
2 1 Remote Network Primary
2 2 DeltaV Batch D-Link (System 1)
2 3 DeltaV Primary ACN (System 1)
2 4 DeltaV Primary ACN (System 2)
3 1 Remote Network Secondary
3 2 DeltaV Batch D-Link (System 2)
3 3 DeltaV Secondary ACN (System 1)
3 4 DeltaV Secondary ACN (System 2)
4 1 DeltaV Primary ACN (System 3)
4 2 DeltaV Primary ACN (System 4)
4 3 Thin Client Host Access Primary
4 4 DeltaV Batch D-Link (System 3)
8 1 DeltaV Secondary ACN (System 3)
8 2 DeltaV Secondary ACN (System 4)
8 3 IZN Primary
8 4 DeltaV Batch D-Link (System 4)
1Gb NIC4 Plant LAN
1Gb NIC3 Thin Client Host Access Secondary
10Gb NIC2 IZN Secondary
10Gb NIC1 Acronis License & Management Server for DVS Virtual Machines

Related information
Server connection plans

15
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

2.2 About the DeltaV Virtual Studio client

The DeltaV Virtual Studio (DVS) client is the user interface for managing the virtual DeltaV
machines that reside on one or more hosts in the DeltaV virtualization system.
Note
The client is also sometimes called the application.

Virtual DeltaV workstations are created from templates supplied on the DVS installation
media. For most workstation types, the templates have the DeltaV software already
installed. Some templates are meant for creating workstations that require operating
system configuration or other software installed prior to DeltaV installation, and these
templates have only the operating system installed.
Virtual DeltaV hardware (such as controllers and CIOCs) are also available as templates on
the installation media.
Important
Virtual DeltaV hardware (such as controllers and CIOCs) should reside on hosts that are
dedicated for virtual hardware (that is, no virtual DeltaV workstations) and set to UTC
time. Having virtual hardware on non-dedicated systems may cause brief time
synchronization issues when starting the virtual machine.

From the DeltaV Virtual Studio client, you can administer the virtual environment. These
administrative functions include:
• Add/remove hosts
• Add/modify clusters (when working from the domain controller)
• Configure virtual networks
• Connect to virtual machines
• Compare virtual switches
• Create templates from existing virtual machines
• Create/delete virtual machines
• Display/edit virtual networks
• Edit host health settings
• Edit the virtual machine's hard disk (VHD) size
• Import/export virtual machines
• Modify virtual machine settings
• Move virtual machines
• Organize virtual machines by server (host)/by user-defined groups
• Start/stop virtual machines
• Upgrade virtual machines
• Upgrade domain controllers to Independent DeltaV Domain Controllers
You can also check the status of the virtual machines residing on any host to which the
DeltaV Virtual Studio client connects.

16
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

Related information
DeltaV virtual machine settings

2.3 Supported operating systems for DeltaV

Virtual Studio
Host servers
The DeltaV Virtual Studio application and the DeltaV system identifier are supported on
the following operating systems:
• Windows 10 Professional (64-bit)
• Windows 10 Enterprise (64-bit)
• Windows Server 2022 Standard (64-bit)
• Windows Server 2022 Datacenter (64-bit)

Installing on host servers

The following rules apply (in addition to the supported operating systems) when installing
DeltaV Virtual Studio on a computer:
• When DeltaV Virtual Studio is installed on the DeltaV network, it must be able to
communicate with the host computer(s). Your network and security constraints must
allow this communication.
• DeltaV Virtual Studio can be installed on a DeltaV computer, provided the operating
system and .NET Framework version are supported for both the DeltaV software and
DeltaV Virtual Studio.

Switches
N-Series switches run a Dell proprietary operating system. For use in a virtualized HCI
system, that operating system must be version 6.7 or later. If it is necessary to update the
OS on a switch, refer to the topic Upgrade the N-series switch OS.
S-Series switch use a Dell proprietary operating system, version 10.5.0.

Related information
Licenses for operating systems
Configure the N-Series switch
Upgrade the N-series switch OS
Configure the S-Series switch

2.4 Licenses for operating systems

There are two operating systems that require licensing: the OS on the physical computer
(host or thin client), and the OS on the virtual machine.

17
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Host computers
The Windows operating system on the host computer is licensed as part of the purchase of
that computer. This is a Microsoft license and is activated and valid for the life of the
physical machine.
If upgrading the host operating system, you must purchase the new operating system and
the license for that operating system.

Virtual machines
Licensing the Windows operating system for virtual machines is accomplished by the
following:
• VDA (Virtual Desktop Access) subscriptions - This is the method used for virtual
machines running the Windows workstation operating system. There must be one VDA
subscription for each device used to connect to client OS virtual machines. VDA
subscriptions have an expiration, but an expired VDA will not impact any running
virtual machines.
Note
It is the responsibility of the customer to keep the subscriptions up to date in order to
be in legal compliance with Microsoft.

• Embedded licenses - This method is used to license virtual machines running Windows
Server operating systems. The embedded license is distributed as a physical COA
(Certificate of Authenticity). A COA is required for each virtual machine server
template. The COA must be placed on each physical host where the virtual machine
resides. The COA for the embedded Windows Server operating systems never expires.
• QNX - There is no customer license required for the virtual machine running the QNX
operating system (used by the DeltaV virtual controller, virtual EIOC, virtual LSNB,
virtual CSLS, and virtual CIOC machines).

Thin client computers

The operating system on the thin client computer is licensed as part of the purchase of
that computer. This is a Microsoft license and is activated and valid for the life of the
physical machine.

Related information
Supported operating systems for DeltaV Virtual Studio
Checklist for installing DVS on an HCI system

2.5 DeltaV virtualization templates

The tables below list the DeltaV version, node types, and operating systems that are
supplied as DeltaV templates for virtualization.
Note
If the computer you are using requires additional operating system configuration or
software installation prior to using a DeltaV template, you must use a template that has
ONLY the operating system correct for that version of DeltaV. For example, the following
require starting with a template that includes the operating system only:
• The ProfessionalPLUS (DeltaV v13.3.1)

18
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

• The ProfessionalPLUS as a domain controller (DeltaV v14.3 or later)

• The ProfessionalPLUS as a Remote Client Server
• DeltaV Simulate Standalone workstations
• Any computer that requires MS Office (Word or Excel)
Note
This does not apply if MS Office 2016 or later is used.

• AMS Server Plus workstations (virtual DeltaV workstations with AMS Client are created
by using the DeltaV templates and selecting the AMS Settings during virtual machine
creation.)
• An Application Station as a domain controller
• An Independent DeltaV Domain Controller
• A non-DeltaV node
• A host domain controller
The ProfessionalPLUS may be installed from a template that has DeltaV pre-installed, as
long as the ProfessionalPLUS is version 14.3 or later and will NOT be a domain controller or
a Remote Client Server.

Note
Once the operating system configuration is complete, you can install the DeltaV software
on the virtual machine in the same manner as if it is a physical computer.

All DeltaV templates contain the DeltaV version as distributed on the physical DVDs. No
additional DeltaV or operating system hotfixes or service packs have been added to the
templates. To check for any updates, please contact your local business partner, Emerson
SureService, or check the Guardian support web site. Updates of operating systems and
DeltaV (patch management) on virtual machines is handled the same as on physical
machines.
Table 2-1: Templates with DeltaV Software Installed
DeltaV version DeltaV workstation type Template name Virtual machine operating
derived from this template system
v14.3.1 ProfessionalPLUS Station 1431SV16 Windows Server 2016 (64-
Local Operator bit)
Operator Station as Remote
Client Server
Local Professional-Base-
Maintenance
Local Application Station
Remote Professional-
Operator-Base
Remote Application Station
Inter-Zone Server
v14.3.1 with Advanced Local Application Station 1431SV16A Windows Server 2016 (64-
Continuous Historian bit)

19
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Table 2-1: Templates with DeltaV Software Installed (continued)

DeltaV version DeltaV workstation type Template name Virtual machine operating
derived from this template system
v14.3.1 ProfessionalPLUS Station 143110ENT Windows 10 Enterprise (64-
Local Operator bit)
Local Professional-Base-
Maintenance
Local Application Station
Remote Professional-
Operator-Base
Remote Application Station
v14.3.1 FP1 ProfessionalPLUS Station 1431FP1SV16 Windows Server 2016 (64-
Local Operator bit)
Operator Station as Remote
Client Server
Local Professional-Base-
Maintenance
Local Application Station
Remote Professional-
Operator-Base
Remote Application Station
Inter-Zone Server
v14.3.1 FP1 with Advanced Local Application Station 1431FP1SV16A Windows Server 2016 (64-
Continuous Historian bit)
v14.3.1 FP1 ProfessionalPLUS Station 1431FP110ENT Windows 10 Enterprise (64-
Local Operator bit)
Local Professional-Base-
Maintenance
Local Application Station
Remote Professional-
Operator-Base
Remote Application Station
v14.FP2 ProfessionalPLUS Station 14FP2SV16 Windows Server 2016 (64-
Local Operator bit)
Operator Station as Remote
Client-Server
Local Professional-Base-
Maintenance
Local Application Station
Remote Professional-
Operator-Base
Remote Application Station
Inter-Zone Server
v14.FP2 with Advanced Local Application Station 14FP2SV16A Windows Server 2016 (64-
Continuous Historian bit)

20
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

Table 2-1: Templates with DeltaV Software Installed (continued)

DeltaV version DeltaV workstation type Template name Virtual machine operating
derived from this template system
v14.FP2 ProfessionalPLUS Station 14FP210ENT Windows10 Enterprise (64-
Local Operator bit)
Local Professional-Base-
Maintenance
Local Application Station
Remote Professional-
Operator-Base
Remote Application Station

Table 2-2: Templates With Operating System Only

DeltaV version Template name Virtual machine operating system
v13.3.1 SV08R2SP1 Windows Server 2008 R2 SP1 Standard
(Embedded)
v13.3.1 10ENT Windows 10 Enterprise (64-bit)
v14.3.1 SV16 Windows Server 2016 (64-bit)
v14.3.1 FP1 Can also be used as a virtual backup
v14.FP2 domain controller for the host
network - without DeltaV installed.
Not Applicable SV12R2 Windows Server 2012 R2 (64-bit)
To be used as a Syncade computer -
without DeltaV installed.

The templates have the following defaults for RAM, virtual processors, and hard drive
maximum size. These values can be modified during creation or later, using the Modify
VM dialog.
Table 2-3: Defaults for RAM, Processors, and Drive size
Type DeltaV RAM (MB) CPU (virtual C: drive (GB) D: drive (GB) VM Units
Version processors) (VMUs)
Server 13.3.1 8192 4 80 40 2
Workstation 13.3.1 4096 4 40 40 1
Server 14.3.1 /14.3.1 16384 4 80 40 2
FP1/v14.FP2
Workstation 14.3.1/14.3.1 8192 4 80 40 1
FP1/v14.FP2

Important
Virtual DeltaV hardware (such as controllers and CIOCs) should reside on hosts that are
dedicated for virtual hardware (that is, no virtual DeltaV workstations) and set to UTC
time. Having virtual hardware on non-dedicated systems may cause brief time
synchronization issues when starting the virtual machine.

21
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Table 2-4: DeltaV Controller Templates

Virtual machine type DeltaV version Template name
DeltaV SX controller v13.3.1 1331VSCTLR
DeltaV MX controller v13.3.1 1331VMCTLR
DeltaV SZ controller v13.3.1 1331VSZCTLR
DeltaV MX controller v14.3.1 1431VMCTLR
DeltaV PK controller v14.3.1 1431VPK1500CTLR
DeltaV SX controller v14.3.1 1431VSCTLR
DeltaV SZ controller v14.3.1 1431VSZCTLR
DeltaV MX controller v14.3.1 FP1 1431FP1VMCTLR
DeltaV PK controller v14.3.1 FP1 1431FP1VPK1500CTLR
DeltaV SX controller v14.3.1 FP1 1431FP1VSCTLR
DeltaV SZ controller v14.3.1 FP1 1431FP1VSZCTLR
DeltaV MX controller v14.FP2 14FP2VMCTLR
DeltaV PK controller v14.FP2 14FP2VPK1500CTLR
DeltaV SX controller v14.FP2 14FP2VSCTLR
DeltaV SZ controller v14.FP2 14FP2VSZCTLR

Table 2-5: DeltaV CHARMs I/O (CIOC) Templates

Virtual machine type DeltaV version Template name
DeltaV CHARMs I/O card (CIOC) v13.3.1 1331VCIOC
DeltaV CHARMS I/O card (CIOC) v14.3.1 1431VCIOC
DeltaV CHARMS I/O card 2 (CIOC2) v14.3.1 1431VCIOC2
DeltaV CHARMS I/O card (CIOC) v14.3.1 FP1 1431FP1VCIOC
DeltaV CHARMS I/O card 2 (CIOC2) v14.3.1 FP1 1431FP1VCIOC2
DeltaV CHARMS I/O card (CIOC) v14.FP2 14FP2VCIOC
DeltaV CHARMS I/O card 2 (CIOC2) v14.FP2 14FP2VCIOC2

Table 2-6: DeltaV CSLS and LSNB Templates

Virtual machine type DeltaV version Template name
DeltaV CHARMs Smart Logic Solver v13.3.1 1331VCSLS
controller (CSLS)
DeltaV Local Safety Network Bridge v13.3.1 1331VLSNB
(LSNB)
DeltaV CHARMS Smart Logic Solver v14.3.1 1431VCSLS
controller (CSLS)
DeltaV CHARMS Smart Logic Solver v14.3.1 1431VCSLS1
controller 2 (CSLS2)

22
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

Table 2-6: DeltaV CSLS and LSNB Templates (continued)

Virtual machine type DeltaV version Template name
DeltaV Local Safety Network Bridge v14.3.1 1431VLSNB
(LSNB)
DeltaV CHARMS Smart Logic Solver v14.3.1 FP1 1431FP1VCSLS
controller (CSLS)
DeltaV CHARMS Smart Logic Solver v14.3.1 FP1 1431FP1VCSLS1
controller 2 (CSLS2)
DeltaV Local Safety Network Bridge v14.3.1 FP1 1431FP1VLSNB
(LSNB)
DeltaV CHARMS Smart Logic Solver v14.FP2 14FP2VCSLS
controller (CSLS)
DeltaV CHARMS Smart Logic Solver v14.FP2 14FP2VCSLS1
controller 2 (CSLS2)
DeltaV Local Safety Network Bridge v14.FP2 14FP2VLSNB
(LSNB)

Table 2-7: DeltaV EIOC Templates

Virtual machine type DeltaV version Template name
DeltaV Ethernet I/O card (EIOC) v13.3.1 1331VEIOC
DeltaV Ethernet I/O card (EIOC) v14.3.1 1431VEIOC
DeltaV Ethernet I/O card (EIOC) v14.3.1 FP1 1431FP1VEIOC
DeltaV Ethernet I/O card (EIOC) v14.FP2 14FP2VEIOC

2.6 Reserved DeltaV IP addresses

The DeltaV system automatically assigns IP addresses to the workstations and controllers.
If Network Time Protocol (NTP) servers are used, they must be assigned specific IP
addresses. Reserved IP addresses can be used for other equipment such as switches,
domain controllers, management stations, and so on.

IP addresses for Network Time Protocol servers

If the NTP server is a DeltaV workstation, it is automatically assigned an IP address. If you
use an external NTP server, you must assign it the following IP addresses:
• Primary NTP server on the primary network: 10.4.128.1
• Backup NTP server on the primary network:10.4.128.2
• Primary NTP server on the secondary network:10.8.128.1
• Backup NTP server on the secondary network:10.8.128.2

IP addresses reserved for other equipment

Reserved primary IP addresses Reserved secondary IP addresses

10.4.128.41 10.8.128.41

23
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Reserved primary IP addresses Reserved secondary IP addresses

10.4.128.42 10.8.128.42
10.4.128.43 10.8.128.43
10.4.128.44 10.8.128.44
10.4.128.45 10.8.128.45
10.4.128.46 10.8.128.46
10.4.128.47 10.8.128.47
10.4.192.xxx No corresponding secondary IP address
(where "xxx" is a random number between 1 and 254)
This is used for virtual machines on a domain initially,
but set to standard DeltaV addresses during
Workstation Configuration.
10.5.128.16 10.9.128.16
10.5.128.17 10.9.128.17
10.5.128.18 10.9.128.18
10.5.128.19 10.9.128.19
10.5.128.20 10.9.128.20
10.5.128.21 10.9.128.21
10.5.128.22 10.9.128.22
10.5.128.23 10.9.128.23
10.5.128.24 10.9.128.24
10.5.128.25 10.9.128.25
10.5.128.26 10.9.128.26
10.5.128.27 10.9.128.27
10.5.128.28 10.9.128.28
10.5.128.29 10.9.128.29
10.5.128.30 10.9.128.30
10.5.128.31 10.9.128.31
10.5.128.32 10.9.128.32
10.5.128.33 10.9.128.33
10.5.128.34 10.9.128.34
10.5.128.35 10.9.128.35
10.5.128.36 10.9.128.36
10.5.128.37 10.9.128.37
10.5.128.38 10.9.128.38
10.5.128.39 10.9.128.39
10.5.128.40 10.9.128.40

24
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

Reserved primary IP addresses Reserved secondary IP addresses

10.5.128.41 10.9.128.41
10.5.128.42 10.9.128.42
10.5.128.43 10.9.128.43
10.5.128.44 10.9.128.44
10.5.128.45 10.9.128.45
10.5.128.46 10.9.128.46
10.5.128.47 10.9.128.47

2.7 Virtual system resource planning guidelines

Virtual machines require host computer resources and are typically limited by host CPU or
RAM availability.
The tables below provide guidelines on how many virtual machines to assign to host
computers based on the VM loading and RAM requirements. Virtual Machine Units (VMUs)
are used to estimate relative CPU loading and host limits. VMUs are a simplified sizing
method and are not intended to be used interchangeably with CPUs or Virtual Processors.
For the most current list of supported host hardware and resource planning guidelines,
refer to the DeltaV Virtualization Hardware product data sheet.
Table 2-8: Host VM Resource Planning
Virtual machine class VMUs RAM (MB)
Workstation operating system (Windows 10)
DeltaV v14.3.1 and later 1 8192
DeltaV v13.3.1 and earlier 1 4096
Windows Server 2022 operating system
DeltaV v14.3.1 and later 1 8192
Windows Server 2016 operating system1
DeltaV v14.3.1 and later 2 16384
DeltaV v13.3.1 and earlier 2 8192
Virtual Hardware
Virtual Controller (PK) 0.8 1024
Virtual Controller (S, M, SZ) 0.4 256
Virtual CHARMs I/O card (CIOC) 0.2 64
Virtual CSLS and LSNB 0.5 64
Virtual Ethernet I/O card (EIOC) 0.8 256

1 Server 2016 is used in systems that run DVS v3.3.4 and earlier. DVS 4.3 runs on Windows Server
2022, but it provides backwards compatibility with Server 2016.

25
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Table 2-9: Supported Limits for Hosts

Virtual machine class VMUs
On-line, production host 24
(Normal operation)
On-line, production host 48
(Temporary failover operation)
Off-line, non-production host 22
(for example, training systems, development
test systems)

Important
Virtual DeltaV hardware (such as controllers and CIOCs) should reside on hosts that are
dedicated for virtual hardware (that is, no virtual DeltaV workstations) and set to UTC
time. Having virtual hardware on non-dedicated systems may cause brief time
synchronization issues when starting the virtual machine.

Operator Training System

An operator training system with these virtual machines
• 1 server class ProfessionalPLUS (2 VMUs)
• 2 server class Application Stations (4 VMUs)
• 6 Operator Stations ( 6 VMUs)
would require 12 VMUs, and could all be run in one off-line host computer.

Development Test System

A development/test system with these virtual machines
• 1 server class ProfessionalPLUS (2 VMUs)
• 2 server class Application Stations (4 VMUs)
• 4 Professional Stations (4 VMUs)
• 2 Operator Stations (2 VMUs)
• 10 S-series Virtual Controllers (4 VMUs)
• 30 Virtual CHARMS IO Cards (6 VMUs)
would require 22 VMUs and at least one off-line host computer.

On-line Production System

An on-line production system with these virtual machines
• 1 server class ProfessionalPLUS (2 VMUs)
• 5 server class Application Stations (10 VMUs)
• 10 Operator Stations (10 VMUs)
would require 22 VMUs and at least one on-line host computer.

26
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

2.8 Recommended system capacities for the Dell

PowerEdge R740xd server
Item Recommended Capacity
Number of clusters in a single host domain 4 clusters
Number of host domain controllers 2 domain controllers required
Number of DeltaV systems in one cluster 1 recommended for production; up to 4 for
simulation or training systems
Number of DeltaV nodes on one system Refer to the Virtual system resource planning
guidelines to calculate the number of VMUs
your system can support.
Number of domains 1 domain per DeltaV Virtual Studio service
manager (where the license files and system
identifier are)
Number of thin clients in one thin client network 96 thin clients

2.9 User accounts for the virtualized DeltaV system

The following tables list the user accounts involved in making the virtual DeltaV system
function, from installation to operation of the system.
Note
Systems built on HCI architecture use only domains.

Type of system Accounts and passwords

Domain system (all computers in the same Accounts are domain accounts, unless
domain) otherwise specified.
Multiple-domain system (hosts are in one A trust must exist between the domains, so that
domain, clients are in another) domain user account authentication and
validation can occur.
Mixed system (hosts are in a domain, clients are Accounts must be both local accounts on all
in a workgroup) machines, and domain accounts on the domain.

• In a domain system (where all computers are in the same domain), the accounts are
domain accounts, unless otherwise specified.
• In a multiple domain system (where hosts are in one domain and clients are in
another), a trust must exist between the domains so that domain user account
authentication and validation can occur.
• In a system where the hosts are in a domain and the clients are in a workgroup, the
accounts must be both local accounts on all machines, and domain accounts on the
domain.
Thick clients using the Connect to console option must be members of the host domain.

27
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

User Account privileges Needed on Used for Notes

Account needed
VirtualAdmin Group Managed Host Communication This account is
Service Account DeltaV between hosts and created by running
(GMSA) Virtual Studio communication the Create a Domain
computers between the DeltaV Account utility on
Virtual Studio the host domain
computers and the controller and
hosts adding the hosts and
DeltaV Virtual Studio
computers to the
group.
DeltaV Local administrator Host The service is used This must be kept as
Virtual Studio group DeltaV for managing the the VirtualAdmin
Service 'Log Virtual Studio hosts by the DeltaV GMSA account.
on as' computers Virtual Studio
account computers.
Logged On Local administrator Current Running Host Setup
user group computer Running the DeltaV
Note Virtual Virtual Studio and
This level of access is machine the DeltaV Remote
only required if the (when Client Connection
logged-on user will connecting client application
be installing the to the virtual Installing DeltaV
system or running machine in Virtual Studio and
the DeltaV Virtual Connect to DeltaV Remote
Studio application. console Client Connection
mode)
DRDC Host's (or host Host Connecting to the
Logged On domain's) computer virtual machine using
user ConnectToConsole Connect to console
user group mode
DeltaV Local administrator DeltaV Running the DeltaV
Virtual Studio group Virtual Studio Virtual Studio
user account computers application
Note Virtual Managing the hosts
This is the machine and virtual machines
account (when using DeltaV Virtual
provided connecting Studio
when to the virtual Connecting to the
starting the machine in virtual machine
DeltaV Connect to through DeltaV
Virtual Studio console Virtual Studio
application. mode) (Connect to console
mode)
DeltaV user DeltaV access level Current Connecting to the
account determines computer virtual DeltaV
privileges needed on DeltaV virtual machine (in the non-
the DeltaV system. machine Connect to console
mode)

28
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

User Account privileges Needed on Used for Notes

Account needed
Administrato Local administrator DeltaV virtual Installing DeltaV (or
r-level group machine other software) and
account that Domain managing the
is not the administrator group operating system of
built-in the virtual machine
Account name and
Administrato
password are
r or the
supplied by user
default
when creating the
Emerson
virtual machine
account.

Related information
Create a domain-level account for DVS

2.10 DeltaV Smart Switch ports and virtual

machines
The DeltaV Smart Switch detects the ports being used and which MAC address is using
each port. When a port is locked, the DeltaV Smart Switch prevents other MAC addresses
from using that port.
A DeltaV Smart Switch port locks when either of the following is true:
• One (1) or two (2) known Emerson MAC addresses are detected on the port.
• One (1) non-Emerson MAC address is detected on the port. (This means if there is more
than one (1) non-Emerson MAC address, the port remains unlocked.)
In a virtual DeltaV system, the physical network card on the host computer carries the
network communications for multiple virtual machines running on that host; each virtual
machine has a unique MAC address.
For hosts, the DeltaV Smart Switch port connected to the host remains unlocked if there is
more than one (1) virtual machine running on the host at the time of locking the switch.
This accommodates the multiple MAC addresses of the running virtual machines using the
host's physical network card.
Note
When configuring the first and second virtual machines on the host, it is necessary to
unlock the entire switch. If more than one virtual machine is configured and running, you
can lock the switch with the understanding that the port with multiple MAC addresses on
it will remain open. Refer to the DeltaV Smart Switch documentation for information on
configuring the switch.

If you lock the switch before you have multiple virtual machines running on the host, the
virtual machines will not be able to communicate through the locked switch after they are
started.

29
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Tip
Always make sure you have at least two (2) virtual machines running on the host
connected to a DeltaV Smart Switch for each of the networks (DeltaV Primary, DeltaV
Secondary, DLINK, and so on) before locking the switch.

2.11 System time in a DeltaV virtual system

The following outlines the rules and concerns for keeping a virtual DeltaV system in time
sync. This is important because history collection, domain communications, and DeltaV
control execution depend on time synchronization.

Rules for synchronizing time in any DeltaV system (physical or virtual)

• SOE (Sequence of Events)/Precise time must use a time device external to the DeltaV
system. Refer to DeltaV Books Online for the network device supported.
• DeltaV time must always be derived from a physical device (even for non-SOE/non-
Precise time).

How a virtual system obtains its time

• Virtual machines obtain their initial clock time from the host when the virtual machine
starts, then drift from (become out of sync with) the host. The longer the virtual
machine runs, the greater the drift.
• All hosts where the virtual machines are part of the same DeltaV system must stay in
time synch with each other because the hosts set the initial time on the virtual
machine. Otherwise, when the DeltaV virtual machine is restarted, you have the
potential for a time mismatch.

Specific to virtual DeltaV system

• For security reasons, we do not recommend connecting the hosts to the DeltaV ACN.
• The virtual controller and virtual CIOC use UTC time only. The QNX operating system
used by the virtual controller and virtual CIOC do not pay attention to time zones.
Important
Timestamps from the QNX-based controller and CIOC virtual machines do not initially
report events with the correct local time (whenever the virtual machine is started,
restarted, or rebooted). However, after several minutes, the virtual controllers and
virtual CIOCs are synchronized with the DeltaV system time. This time disparity is due
to the QNX software recognizing time as UTC time. Note that this is not an issue if the
hosts and DeltaV system are also set to UTC.

Domains and time

Domain controllers normally act as time sources for the domain they are controlling.

30
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

Examples of how to connect physical time servers with a virtual DeltaV system

Figure 2-1: External Time Server for Sequence of Events (SOE) and Precise Time Applications

31
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Figure 2-2: Hosts as Time Server (Non-SOE and Non-precise Time Applications)

Host Domain Controller

as Master Time Server

Non-ACN network

Host network

Host 1 Host 2 Host 3

DeltaV
Del
Master
Mas Del
DeltaV Del
DeltaV
Time
Tim Nod
Node Nod
Node
Node
Nod

DeltaV
Del Del
DeltaV Del
DeltaV
Node
Nod Node
Nod Node
Nod

DeltaV ACN

Time synchronization for virtual embedded nodes

Virtual nodes require time to synchronize with the master time source after a download.
The following table lists the average time required for each type of virtual node.
Table 2-10: Time Required for Virtual Nodes to Synchronize with Master Time Source
After a Download
Embedded Node Average Time to Synchronize (seconds)
Virtual CHARMs I/O Card (CIOC) 160
Virtual CHARMs I/O Card 2 (CIOC2) 159.83
Virtual Ethernet I/O Card (EIOC) 156.36
Virtual M-Series Controller 160.67
Virtual PK Controller 155

32
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

Table 2-10: Time Required for Virtual Nodes to Synchronize with Master Time Source
After a Download (continued)
Embedded Node Average Time to Synchronize (seconds)
Virtual S-Series Controller 155.83
Virtual SZ Controller 150.83

Related information
Synchronize DeltaV system time with an external node

2.12 Synchronize DeltaV system time with an

external node
This task explains how to synchronize the time on your virtual DeltaV System with an
external time source, for example, a host computer or a plant-wide network.
Requirements:
• The workstation that is to synchronize with the time server must have network access
to that server. For example, if the time server is only accessible via the plant LAN, the
workstation must have a plant LAN connection.
• The time source must adhere to Network Time Protocol (NTP).
1. From DeltaV Explorer, select Remote Network under the ProfessionalPLUS
workstation or Application Station.
2. From the context menu, select Properties.
The Remote Network Properties dialog appears.

Note
It is not necessary to select Enable Remote Network for time synchronization to
work.

3. Select the Advanced tab on the Remote Network Properties dialog.

4. Enter the IP address of the plant-wide master into the Master Time Server field.
5. If your network has a backup time server, enter its IP address in the Backup Time
Server field.
6. Open the properties dialog for the Physical network.
7. On the System Time tab Master Time Server field, browse to the DeltaV node
configured to communicate with the plant-wide Master Time Server.
This is the ProfessionalPLUS or Application workstation whose Remote Network you
selected in step 1.
8. If you are using a backup time server, browse to it in the Backup Time Server field.
9. Download the changed setup data on the ProfessionalPLUS workstation or the
Application station.

33
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

Related information
System time in a DeltaV virtual system

2.13 Downloads to obtain before starting

To configure a PowerEdge 740xd XL, you should have the Dell Power Edge 740xd
documentation. This documentation is available at http://www.dell.com/support/
manuals. Refer to this documentation when questions arise about the physical device
(how to insert the drives, for a port diagram, what iDRAC ports to connect to, and so on).

Necessary software
You must have the following before you begin installing DeltaV Virtual Studio:
• Updates for Dell servers
• Microsoft updates

Related information
Download updates for Dell servers
Download Microsoft updates
Checklist for installing DVS on an HCI system

2.13.1 Download updates for Dell servers

1. Locate the latest copy of the DeltaV Virtualization Hardware Driver and Firmware
Updates for DeltaV Virtual Studio v4.3.x KBA. This document will list the latest tested
versions of all firmware and drivers for each model of Dell servers.
2. In the KBA, find the model of server you will update and take note of all the
firmware and drivers.
3. Open a browser and go to the Dell support web site (dell.com/support).
4. In the search window, enter the model of the Dell server you need to update. The
window will use Autofill to show a list of possible matches.
5. Select your model from the list.
6. In the results, click Drivers & Downloads.
7. For every driver or firmware package for that model of server, do the following:
a) Enter search criteria in the Keyword window and click the Search icon.
b) Scroll down to the results.
c) Find the software version that matches the version listed in the KBA, and
click Download. If you do not see the correct version in the results, go to step
8; otherwise, go to step 9.
d) Use the screen controls to save the software.

8. Perform this step only if necessary:

a) Click Older versions.
b) Find the version listed in the KBA, and download it.

34
 Planning the DeltaV Virtual Studio Installation
D800142X012 August 2022

c) If you cannot find the correct version, check the rest of the search results to
see if it is listed elsewhere.
d) If you cannot find the listed version anywhere, download and use the latest
version available, whatever it is.

9. Repeat step 7 (and step 8, if needed) until you have downloaded all the software
listed in the KBA for that model of server.
10. Copy all the downloaded files to removable media so you can later copy them to the
server.

Related information
Downloads to obtain before starting

2.13.2 Download Microsoft updates

1. Find the latest version of KBA AK-1200-0033 on Guardian or SMS.
2. Look for a link in the KBA for HyperV2016Host_ALL_X.zip, where X is the month
and year of the update’s release.
3. Download the ZIP file and save it locally.
4. Extract the contents of the ZIP file and save them to a DVD or USB drive. This
includes the updates for both hosts and domain controllers.
Note
The downloaded software will be installed during configuration of the host domain
controller. (Configure a physical host domain controller)

Related information
Downloads to obtain before starting

35
Planning the DeltaV Virtual Studio Installation
August 2022 D800142X012

36
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

3 Installing DeltaV Virtual Studio on an

HCI system
3.1 Checklist for installing DVS on an HCI system
This topic provides a broad outline of the action sequence to follow in order to install
DeltaV Virtual Studio (DVS) on a virtualization system built on the HCI architecture.
Details on how to perform the actions in each phase are found in other sections of this
installation guide, which are linked to from this topic.
The procedures for adding further hosts to the DVS application (the user interface, also
called the client), and for creating and configuring virtual machines, are not covered in this
document. This covers only the process of making DVS run on a computer network. For
information on using the DVS application, refer to the DVS online help,
HCIEmersonVirtualMachineManager.chm.
Multiple reboots are required to complete the installation.
Important
Complete all the configuration tasks described here.

1. Make sure you have downloaded the latest firmware and drivers - refer to the
document section Downloads to obtain before starting.
2. Make sure the server(s) are set up properly - refer to the topic Set up a Windows
Server host computer.
3. Configure RDMA on each host server - refer to the topic Configure RDMA.
4. Make sure the system nodes are connected properly. Check cable runs against
diagrams in the document section HCI network architecture.
5. Initialize the host on each server - refer to the topic Initialize a host.
6. If the system uses S-series HCI switches, configure them - refer to the topic
Configure the S-Series switch
7. If necessary, enable or disable additional ports on the S-series switches. Refer to the
topic Enable or disable S-Series switch ports.
8. If the system uses N-series HCI switches, configure them - refer to the topic
Configure the N-Series switch.
9. Configure a a primary domain controller. This can be either a physical or a virtual
domain controller. For more information, refer to the topics in the document
section Setting up domain controllers.
10. Join each host to the domain - refer to the topic Join a host to a domain.
11. Set up an additional domain controller - refer to the topic Configure an additional
host domain controller as a VM.

37
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
This uses the same Autorun function as phase 8, but you will specify a different
domain controller in this phase.

12. Harden the domain - refer to the topic Harden domain controllers.
13. Create a domain account for use by hosts - refer to the topic Create a domain-level
account for DVS
14. Install the DVS service on either a host or a VM. Refer to the topic Install DeltaV
Virtual Studio.
15. Install the DVS client on each domain controller - refer to the topic Install DeltaV
Virtual Studio.
Note
This uses the same Autorun function as phase 14, but is performed locally on
different machines.

16. Install the DVS license - refer to the topic Copy the DVS license to the DeltaV Virtual
Studio computer.
17. Install the DVS virtualization system identifier. The machine used can be either a
host or a VM.
• Install the DeltaV Virtualization system identifier
• Install the DeltaV Virtualization system identifier on a VM

18. Configure hosts for live storage migration - refer to the topic Configure hosts for live
storage migration.
19. Start the application - refer to the topic Start the DeltaV Virtual Studio client.
20. Run host setup from one of the domain controllers - refer to the topic Set up the
hosts.
21. Copy the release-specific files from the installation media to the host - refer to the
topic Copy release-specific files to the host.
22. Run host network setup from one of the domain controllers - refer to the topic Set
up host networks.
23. Set up the witness machine - refer to the topic Set up the witness machine.
24. Set up a cluster - refer to the topic Set up a cluster.
25. Set up virtual networks - refer to the topic Set up virtual networks.
26. Install DRDC on the thick or thin clients - refer to the topic Installing the DeltaV
Remote Desktop Connection (DRDC).

Related information
Downloads to obtain before starting
Licenses for operating systems
HCI network architecture

38
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

3.2 The Autorun.Hci interface

The Autorun UI is used to install DeltaV Virtual Studio and to configure a system which
supports virtualizing your DeltaV system. It is opened by activating the
Autorun.Hci.exe file.
The list of tabs down the left side of the UI show the actions that can be performed.

Note
When the Autorun UI opens, it does not show all the tabs. You must scroll down to see the
last tab. The scroll bar appears when you place the mouse pointer above the tab list.

The figure below shows how subtabs appear in the Autorun UI when you are performing
an action. Each tab has a list of subtabs that are unique to that tab. A white-and-green
check mark appears when the actions in that subtab are completed.

39
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

The information and controls that are shown in the right-side pane of the interface depend
on which subtab is current. You can click on a subtab to change the information in the
right-side pane.
You can go back in the action sequence when you need to change something done earlier.
For example, when the Initialize Host tab is showing, and you have completed the host
access network setup, you could click the StorageAccess Network Setup subtab, and
return to that. Then you could repeat the actions from that point forward.

The table below shows the uses, prerequisites for, and results of using, the tabs on the
Autorun interface.

Main Tab Where To Run Preconditions for When To Run Actions Subtabs That
the Action Running This Automatically Show When the
Named in the Tab Action Carried Out tab is Selected
Initialize Host Each Host • Running as • New host • Enables • Windows
Administrator Windows Feature Setup
features
• Operating • Network
(hardening
System Setup
requires a
Supported
reboot) • Host Access
• Running on Network
• Creates switch
HCI host Setup
embedded
server
team (SET) • Review
• Enough free
• Sets up virtual
disk space
switches and
• Enough RAM IP addresses

Configure HCI S- Any host machine • Running as • New HCI S- • Configures • Connection
Series Switch connected to Administrator series switch HCI switch Status
switch with a ports
• Host is • Username/
serial port
initialized • Configures Password
VLANs
• IP address
• Configures setting
users
• Import
• Configures Configuration
security
settings
• Shuts down all
uplink ports

Configure HCI N- Any host machine • Running as • New HCI N- • Configure • Connection
Series Switch connected to Administrator series switch VLANs Status
switch with a
• Host is • Configure • Configure
serial port
initialized Security Ports
Settings
• Thin Client
• Shuts down all
• HCI Host
uplink ports
• Cluster
Management

40
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Configure DVS Host where DC • Running as • DVS domain • Creates DC • Domain

Domain VM will run Administrator controller VM Controller
Controller VM needed Type
• Operation • If PDC, then
System creates • Domain
Supported domain Controller
Name
• Hyper-V • On a domain
Service is controller, • Domain Name
Enabled automatically
• StorageAccess
runs:
• StorageAccess Network
— Apply
Virtual Switch
Domain • Host Access
Created
Hardening Network
— Create • Template
Domain
• Review
Account
for DVS
Services
— Install
DeltaV
Virtual
Studio
— Set Up
Host

Join Domain Each host and file • Running as • New host • Joins machine • Join Domain
share witness Administrator to domain Info
• Machine is
part of a
Workgroup

Apply Domain Each domain • Running as • First time HCI • Applies • Apply Domain
Hardening controller Administrator installed or hardened Hardening
DVS version default
• Operating
changes domain policy
system is
(includes host
supported
hardening)
• Running on a
• Local domain
domain
controller
controller
registry edits
• User is a
member of
domain
admins
• User is not
built-in
administrator

41
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Create Domain One of the • Running as • After adding a • Creates DVS • Select
Account for DVS domain Administrator new host domain Machines
Services controllers account (if not
• Operating
there)
system is
supported • Authorizes
hosts to use it
• Running on a
domain
controller
• User is a
member of
domain
admins

Install DeltaV A host or each • DeltaV Virtual • First time HCI • Installs DVS • NTP Settings
Virtual Studio domain controller Studio is is installed client and
• Review
and other installed (not a service
• DVS version
management precondition)
changes • Sets up NTP
machines
• Running as (Network
• Additional
Administrator Time Protocol)
DVS client
• Operating needed
system is
supported

Set Up Hosts One of the • Running as • First time HCI • Installs host • Password
domain Administrator is installed or agent Entry
controllers DVS version
• Running on a • Sets up NTP • (One tab for
(SAN, VRTX, HCI) changes
domain each host)
• Authorizes
controller
hosts to use
• Operating gMSA
system is
supported

Set Up Host One of the • Running as • First time HCI • Create virtual (One tab for each
Networks domain Administrator installed switches network)
controllers • StorageAccess
• Operation • Set IP
System addresses • PlantLAN
Supported
• Validate • DeltaV
• Running on communicatio Primary
Domain n between
Controller hosts • Etc.

Set Up Witness Computer used • Running as • First time HCI • Set up NTP • Network
for Witness Administrator installed Setup
• Set up 2
network • NTP Settings
adapters for
• Join Domain
host access
Info
• Join Domain

42
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Set Up Cluster One of the • DeltaV Virtual • First time HCI • Create cluster • Set Name
domain Studio is installed or
• Set up cluster • Select Hosts
controllers Installed new host
shared
added • Set IP
• Running as storage, add
Addresses
Administrator witness
• Select Witness
• Operation
System • Create Cluster
Supported
• Running on
Domain
Controller

Expand Cluster One of the • Running as • When adding • Validates the • Select Cluster
domain Administrator node to cluster
• Select Host
controllers cluster configuration
• Expand
• Adds node to
Cluster
cluster
• Allocates new
drives

3.3 Set up a Windows Server host computer

In a DeltaV Virtual Studio system, the operating systems on all hosts must all match. That
is, you can only have hosts of one operating system in the network.
Installation must be local, either from the install media or from files copied to the host
computer hard drive. Attempting to install from a non-local network drive may result in
errors.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. On the host, verify the following:
• The Boot Optimized Server Storage (BOSS) raid controller is RAID1.
• The OS partition was set at the maximum size when the host was booted for the
first time.
Important
Refer to the topic Install Windows operating system with RAID level verification.
If the RAID level is incorrect, you must change it to RAID1.

2. Install Windows Server 2022 according to the Windows instructions.

3. Log on to the host computer as an administrator.
4. Install the latest firmware and drivers that you downloaded.
5. Rename the computer.
This is the host computer's name and it cannot match any of the DeltaV virtual
machine names that you will create later. Names must conform to the host
operating system naming requirements as well as other naming requirements, such

43
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

as Microsoft domain member names, Microsoft DNS naming restrictions, any Active
Directory restrictions if this host will be a part of a larger domain, your corporate
naming restrictions, and so on. It is recommended you keep the name
alphanumeric, without using any special characters.

6. Install updates as appropriate. For information on this, refer to Downloads to obtain

before starting.
Note
Update the host computer operating system cautiously. Many updates require a
reboot of the computer. You should only install the updates listed in Emerson KBA
#AK-1200-0033.

a) Some updates require other updates to be installed first. You may be notified
that more updates exist even if you have just updated the host. If more exist,
install them as appropriate.
b) Disconnect the Ethernet port after the updates are installed and before
running the host and network setup utilities.

7. Set the date and time.

3.4 Configure RDMA

Remote Direct Memory Access (RDMA) enables computers to transfer data across the
network without involving CPU or OS resources of the hosts involved. This improves
throughput and performance, and reduces latency and CPU overhead.
Slots 1 and 7 on host servers are used for RDMA network connections in an HCI DeltaV
Virtual Studio system.
Note
The figures in this topic have been edited to conceal information that could identify the
system.

Note
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.

1. Reboot the server.

2. During the POST, press F2 to go into System Setup.
3. Select Device Settings.
4. Select the NIC in slot 1, port 1.

44
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

5. Select Device Level Configuration.

6. In the Virtualization Mode area, select the SR-IOV option.

45
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
Although you selected only port 1, this actually configures both ports 1 and 2 in slot
1.

7. Repeat steps 3 through 6 for the NIC in slot 7.

Note
Although you select only port 1, this actually configures both ports 1 and 2 in slot 7.

8. Go back to the System Setup Main Menu and select System BIOS.

9. Select Integrated Devices.

46
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

10. In the SR-IOV Global Enable area, select the Enable option.

11. Save your configuration and reboot the server.

When you finish this, proceed to initializing the host servers - Initialize a host.

3.5 Initialize a host

You must make sure operating systems are configured according to the instructions in Set
up a Windows Server host computer. Repeat this on each host server.

47
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
During the install process, you will have to configure or at least confirm IP addresses
several times. Any time you work with an IP address, record that address so later you can
be sure you do not try to reuse it.

When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log on to the host server as the Administrator.
2. Open the Network and Sharing Center and make sure all four of the 25GbE ports for
the NICs in slots 1 and 7 are visible. If any are missing, contact Emerson support
before you proceed with the DVS installation.
Note
The NIC names follow this form: Intel(R) Ethernet 25G 2P E810-XXV Adapter <num>

3. Start Autorun.
a) Load the installation media.
b) Start File Explorer and browse to the \Autorun folder on the installation
media.
c) Right-click Autorun.Hci.exe and select Run as administrator from the
context menu.
Note
For information about the Autorun UI, refer to the topic The Autorun.Hci
interface.

4. Click Initialize Host.

5. Click Next Step.
Autorun checks the system and shows a list of features that must be configured,
such as host hardening or MPIO configuration. These features will be set up
automatically.
6. Click Configure Features.

Note
You may be prompted to perform some actions. And the host computer may
reboot automatically.

7. After the reboot, log into the computer as the Administrator. Autorun will restart
and complete the feature configuration.
8. Complete the IP address for the StorageAccess network.
9. Optional: Enter a new subnet mask, and/or a new IP addresses for the Primary DNS
server.
10. Optional: Choose how to deal with a backup DNS server.
• If a backup DNS server is detected, Autorun displays the IP address for that
server. To keep that server, make sure it has the IP address you want.

48
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

• If a backup DNS server is detected, and you do not want to use it, click - Remove
Backup DNS Server. The UI changes to read + Add Backup DNS Server and the
IP address disappears.
• If a backup DNS server is not detected, and you do want to use a backup, + Add
Backup DNS Server. The UI changes to read - Remove Backup DNS Server and
displays a feature for entering an IP address. Make sure the backup has the IP
address you want.

11. Click Next Step.

12. Use the Select Net Adapter dropdown to choose an adapter for the host access
primary network. In the diagram at the top of the Autorun UI, flashing colors
indicate the currently-selected adapter.
Note
To help decide which connections to use, refer to the network diagrams in the
document section HCI network architecture.

13. Optional: Change the IP address(es) for the primary network, and/or the DNS
server(s).
14. Optional: Change the subnet mask.
15. Optional: Click Add Host Access Secondary, and repeat steps 11-13 for the host
access secondary network.
Note
When there is not a secondary network, the Next Step button is inactive. Click Add
Host Access Secondary to activate the button.

16. Click Next Step. Autorun will begin configuring the interfaces.
17. When the configuration finishes, if there are no error messages, click Deploy Now.

Related information
Install software from ISO file onto the virtual machine

3.6 Configure the S-Series switch

If the switch is replaced, you do not have to run the entire DVS install process to configure
the new switch.

When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log in to any HCI host that is connected to the switch through a serial port.
2. Load the DeltaV Virtual Studio installation media.
3. Start File Explorer and browse to the Autorun folder on the installation media.
4. Right-click Autorun.Hci.exe and select Run as Administrator.

49
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
For information about the Autorun UI, refer to the topic The Autorun.Hci interface.

5. Click Configure HCI S-Series Switch.

Note
This will shut down all uplink ports.

6. Click Next Step.

Autorun checks the connection with the switch.
Note
If the connection status is not good, click Refresh to see if that re-establishes the
connection.

7. Click Next Step.

8. In the list, select the password option you want.
• For a new HCI switch:
a. Select Create New User.
b. Enter the new user name.
c. Enter and confirm the new password.
d. Record the name and password.
e. Click Next Step.
• To simply log in on the HCI switch:
a. Select Login.
b. Enter the user name.
c. Enter the password.
d. Click Next Step.
• To change the password on the HCI switch and then log in:
a. Select Change Password.
b. Enter the user name.
c.
d. Enter the old password.
e. Enter and confirm the new password.
f. Click Next Step.

9. Enter the desired IP address for the switch.

50
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Note
The switch IP address is used by DVS Diagnostics and is required when filling out the
Edit Health Collection Settings dialog in the DVS client. Each switch should be
assigned a unique, unused IP address located on the StorageAccess subnet.

10. Click Next Step.

11. Click Start Import.
If some of the uplink ports are needed, enable only those needed. It is recommended that
you disable unused ports on the S-series switch. Refer to the topic Enable or disable S-
Series switch ports.

Related information
HCI network architecture
Supported operating systems for DeltaV Virtual Studio

3.7 Enable or disable S-Series switch ports

During the process of configuring an S-series S5212F-ON switch, HCI autorun will enable
all 25GbE ports and disable all 100GbE ports. If you need 100GbE ports for additional
network connections, you must enable them manually. Any unused ports should be
disabled.
You can see the status of all ports. The figure below shows the table that is the output
from the command given in step 2.

In the Status column, the value "up" means the port is enabled, and the value "admin
down" means the port is disabled/shut down.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.

51
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

If you need to change which ports are up or down, do the following:

1. Use Putty (or some terminal emulator) to log in to the S-series switch. (For the
default username and password, check the manufacturer's documentation that
comes with the switch.)
2. To see which ports are enabled and disabled, enter this command: show ip
interface brief
This will show a table of interfaces like the one seen above.

3. To enable a port, enter the following sequence of commands.

Note
Each time you enter a command, the command prompt will change. This is shown
in the following examples.

OS10# config
OS10(config)# interface ethernet <port #>
OS10(conf-if-eth1/1/<port #>)# no shutdown
OS10(conf-if-eth1/1/<port #>)# exit
OS10(config)# exit
OS10#

Note
In these examples, <port #> represents the number of a port. So if you want to
specify port number 1/1/12, the syntax is interface ethernet 1/1/12.

4. If there is more than one port to disable, repeat the sequence in step 3 as many
times as needed, using different port numbers.
5. To disable a port, enter the following sequence of commands.

OS10# config
OS10(config)# interface ethernet <port #>
OS10(conf-if-eth1/1/<port #>)# shutdown
OS10(conf-if-eth1/1/<port #>)# exit
OS10(config)# exit
OS10#

6. If there is more than one port to disable, repeat the sequence in step 5 as many
times as needed, using different port numbers.
7. Verify the status of ports is correct by entering this command: show ip
interface brief
Check port condition in the Status column.

8. Shut down the terminal emulator.

9. If you have more than one S-series switch, you may need to repeat this procedure
on the other switch(es).

52
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

3.8 Configure the N-Series switch

The N-series HCI switch, if it is used, is most often used for connecting thin clients with the
host server network and the witness box.

When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log in to any HCI host that is connected to the N-series HCI switch through a serial
port.
2. Load the DeltaV Virtual Studio installation media on that host.
3. Start File Explorer and browse to the Autorun folder on the installation media.
4. Right-click Autorun.Hci.exe and select Run as Administrator.

Note
For information about the Autorun UI, refer to the topic The Autorun.Hci interface.

5. Click Configure HCI N-Series Switch.

6. Click Next Step. Autorun checks the connection with the switch.
• If the connection status is bad, a failure message displays. Click Refresh to retry
the check.
• If the connection is good, the message "Connected to the switch" displays. Click
Next Step to continue.

7. Enter the numbers of ports that the host will use for different purposes:
• # for thin client only ports
• # for HCI host ports
• # for host access only ports
In this, you are not entering port designations. Each number represents a quantity -
how many ports are allocated to the uses shown. The ranges are sequential and the
system automatically starts one range immediately after the previous range. The
figure below shows the port allocation pane with port quantities entered.

53
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
In the column to the right of the pane, the numbers show ranges - which groups of
ports are used for which purposes.

8. Record the numbers of ports by type for future reference, then click Import.

Note
If the configuration fails, it may be due to an incompatible OS on the switch. If so, refer to
the topic Upgrade the N-series switch OS.

Related information
HCI network architecture
Supported operating systems for DeltaV Virtual Studio
Upgrade the N-series switch OS

3.9 Setting up domain controllers

You can use physical domain controllers in the HCI system, or virtual domain controllers,
or both. However, the Autorun program used to install DeltaV Virtual Studio only provides
an option for setting up virtual domain controllers. If you want to set up one or more
physical domain controllers, you must do that manually by using Server Manager. For that,
refer to the topic Configure a physical host domain controller.
A host domain can be created for any multiple host configuration. When using failover
clustering, a host domain is a requirement. The storage manager computer can be both
the domain controller and the storage manager computer, provided the computer meets

54
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

the minimum requirements for both roles. All hosts must join this domain to participate in
the failover cluster.
All domain controllers for the host domain must be at the same operating system version
as the hosts (except during the process of upgrading the hosts). Therefore, on hosts
running Windows Server 2022, the host domain controller must be running Windows
Server 2022. To support the VMs running on the hosts, the functional level of the host
domain must be set to 2016.

Note
For multiple-cluster systems, all clusters should be in the same domain.
It is recommended that all hosts be in one domain. If not, you must establish two-way
trusts between the domains if replicating or moving virtual machines across the domains.
DNS forwarding may also be necessary to connect to the hosts by name. Consult your
network administrator or Microsoft for specifics on configuring domain-to-domain
communication.

An additional host domain controller is required to keep the host domain functioning in
the event the first domain controller fails. The additional domain controller can also act as
an additional DeltaV Virtual Studio application computer, and it can become the storage
manager computer in the event the first domain controller fails (provided the computer
meets the minimum requirements for both roles). The additional host domain controller
can also be a virtual machine.
Note
Virtual machines are not supported for use as master or backup time servers.

Connect the host domain network cards to the HostAccess Only ports on the N-series
switches to build the domain.
Important
Keep the domain controllers updated with the Microsoft updates listed in Emerson KBA
#AK-1200-0033. Failure to apply patches listed in the KBA can lead to spontaneous
reboots of the domain controllers, or other serious impact to machine functionality.

3.9.1 Configure a virtual host domain controller

You should run this procedure first to set up the primary domain controller, and then
repeat it later to set up any additional domain controllers you need. You can have multiple
additional domain controllers.

WARNING
You must leave virtual domain controllers running on the host's local storage. Do not
move them to the cluster shared storage. Moving them would result in complete loss of
the cluster and all virtual machines if both nodes go down at the same time. This is an
unrecoverable scenario.

During the install process, you will have to configure or confirm IP addresses several times.
Any time you work with an IP address, record that address so that later you do not try to
duplicate it.

55
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
For an additional domain controller, you will be prompted to enter login credentials for a
user.

When you finish this phase of the install process, if you do not need to configure another
domain controller, you can return to the checklist to view the next phases - Checklist for
installing DVS on an HCI system.
1. Log in on the host where the domain controller VM will run, and start Autorun.
a. Start File Explorer and browse to the \Autorun folder.
b. Right-click Autorun.Hci.exe and select Run as administrator from the
menu.
Note
For information about the Autorun UI, refer to the topic The Autorun.Hci interface.

2. Select Configure DVS Domain Controller VM and click Next Step.

3. Use the pull-down list to select the domain controller type, and click Next Step.
4. Enter a name for the domain controller, and click Next Step.

Important
Domain controller names must be unique.

5. If you are creating an additional domain controller, skip this step. For a primary
domain controller, enter a fully qualified domain name, and click Next Step.

Important
If you will be using DVS to manage both an old DVS system and a new HCI system,
you can use the existing domain by entering the fully qualified name for the domain
in the older DVS system.

The system validates the domain name.

6. Make sure the IP address and the subnet mask for the StorageAccess network are
correct (you can change the entries if you want), and click Next Step.
7. Make sure the IP addresses and the subnet masks for the Host Access primary and
secondary networks are correct, (you can change the entries if you want) and click
Next Step.
8. Browse to the location of the Windows Server 2022 template.
a) Click Browse for template location. A file browsing dialog opens.
b) In the file browser, navigate to the folder that holds the desired template.
c) Click OK.
d) Click Next Step.

9. Review the settings, and if they are correct, click Deploy. If not, click a stage name
in the left sidebar of the Autorun UI to return to that stage, and start over from
there.

56
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

The system configures the virtual domain controller, doing things like setting up
the NICs and mounting a virtual hard drive. This will take approximately 4 to 5
minutes.
10. A virtual machine window opens, and shows that Hyper-V is starting.
Note
The title bar at the top of the VM window should show the name you entered back
in step 4.

11. You may be prompted for a Windows product key. If you have the key, enter it and
click Next. Otherwise, click Do this later.
The virtual machine reboots.
Note
During reboots, the VM window will go completely black. This is normal. If the
Virtual Machine Connection window is showing only a black screen for more than
one minute, close the Virtual Machine Connection window and then click Launch
VM Console.

12. Inside the VM window, the Date and Time dialog displays. Make sure the date,
time, and time zone are correct for the location of the domain controller, and click
OK.
13. The Microsoft software license terms dialog appears. Read the terms, scroll down to
the bottom, and click I agree.
The virtual machine reboots.
14. You are prompted for account credentials. Enter a domain administrator name, and
enter the password twice, and click OK.

Note
The name "Administrator" is not allowed.

15. The virtual machine reboots several times. During this it does things like applying
personalized settings and running PowerShell and VM setup.
This step will take several minutes. The system may reboot up to 10 times while it
checks user accounts and applies configuration settings.
Important
During this reboot cycling, do not resize, move, or otherwise manipulate any VM
windows. Doing so may cause a malfunction.

16. In the VM window, click the Ctrl+Alt+Delete icon, and log in. This completes
domain controller configuration.

57
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

3.9.2 Configure a physical host domain controller

Static IP addresses configured on this computer must match the subnets of the host
computers.
Disable any unused NICs.
Make sure the date, time, and time zone are the same on all domain controllers.
All domain controllers for the host domain must be at the same operating system version
as the hosts (except during the process of upgrading the hosts). Therefore, on hosts
running Windows Server 2022, the host domain controller must be running Windows
Server 2022. To support the VMs running on the hosts, the functional level of the host
domain must be set to 2016.
Make note of the IP addresses of the NICs that are handling the host domain traffic. Those
are the addresses to use when setting up DNS addresses of the host NICs.
Note
For multiple cluster systems, all clusters should be in the same domain.
It is recommended that all hosts be in one domain. If not, you must establish two-way
trusts between the domains if replicating or moving virtual machines across the domains.
DNS forwarding may also be necessary to connect to the hosts by name. Consult your
network administrator or Microsoft for specifics on configuring domain-to-domain
communication.
If the Server Manager displays any error messages, refer to the Windows documentation.

When you finish this phase of the install process, if you do not need to configure another
domain controller, you can return to the checklist to view the next phases - Checklist for
installing DVS on an HCI system.
1. Log in on the host server that will be the domain controller.
2. Open Server Manager and select Add Roles and Features.
If an information screen appears, click Next.
3. Select Role-based or feature based installation and click Next.
4. Click Select a server from the server pool, select the local server, and click Next.
5. Select the Active Directory Domain Services check box.
6. Click Add Features on the window.
7. Select the DNS Server check box.
8. Click Add Features on the window.
9. Click the expansion icon beside the File and Storage Services check box.
10. Click the expansion icon beside the File and iSCSI Services check box.
11. Click Add Features and then click Next.
12. Select the Failover Clustering check box.
13. Click Add Features on the window, and then click Next.
14. Click Next twice, then click Install.
15. Wait for the installation to complete, then click Close.

58
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Note
Make sure you wait until the progress meter at the top shows the installation is
complete.

16. In Server Manager, click the Notification flag (this should have a yellow exclamation
mark).
17. Under Post-Deployment Configuration, click the link labeled Promote this server
to a domain controller.
18. In the Active Directory Domain Services Configuration Wizard, select Add a new
forest
19. Enter the root domain name and click Next.
20. On the Domain Controller Options page, accept the defaults and provide the
Directory Services Restore Mode password.
21. Click Next.
22. On the DNS Options page, ensure the check box is clear, and click Next.
23. On the Additional Options page, verify the NetBIOS name, and click Next.
24. On the next two pages (Paths and Review Options pages), accept the settings and
click Next.
25. On the Prerequisites Check page, review the warnings (there are always warnings
but none should require action) and verify that the domain controller passed the
check successfully.
This will take some time. Wait for the message window to be populated.
26. Click Install.
27. Wait for the installation to complete, then click Close.
The server reboots.
28. Log in as the domain administrator. The password will be the same as that for the
local administrator.
29. In the Server Manager, check for ADDS (Active Directory Domain Services) and DNS
entries in the list under Dashboard, Local Server, All Servers.
30. Set the local time on the domain controller to correspond to the time at the
location where the servers will be deployed.
31. Install the drivers and firmware you downloaded from Dell. Make sure the installed
version is the same as that listed for the model of server in KBA NK-1700-0089 (or
newer, if the listed version was unavailable).
32. Install the Microsoft updates you copied to a storage device when you downloaded
updates. The appropriate file to run on the domain controllers should be named
something like windows10.0…_MONTHYEAR.msu where MONTHYEAR is the month
followed by the year of the patch’s release.
Keep the domain controllers updated with the Microsoft updates listed in Emerson KBA
AK-1200-0033.
Important
Failure to apply patches listed in the KBA can lead to spontaneous reboots of the domain
controllers, or other serious impacts to machine functionality.

59
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Enable or disable Remote Shell access

Before you can configure an additional host domain controller, you must temporarily
enable Remote Shell access on that machine. To do this, edit the access group policies.

Enable Access
1. On the additional domain controller, start the Group Policy Management Editor.
2. Select Domain name → Domains → Domain name → Domain Controllers →
Default Domain Controllers Policy.
3. Right-click on the Forest, and then click Edit.
4. Select Computer Configuration → Policies → Administrative Templates: Policy
Definitions → Windows Components → Windows Remote Shell.
5. On the right-side pane, find Allow Remote Shell Access, and change the policy
setting to Enabled.
6. Click OK.
7. Select Domain name → Domains → Domain name → Domain Controllers →
Default Domain Policy.
8. Right-click on the Forest, and then click Edit.
9. Select Computer Configuration → Policies → Administrative Templates: Policy
Definitions → Windows Components → Windows Remote Shell.
10. On the right-side pane, find Allow Remote Shell Access, and change the policy
setting to Enabled.
11. Click OK.
12. Open a Command Prompt window and enter this command: gpupdate /force

Disable access
1. On the additional domain controller, start the Group Policy Management Editor.
2. Select Domain name → Domains → Domain name → Domain Controllers →
Default Domain Controllers Policy.
3. Right-click on the Forest, and then click Edit.
4. Select Computer Configuration → Policies → Administrative Templates: Policy
Definitions → Windows Components → Windows Remote Shell.
5. On the right-side pane, find Allow Remote Shell AccessOn the machine that will be
the, and change the policy setting to Disabled.
6. Click OK.
7. Select Domain name → Domains → Domain name → Domain Controllers →
Default Domain Policy.
8. Right-click on the Forest, and then click Edit.

60
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

9. Select Computer Configuration → Policies → Administrative Templates: Policy

Definitions → Windows Components → Windows Remote Shell.
10. On the right-side pane, find Allow Remote Shell Access, and change the policy
setting to Disabled.
11. Click OK.
12. Open a Command Prompt window and enter this command: gpupdate /force

Configure DNS addressing for host network on domain

controllers
A host domain must exist with each domain controller also having the role of the DNS
server.
Important
You must configure the DNS addressing for host networks on both domain controller
machines before you configure an additional domain controller.

All members of the host domain must have the DNS servers' IP addresses designated on
both the host primary and host secondary network cards.
Important
This topic is a guide to configuring DNS server IP addressing on the domain controllers.
There are options you may need or want to take advantage of that are not incorporated
here. For more detailed information on DNS, refer to Microsoft's TechNet. Some examples
of articles to read are
• http://technet.microsoft.com/en-us/library/dd378849(v=ws.10).aspx
• http://technet.microsoft.com/en-us/library/ff807362(v=ws.10).aspx

1. Open the Control Panel and select Settings → Network and Internet → Change
Adapter Options.
2. Select the primary host domain network card.
a) Right-click and select Properties...
b) Select Internet Protocol Version 4 (TCP/IPv4) from the list.
c) Click Properties.
d) Select Use the following DNS server addresses:.
e) Enter the IP addresses as follows, using the primary host network IP
addressing:
Table 3-1: DNS configuration for the Primary Host Network Card
Current computer you Preferred DNS for Alternate DNS for
are on primary host network primary host network
Domain controller (first The IP address of the The loopback address
promoted) additional domain (127.0.0.1)
controller's primary host
network's card

61
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Table 3-1: DNS configuration for the Primary Host Network Card
(continued)

Current computer you Preferred DNS for Alternate DNS for

are on primary host network primary host network
Domain controller (second The IP address of the first The loopback address
promoted) domain controller's (127.0.0.1)
primary host network's
card

f) Click OK.

3. Select the secondary host domain network card.

a) Right-click and select Properties...
b) Select Internet Protocol Version 4 (TCP/IPv4) from the list.
c) Click Properties.
d) Select Use the following DNS server addresses:.
e) Enter the IP addresses as follows using the secondary host network IP
addressing:
Table 3-2: DNS configuration for the Secondary Host Network Card
Computer where you are Preferred DNS for Alternate DNS for
logged in primary host network primary host network
Domain controller (first The IP address of the The loopback address
promoted) additional domain (127.0.0.1)
controller's secondary host
network card
Domain controller (second The IP address of the first The loopback address
promoted) domain controller's (127.0.0.1)
secondary host network
card

f) Click OK.

4. Repeat these steps on all domain controllers.

Configure an additional host domain controller as a VM

This procedure is performed on the host machine that will run the VM for the additional
domain controller. You can use a remote connection to that machine.

WARNING
You must leave virtual domain controllers running on the host's local storage. Do not
move them to the cluster shared storage. Moving them would result in complete loss of
the cluster and all virtual machines if both nodes go down at the same time. This is an
unrecoverable scenario.

62
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

You must be logged in to the host computer as a domain administrator.

All domain controllers for the host domain must be at the same operating system version
as the hosts (except during the process of upgrading the hosts). Therefore, on hosts
running Windows Server 2022, the host domain controller must be running Windows
Server 2022. To support the VMs running on the hosts, the functional level of the host
domain must be set to 2016.
The functional level is automatically set on the domain controller VM.
Make note of the IP addresses of the NICs that handle the host domain traffic. Those are
the addresses to use when setting up the host NICs' DNS secondary addresses.
Note
For multiple cluster systems, all clusters managed by one DVS client should be in the same
domain.
It is recommended that all hosts be in one domain. If not, you must establish two-way
trusts between the domains if moving virtual machines across the domains. DNS
forwarding may also be necessary to connect to the hosts by name. Consult your network
administrator or Microsoft for specifics on configuring domain-to-domain
communication.
If the Server Manager displays any error messages, refer to the Windows documentation.

When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log in on the host and start Autorun.
a. Start File Explorer and browse to the \Autorun folder.
b. Right-click Autorun.Hci.exe and select Run as administrator from the
menu.

2. Select Configure DVS Domain Controller VM and click Next Step.

3. Use the drop-down list to select Additional Domain Controller, and click Next
Step.
4. Enter a name for the additional domain controller, and click Next Step.
5. Enter the fully qualified domain name, and click Next Step.
6. Enter a valid IP address and subnet mask setting for the StorageAccess network,
and click Next Step.
7. Enter a valid IP address and subnet mask setting for the primary host access
network.
8. Optional: a valid IP address and subnet mask setting for the secondary host access
network.
9. Click Next Step.
10. Click Browse for template location.
11. Browse to and select a directory that holds valid template files, a valid IP address
and subnet mask setting for the additional domain controller, and click Next Step.
12. Check the settings displayed. If a setting is incorrect:
a) Click the tab on the left side of the Autorun UI for that setting.

63
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

b) Enter a correction a valid IP address and subnet mask setting for the
additional domain controller, and click Next Step.
c) Step through this procedure until you return to this point.

13. Click Deploy.

The system configures the virtual domain controller, doing things like setting up
the NICs and mounting a virtual hard drive. This will take approximately 4 to 5
minutes.
14. A virtual machine window opens, and shows that Hyper-V is starting.
Note
The title bar at the top of the VM window should show the name you entered back
in step 4.

15. You may be prompted for a Windows product key. If you have the key, enter it and
click Next. Otherwise, click Do this later.
The virtual machine reboots.
Note
During reboots, the VM window will go completely black. This is normal - just wait
for the reboot to finish.

16. Inside the VM window, the Date and Time dialog displays. Make sure the date,
time, and time zone are correct for the location of the domain controller, and click
OK.
17. The Microsoft software license terms dialog appears. Read the terms, scroll down to
the bottom, and click I agree.
The virtual machine reboots.
18. You are prompted for account credentials. Enter a domain administrator name, and
enter the password twice, and click OK.

Note
The name "Administrator" is not allowed.

19. The virtual machine reboots several times. During this it does things like applying
personalized settings and running PowerShell and VM setup.
This step will take several minutes. The system may reboot up to 10 times while it
checks user accounts and applies configuration settings.
20. When the rebooting is finished, in the VM window, click the Ctrl+Alt+Delete icon,
and log in. This completes domain controller configuration.

64
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

3.10 Join a host to a domain

You may need to reboot after running this procedure.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log in to the machine that will join the domain.
2. Load the DeltaV Virtual Studio installation media on that machine.
3. Start File Explorer and browse to the Autorun folder on the installation media.
4. Right-click Autorun.Hci.exe and select Run as Administrator.

Note
For information about the Autorun UI, refer to the topic The Autorun.Hci interface.

5. Select Join Domain and click Next Step.

6. Enter the following configuration settings:
• Fully qualified domain name for the domain you are joining
• Domain administrator username
• Domain administrator password
Important
If you will be using DVS to manage both an old DVS system and a new HCI
system, you can use the existing domain by entering the fully qualified name for
the domain in the older DVS system.

7. Click Join.
Repeat this procedure on each machine that must join a domain.

Note
If you are installing a new system, proceed to the phase of hardening the domain, covered
in topic Harden domain controllers.

3.11 Harden domain controllers

This explains how to harden your hosts and domain controllers within a DeltaV Virtual
Studio system in line with Center for Internet Security guidelines. The hardening is
implemented through group policies and registry changes.
You must manually run hardening on a domain controller. This is not necessary on hosts,
because because they are hardened automatically during host initialization.
Note
Mapping of network drives is disabled by the hardening process until Host Setup is
executed. Move all required resources onto the Domain Controller before you run the
hardening utility.

65
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

On a domain controller created as a VM, the install media is automatically copied to the
folder C:\DvsMedia.
The operating system is Windows Server 2022.
The system is within a domain.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log in to the domain controller.
2. On a physical domain controller, load the DeltaV Virtual Studio installation media.
3. Start File Explorer and navigate to the Autorun folder.
4. Right-click Autorun.Hci.exe and select Run as administrator. The Autorun dialog
opens.
Note
For information about the Autorun UI, refer to the topic The Autorun.Hci interface.

5. Click Apply Domain Hardening.

6. Click Next Step.
7. When hardening is finished, click Restart to continue setup.

3.12 Create a domain-level account for DVS

This procedure is executed on the primary domain controller. Perform this procedure
when creating your host system, when you upgrade a virtualized system, or when you add
a new host to a virtualized system.
The domain account created with this procedure is a special account that is required for
computers running the DeltaV Virtual Studio application and all hosts in a domain-based
system in order to communicate with each other.
On a domain controller created as a VM, the install media is automatically copied to the
folder C:\DvsMedia.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log on the domain controller as an administrator-level user.
2. On a physical domain controller, load the DVS installation media.
3. Start Autorun.
a) Start File Explorer and navigate to the \Autorun folder.
b) Right-click Autorun.Hci.exe and select Run as administrator.

Note
For information about the Autorun UI, refer to the topic The Autorun.Hci
interface.

4. Select Create Domain Account for DVS Services.

66
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

5. Click Next Step.

6. Select the check boxes for all hosts that will need to communicate with each other,
and/or that will be managed by this machine, and click Deploy Now.
If you are installing DVS on a new system, proceed to Install DeltaV Virtual Studio.
If you are upgrading a domain, continue to the task of upgrading the hosts.

Related information
User accounts for the virtualized DeltaV system
Create a domain user

3.13 Install DeltaV Virtual Studio

Installation must be local, either from the install media or from files copied to the
computer's hard drive. Attempting to install from a non-local network drive may result in
errors.
You can install DeltaV Virtual Studio (DVS) on
• A host
• A physical domain controller
• A virtual domain controller
• A physical or virtual DeltaV node
For an online DeltaV system, the DeltaV Virtual Studio may only be installed on a host
computer, or a computer that is not a DeltaV node and that meets the operating system
requirements. For offline systems, the DeltaV Virtual Studio can be installed on the
ProfessionalPLUS node.
Note
It is not supported to install DeltaV Virtual Studio on a DeltaV computer where the version
of .NET Framework is lower than what is installed by DeltaV Virtual Studio.

This procedure installs both the DVS service, and the DVS application (the user interface,
also called the client). The service runs only on the machine where the virtualization
system identifier is connected, but the client runs everywhere it is installed.
When you are installing DVS for the fist time, you must run this procedure twice. First to
install the DVS service, and then again to install the DVS client.
DeltaV Virtual Studio must be installed on a computer that has access to the virtual
machine host(s) that DVS will manage. Typically, this is the host computer; or, in a host
domain, the host domain controller. However, it can be any machine that can
communicate with the hosts being managed by this instance of DeltaV Virtual Studio.
Note
This operation may require rebooting the computer.

To avoid having to skip and repeat any steps, log in as a local administrator when in a
workgroup, or as a domain administrator when in a domain.

67
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
In an HCI system, hosts are in a domain, but VMs can be arranged in workgroups.

When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Take steps to ensure a reboot will not shut down important activities running on the
computer.
For example, if this is on a domain controller, verify the domain is healthy and that
another domain controller can continue to maintain the domain.
2. Start Autorun.
a) Load the installation media.
b) Start File Explorer and browse to the \Autorun folder on the installation
media.
c) Right-click Autorun.Hci.exe and select Run as administrator from the
context menu.
Note
For information about the Autorun UI, refer to the topic The Autorun.Hci interface.

The Autorun dialog opens.

3. Click Install DeltaV Virtual Studio.
4. Click Next Step.
If needed, acknowledge the prompt that a reboot is required.
5. During the DeltaV Virtual Studio installation, the NTP Settings utility displays. If NTP
has not already been configured on the computer, set the options based on where
you are installing the software.
The DeltaV Virtual Studio computer must be connected to the host network and
must remain synchronized in time with the host computers. Therefore, you can
select the Listener role for this computer.

Note
If you are installing DeltaV Virtual Studio on a host computer, you do not need to
modify the settings for NTP because the host setup required NTP configuration.

a) Click Yes when prompted to set up NTP.

Clicking No skips the NTP utility, and is not recommended unless you have
already configured NTP through another DeltaV Virtual Studio client on this
computer.

b) Select the role. Listener is recommended for an independent (non-host)

DeltaV Virtual Studio computer.
Note
Virtual machines are not supported for use as master or backup time servers.

Listener This node obtains the time from the master or backup
time server. Use this for all nodes other than any
designated as a master or backup time server.

68
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Master Time This node supplies time to all other nodes.

Server
Backup Time This node supplies time in the event the master is not
Server available.

c) Based on the role selected, enter the appropriate IP address for the time
server machine.
Important
Do not use the automatic private IP address of 169.x.x.x (where x= a
number).
Virtual machines are not supported for use as master or backup time servers.

Role Request time from Notes

(IP Address/Subnet
Mask)
Listener Enter the addresses of the You are defining the two
ports on the master and IP addresses the computer
backup time servers from can use for time (only the
which this computer will master is required). The
poll the time. listener does not supply
time to any other node.
Master Time Server Not required. The master is the time
source. All other
computers will go to this
IP address for their
primary time server.
The host domain
controller must be the
master time server.
Backup Time Server Enter the address of the You are defining the IP
port on the master time address where the backup
server from which this time server goes for its
computer gets its time. time.

d) Click Next.
e) Based on the role selected, enter the appropriate IP addresses to respond to
time requests.
Important
Do not use the automatic private IP address of 169.x.x.x (where x= a
number).
Virtual machines are not supported for use as master or backup time servers.

69
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Role Respond to time Notes

requests on
(IP Address/Subnet
Mask)
Listener Not applicable. The Listener role does not
respond to time requests.
Master Time Server Enter the addresses of the You are defining the IP
ports on this computer address from which all
(the master time server) other computers will poll
on which other computers the time.
will request the time. You must define at least
one IP address.
Backup Time Server Enter the addresses of the You are defining the IP
ports on this computer address from which all
(the backup time server) other computers will poll
on which other computers the time in the event that
will request the time in the the master time server is
event that the master time unreachable.
server is unavailable. You must define at least
one IP address.

f) Click Next.
g) Review your IP addresses. Click Back to change an entry, click Apply to
accept the values.
h) Click OK to confirm NTP configuration is finished.

6. When you are prompted that the NTP installation is finished, click OK on the
message box.
The Autorun UI now shows the Review pane.
7. If prompted to reboot, click Yes. This completes the installation of the DVS
software.

Related information
Install the DeltaV Virtualization system identifier on a VM
Copy release-specific files to the host
Install the DeltaV Virtualization system identifier

3.14 Copy the DVS license to the DeltaV Virtual

Studio computer
The virtualization licenses must be placed on the DeltaV Virtual Studio (DVS) computer
(the same computer where you install the system identifier).
1. Log in to the computer that is running the DVS service, and load the license media.
Note
The license media is not the same as the install media.

70
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

2. Browse to the license file on the license media (in the Licenses folder on the
media).
License files have a .LIN extension.
3. Copy the *.LIN file.
4. Paste the *.LIN file in the \EmersonVirtualization\License folder.

3.15 Using the virtualization system identifier

The DeltaV virtualization system identifier, also called the access key, is a USB drive (flash
drive or "thumb" drive) that contains authentication data required to run the DeltaV Virtual
Studio (DVS) service. It is often called a "dongle".
Installing the access key allows access to all DVS functionality. Without the access key, the
only functions available are those which are critical in disaster recovery. For more
information, refer to Critical functions.

Related information
Install the DeltaV Virtualization system identifier
Install the DeltaV Virtualization system identifier on a VM

3.15.1 Install the DeltaV Virtualization system identifier

The DeltaV Virtualization system identifier (the system access key) must be installed on
the DeltaV Virtual Studio Manager computer. This is the same computer where you copy
the license (.LIN) file.
In an HCI system, it is recommended you use one of the host servers as the DVS computer.
Note
The DeltaV Virtual Studio Manager computer may be the same computer as the Domain
Controller. The DeltaV Virtualization system identifier is not the same as the DeltaV
system identifier.

Installing the access key allows access to all DVS functionality. Without the access key, the
only functions available are those which are critical in disaster recovery. For more
information, refer to Critical functions.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log in to the DVS Manager computer (the machine running the DVS service).
2. Insert the system identifier into a working USB port.
3. Using DeltaV Virtual Studio, verify the system identifier is recognized.
a) Start DeltaV Virtual Studio.
b) Connect to the Virtual Studio Manager machine (where both the system
identifier and license file are).
c) Go to Help → Licensing menu and verify the license count. If no license
count displays, either your system identifier or your license file is not
recognized.

71
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
You can use Device Manager to view the USB ports. The system identifier is
displayed there as SafeNet, Inc. HASP key, or SafeNet, Inc Hardlock key.

Related information
Install DeltaV Virtual Studio

3.15.2 Install the DeltaV Virtualization system identifier on a

VM
The USB to IP device is also called the UTN device.
To accept the DeltaV Virtualization system identifier (access key) and be used as the DVS
host machine, the license file (.LIN) must be copied to the VM.
Note
The virtual machine that connects to the USB to IP converter must have a user logged in or
the application must be installed as a service. Otherwise, the device will not be recognized.
Refer to the instructions provided by the manufacturer.

Installing the access key allows access to all DVS functionality. Without the access key, the
only functions available are those which are critical in disaster recovery. For more
information, refer to Critical functions.

1. Determine the IP address you will use for the USB to IP device based on the
following:

Option Description
On the DeltaV Set the IP address of the device by following the recommended
ACN (preferred IP addresses for non-DeltaV equipment on the DeltaV network
method) (for example, a 10.4.x.x IP address where x is a number).
Note
The IP address assigned to the USB to IP device is not tracked.
This means that the USB to IP device IP address could be
assigned to a DeltaV node if you add the DeltaV node after you
configure this device. Therefore, Emerson recommends that you
adhere to the reserved IP addresses found in Reserved DeltaV IP
addresses.

On a dedicated Set the IP address of the USB to IP device to the network IP

network such address range that you are using for the network; for example
as the Thin 198.168.x.x (where x is a number).
Client Network The host and the virtual ProfessionalPLUS must also have an NIC
assigned and connected to this network.
Note
Each virtualized system must have its own virtualization system
identifier.

72
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

2. Connect the Ethernet port on the UTN device to a switch on the chosen network.
3. Make sure the UTN device has power and the Ethernet port is connected to the
switch corresponding to the network you are going to use.
4. Connect to the virtual Professional or ProfessionalPLUS machine using DeltaV
Remote Desktop Connection with the Connect to console option. Or, you can use
DeltaV Virtual Studio to connect to the console of the virtual machine.
5. Locate the SEH UTN Manager installer file and copy it to the VM where you want to
install it.
6. Double-click on the installer to share it and proceed through the installation,
keeping all defaults.
7. Open SEH UTN Manager and click Edit under Selection List.
8. Click Scan and watch for the UTN device to appear under Network List.

Note
In its unconfigured state, the UTN device will have a random IP address in the
169.254.x.x range. The UTN software should still be able to detect it without being
on the same network.

9. Click on the UTN device and then click Add.

10. Verify that the UTN device was added to the Selection List, then click OK.
11. Right-click the UTN device and select Set IP Address.
12. Enter the IP address and subnet mask you chose in step 1.
13. You must enter a value for Gateway. If your chosen network does not have a default
gateway, enter the IP address of the primary domain controller.
14. Verify the settings are correct, then click OK.
15. Refresh the network list until you see the UTN device appear with its new IP.
16. If you have not already done so, physically attach the virtualization system identifier
to the UTN device.
17. Refresh UTN Manager and verify that the virtualization system identifier shows up.
It should be called "Hardlock USB".

73
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
This may also be called "Sentinel HL" or "HASP HL".

18. Right-click the virtualization system identifier and click Activate. Then verify the
status changes to Activated.
If the status is not correct:
• You may have a bad UTN device
• The license key may be wrong
• One of the steps above may have been done incorrectly

19. Right-click the UTN device and select Activate Auto-Connect.

20. Select the check box for the USB port that the virtualization system identifier is
plugged into, and click OK.
21. Now the VM should auto-connect to the virtualization system identifier if the VM is
restarted.

Related information
Install DeltaV Virtual Studio
Install the DeltaV Virtualization system identifier
Using the virtualization system identifier

3.16 Configure hosts for live storage migration

This utility must be run from the host's domain controller. It is part of the installation
process when installing DeltaV Virtual Studio on the domain controller. If DeltaV Virtual
Studio is not installed on the host, you must run this utility from the DeltaV Virtual Studio
installation media.
This option is not available on non-domain installations.
You must be logged in as a domain administrator to run this utility.
Important
Run this utility whenever you add a new host that you want to move virtual machines to or
from.

This utility sets the constrained delegation between the selected hosts so that
authentication between those hosts can occur during live storage migration of the virtual
machines.
For more information about live storage migration, refer to the Microsoft TechNet article
at this location: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/
manage/Use-live-migration-without-Failover-Clustering-to-move-a-virtual-machine.
You can also run this utility from the Start menu if DeltaV Virtual Studio is installed on the
host's domain controller.
1. Run the utility from the Start menu (Start → DeltaV Virtual Studio → Configure
Hosts for Live Migration) or when prompted during DeltaV Virtual Studio
installation.

74
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Note
If DeltaV Virtual Studio is not installed on the host's domain controller, run the
utility from the DeltaV Virtual Studio installation media. To do this, browse to the
installation media's Service\program files\Emerson\Virtualization
\_Support folder and double-click the
EmersonProcess.Virtualization.LMAuthentication.exe file.

2. On the Configure Hosts for Live Storage Migration dialog, select the hosts where
Kerberos will be used to authenticate live storage migration traffic.
Note
This selection is necessary. Do NOT click Skip, if it appears on the dialog.

3. Click Add.

3.17 Start the DeltaV Virtual Studio client

The DeltaV Virtual Studio client, also called the application, can exist on any computer
with a connection to the host, provided that computer meets the DeltaV Virtual Studio
system requirements.
You must be logged in as an administrator on the DeltaV Virtual Studio (DVS) computer.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.

1. Double-click the DeltaV Virtual Studio desktop shortcut icon.

2. Enter the user name and password.

This username and password must exist as an administrator on the DeltaV Virtual
Studio computer and any host computers that you are managing.

3. Use DVS to add and manage your hosts and virtual machines.
Refer to the DVS online help (Help → View Help) for details on using this
application.

3.18 Set up the hosts

Before starting this procedure, configure the operating system - refer to the topic Set up a
Windows Server host computer.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log in to a DVS system domain controller.
2. Start Autorun.

75
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

a) Start File Explorer and browse to the \Autorun folder.

• On a physical domain controller, load the DeltaV Virtual Studio
installation media and browse to \Autorun.
• On a virtual domain controller, browse to C:\DvsMedia\Autorun.

b) Right-click Autorun.Hci.exe and select Run as Administrator from the

context menu.
Note
For information about the Autorun UI, refer to the topic The Autorun.Hci
interface.

3. Select the Set Up Hosts option and click Next Step.

4. Enter a domain administrator password and click Validate Password.
5. Complete the following for each host tab listed:
a) If the NTP settings are incorrect, click Launch NTP and configure the NTP
settings. For information on NTP, refer to the topic Set the NTP time
synchronization.
b) Click Deploy.
c) After the current host setup completes, if you are prompted to restart the
host, log on the host being configured, and manually restart it.
d) Copy the release-specific files, including installation media ISO files, to the
host that was just configured. For more information, refer to the topic Copy
release-specific files to the host.
This completes host setup.

Related information
Set up host networks

3.19 Copy release-specific files to the host

The last step of host setup is copying the DeltaV release-specific files, including DeltaV
installation media ISO files, to the host. The DeltaV installation media ISO files are used
when creating a virtual DeltaV machine where you cannot use a pre-installed template (for
example, a ProfessionalPLUS that is a domain controller).
This procedure uses the CopyFilestoHost application.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Attach the server template media to the host. (Insert the USB drive.)
2. Start File Explorer and browse to the \Templates folder.
3. Right-click copyfilestohost.exe and select Run as Administrator
4. Click Copy Files.

76
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

5. When the operation is finished, click the X icon to close the dialog.
6. Repeat this procedure on each host where DeltaV release-specific files are needed.

3.20 Set up host networks

Use this procedure to configure the networks for the hosts on your PowerEdge servers.
Before you begin this:
• Make sure you have run Host Setup on all hosts.
• Determine which network card will be used for what purpose.
• Recommended - produce a network diagram. Some possible networks are shown in
Server connection plans.
For information about the Autorun UI and how to use it, refer to the topic The Autorun.Hci
interface.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Connect all static IP address networks.
2. Log in to any host and start Autorun.
a) Start File Explorer and browse to the \Autorun folder.
• On a physical domain controller, load the DeltaV Virtual Studio
installation media and browse to \Autorun.
• On a virtual domain controller, browse to C:\DvsMedia\Autorun.

b) Right-click Autorun.Hci.exe and select Run as Administrator from the

context menu.
Note
For information about the Autorun UI, refer to the topic The Autorun.Hci
interface.

3. Click Set Up Host Networks. The network interfaces will be collected from each
host.
4. Click Next Step.
The network interface ports are listed as tabs.

77
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

5. Select a tab. The physical port is represented by the highlight in the graphic.

6. In the Interface Name field, enter the desired port network name.
7. Use the Select Network Adapter Role drop-down to select the desired role for this
port.
8. Use the controls in the Common Configuration card to enter the information
common to all of the hosts. This includes:
• Subnet mask
• Default gateway IP address
• Preferred DNS Server IP address
• Alternate DNS Server IP address

9. Expand each host card to enter the host-specific IP address.

10. Click Validate Connections.
11. Repeat steps 5 - 10 for each port you want to define.

Related information
Set up the hosts

3.21 Set up the witness machine

The witness is usually a small PC networked with the hosts, as shown in the HCI
architecture diagram.
Any time you work with an IP address, you should record that address so that later you can
be sure you do not reuse it.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.

78
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

1. Log in on the witness machine and start Autorun.

a) Load the DVS installation media.
b) Start File Explorer and browse to the \Autorun folder.
c) Right-click Autorun.Hci.exe and select Run as administrator from the
menu.
Note
For information about the Autorun UI, refer to the topic The Autorun.Hci
interface.

The Autorun dialog appears.

2. Select Set up Witness, then click Next Step.
3. Complete the IP address for the witness, and make sure the subnet mask is correct
(you can change the entry if you want).
4. Make sure the IP addresses and the subnet masks for the primary and backup DNS
servers are correct, (you can change the entries if you need), and click Next Step.
5. If you need to set up NTP for the witness, click Launch and refer to the topic Set the
NTP time synchronization. If not, click Skip.
6. Join the witness to the domain.
a) Enter the fully qualified domain name.
b) Enter the domain administrator name and password.
c) Click Join.

Related information
HCI network architecture

3.22 Set up a cluster

Each host which is not a witness must be part of a cluster. You can have more than one
cluster.
This procedure is required during system virtualization. You may need to repeat it later, if
you add more machines or if you want to create an additional cluster.
Important
A DVS HCI cluster supports a maximum of 4 hosts.

When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log in on a domain controller as an administrator.
2. Start Autorun.
a) Load the DVS installation media.
b) Start File Explorer and navigate to the \Autorun folder.
c) Right-click Autorun.Hci.exe and select Run as administrator.

79
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
For information about the Autorun UI, refer to the topic The Autorun.Hci
interface.

3. Select Set Up Cluster.

4. Enter a name for the cluster and click Next Step.
5. Select the machines that will be part of the cluster, and click Next Step.
6. For each host in the cluster, set the IP address.
7. If you need to create another cluster, repeat steps 4 and 5 as needed.
8. Click Next Step.
9. Select the machine that will be the witness box, and click Next Step.
10. Click Create Cluster.

Note
This step will take several minutes. When it completes, the cluster will be set up and
ready for use.

11. Optional: Click Set up Another Cluster to return to step 4, so you can create a
different cluster.
The cluster is automatically validated during this process. Manual validation should
not be needed unless there is a problem that requires troubleshooting.

Related information
Validate a cluster

3.23 Set up virtual networks

You must set up virtual networks in DeltaV Virtual Studio so the VMs can communicate
properly. These virtual networks separate the traffic from each network in DVS so VMs can
be assigned to separate networks.
You will need the names of the NICs you named when you set up the host networks,
earlier.
When you finish this phase of the install process, you can return to the checklist to view
the next phases - Checklist for installing DVS on an HCI system.
1. Log in to any host and start the DVS client.
2. Right-click on one of the hosts and select Edit Virtual Networks.
3. Click Add Virtual Network.
4. Use the Physical Network Card drop-down to select one of the NICs that you
named when setting up the host.
5. Repeat steps 2 and 3 until you have selected all NICs that were named in host setup.

80
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Note
Only select the Connect Host check box for a host if you want the host computer to
connect directly to the virtual network. Normally the host should not be directly
connected. If you have a need for the host to directly connect, you should also
configure the IP address field.

6. Verify the settings for each network and click OK.

7. Repeat steps 1 through 5 for each host in DeltaV Virtual Studio.

3.24 Installing the DeltaV Remote Desktop

Connection (DRDC)
The DeltaV Remote Desktop Connection is the mechanism by which you will connect to a
DeltaV virtual machine. The DRDC connects using two mechanisms: a console connection
that simulates being at the computer, and a remote client connection.
Normally, you would not install DRDC on a host or a domain controller. It is meant for use
on thin clients and thick clients, to connect to virtual machines elsewhere in the system.
The purpose of using DRDC, instead of using the Remote Desktop Connection
(mstsc.exe) in Windows, is to ensure that a remote workstation has all active and
disconnected sessions (except session 0) logged off prior to remote access by the client.
This avoids issues with DeltaV and fast user switching. When connecting to DeltaV using
the DeltaV Remote Client Sessions, either DRDC or Windows Remote Desktop Connection
can be used.
Install the DeltaV Remote Desktop Connection on any computer that will need to access
the virtual machine.
Note
The screen resolution of the physical DRDC client is used for the connection to the virtual
machine. Therefore, before connecting, you must set the screen resolution of the DRDC
client to a supported resolution for DeltaV.

Installation must be local, either from the install media or from files copied to the host
computer hard drive. Attempting to install from a non-local network drive may result in
errors.
Note
The DeltaV Remote Desktop Connection (DRDC) installer requires Microsoft .NET
Framework 3.5 or later.

81
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

To avoid having to skip and repeat any steps, log in as a domain administrator.
1. Connect the installation media to the computer.
2. Start File Explorer and browse to DeltaV Virtual Studio\Autorun.
3. Right-click Autorun.Vrtx.San.Sa.exe and select Run as administrator

Note
Do not select Autorun.Hci.exe.

4. Click Install DeltaV Remote Desktop Connection.

5. If you have not configured NTP, select the Setup to run NTP check box. If you have
configured NTP, proceed to step 8.
6. Select the check boxes for the other options you want.
• Automatically start DRDC after reboot - Configures DRDC to start on boot up
anytime this computer is restarted. This is recommended for any computer that
serves as an operator station, specifically a thin client.
• Default Virtual Machine - Configures DRDC to connect to a specific virtual
machine. This is recommended for any computer that serves as an operator
station and always connects to a specific virtual machine. This can be changed at
any time from the DRDC application. This option requires that you select the
Automatically start DRDC after reboot option.

Note
If you select this, you must enter a machine name.

• Lock USB ports - Hardens the client so that the USB ports cannot be used to
access storage devices. Your USB-based keyboards, mice, and network interface
devices continue to operate.
• Enable network redundancy - Sets the thin client network NICs for redundant
networks. Two NICs are required.
• Enable write filter (for thin clients only) - Sets the thin client write protection
feature to Enabled. If you have additional hardware configuration to perform on
the client (for example, monitor installation/configuration) where you will need
to write to the hard drive, do not select this option now. You can set this from
the administrator login's desktop.
• Add hosts to trusted list and enable delegation (for connect to console) -
Enables you to enter the names of the hosts that will connect to this client.
• Apply security settings (requires reboot) -
• Reboot this computer after installation is finished - Reboots the client once
the DRDC installation is complete. If this option is cleared, you must reboot the
machine later to enforce all setup options.

7. Click OK.
8. If you selected the Setup to run NTP option, the NTP Settings utility displays.
Otherwise, skip to step 9.

82
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Note
The clients should be set as listeners for the same NTP source as the hosts and the
DeltaV virtual machines to which they are connecting. If the client time becomes
out of sync with either the hosts or the DeltaV system, the client will not be able to
connect to the virtual machine (either to the console of the virtual machine or to
the DeltaV desktop).

a) Select the role of Listener.

This node obtains the time from the master or backup time server, and
should be used for all nodes other than a master or backup time server.

b) Click Next.
c) Enter the appropriate IP address for the time server machine.
Important
Do not use the automatic private IP address of 169.x.x.x (where x= a
number).
Virtual machines are not supported for use as master or backup time servers.

Role Request time from Notes

(IP Address/Subnet
Mask)
Listener Enter the addresses of the You are defining the two
ports on the master and IP addresses the computer
backup time servers from can use for time (only the
which this computer will master is required). The
poll the time. listener does not supply
time to any other node.

d) Review your IP addresses. Click Back to change an entry, click Apply to

accept the values.
e) Click OK on the confirmation message.
The DRDC installation continues.

9. If you selected the Enable thin client redundancy option, you are prompted to
configure the thin client network's redundancy settings.
a) Select the two thin client networks from the list to enable redundancy.
b) Click OK to configure the redundancy between the two selected networks.
This starts the service.

Note
Thin client network redundancy must also be configured on the virtual machines
that have two virtual NICs for the thin client network..

10. You are prompted to reboot the computer, if that option was selected. If that
option was not selected, you will need to reboot the computer at a later time to
finish the application's installation.

83
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
In order to use Connect to Console, the computer running the DeltaV Remote
Desktop Connection must have the Remote Server Administration feature enabled,
allowing it to interact with the host computer.

The installation of the DeltaV Remote Desktop Connection enables Connect to

Console. However, you can verify that it is running by following these steps:
a) Open the Windows Control Panel.
b) Click Programs and Features.
c) Click Turn Windows features on or off.
d) Enable the Hyper V tools under Remote Server Administration Tools →
Role Administration Tools → Hyper-V Tools.

To connect to the DeltaV virtual machine using the DeltaV Remote Desktop Connection
(without the Connect to console option), you must enable Terminal Services on the
virtual machine. To do this, connect to the virtual machine's operating system desktop
and open the Services window (usually found under either Control Panel or Computer
Management, depending on the virtual machine's operating system).

Related information
HCI network architecture
Configure the thin client network redundancy
Set the NTP time synchronization

3.24.1 Supported operating systems for the DeltaV Remote

Desktop Connection
The DeltaV Remote Desktop Connection (DRDC) client can be installed on specific
workstation operating systems and used to connect to the DeltaV virtual machine. The
DeltaV Remote Desktop Connection client computer must have a common network with
the virtual machines; for example, the thin client network.
The DeltaV Remote Desktop Connection (DRDC) client can connect to any version of
virtual DeltaV machine, provided the DRDC client is installed on one of the supported
operating systems.
Note
The list below shows the operating systems for non-thin client devices. Our dedicated thin
clients come with an embedded operating system that cannot be changed. That device is
tested for use as a DRDC client and therefore is excluded from this table. The intent of the
list is to show other operating systems on which DRDC can be installed; for example, when
creating a thick client.

The screen resolution of the physical DRDC client is used for the connection to the virtual
machine. Therefore, before connecting, you must set the screen resolution of the DRDC
client to a supported resolution for DeltaV.
These operating systems allow the client to connect to the virtual machine using the
Connect to Console option:

84
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

• Windows 10 Professional LTSB (32-bit and 64-bit)

• Windows 10 Enterprise LTSB (32-bit and 64-bit)
• Windows Server 2022 Datacenter (64-bit)
• Windows Server 2022 Standard (64-bit)
Note
The DeltaV Remote Desktop Connection client computer must have the Remote Server
Administration feature enabled.

3.24.2 Allowed DeltaV Remote Desktop Connection types

The DeltaV Remote Desktop Connection (DRDC) application supports two connection
types. Connecting to the virtual machine using the Remote Desktop option enables you to
log into the virtual machine's Windows desktop (when you provide a Windows user with
appropriate credentials). However, you cannot always log into the DeltaV desktop. The
information below illustrates when you will need to use the Connect to Console feature
versus the Remote Desktop connection option.
Selecting the Connect to console option is required when:
• You are logging in to a virtual Application Station or any other DeltaV workstation type
that does not support DeltaV Remote Client Sessions.
• You are connecting to a DeltaV virtual workstation running a Windows Server
operating session where you do not have DeltaV Remote Client Sessions configured.
Once logged into the operating system, you can log into DeltaV.
The Remote Desktop connection is sometimes required because:
• DeltaV workstations running a Windows Server operating system require DeltaV
Remote Client Sessions in order to log into the DeltaV system.
• DeltaV workstations running the Windows workstation operating systems (for
example, Windows 10), can support one DeltaV Remote Desktop Connection.
The following table shows the allowed (= can log into DeltaV) DeltaV Remote Desktop
Connections to the virtual DeltaV machine.
Table 3-3: Allowed connections log into the DeltaV virtual machine
DeltaV Windows server Windows server Windows Windows
workstation type operating operating workstation workstation
system on VM system on VM operating operating
(DRDC) (DRDC with system on VM system on VM
Connect to (DRDC) (DRDC with
Console) Connect to
Console)
ProfessionalPLUS Not allowed Allowed Allowed Allowed
ProfessionalPLUS Allowed Allowed Not applicable Not applicable
as a Remote
Client Server

85
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Table 3-3: Allowed connections log into the DeltaV virtual machine (continued)
DeltaV Windows server Windows server Windows Windows
workstation type operating operating workstation workstation
system on VM system on VM operating operating
(DRDC) (DRDC with system on VM system on VM
Connect to (DRDC) (DRDC with
Console) Connect to
Console)
Local Operator Not normally Not normally Allowed Allowed
installed on the installed on the
Windows Server Windows Server
operating operating
systems systems
Operator Station Allowed Allowed Not applicable Not applicable
as Remote Client
Server
Local Not allowed Allowed Allowed Allowed
Professional-Base-
Maintenance
Local Application Not allowed Allowed Allowed Allowed
Station
Remote Not allowed Allowed Allowed Allowed
Professional-
Operator-Base
Remote Not allowed Allowed Allowed Allowed
Application
Station
Inter-Zone Server Not allowed Allowed Not applicable Not applicable
Simulate for Not applicable Not applicable Allowed Allowed
standalone laptop
or workstation

3.24.3 Using the DeltaV Remote Desktop Connection

commands
The DeltaV Remote Desktop Connection (DRDC) is the interface to connect to the virtual
machines. Once installed, a single icon for DRDC is placed on the desktop.
By using the DeltaV Remote Desktop Connection commands, you can create multiple
desktop shortcuts that connect to different default virtual machines, as well as connect to
a virtual machine using a Remote Desktop Protocol (RDP) session file. These commands
can also be run from a command prompt, if you have access to one.
Note
The default installation location (path) of DeltaV Remote Desktop Connection on a
Windows 10 computer is C:\Program Files (x86)\Emerson\Virtualization
\DRDC.

Connect to default virtual machine using DRDC

86
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Open a Command Prompt window and enter this command: DRDC.exe connect

Note
The default virtual machine is set in the DeltaV Remote Desktop Connection instance on
the client.

Connect to a specific virtual machine using DRDC

Open a Command Prompt window and enter this command: DRDC.exe connect
VirtualMachineName
(Where VirtualMachineName is the actual name of the virtual machine to which you are
connecting.)
Connect to a virtual machine using a custom .RDP file
Open a Command Prompt window and enter this command: DRDC.exe "C:
\mycustomfile.rdp"
(Where C:\mycustomfile.rdp is the path to and filename of the custom .RDP file you want to
use to connect to the virtual machine.)

3.25 Additional setup actions following DVS

installation
Once the initial installation is completed, there are other actions that need to be
performed, or that could be.

3.25.1 Upgrade the N-series switch OS

N-Series switches run a Dell proprietary operating system. For use in a virtualized HCI
system, that operating system must be version 6.7.
If the switch configuration fails, you may need to install a new OS on the switch. To do
that:
1. Open a Web browser and go to the URL for your switch model:
• N2200 series: https://www.dell.com/support/home/en-us/product-support/
product/networking-n2200-series/drivers
• N3200 series: https://www.dell.com/support/home/en-us/product-support/
product/networking-n3200-series/drivers
• N3000E-ON series: https://www.dell.com/support/home/en-us/product-
support/product/networking-n3000e-on/drivers

2. Use the controls on the Dell web site to select and download the latest 6.7 release
of the OS.
3. Connect a console to the switch, and use PuTTY or some other terminal emulator to
connect to the switch as an administrator.

87
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
Check the manufacturer documentation that comes with the switch for login
information.

4. Connect the removable media to the switch and download the new OS to the
switch.
5. Reboot the switch and repeat the step for using Autorun to configure the switch for
the virtualized system.

Related information
Configure the N-Series switch
Supported operating systems for DeltaV Virtual Studio

3.25.2 DeltaV Virtual Studio Registration service

The DeltaV Virtual Studio Registration service is a Windows service that collects details
about your DeltaV virtualization hardware and software so you can communicate those
details to Guardian. This enables Emerson to administer the various support services
provided with your DeltaV system. These services include product warranty, telephone
technical support, limited-access internet support pages, and a notification process to
alert you to important technical developments concerning your system. These services are
tailored to the specific hardware and software content of your system.
The service also enables Emerson Lifecycle Services to calculate an accurate health score
for your system.
The service collects details about your system periodically and saves them in a DeltaV
Virtual Studio Registration file located, by default, in c:\DVSRegistration. It captures
the following:
• HCI, SAN and VRTX hardware components
• Blade hardware components
• DVS software version
• Number of DeltaV Systems under your DVS license
• Number of VMs under your DVS license
• Operating system of each VM
• Microsoft patches installed on the domain controller and host blades
• Firmware version of the VRTX and SAN hosts
The DeltaV Virtual Studio installation process installs the registration service on the
domain controller computer. The service is set to Automatic start, and it starts after the
final computer reboot of the DVS installation process. You can change the storage
location for the registration file, and the interval between captures.

Related information
Upload a DeltaV Virtual Studio registration file to the Guardian website
Modify the DeltaV Virtual Studio Registration CONFIG file

88
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Modify the DeltaV Virtual Studio Registration CONFIG file

The config file is named DvsRegistrationService.exe.config and is located in c:
\Program Files (x86)\Emerson\Virtualization\Registration.
You can change the following key values in the service’s CONFIG file:
• XMLSaveLocation: The folder where the service stores the registration file containing
your system information
• XMLGenerateInterval: The interval (in hours) when the service regenerates the
registration file containing your system information

Related information
DeltaV Virtual Studio Registration service
Upload a DeltaV Virtual Studio registration file to the Guardian website

Upload a DeltaV Virtual Studio registration file to the

Guardian website
The service stores registration files on the DVS system domain controller computer in the
c:\DVSRegistration folder (unless you specify a different location in the CONFIG file).
Registration files follow this format: system-id_date_time_SysRegData.epm.
To upload a registration file:
1. Copy the registration file to a USB drive.
2. Using the USB drive, copy the registration file to a computer with access to the
Guardian website.
3. Access your Guardian account.
4. Click System Info.
5. Click Browse and navigate to the registration file.
6. After you select the registration file, click Start Upload.

Related information
DeltaV Virtual Studio Registration service
Modify the DeltaV Virtual Studio Registration CONFIG file

3.25.3 Create and configure a system of VMs in an IDDC

Domain
This section will focus on how to create a system of VMs running in an Independent DeltaV
Domain Controller (IDDC) domain. This system starts with VMs for the IDDC nodes and a
ProfessionalPLUS. Then you can use the VM Builder tool to create VMs for other nodes in
your DeltaV system. To improve the security of the system, you should harden the hosts
and domain controllers.
Note
Another option, not described here, is to use your ProfessionalPLUS as the domain
controller instead of using IDDC.

89
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Create Independent DeltaV Domain Controller VMs

1. Start DeltaV Virtual Studio.
2. Find and click on the host where the Independent DeltaV domain controller (IDDC)
should be located, and then click Create VM. The Create Virtual Machine dialog
opens.

3. On the DeltaV tab, In the Template Source field, select the folder where the
virtualization templates were copied.
4. In the DeltaV Version field, select the version that you will install on the system.
5. In the Template field, select Blank Server (Server 2016).
6. In the Install As field, select Independent DeltaV Domain Controller.
7. In the Node Name field, enter the name you want for the IDDC node.
8. In the Domain Role field:
• If this is the first IDDC set up, select Primary Domain Controller.
• If there is another IDDC already in the system, select Additional Domain
Controller.

9. In the Fully Qualified Domain Name field, enter the full domain name you want to
use for your DeltaV domain.
Important
You must not use "DeltaV" as the first part of your domain name - Emerson does not
support having a domain that starts in that way.

10. Verify all the information you entered is correct and click Next.

90
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

11. On the General tab, assign each Virtual Network needed by the VM. You can add or
remove networks as necessary by using the Add and Remove buttons.
12. If necessary, rename the Virtual Network Cards to make the names more
meaningful for your networks. Assign the appropriate Virtual Switch to each card."
13. Check the IP address of each NIC. You should not change any values assigned to the
DeltaV Primary or Secondary networks, but you can enter information for the other
networks as needed.
14. Verify that all information entered is correct and then click Next.

15. On the Advanced tab, leave the default value for the Virtual Machine Folder and
Group fields.
16. Assign RAM and virtual processors as necessary according to your design
document. 16 GB of RAM and 2 virtual processors should be sufficient for an IDDC.

91
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

17. Verify Failover settings. If you are using failover, make sure the first host listed is
where the VM will normally run, and the second host listed is where it should fail
over.
18. Assign the Maximum Size of the hard drives according to your design document. It
is recommended that you leave the Dynamic check box selected. 80 GB on the C:
drive and 40 GB on the D: drive should be sufficient for an IDDC.
19. Verify that your settings are correct and click Next.

Note
Leave the Advanced settings in their default configuration.

20. Click Finish.

21. In DeltaV Virtual Studio, navigate to the host where you set up the VM, and expand
the view. You should now see the new VM. To monitor progress, click on the VM
and view the Current Operation and Progress columns.

Related information
Configure Independent DeltaV Domain Controller VMs

Configure Independent DeltaV Domain Controller VMs

Most of the VM configuration is done automatically by DeltaV Virtual Studio. This process
will take time and the VM may log out and restart several times. Do not interfere with the
automated process except when it asks for user input.
Note
This section is written for setting up the primary domain controllers. The process is the
same for subsequent domain controllers except you will enter the previously created
password when prompted, rather than creating new accounts.

1. After the VM is finished configuring in DVS, connect to it by selecting it and then

clicking Connect.
2. On the Product Key screen, click Do this later.

Important
You must activate Windows on the VM before deploying the system to production.

3. When you see the Date and Time screen, do the following:
a) Click Change time zone.
b) Select the time zone where the server will be deployed, then click OK.
c) Click Change date and time.
d) Set the date and time to fit the location where the server will be deployed,
then click OK.
e) Click the Internet Time tab and select Change settings.
f) Clear Synchronize with an internet time server and click OK.
g) Click OK.

92
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

4. On the License Terms screen, click I Agree.

5. When prompted to create the domain administrator account for the domain, enter
a username unique to your system.
6. Create a password then click OK.

Important
Make sure you document the domain username and password. If you forget these
credentials you will be locked out of the system.

7. When prompted for the Directory Services Restore Mode password, create a
password and click OK.

Important
Make sure you document the DSRM password. You will need it anytime you make
changes to the domain or add domain controllers.

8. After the VM restarts, log back in with the account you created in step 5.
Note
To pass the Ctrl+Alt+Delete command to the VM and unlock it, click the Ctrl+Alt
+Delete icon at the top left of the VM connection window.

9. When prompted to set the password for the DeltaV Services account, create and
enter a password.
Important
Make sure you document the password for the DeltaVAdmin service account. You
will need this account to set up DeltaV services in the future.

10. At this point the manual input is finished. Wait for automatic setup to complete,
and log back in after the final restart.

Related information
Create Independent DeltaV Domain Controller VMs

Create a ProfessionalPLUS VM
This procedure is performed in DeltaV Virtual Studio.
1. Click on the host where the ProfessionalPLUS should be created, and then click
Create VM.
The Create Virtual Machine dialog opens.

93
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

2. In the Template Source field, select the folder where the virtualization templates
were copied.
3. In the DeltaV Version field, select the version that you will install on the system.
4. In the Template field, select DeltaV Workstation (Server 2022).
5. In the Install As field, select DeltaV ProfessionalPLUS.
6. In the Node Name field, enter the name you want for the ProfessionalPLUS.
7. In the Domain Role field, select Domain Member.
8. In the Fully Qualified Domain Name field, enter the full DeltaV domain name
specified when creating the IDDC nodes.
9. If desired, select the Enable Remote Client Functionality check box.
10. Verify all the information you entered is correct, and click Next.
11. On the General tab, assign each virtual network needed by the VM. You can add or
remove networks as necessary by clicking Add and Remove .
12. If it is useful, rename the Virtual Network Cards to make them more meaningful for
your networks. Assign the appropriate Virtual Switch to each card.
13. Check the IP address of each NIC. You should not change any values assigned to the
DeltaV Primary or Secondary networks, but you can enter the information for the
other networks as needed.
14. Verify that all information entered is correct, then click Next.

94
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

15. Leave the default value for the Virtual Machine Folder and Group fields.
16. Assign RAM and virtual processors as necessary according to your design
document. 16 GB of RAM and 4 virtual processors should be sufficient for a
ProfessionalPLUS.
17. Verify Failover settings. If you are using failover, make sure the first host listed is
where the VM will normally be, and the second listed is where it should fail over to.
18. Assign the Maximum size of the hard drives according to your design document. It
is recommended that you leave Dynamic selected. 80 GB on the C: drive and 120
GB on the D: drive should be sufficient for a ProfessionalPLUS.
19. Verify that your settings are correct, and click Next.

Note
Leave the Advanced settings in their default configuration.

20. Click Finish.

21. In DeltaV Virtual Studio, navigate to the host where you set up the VM, and expand
the view. You should now see the new VM. To monitor progress, click on the VM
and view the Current Operation and Progress columns.

Configure the ProfessionalPLUS VM

Most of the VM setup will be done automatically by DeltaV Virtual Studio. This process will
take time, and the VM may log out and restart several times. Do not interfere with the
automated process except when it asks for user input.
When the VM configuration is finished, do the following:
1. Connect to the VM by selecting it and then clicking Connect.
2. On the Product Key dialog, click Do this later.

Important
You must activate Windows on the VM before deploying the system to production.

3. When prompted to enter the domain administrator account, enter the credentials
you set up during IDDC setup, and click OK.
4. After the VM restarts, log back in with the domain administrator account.
Note
To use the Ctrl+Alt+Delete command to unlock the VM, click the Ctrl+Alt+Delete
icon at the top left of the VM connection window.

5. On the Workstation Configuration prompt, click Next.

6. Click Yes to run system preferences.

95
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

7. Configure system preferences as needed, and click OK.

8. On the next screen, leave all the defaults and click Next.
9. Enter settings that fit your system's domain or workgroup design, then click Next.
10. Eventually you will see the prompt that the Workstation Configuration process
must restart your computer. Click OK.
11. After the reboot, log back in and wait for configuration to resume automatically.
12. When prompted, click OK to log off the system, and then log back in.
13. When you get the prompt that DeltaV Workstation Configuration is done installing
DeltaV, take note of the instructions and then click OK.
14. After the system restarts, log back in.
15. Now that DeltaV is installed you should also log in to DeltaV. In the password field
enter the password for the domain administrator account and click OK.
16. In FlexLock, click Windows Desktop to proceed to the Windows environment.
17. Make sure the Date and Time settings are correct.
By default, system time is derived from the same internal clock used by the
Windows Date and Time utility. If you need to synchronize system time for
workstations and controllers on the DeltaV Control Network, you must run deltav
\bin\SystemTime.exe to open the DeltaV System Time dialog.

18. Copy the DeltaV ISO files locally to the ProfessionalPLUS VM.
19. Right-click the SQL disk ISO (DVD 3) and click Mount.
20. Open File Explorer and navigate to the DeltaV\bin directory.
21. Find the SecurityUpdateManager application and double-click it to start.
22. Click OK on the first window.
23. Browse to the SQL disk you mounted, select the disk, and click OK. The installation
should proceed automatically.
24. After the installation is complete, the server will restart. Log back in to Windows and
DeltaV.
25. In File Explorer, navigate to the ISO files you copied, right-click the AMS1 media
(DVD 5), and click Mount.
26. Navigate to the mounted disk and double-click the AMSDeviceManagerSetup
application.
27. Click Next to proceed with setup.
28. Click I accept the agreement and then click Next.
29. Click Yes to continue.
30. Select Server Plus Station or Client SC Station, according to your system
architecture, then click Next.
31. Keep the default install location and click Next.
32. Keep the default components and click Next.
33. Click OK to restart the computer.
34. Log back in to Windows and DeltaV. Then repeat steps 25 and 26.

96
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

35. Click OK.

36. Select Yes, I want to restart my computer now and click Finish.

Related information
Create a ProfessionalPLUS VM

Connect USB to IP Device

The host operating systems do not support direct sharing of the host USB port with the
virtual machine. Therefore, in order to connect a DeltaV USB system identifier to a virtual
Professional or ProfessionalPLUS workstation, you must use a USB to IP converter.
Note
The virtual machine that connects to the USB to IP converter must have a user logged in or
the application must be installed as a service. Otherwise, the device will not be recognized.
Refer to the instructions provided by the manufacturer.

1. Determine the IP address you will use for the USB to IP device based on the
following:

Option Description
On the DeltaV Set the IP address of the device by following the recommended IP
ACN (preferred addresses for non-DeltaV equipment on the DeltaV network (for
method) example, a 10.4.x.x IP address where x is a number).
Note
The DeltaV system does not record or track the IP address
assigned to the USB to IP device. This means that DeltaV could
assign the USB to IP device's IP address to a DeltaV node if you
add the DeltaV node after you configure this device. Therefore,
Emerson recommends that you adhere to the reserved IP
addresses found in Reserved DeltaV IP addresses.

Note
When using the DeltaV network, be aware that the USB to IP
device is not redundant.

On a dedicated Set the IP address of the USB to IP device to the network IP

network such address range that you are using for the network; for example
as the Thin 198.168.x.x (where x is a number).
Client Network The host and the virtual DeltaV ProfessionalPLUS must also have
an NIC assigned and connected to this network.
Note
Each DeltaV system must have its own system identifier.

2. Connect the Ethernet port on the UTN device to a switch on the chosen network.
3. Make sure the UTN device has power and the Ethernet port is connected to the
switch corresponding to the network you are going to use.

97
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

4. Connect to the virtual Professional or ProfessionalPLUS machine using DeltaV

Remote Desktop Connection with the Connect to console option. Or, you can use
DeltaV Virtual Studio to connect to the console of the virtual machine.
5. Locate the SEH UTN Manager installer file and copy it to the VM where you want to
install it.
6. Double-click on the installer to share it and proceed through the installation,
keeping all defaults.
7. Open SEH UTN Manager and click Edit under Selection List.
8. Click Scan and watch for the UTN device to appear under Network List.

Note
In its unconfigured state, the UTN device will have a random IP address in the
169.254.x.x range. The UTN software should still be able to detect it without being
on the same network.

9. Click on the UTN device and then click Add.

10. Verify that the UTN device was added to the Selection List, then click OK.
11. Right-click the UTN device and select Set IP Address.
12. Enter the IP address and subnet mask you chose in step 1.
13. You must enter a value for Gateway. If your chosen network does not have a default
gateway, enter the IP address of the primary domain controller.
14. Verify the settings are correct, then click OK.
15. Refresh the network list until you see the UTN device appear with its new IP.
16. If you have not already done so, physically attach the DeltaV system identifier to the
UTN device.
17. Refresh UTN Manager and verify that the system identifier shows up. It should be
called "Hardlock USB".
Note
This may also be called "Sentinel HL" or "HASP HL".

18. Right-click the system identifier and click Activate. Then verify the status changes
to Activated.
If the status is not correct:

98
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

• You may have a bad UTN device

• The license key may be wrong
• One of the steps above may have been done incorrectly

19. Right-click the UTN device and select Activate Auto-Connect.

20. Select the check box for the USB port that the system identifier is plugged into, and
click OK.
21. Now the VM should auto-connect to the system identifier if the VM is restarted.

Create nodes in a DeltaV system and generate DVData File

This section will explain the process needed to generate the DVData file. This file is used to
quickly and easily create the DeltaV VMs corresponding to the nodes in the DeltaV system.
Note
You must set up the UTN device and connect the DeltaV System Identifier to the
ProfessionalPLUS before proceeding with this section.

1. Log in to the ProfessionalPLUS VM and open DeltaV Explorer.

2. Expand the system tree until you can see Control Network.
3. Right-click Control Network and select New.
4. Click the type of station you want to create (Application Station or Operator
Station).
5. On the General tab, supply the Name and Description of the station according to
your documentation. Leave the other tabs for now.
6. Click OK and verify that the new station appears in the DeltaV system tree.
7. Repeat steps 3 through 6 until you have added nodes corresponding to every
DeltaV station in the system.
8. In DeltaV Explorer, click File and select Export → Workstation Configuration.
9. Save the DevData.cfg file to a location that is accessible from the server that runs
DVS.
10. On the DVS server, navigate to the C:\EmersonVirtualization folder. In it,
create a new folder named DevData.
11. Copy the DevData.cfg file you created on the ProfessionalPLUS and paste it into
the C:\EmersonVirtualization\DevData folder.

Note
If you copy the DevData.cfg file to the exact location listed, DVS will find it
automatically. If you put it anywhere else, DVS may not be able to find it.

Create multiple VMs using the VM Builder Tool

The VM Builder tool will allow you to create many VMs in DVS at once. This can make
deploying VMs in a larger system much faster.

99
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Important
Before using VM Builder, you must create a DevData.cfg file on the ProfessionalPLUS,
export it, and copy it to C:\EmersonVirtualization\DevData.

Note
You should not use the VM Builder tool for Base Stations or Non-DeltaV servers.

1. In DeltaV Virtual Studio, select Tools → VM Builder.

2. Choose the correct DeltaV Version for your system.
3. Make sure DevData.cfg appears in the Workstation Configuration File field, and
the correct domain is listed under Fully Qualified Domain Name. Then click Next.
4. Select all VMs you want to deploy with the tool.
Important
Using the VM Builder to deploy base stations or AMS Server Plus is not supported. If
any of those machines are listed, make sure you deselect them.

5. For each VM, select the appropriate host according to your documentation.
6. For each VM, verify the appropriate storage location is selected. This location is
probably the ClusterStorage volume, but may vary depending on your setup.
7. Select the proper template for each VM. Normally, Application Stations should be
Server 2022 or Server 2016, and Operator Stations should be Windows 10.
8. Adjust storage, memory, and virtual processor assignments for each VM according
to your documented requirements.
9. Make sure all settings are correct, then click Next.
10. Assign each Virtual Network Card the VMs will use to a Virtual Network Switch. If
you need to add or remove a network use the Add NIC and Remove NIC buttons.
11. Verify all the names are correct, then click Next.
12. Select the appropriate Virtual Network Cards for the DeltaV Primary and Secondary
networks, then click Next.
13. For each VM, select the check boxes for all networks that will be connected, then
click Next.
14. Leave the default group assignments and click Next.
15. If necessary, change the Virtual Hard Disk assignments, then click Next.
16. Verify that failover options are correct, then click Next.
17. Verify that all settings are correct, then click Finish.
18. Wait for the VMs to finish deploying in DVS. This may take several minutes.
19. After VM deployment is finished, connect to one of the VMs through DVS.
20. Workstation Configuration will automatically run. Wait and let it run until it
prompts you for input.
21. When prompted, enter the domain administrator account credentials.
22. If you see a message saying workstation configuration must restart, wait 5
minutes, then click OK.
23. When prompted, enter the DeltaVAdmin service account password.

100
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

24. After Workstation Configuration completes, the server will restart. Log back in to
Windows and DeltaV to ensure the setup was successful.
25. Verify the date and time are correctly set to the time zone where the system will be
deployed. If not, correct them manually.
26. Repeat steps 20 through 26 for each VM you created with the VM Builder tool.

3.25.4 Creating VMs from OS-only templates

Some virtual machines (VMs) are created from templates that do not have DeltaV
preinstalled. This section will explain how to set up those unique types of VMs. You must
set up the DeltaV domain controller VM (either Independent DeltaV Domain Controller or
the ProfessionalPLUS) before you try to set up the types of VMs that are covered in this
section.

Create a non-DeltaV Server 2016 or Server 2022 VM

1. In DeltaV Virtual Studio, click on the host where the server should be, and then click
Create VM.
2. In the Template Source field, select the folder where you copied the virtualization
templates.
3. In the DeltaV Version field, select the DeltaV version that you will install on the
system.
4. In the Template field, select Blank Server (Server 2016). or Blank Server (Server
2022).
5. In the Install As field, select Basic OS.
6. In the Node Name field, enter the hostname you want the Server to have.
7. In the Domain Role field, select Workgroup.

Note
You can still join the DeltaV domain after the VM is created. However, on some
servers you will have to perform some setup before joining the domain, or domain
restrictions will prevent the setup from working.

8. Verify all the information you entered is correct and click Next.
9. Assign each Virtual Network needed by the VM. You can add or remove networks as
necessary by using the Add and Remove buttons.
10. If it is useful, rename the Virtual Network Cards to make them more meaningful for
your networks. Assign the appropriate Virtual Switch to each card.
11. Check the IP address of each NIC. You should not change any values assigned to the
DeltaV Primary or Secondary networks, but you can enter the information for the
other networks as needed.
12. Verify that all information was entered correctly, and click Next.
13. Leave the default value for the Virtual Machine Folder and Group fields.

101
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

14. Assign RAM and virtual processors as necessary according to your design
document. 16 GB of RAM and 2 Virtual Processors should be sufficient for most
standalone servers.
15. Verify failover settings. If you are using failover, make sure the first host listed is
where the VM will normally run, and the second listed is where it should fail over.
16. Assign the Maximum size of the hard drives according to your design document. It
is recommended that you leave Dynamic selected for 80 GB on the C: drive. 120 GB
on the D: drive should be sufficient for most standalone servers.
17. Verify that your settings are correct and click Next.
18. Click Finish.
19. In Virtual Studio, navigate to the host where you set up the VM and expand it. You
should now see the new VM. To monitor progress, clicking on it and check the
Current Operation and Progress columns.

Related information
Configure the non-DeltaV Server VM
Configure a base station VM

Configure the non-DeltaV Server VM

Before you begin this procedure, set up the DeltaV domain controller VM (either the
Independent Domain Controller or the ProfessionalPLUS), and finish the VM configuration.
1. Connect to the VM by selecting it and clicking Connect.
2. On the Product Key dialog, click Do this later.

Note
You must activate Windows on the VMs before deploying the system to production.

3. When you see the Date and Time dialog, do the following:
a) Click Change time zone.
b) Select the time zone where the server will be deployed, then click OK.
c) Click Change date and time.
d) Set the time and date for the location where the server will be deployed, then
click OK.
e) Click the Internet Time tab and select Change settings.
f) Clear Synchronize with an internet time server and click OK.

4. Click OK.
5. On the License Terms screen, click I Agree.
6. When prompted, enter a username.
7. Create a password and click OK.

102
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Note
You will only use this local account until you join the server to a domain. Make sure
you document the username and password.

8. After the VM restarts, log back in with the account you created in step 6.
The initial setup of the VM is complete.

Related information
Create a non-DeltaV Server 2016 or Server 2022 VM

Configure a base station VM

The current guidance from Guardian support is to create base station VMs as standalone
VMs, and perform some of the setup necessary to enable remote desktop functionality,
before installing DeltaV or joining the VM to the domain. For this reason, it is important
that you perform the actions in this section in the order shown here.
You must create and configure a VM that is not part of the DeltaV system before you begin
this procedure.
1. Log in to the non-DeltaV server you created earlier.
2. Make sure that server has an IP address that is on the same network as the
Independent DeltaV Domain Controllers. If necessary, change the IP address now.
Note
You can configure this as any unused IP on the ACN network. These IP settings will
be overwritten by DeltaV when you run workstation configuration.

3. In the Start menu, enter Services.

4. Click on the Services application.
5. Verify that the Windows Remote Management service is set to Automatic and is
running.
6. Open Server Manger and click on Add Roles and Features.
7. On the Before you begin page, click Next.
8. Select Role-based or feature-based installation, then click Next.
9. Select your server and click Next.
10. Select Remote Desktop Services and click Next.
11. On the Remote Desktop Services screen, click Next.
12. Select Remote Desktop Session Host and then click Add Features.
13. Select Remote Desktop Licensing and click Add Features.
14. Click Next.
15. Verify the settings you have chosen are correct and click Install.
16. When the installation is finished, restart the server and log back in.
17. In the Start menu, enter Services.
18. Click on the Services app.
19. Verify that Remote Desktop Services is set to Automatic and is running. If it is not,
follow the steps below to set it correctly:

103
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

a) Right-click on Remote Desktop Services and select Properties.

b) Change Startup type to Automatic and click Apply.
c) Click Start and verify that the Service status changes to Running.
d) Click OK.

20. Copy the DeltaV installation ISOs and the DevData.cfg file to the server.
21. Mount the DeltaV Installation Media (DVD 1).
22. Navigate to the Autorun folder, and start Autorun.exe.
23. Click Install DeltaV.
24. Click Next.
25. Click Yes to accept the license agreement.
26. Select Local Professional-Operator-Base-Maintenance.
27. Select Typical (DVData on D drive).
28. Click Next.
29. You will see a message that you that you will not be able to cancel the installation.
Click Yes.
30. You will be prompted to ask if you want to reboot. Click OK.
31. Log back in and wait for workstation configuration to restart.
32. On the configuration screen, click Next.
33. Browse to and select the DevData.cfg file.

104
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

34. Select the base station from the workstation list, and click Next.
35. Select the correct NICs for the DeltaV Primary and Secondary networks, and click
Next.
36. After a few minutes you will see the error message “Workstation was not able to
join the domain. Access is denied.” This message is an expected part of the setup.
Click OK.
37. Enter the DeltaV domain DVAdmin credentials and click OK.

Note
Make sure to include the domain\ part of the domain username. For example, if the
fully qualified domain name of the DeltaV domain was
TEST.EMERSON.DELTAV.LOCAL you would enter TEST\DVAdmin.

105
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

38. When a message appears asking to restart the computer, wait 5 minutes, then
click OK.
39. After the computer restarts, log in using the domain DVAdmin account.
40. Click OK on the message asking to log off the system.
41. Log back in using the domain DVAdmin account.
42. Enter the password for the DeltaVAdmin service account, then click OK.
43. Click OK on the final workstation configuration message and restart the VM.
44. Log back in to Windows and DeltaV to verify that DeltaV was installed correctly.

Related information
Create a non-DeltaV Server 2016 or Server 2022 VM

3.25.5 Install software from ISO file onto the virtual machine
ISO files can be used to install software (such as DeltaV software) on a virtual machine. This
removes the need to have a physical CD/DVD on the host that is captured by the virtual
machine. The ISO file can be mounted as though it is a drive that the virtual machine can
then see.
1. Copy the ISO file to a hard drive that host and virtual machine can access (preferably
that virtual machine's host computer's hard drive).
Copying the DeltaV ISO file is done by using the CopyFilestoHost application. For
more information, refer to the topic Copy release-specific files to the host.
2. Connect to the virtual machine's console.
Note
You can connect to the virtual machine console session in two ways:
• Double-click the virtual machine name in the hierarchy pane of DeltaV Virtual
Studio.
• Use the Connect to console option in DeltaV Remote Desktop Connection.

3. With the connection window not maximized, select Media → DVD Drive → Insert
Disk....
4. Browse to the location of the ISO file, select it, and click Open.
The ISO file appears as a DVD drive in File Explorer.
Note
Only one ISO file can be 'inserted' at a time.

5. Using File Explorer, browse to that drive.

6. For each software package, install as per the instructions specific to the package.
7. To use additional ISO files to complete the installation:
a) Select Media → DVD Drive → Eject Disk....
b) Select Media → DVD Drive → Insert Disk... and browse to the next ISO disk
needed.

106
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

8. When you are done installing, select Media → DVD Drive → Eject Disk....

Related information
Initialize a host

3.25.6 Setting up a thin client computer

Important
To perform the procedure shown below, you must be in administrative mode on the thin
client with no security features enabled. Only administrators can modify thin client
configurations to persist after a thin client reboot.
To log on as an Administrator, log off the User desktop while holding down the Shift key
until the Log On to Windows dialog appears.

Once you have logged in as an administrator:

1. Plug in the monitors and power them on.
Note
The order in which you connect the monitors determines the monitor number.
Monitor number is important to DeltaV Operate with multiple monitor systems.
The figures below show the ways you can set up the monitor numbers.

Figure 3-1: Wyse thin client model 5070 quad video port connection order

107
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Figure 3-2: Wyse thin client model 5070 quad video port alternate connection
order

2. Turn on the thin client.

3. Turn off the File Based Write Filter (FBWF) by double-clicking the FBWF Disable icon
on the desktop.
4. Reboot the thin client and log in as the administrator again.
Note
Disabling or enabling FBWF requires a reboot and logging in again.

5. Name the computer.

Note
Keep the name alpha-numeric, without special characters, to maintain
compatibility with naming convention restrictions on the host and with the virtual
machines.

6. (For this step, refer to the thin client manufacturer's documentation for specific
instructions on setting properties.) Set the following properties for the computer:
a) Make the computer a member of a workgroup.
b) Set the administrator password.
c) Set the time.

7. Disable FBWF and log out.

8. Reboot the thin client.
9. Log in as a user, not as the administrator.
10. For that user account, set the power option to Never Sleep or turn off display.

108
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

11. Log out.

12. For every user account, repeat steps 9 through 11.
13. When power options are set for all user accounts, reboot the thin client and log in
again as the administrator.
14. Arrange the monitors to physically match the DeltaV multiple monitor layout (1x2,
2x2, 1x4).
15. Set the screen resolution, color depth, and refresh rate for each monitor.

Note
For information on how to set these parameters, refer to the user documentation
for the operating system on the client computer.

• Set screen resolution on square monitors to 1024×768 or 1280×1024. For wide-

screen monitors, select 1680×1050 or 1920×1080. All screens in a multiple
monitor layout must use the same display resolution.
Note
Using a display resolution other than the supported resolutions with a display
created from the DeltaV Operate templates is not supported. DeltaV Operate
opens the display, but the resolution differences cause picture distortion. All
standard DeltaV Operate graphics are created from the DeltaV Operate
templates.

• Set the orientation.

• Except for monitor 1, extend the displays.
Note
If you change the screen resolution, it may be necessary to reset the color depth
setting to 16 bit (65,536 colors).

• Set the refresh rate according to the type of monitor used.

• If available, set colors to 16-bit High Color (this setting is not supported by some
thin client models).

16. Configure the IPv4 properties of the onboard network card.

The following options are required for all connections to the thin client network:
• Static IP address and Subnet mask that match the host's thin client network.
• Blank DNS addresses. (NetBIOS is used instead.)
• NetBIOS setting enabled
a. Click Advanced.
b. On the WINS tab, select NetBIOS as the default. (Or, select Enable
NetBIOS over TCP/IP.)

17. For redundant thin client networks:

Note
Many thin client models have two Ethernet ports, so attaching a USB to Ethernet
adapter might not be necessary.

109
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

• On a Quad-head thin client:

a. Attach the USB to Ethernet adapter.
b. Wait for the operating system to detect the device. If it does not, you
must install a device driver for the adapter by one of the following means:
— Use a USB drive that holds copies of the device drivers.
— Map to the host computer hard drive where the device drivers have
been copied.

c. Set a static IP address and Subnet mask that match the host thin client
network.
d. Blank the DNS addresses. (NetBIOS is used instead.)
e. Enable the NetBIOS setting as the Default option (as found under the
Advanced... button's WINS tab). Or, select Enable NetBIOS over TCP/IP.
• On a Dual-head thin client, on the IPv4 properties of the expansion slot network
card:
a. Set a static IP address and Subnet mask that match the host thin client
network.
b. Blank the DNS addresses. (NetBIOS is used instead.)
c. Enable the NetBIOS setting as the Default option (as found under the
button's WINS tab). Or, select Enable NetBIOS over TCP/IPAdvanced....

Important
NetBIOS must be enabled on the thin client network cards. This allows DeltaV
Remote Desktop Connection (DRDC) to access the virtual machines by name, and
not IP address. This is especially important for redundant thin client networks.

18. Connect the network cables and verify the network is communicating by pinging a
running virtual machine that is connected to the thin client network.
19. Install DeltaV Remote Desktop Connection on the computer from the USB drive
provided.
20. Set the security options on the thin client as follows:
• File Based Write Filter option = Enabled
• USB Port Lockdown

21. Enable FBWF and reboot the thin client.

Related information
Having multiple monitors in a virtual DeltaV system

Thin client redundant network

The thin client network is used to connect a client such that it can remotely connect to the
virtual machine. The thin client network can be simplex or redundant.
For redundant thin client networks, NetBIOS must be enabled on the thin client network
cards.

110
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Configuration
If the Thin Client Network Redundancy Setup utility and service has not been configured
on both the thin client and the virtual machine, connecting to the virtual machine must be
done using the virtual workstation name.
Note
If the session to the DeltaV virtual machine becomes disconnected, DeltaV logs the user
out. This can occur during a thin client network switchover. When the connection is re-
established, the user is prompted to log in.

Thin client network redundancy is achieved by installing the Thin Client Network
Redundancy service and running the Thin Client Network Redundancy Setup utility on
both ends of the thin client redundant network. The Thin Client Network Redundancy
service is configured on both client and server ends of the remote connection, by choosing
the two redundant networks.

Integrity messages
Once the service is configured and running, Multicast integrity messages are sent from
each participant every 500ms, alternating primary and secondary networks such that each
participant sends a Multicast message each second on each network. In addition to
continuously sending status messages, each participant listens for integrity messages
from all other participants. Using the information received in the integrity information,
each participant determines the ability to communicate with all other participants over
each of their common networks. When a participant detects a problem with one of the
redundant networks, it creates a route through the alternate network path, if the alternate
path is good. The net result is that any participant should always be reachable by both of
its thin client network IP addresses, even if one network is down.
In a scenario where all sides are participants in the thin client redundancy network service,
and a thin client network cable is disconnected while actively remoting into a virtual
machine from a participant thin client, a pause in the video of at least 2-3 seconds will be
observed. That time includes up to 2000ms to guarantee at least three integrity messages
have been sent from each of the participants.
Because the thin client communications are being exchanged over a TCP connection,
messages sent between the time a cable is disconnected and the creation of the alternate
route will be re-transmitted based on timeouts in the TCP protocol stack. Additional delay
may be incurred due to the frequency of the display update rate. Once the alternate route
is created, both the client side and server side rapidly process buffered RDP packets
(including video, audio, and control data) until it is once again current.

Setup utility
For the thin clients, both the Thin Client Network Redundancy service and the Thin Client
Network Redundancy Setup utility are included with the DeltaV Remote Desktop
Connection installation. The Thin Client Network Redundancy service and Thin Client
Network Redundancy Setup utility are deployed on all virtual machines. By default, the
Thin Client Network Redundancy service is set to manual start.
The Thin Client Network Redundancy Setup utility, named TcpRedundancySetup.exe,
is located on the virtual machine in C:\EmersonVirtualization\bin\. To use it, click
Start → DeltaV Virtual Studio → Thin Client Network Redundancy Setup.

111
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Once the virtual machine is configured for redundant thin client networks, the DeltaV
hardware alarm summary picture and DeltaV Condition Alarm Summary application show
when a thin client network has switched over.

Related information
Configure the thin client network redundancy
Thin client computer security settings

Thin client computer security settings

Thin client computers are designed to have a small security-attack footprint and to require
minimal security updates.
Further thin client security can be obtained by configuring the following:
Note
These instructions are subject to change by the manufacturer of the thin client computer.
Please refer to the manufacturer's documentation for any updates to setting these
features.

File Based Write Filter (FBWF)

Restrict disk write access to administrators only. This prevents non-administrator accounts
from making any permanent changes to the disk. The flash storage is restored to last good
image after each reboot.
Note
You must be logged on as an administrator to enable this feature.

Run the File Based Write Filter through one of the following methods:
• Executing through the Start → Run command line (FBWFmgr.exe C:)
• Using the desktop icons (a red dot and a green dot).
• Double-clicking the File Based Write Filter icon in the Administrator system tray
Important
Failure to restrict disk write access results in performance degradation to an unacceptable
level for online production control.

USB Port Lockdown

This is set during the installation of DeltaV Remote Desktop Connection (DRDC) on the
thin client computer. Locking the USB port disables USB storage on all USB ports while still
maintaining USB input/output (I/O). USB I/O must be available for keyboard, mouse, and
USB Ethernet adapters.

Related information
Thin client redundant network
Configure the thin client network redundancy

Configure the thin client network redundancy

Thin client network redundancy is achieved by installing the Thin Client Network
Redundancy service and running the Thin Client Network Redundancy Setup utility on

112
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

both ends of the redundant thin client network. You must be logged in as an administrator
to run this utility on either the DeltaV virtual machine or the thin client.
For the thin clients, the Thin Client Network Redundancy Setup utility is located under
Start → DeltaV Virtual Studio → Thin Client Network Redundancy Setup.

Note
When installing on a DeltaV virtual machine, run the utility after the DeltaV software is
installed.

1. Launch the Thin Client Network Redundancy Setup utility.

a. Select the virtual machine from the list in DeltaV Virtual Studio.
b. Connect to the virtual machine (log on as an administrator).
c. Start File Explorer and browse to C:\EmersonVirtualization\bin\.
d. Right-click TcpRedundancySetup.exe and select Run as Administrator.

2. Select the two thin client networks from the list to enable redundancy.
3. Click OK to configure the redundancy between the two selected networks.
This starts (or restarts) the service.
4. Click Close to close the dialog.
Subsequently running the Thin Client Network Redundancy Setup utility will display
the current settings of the service.

Related information
Installing the DeltaV Remote Desktop Connection (DRDC)
Thin client redundant network
Thin client computer security settings

3.25.7 Set up a thick client computer

The thick client computer is any computer that supports the installation of the DeltaV
Remote Desktop Connection and has one of the supported DeltaV Remote Desktop
Connection operating systems.
The thick client can be used to connect to a virtual machine using the thin client network.
Alternately, a thick client can use the host domain network to connect to the console
session of a virtual machine. For more information, refer to the document section Host
user setup for Connect to console option.
Select ONE method of connecting to the virtual machines (due to how the network cards
must be configured). You should not span both networks from one thick client.
Important
All concerns and mitigations regarding the thick client's security (access to the computer,
limiting the USB ports, firewalls for any connection to other networks, and so on) are solely
your responsibility.

This procedure prepares the thick client computer. It assumes the operating system has
been installed and configured for your environment.

113
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Important
All instructions here require you to be an administrator on the computer.

1. Plug in the monitors and power them on.

Note
On many computers, the order in which you connect the monitors determines the
monitor number. Monitor number is important to DeltaV Operate with multiple
monitor systems. If you are not using this computer to run DeltaV Operate, monitor
order might not be important.

2. Turn on the thick client computer and log on as an administrator.

3. Set the following properties for the computer:
For specific information about how to set these properties, refer to the
manufacturer's documentation.
• Make it a member of the host's domain.
• Set the computer time.
• If using the computer for an operator station, set the power options to Never
Sleep or turn off display.

4. If using the computer for an operator station, arrange the monitors to physically
match the DeltaV multiple monitor layout (1x2, 2x2, 1x4).
5. Set the screen resolution, color depth, and refresh rate by monitor.
a) Right-click the desktop background.
b) Select Screen resolution.
The following settings apply only if using the computer as an operator
station.
• Set screen resolution on square monitors to 1024×768 or 1280×1024. For
wide-screen monitors, select 1680×1050. All screens in a multiple
monitor layout must use the same display resolution.
Note
Using a display resolution other than the supported resolutions with a
display created from the DeltaV Operate templates is not supported.
DeltaV Operate opens the display, but the resolution differences cause
picture distortion. All standard DeltaV Operate graphics are created from
the DeltaV Operate templates.

• Set the orientation.

• Except for monitor 1, select Extend these displays for the Multiple
displays option.

Note
If you change the screen resolution, it may be necessary to reset the color
depth setting after.

c) Click the Advanced settings link.

114
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

d) Select the Monitor tab.

• Set the refresh rate according to the type of monitor used.
• Set colors to the supported color depth for the version of DeltaV.

e) Click OK.
f) Click OK again.
g) Repeat the screen resolution, color depth, and refresh rate for each monitor.

6. Configure the IPv4 properties of the computer's network card.

If connecting to the host domain network, set the IP address and DNS appropriate
for that network.
The following options are required for all connections to the thin client network.
Configure two network cards when using redundant thin client networks.
• Static IP address and Subnet mask that matches the host's thin client network
• Blank DNS addresses (NetBIOS is used instead.)
• NetBIOS setting enabled
a. Click Advanced.
b. On the WINS tab, select NetBIOS as the default. (Or, select Enable
NetBIOS over TCP/IP.)

Important
NetBIOS must be enabled on the thin client network cards. This allows DeltaV
Remote Desktop Connection to access the virtual machines by name, and not IP
address. This is especially important for redundant thin client networks.

7. Connect the network cables and verify the network is communicating by pinging a
running machine on the same network.
8. Install DeltaV Remote Desktop Connection on the computer.
9. Reboot the computer.

3.25.8 Connect to the virtual DeltaV Application Station

In order to connect to a virtual DeltaV Application Station, use the Connect to Console
option from DeltaV Remote Desktop Connection (DRDC).
Connecting to the virtual machine using this option is the same as being in front of a
physical computer's console. Once connected, you must log on to the DeltaV system as a
DeltaV user.

3.25.9 Host user setup for Connect to console option

It is important that you configure the users on the host correctly so that you can connect
to either the virtual machine desktop or the host desktop. For specific instructions on
adding a user to a Windows group, please refer to the Windows help for the operating
system you are using.

115
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

To the virtual machine's desktop

In order to use the Connect to console option when connecting to the virtual machine
desktop, the user credentials entered from the DeltaV Remote Desktop Connection
(DRDC) computer must belong to the host ConnectToConsole group, with the following
conditions:
• When the hosts are in a domain and the DRDC client is in the same domain, the user
account entered in the connection dialog is a member of the host domain
\ConnectToConsole group.
• If the hosts are in one domain and the DRDC client is in another domain, a two-way
trust between the domains should exist and the user account entered in the
connection dialog is a member of the host domain\ConnectToConsole group.

To the host desktop

In order to use the Connect to console option when connecting to the host desktop, the
user who is logged on to the DeltaV Remote Desktop Connection (DRDC) computer must
belong to the host Remote Desktop Users group.

Note
• Remote access on the host must be enabled.
• The DRDC computer is running a supported operating system.

In order for the user logged on to the DRDC computer to be made a member of the host
computer Remote Desktop Users group, at least one of the following must be true:
• The host and the DRDC computers are in the same domain.
• The host is in a domain and the DRDC computers are in workgroups.

Requirements for Connect to Console from a client in a

workgroup to a host in a domain
Remote management must be enabled on both the host side and the client side.
On the host server, run the following command in PowerShell:

Enable-PSRemoting

Enable-WSManCredSSP -Role server

Run the following command in PowerShell to verify the host is properly set up:

Get-WSManCredSSP

Run the following command from the command line on the host:

Winrm quickconfig

116
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

On the client machine, run the following commands in PowerShell:

Enable-PSRemoting

$servers = "host1", "host2", "host3"

Enable-WSManCredSSP -Role "Client" -DelegateComputer $servers

Run the following command in PowerShell to verify the client is properly set up:

Get-WSManCredSSP

Run the following command from the command line on the client:

Winrm quickconfig

To set trusted hosts, run the procedure in topic Set trusted hosts for Connect to Console.
Then return here.

Run the following command in PowerShell to verify the host is in the trusted host list:

winrm get winrm/config/client

The local group policy of the client must allow delegating fresh credentials.
1. In DeltaV Remote Desktop Connection, select Computer Configuration →
Administrative Templates → System → Credentials Delegation.
2. Make sure the Allow delegating fresh credentials check box is selected.
3. Click Enable and add every required host to the list (wsman/host).
Refer to the following figure for an example of adding host1.

117
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Using impersonation
Using impersonation can work for workgroup-to-domain and workgroup-to-workgroup
applications. However, impersonation requires administrative privileges on the host and
therefore does not follow the recommended principle of least privilege.
• You can impersonate a local user on the target VM host for Connect to Console
authentication. In this case, the local user on the target VM host must be a member of
the local Administrators group on that host.
• You can impersonate a user in the cluster domain containing the target VM host for
Connect to Console authentication. In this case, the cluster domain user must be a
member of the local Administrators group on the target VM host.
• You can impersonate the local user on the remote client for Connect to Console
authentication. In this case, you must
1. Create a local user with the same name and password on the target VM host.
2. Add that impersonated user to the local Administrators group on the host.
Doing this enables the connection to work without having to set a different user.
Be careful when configuring a thin client with an impersonated user. Most Dell/Wyse thin
clients have only two built-in Windows accounts: Admin for configuring the unit and User
for long-term operation.
Important
The Windows user on the thin client is independent of the DeltaV user security of the
target VM.

For a workgroup client connecting to a host in a domain, refer to Add a domain user to a
local group for impersonation for information about adding a domain user to the local
Administrators group.

118
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Network connectivity
A Connect to Console connection to a target VM is actually a connection to the host of that
VM. A network connection between the remote client and the target VM is not required,
but the host must share a network with the remote client. In a DeltaV clustered Hyper-V
virtualization environment, Emerson recommends connecting the remote client to the
Cluster Management Network for Connect to Console purposes, because the host will
already have Cluster Management Network IPs assigned.

IP addresses
Emerson recommends using static IP addresses when configuring network interface IP
addresses on the remote client. Disable IPv6 on all network interfaces involved in the
Connect to Console connection. Set all interface metrics to Automatic on all remote client
devices.

Name resolution
NetBIOS is sufficient for name resolution. The Preferred and Alternate DNS Servers may be
left blank in the remote client's IPv4 network configuration.

Network configuration
Primary and secondary networks may be configured between the remote client and the
target VM's host, but only one will be used for an active Connect to Console session. There
will be no automatic network switchover if the active network becomes disconnected.
When network configuration is complete, ensure that it is possible to ping the target VM's
host by IP on each network from the remote client, and again by name.
Note
Make sure the hosts and the networks use the same subnet. Otherwise, the firewall in the
host will reject the Connect to Console connection and you will need to create a special
firewall rule.

Client is in a workgroup and host is in a domain

1. Install the latest version of DVS Host Setup on the target host(s).
2. Create a non-administrative user in the host domain. Refer to Create a domain user
for detailed instructions.
3. Add the non-administrative user to the Connect to Console group. Refer to Add a
domain user to the Connect to Console group for detailed instructions.
4. Install DeltaV Remote Desktop Connection on the client. When prompted to select
DRDC Installation Options, select the Add hosts to trusted host list and enable
delegation (for thick clients only) check box.

119
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

5. Click OK.
The Specify hosts for Connect to Console dialog appears.
6. On the Domain Hosts tab, enter the names of the hosts that this client will connect
to, and click OK. You do not need to enter a fully qualified domain name. You do
not need to enter the host names on the Workgroup Hosts tab.

120
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Client and host are in the same domain

1. Install the latest version of DVS Host Setup on the target host(s).
2. Create a non-administrative user. Refer to Create a domain user for detailed
instructions.
3. Add the non-administrative user to the Connect to Console group. Refer to Add a
domain user to the Connect to Console group for detailed instructions.
4. Install the latest version of DeltaV Remote Desktop Connection on the client. When
prompted to select DRDC installation options, ensure Add hosts to trusted host
list and enable delegation (for thick clients only) is disabled.
5. Ensure host setup is updated for all required hosts.

Set trusted hosts for Connect to Console

The Set Trusted Hosts for Connect to Console utility enables you to set up the list of
trusted hosts after you install DRDC.
1. Click Start → DeltaV Virtual Studio → Set Trusted Hosts for Connect to Console
The application displays the Domain Hosts tab.

121
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

2. Enter the names of the domain hosts to which this client will connect.
3. If there are any workgroup hosts, click the Workgroup Hosts tab.

4. Enter the names of the workgroup hosts to which this client will connect.
5. Click OK.

Create a domain user

1. Log onto the domain controller as an administrator.
2. Launch Active Directory Users and Computers. You can launch it from the Windows
Start menu or by running dsa.msc from the command line.
3. Right-click the Users folder in the configuration tree and select New → User.
4. Complete all the fields on the dialog that appears.
5. When the fields are completed, click Next until the summary page appears.
6. Click Finish to create the user.

Related information
Create a domain-level account for DVS
Add a domain user to the Connect to Console group
Add a domain user to a local group for impersonation

Add a domain user to the Connect to Console group

1. Log onto the domain controller as an administrator.
2. Launch Active Directory Users and Computers. You can launch it from the Windows
Start menu or by running dsa.msc from the command line or from the Run
command.
3. Select the Users folder in the configuration tree and find the user you want to add in
the right-hand pane.

122
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

4. Right-click the user name and select Add to a group.

5. Add the user to the Connect to Console group. The following figure shows the user
Operator added to the group.

123
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Related information
Create a domain user

Add a domain user to a local group for impersonation

Using the UI
1. On the cluster domain controller, run mmc from the command line.
2. On the dialog that appears, select File → Add/Remove Snap-in.
3. Select Computer Management in the list on the left, and click Add.
4. When prompted, click Another Computer and enter the name of the host server for
the target VM.
5. Click Finish and then click OK. Find the lists of Local Users and Groups in the tree on
the left-hand side of the MMC dialog.
6. Add the user to the local Administrators group on the host as shown in the
following figure.

Using the command line

If you have access to a console session on the bare-metal host server, you can add a
domain user to a local group using the command line. The following figure shows the
syntax for adding the user ctcuser to the local Administrators group in the pedvs331
domain.

124
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Related information
Create a domain user

3.25.10 Using Connect to Console

1. Run DeltaV Remote Desktop Connection.
2. Select Connect to Console and click Connect.
3. Click VM Connect to open a Virtual Machine Connection window.
If you are unsure of the name of the host where the target VM is located, you can
use Hyper-V Manager or the DVS client to investigate.

4. On the Virtual Machine Connection dialog, select Connect as another user and
click Set User.

5. On the Windows Security dialog, enter the credentials of the domain user (a non-
administrative user who is a member of the Connect to Console group). If the host
is in a workgroup, you must enter the computer name, followed by a backslash,
followed by the user name. In the following example of a workgroup host, the
computer name is td and the user name is Operator.

125
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note that the Remember me check box does not work.

6. Wait a few seconds for the warning to clear and for DeltaV Remote Desktop
Connection to populate the list of available VMs.

Change the DeltaV Virtual Studio service account

(VirtualizationAdmin) password
Use this procedure to change the password for the DeltaV Virtual Studio service account
(named VirtualizationAdmin) on workgroup-based systems. Domain-based systems use a
different account.
The DeltaV Virtual Studio (DVS) service is used in communications between hosts, and
between the DVS computers and the hosts. It runs on the computer where the system
identifier is attached. The DVS service Log on as account is the VirtualizationAdmin
account when the hosts are in a workgroup. Domain-based hosts use a different account.
The DVS application, or client, is the user interface for managing virtual machines and
hosts. It also uses the VirtualizationAdmin account when in a workgroup-based system.
Important
When changing the VirtualizationAdmin user account password, you must make sure the
password is the same on all host computers that the service manages, and o all DVS
computers connecting to those hosts.

Log in to the computers that have the VirtualizationAdmin user account with a minimum
of local administrator privileges.
1. On all hosts, all host domain controllers (if applicable), and on all computers
running the DVS application (the user interface for managing the hosts and virtual
machines), use the DVS Server Password utility to modify the account password for
the VirtualizationAdmin account.

126
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Note
You must log in to the computer as an administrator-level user who has the
privileges to modify local user accounts, and, in the case of a domain, domain
accounts.

a) Select the WinKey on the keyboard and, from the Start menu, select DeltaV
Virtualization → Tools → DVS Server Password.
The following dialog is displayed.

b) Enter the new password in the Password field.

c) Enter the same password in the Confirm Password field.
d) Click OK.
e) When prompted to confirm resetting the password, click Yes.

2. Verify communication by attempting to connect to each host using DeltaV Virtual

Studio.

User Access Control and running the DeltaV virtualization

applications
User Access Control (UAC) and its Admin Approval Mode are security features in Windows
operating systems. When UAC is enabled, local administrator accounts run as standard
user accounts for some actions (the executing of a program, for example), effectively
disabling the administrative privileges.
This Windows security feature has a negative impact on the running of DeltaV
Virtualization executables, such as DeltaV Virtual Studio or DeltaV Remote Desktop
Connection.
Important
Other security features, such as group policies, can also affect the way the DeltaV
Virtualization applications run. Before changing any security-related feature or policy,
check with your system administrator.

To disable UAC, you can do one of the following:

127
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Note
Other valid methods may also exist. Consult with your system administrator for the
appropriate method on your system.
You must be logged on to the computer as a member of the local administrators group to
perform any of these tasks.

• Temporarily (one time only) run the application in elevated mode

This method sets the elevated mode for only the user who is currently logged in.
1. Right click the application name (found either in the Start menu, as a tile on the
Start page, or as an icon on the desktop).
2. Select Run as Administrator.
• Set the application to always run in the elevated mode
This permanently sets the Run as administrator option for this application.
1. Browse to the EXE file name.
2. Right-click and select Properties...
3. Select the Compatibility tab.
4. Click Change settings for all users.
5. Select the Privilege Level to Run this program as an administrator.
• Turn off UAC completely
This turns off the Windows User Access Control security feature on this computer.
Important
Please consult your Windows operating system help for complete instructions on how
to perform this. Consult with your system administrator before turning off UAC
completely.

1. Open the Windows Control Panel.

2. In Control Panel, open User Accounts.
3. In the User Accounts window, click User Accounts.
4. In the User Accounts tasks window, click either Turn User Account Control on
or off, or Change User Account Control settings.
5. Select the lowest setting (No or Never notify).

Note
You must restart the computer for these changes to take effect.

Configure a DeltaV node to run DeltaV Virtual Studio or

DeltaV Remote Desktop Connection
In order for a DeltaV node to run either DeltaV Virtual Studio or the DeltaV Remote
Desktop Connection software, the Windows Credential Manager service must be enabled.
The DeltaV Workstation Configuration process disables this service.
1. Open the Start menu.

128
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

2. In the Search programs and files field, enter Services.msc.

3. Open Services.msc.
4. Right-click Credential Manager and select Properties.
5. Open the Startup type drop-down list and select Automatic.
6. Click OK.
7. Install DeltaV Virtual Studio or DeltaV Remote Desktop Connection on this node.

3.25.11 DeltaV virtual machine settings

The DeltaV virtual machine is independent of the host machine. Because of this, updates
to the host machine are not propagated to the virtual machines. You must treat the virtual
machine as though it is a physical computer.
When setting up your DeltaV virtual machine, you must verify that all the settings on the
virtual machine are correct, for example, date and time and time zone. The virtual
machine templates were created in the Central Time zone of the United States of America.
The time and time zone where the virtual machines are sited may be different.
Other settings should also be verified, such as language, region, keyboard, and so on.
To connect to the DeltaV virtual machine (that is running a Windows Server operating
system) using the DeltaV Remote Desktop Connection (without the Connect to console
option), you must enable Terminal Services on the virtual machine. To do this, connect to
the virtual machine's operating system desktop and open the Services window (usually
found under either Control Panel or Computer Management, depending on the virtual
machine's operating system).

Related information
About the DeltaV Virtual Studio client

3.25.12 Add networks to the virtual DeltaV system manually

The default networks and network cards that come with your host computer and that exist
on the DeltaV templates are based on the most-used DeltaV network configurations.
However, you can reconfigure any unused network cards to fit your network
configuration. For example, to create a DeltaV Inter-Zone Server (IZS) network, you can
either use one of the default Remote networks (if not already used); or, create a new
network and new NIC on the virtual machine and map the new NIC to the new virtual
network.
Note
Your host must be able to support all the network configurations for all the virtual
machines it is hosting. Therefore, you may need to add additional network cards to the
host to support more networks.

1. Configure a physical NIC on the host to be used by this new network.

Note
Refer to the Microsoft Windows Server 2022 installation and setup instructions for
information on configuring the NIC.

129
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

2. Create the required virtual network on the host.

a) Run DeltaV Virtual Studio.
b) Select the host.
c) Click Edit Virtual Networks.
The Edit Virtual Networks dialog is displayed.
d) Click Add Virtual Network.
e) Select the network card from the list in the Physical Network Card column.
Selecting <None> creates an internal network that does not use a physical
network card.
You can scroll to the right to see the network card's Device Name, MAC
address, and GUID. These fields are useful when determining the network
adapters on the virtual machine.
Important
Do not select a network card that is already in use. For example, do not select
the iSCSI or host domain/cluster networks. Doing so will reconfigure the NIC
on the host for use by the virtual machine.

When the Device Name column shows Internal, the network switch is used
only as an internal network between the virtual machines on this host.
The Connection Status column shows the connection status of the selected
network card.

f) Enter a name for the Virtual Network Switch in that column.

g) For the Connect Host option, configure as follows.
• Checked - allows the host to be connected to the virtual machines on this
virtual network.
• Unchecked - prevents the host from connecting to the virtual machines
on this virtual network.
Note
Leave this box unchecked for the virtual switch used for any DeltaV-specific
networks (for example, the ACN, the batch Direct Link, or the Inter-zone
networks).

3. Create the required NIC on the virtual machine.

a) From DeltaV Virtual Studio, shut down the virtual machine.
b) Connect to the virtual machine: double-click the virtual machine name in the
left pane (the By Host or By Group pane).
c) Select File → Settings... from the Virtual Machine Connections window.
d) Select Add Hardware and Network Adapter from the Settings window.
e) Click Add.

130
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

f) Connect the network adapter to the new virtual network (configured on the
host).
g) Click OK.
h) From DeltaV Virtual Studio, start the virtual machine.
i) Connect to the virtual machine: double-click the virtual machine name in the
left panel (the By Host or By Group panel).
j) Log in to the virtual machine.
Note
You can use the Ctrl-Alt-Delete button

( ) from the toolbar of

the Virtual Machine Connection window, which is only available when that
window is not full-screen. Or, you can use the Ctrl-Alt-End key sequence.

k) Select File → Settings... from the Virtual Machine Connections window.

l) Select the network adapter just created and note its MAC address.
m) Open the Network Connections dialog.
n) Identify the NICs on the virtual machine.
Tip
Use the NIC MAC address displayed in the virtual machine's modify dialog in
DeltaV Virtual Studio to assign the NICs correctly.

a) Right-click and select Rename.

Name the virtual machine's network card in a way that allows you to identify
the network to which it is connected.

4. If you are adding a DeltaV network, run DeltaV Workstation Configuration on the
virtual machine and supply the new DevData.cfg file that was created when you
configured this workstation in DeltaV Explorer.
Note
The thin client network (for operating using a virtual DeltaV Operator Station) is not
a DeltaV network and does not require running DeltaV Workstation Configuration.

5. If you are not adding a DeltaV network, set the IP address according to that
network's specification.

3.25.13 Setting up the virtual ProfessionalPLUS workstation type

131
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

This procedure sets the workstation type on the virtual machine to ProfessionalPLUS. Only
use this procedure on a virtual machine if all the following apply:
• The machine is a ProfessionalPLUS.
• It was migrated from a previous release.
• In that previous release, the workstation type was not set.
DeltaV Virtual Studio recognizes the virtual DeltaV workstation type based on the
template's virtual machine settings. This is important for the virtual ProfessionalPLUS
because DeltaV Virtual Studio will read the database mode and display that mode, if it
knows the virtual machine is a ProfessionalPLUS workstation. The workstation type is set
when creating a virtual machine from a template (you are prompted when using an
operating system only template).
1. In DeltaV Virtual Studio, connect to the virtual machine's desktop as an
administrator. You can double-click the virtual machine name in the hierarchy, or
select the virtual machine and click Connect.
2. In the virtual machine window, select File → Settings.
This menu is available when the virtual machine connect window is NOT at full
screen.

3. Scroll to the Management section in the hierarchy.

4. Click Name.
5. In the right-side pane, edit the notes on the WorkstationType line as follows (the
entry is case-sensitive):

WorkstationType:ProfessionalPLUS

Important
Use care when editing this line. Do not add empty lines or remove line breaks. You
are editing the notes of the virtual machine in an area that is not normally modified
manually.

Note
The virtual machine's workstation type is only read by DeltaV Virtual Studio when
importing or creating the virtual machine.

6. Click OK.
7. Disconnect from the virtual machine.
8. To refresh DeltaV Virtual Studio for an existing virtual ProfessionalPLUS workstation
after editing the workstation type, do the following:
a) Remove the host that contains the virtual ProfessionalPLUS. (Refer to the
DeltaV Virtual Studio online help, HCIEmersonVirtualMachineManager.chm.)
b) Wait for DeltaV Virtual Studio to refresh (a few minutes might be required).
c) Add the host again. (Refer to the topic Initialize a host.)

132
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

3.25.14 Configure DCOM on the DeltaV system for Remote

Logoff
The following steps show how to configure the DCOM settings on your virtual machine so
that a user attempting to connect to a DeltaV workstation that already has an active
Remote Desktop connection can request the currently-connected user be logged off.
Without these settings, the user attempting to connect is denied access to the DeltaV
workstation.
When you connect to a virtual DeltaV machine using DeltaV Remote Desktop Connection
(DRDC) with the Remote Desktop option, DRDC checks to see if there is already a user
logged on. Only one user may be logged on at a time; therefore, DRDC allows the user
who is attempting access to do one of the following:
• Ask the user currently logged on to log off
• Force the user currently logged on to log off
• Cancel the connection attempt
Note
The DRDC can only request the log off, or force the log off, when the requesting user has
the same or higher privileges. The user attempting to log in can never log out another
user who has higher privileges (for example, an operator cannot log out an administrator
unless the operator is also an administrator).

1. Connect to the virtual machine and open the Start menu.

2. Enter the command Dcomcnfg.exe in the Search programs and files field.
3. Click the Dcomcnfg.exe result.
4. In the Component Services window, click Console Root, expand Component
Services → Computers, and select My Computer.
5. In the Actions pane, click More Actions and select Properties from the menu.
6. In the My Computer Properties dialog, select the COM Security tab.
7. In the Access Permissions section, click Edit Limits.
8. Click Add and enter the name of the group you want to add (for example,
Operators).
Add the local group if DeltaV is in a workgroup. Add both the local and domain
groups if DeltaV is in a domain. Add the Everyone group if there are access
problems with the other groups.
Note
The local DeltaV user group is configured by default with the correct DCOM
privileges. Domain groups or any new local group you create must be added
manually.

9. Click OK on the Select Users or Groups dialog.

10. On the Access Permissions dialog, under the Permissions for user group section,
check Allow for the Remote Access row.
11. Click OK.

133
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

12. In the My Computer Properties dialog box, on the COM Security tab, in the Launch
and Activation Permissions section, click Edit Limits.
13. Click Add and enter the name of the group you want to add (for example,
Operators).
Add the local group if DeltaV is in a workgroup. Add both the local and domain
groups if DeltaV is in a domain. Add the Everyone group if there are access
problems with the other groups.
Note
The local DeltaV user group is configured by default with the correct DCOM
privileges. Domain groups or any new local group you create must be added
manually.

14. Click OK on the Select Users or Groups dialog.

15. On the Launch and Activation Permission dialog, under the Permissions for user
group section, check Allow for the Remote Launch and Remote Activation rows.
16. Click OK on all open windows.
17. Close the Component Services window.
18. Exit the virtual machine connection.
19. Reconnect to the virtual machine using DeltaV Remote Desktop Connection
(DRDC) in the non-console mode (as an operator would).

3.25.15 Enable the DeltaV Screen Saver

When connecting to a virtual DeltaV operator station using DeltaV Remote Desktop
Connection, the DeltaVScreenSaver task requires a Windows scheduled task on the
virtual machine. This task exists on the DeltaV-installed virtual workstation machines and
needs to be enabled. The task applies to any user who is logged on to the virtual DeltaV
workstation and is a member of the DeltaV user group.
For any virtual DeltaV machine created from an operating system only template, you will
need to create the scheduled task. Refer to one of the virtual DeltaV machines created
from a DeltaV-installed template for the example.
The DeltaVScreenSaver task is only required for workstation operating system virtual
machines.
Note
You must log onto the virtual DeltaV machine as a local administrator.

1. Connect to the virtual DeltaV machine's desktop and log in as an administrator.

2. Go to Start → All Programs → Accessories → System Tools and select Task
Scheduler.
3. Select Task Scheduler Library in the hierarchy.
4. Select the DeltaVScreenSaver task from the list in the middle pane.
5. Right-click and select Enable from the context menu.
6. Close Task Scheduler.

134
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

3.25.16 Installing AMS Device Manager on a virtual machine

When installing AMS Device Manager, refer to the documentation accompanying it. There
are special considerations for installing AMS Device Manager in a domain environment.
To install the AMS Device Manager Client SC on a DeltaV node, select the Install AMS
Client option when creating the virtual DeltaV machine from a DeltaV template.
To install the AMS Device Manager Server Plus workstation, you must first start with a
blank operating system template.

3.25.17 Having multiple monitors in a virtual DeltaV system

Multiple-monitor configuration for a virtual DeltaV workstation is supported as shown in
the following table.
Note
These tables refer to DeltaV versions and operating system versions that are not used in an
HCI system. But the HCI system may connect with a previous standalone system that has
machines which do use this software.

# of Monitors DeltaV Versions Virtual Surface Connection Display

Machine's Resolutions
Operating
System
2 (dual head) v13.3.1 Windows 10 Multi-monitor 1024x768
v14.3.1 1280x1024
1680x1050
1920 x 1080
3 v13.3.1 Windows 10 Multi-monitor 1024x768
v14.3.1 1280x1024
1680x1050
1920 x 1080
4 (quad) v13.3.1 Windows 10 Multi-monitor 1024x768
v14.3.1 1280x1024
1680x1050
1920 x 1080

Important
In order to support multiple monitors on a virtual DeltaV workstation where the
connection to the virtual machine uses the span option (as with DeltaV v11.3 and
v11.3.1), DeltaV Operate must be updated with Emerson hotfix 53190 / TFS# 43677.

When the monitor display is set to show one surface (span), the surface acts like one
monitor; that is, maximizing an application window spreads it across all screens.
Note
The maximum resolution when connecting using the span option is 4096 x 2048

135
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

Figure 3-3: Screen arrangements for dual monitors

Figure 3-4: Screen arrangements for 3 and 4 monitors in SPAN mode

Figure 3-5: Screen arrangements for 3 and 4 monitors in MULTI-MONITOR mode

136
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

Related information
Setting up a thin client computer

3.25.18 Configure an additional host domain controller

This procedure is performed on the machine that will be an additional domain controller.
You can use a remote connection to that machine.
Important
Before performing this procedure, you must configure the DNS addressing for host
networks on both domain controllers. Previous configurations may have been lost during
setup so you must verify IP and DNS settings are correct on both domain controllers
before proceeding.

Important
Before performing this procedure, you must temporarily enable remote shell access. Refer
to Enable or disable Remote Shell access.

All the following conditions must be met:

• Static IP addresses configured on this computer match the subnets of the host
computers.
• The computer is named according to all domain/DNS naming conventions.
• The computer is a member of the host domain.
• You are logged into the computer as a domain administrator.
• Unused NICs are disabled.

All domain controllers for the host domain must be at the same operating system version
as the hosts (except during the process of upgrading the hosts). Therefore, on hosts
running Windows Server 2022, the host domain controller must be running Windows
Server 2022. To support the VMs running on the hosts, the functional level of the host
domain must be set to 2016.
Make note of the IP addresses of the NICs that handle the host domain traffic. Those are
the addresses to use when setting up the host NICs' DNS secondary addresses.
If you create this additional domain controller as a virtual machine, it is recommended you
do not replicate the virtual additional domain controller. Instead, if this virtual domain
controller takes over as the first domain controller, you can rectify the problem with the
physical first domain controller and bring it back as quickly as possible. This will ensure
always having two domain controllers for the host network, where one is always physical
and one is virtual.
Note
For multiple cluster systems, all clusters managed by one DVS client should be in the same
domain.
It is recommended that all hosts be in one domain. If not, you must establish two-way
trusts between the domains if replicating or moving virtual machines across the domains.
DNS forwarding may also be necessary to connect to the hosts by name. Consult your
network administrator or Microsoft for specifics on configuring domain-to-domain
communication.

137
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

If the Server Manager displays any error messages, refer to the Windows documentation.

1. Install anti-virus software on the computer with the same settings as for a DeltaV
workstation.
If not possible now, return to this step when it is possible.

2. Set the date and time on the domain controller to correspond to the date and time
at the location where the servers will be deployed.
3. Configure the NIC cards to meet all the following criteria:
• IP addresses are set
• Subnets are set
• DNS references the first domain controller
Important
The first domain controller must be referenced in order to join the domain.

4. Select Server Manager → Add Roles and Features.

5. Click Next.
6. Select Role-based or feature based installation and click Next.
7. Click Select a server from the server pool, select the local server, and click Next.
8. Select the Active Directory Domain Services check box.
9. Click Add Features on the window.
10. Select the DNS Server check box.
11. Click Add Features on the window.
12. Click the expansion icon next to the File and Storage Services check box.
13. Click the expansion icon next to the File and iSCSI Services check box.
14. Select the DFS Replication check box.
15. Click Add Features on the window and click Next.
16. Click Features and select the Failover Clustering check box.
17. Click Add Features on the window, and then click Next.
18. Click Next twice more, then click Install.
19. Wait for the installation to complete, then click Close.
20. In Server Manager, click the Notification flag (this should have a yellow exclamation
mark).
21. Under Post-Deployment Configuration, click the Promote this server to a domain
controller link.
22. In the Active Directory Domain Services Configuration Wizard, select Add a
domain controller to an existing domain and specify the domain name (listed as
the only domain controller by default).
If not logged in as a domain administrator, you must change the current credentials
to perform this operation.
a. Click Change...

138
 Installing DeltaV Virtual Studio on an HCI system
D800142X012 August 2022

b. Provide the domain administrator credentials.

c. Click Next.

23. On the Domain Controller Options page, accept the defaults and provide the
Directory Services Restore Mode password.

Note
Make this password the same password as on the first domain controller.

24. Click Next.

25. On the DNS Options page, click Next.
26. On the Additional Options page, in the Replicate From list, select the host
domain's primary domain controller as the domain controller to replicate from,
then click Next.
27. Click Next on the next two pages (the Paths and Review Options pages).
28. On the Prerequisites Check page, review the warnings (there are always warnings
but none should require action) and verify that the domain controller passed the
check successfully.
29. Click Install.
30. Wait for the installation to complete, then click Close.
The server reboots.
31. Log in as a domain administrator.
32. On the first domain controller, check for the second domain controller under Active
Directory's Users and Computers → Domain Controllers.
33. On the second domain controller, configure the NTP settings using the NTP Settings
utility provided on the DeltaV Virtual Studio installation media. For instructions,
refer to Set the NTP time synchronization.
34. Install the drivers and firmware you downloaded from Dell earlier. Make sure the
installed version is the same as that listed for the model of server in KBA
NK-1700-0089 (or newer if the listed version was unavailable).
35. Install the Microsoft updates that you had copied to a DVD when you downloaded
updates. The appropriate file to run on the domain controllers should be named
something like windows10.0…_MONTHYEAR.msu, where MONTHYEAR is the month
followed by the year of the patch release.
36. Keep the domain controllers updated with the Microsoft updates listed in Emerson
KBA AK-1200-0033.
Important
Failure to apply patches listed in the KBA can lead to spontaneous reboots of the
domain controllers, or other serious impact to machine functionality.

139
Installing DeltaV Virtual Studio on an HCI system
August 2022 D800142X012

140
 Maintaining an HCI DeltaV Virtual Studio system
D800142X012 August 2022

4 Maintaining an HCI DeltaV Virtual

Studio system
4.1 Maintenance overview
For most repairs in an HCI environment, refer to the manufacturer's instructions, or follow
the guidance of your technical support representative. This guide covers the actions
necessary to integrate replaced components back into the HCI environment.

4.2 Set the NTP time synchronization

Important
The date and time on the system must match the date and time at the location where the
servers will be deployed.

Use this procedure to set the properties for master and backup time servers, and for
listeners. All the nodes in your system must be synchronized. This means all the thin
clients, DeltaV nodes (virtual and physical), hosts, and host domain controllers must be in
sync with each other. So you must configure all the machines in your system in one of
these roles.
You have the option to run the NTP Settings utility during host setup, or during DeltaV
Virtual Studio and DRDC installation. When needed, it can also be run independently of
the installation programs, such as on the host domain controller.
All computers, both physical and virtual, eventually experience time drift. When this
happens, communication between computers fails. NTP keeps machines synchronized
within the acceptable parameters to not affect communications.
The domain controller is normally the master time server for the domain. Therefore, this
utility must be run on your host domain controller (DeltaV nodes in a domain have this
done for them by the DeltaV install).
Since the hosts set the initial time on any virtual machine it is hosting, and, if there are
multiple hosts that become out of sync, the virtual machines will become out of sync with
each other and any physical machines to which the virtual machines communicate (for
example, thin clients, other physical DeltaV nodes, a physical PI historian node, and so on).
Important
Running the NTP Settings utility enables NTP time and therefore disables Windows Time. If
you do not configure the NTP settings on a node (meaning the host, the DeltaV Virtual
Studio computer, and the thin clients), that node will use its own time, which will not stay
in sync with other nodes due to normal time drift. NTP settings may be left undone in a
test environment where precise time is not required.

1. Run the NTP Settings utility one of the following ways:

• Click Start → DeltaV Virtual Studio → NTP Settings.

141
Maintaining an HCI DeltaV Virtual Studio system
August 2022 D800142X012

• From the installation media, go to the \autorun folder and run ntpsettings.exe
in an elevated mode (right-click and select Run as administrator).

2. From the NTP Settings dialog, select the Role for the computer you are configuring.

Note
Virtual machines are not supported for use as master or backup time servers.

• Role - Select the role you are configuring.

Listener This node obtains the time from the master or backup time
server. Use this for all nodes other than any designated as a
master or backup time server.
Master Time This node supplies time to all other nodes.
Server
Backup Time This node supplies time in the event the master is not
Server available.

3. Click Next.
4. Based on the role selected, enter the appropriate IP address for the time server
machine.
Important
Do not use the automatic private IP address of 169.x.x.x (where x= a number).
Virtual machines are not supported for use as master or backup time servers.

Role Request time from Notes

(IP Address/Subnet Mask)
Listener Enter the addresses of the You are defining IP addresses
ports on the master and the computer can use for
backup time servers from time (only the master is
which this computer will poll required). The listener does
the time. not supply time to any other
node.
Master Time Server Not required. The master is the time
source. All other computers
will go to this IP address for
their primary time server.
A GPS time device is
recommended for use in a
domain.
Backup Time Server Enter the address of the port You are defining the IP
on the master time server address where the backup
from which this computer time server goes for its time.
gets its time.

5. Click Next.
6. Based on the role selected, enter the appropriate IP addresses to respond to time
requests.

142
 Maintaining an HCI DeltaV Virtual Studio system
D800142X012 August 2022

Important
Do not use the automatic private IP address of 169.x.x.x (where x= a number).
Virtual machines are not supported for use as master or backup time servers.

Role Respond to time requests Notes

on
(IP Address/Subnet Mask)
Listener Not applicable. The Listener role does not
respond to time requests.
Master Time Server Enter the addresses of the You are defining the IP
ports on this computer (the address from which all other
master time server) on which computers will poll the time.
other computers will request You must define at least one
the time. IP address.
Backup Time Server Enter the addresses of the You are defining the IP
ports on this computer (the address from which all other
backup time server) on computers will poll the time
which other computers will in the event that the master
request the time in the event time server is unreachable.
that the master time server is You must define at least one
unavailable. IP address.

7. Click Next.
8. Verify the entries are correct. If not, click Back and correct the addresses.
9. When the entries are verified as correct, click Apply.
If all the fields are filled in appropriately, the configuration is set. Otherwise, a
message prompts you to complete the required fields.
10. Click OK on the confirmation dialog.
11. If you are replacing a node and have to establish NTP on the replacement, you can
stop now. If you are setting up a new HCI system, repeat this procedure on all hosts,
domain controllers, DeltaV nodes, and thin clients.

Related information
Installing the DeltaV Remote Desktop Connection (DRDC)

4.3 Replace the witness machine

1. If possible (if the witness is still responding to console input), record the machine
name and NIC settings.
2. Record the network cable connections.
3. Connect the new witness box to power and connect the console.
4. Log in to the new witness and change the machine name and NIC settings to match
those from the old witness.
5. Connect the network cables and ping other nodes in the system - make sure
communications are good.

143
Maintaining an HCI DeltaV Virtual Studio system
August 2022 D800142X012

6. Add the new witness to the domain - refer to the topic Join a host to a domain.
7. Synchronize the time settings on the new witness - refer to the topic Set the NTP
time synchronization.
8. Use Autorun to configure the witness node - refer to the topic Set up the witness
machine.

4.4 Replace an HCI switch

This applies to both S-Series switches and N-Series switches.
1. Record any custom settings for the switch uplink ports.
2. Record the port connections on the switch that will be replaced.
3. Disconnect all network cables, power down the switch, and remove the switch.
4. Insert the new switch in the chassis.
5. Power up the new switch and reconnect the network cables, using the same ports
as the old switch.
6. Configure the new switch, depending on the switch type. For information on doing
this. refer to these other topics:
• Configure the S-Series switch
• Configure the N-Series switch

7. If necessary, reapply the custom settings for the uplink ports.

4.5 Validate a cluster

The cluster is validated automatically during the creation process. You should not need to
run this procedure manually unless you need to troubleshoot something.
Validating can help you find problems you otherwise may not see.
1. From the Start menu on the domain controller, open Failover Cluster Manager.
2. In the top left of the Failover Cluster Manager window, right-click on Failover
Cluster Manager and select Connect To Cluster…
3. Enter the name of your cluster in the Cluster Name field and click OK
4. You should now see the cluster listed in the top left corner of the window. Click on
it.
5. In the Actions menu, click on Validate Cluster.
6. On the Before You Begin dialog, click Next.
7. Select Run only tests I select, then click Next.
8. Clear Storage and Storage Spaces Direct, then click Next.
9. Click Next to begin the test.
10. When the summary page appears, click View Report.

144
 Maintaining an HCI DeltaV Virtual Studio system
D800142X012 August 2022

11. A web page will open, showing a Failover Cluster Validation Report. Read it and
check for any warnings or errors.
Note
Some warnings in this report are expected. Some of expected errors include
• QuoroumArbitrationTimeMax value set to 90
• IPV4 address configured as APIPA
• Does not have an adapter usable by the cluster with a default gateway

12. When you finish the report, click Finish.

Related information
Set up a cluster

4.6 Verify Active Directory and DNS health across

the host domain
Use this procedure to verify your host domain is healthy.
When upgrading your hosts and keeping the domain intact, it is vital that overall Active
Directory and DNS configuration is functioning properly before switching from the
primary domain controller to the alternate domain controller.
1. Run Net.exe share on each domain controller and verify it shows that the
NETLOGON AND SYSVOL shares are defined.

C:\ >net share

Share name Resource Remark

------------------------------------------------------------
-------------------
ADMIN$ C:\WINDOWS Remote Admin
IPC$ Remote IPC
C$ C:\ Default share
Databases C:\DeltaV\DVData\Databases DeltaV
Databases
DVData C:\DeltaV\DVData
NETLOGON C:\WINDOWS\SYSVOL\sysvol\ddv-1031.emerson.local
\SCRIPTS
Logon server
share
SYSVOL C:\WINDOWS\SYSVOL\sysvol Logon server
share
The command completed successfully.

C:\ >

2. Run the command Repadmin.exe /showrepl and verify it shows no errors on

any of its Inbound Neighbors. Any failures must be resolved before proceeding with
the upgrade.

145
Maintaining an HCI DeltaV Virtual Studio system
August 2022 D800142X012

3. Run the command DCDiag.exe /a /c and verify it reports no (or no unexpected)

errors.
More specifically, because DeltaV and DeltaV Virtual Studio use NTP instead of the
Windows Time service, the time service related tests (Advertising and Services) will
always fail. Those are the only two tests that will always fail for DeltaV and DeltaV
Virtual Studio implementations. Additionally, the FrsEvent, DFSREvent and
KccEvent test will fail if it finds any Error event in the associated logs. These events
should be scrutinized to see if the actual Error events are an issue or not. All other
test should pass. If they do not, they should be investigated prior to the upgrade of
the hosts and clusters.

4.7 Replace a server NIC

In Dell PowerEdge R740xd servers, you can replace a bad NIC by itself.
It is not necessary to power down the server for this procedure.
1. Note the existing cable connections using the defective NIC, and unplug all those
cables.
2. Remove the screw that secures the NIC, and pull out the NIC.
3. Slide the new NIC into place, and secure it.
4. Reconnect the cables in the same way as before.

4.8 Update server firmware

Server updates are normally controlled by the security policies. You should make sure the
firmware is updated before initializing a host, and you may need to do that manually. You
should make sure all host servers have the most recent firmware.
Server updates can be performed by using the Dell Server Update Utility (SUU).
Important
The utility is operating-system specific, so you must use the version that matches the OS
on your host server.

1. Download the latest updates - refer to the document section Downloads to obtain
before starting.
2. Open a Web browser and go to this URL: https://www.dell.com/support/home/en-
us
3. Enter the tag number or other data to identify your host server in the Search field,
and click Search.
4. Click the Drivers and Downloads tab.
5. Select the correct System Management category and choose the SUU file for your
server.
6. Download that utility and save it on removable media.

146
 Maintaining an HCI DeltaV Virtual Studio system
D800142X012 August 2022

7. Log on to the server that you will update, and attach the media containing the
utility.
8. In the Web browser, go to this URL: https://www.dell.com/support/kbdoc/en-us/
000123359/dell-emc-server-update-utility-suu-guide-and-download
9. Follow the directions on that Web page to use the utility for updating the firmware.
10. Reboot the server.
11. Repeat this procedure on all the other host servers.

4.9 Install Windows operating system with RAID

level verification
The Boot Optimized Server Storage (BOSS) raid controller is supposed to be RAID1. If it is
not, you must run this procedure to change it.
1. Connect to iDRAC and open a virtual console.
2. Click Connect Virtual Media.
3. Under the Map CD/DVD drive heading, click Choose File.
4. Select the install media.
5. Click Map Device.
6. Click Close.
7. In the Boot menu, select the Lifecycle Controller.
8. Confirm your selection.
9. Click the Power menu and select Reset System (warm boot).
10. Confirm the reboot. After the reboot, the Lifecycle Controller restarts automatically.
11. In the Lifecycle Controller, select OS Deployment from the menu list, and click
Deploy OS.
12. On Step 1 of 5, select the Configure RAID First option and click Next. Check the
RAID level.
• If the RAID level is RAID1:
— If you are not re-installing Windows, exit the Lifecycle Controller and reboot
the host server.
— If you are re-installing Windows:
a. Click Back.
b. Click Go Directly to OS Deployment.
c. Proceed to step 17 in this procedure.
• If the RAID level is incorrect, click Next and continue to step 13 in this procedure.

13. Select RAID1 and click Next.

14. Click Select All and then click Next.

147
Maintaining an HCI DeltaV Virtual Studio system
August 2022 D800142X012

15. In the Virtual Disk Name field, enter OS, and then click Next.
16. Click Finish.
17. On Step 2 of 5, make sure the Boot Mode is UEFI.
18. In the Available Operating Systems drop-down list, select Microsoft Windows
Server 2022.
19. Click Next.
20. On Step 3 of 5, select Manual Install and click Next.
21. In the Select Media pull-down list, select EFISECTOR (Virtual CD). A warning dialog
appears.
22. On the dialog, click Yes.
23. On Step 5 of 5, review the settings that you have selected.
• If the settings are correct, click Finish. The system reboots and the operating
system installation begins.
• If the settings are not correct, use the Back button to go back and make the
corrections. Then click Finish.

24. At this point, you will go through the process of installing the operating system.
During this process, make sure you:
• When you are prompted to choose the operating system to install, select
Windows Server 2022 Datacenter (Desktop Experience).
• When you are prompted to select the drive/partition to use, select the choice
that is closes to 450 GB. This will typically be close to the bottom of the list.

25. The system reboots at least one time. After the final reboot, you are prompted to
change the administrator user's password. Click OK.
26. Click OK to the confirmation that the password has been changed. You are logged
on to the machine.
27. Remove the installation media.
28. Return to the DVS installation process at step 2 of the phase Set up a Windows
Server host computer.

4.10 Critical functions

All the information here applies to the way the DeltaV virtualization identifier (access key)
affect operation on both a physical machine and on a VM.
The following features continue to function without the DeltaV Virtual Studio system
identifier and license.
• Move VM
• Start VM

148
 Maintaining an HCI DeltaV Virtual Studio system
D800142X012 August 2022

• Shut down VM
• Turn off VM
Installing the access key allows access to all DVS functionality, listed below.
• Move VMs
• Start all VMs
• Shut down all VMs
• Turn off all VMs
• Add hosts
• Add groups
• Compare virtual switches
• Create VMs
• Delete groups
• Delete VMs
• Detect hosts
• Display virtual networks
• Edit clusters
• Edit collection settings
• Edit VHD
• Edit virtual networks
• Export VMs
• Generate templates
• Import VMs
• Insert Update Setup disk
• Modify groups
• Modify hosts
• Modify VMs
• Open VM Builder
• Remove hosts
• Replicate hosts
• Visualize host

149
Maintaining an HCI DeltaV Virtual Studio system
August 2022 D800142X012

150
 Expanding a DeltaV Virtual Studio v4.3 HCI system
D800142X012 August 2022

5 Expanding a DeltaV Virtual Studio

v4.3 HCI system
5.1 Install a new server
You may need to do this to expand the system with an additional host server.
1. Secure the server in the rack and connect it to power, according to the directions in
the manufacturer's documentation.
2. Make sure the HCI system nodes are connected properly. Check cabling against
diagrams in the document section HCI network architecture.
3. Connect a control keyboard and monitor.
4. Configure RDMA on the server - refer to the topic Configure RDMA.
5. Make sure the host server is set up properly - refer to the topic Set up a Windows
Server host computer.
6. Install Windows Server 2022 on the server according to Microsoft instructions.
Note
Update settings are defined by domain group policy, so you do not need to
manually update the system.

7. Log on to the computer as an administrator.

8. Rename this computer.
This name cannot match any of the DeltaV virtual machine names that you will
create later. Names for servers must conform to the operating system naming
requirements as well as other naming requirements; such as, Microsoft domain
member names, Microsoft DNS naming restrictions, any Active Directory
restrictions if this host will be a part of a larger domain, your corporate naming
restrictions, and so on. It is recommended you keep the name alphanumeric,
without using any special characters.

5.2 Expanding the storage cluster

The process of expanding a cluster involves several distinct actions, and there are two
expansion tracks, as shown in the following table.

Expanding from 2 nodes to 3 nodes Expanding from 3 nodes to 4 nodes

Expand the existing cluster. Expand the existing cluster.
Use Autorun.Hci. Use Autorun.Hci.
Migrate all data from the original Cluster Shared Configure the new CSV. This includes removing
Volume (CSV) to the new CSV. the old CSV.
Use the DeltaV Virtual Studio client. Use Failover Cluster Manager and Server
Manager.

151
Expanding a DeltaV Virtual Studio v4.3 HCI system
August 2022 D800142X012

Expanding from 2 nodes to 3 nodes Expanding from 3 nodes to 4 nodes

Configure the new CSV. This includes removing Expand the new CSV virtual disk and partition.
the old CSV. Use Server Manager and Disk Management.
Use Failover Cluster Manager and Server
Manager.
Expand the new CSV virtual disk and partition. Expand the existing cluster to 4 nodes.
Use Server Manager and Disk Management. Use Autorun.Hci.

Note
From start to finish, the full expansion process may take several hours.

These procedures assume the reader is familiar with using storage clusters and CSVs.

5.2.1 Expand an existing cluster

Run this procedure when you need to add a node to a cluster in the virtualized system. This
will increment the number of clusters by one. It will expand a 2-node cluster to 3 nodes, or
expand a 3-node cluster to 4 nodes. It will not support going directly from 2 nodes to 4
nodes.
Clusters are created for the first time during the DeltaV Virtual Studio installation process.
For information on that, refer to the topic Set up a cluster.
1. Log on to a domain controller as Administrator.
2. Start Autorun.
a. Load the installation media.
b. Start File Explorer and browse to the \Autorun folder on the installation
media.
c. Right-click Autorun.Hci.exe and select Run as Administrator from the
context menu.

3. Select Expand Cluster and click Next Step.

4. Select the cluster you want to change, and click Next Step.
5. Select the host you want to add, and click Next Step.
6. Click Expand Cluster. You will see a success message when the expansion is
complete.
Note
This step may take several hours to complete.

If you expanded from a 2-node cluster to 3 nodes, you must immediately move data into
the new CSV as shown in the topic Migrate data to an expanded cluster. If you are
expanding from 3 nodes to 4, skip that action and proceed to the configuration shown in
the topic Configure the new Cluster Stored Volume.

152
 Expanding a DeltaV Virtual Studio v4.3 HCI system
D800142X012 August 2022

Related information
Migrate data to an expanded cluster
Configure the new Cluster Stored Volume
Expand a new Cluster Shared Volume virtual disk and partition

5.2.2 Migrate data to an expanded cluster

After you expand the storage cluster, you will have two Cluster Shared Volumes (CSVs):
one in use, and a new one which is empty. If you are expanding from 2 nodes to 3 nodes,
you must now migrate all stored data from the existing CSV into the new CSV. If you have
any data stored in the first CSV which is not in a VM, you must manually move that data
into the new CSV.
This action is not required if you are expanding from 3 nodes to 4 nodes.
1. Log in on the server that is running the DeltaV Virtual Studio service (where the
DeltaV Virtualization system identifier is installed).
2. Start the DVS client and select any VM under the clustered hosts.
3. Click Move VM. The Move Virtual Machines dialog opens.
4. In the Move to Host window, select a host. It is recommended you select the
current host.
5. In the Move to Storage window, select the name of the new CSV.
6. Click OK. A new window opens to show information about the move, such as the
move type.
7. Click OK.
8. Repeat steps 3 through 7 for every VM in the old CSV.
Note
Only 2 live/storage migrations can be done at the same time.

9. Use File Explorer to check the old CSV for folders/files that were not included in a
VM. If you find any, manually move them to the new CSV.
At this point, proceed to the action Configure the new Cluster Stored Volume.

Related information
Expand an existing cluster
Configure the new Cluster Stored Volume
Expand a new Cluster Shared Volume virtual disk and partition

5.2.3 Configure the new Cluster Stored Volume

After clearing the previous CSV and ensuring there is no remaining data on the CSV it
should be removed from the cluster shared volumes. This also involves removing the
virtual disk that underlies the previous CSV.

153
Expanding a DeltaV Virtual Studio v4.3 HCI system
August 2022 D800142X012

Be very careful to choose the correct CSV. The name of the CSV will match the path and
the path can be seen within the CSV information in Failover Cluster Manager. Use that
information to ensure the correct CSV is being chosen for these steps.
1. Open Failover Cluster Manager.
2. Right-click the previous, now-empty CSV, and select Remove from Cluster Shared
Volumes
3. Confirm you wish to remove the disk from Cluster Shared Volumes. The disk will
now show as Available Storage instead of a CSV.
4. Record the “Owner Node” of the disk that is now showing as Available Storage.
5. Right-click that same disk again, and select Remove.
6. Confirm you want to remove the disk from Available Storage.
7. Log in as an administrator to the host which was recorded in step 4 as the previous
“Owner Node” of the previous CSV.
8. Open Server Manager and navigate to File and Storage Services → Volumes →
Storage Pools. There should be a Storage Pool in the list called S2D on < Name of
Cluster >.
9. Select that Storage Pool.
Note
In the Virtual Disks section there should be a disk which matches the name of the
previous CSV. This disk will have a warning triangle next to it. If you hover the
pointer over the triangle it will say “Unknown: Detached”.

10. Right-click on the virtual disk and select Delete Virtual Disk.

CAUTION
Be very sure you are deleting the correct disk; this is a destructive action which will
result in all data on that disk being lost.

11. Read and acknowledge the warning prompt.

Related information
Expand an existing cluster
Migrate data to an expanded cluster
Expand a new Cluster Shared Volume virtual disk and partition

5.2.4 Expand a new Cluster Shared Volume virtual disk and

partition
You must expand the new CSV to take advantage of the full capacity available for the
cluster. This is done in two steps. First the virtual disk for the new CSV must be expanded,
and then the partition within the virtual disk is expanded to realize the new storage.

154
 Expanding a DeltaV Virtual Studio v4.3 HCI system
D800142X012 August 2022

These operations are performed on the host which is the owner of the new CSV. This
information can be found in Failover Cluster Manager under Storage → Disks.
1. Log in to the host which is the owner of the new CSV.
2. Open Server Manager and navigate to File and Storage Services → Volumes →
Storage Pools. There should be a Storage Pool in the list called S2D on < Name of
Cluster >.
3. Select that Storage Pool. In the Virtual Disks section there should be a disk which
matches the name of the new CSV.
4. Right-click on that disk and choose Extend Virtual Disk....
5. In the dialog which appears, click Maximum Size and then click OK.

Note
You will see a disk on the host which has the name of the new CSV. There will be
unallocated space at the end of the partition.

6. Open Disk Management.

7. Right-click on the partition which has the name of the new CSV, and select Extend
Volume....
8. Proceed through the wizard which appears, keeping all default values.
The new cluster is now ready to use.

Related information
Expand an existing cluster
Migrate data to an expanded cluster
Configure the new Cluster Stored Volume

5.3 Add a new host to the virtualized system

Before you can make any VMs in DeltaV Virtual Studio (DVS), you must add hosts for the
VMs. In effect, this identifies for the DVS service those hosts that it will manage.
Hosts are usually added to the DVS system during installation; use this procedure if you
need to expand the system by adding another host later.
1. Connect a new server to the network and set it up - refer to the topic Install a new
server.
2. Initialize the host on the new server - refer to the topic Initialize a host.
3. Join the new host server to the domain - refer to the topic Join a host to a domain.
4. Install the DVS client on the new host server - refer to the topic Install DeltaV Virtual
Studio.
5. Run host setup on the new host server - refer to the topic Set up the hosts.
6. Copy the release-specific files from the installation media to the host server - refer
to the topic .

155
Expanding a DeltaV Virtual Studio v4.3 HCI system
August 2022 D800142X012

7. Run host network setup to include the new host server in the network - refer to the
topic Set up host networks.
8. Add the new host server to a cluster - refer to the topic Set up a cluster.
9. Set up virtual networks - refer to the topic Set up virtual networks.
10. Open the DVS client and click Add Hosts.
The Add Hosts dialog opens.

Note
For security reasons, the host names have been blanked.

11. In the Host name field, enter the name of a host, then click Connect.
The names of other hosts in the cluster appear.
12. Select the hosts you want to add, and click OK.

5.4 Transfer FSMO roles from primary controller to

an additional controller
When upgrading the domain, you will switch the domain roles (FMSO roles) from the
primary controller to the additional controller. This preserves the domain, all its roles, OUs,
group policies, and user accounts.
Important
When transferring the roles, do not use "Seize". If the domain controllers are healthy and
communicating properly, there will be no issues in using "Transfer" to move the roles
gracefully.

You must verify that the domain is healthy - refer to the topic Verify Active Directory and
DNS health across the host domain.
1. Log in to the primary domain controller as an administrator, and open a command
prompt window.
2. Run the following command (anywhere there is a ellipsis indicates that output has
been truncated for clarity):

C:\>ntdsutil.exe
ntdsutil.exe: roles
fsmo maintenance: connections
server connections: connect to server
<BACKUP_DOMAIN_CONTROLLER_NAME>

156
 Expanding a DeltaV Virtual Studio v4.3 HCI system
D800142X012 August 2022

Binding to <BACKUP_DOMAIN_CONTROLLER_NAME> ...

Connected to <BACKUP_DOMAIN_CONTROLLER_NAME> using
credentials of locally logged on user.
server connections: quit
fsmo maintenance: transfer pdc
Server "<BACKUP_DOMAIN_CONTROLLER_NAME>" knows about 5 roles
…
fsmo maintenance: transfer schema master
Server "<BACKUP_DOMAIN_CONTROLLER_NAME>" knows about 5 roles
…
fsmo maintenance: transfer naming master
Server "<BACKUP_DOMAIN_CONTROLLER_NAME>" knows about 5 roles
…
fsmo maintenance: transfer infrastructure master
Server "<BACKUP_DOMAIN_CONTROLLER_NAME>" knows about 5 roles
…
fsmo maintenance: transfer rid master
Server "<BACKUP_DOMAIN_CONTROLLER>" knows about 5 roles
Schema - CN=NTDS
Settings,CN=<BACKUP_DOMAIN_CONTROLLER_NAME>,CN=Servers,CN=De
fault-First-Site-Name,CN=Sites,CN
=Configuration,DC=PEDVSHA,DC=EMERSON,DC=LOCAL
Naming Master - CN=NTDS
Settings,CN=<BACKUP_DOMAIN_CONTROLLER_NAME>,CN=Servers,CN=De
fault-First-Site-Name,CN=S
ites,CN=Configuration,DC=PEDVSHA,DC=EMERSON,DC=LOCAL
PDC - CN=NTDS
Settings,CN=<BACKUP_DOMAIN_CONTROLLER_NAME>,CN=Servers,CN=De
fault-First-Site-Name,CN=Sites,CN=Co
nfiguration,DC=PEDVSHA,DC=EMERSON,DC=LOCAL
RID - CN=NTDS
Settings,CN=<BACKUP_DOMAIN_CONTROLLER_NAME>,CN=Servers,CN=De
fault-First-Site-Name,CN=Sites,CN=Co
nfiguration,DC=PEDVSHA,DC=EMERSON,DC=LOCAL
Infrastructure - CN=NTDS
Settings,CN=<BACKUP_DOMAIN_CONTROLLER_NAME>,CN=Servers,CN=De
fault-First-Site-Name,CN=
Sites,CN=Configuration,DC=PEDVSHA,DC=EMERSON,DC=LOCAL
fsmo maintenance: quit
ntdsutil.exe: quit

C:\>

Note
As each role is transferred, make sure that no errors occur. The role summary
output (only shown for the last transfer above) should reflect the new ownership for
the role you just transferred.

3. Log in to the other domain controller (it was the additional but is now the primary)
as an administrator, and open a command prompt window.
4. Enter the following command:

C:\>netdom query fsmo

Schema master
<BACKUP_DOMAIN_CONTROLLER>.PEDVSHA.EMERSON.LOCAL
Domain naming master
<BACKUP_DOMAIN_CONTROLLER>.PEDVSHA.EMERSON.LOCAL
PDC
<BACKUP_DOMAIN_CONTROLLER>.PEDVSHA.EMERSON.LOCAL

157
Expanding a DeltaV Virtual Studio v4.3 HCI system
August 2022 D800142X012

RID pool manager

<BACKUP_DOMAIN_CONTROLLER>.PEDVSHA.EMERSON.LOCAL
Infrastructure master
<BACKUP_DOMAIN_CONTROLLER>.PEDVSHA.EMERSON.LOCAL
The command completed successfully.

C:\>

5. Ensure that the appropriate domain controller owns all five FSMO Roles (PDC,
Naming Master, RID Pool Manager, Infrastructure Master and Schema Master)
before continuing.

5.5 Join an earlier DVS system to an HCI system

You can use DVS 4.3 to manage both an older DVS system and the new HCI system. To do
so, you must install v4.3 on all systems being managed by the same DVS 4.3 application.
Be aware that Dell VRTX rack servers are end-of-life, so replacements will be unavailable. If
you wish to keep using existing VRTX servers you can, but you should starting planning to
eventually move everything onto the HCI system.
1. Upgrade the DeltaV Virtual Studio software on the older virtualized system to DVS
v4.3. Instructions for doing this are found in these documents:
• For upgrading a VRTX system: DeltaV Virtual Studio v4.3: Virtualization with High
Availability on a Dell PowerEdge VRTX
• For upgrading a SAN system: DeltaV Virtualization Planning and Installation Guide
v4.3
Note
In these documents, the upgrade path for the DVS software is from version 3.3.4 to
version 4.3. If your existing DVS system is using a version of DVS earlier than 3.3.4,
you must first upgrade your DVS installation up to version 3.3.4, and then carry out
a separate, complete upgrade process to bring the system up to version 4.3.

2. Install DVS on the virtualized HCI system as described in chapter 3 of this

installation guide, with these differences:
a. Configuring a virtual host domain controller (section 3.7, Configure a virtual
host domain controller)is not necessary, unless you want to create an
additional domain controller that is part of the domain from the older DVS
system.
b. In section 3.8, Join a host to a domain, join the hosts to the domain from the
older DVS system.

3. This step is unnecessary unless you need or want to replace the VRTX servers, but it
is highly recommended: When the HCI installation is complete, move the VMs from
the older VRTX or SAN system to the HCI system hosts. For information, refer to the
topic The Move Virtual Machines dialog in the DVS online help,
HCIEmersonVirtualMachineManager.chm.

158
 Index
D800142X012 August 2022

Index
Special Characters Capacities (continued)
Workstations 27
.LIN license file 70, 71 Charms I/O Cards: See "CIOCs" 18
.NET Framework 17, 81 Charms Smart Logic Controllers: See "CSLS" 18
Checklist, installation 37
CIOCs
A Hardware 16
Access key License needs 17
on a VM 72 Templates 18
Accounts, user 27 time use 30
ACH 18 Client
Activate Windows licenses 17 Start DVS 75
Active Directory 145 Client (DVS)
Add Hosts dialog 155 Defined 7
Adding hosts 155 Cluster
Additional domain controller 156 Validate 144
Administrators Clusters
security 112 Capacity 27
Security 107, 113 Expanding 152
AMS Device Manager Set up 79
Installing 135 COA 17
AMS Server Plus 99 Commands
AMS templates 18 DeltaV Remote Desktop Connection 86
Application (DVS) Configure
Defined 7 DCOM 133
Application Station host 75
connect 115 Host 77
Architecture Server 77
Network 9, 11 Configure Hosts for Live Storage Migration dialog 67
authentication Configuring
live migration 74 HCI switch 49
Autorun dialog 47, 49, 65, 67 N-series switch 53
ProfessionalPLUS VM 95
S-series switch 49
B connect
Application Station 115
Backup time server 141
Remote desktop 81
Base Stations
Connect
Not using VM Builder tool 99
DeltaV system identifier 97
BWFmgr.exe C: 112
DeltaV virtualization system identifier 72
Connect to console
C DRDC 133
USB to IP device 72, 97
Cable connections 11 virtual DeltaV Application station 115
Cabling virtual machine 115
Connection points 11 Connect to Console
Types of cables 11 About connections 119
Capacities Connecting to a VM 125
Clusters 27 Connecting
Domain controllers 27 Remote desktop 86
Domains 27 To VMs 86
Server 27 ConnectToConsole Users
Thin clients 27

159
Index
August 2022 D800142X012

ConnectToConsole Users (continued) DeltaV system identifier

Connect to console 115 Supported operating systems 17
Console DeltaV Virtual Studio
Supported operating systems 84 DeltaV node 128
Console session Start 75
DRDC 81 DeltaV virtualization system identifier
copy on a VM 72
virtual machine 74 DevData.cfg file 99, 129
Copyfilestohost.exe 76 Development test system 25
Copying release-specific files 76 Dialogs
CPUs 25 Add Hosts 155
Create Autorun 47, 49, 65, 67
Domain-level account 66 Configure Hosts for Live Storage Migration 67
Nodes in a DeltaV system 99 Create Virtual Machine 93
Create Virtual Machine dialog 93 Host Network Card Configuration 77
Creating Launch and Activation Permission 133
IDDC VMs 90 Log On to Windows 107
ProfessionalPLUS VM 93 Modify VM 18
Services account 126 My Computer Properties 133
VirtualizationAdmin account 126 NTP Settings 141
VMs using VM Builder tool 99 Product Key 95
CSLS Select Users or Groups 133
Templates 18 Specify hosts for Connect to Console 119
Disaster recovery 71
Disk write access
D Restricting 107, 112
DAC (Direct Attach Copper) 11 DNS
Database mode 131 Thick client network 113
Date Thin client network 107
Virtual machine settings 129 DNS server
dcdiag.exe 145 Setting up 47
DCOM DNS: See 'Domain Name System' 61
Configuration change 133 domain
Dcomcnfg.exe 133 health 145
Dell servers host 58, 62, 137
Download updates 34 Domain
DeltaV Joining 65
Templates 18 domain controller
time 30 host domain 58, 62, 137
Versions supported 18, 25 domain controllers
virtual machine settings 129 Time source 30
DeltaV connection Domain controllers
Remote desktop 81, 86 Additional 156
DeltaV Inter-Zone Server 129 Capacity 27
DeltaV node DNS addressing 61
DeltaV Remote Desktop Connection 128 FSMO 156
DeltaV Virtual Studio 128 Hardening 65
Windows Credential Manager 128 Host domain 61
DeltaV nodes Primary 156
Create 99 Templates 18
DeltaV remote client sessions Time servers 141
virtual machine connection 115 Transferring roles 156
DeltaV Remote Desktop Connection Domain controllers, virtual
Connect to console 72, 97 Number of 25
DeltaV node 128 Domain Name Service
Installing 81 health 145
supported connections 85 Domain Name System

160
 Index
D800142X012 August 2022

Domain Name System (continued) Files (continued)

Configuring addressing 61 DevData.cfg 129
Domains TcpRedundancySetup.exe 110
Capacity 27 Firmware 146
dongle 71 Force log off 133
Downloads FSMO 156
Before starting 34
Dell servers 34
Microsoft updates 35 G
DRDC Generate DVData file 99
Commands 86 Guardian 89
Connect to console 72, 97
Force log off 133
installing 81 H
supported connections 85
Supported operating systems 84 Hardening
Dual monitors Domain controllers 65
DeltaV Operator stations 135 Hosts 47
DVData file HCI
Generate 99 Architecture 9
DVS HCI switch
Application 16 Configuring 49
Client 16 health
Hosts 129 Active Directory 145
Licenses 70 AD 145
Manage virtual machines 16 DNS 145
Virtual machine manager 67 domain 145
DVS application (Defined) 7 Domain Name Service 145
DVS client (Defined) 7 host
DVS server (Defined) 7 domain 58, 62, 137
DVS service Host
Installing 67 Domain 61
DVS software (Defined) 7 Host Network Card Configuration dialog 77
Hosts
Adding 155
E Copy release-specific files 76
Harden 47
EIOCs Initialize 47
Templates 18 Manage with DVS 75
Enabling Network setup 77
NetBIOS 107 Operating system licenses 17
Enhanced Write Filter 112 PowerEdge server 34
Ethernet I/O Cards: See "EIOCs" 18 Set up 75
Expanding clusters 152 Setup 151
External time source Sizing 25
Synchronize with DeltaV system 33 System time 33, 141

F I
F2 151 Importing
FBWF 107, 112 Ports 53
FHX file 18 Initializing
Fiber 11 Hosts 47
File Based Write Filter 107 Installation checklist 37
File Based Write Filter: See 'FBWF' 112 Installing
Files DRDC 81
Copyfilestohost.exe 76 DVS service 67

161
Index
August 2022 D800142X012

Installing (continued) Modify VM dialog 18

New server 151 Monitors
On ProfessionalPLUS 67 Multiple monitors 135
Installing the virtualization system identifier mount drive
on a VM 72 ISO 106
IP move virtual machine
USB, converted from 72, 97 live migration 74
IP addresses MPIO 47
For DNS servers 61 MS Excel 18
Reserved addresses 23 MS Office 18
ISO MS Technet articles 61, 67
mount drive 106 MS Word 18
software installation file 106 mstsc.exe 81
ISO files 47 MUI 18
IZS Multicast 110
Network 129 Multiple monitors 107, 135
IZS: See 'DeltaV Inter-Zone Server' 129 My Computer Properties dialog 133

J N
Joining domain 65 N-series switch
Configuring 53
Replace 144
K NetBIOS
Kerberos Enabling on thin client 107
security 74 Thin client network 110
netdom query fsmo 156
netshare.exe 145
L Network
Architecture 9, 11
Launch and Activation Permission dialog 133
Load distribution 9
License file .LIN 71
Network cards
Licenses
VMs 129
.LIN license file 70
Network ports
Virtualization 70
Server 14
Windows operating system 17
Network Setup utility 77
live migration
Network Time Protocol
authentication 74
NTP 33
move virtual machine 74
Network time server
Load distribution 9
Synchronize 33, 141
Local Safety Network Bridge: See "LSNB" 18
Networks
Lockdown USB 107
Connectivity 119
Locking down USB 112
IZS 129
Log On to Windows dialog 107
Thin client 129
LSNB
NICs
Templates 18
Server 14
VMs 129
M Non-console mode connection
To virtual machine 133
MAC addresses Non-DeltaV server VM 101
Smart Switch 29 Non-DeltaV servers
VMs 29, 129 Not using VM Builder tool 99
Master time server 141 ntdsutil.exe 156
Microsoft NTP
Documentation 34 Network Time Protocol 33
Download updates 35 system time 33
Microsoft Terminal Server 17 NTP server

162
 Index
D800142X012 August 2022

NTP server (continued) RDP (continued)

IP addresses reserved for 23 supported connections 85
NTP Settings dialog 141 Supported operating systems 84
NTP Settings utility 81 Redundant network
Thick client 113
Thin client 110
O Redundant Network
Operating systems Thin client 107
For DeltaV Remote Desktop Connection 84 Redundant networks
Licenses 17 Thin clients 112
On templates 18 Registration service
Supported 17 About 88
Operator training system CONFIG file 89
Number of VMUs 25 Uploading a file 89
Remote access 115
remote desktop
P virtual DeltaV Application station 115
Remote Desktop Protocol
Passwords 27
supported connections 85
Plant LAN
Remote Desktop Users
Need for synchronizing time 33
Connect to console 115
Ports
Remote logoff 133
Importing 53
repadmin.exe 145
Locking 29
Replacing
Server 11
HCI switch 144
Smart Switch 29
Witness machine 143
PowerEdge R740xd XL
Reserved IP addresses 23
Cable connections 11
Restricting
PowerEdge server
Disk write access 112
Host 34
Restricting disk write access 107
PowerEdge servers
Host 77
Precise time S
SOE 141
Primary domain controller 156 S-series switch
Product Key dialog 95 Configuring 49
Production system Replace 144
Number of VMUs 25 Scheduled task 134
ProfessionalPLUS Screen saver 134
Creating VM 93 security
ProfessionalPLUS VM Kerberos 74
Configuring 95 Security
Thick client 113
Thin client 107, 112
Q Select Users or Groups dialog 133
Servers
QNX operating system 17, 30
Cable connections 11
Quad monitors
Capacities 27
DeltaV Operator stations 135
Downloads 34
Host 34
R Install new 151
NICs 14
RAM 25 Setup 77
RAM required Update firmware 146
IDDC VMs 90 Service (DVS)
ProfessionalPLUS VM 93 Defined 7
Standalone server 101 Service manager
RDP DVS 70

163
Index
August 2022 D800142X012

Service manager account Thick client (continued)

Host setup 151 Redundant network 113
Services account Security 113
Creating 126 Thin client
Set up Redundant network 107
DNS server 47 Thin Client Network Redundancy Setup utility 110
Windows Server 2022 43 Thin clients
Setting up Capacity 27
Cluster 79 NetBIOS 110
Thin client 107 Network 129
Virtual ProfessionalPLUS 131 Operating system license 17
Settings Redundant network 110, 112
Virtual machines 129 Security 107, 112
Shortcuts Setting up 107
DRDC 86 Time
Smart Switch Virtual machine settings 129
Port locking 29 Time server
SOE Backup 141
Precise time 141 External network 33
Software (DVS) Master 141
Defined 7 time servers
software installation file external 30
ISO 106 physical 30
Specify hosts for Connect to Console dialog 119 timestamps 30
Standalone server 101 Transferring domain controller roles 156
Starting
DVS 75
storage manager computer
U
Active Directory UAC
host domain 58, 62, 137 User Access Control 127
host domain 58, 62, 137 Updating firmware 146
Subnet mask 47 upgrade
supported connections domain health 145
virtual machine desktop 85 Upload a registration service file to Guardian 89
Supported operating systems 17 USB
synchronize system time 30 to IP converter 72, 97
System setup 151 USB lockdown 107, 112
system time User Access Control (UAC)
synchronize 30 disable 127
System time User accounts 27
External time source 33 User groups
Synchronize 33, 141 ConnectToConsole 115
Virtual machines 141 Remote Desktop Users 115
Security 107, 112, 113
T UTC time 30
UTN 72
TcpRedundancySetup.exe file 110
Templates
AMS 18
V
CIOC 18 Validating cluster 144
CSLS 18 Virtual CIOCs
EIOC 18 Number of 25
LSNB 18 Virtual domain controllers
Workstation 18 Number of 25
Thick client virtual machine
DNS 113 copy 74
NetBIOS 113

164
 Index
D800142X012 August 2022

virtual machine (continued) Workstations

live migration 74 Capacity 27
move 74 Templates 18
Virtual machine Types 18
Settings 129 Workstation templates 16
virtual machine desktop Wyse thin client 107
supported connections 85
Virtual machine manager 67
Virtual Machine Units 25
Virtual machines
Create non-DeltaV server VM 101
DVS 16
System time 141
Virtual workstation types
DeltaV workstations 18
Virtualization system identifier 71
VirtualizationAdmin
User account 27
VirtualizationAdmin account
Creating 126
VM
Installing the access key 72
VM Builder tool 99
VMs
Configuring ProfessionalPLUS VM 95
Creating IDDC VMs 90
Creating ProfessionalPLUS VM 93
Creating using VM Builder tool 99
MAC addresses 129
Manage with DVS 75
Network cards 129
Number of 25
Operating system license 17
Setting up the ProfessionalPLUS workstation type 131
System time 30
VMS
Redundant thin client network 112
VMUs
Number of 25

W
Windows
Licenses 17
Windows 10 17
Windows Credential Manager
DeltaV node 128
Windows Server
2016 25
2022 25
Number of VMUs 25
Windows Server 2022
Host setup 151
setup 43
Windows time 141
Witness machine
Replace 143

165
Index
August 2022 D800142X012

166
D800142X012 August 2022

167
D800142X012
2022