VMware End-User Computing: Design — Lesson 4: Sizing, concurrency, storage performance, availability, disaster recovery, monitoring, user-experience metrics, lifecycle, and operational handover

Learning Objectives

• Assess dependencies, controls, resilience, and the intended service outcome for Sizing, concurrency, storage performance, availability, disaster recovery, monitoring, user-experience metrics, lifecycle, and operational handover.
• Demonstrate the workflow and leave reproducible evidence in capacity model and EUC design validation pack.
• Recommend a preventive improvement after resolving peak login demand exhausting resources before monitoring thresholds trigger.

Detailed Topics

• Sizing
• Concurrency
• Storage performance
• Availability
• Disaster recovery
• Monitoring
• User-experience metrics
• Lifecycle
• And operational handover
• Decision ownership, prerequisites, and acceptance evidence for Sizing, concurrency, storage performance, availability, disaster recovery, monitoring, user-experience metrics, lifecycle, and operational handover
• Relevant access, security, capacity, dependency, performance, recovery, and support considerations

Instructor Demonstration

The instructor configures and tests Sizing, concurrency, storage performance, availability, disaster recovery, monitoring, user-experience metrics, lifecycle, and operational handover within a scenario aimed at an end-user computing design that aligns personas, application delivery, desktop architecture, security, availability, capacity, and operational support with measurable user experience. The walkthrough contrasts a valid setup with a flawed one and uses capacity model and EUC design validation pack to make the difference explicit.

Hands-On Exercise

Work through a role-based scenario involving Sizing, concurrency, storage performance, availability, disaster recovery, monitoring, user-experience metrics, lifecycle, and operational handover. Validate the expected path, test “peak login demand exhausting resources before monitoring thresholds trigger,” choose the safest corrective action, and capture the reasoning and outcome in capacity model and EUC design validation pack.

1. Map the current workflow and mark where the expected result can first be observed.
2. Run the scenario while preserving timestamps, object identifiers, and relevant output.
3. Apply a reversible correction only after evidence supports the cause.
4. Retest the original case plus an unaffected case and update the handover record.

Scenario Analysis

• Clarify the service trigger, affected components and roles, prerequisites, and acceptable result for Sizing, concurrency, storage performance, availability, disaster recovery, monitoring, user-experience metrics, lifecycle, and operational handover.
• Compare at least two implementation or correction choices and identify which evidence would distinguish them.
• Decide how capacity model and EUC design validation pack should be reviewed, approved, retained, and handed to the next owner.

Troubleshooting Guidance

Avoid changing multiple settings at once while troubleshooting Sizing, concurrency, storage performance, availability, disaster recovery, monitoring, user-experience metrics, lifecycle, and operational handover. Preserve the failing example, review capacity model and EUC design validation pack, and verify whether “peak login demand exhausting resources before monitoring thresholds trigger” is the root cause. After remediation, confirm downstream effects and add a monitoring action.

Validation Checklist

• Configuration and source state used for Sizing, concurrency, storage performance, availability, disaster recovery, monitoring, user-experience metrics, lifecycle, and operational handover are versioned or otherwise traceable.
• Capacity model and euc design validation pack shows both baseline and accepted result.
• Security, performance, dependency, and resilience side effects are considered where relevant.
• Recovery steps and handover notes are usable by an operations practitioner.

Lesson Outcome

Learners can apply Sizing, concurrency, storage performance, availability, disaster recovery, monitoring, user-experience metrics, lifecycle, and operational handover, explain the decisions made, and defend the result with capacity model and EUC design validation pack.