Virtual IP Address Support

Overview

The HyWorks Controller v3.4 introduces virtual IP feature for multi-user Windows and Linux session host servers.

The session host server serves multiple shared hosted desktop sessions or application sessions from the same server. By default, all the session traffic is generated through the server IP address and hence it is difficult to distinguish the traffic on the network layer. The virtual IP address feature helps to distinguish the network traffic on the network layer, so firewall policies can be applied to users.

Virtual IP address needs to be configured on the Team and its respective Application and Desktop pool to enable the Virtual IP address assignment on a shared hosted desktop session or application session. The controller assigns a Virtual IP address to the shared hosted desktop session or application session as per the policy applied on the Team, Application, or Pool. This session’s Virtual IP address is then configured on the session host server by the session host service and all network traffic will be generated using the assigned Virtual IP address for that user session. So, network traffic can be distinguished for user sessions by using this Virtual IP address.

Virtual IP address set or range can be defined on Team in the network settings page of Team wizard, other assignment settings are applied from the Desktop Pool or Application wizard.

• The feature is configured from the HyWorks Controller Management Console.

• The feature is supported on both Linux and Windows Session host servers for shared hosted desktop and application sessions.

• Virtual IP can be applied to all processes or specific processes.

• Administrators can choose to block the session, if the virtual IP address is not available (Provide session only when virtual IP is available).

• Virtual IPs can be temporarily or permanently assigned.

Important

IP virtualization feature is currently not supported by cloud providers like Azure, AWS or OCI. This information is being captured with HyWorks v3.4-SP1 and any future extensions will be notified.

Virtual IP address configurations

Refer to the below section to configure the virtual IP address:

1. Enable Network Virtualization on Session Host
2. Configurations in the Server Team wizard
3. Enable Virtual IP in Application Wizard or Enable Virtual IP in Desktop Pool Wizard
4. Virtual IP Assignment Verifications

Pre-requisites:

1. The virtual IP address feature on Windows servers requires a network card with static IP configuration. DHCP configured network cards can not be used for virtual IP addresses. Linux servers with DHCP configurations can be used.

Enable IP Virtualization on Session Host

Windows Session Host Server

Follow the steps given below to enable the IP Virtualization on the Windows Session Host server:

1. Take RDP access or console access of the session host server with the administrator account.

2. Open the registry settings and go to: HKLM\SOFTWARE\Accops\DVMAgent\Advance Settings\

3. Set Enable VIP Management as True.

4. Restart HyWorks Desktop agent service. The session host server is ready for IP virtualization.

Linux Session Host Server

Follow the steps given below to enable the IP Virtualization on the Linux Session Host server

1. Connect to Linux SHD server via SSH client or terminal with root privileges.

2. Go to the linuxDVM directory to enable the IP virtualization.

   cd /etc/edcdvm/linuxDVM/

3. Open file vminfo.json and set the flag Enable Vip Management as True.

4. Restart the DVM Agent service.

   sudo systemctl restart edcdvm

Now the Linux Session Host server is ready for the virtual IP enabled pooled desktops or app delivery.

Enable IP Virtualization on Session Teams

Follow the steps given below to enable the VIP in Session Teams:

1. Log in to the HyWorks management console using the Super administrator user account.

2. In Session Teams, click the Add/ Edit wizard.

