I upgraded our cloudserver to 3.5.6 and updated 2 of the 4 connected ES devices to 3.5.6 as well leaving 2 ES devices connected as 2.8.8. On the 3.5.6 ES I enabled the persistent TCP to update the hierarchy on the target to match the source. I noticed that the target now has an NEW directory MU2 and the structure is switched around so SITES are under MU2 directory even though on the ES MU2 is under SITES. Why is this happening? The tree structure on 2 other 2.8.8 ES connected devices work fine. I want the ES to have the same structure as the cloud and not create a new MU2 named directory off the cloud's root?
This is the ES hierarcy...
[ two folders and one nest of folders 4 deep ]
This is the cLoudserver's hierarchy ... I have created the structure I want but the ES creates a new MU2 directory above and does not use the existing structure.
[ the two folders, the four deep folder with some extras, and then the MU2 directory with the four deep folder possibly inside it, but only revealed two levels deep ]