first-login-vsphere-6-vcsa-vcenter-server-appliance

When login in to the vSphere Webclient for the first time there is one important thing to keep in mind: make sure to use the administrator Account! In my case it’s: vsphere6.localadministrator! If using the the root-account to login, it is possible, but you can´t be sure that you have the required priviliges. Unfortunately I ran into that issue as I intuitively logged in using root and not the administrative account – so make it better.

vmware vcenter single sign on login

Assigning licenses

When logging into vCenter Server Appliance for the first time you find a notification at the top of the website that tells you about licenses to expire and it offers quick access to the licensing view of the webclient. You don’t necessarily have to assign a license. If you just want to use your installation for a short period of time (no longer than 60 days), feel free to skip this step. If you’re planning to keep it for some more time then you should assign a license to the vCenter.

license vsphere

60 Days of trial are a good start, but I need the vCenter Server Appliance for longer. To do so, I use the “Manage your licenses” at the top in the notification the webclient sends me to the licensing tab.

vCenter Server Appliance add license

As you might have noticed I added several license keys at once. I will use them later on after adding ESXi hosts to the vCenter. For now I only assign the vCenter license at Assets in the license category. And right click my new installed vCenter 192.168.99.153 and click Assign License… to switch the license from the Evaluation License to the one I added before.

add vcenter license

There’s a notification to let you know that some features will become unavailable when assigning my license. Of course this is only the case when changing to a license with less features.

license change vcenter

In my case it was the license for the vSphere Storage Appliance. That’s totally fine for me as I don´t need it in this environment.

Summary

The installation of the vCenter Server Appliance 6.0 is finished with these last steps. The next tasks is the installation and connection of VMware ESXi hosts to the vCenter.

CNIL
Metrics and Logs

(formerly, Opvizor Performance Analyzer)

VMware vSphere & Cloud
PERFORMANCE MONITORING, LOG ANALYSIS, LICENSE COMPLIANCE!

Monitor and Analyze Performance and Log files:
Performance monitoring for your systems and applications with log analysis (tamperproof using immudb) and license compliance (RedHat, Oracle, SAP and more) in one virtual appliance!

Subscribe to Our Newsletter

Get the latest product updates, company news, and special offers delivered right to your inbox.

Subscribe to our newsletter

Use Case - Tamper-resistant Clinical Trials

Goal:

Blockchain PoCs were unsuccessful due to complexity and lack of developers.

Still the goal of data immutability as well as client verification is a crucial. Furthermore, the system needs to be easy to use and operate (allowing backup, maintenance windows aso.).

Implementation:

immudb is running in different datacenters across the globe. All clinical trial information is stored in immudb either as transactions or the pdf documents as a whole.

Having that single source of truth with versioned, timestamped, and cryptographically verifiable records, enables a whole new way of transparency and trust.

Use Case - Finance

Goal:

Store the source data, the decision and the rule base for financial support from governments timestamped, verifiable.

A very important functionality is the ability to compare the historic decision (based on the past rulebase) with the rulebase at a different date. Fully cryptographic verifiable Time Travel queries are required to be able to achieve that comparison.

Implementation:

While the source data, rulebase and the documented decision are stored in verifiable Blobs in immudb, the transaction is stored using the relational layer of immudb.

That allows the use of immudb’s time travel capabilities to retrieve verified historic data and recalculate with the most recent rulebase.

Use Case - eCommerce and NFT marketplace

Goal:

No matter if it’s an eCommerce platform or NFT marketplace, the goals are similar:

  • High amount of transactions (potentially millions a second)
  • Ability to read and write multiple records within one transaction
  • prevent overwrite or updates on transactions
  • comply with regulations (PCI, GDPR, …)


Implementation:

immudb is typically scaled out using Hyperscaler (i. e. AWS, Google Cloud, Microsoft Azure) distributed across the Globe. Auditors are also distributed to track the verification proof over time. Additionally, the shop or marketplace applications store immudb cryptographic state information. That high level of integrity and tamper-evidence while maintaining a very high transaction speed is key for companies to chose immudb.

Use Case - IoT Sensor Data

Goal:

IoT sensor data received by devices collecting environment data needs to be stored locally in a cryptographically verifiable manner until the data is transferred to a central datacenter. The data integrity needs to be verifiable at any given point in time and while in transit.

Implementation:

immudb runs embedded on the IoT device itself and is consistently audited by external probes. The data transfer to audit is minimal and works even with minimum bandwidth and unreliable connections.

Whenever the IoT devices are connected to a high bandwidth, the data transfer happens to a data center (large immudb deployment) and the source and destination date integrity is fully verified.

Use Case - DevOps Evidence

Goal:

CI/CD and application build logs need to be stored auditable and tamper-evident.
A very high Performance is required as the system should not slow down any build process.
Scalability is key as billions of artifacts are expected within the next years.
Next to a possibility of integrity validation, data needs to be retrievable by pipeline job id or digital asset checksum.

Implementation:

As part of the CI/CD audit functionality, data is stored within immudb using the Key/Value functionality. Key is either the CI/CD job id (i. e. Jenkins or GitLab) or the checksum of the resulting build or container image.

White Paper — Registration

We will also send you the research paper
via email.

CodeNotary — Webinar

White Paper — Registration

Please let us know where we can send the whitepaper on CodeNotary Trusted Software Supply Chain. 

Become a partner

Start Your Trial

Please enter contact information to receive an email with the virtual appliance download instructions.

Start Free Trial

Please enter contact information to receive an email with the free trial details.