[What the hell happened to the discussions forum :-(]

You think that is bad, try searching google and see what happened to EVERY single search result that links to a discussion...zero continuity for links, and best still exact post title searches yield no result on the built in search.

Way to screw over your admins...I cannot wait to finish moving to AVD.

[New Teams Client]

Anyone had any luck getting this to launch?

 

I'm using: Start-Process shell:AppsFolder\MSTeams_8wekyb3d8bbwe!MSTeams

 

And all I get every single time is a crash with the faulting module being ucrtbase.dll

 

Note that command works just fine on the local machine. No AV is installed.

[GRID card boot loop.]

Very much not the case unfortunately, when it detects a new video card (only device I can attest to this being true for) it automatically reboots. Sadly not optional.

[GRID card boot loop.]

If I recall correctly the solution I came up with was to create a template in VMWare, assign that as the template to use in the ELM for the VMWare connector, then create the platform layer, install PVS, vda, GRID driver, join domain, reboot, install appsense, disjoin domain, reboot, delete the domain users profile, finalize then deploy my targets in VMWare using the same template I used to create the layer. For sanity sake the template itself didn't actually have the GRID card added as I use that template for everything, GRID and non-GRID, I just added a 4q GRID to it after spinning up the packaging and target VM's.

 

It is VERY specific about things and if you have problems you may also need to make sure the PCI device locations match as well.

[GRID card boot loop.]

I have a template of the VM I created the OS layer from so what I did last night was clone a VM off it, drop the disks, make sure it had a GRID card, convert to template, set that at the template in the connector, create a new version of the platform layer, messed around a bit, made sure the drivers were working, ran the PVS Optimizer script, set the NIC settings and finalized, same loop.

 

I HAVE seen it reboot when it creates a packaging VM for the platform layer.

 

Forgot two specs to mention, Server 2016 and ELM 4.4.

[GRID card boot loop.]

Created the image master VM without a GRID card attached to test something, when I create the platform layer and attach a GRID card (in this case M60) to the platform layer packaging VM and then publish the layer to PVS it gets into windows and boot loops, it appears to be rebooting because it found new hardware (pci device ID's match, everything I can find matches, target devices are clones of the same VM I used to create the OS layer).

 

We use the following:

• ESX 6.0u2
• PVS 7.15
• XenApp 7.15

Now some of our hosts run K2's and some run M60's.

 

If I can't attach the GRID cards at the platform layer without causing the underlying OS to boot loop then that means I cannot use one OS layer (and therefore one set of App layers) for both the K series hosts and M series hosts.

 

That is a pretty big deal breaker, is there any guidance anywhere on what does and does not get omitted from the platform layers? I would kind of expect that this should have worked but I have done it multiple times now and with Server 2016 the only way I can get this to work is to have the GRID card attached to the VM I install the OS to BEFORE I import the OS layer.

 

Which to me again seems to indicate that the problem is that something isn't being picked up in the platform layer that IS picked up when it imports the OS layer (guessing it doesn't make it through the filter driver?).