1.2.0

Table Of Contents
Check Configuration Readiness
Before you start configuring Orchestrator, you can check whether the Web configuration service is ready.
Procedure
1 In Windows, select Start > Programs > Administrative Tools > Services.
2 Select VMware vCenter Orchestrator Configuration.
3 If the status is not Started, right-click VMware vCenter Orchestrator Configuration and select Start.
Log In to the Orchestrator Configuration Interface
To start the configuration process, you must access the Orchestrator configuration interface.
Prerequisites
The VMware vCenter Orchestrator Configuration service must be running.
CAUTION To avoid potential exploitation of the administrative credentials, change the nonsecure password
when you first access the configuration interface. Retaining the default password might cause serious security
issues in a production environment and is a common cause of data breach.
Procedure
1 Select Start > Programs > VMware > vCenter Orchestrator Web Configuration.
You can also access the Orchestrator configuration interface by entering the following URL address in a
Web browser:
http://
orchestrator_server_DNS_name_or_IP_address
:8282
8282 is the default HTTP access port reserved for the Web UI of Orchestrator configuration. To enable
HTTPS connection through port 8283, you must configure Jetty to use SSL. See Jetty Documentation,
Configuring SSL.
2 Log in with the default credentials.
n
User name: vmware.
You cannot change the vmware default user name.
n
Password: vmware
When you log in to the Orchestrator configuration interface for the first time, you see the installation path, the
Orchestrator version, and the server status in the Information tab. The status indicators of all tabs on the left
display red triangles, indicating that the components are not configured.
What to do next
Select a tab and follow the links in the inspector on the right, entering the necessary information until a green
circle appears on the selected tab. The green circle indicates that your configuration changes are correct and
that all dependencies are met.
Lifecycle Manager Installation and Configuration Guide
28 VMware, Inc.