3. Provide all other details as per your requirement and navigate to the Network Settings tab. (Refer this for more details on different fields of session teams wizard.

4. Network Settings: Provide the virtual IP address details in Network Settings:

   1. Enable session virtual IP address: Select to enable the session virtual IP address support.

   2. Select Network Card from Multiple NICs: If multiple network cards are available on the server, then select the preferred network card. The session virtual IP address feature will not work on servers with multiple network cards and if the preferred network card is not specified in the HyWorks Controller.

   3. IP Address or IP Range: Enter the comma separated IP addresses or IP range, which can be a virtual IP.

      Examples of valid IP format: 192.168.0.241, 192.168.0.1-192.168.0.255. The IP address range should be valid and free on the network.

   4. Subnet Mask: Enter the subnet mask which will be used to assign the virtual IP address on the server along with one of the given IP addresses. The subnet mask bit should be valid values like 255,252,248,240,224,192,128 and 0.

5. Click Save to save Session Teams with virtual IP feature enabled.

Virtual IP Configurations on Pool and Virtual Apps

Prerequisites for the virtual IP address on the application or shared hosted desktop pools

1. The virtual IP address must be configured on the Session Team from where the application or desktop pool is published.

2. The virtual IP address must be valid and allow communication on the network from the session host server.

3. If multiple network cards are available on the server, select the preferred network card in the team wizard. The session virtual IP address feature will not work if the administrator does not provide the preferred card and has multiple network cards.

Note

• Virtual IP address feature on Windows servers requires a network card with static IP configuration. DHCP configured network card can not be used for virtual IP addresses.

Application Wizard

1. Go to Apps > Virtual Apps section. Open the Add/ Edit Application wizard. Follow the steps provided in the Application wizard to fill in all the required details to publish an application.

2. Considering all other details are provided correctly, configure the virtual IP settings using the following descriptions of the associated fields:

   1. Go to the Virtual IP Address tab for VIP configuration.

      1. Enable session virtual IP address: Select the option to enable virtual IP address support for sessions.

      2. If no virtual IP address is available: Configuration to be done when virtual IP addresses are not available for the session. The currently available options are to block session or allow session with the server IP address.

      3. Apply virtual IP address to: Specify whether a virtual IP address is to be applied to all processes or specific processes.

         1. All Process: Session virtual IP address will be applied to all processes within a session.

         2. Specified processes only:

            1. Process list to be: Specify whether the virtual IP address should be assigned to the configured list of processes or not. Included: All mentioned processes will use the configured virtual IP address and the rest of the processes will use the server IP address. Excluded: Specified processes will not be assigned any virtual IP address and all the other processes will use the virtual IP address.

            2. Specify Process List: List of processes to be included or excluded. A maximum of 50 processes can be defined and each process should be less than 255 characters.

      4. Session virtual IP address on team: Information of virtual IP address configurations from source Session Team.

3. Save the application.

4. Application is now available to entitled users with virtual IP address enabled.

Important

• Remote App: In case of multiple virtual IP addresses enabled Remote app the process list is merged. The Last virtual IP address policy will override the previous policy and the include and exclude list will be merged with previous policy applied.

Recommendations:

1. App/process from the same Session Team should have identical VIP settings.

2. Use the Specified processes only option for remote apps.

Pool Wizard

Configure the virtual IP address settings for the desktop pool and desktop sessions will be delivered with the virtual IP address:

1. Log in to the HyWorks management console using Super administrator user account.

2. Go to VDI > Pools > Add or Edit the existing pool.

3. Go to Virtual IP Address tab for VIP configuration.

   1. Enable session virtual IP address: Select to enable the session virtual IP address support.

   2. User Virtual IP Assignment: Session virtual IP address life span can be temporary or permanent. Permanent option will reserve the same IP address for all user sessions in future and the temporary option will give different virtual IP address on every logon.

   3. If no virtual IP address available: Configuration to be done if virtual IP addresses are not available for the session. Available options are block session or allow session with server IP address.

   4. Apply virtual IP address to: Specify whether virtual IP address is to be applied to all the processes or specific process.

      1. All Process: Session virtual IP address will be applied to all the processes within a session.
      2. Specified processes only:
         1. Process list to be: Specify whether a virtual IP should be assigned on the configured list of processes or not. Included: All the specified processes will use the configured virtual IP address and rest of the processes will use server IP address. Excluded: All the specified processes will not be assigned any virtual IP address.
         2. Specify the process list: List of processes to be included or excluded. Maximum of 50 processes can be defined and each process should be less than 255 characters.
         3. Session virtual IP address on team: Information of virtual IP address configurations from source session team.

4. Save the desktop pool. Desktop pool is now available to entitled users with virtual IP addresses enabled.

Validation of Virtual IP Address

For Application Sessions

App Session is any independent application accessed using HyWorks Client or HyLite. It is recorded and displayed in the HyWorks Controller Management console. All applications being delivered to users are tracked using unique App Session IDs.

1. Go to Monitor > Live Sessions > Applications

2. View details of all application Sessions by clicking Username:

Sr No	Column Name	Description
1	Application name	The name of the application that was launched.
2	Server name	The name of the session provider.
3	VIP Address	Virtual IP Address.
4	Status	Status of the app session (Initializing/ Running/ Disconnected).

1. Check the assigned VIP by executing the ipconfig /all command on the session host server.

2. Also assigned VIP can be seen in the Desktop agent logs.

Logs

    2022-11-29 17:07:46,738 [76] INFO  - [SHD>DVM] AddVipInSystem() called with data: {"Id":null,"Username":"sk2","AppProcessName":"notepad","Application":"*","VIP":"172.26.4.6","ActionType":0,"NIC":"Ethernet0","Subnet":"255.255.240.0","SessionType":1,"CntAppOrDesktopSessionId":"497593c9-7cbe-4953-a870-5aefb28634cf","wtsId":-1,"IsReuseVip":true,"BlockSession":true,"ProviderSessionId":"d2cd67e4-4e8e-47f6-8ed0-4a1ddfd867a1","IsExcludeVip":false}
    2022-11-29 17:07:48,238 [81] INFO  - AddVip() called with data: NicFilter:Ethernet0, AddIpAddress:172.26.4.6, SubnetMask:255.255.240.0
    2022-11-29 17:07:48,238 [81] INFO  - [NugNWHelper] AddIP() Adding ip address 172.26.4.6 : 255.255.240.0, Nic name Ethernet0
    2022-11-29 17:07:50,269 [76] INFO  - VIP '172.26.4.6' is found attached to machine.

For Desktop Sessions

The desktop session is any desktop accessed using HyWorks Client or HyLite will be displayed and managed in the HyWorks Controller Management console. Desktop sessions can be monitored on the HyWorks Controller Management Console:

1. Go to Monitor > Live Sessions > Desktops

   1. The assigned virtual IP address should be displayed against the session entry.

2. Check the assigned VIP by executing the ipconfig /all command on the session host server.

3. Also assigned VIP can be seen in the Desktop agent logs:

Logs

    2022-11-29 16:48:27,476 [87] INFO  - [SHD>DVM] AddVipInSystem() called with data: {"Id":null,"Username":"sk2","AppProcessName":"*","Application":"","VIP":"172.26.4.7","ActionType":0,"NIC":"Ethernet0","Subnet":"255.255.240.0","SessionType":0,"CntAppOrDesktopSessionId":"3b310598-175f-4034-91df-5c3d66204899","wtsId":-1,"IsReuseVip":false,"BlockSession":true,"ProviderSessionId":"3b310598-175f-4034-91df-5c3d66204899","IsExcludeVip":false}
    2022-11-29 16:48:27,491 [6] INFO  - AddVip() called with data: NicFilter:Ethernet0, AddIpAddress:172.26.4.7, SubnetMask:255.255.240.0
    2022-11-29 16:48:27,507 [87] INFO  - [DHCP-to-Static] Converting NicName 'Ethernet0' to static
    2022-11-29 16:48:27,523 [6] INFO  - [NugNWHelper] AddIP() Adding ip address 172.26.4.7 : 255.255.240.0, Nic name Ethernet0
    2022-11-29 16:48:31,773 [6] INFO  - VIP '172.26.4.7' is found attached to machine.`

Checking Virtual IP Information on Linux Session Host Server

When a virtual IP is attached to the session, an entry of the session is added to the ip_info file, and on user logout the entry is removed.

To see session entries with virtual IP:

1. Connect to Linux SHD server using SSH client or terminal.

2. Run the following command:

   suo cat /etc/ip_info

3. It will show entries in the following format:

   USERNAME=exampleuser,APPLICATION=*,VIP=192.168.1.89,ActionType=0

Virtual IP Address Assignment Flow

1. Controller to select the best session host server for application or desktop session and calculates appropriate policies for the session.

2. Virtual IP address calculation: If it is enabled on the application and respective team:

3. Enabled on the Application and disabled on Team, then the session will be allowed without a virtual IP address or blocked as per the settings done for If no virtual IP address available.

4. If all given virtual IP addresses of a Team are used by other sessions and no free virtual IP address is available for a new session, then the session will be allowed without a virtual IP address or blocked as per the If no virtual IP address available setting on application.

   1. If a virtual IP address is enabled and a valid IP is available for the session, then the Controller sends the Virtual IP address to the session host server.

5. The session host tries to add the virtual IP address to the Network interface card. If a single Network interface card is available on the server then the virtual IP address is added to that network card.

   1. If multiple Network interface cards are available on the server then the session host tries to filter the network card using the Filter on Network Card Name setting from the team. If more than one Network interface cards are found, then the virtual IP address addition is marked as failed, and the session gets logged out.

6. Network traffic will use an added virtual IP address as the source IP address for the session so that network traffic can be distinguished from a user session on the network layer.

7. The session host removes the virtual IP address entry from the Network interface card once the session is logged out and sends the removal confirmation to the controller.

8. Used virtual IP address gets free for other sessions for application sessions. For desktop sessions assigned virtual IPs can be kept reserved or assigned to the users in permanent assignment cases.

Permanent Virtual IP address on Pool

For Desktop Pools, HyWorks provides option to assign permanent virtual IP address, ensuring a user gets same virtual IP address, while connecting to desktops from the desktop pool. The section will provide detailed information on following topics:

1. Automatic Assignment of Permanent Virtual IP Address

2. Manual Assignment of Virtual IP Address using CSV Import

3. How to Remove Permanently Assigned Virtual IP Addresses

Automatic Assignment of Permanent Virtual IP Address

Permanent virtual IP address is the reserved IP address for a user, so that the user gets the same virtual IP address on every login. With automatic assignment, a permanent virtual IP address gets reserved for the pool for the respective user, when the user connects to a shared hosted desktop for the first time. Then onwards, the user will get the same virtual IP address on every logon of that pool.

• The permanent virtual IP address is assigned to the user when the user connects to the virtual IP enabled desktop pool for the first time.

• The virtual IP address will remain assigned to the user until the user is deleted or the IP is manually removed from the user.

• The permanently assigned virtual IP can be removed from Users > Registered Users section. See the details here.

• HyWorks Controller v3.4-SP2 or later is having provision to assign permanent virtual IP addresses to the user using CSV operation. Please refer section Manual assignment of permananent virtual IP addrress for the detailed process.

Note

Permanent virtual IP addresses are not supported for applications.

Manual Assignment of Virtual IP Address using CSV Import

Sometimes it is required to assign a virtual IP address, before it logs-in and connects to the desktops and thus a feature to assign permanent virtual IP address to user for a specific desktop pool has been integrated in HyWorks v3.4-SP2 or later.

Supported Version: v3.4-SP2 or later

CSV Import Process

Follow below steps to assign permanent IP addresses to users using CSV import:

1. Login into HyWorks Management Console with user having super administrator role or privilege to import CSVs.

2. Navigate to VDI > Session Servers > Server Teams.

3. Click on CSV Operations > Download Template > Permanent VIP Assignment.

   1. Template download is not mandatory, if a CSV is already availble with appropriate entries.

4. Edit the downloaded template and provide the entries. (Do not delete values in first two rows. First row has rules and second row as column headers. Entries are imported from 3rd row.)

   • Pool Name: The name of the shared hosted desktop pool, to which permanent virtual IP address has to be assigned.

   • User Id: User Id, user is using to login into HyWorks.

   • Permanent Virtual IP Address: The IP address to be assigned to the user.

   • Subnet: Valid subnet of configured IP address.

   • Operation: Assign - to assign an IP address if its not already assigned, Unassign - to unassign IP address if its already assigned, Update - to update IP assignment if an entry already exists.

5. Save file in appropriate CSV format.

6. Navigate to VDI > Session Servers > Server Teams.

7. Click on CSV Operations > Import > Permanent VIP Assignment.

   1. Chose appropriate CSV type to import.

   2. Browse and open the prepard CSV in Import wizard.

   3. All records being imported will be shown in Import Permanent VIP Assignment to update prompt. It also lists the record which will not get imported with reason of failure.

   4. Click on Save to continue importing.

8. All entries will be processed as per defined operation.

9. The updates can be verified by exporting the Permanent VIP list from CSV Operations > Export > Permanent VIP Detailed or Permanent VIP Assignment.

   1. The detailed exported CSV is for review with additional columns and can not be imported back.

   2. The Permanent VIP Assignment CSV can be used to import back to modify the assignments.

CSV Import Rules and Template

• CSV Import Rules: Following things must be considered carefully to avoid CSV import failures:

  • Do not delete the top two rows of the template. HyWorks by default reads from row-3, from where VIP entries should be provided.

  • Provided IP address belongs to the range mentioned in the session server teams.

  • Given IP Address should not be assigned to any user in HyWorks.

  • Unassigned IP should not be in Problematic IP List: The system will validate that an unassigned IP address is not part of a problematic or blocked IP list.

  • Pool Requires Permanent VIP Assignment Feature: The pool must support permanent assignment for the Virtual IP feature to be enabled.

  • Warning if user desktop is active: If a user desktop session is already running, the system will issue a warning that the Virtual IP assignment will only be effective in the next session.

  • Import Records Limit: 300. At a given time, not more than 300 records can be processed from a CSV.

• Template format:

  • Row-1/Column-1: Rule
  • Row-2/ Column-1 to Column-5: Column Headers (Pool Name, User Id, Permanent Virtual IP Address, Subnet, Operation)
  • Row-3 onwards: Actual Virtual IP entries start from here.

Rule: 'Operation' can be 'Assign' or 'Unassign' or 'Update'. 'Assign' will be used to assign a VIP to user. 'Unassign' will unassign the VIP for user. 'Update' will update the subnet and IP Address for the specified pool and UserId. Note: Do not edit/delete the sequence of any row/column**
Pool Name	User Id	Permanent Virtual IP Address	Subnet	Operation
SHDPool	test.qa11	x.x.x.x	x.x.x.x	Assign
SHDPool	test.qa12	x.x.x.y	x.x.x.x	Update
SHDPool	test.qa13	x.x.x.z	x.x.x.x	Unassign
more entries...

Remove Permanent Virtual IP

Administrator can remove the permanent VIP assignment from the HyWorks Management Console if the assigned VIP is marked as Problematic or needs to be freed. Follow the steps given below to remove the permanent VIP:

1. Log in to the HyWorks Management Console using Super administrator account.

2. Go to Users > Registered User.

3. Click Username > User Desktops tab and check the assigned pool.

4. Virtual IP Assignment Type > Assigned Virtual IP gets displayed.

5. Click Remove Virtual IP assignment > Pop-up will be displayed to confirm the action.

6. Enter the assigned VIP > Click Delete.

7. VIP assignment for the user will be deleted.

8. The controller will keep this IP as free and will assign to user in upcoming connections.

Problematic Virtual IP address

Problematic virtual IP addresses are the virtual IP addresses for a team that are in a problematic state so they can not be assigned to new upcoming session even if the last session that was using this virtual IP address is logged out. Below are the situations where the virtual IP address is moved under the problematic list.

1. IP conflicts.
2. Host addition failure.
3. Unable to add virtual IP to NIC.
4. Unable to remove virtual IP from NIC.
5. The controller sends a logout but confirmation is not received from the session host.

How to Remove Problematic Virtual IP Address

Refer section Session synchronization with Session Server

Exporting Virtual IP Address Details

Administrators can export different types of virtual IP address data from server teams or session server pages. The following types of data can be exported:

1. Exporting All VIP Sessions

2. Exporting Problematic Virtual IPs

3. Exporting Permanent Virtual IPs

Session synchronization with Session Server

The controller decides the appropriate session provider based on the load balancing algorithm for a new application or desktop session and creates a session in the controller database to track it.

Similarly, the controller sends the session information to the session host server and it also maintains the session data in its database. However, over a while, a session in the controller database and a session in the session host database can create discrepancies due to communication errors or some other issues. In case of such discrepancies, the session host server and controller can be synchronized to correct the session details.

Session Synchronization Steps

Session discrepancies can be cleaned up using two ways.:

1. Interval based session sync from session host.
2. Manual session sync from team and load balancing page.

Interval based session sync from Session host: Interval based session sync from the session host can be enabled using the below mentioned advance settings (Settings > General > Advance Config):

1. Enable Session Sync on Session Host: If set as True, then the session synchronization will be done by the session host after the Session Sync Interval on Session Host.
2. Session Sync Interval on Session Host: Session synchronization will be performed by the session host after the specified interval in minutes, if the Enable Session Sync on Session Host setting is set to True.

Manual session sync from team and load balancing page: In some cases if it is required to initiate explicit session sync, the action can be initiated from the HyWorks management console:

1. Team page: Go to VDI > Session Servers > Server Teams. Then select team and click on 'Sync session info' button
2. Load balancing page: Go to VDI > Session Servers > Server Teams. Then click on team name. After loading load balancer page, select any session server and click on 'Sync Session info' button

Session Synchronization Flow

Session synchronization between HyWorks controller and session servers works uses following flow:

1. Session host fetches the session list and problematic virtual IP address list from controller

2. Session host finds the difference in controller and session host session list

3. All the sessions get logged out from the controller or session host, if they can not be validated on session host or controller databases.

4. Session host tries to check the problematic virtual IP addresses, and if the virtual IP address is not in problematic state then confirmation will be sent to controller. And now controller can remove the virtual IP address from problematic list. Refer the Problematic virtual IP address section for more details.

Default IP Support

Virtual IP can be applied to all the processes or specific process in a desktop session. In cases, where virtual IP has to be applied only to specific processes, all the other processes will use the default IP sent by controller or default IP configured by admin in the registry setting of windows session host server.

Controller considers the default IP as the one, which is used for the SHD communication, but if it is needed to use some other IP as the default one, then follow the below steps to enable to configure the default IP:

Default IP on Windows Session Servers

1. Take the remote or console access of session host server with administrator account

2. Open registry settings and go to

   HKEY_LOCAL_MACHINE\SOFTWARE\Accops\DVMAgent\ADVANCE SETTINGS\VIP SETTINGS

   • UseVMDefaultIPFromCNT: Default value true. If true, then use default IP pushed by controller in VMDefaultIPByCNT flag, if false then use VMDefaultIP configured by administrator.
   • VMDefaultIP: Default value empty. Different IP address to be used than controller managed default IP. This value will be used, if UseVMDefaultIPFromCNT is false. This Default IP (provided by admin) will be used in sessions or for processes without virtual IP.
   • VMDefaultIPByCNT: Default value empty. Administrator must not modify this value. This Default IP (updated by controller) will be used in case no VIP is assigned for that session/process.

Note

• The registry setting changes will be applied after DVM agent service restart.

Default IP on Linux Session Servers

1. Connect to Linux SHD server using SSH client or terminal

2. Edit the following file to change settings for the following flags:

/etc/edcdvm/linuxdvm/vmInfo.json

1.  UseVMDefaultIPFromCNT: Default value true. If true, then use default IP pushed by controller in VMDefaultIPByCNT flag, if false use VMDefaultIP configured by administrator.

2.  VMDefaultIP: Default value empty. Different IP address to be used than controller managed default IP. This value will be used, if UseVMDefaultIPFromCNT is false. This Default IP (provided by admin) will be used in sessions or for processes without virtual IP.

3.  VMDefaultIPByCNT: Default value empty. Administrator must not modify this value. This Default IP (updated by controller) will be used in case no VIP is assigned for that session/process.

When DVM agent service starts, default IP entry is added in ip_info file based on flag UseVMDefaultIPFromCNT with username: USR_NONE. Network monitoring module binds all the other processes with this default IP.

Note

1. If UseVMDefaultIPFromCNT is ON then VMDefaultIPByCNT IP will be used as default IP address otherwise VMDefaultIP will be used.

2. The vmInfo.json file setting changes will be applied after DVM agent service(edcdvm service) restarts.

Advance settings

Converting Dynamic to Static IP on Session Host Server

Virtual IP address feature on Windows servers require network card with static IP configuration, where as for cloning session host server, DHCP is required to avoid the IP address conflict. To overcome this, below configurations can be done to set the IP address allocated via DHCP to static:

1. Take RDP access or console access of session host server with administrator account

2. Open the registry settings and go to below mentioned location:

   HKLM\SOFTWARE\Accops\DVMAgent\ADVANCE SETTINGS\VIP SETTINGS

   • AutoConvertDhcpToStatic: Default value is False. If true, DVM agent will convert the DHCP configured network card to static on Desktop agent service start. When the SHD is a part of managed team and has DHCP configured network card, This setting is required to be set.

   Note

   • Before every cloning operation start, this flag has to be set as True on the gold master VM. But make sure not to restart the DVM agent service.
   • If the gold master is restarted after making the flag is true, it may convert the DHCP to static and thus should be set to DHCP only before cloning.

   • DhcpNicConversationFilter: Default value is (*). If multiple network cards have been configured on the session host server, specify the name of the network card to be converted to static. If the system has a single network card attached then * will convert the only available DHCP network card to static using existing IP configurations.

   • PostCustomizationAutoConvertDhcpToStatic: Default value is 'False'. If this flag set as True then after before setting the customization status as completed the AutoConvertDhcpToStatic gets set as true and DHCP configured network card gets converted to the Static.