When running Acrobat reader, it uses up to 50% cpu time. If multiple users are running it on a terminal server, it uses up to 100% CPU time.
Older versions of Adobe Reader doesn’t work well with a redirected %appdata% to UNC path eg. servernameusers%username%appdata
It tests every folder in the appdata path and thus, when it reach the “”, then hangs or generate an error
Solution 1:
Remove the redirected folder settings for %appdata%
Solution 2:
If you don’t want to remove the redirected folder settings, you can just trick Adobe by modifying a registry.
HKCUSoftwareMicrosoftWindowsCurrentVersionExplorerUser Shell FoldersAppData
This will have a value of the UNC path eg serverusers%username%appdataroaming
Change this to c:users%username%appdataroaming
Doing it this way, you get to keep your folder redirection settings as well as tricking adobe so that it doesn’t run.
Please note that you have to make the registry changes everytime the user logs on, so you have to do it using login scripts or GPP or whatever login process you have for the users.
