Let’s do an example. Let’s say you have 3 datastores on your VMware host and you want the SVA to be on the third datastore. During setup it will simply ask you for the datastore number you want to install to. In this case you would type 3 and hit enter. My thoughts are is that you have to figure out your datastore problem. Here is the specific wording from the xml file
========== ========== ========== ======
# Datastore Selection prompt to install the SVA
# 0 - Automatically install the SVA on the first datastore detected
# 1 - Prompt to select datastore from available ones detected
========== ========== ========== =======
One other thing is to check to make sure the user you are defining inside the SVA_InstallSettngs.XML file has the admin level access inside VMware to make all the changes required as part of the install.
I am being told by Symantec Support the versions of vshield and ESXi I am using are not supported by Symantec Endpoint Protection Manager 12.1.2. I am using vShield Endpoint 5.1, vShield Manager 5.1 and ESXi 5.1. What version did you use for your setup?
A VMware Administrator can use the SVA installation tool with the "forceclean" option to remove the orphaned SVA entries from VMware vShield Manager. The forceclean option parses through the entire vCenter inventory of managed object ID's (moid), and removes the orphaned Symantec Endpoint Protection SVA entries from VMware vShield Manager.<<Also by default client and SEPM server is communicating via port no 8014. We should see traffic from those guest if they are configured correctly as expected.
Java –jar Symantec_SVA_install.jar –s SVA_InstallSettings.xml –forceclean
I was having the same issue as above and found a VM article that states the EPSEC driver needs the guest image to be restarted. I restarted my guest, and they started working.
After weeks of working with Symantec Support and escalating the ticket, Symantec finally found an issue with the SVA_INSTALLSETTINGS.XML file. Apparently the file has some of the relevant config settings commented out. You need to make sure there aren't any <!-- or --> symbols around any of the config settings related to the ESX hosts or VCENTER communications. I believe it was my SVA NETWORK CONFIGURATION that was commented out for some reason. After reinstalling ALL the SVAs, the clients started displaying their SVA.
By default, Shared Insight cache is setup with no authentication and no SSL. As such, the default setting for the password is null. In other words, the password is blank. If you set Shared Insight Cache to Basic authentication with SSL or Basic Authentication with no SSL, you must specify a username's password that can access Shared Insight Cache.
After deploying an SVM to an ESX host, the Endpoint Status panel does not report the status of that SVM. This is because the vShield Manager does not propagate some configuration parameters to the SVM until an inventory change occurs in the vCenter Server. Workaround: Perform an inventory change in the vCenter Server, such as suspending and then resuming that virtual machine.
On the EPSec status page, events may be reported for the wrong VM if two or more VMs share the same BIOS UUID. Workaround: Change the UUID of one or more of the virtual machines. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1002403
One of these versions:
ESXi 5.0 Update 1
ESX 4.1, with Patch ESX410-201107001
One of these versions:
VMware vShield Manager 5.1 with VMware vShield Endpoint 5.1
VMware vShield Manager 5.0 Update 1 with VMware vShield Endpoint 5.0 Update 1
Note: You must use vShield Manager to deploy vShield Endpoint to each host you want to manage.
Have you met the pre-requites?