anothervsphereu's Posts

I figured this out.   I was trying to connect directly to my Horizon cloud pod URL instead of using the Universal broker URL.  I am able to logon using the Universal Broker URL. However... I have MFA enabled on my pods.   I have Windows SSO and maintain windows username enabled on all of my UAGs.  I can successfully authenticate, but i am prompted twice for my password.  Once before the MFA prompt, and again after the MFA prompt.  Is this normal behavior?  I cannot find any reason that it is doing this.

I also found that if i open a command prompt and use the vmware-vew.exe command line switches to connect to my published app. but if I use that same command line set of switches and create a shortcut, either manually in windows, or with UEM, i get the same entitlement error.

sorry, my screenshot didnt paste The error is You are not entitled to that desktop or application.  I know I am entitled because I can run it by just opening the client and selecting the published app. I opened a case with Vmware and was simply told this wasnt supported.  I know I had this working once before, but it was on and older Horizon Version and older Horizon client version. 

We recently ran into a similar situation.   We just stood up a new Horizon 7.12 environment and decided early on to provide some sort of grid ram solution.  Long story short, we went with the nVidia T4.  We didn't really have a clear goal in mind, just that we wanted to purchase all the hardware up front because we had the budget.  Not being familiar with the nVidia hardware, we didn't really ask the right questions and found out after the fact that it doesn't support sVGA.  What we have decided to do is provide 1gb of video ram for knowledge workers and 2gb (at least for now) for CAD users.  We can have up to 2 different grid profiles in our single cluster because each of our hosts have 2 T4 cards.  Another disappointing thing we found is that with the "Grid Virtual PC" nVidia licenses that we purchased; we can only do up to 2gb of grid ram per desktop.  In order to have more than 2gb would require the "Quadro vDWS" license.  I have not had any issues with vMotion of grid assigned desktops between hosts.  One thing I need to be cognizant of is how many grid assigned desktops I have deployed at any one time to be sure that there is sufficient resources available to perform host maintenance. It would be nice if there was a grid profile allowing 512mb of ram...but unfortunately there isnt. We are still in the early testing stages for CAD users and I have not rolled our grid ram to all knowledge workers yet.  Baby steps...

so...and update on this issue.   I does appear that the thinapp assignment was removed, but the icon was still hanging around because it was being stored in my writable volume data.   The only way I could find to remove the icon was to delete my profile folder and my writable volume and rebuild my profile.  Once I deleted those items, the icon disappeared.

Now the folders are magically showing up again I guess I understand roaming profile and folder redirection differently.  Before enabling folder redirection, nothing in my profile would roam. 

Thanks ArnoM.  I have read that article, and that is how i set up UEM and profiles.  I have had this working for a few months and all of the sudden those other folders from the redirection settings don't appear in my profile share.  I have the UEM profiles archive setting in the GPO pointing to the same path as the folder redirection settings shown in my first post.  What i can't figure out is where in the archives is desktop data stored?  As I mentioned, i tested by creating a file on the desktop, logging off and back on, and the file is still there.  But I can't find that file in my UEM archive.