A computing system (40; 50; 80) comprising: published resources; client devices (41; 51; 81), wherein each client device runs an endpoint management application which enumerates the published resources; a computing device, comprising a memory and a processor cooperating with the memory and configured to generate connection leases (94; 95) for the published resources selected by the client devices (41; 51; 81), the connection leases (94; 95) providing instructions for connecting the client devices (41; 51; 81) to virtual computing sessions (43; 73; 83) corresponding to the published resources, each connection lease (94; 95) comprising a published resource lease component unique to the selected published resource, and a common lease component referenced by the published resource lease component and shared by a plurality of different published resources, the common lease component and the published resource lease component being JSON documents and being linked together as JSON documents, wherein the published resource lease component includes a reference section that lists filenames of common lease components that it references, each filename comprising a version number of that common lease component, and wherein the endpoint management application resolves the references of the published resource lease component by performing a lookup for a referenced common lease component filename and also any filenames with a newer version to select the latest version of that common lease component. published resources; client devices (41; 51; 81), wherein each client device runs an endpoint management application which enumerates the published resources; a computing device, comprising a memory and a processor cooperating with the memory and configured to generate connection leases (94; 95) for the published resources selected by the client devices (41; 51; 81), the connection leases (94; 95) providing instructions for connecting the client devices (41; 51; 81) to virtual computing sessions (43; 73; 83) corresponding to the published resources, each connection lease (94; 95) comprising a published resource lease component unique to the selected published resource, and a common lease component referenced by the published resource lease component and shared by a plurality of different published resources, the common lease component and the published resource lease component being JSON documents and being linked together as JSON documents, generate connection leases (94; 95) for the published resources selected by the client devices (41; 51; 81), the connection leases (94; 95) providing instructions for connecting the client devices (41; 51; 81) to virtual computing sessions (43; 73; 83) corresponding to the published resources, each connection lease (94; 95) comprising a published resource lease component unique to the selected published resource, and a common lease component referenced by the published resource lease component and shared by a plurality of different published resources, the common lease component and the published resource lease component being JSON documents and being linked together as JSON documents, wherein the published resource lease component includes a reference section that lists filenames of common lease components that it references, each filename comprising a version number of that common lease component, and wherein the endpoint management application resolves the references of the published resource lease component by performing a lookup for a referenced common lease component filename and also any filenames with a newer version to select the latest version of that common lease component.