https://worldofeuc.com logo
Join Slack
Powered by
This message was deleted.
# citrix-vad
s
This message was deleted.
k
Secure Boot enabled?
b
I think I have seen this issue before when I boot an UEFI VM from a PVS-image created on a BIOS VM.
r
Good question here. In app layering you can only use UEFI with offload compositing connectors which meant that you could not use it with PVS because we didn't have one. We now let you use another connector in pvs to create vhdx files which is a ce connector and i hadnt thought of this. Let me check with the engineers to see if they think this will work. As a workaround in the past I have used a hyperv server to publish the vhd to then copy that to pvs.
Ok they say it will work so you need to make sure you use a CE connector along with the pvcs connector and of course that connector has to be hyperv or vsphere otherwise it wont support offload compositing.. Like this
b
Hey @Rob Zylowski, thanks for the quick reply. Unfortunately we already have had the new CE connector for a while now. We even tried to create a new connector since upgrading to 2112, but still no luck.
@Kasper Johansen no secure boot. Is it required?
r
Does your vmware template you use with the ce connector have uefi enabled?
b
Yes. Actually that's another reason we created another connector, to make sure the template was UEFI.
r
k
do you have nay extra partitions on the os layer
b
I think we skipped any extra partitions during the import. I'm spinning up a version now to double check.
Ugh, is this the issue?
Also, our TAM is telling us Win11 isn't supported on PVS until 2109, we're running 1912 CU3. Is there a difference between “supported” and “won't work” here? Haha
r
Bill is this vsphere and are you uisng pxe or an iso to boot
b
vSphere & ISO
r
Thanks and is this working outside app layering ?
b
Yes. Going to reimport again today. Will let you know how it goes.
r
Thanks ill check with ghe engineers again with this jnfo. The did ask if your using vsphere 7.02 and TPM but i figured you had those requirements covered.
b
vSphere is 7.0.3. No TPM, we used the registry hack to bypass:
HKEY_LOCAL_MACHINE\SYSTEM\Setup\LabConfig /v ByPassTPMCheck /t REG_DWORD /d 1 /f
r
Ok thanks let me know how your test goes
The engineers dont see anything obvious in what you have posted. After you do your test if it does work there open a case because they think they need ot see your image to troubleshoot more.
b
Ok, thanks for all your help, Rob!
👍 1
@Rob Zylowski Same problem after reimporting. Tried to upgrade PVS to 2112 and that didn't help either. Just opened case #80997282
r
But does it work if you just make a vdisk the normal way using the imaging wizard?
b
Yes
r
prefect thanks then yea woudl be good to open a case
👍 1
b
Only has an issue when we try to import into the ELM using the script
r
I thought the original issue was that you couldnt boot the vdisk in pvs?
b
Correct, my phrasing was bad. The import is successful, but, after that it will no longer boot in PVS.
3 Views
Open in Slack
PreviousNext
Powered by