Scenario: A Citrix Administrator created a machine catalog using Machine Creation Services. The Desktop Experience was set to 'Random'. Where will the unique information for the virtual machines be…

Question

Options

• AIn the identity disk of each virtual machine
• BIn the PERSONALITY.INI file at the root directory of each virtual machine
• COnly in the Site database
• DIn the differencing disk of each virtual machine

• A
  92% (34)
• C
  5% (2)
• D
  3% (1)

Explanation

In MCS, each virtual machine is provisioned from a shared master image, so unique identity data - including the computer name, Active Directory machine account, and SID - must be stored separately per VM. That per-VM uniqueness lives on the identity disk, a small dedicated disk attached to each machine that persists this information independently of the shared base image.

Why the distractors are wrong:

• B (PERSONALITY.INI): This file is associated with Citrix Provisioning Services (PVS), not MCS - it's a common trap that mixes up the two provisioning technologies.
• C (Site database only): The database holds catalog and brokering metadata but does not store per-VM identity data; the VM itself needs local access to its own unique identity at boot.
• D (Differencing disk): The differencing disk captures runtime OS changes layered on top of the base image, but for Random (non-persistent) catalogs this disk is discarded or reset at logoff - it cannot reliably hold unique identity information.

Memory tip: Think "Identity disk = Individual identity" - every VM gets its own "ID card" disk so it can announce itself to Active Directory with a unique name and SID, no matter how many VMs share the same master image.

No community discussion yet for this question.