Configuring and Operating Microsoft Azure Virtual Desktop: Troubleshooting Slow Session Host Deployment

Troubleshooting Slow Session Host Deployment

Question

You decide to add a new image to the Shared Image Gallery definition.

This image is utilized for a large-scale Azure Virtual Desktop deployment with 60 Session Hosts.

While deploying, you notice that the new session host process is somewhat slow and it gets time out.

Which of the following steps would you take to resolve this issue?

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

Correct Answer: B

Each image replica can create up to 20 VMs at a time.

Therefore, to implement 60 Session Hosts, 3 replicas are recommended.

Replicating the image to different regions won't help as the Session Hosts are built with the replica in the deployment region.

Option A is incorrect.

Each image replica can create up to 20 VM's at a time.

Therefore, to implement 60 Session Hosts, 3 replicas are needed.

Option B is correct.

Increasing the replica count to 3 in the deployment region will help in resolving the issue of slow speed and time out.

Option C is incorrect.

6 replicas would be needed if there would have been 120 session hosts.

Option D is incorrect.

Replicating the image to different regions won't help as the Session Hosts are built with the replica in the deployment region.

Option E is incorrect.

Replicating the image to different regions won't help as the Session Hosts are built with the replica in the deployment region.

When deploying a large-scale Azure Virtual Desktop deployment with 60 Session Hosts, it's important to ensure that the new session host process is running smoothly and not timing out. To address this issue, you should consider replicating the image to multiple regions.

Replication of the image to multiple regions helps to improve the overall performance of the deployment by reducing the latency for accessing the image. This can help to ensure that the session host process runs smoothly and does not time out.

Option D suggests replicating the image to 10 different regions, which may provide better performance and ensure that the image is readily available to all Session Hosts across multiple regions. However, replicating the image to 10 regions may not be necessary, and it may add additional cost to the deployment.

Option E suggests replicating the image to 5 different regions, which may provide a good balance between performance and cost. This option may be sufficient to ensure that the image is available to all Session Hosts across multiple regions, without incurring too much additional cost.

Therefore, the best option to resolve the issue of slow session host process and timeouts would be to replicate the image to multiple regions, such as Option D or Option E. However, Option E may be more cost-effective and may provide sufficient performance.