1Y0-300 Citrix Study Guide Section Three

1Y0-300 Deploying Citrix XenDesktop 7 Solutions Study Guide Section Three

Section 3: Testing Configurations

3.1

 

Testing Aspect: How

 

Task Description: Test backup servers/mirroring/clustering

 

To verify the correct interaction between the XenDesktop site and the mirrored database, use the following sequences of tests:

 

  • Database connectivity on service start-up

 

  • Verify that the service can successfully connect to both database servers.

 

  • Use the information present in the connection string as the service starts up.

 

          AND

 

  • Database connectivity following database failover

 

  • Verify that the services automatically follow the active database between servers when a database failover is triggered.

 

3.2

 

Testing Aspect: How

 

Task Description: Test user experience (is everything working as smoothly as expected)

 

In Studio, both delivery groups and machine catalogs can be tested.

 

  • Click Studio to display the console.

 

  • Select a machine catalog or a delivery group and click Test Machine Catalog or Test Delivery Group, respectively.

 

  • When the test completes the engineer can view a report, resolve any issues and optionally run the test again.

 

3.3

 

Testing Aspect: Why

 

Task Description: Verify the effects of the user profile

 

Automatic configuration with user profiles:

 

  • Delete locally cached profiles on logoff, Profile streaming, and Always cache are enforced by the auto-configuration feature.

 

  • Because Profile streaming is disabled for both persistent and dedicated machines, which includes Desktop OS machines with a static assignment and Personal vDisk created with MCS, the Always cache setting is always ignored.

 

3.4

 

Testing Aspect: Why

Task Description: Verify enumeration of applications and desktops

An engineer is configuring a pilot deployment of StoreFront and NetScaler Gateway to provide remote access to the environment. Test users report that when they log on to the Receiver for Web and they don’t see any applications. The following message is shown instead.

 

  • This issue is most likely caused by incorrect controller configuration in StoreFront.

Comments are closed.