1Y0-201 · Question #136
Users report that when they work remotely on weekends, they experience noticeably longer desktop launch times. Which action should a Citrix Administrator take to resolve this issue?
The correct answer is D. Increase the number of active machines during the weekends. Longer desktop launch times on weekends indicate that fewer machines are pre-started and available, so increasing the number of active machines during that period ensures users connect to already-booted desktops instead of waiting for cold starts.
Question
Users report that when they work remotely on weekends, they experience noticeably longer desktop launch times. Which action should a Citrix Administrator take to resolve this issue?
Options
- ASet peak hours for the weekend.
- BAnalyze the logon times in Citrix Director.
- CSchedule the weekend backups to run at night.
- DIncrease the number of active machines during the weekends.
How the community answered
(28 responses)- A14% (4)
- B4% (1)
- C7% (2)
- D75% (21)
Why each option
Longer desktop launch times on weekends indicate that fewer machines are pre-started and available, so increasing the number of active machines during that period ensures users connect to already-booted desktops instead of waiting for cold starts.
Setting peak hours for the weekend configures power management scheduling, but without also increasing the number of machines that should be active during those hours, it does not guarantee more machines are pre-booted and available.
Analyzing logon times in Citrix Director is a diagnostic step that identifies where delays occur but does not resolve the underlying shortage of pre-started machines.
Rescheduling weekend backups to run at night may reduce storage I/O contention but does not address the root cause, which is an insufficient number of powered-on machines available during peak remote usage times.
Desktop launch delays are typically caused by machines needing to power on and complete their boot sequence before a session can be established. By increasing the number of pre-started (active) machines scheduled for weekends via Delivery Group power management settings, the administrator ensures a pool of ready machines is available, eliminating the boot-time delay for remote weekend users.
Concept tested: Delivery Group power management and pre-started machine count
Source: https://docs.citrix.com/en-us/citrix-virtual-apps-desktops/install-configure/delivery-groups-manage.html#manage-power-management-settings
Topics
Community Discussion
7
Samuel O.Dec 5, 2025D is your answer. When remote users hit slow desktop launches on weekends, the root cause is almost always that your delivery group does not have enough powered-on machines ready to hand out sessions, so users sit there waiting for a machine to boot instead of connecting instantly, and the fix is to bump up the number of machines in the active powered-on state during those weekend hours.
Bao N.Dec 8, 2025Samuel is right that powered-on capacity is the first thing to check, but do not overlook whether your weekend schedule in Autoscale is actually configured to match your real peak hours, because a correct buffer count set against the wrong time window gets you nowhere.
Hiroshi T.Dec 29, 2025Option B is tempting but diagnosis is not resolution; D is correct.
Giselle K.Dec 9, 2025D is right, but let me push back on A for a second because it trips people up. Setting peak hours on the weekend sounds logical, and it does matter for power management scheduling, but peak hours alone do not spin up more machines if your delivery group is not configured to pre-launch or buffer sessions against that schedule. The actual problem is that on weekends the machine catalog is sitting near its minimum buffer, so users are waiting for machines to power on and register before they can connect, which is your long launch time right there. You fix that by increasing the number of machines kept in a powered-on and registered state during weekend hours, whether that is through peak period settings tied to a higher machine count or a manual adjustment to your power management policy that keeps more machines active when remote workers are logging in.
Fatima Z.Jan 4, 2026Okay so think of Peak Hours like a restaurant that only preps food during dinner rush, Monday through Friday. If nobody told the kitchen that Saturday and Sunday are ALSO busy now, the cooks show up late and users are sitting there twiddling their thumbs waiting for their virtual desktop to warm up. That is exactly what is happening here, the Delivery Controller is not pre-launching machines on weekends because it thinks those are off-peak ghost-town hours. Setting peak hours for the weekend tells Citrix to have those machines ready and waiting like a good host at the door, so launch times drop immediately. My hook for this is PREP, Peak hours = Ready Environment Pre-launch, and when the environment is not prepped, users wait.
Bao N.Dec 25, 2025Slow desktop launch on weekends screams a logon bottleneck to me, and Director is exactly where you dig into that because it breaks down every phase of the logon process so you can see whether the delay is in profile load, GPO processing, or something else entirely. Without that data you are just guessing, and B gives you the visibility you need before you start changing anything.
Giselle K.Dec 27, 2025Good point on Director for logon analysis in general, Bao, but the weekend-specific pattern points to power management schedules in the delivery group, which is why D is correct here. If the schedule is powering down machines over the weekend, users are waiting on cold starts, and that is the first thing to check before you ever open Director.