1.0.2
Table Of Contents
- Lifecycle Manager Administration Guide
- Contents
- Updated Information
- About This Book
- Understanding LCM
- Installing LCM
- Migrating from LCM 1.0.1 to LCM 1.0.2
- Configuring LCM
- Check Configuration Readiness
- Initial Configuration of Lifecycle Manager
- Configure the LCM Webview
- Set Approval Requirements
- Configure Archiving Settings
- Change Authorization Groups
- Change the Base Name for Virtual Machines
- Enable Email Notifications
- Configure Email Notification Content
- Configure Currency and Date Formats
- Customizing the User Interface
- Setting Up the Virtual Machine Environment
- Using LCM
- LCM Administrator’s Interface
- Request a Virtual Machine
- Display Requested Virtual Machines
- Modify Request Options
- Check the Power State of a Virtual Machine
- Power a Virtual Machine On and Off
- Connecting to a Virtual Machine
- Create or Revert to a Snapshot
- Generate Reports
- Register Virtual Machines with LCM
- Activate Webview Debug Mode
- Relink Tokens to Virtual Machines
- Check Licensing Status
- Export Logs and Application Settings
- Troubleshoot LCM
- Index
Lifecycle Manager Administration Guide
16 VMware, Inc.
To disable access to workflows from Web service clients
1 NavigatetothefollowingfolderontheOrchestratorserversystem.
<installation_directory>\VMware\Orchestrator\app-server\server\vmo\conf
2Openthevmo.propertiesconfigurationfileinatexteditorandaddthefollowingline.
#Disable Orchestrator client connection
com.vmware.o11n.web-service-disabled = true
Ifthevmo.propertiesconfigurationfiledoesnotcontainthisproperty,orifthepropertyissettofalse,
OrchestratorpermitsaccesstoworkflowsfromWebservices.
Installation Requirements
BecauseLCMrunsasanOrchestratorplug‐in,thesystemrequirementsofthetwoproductsarethesame.For
detailedinformationaboutOrchestratorsystemrequirements,seethevCenterOrchestratorInstallationand
ConfigurationGuide.
BeforeyouinstallLCMonMicrosoftWindows,makesurethatyoursystemmeetstheinstallation
prerequisites.
Table 2-1. Installation Prerequisites
Component Description
VMwarevCenterOrchestrator4.0
VMwarevSphere
™ vCenter4.0incompatibilitymode(default)
TheSyspreputilityfortheguestOSmustbeavailableintheproper
directoryonthevCenterServer.
VMwareESX
™ SupportforESXdependsontheversionofvCenterthatyouareusing.
See thedocumentationfortherelevantversionofvCenter.
SampleActiveDirectorygroupsthat
correspondtoLCMroles
Therolesare:
LCMAdministrator
LCMITStaff
LCMApprover
LCMTechRequester
LCMRequester
StaticaccountforeachvCenterServerthat
LCMandOrchestratorcanuse
AppropriatepermissionsfortheLCM
groups
Includethefollowingpermissions:
AllowtheOrchestratorAdministratortodeployfromvCenter
templates
RDPaccessintheguestoperatingsystem
UsexrdpforLinuxvirtualmachines
LCMdatabase Chooseoneofthefollowing:
UsethesamedatabaseasOrchestrator
UseaseparatedatabaseforLCM(recommended)
N
OTE Because ofCPUandmemoryusage,VMwarerecommendsthatyou
hosttheLCMdatabaseandtheOrchestratorserverondifferentmachines
onalocalnetworkwithlowlatency.
ActiveDirectorydomain
DHCPserverandfixedrangeofIP
addressesfornewvirtualmachines