whibr's Posts

We have also began testing of the 348.20 beta driver from NVIDIA.  So far, after one day...zero random session disconnections from anyone that has experienced those before.  I will update if anything interesting develops.  I would suggest anyone wanting to test this windows display driver create a VMware SR, explain your environment and problem symptoms, and you should receive this driver to begin testing.

Elgwhoppo, We have upgraded to the 348.07 windows driver and the 346.68 vib a week ago, but that hasn't fixed our dual-display, 2vcpu session disconnects.  I also have a SR open and hope to get some feedback soon.  Our workaround plan is to start giving users a 24-in monitor instead of the two 19-in they are currently using.

I am also finding this disconnection issue happening in our environment.  So far, it seems to just be a random event among many of our Dell Wyse zero client users (dual-display, P25, 4.8 FW) and vGPU linked clone desktops pools.  I would like to try upgrading with the newer NVIDIA drivers, and see if that helps any as well.  Once I do, is there any way that you have found to reproduce this error?  Also, we have upgraded our K2 card gpu VBIOS in our older (circa 2013) GRID K2 card's to a newer version (Dell link).  I was wondering if anyone has done this VBIOS upgrade also?

Pretor989, I ran across this post as I was looking for additional tips.  I solved an issue same as yours by setting this policy in the ViewPM.adm GPO.  I imagine you can set the same using the local policy. Computer Configuration > Policies > Administrative Templates > VMware View Agent Configuration > Persona Management > Roaming & Synchronization: - Roam local settings folders = Enabled Prior to this setting, the Outlook 2013 .ost file was created under the C:\Users\%username%\AppData\Local\Microsoft\Outlook folder, but that folder was not being uploaded to the Persona repository.  When the user logged off, the desktop refreshed, and the .ost was lost, meaning it needed to be recreated again on next login.

Interesting.  I don't actually have a larger monitor to test at the moment, I have just one 1920x1080 available.  So, in the vSphere 6 Web client, I am looking at the video card section of the VM settings (see pic).  When I change the number of monitors to 4, I can't enter any higher than 128MB for Total Video memory.  For 3D Memory, it will allow me to enter up to 2048MB.  Do you know how these different memory settings work?  This particular VM has the NVIDIA vGPU k260q profile assigned to it.

Thanks again, fellas.  Our first vSphere 6.0 install was to upgrade our GRID K2 vSGA server from vSphere 5.5 using vCenter Server Update Manager.  After the initial upgrade scan of the host, it showed an error message regarding the currently installed VIB as being incompatible with vSphere 6.0 and that it needs to removed.

Linjo, krd, Excellent, thank you both for the clarification..one follow up question then.  I have another vSphere 5.5 host with NVIDIA GRID K2's, currently hosting several vSGA pools and two vDGA vm's. So, I would like to upgrade this system to vSphere 6.0, which VIB will I need to install that does not enable vGPU?  I want to keep the vSGA and vDGA pool vm's running on this host intact after upgrading to ESXi 6.0. Or would you recommend leaving this as a vSphere 5.5 until we are ready to migrate those pools to vGPU?

I didn't see 6.0 in the App Volumes 2.6 user guide, unless I missed it, is why I was asking.  Though, as you've said, with all products being released at the same time that should indicate cross-compatibility, you would think.

I will, and hopefully version next will arrive soon...  I've spent way too much time trying to tweak and work out a functioning deployment with just basic corporate-needed apps.  No success, just too buggy and not reliable yet for our use.

Thanks for the reminder, but I'm still experiencing some odd anomalies.  I decided to blow away the writable and create a new writable using the "uia_plus_profile" template instead this time.  Logged in to the pool one time with no appstacks assigned just to create the profile into the writable.  Then in the OCT, I removed the desktop shortcut entry from the MSP file, re-provisioned the appstack with Project, and manually drag-drop a shortcut into the folder C:\Users\Public\Desktop before completing the provisioning process.  All went well, and I attach the stack on next login,  Project shortcut on desktop showed up just fine.  Logoff, then login again to ensure it carries forward to another random pool desktop...success.  My last test is to unassign the appstack at logoff from the AD group it was assigned (my user account is member of this group).  I logoff and log back in, and the desktop shortcut is still there even though the Project appstack is no longer attached.  Under Start > All Programs > Microsoft Office 2013 there is still a Project 2013 entry, but when I click on it it doesn't work and I get a message saying that the product is not installed.  I logged off again and on, same result...desktop shortcut is still present also.  I will do some more testing and hopefully I can figure something out.

Nice. I now have the full Office ProPlus 2013 in the parent base image.  Works great in the clones, with the users also getting a writable (profile only) upon first login to the pool.  Using the Office Customization Tool, I created a MSP file to make a [Desktop Folder] shortcut as part of the installation. I then provisioned a Project Standard 2013 app stack applying this MSP file during installation.  If this Project app stack is next assigned to a user that hasn't yet logged in to the pool (and doesn't have their profile/writeable initialized), the Project 2013 shortcut on the desktop appears as expected.  But if this app stack is assigned to a user that has already previously logged in and has been using a writable, then the desktop shortcut never appears.  The Project app is there, it works fine if you launch it from the Start > All Programs menu, but I would like the shortcut to appear for the users when they have been assigned the app stack.  Any ideas?

I'm testing with Office 2013 ProPlus with KMS licensing, and will also want to add Project and Visio.  Not sure if Office 2010 is the same, but how did you deal with the activation in the base image (or App Stack)?  Any additional recommendations you found around the activation when capturing the app stacks would be helpful.  I've been trying /act and ospprearm.exe when provisioning with ok results, but not sure if that is necessary.  Our clones are refresh on log off.