Eric Sloof

VMware Identity Manager is an authentication and application access portal that provides a single point of application provisioning and entitlement for enterprise desktop and mobile users. Although this paper describes on-premises deployment, VMware Identity Manager is also offered for Software as a Service (SaaS) deployment.

This paper describes general considerations and best practices for planning an on-premises VMware Identity Manager™ deployment, including sizing, design, and gathering of critical environment data.

However, because every environment is unique, each deployment of VMware Identity Manager is unique as well. VMware recommends that you consult the VMware Professional Services Organization (PSO) or one of our certified partners for assistance in designing an implementation that meets your specific requirements. VMware Identity Manager is compatible with View in Horizon 7 and Horizon 6 as well as with other earlier releases.

This utility connects to App Volumes 2.x, 3.x and Horizon Air Hybrid-Mode (Enzo) environments, pulling data from the native REST APIs into a single interface for ease of management. Configuration items such as deleting AppStacks and managing Writable Volumes, which are not available in the App Volumes 3.x interface, are easily managed with this utility. The utility leverages native REST API calls for all actions.

The goal of this design guide is to outline several NSX solutions available for multi-site data center connectivity before digging deeper into the details of the Cross-VC NSX multi-site solution.

Learn how Cross-VC NSX enables logical networking and security across multiple vCenter domains/sites and how it provides enhanced solutions for specific use cases.

No longer is logical networking and security constrained to a single vCenter domain. Cross-VC NSX use cases, architecture, functionality, deployment models, design, and failure/recovery scenarios are discussed in detail.
 
This document is targeted toward virtualization and network architects interested in deploying VMware® NSX Network virtualization solution in a vSphere environment.


The design guide addresses the following topics:

• Why Multi-site?
• Traditional Multi-site Challenges
• Why VMware NSX for Multi-site Data Center Solutions?
• NSX Multi-site Solution

It also covers the Cross-VC NSX:

• Use Cases
• Architecture and Functionality
• Deployment Models
• Design Guidance
• Failure/Recovery scenarios

The Horizon Migration Tool helps you migrate published applications and desktops from XenApp to Horizon View. One XenApp farm is migrated to one or more Horizon View farm(s). The GUI wizard-based tool helps you:

• Validate the View agent status on RDS hosts (from View connection server, and XenApp server)
• Create farms
• Validate application availability on RDS hosts
• Migrate application/desktop to one or multiple farms (new or existing)
• Migrate entitlements to new or existing applications/desktops. Combination of application entitlements are supported
• Check environment
• Identify incompatible features and configuration

This free e-learning course demonstrates how VMware vRealize Operations Manager delivers intelligent operations management from applications to infrastructure across physical, virtual, and cloud environments. After completing the program, you should be able to:

• Explain how an analytics-based operational process addresses the challenges of IT operations
• Name the three main use cases for intelligent operations 
• Describe how the architecture of vRealize Operations Manager supports scalability, reliability, and extensibility
• Summarize the process to deploy vRealize Operations Manager
• Recognize how vRealize Operations Manager helps IT Operations: 
• - Optimize utilization
• - Ensure performance and availability across the software-defined data center (SDDC)
• - Monitor heterogeneous data centers and hybrid clouds
• Browse for solutions to extend intelligent operations from applications to infrastructure across physical, virtual, and cloud environments

You create workflow subscriptions that use the event broker service to monitor the registered services for event messages in vRealize Automation, and then run a specified vRealize Orchestratorworkflow when the conditions in the subscription are met. To configure the subscription you specify the event topic, the triggering conditions, and the workflow that runs when triggered.

Tenant administrators can create and manage the workflow subscriptions that are specific to their tenant. The system administrator can create and manage system workflow subscriptions. The created system workflow subscriptions are active for events in any tenant and for system events.

The machine provisioning and machine life cycle event topics use the same life cycle schema. The differences are in the triggering states. Machine provisioning receives messages based on provisioning states and events, and machine life cycle receives messages based on active states and events. Some provisioning states include BuildingMachine and Disposing. Some life cycle states include InstallTools and Off.

The vRealize Orchestrator parameters are mapped to the event's payload by name and type. The virtual machine custom properties are not included in the event payload unless they are specified as an extensibility custom property for the life cycle state. You can add these properties to IaaSendpoints, reservations, blueprints, requests, and other objects that support custom properties.

For example, if you want to include hidden properties and all properties starting with "Virtual" when the virtual machine state is BuildingMachine, you add the custom properties to the machine in the blueprint. The custom property name for this example is Extensibility.Lifecycle.Properties.VMPSMasterWorkflow32.BuildingMachine, and the values are __* andVirtual*, separated by a comma.

The double underscore (__*) includes the hidden properties. The Virtual* value includes all properties that begin with virtual. The asterisk (*) is a wildcard and can be used as the only value, but using the wildcard this way results in the transfer of large amounts of data.

The custom workflow that you create must have an input parameter that is payload with the type Properties. The provisioning or life cycle event data payload is put in this parameter when the workflow runs in vRealize Orchestrator. You can also include separate input parameters that match the name and the type of the fields in the event's payload.