Scenario: After the roll out of a number of major infrastructure changes, users are able to log in to StoreFront for Web and launch persistent Desktop OS machines but NOT pooled-random Desktop OS mach

DHCP scope issues affect IP address allocation for endpoints and VMs; they would not prevent Studio from connecting to the site or block the Broker from assigning pooled desktops.

Reinstalling Citrix Studio is a client-side action that would not resolve a backend service or database outage affecting machine brokering and site connectivity.

Citrix Virtual Apps and Desktops stores all site configuration, machine catalog data, and session brokering state in a SQL Server database. Pooled-random desktops require the Broker service to query SQL in real time to identify and assign an available machine. Persistent desktops can sometimes be launched if the assignment was previously cached or static. Studio is also unable to connect because it reads site data directly from SQL, so a stopped SQL Server service explains all three observed symptoms simultaneously.

Disabling Windows Firewall on static desktops addresses only inbound connectivity to persistent machines and has no effect on pooled-random desktop assignment or Studio database connectivity.