Recently came across an issue were some GPO settings weren’t taking when launching published IE instances. Confusingly could launch the published desktop with the same IE instance and the settings would appear to take fine in IE.
Issue manifested itself with application timeouts occurring etc, in my instance we had cookies set at medium at the GPO level, however the setting was “ignored” and set to Block All Cookies
Turns out the wfshell plays a part in all this:
Once programmed in the fix from above all was good with the world
A few posts about this one, can have a variety of fixes – in the instance I came across (environment : xenapp 6.5 servers, bare metal).
Seen this issue caused by a xenapp 6.5 to 6.5 farm migration. Post migration systems would hang from time to time, users couldn’t connect via ICA / RDP. A number of similar events to above recorded relating to different services.
Ultimately issue was resolved by migrating some missing policies that were missing.
Client drive redirection set to prohibited
Automatic inbox installation of drivers set to prohibited
auto client connect drives set to prohibited
client USB plug and plug device redirection set to prohibited
Issue was caused by an influx of usb / print drivers spilling onto the systems (urgh) – clearing them out and having the above policies got things back on track
Being an active member on the VMware communities has amongst its many benefits an opportunity to stumble upon issues (and even better fixes:)) that one comes across in their own environment
Take for example the case of the mystery IOPs
Spookily enough came across this very instance in one of our older clusters – a quick trawl through /tmp/ramdisk as well to verify confirmed SNMP was in our instance the same culprit. Indebted to user CB_VM to being the “canary down the well” on this one.
Not so much a new feature as a definitive improvement for me on its predecessor. Nice write up about it here
and articulated my thoughts just as well.
Love in particular moving the recent tasks back down to the bottom of the screen a la old vSphere client and the improved responsiveness (though will tell over time as objects grow in my DB).
Good work VMware on it, definitely been listening to the community and its concerns and taken them onboard.
One of the key areas always keen to keep an eye on when VMware release a new version of vSphere is around the area of virtual machine enhancements. One attractive feature that comes with the new virtual machine hardware version (11 already by the way, can you believe it v4 only seems like yday) is around vNuma enhancements.
As VMware can probably phrase it better than me taken direct from their new features guide
When a vNUMA virtual machine with the hot-add memory option is enabled and memory is hot-added to it, that memory is now allocated equally across all NUMA regions. In previous releases, all new memory was allocated only to region 0. This enhancement ensures that all regions benefit from the increase in RAM, enabling the virtual machine to scale without requiring any downtime.
Where this feature can come into its own is in the “monster VM” arena, I’ve worked on VM’s carrying 128gb of RAM and NUMA location can play its part in adding unwanted latency and generally as these VM’s are in the “gold” or “platinum” tier given their spec its just when you need performance to be optimal.
Anything that can assist in this case is always worthwhile and a good addition to the feature-set.
From testing in my home lab inadvertently came across this feature. What I didn’t realize prior to installation is it is enabled automatically as long as both vCenter instances are joined to the same vCenter Single Sign-on domain. This helps cuts down the additional config involved in prior releases.
More details enclosed::
Not a game changer but a nice to have
So, environment is:
Citrix PVS 6.1 Hotfix 19
SCCM 2012 r2 Client (version : 5.00.7958.1000) installed in vDisk image
Duplicate Guid’s for all target devices
Followed the steps in
Did find this piece in addition to the above steps to fix
In it mentions disabling the client authentication service under the personal folder and your server certificate.
Untick the client authentication box, click ok, do your sealing up steps and voila! no more duplicate GUID’s!