Virtualization, Cloud, Infrastructure and all that stuff in-between

My ramblings on the stuff that holds it all together

Problem with Installing vCenter Chargeback – cannot configure with SQL Windows Authentication

 

I am setting a trial of the new vCenter Chargeback product on my lab environment, and have followed the instructions to configure the SQL database (new DB and new account with database owner permissions) however when I try to configure the Windows application I get errors from the jdbc component as follows;

“The user is not associated with a trusted SQL Server connection”

If I try with the appliance version of the application it ignores the slash in the DOMAIN\USER syntax for the database permissions and puts in DOMAINUSER, which obviously doesn’t work.

for now I have configured it using SQL authentication and that works ok isn’t ideal from a management point of view, would be good to understand why this is, as the appliance issue looks like a bug to me.

Advertisements

4 responses to “Problem with Installing vCenter Chargeback – cannot configure with SQL Windows Authentication

  1. naveen July 16, 2009 at 3:59 am

    VMware vCenter Chargeback does not support windows authentication in version 1.0

    • vinf July 16, 2009 at 9:05 am

      Thanks, Naveen that would explain it then 🙂

  2. Abhi October 28, 2009 at 5:14 am

    vCenter Chargeback 1.0.1 is available now with support for SQL Server Windows Authentication.

    Text from http://communities.vmware.com/docs/DOC-11005….

    vCenter Chargeback 1.0.1 provides the following new features:

    * Support for Windows Authentication
    This release of vCenter Chargeback supports Windows Authentication for SQL Server databases. If you are using SQL Server for the vCenter Chargeback database or for the vCenter Server database, then you can configure the application to use Windows Authentication instead of SQL Authentication.
    * New computing resource and billing policies added
    This release of vCenter Chargeback introduces a new computing resource, vCPU, and two new billing policies, vCPU Count and Memory Size and Fixed Cost and vCPU Count and Memory Size. These policies enable you to calculate cost based on the number of virtual CPUs and the amount of memory allocated to the virtual machines.
    * Resource Summary section lists rolled-up usage data for all entities
    The Resource Summary section of the chargeback reports show the rolled-up usage data for all the entities.
    * Global fixed cost history is retained
    This release of vCenter Chargeback lets you to set different cost values for different time periods on the same global fixed cost. The old values are retained and not overwritten.
    * Ability to undo to the most recent operation on the chargeback hierarchy
    The most recent operation on the chargeback hierarchy can be undone. This undo feature is available for entities that are added or moved in the hierarchy. The undo option is not available for rename and delete operations.
    * Ability to use the vCenter Chargeback APIs
    vCenter Chargeback APIs provide an interface to programmatically use the various features of vCenter Chargeback. As an application developer, you can use these APIs to build chargeback applications or integrate vCenter Chargeback with your internal billing systems and compliance policies. Please do note that the APIs released with this version of vCenter Chargeback are only for a technical preview.

    • vinf October 28, 2009 at 10:49 am

      Thanks – will check it out

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: