Splunk® App for VMware (Legacy)

Installation and Configuration Guide

On August 31, 2022, the Splunk App for VMware will reach its end of life. After this date, Splunk will no longer maintain or develop this product. The functionality in this app is migrating to a content pack in Data Integrations. Learn about the Content Pack for VMware Dashboards and Reports.
This documentation does not apply to the most recent version of Splunk® App for VMware (Legacy). For documentation on the most recent version, go to the latest release.

Answers

Have questions?

Visit Splunk Answers to see what questions and answers other Splunk users had about Splunk for VMware.

Question: Do I need to validate the service accounts I create on each VC and each ESX/i hosts?

Answer: Yes. A common mistake is for users to create a service account and validate that it works on VC, assuming that this will also affect all of their ESX/i hosts. This is an incorrect assumption. VC and ESX/i hosts have completely independent security subsystems, so you must do the creation / mapping steps in this topic for each VC and ESX/i host independently, and then validate each one independently.

Last modified on 12 July, 2013
credentials.conf.spec   How to get out of trouble

This documentation applies to the following versions of Splunk® App for VMware (Legacy): 1.0, 1.0.1, 1.0.2, 1.0.3, 2.0


Was this topic useful?







You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters