VMware Tools pre-installed on Vault VM before CyberArk installation — will Vault installation or hardening process disable or conflict with it?

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

VMware Tools pre-installed on Vault VM before CyberArk installation — will Vault installation or hardening process disable or conflict with it?

L0 Member

We are deploying CyberArk Vault on a VMware VM. Our infrastructure team will provision the vault VM with VMware Tools already installed before we begin vault installation and hardening.

 

We are aware of the existing community thread on VM tools installation on the Vault, which discusses installing VMware Tools on an already hardened vault using the WSUS script to temporarily enable Windows Installer service.

 

Our specific question is about sequencing: will the CyberArk Vault installation process and/or hardening script disable or conflict with VMware Tools that is already pre-installed on the VM? Or should we remove VMware Tools before beginning vault installation and hardening, and reinstall afterward using the WSUS script approach?

 

What is the recommended sequence?

5 REPLIES 5

L7 Applicator

Hey @Madhav Bhasin​ 

The supported installation is on a completely vanilla OS, and this includes not having VMware tools installed. If you run into any issues with the Vault then support will have a difficult time helping due to the unsupported installation setup.

 

You should reimage the machine - uninstall of VMware Tools may not be enough - not install VMware tools right away, and then install the Vault from a completely vanilla OS. If VMware tools are required, installing them after the Vault installation is completed can def be done, but definitely should not be done before.

 

Good luck!

 

-Matt

Hello Matt,

 

Thanks for your input,

Her my experience on this topic, I had the same question and use case, after some investigation and asking the support feedback on this, installing VMTools after the Vault it's not an gig issue (regardless the Vault should be a clean vanilla machine - agree), however, my argument was or is that the Vault hardening will block the communications between the VMTools app engine and the Hypervisor (ESXi OS), and this is also was the support opinion.

 

If this is the case, what is the point of installing VMTools in the first place if the Hypervisor can't manage or see the VM configurations, status, etc. Which is the purpose of the VMTools on a VM.

 

I look forward to hear your feedback

 

Thank you

Have a nice day

Anan

@Abdichakour Ahmed​ 

I agree with Support on this; I don't think it's good to install VMware Tools on the vault.

 

-Matt

L0 Member

Thanks for the responses. To clarify our specific use case:

 

We have a business requirement from our infrastructure team to use VMXNET3 paravirtual NIC drivers on our vault VM for network performance. Without these drivers, the VM falls back to E1000 legacy emulation, which is insufficient for our production environment.

 

Based on the WSUS script documentation and the posts here, our proposed sequence is:

  1. Deploy vanilla vault VM (no VMware Tools pre-installed)
  2. Run CyberArk prerequisite scripts and vault installation with hardening
  3. Execute OpeningServices.ps1 (WSUS script) to temporarily enable Windows Installer service
  4. Install VMware Tools (loads and attaches VMXNET3 adapter)
  5. Verify VMXNET3 driver is loaded and functional
  6. Execute ClosingServices.ps1 to re-harden and disable Windows Installer service

 

Our understanding is that VMXNET3, once loaded and attached to the VM, remains functional post-hardening because the driver

operates at the kernel level and doesn't require ongoing VMware Tools service communication.

 

Can anyone confirm this understanding, or flag any known issues with VMXNET3 persistence after re-hardening?

Hello,

 

Except to Matt's reply above & it's not support to have 3rd-party apps on the vault, in my experience, the short answer there is no issue to install VMTools on a hardened Vault. That said, if in your case you are sure that the root cause is VM's NIC falls back to E1000 and this is the only workaround. Which I'm not sure why, basically VMXNET3 NIC config it's at the VM creation level regardless (hardware shell config) if VMTools is installed or not if I'm not mistaken.

 

Does it happen to other VMs, or only the Vault? Have you tried a lab for to try new VM with/out Vault app? etc.

It's subject to test and further investigation I'd check the Physical (ESXi) NICs and the Switches; Drivers, Firmware, ESXi version, etc.

 

Q: what is "CyberArk prerequisite script" ?!

 

Thank you

Anan

  • 76 Views
  • 5 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!