Users with elastically assigned app layers do not have those app layers showing up at login.

Elastic layering assignment files are changing on the network share used for elastic app layers.

Layers.json
ElasticLayerAssignments.json

On the user's session where the elastic layers did not attach, look at either of the following logs:

From the current user's session:
C:\ProgramData\Unidesk\Logs\ulayersvc.log

If user layers are enabled as well, you will find ulayersvc.log embedded in logoff#.txt in the user's User Layer network folder. The # rotates on every logoff and allows you to track issues on a per session basis.


You will likely see no layer assignments as shown below, or you will see incorrect assignments.

---------== Layering Results ==-----------
User: <domain>\<user> (S-1-5-21-1234567890-0987654321-1234567890-1118), Machine: <name>, ULayer: <version>
Assigned Layers:
------------------------------------------


When the json files are in their changed / incorrect state, please open MachineAssociations.json from the network share and make note of the IP address shown in the file. This is the IP to the ELM that made the last change to the layer assignments.

Find the second ELM and point it to a new network share location. It can be a completely new network share or even a sub folder of the existing one. However each ELM must be assigned a unique location or they will overwrite each other's layering assignments.

---

Problem Cause

It is common for a site to have two ELM's deployed. One for production and one for testing or development. Each ELM must have a unique network share location for their elastic layers. If they are pointed to the same location, then each ELM will overwrite the other's layering assignments as assignments are updated in the management console or as the ELM's scheduled task to keep the assignments intact run every 24 hours.