Skip navigation

Jonathan's Blog

4 posts

Configuring LDAP Source in VMware vROPS

1. In vROPS UI, go to Administration, Authentication Sources. Click on the “+” icon to add the new LDAP source




2. Provide the LDAP source details for your domain (e.g. AS.corp.local)



3. Click Ok.

4. Sync users group from the selected LDAP Source



5. Import Active Directory Security Group from the domain (e.g. as.corp.local\vdiadmins).



6. Grant Administrator role and allow access to all the objects.



7. Click Finish.

8. Click Yes to continue

9. Test the login with a domain credential to vROPS UI page.

Installing and Configuring vROPS Horizon View Broker Agent

1. Login to Horizon View Connection Server (Primary)

2. Launch the Horizon Broker Agent settings wizard (Run as Administrator)

3. Test and Pair the connection server with Horizon Adapter using the pairing credential. Click Next

4. Provide Horizon Administrator credential using the Active Directory Service Account

5. Enter the Events DB credentials (Use the SQL User account configured for View Events Database

6. Add the App Volumes Managers: (Enter the IP Addres or FQDN of App Volumes Manager instances with a Active Directory Service Account used for AVM integration.

7. Choose default timeout values and click Next

8. Default logging levels for Broker. Default is good for most circumstances

9. Ensure Broker Agent service status shows Running

10. Review the summary and click Finish to complete the configuration wizard.

11. Verify that the View Adapter is now listed as “Collecting” and “Data Receiving”

12.  Configuring vROPS Horizon View Broker Agent is complete!

Adding Nvidia GPU Management Pack in VROPS

1. In vROPS UI, go to Administration tab, click on Solutions, click + to create a new solution



2. Select the Nvidia vGPU vROPS Management Pack (NVIDIA_vGPU_Management_Pack_1.1.25168221_signed.pak)



3. Click Upload and then click Next



4. Accept the EULA and click Next to start the PAK installation



5. Click Finish the complete the PAK installation



6. Select Nvidia Virtual GPU solution and click the Gear icon to configure



7. Add the vCenter Server for Nvidia and provide the credentials, test the connection and save the settings



8. Click Close to complete the Nvidia GPU Management Pack in VMware vROPS.

there is no direct method to disable unused NIC ports in VMware ESX/ESXi. However, we may perform the below workaround using a utility called vmkchdev (VMkernel Change Device) to change the way of passing a particular device to be controlled by either the VMkernel or as a passthrough device to a virtual machine.


CAUTION: This is using an undocumented utility. You should test this out in a development/lab environment before using it in a production environment.

By passing the device over as a passthrough device, the vmnic is actually unrepresented to the VMkernel and does not show up under network adapters or even the unused/unlinked adapter list in the vSwitch configurations.

Here is an example of passing one of the NIC port as a passthrough which I did in lab:


Identify the vmnic's PCI slot, we do by running the "-l" (I used unused NIC vmnic9)

Command: vmkchdev -l | grep vmnic9


Pass the device from the VMkernel to passthrough/VM using the "-p" flag and specifying the PCI slot, which in this case it is 00:05:00.3

Command: vmkchdev -p 00:05:00.3

Refresh the network section so the changes are reflected in the vSphere Client by using vim-cmd

Command: vim-cmd /hostsvc/net/refresh


Device type changed from vmkernel to Passthrough. We can run the same command to list the device.

Command: vmkchdev -l | grep vmnic9



Check the NIC List using the output of esxcfg-nics and the vSphere Client, you will notice that vmnic9 is no longer listed as a vmkernel device.

Command: esxcfg-nics -l



If you would like to enable or re-present the vmnic as vmkernel device, you just need to pass the device back over to VMkernel by using the "-v" flag and refresh host network section.

Command: vmkchdev -v 00:05:00.3

Command: vim-cmd /hostsvc/net/refresh

To automatically persist this change across reboots, specifically for ESXi as changes are not saved, we need to add the following lines to /etc/rc.local which will execute the disabling of the vmnic's after bootup.

Command: vi /etc/rc.local

Edit and save the file with the below lines.


You will also need to run /sbin/ to ensure the changes to /etc/rc.local are saved and reloaded upon the next reboot.

Command: /sbin/