This message was deleted.
# citrix-app-layering
s
This message was deleted.
r
The new connectors have to be run from Azure because they use managed identity for permissions. So in the future if you want on prem and azure you could use two appliances and import/export or one appliance in azure. That decision will eb very dependent on bandwidth to/from azure.
👍 1
Im working on a new blog to cover this as well as updating my layer priority utility to sync layer priority between appliances when using import/export.
d
Thank you @Rob Zylowski again! What is the blog URL?
r
working on 🙂 so no url yet
d
ah gotcha. do you blog on Citrix blogs?
r
yes
👍 1
but ill let you know
will be a little while still working out all the details of the new conntectors
d
Looking forward. Really want to give layers the best shot as its a hassle to manage so many images
❤️ 1
Are there any good existing "getting started" and best practices type of blogs I should be checking out? (Not a read the manual person but 😄 )
r
for app layeirng in general or the new azure connectors
d
in general
r
sure give me a sec
and im sure now your sorry you asked :)
👍 1
d
Super helpful
p
I noticed this in the release notes when the new version came out. This is a huge middle finger to customers who have local Datacenters AND Azure.
d
Can the azure ELM manage onprem instances?
Maybe thats the way to go... just keep one ELM on Azure
r
Yes if you have enough bandwidth
👍 1
d
thats a good point since its egress
p
I'm sure thats about all the thought that went into this change. For customers who have invested time and resources into this product just to have functionality ripped out it is very frustrating. Running two ELMs is not an option we want to pursue, and having an ELM in Azure to work primarily with local datacenter hypervisors is dumb.