Known limitations and workarounds

This section describes the known limitations and possible workarounds.

Copying VMware machines into another vCenter
Known limitation: When you copy into a vCenter VMware machines, that were created on another vCenter, this operation may create InstanceUUID duplications and cause wrong correlated representations.
Workaround: Create a new unique InstanceUUID for the VMware machine you migrated from one vCenter to another.
Client and Session relevance expressions with a large number of elements
Known limitation: The evaluation of client or session relevance expressions containing a large number of elements could be expensive, and result in the crash of the process running them (Client, Plugin Portal, FixletDebugger, QnA, WebReports, and so on) depending on the hardware or software resources of the machine.
Workaround: Define the client or session relevance expressions with a limited number of elements inside. For example, avoid the use of relevance expressions containing an high number of logical conditions or hundreds of elements in a set.
Computer Name for Windows is limited to 15 characters
Known limitation: The Computer Name property for the Windows agents retrieves the Netbios name of the computer, which is limited to 15 characters. See http://support.microsoft.com/kb/909264.
Workaround: If you want something different from the Netbios name on Windows, you must use a different Inspector (retrieved property). You can use such properties as host name, dns name to provide additional values as needed.
License Key Password is limited to 35 characters
Known limitation: The License Key Password is limited to 35 characters and cannot contain double quotes.
Workaround: Avoid using the double quotes and ensure that the License Key Password is not longer than 35 characters.
Changing the domain of AD/LDAP operators can cause issues on Web Reports
Known limitation: Modifying the domain of AD/LDAP non-master operators causes Web Reports to manage the AD/LDAP user as a different operator. The new operator will not have access to the private reports and to other private objects associated to the original operator.
Workaround: None.
SQL Server Database collation
Known limitation: Some SQL Server collation may not work with BigFix due to incompatible chars used in table names. Known collation not working:
  • SQL_Latin1_General_CP1254_CI_AS
Workaround: Use an alternative collation, such as SQL_Latin1_General_CP1_CI_AS.