Check procmon and see where the file is being written (if it is being
written successfully at all). Apps can use all sorts of ways to find the
"my docs" folder, so valid and some less so. If you can see the actual
behavior, you can script around it.
On Tue, Jul 14, 2015 at 4:14 PM, Webster <webster@xxxxxxxxxxxxxxx> wrote:
*Folder Redirection and environment variables*
The folder redirection client side extension is only able to process two
environment variables: %username% and %userprofile%. Other environment
variables such as %logonserver%, %homedrive% and %homepath% will not work
with folder redirection.
I have no idea if that helps you or not since that is referring to GPO
processing but it is worth a try.
*From:* thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] *On
Behalf Of *Jason Benway
*Sent:* Tuesday, July 14, 2015 2:51 PM
*Subject:* [THIN] Folder redirection doesn't work in DOS and other apps
We are redirecting my documents and some other locations.
If I open a dos window and cd c:\users\username\documents it does to a
local directory not the redirected location. I can browse that same path in
explorer. it seems to only be when I use the library and shortcuts in a
"open" dialog that I see the folder redirection location.
A new application we are using saves the config file to "my
I've saved the config file to the redirect my docs\application\session,
but the application doesn’t pull up with the config. I'm guessing its not
using the correct environment variable to look for the config file. What is
the correct environment variable that would recognize redirected folders?