When using the EUC Sync script, a user found that the Folder Path was double nesting. It was suggested that they use Folder Mappings (https://support.controlup.com/docs/euc-synchronization-with-universal-sync-script#custom-folder-mapping) to map "EUC Environments" with "Horizon", so the Root-level can be pointed to. The user considered the suggestion and noted that the naming conventions were similar.
Read the entire ‘Resolving Double Nesting in EUC Sync Script Folder Path’ thread below:
I could use a quick bit of direction. Using the EUC Sync Script – I am finding that when I define a Folder Path, It double nests. I’ll show in the threads what I’m referring to.
What do you have under EUC Environments?
Horizon is the top level – So perhaps that is it, but it is redundant in this case. Wondering how I can move it up a level. Is there a way to point at the Root level?
When I leave it blank it errors – sensibly
Most people use Horizon Sites or Horizon Environments for the root.
EUC Requires that they’re combined – because they are part of the same Cloud Pod – So I don’t really have a choice to separate them. Its not the end of the world, but ideally it would be
ROOT –> Horizon –> POD
Folder mappings may do the trick here though.
Ok – I’ll digest that and come back if I don’t come up with something satisfactory. Thanks Landon!
You should be able to do a “euc environments\horizon,Horizon” in the folder map and get what your looking for.
We share similar naming conventions… 😄
Continue reading and comment on the thread ‘Resolving Double Nesting in EUC Sync Script Folder Path’. Not a member? Join Here!
Categories: All Archives, ControlUp Scripts & Triggers