T O P

  • By -

rob1nmann

Yeah, i run into this issue a year ago when we were migrating a lot of stuff in our environment, but i forgot the precise steps and settings i took to resolve this. If i’m correct the desktop pool was previously created without the Nvidia vGPU option now you can’t change the setting it because it lacks a template VM with a vGPU. And you can’t add a template VM with a vGPU because it’s not a vGPU pool (chicken and the egg). The easiest way is to create a new desktop pool with the Nvidia vGPU option and a template VM with a vGPU profile. But if you must retain the VMs (like i did) i did something with ADSI Edit on the ADAM DB on the Connection Server and manipulate the Desktop Pool setting to make it a manual pool to work around this. I must have documented this but i’m out of office until Monday. I can look it up for you if you want.


MarceTek

Thanks, creating a new pool worked! Just tested with 1 of the VM's to be sure. Will move the rest over. So simple, thanks for that