Today I had an issue in an RDSH Farm environment, on Windows Server 2012 R2 with User Profile Disks enabled, when users trying to install Google Chrome extensions get the error “Could not install package: ‘COULD_NOT_GET_TEMP_DIRECTORY'”. This is an issue for several years already with any type of dynamic/mounted volume anywhere in the path of %temp%, %userdata% etc. What Chrome does is take the path specified in your case c:\users\%username%\appdata\local\chromeDataDir asks the os to dereference it to a canonical path which turns into something like \?\\HardDisk2\Partition1\…
All posts in RDSH
![[How-to] Install custom certificate on RDSH Server](http://35.204.150.161/content/images/wordpress/2016/12/120616_1048_HowtoInstal3.png)
So, the release of Windows Server 2012 has removed a lot of the old Remote Desktop related configuration utilities. There is no more Remote Desktop Session Host Configuration utility that gave you access to the RDP-Tcp properties dialog that let you configure a custom certificate for the RDSH to use. In its place is a nice new consolidated GUI that is part of the overall “edit deployment properties” workflow in the new Server Manager. It turns out that much of the configuration data for RDSH is stored in the Win32_TSGeneralSetting class in WMI in the root\cimv2\…
![[Fix] Remote Desktop DPI scaling issues](http://35.204.150.161/content/images/wordpress/2016/03/screreso.png)
Do you have a computer with High-DPI screen? A very high resolution display? And is everything too small to see within your Remote Desktop Connection, try this solution… This issue is caused by lack of not being DPI scaling aware of the Remote Desktop Client. If you open a Remote Desktop connection to a server or other computer the native resolution of the computer is used instead of the scaling to 1920×1080, so you’ll get very small icons etc. Some other blogs mention to fix the issue with using Remote Desktop Connection Manager 2.7…