https://worldofeuc.com logo
Join Slack
Powered by
Hey guys, looking at layering docs and it says che...
# citrix-app-layering
d
Hey guys, looking at layering docs and it says check the UEFI box under VMWare connector setup. But.... I dont see it? I just installed latest ver of ELM and its not there and not in my slightly outdated prod ELM. What did I mess up?
r
might be new in 2403 let me upgrade and look
d
I just installed the latest. its not there for me under the VMWare connector
r
probably jsut a doc mistake ill ask
where is that from
d
I was looking through docs for uefi info for AppLayering and this came up
r
i see it ill ask did you try creating a new connector or use an existing one
d
i tried both - no go.
r
thanks
d
thank you for helping with this. maybe im just blind but i cannot find any AppLayer configs related to uefi - either in connectos or settings
r
there really isnt any requirement. You need a hypervisor template that defines the vm as uefi, then you create an os layer version wiht a connector that uses that template. Then when you publsih you use that OS versions and if its mcs a template that defines uefi or for pvs the pvs template needs to be uefi
Yea the doc is just wrong well get it changed
if you have any questions about what i wrote above let me know
d
so if I already have OS layer built can I somehow update it for UEFI?
and do I need to update the platform layer?
r
yes thats what i meant above. You can add a version to the os and basically switch it to uefi. thats done based on the hypervisor template you define in your connector. SO you will need a new connector tfor packaging wiht a uefi based template. then you use that to create the new version
And to so UEFI you need an offload composting connector whcih is what the documetaiton should have said
d
ah ok cool. That makes sense. I havent been using templates in VMWare connector though. IS that an issue?
sorry for the silly questions, im somewhat new to layering
r
not an issue for bios though you do ofetn get time issues without them but you wont be able to do uefi wihtout one
the best way is to have a working vm that you clone, then remove the disk
that way you get a funtional virtul buos in the template
i normally use a clone of my gold image
i dont hink the template vm has to be uefi
just the settings of the vm ebfore you mnake it a template
d
Can I use a copy of PVS template and remove cache disk from there?
r
probably
ive never done that but i dont know why it woudlnt work
after all its what youy are going to use later to deploy targets
just mae sure it has efi defined
d
ok cool, so if I dont need to configre that template for UEFI I am assuming I will need to update the OS machine to UEFI prior to writing the layer ver?
r
no you do need the template to be uefi thats the point. do you mean you didnt need it booted as uefi that i think is true
d
or do I just need to confer C driv from mbr to gpt and thats it?
r
no
we do that for you
d
well.... do I even need to do anything then? 🙂
r
yes
you need a uefi version fo the os layer
d
and that is created by adding a template (which does not have to be UEFI) and then creating new version using that template and then?
r
the hypervisor template has to have uefi defined like this. Otherwise we wont confifure the os layer for uefi
d
ah ok, so the template has to be uefi. thats the part i missed
r
yea
d
ok cool. thank you!!! this is super helpful.
r
good luck
Open in Slack
PreviousNext
Powered by