I’ve been in the IT industry for over 15 years with my focus on Application Delivery, Server Based Computing, and Virtualization. These technologies include but are not limited to Microsoft, Citrix, VMware, AppSense, and Liquidware Labs. Troubleshooting complicated scenarios, and incorporating best practices into customer’s environments has been my goal for my years working as a consultant. Now I can share the many solutions to the unique and different issues I run into.
Product: AppSense Environment Manager 8.x
** NOTE: For AppSense Environment Manager Version 8.0, the following is in the user’s desktop settings within personalization. For any newer version it will be in the user’s Session Data within personalization.
A user logs into their desktop and they report they cannot see their mapped drives. If the user creates a new mapped drive within their session, logs off and back into their desktop, the mapped drive is no longer there. This only occurs for random users. Upon further investigation, when looking at the user’s session data in personalization analysis, the mapped drives are being personalized. This is found under the registry key HKCU\Network. In fact, even the newly mapped drive shows up here as well. Read the rest of this entry »
Posted in CITRIX on January 27, 2014
During the testing phase of a new VDI rollout, there were many users complaining they had to set their default printer each time they logged into their desktop. I worked with a few of the users and noticed the issue would only occur if they were setting one of their Citrix auto-created printers as the default. We did not see the issue if the user set a network printer as their default printer. Before we go further, lets look at what the environment consisted of:
Citrix XenDesktop 5.6
Citrix Provisioning Server 6.1
VDI Image Operating System: Windows 7 Sp1
AppSense: Environment Manager 8.4
Within our AppSense configuration, we were utilizing Session Data in personalization to capture the user’s default printer which is held under the following registry string entry: Read the rest of this entry »