VERDE Dynamic Network Configuration
VERDE Dynamic Network Configuration assigns static network parameters to dynamic virtual desktop environments. For example, permissions or policies may need to be configured for given desktops by specifying their computer names, IP addresses, or MAC addresses. This file enables VERDE to work with these assigned values. Common uses include:
- Support application access restricted by IP address. Assign static IP addresses to dynamic virtual desktops using bridged networking without requiring a DHCP server or static MAC address assignment.
- Support Windows workgroup functions requiring static computer names (network scanners, etc.). Assign static Windows computer names to dynamic virtual desktops using bridged networking.
Dynamic Network Configuration is currently limited to Windows virtual desktop environments . For both computer name and IP address, the netcfg settings overwrite Session Settings.
VERDE runs an agent inside Windows virtual machines that automatically performs dynamic network configuration.
If specified, it assigns any IPv4 parameters for the session as well as a Windows Computer Name, and the virtual desktop will join the Active Directory domain.
After the virtual desktop joins the domain, it will reboot twice. The first reboot displays a Windows login credentials screen. Windows is trying to login with an Active Directory account when the virtual session has not yet joined Active Directory. The session will restart within a few seconds.
There may be a delay on the credentials screen as the session joins the domain.
A virtual desktop goes through the domain join procedure described above every time the Gold Image is updated. If the Gold Image is updated, the delta file is no longer valid. The next time the dynamic desktop starts, it must join the domain again.
VERDE Dynamic Network Configuration uses a CSV file to map dynamic virtual desktops to specific network configurations. Create this file and import it into the VERDE Management Console.
Fields must be separated with a comma. Use of spaces or other characters will cause the file to fail. The last three fields are being deprecated, the domain name, administrator and password should be left blank (do not remove the comma separators). The information to join the domain is not set in the netcfg file anymore, it is done in the Session Settings in the VERDE Management Console.
Field | Description |
---|---|
<user> | The user name or Linux user ID of the user receiving the virtual desktop. This is case sensitive.<username@<LDAP_Alias>@<org-ID> Where <LDAP_Alias> is set in the LDAP server definition in the VERDE Management Console and <org-ID> is the id attributed to a new organization (the ID column in the Organization screen).For a user "joe," AD domain "addomain.com," belonging to an organization with LDAP server name "Org1-AD" (org-ID: org-7), the user syntax is:joe@Org-AD@org-7 To only set the computer name to "Test-Netcfg-01" for that user starting the desktop "Win7-32", the entry would look like:joe@Org1-AD#org-7,Win7-32,,,,Test-Netcfg-01,,, |
<gold-image> | The image name of the virtual desktop, as defined in the VERDE Management Console. This is case sensitive. |
<ip-address> | The IPv4 address to set for the session, if using bridged networking. |
<netmask> | The IPv4 network mask to set for the session, if using bridged networking. |
<gateway> | The IPv4 default gateway to set for the session, if using bridged networking. |
<Computer-Name> | The Windows Computer Name to set for the session, up to 15 characters in length (longer names are automatically truncated). |
<domain> | The fully qualified Active Directory domain name (domain.company.com). This setting is Deprecated. The VERDE server should still have the domain controller as the primary DNS. The guest still uses that in NAT mode. |
<domain-admin> | The Active Directory domain administrator who can join computers to the domain. Type the domain name in capital letters when specifying users, such as AUS\verde1 . This setting is Deprecated. |
<domain-password> | The Active Directory domain administrator's password, in plain text format. This setting is Deprecated. |
For example, to assign the image winxp for the user xpuser to IPv4 parameters:
- IP Address. 192.168.10.5
- Network Mask.255.255.255.0
- Default Gateway. 192.168.10.1
- Windows Computer Name. xpuser-winxp
- Active Directory domain. ad.corp.com
- Domain administrator. admin
- Domain password. password
The row in the netcfg.csv
file would look like:
xpuser,winxp,192.168.10.5,255.255.255.0,192.168.10.1,xpuser-winxp,ad.corp.com,admin,password
To perform the same assignment but without IPv4 parameters (defaults to DHCP):
xpuser,winxp,,,,xpuser-winxp,ad.corp.com,admin,password
To perform the same assignment but without joining the Active Directory domain:
xpuser,winxp,192.168.10.5,255.255.255.0,192.168.10.1,xpuser-winxp,,,
Blank fields must still be separated by commas. Improperly formatted rows are ignored.
The VERDE Server must have the IP address of the Windows Domain Controller as the first name entry in the /etc/resolv.conf file; for example:
# ***** resolv.conf *****
search ad.corp.com
nameserver 192.168.1.111 (IP address of Windows Active Directory server)
nameserver 24.93.41.115
nameserver 24.93.41.116
IPv4 parameters are only recognized if using bridged networking.
In order to join Active Directory, all three parameters (FQDN, domain administrator user name, and domain administrator password) must be correctly listed.
The user name and image name are case sensitive. Windows fields are generally not case sensitive unless required by the domain controller.
There is no limit to the number of rows in the CSV file.
By default, the netcfg.csv
file is not synchronized with VERDE branch servers. This is for security reasons, as the file contains administrator login information.
To enable the branch and branch server synchronization, add the VERDE_BRANCH_SYNC_NETCFG=1
settings line to the /home/vb-verde/.verde-local/settings.cluster
file.