Configuring the jump server

End of Marketing: As of 31 October 2025, new deployments of VMware Solutions offerings are no longer available for new customers. Existing customers can still use and expand their active VMware® workloads on IBM Cloud®. For more information, see End of Marketing for VMware on IBM Cloud.

Now that the jump server is ordered and available for connection on its public IP address from your laptop, you can follow these steps:

  1. Change the Domain Name Services (DNS) client so that it points to the VMware Cloud Foundation for Classic - Automated instances - Active Directory™ DNS (AD/DNS) server instead of the IBM Cloud® DNS resolver. It allows name resolution for components, such as the vCenter appliance and VMware NSX-T™ Manager. The VSI has two Ethernet interfaces, one for the private network and one for the public network.
  2. Download software that enables administration functions, such as mRemoteNG and Firefox®.
  3. Install PowerCLI. PowerCLI is a collection of PowerShell Modules to manage VMware® infrastructure, including network, storage, virtual machine (VM), and guest OS.

Changing DNS

  1. In the VMware Solutions console, click Resources > VCF for Classic from the left navigation panel.

  2. Select the instance and click the Access information tab to capture the IP address of your AD/DNS servers DNS1 and DNS2.

  3. From your laptop, use an RDP client to access the jump server.

  4. When connected to the jump server, open a PowerShell console with admin privileges.

  5. Use Get-DNSClientServerAddress to display the interfaces and their parameters. You need to capture the Interface Indexes IF1 and IF2 for the Ethernet interfaces for use in the next command.

  6. Use the following command to change the first interface: Set-DNSClientServerAddress –interfaceIndex <IF1> –ServerAddresses (“<DNS1>”,“<DNS2>”). For example, Set-DNSClientServerAddress –interfaceIndex 11 –ServerAddresses (“10.38.207.132”, “10.38.207.133”).

  7. Use the following command to change the second interface: Set-DNSClientServerAddress –interfaceIndex <IF2> –ServerAddresses (“<DNS1>”,“<DNS2>”). For example, Set-DNSClientServerAddress –interfaceIndex 15 –ServerAddresses (“10.38.207.132”, “10.38.207.133”).

  8. Use the command Get-DNSClientServerAddress to verify the interfaces and their parameters.

Downloading the software

Open a PowerShell window and use the following commands to download and install mRemoteNG and Firefox.

Invoke-WebRequest -Uri https://github.com/mRemoteNG/mRemoteNG/releases/download/v1.76.20/mRemoteNG-Installer-1.76.20.24615.msi -OutFile C:\Users\Administrator\Downloads\mRemoteNG-Installer-1.76.20.24615.msi
Invoke-WebRequest -Uri "https://download.mozilla.org/?product=firefox-msi-latest-ssl&os=win64&lang=en-GB" -OutFile C:\Users\Administrator\Downloads\firefox-msi-latest.msi
cd C:\Users\Administrator\Downloads
.\mRemoteNG-Installer-1.76.20.24615.msi
.\firefox-msi-latest.msi

Installing PowerCLI

PowerShell is installed by default with Windows® Server. However, PowerCLI needs to be installed from the PowerShell gallery.

  1. Install VMware PowerCLI by entering Install-Module -Name VMware.PowerCLI.
  2. At the prompt, enter Y.