Mapped Drives are not being personalized for random users with AppSense Environment Manager

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.


However, after looking at each individual drive, we did see a drive letter which had no data under it. Here we see a mapped drive T and it has no information listed under the key.


A valid entry should look like the following:


In order to get around this issue, have the user log off their session. Then within personalization analysis delete the drive letter registry key which is missing info from their personalization. When the user logs back in, they will see all of their mapped drives again. This is a great fix for a single user, however should this issue be widespread, you can add the following PowerShell script within the AppSense config under the logoff node. This will look for the dead registry entry and remove it as the user logs out. When the user logs back in, all of their mapped drives will appear again.

Get-ChildItem HKCU:\Network | Where-Object {$_.ValueCount -eq 0} | Remove-Item


This script can also be used on the logon node instead of logoff, however make sure it is one of the last actions to run during the logon process. As to what the true cause of this issue is, it is still unknown. From our research we did find a correlation between users who were disconnecting mapped drives who later started experiencing this problem. It is possible, Windows failed to delete the entire registry key.

© 2014 Eddie Kwasnik “the Wolf” All Rights Reserved


, , , , ,

  1. Leave a comment

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: