1Y0-312 Citrix Virtual Apps and Desktops 7 Advanced Administration Questions and Answers

ns.log

aaad.debug module

Wireshark trace

nsvpn.log

The PowerShell command New-DatabaseConfiguration must be run prior to updating the Administration Console.

The Agent must be upgraded prior to upgrading the Administration Console.

The associated .DLL files must be updated using the command-line interface after upgrading the Administration Console.

The infrastructure service and the database must be upgraded prior to upgrading the Administration Console.

It is recommended to NOT use both WEM Application Security and Windows AppLocker interfaces at the same time to manage rules.

Application Security rules set to "Audit" are still enforced.

Exported Windows AppLocker rules CANNOT be imported into WEM.

It provides control over which applications users are permitted to run on a given machine.

Deployments that use Citrix Provisioning with a write cache drive.

Deployments that use the Delivery Controllers or Controller SIDs policy setting.

Deployments that do NOT use Controller groups.

Deployments that use ListOfSIDs.

On a Common Internet File System (CIFS) share location on the local domain file share server

On the Repository located on the local storage of the Enterprise Layer Manager (ELM)

On the Server Message Block (SMB) file share configured from the Citrix App Layering management console

On local storage attached to the hypervisor platform being used to create the images

TCP port 443 is NOT open between the VDA and Delivery Controllers on the Disaster Recovery Site

The VDA is configured with a GPO to register with the Delivery Controllers from the Production Site

The Delivery Controllers were set manually during VDA configuration and point to the Production Site

The Delivery Controllers in the Disaster Recovery Site were NOT able to contact the Delivery Controllers in the Production Site to complete the registration process

Citrix Analytics

Citrix Configuration Logging Service

Citrix Broker Service

Citrix Configuration Service

1000; Advanced

1000; Rules

500; Advanced

500; Rules

Cross-Platform Settings

Synchronization

Profile Handling

Streamed User Profiles

It can be updated directly using the Citrix App Layering Management console.

Its purpose is to create a template that outputs to a virtual machine (VM) or a virtual disk.

It has limited use-case scenarios, such as making minor updates to an App Layer.

It is used every time changes are made, and a Platform Layer is being published.

It is only supported as an on-premises solution for Citrix App Layering.

It is used to manage system settings for Citrix App Layering.

It is used to add layered images into Citrix Studio.

It is a web-based console that runs on the Enterprise Layer Manager (ELM) server.

It coordinates all communications within the Citrix App Layering environment.

The Agent would need to contact the Infrastructure Service after restart to gather cache data again

The cache is lost at each restart without a persistent disk

The environment is NOT supported because the usage of a persistent disk is mandatory when using WEM

The WEM Agent applies real time updates only when the persistent disk is used

Templates are NOT required when creating a VHD file for a Citrix Provisioning deployment.

To minimize management effort, use the same template to generate layered images for each hypervisor platform used.

Templates are NOT supported for use with physical machine imaging platforms.

After machines are provisioned from a layered image, delete that layered image to reduce storage consumption.

It hosts the SMB file share for the Elastic Layers data.

It manages and maintains copies of all layers and layered images.

It is a Windows-based virtual appliance maintained on the hypervisor.

It hosts the Citrix App Layering Management Web Console.

It coordinates all communication within the Citrix App Layering imaging process.

It hosts the secondary file share for User Layer profile data.