Let users logon twice to setup the new temporary folder location for them and it should be possible again to install Google Chrome extensions.After digging deep into RoboForm’s security whitepaper and carefully examining the password manager, I’ve highlighted the most important need-to-knows, shared below: It should look something like this, click OK to close the Logon Properties. Select the tmp.cmd with Browse… or type it in the box manually, click afterwards on OK to close the window.
You’ll get a new window like the picture below:Ĭlick on Show Files…, this will open a Windows Explorer at the location \\\SysVol\\Policies\\User\Scripts\Logon copy the batch-file tmp.cmd to this location and close the window. Save this in a temporary folder and get back to your Group Policies, browse to User Configuration\Windows Settings\Scripts (Logon/Logoff) and double-click Logon. tmp.cmd and put in these lines: mkdir C:\Temp\%USERNAME% This setting is found in your Remote Desktop Services Collection properties, see the picture below: We also want to make sure that the temp folder is emptied at the user logoff, this ensures we don’t consume unnecessary disk space on the RD Server. Then we need to set some settings, firstly we set a Group Policy, Configure Logon Script Delay found under Computer Configuration\Administrative Templates\System\Group Policy\ to disabled, this make Group Policy will run scripts immediately after logon instead of Group Policy will wait five minutes before running logon scripts. Make a directory under a drive, in our case we used C:\TEMP, and set the permissions that users can make subdirectories, write access etc. There is a workaround for this issue, described below.
D:\somepath which it only does if the disk is also visible under its own drive.
it then checks if this matches a path rooted at a drive letter e.g. 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\somepath…. This is an issue for several years already with any type of dynamic/mounted volume anywhere in the path of %temp%, %userdata% etc. 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'”.
0 kommentar(er)
