T
tehtechie
I think I have stumbled across the solution - I have yet to completely
confirm with most people in my office due to the fact some are off on
Fridays...
All of the potential solutions that I've come across for this "word
working without a work file" issue all point to checking your "temp"
files location, to ensure you have rights. I know we've tried giving
full access to the users temp folders to no avail.
Well, after using process monitor on my own machine to see where word
was storing temp files, I discovered that it not only stores them in
your current "temp" or "tmp" variable, but ALSO in wherever your
"Temporary Internet Files" variable is, inside a subfolder called
"Content.Word".
So, after checking random registries of the users impacted, I was
consistently finding their cache pointing to "%systemroot%\Temporary
Internet Files". This explains why elevated privileges would
alleviate the problem.
This has yet to be tested, but if you have a few clients you can
remove Power User, and just move their temporary internet files
location to "c:\documents and settings\username\Local Settings
\Temporary Internet Files". That should be done within the IE ->
Tools ->Internet Options dialog.
If this doesn't work, then I invite you to to run process monitor on a
client machine currently experiencing the issue, in case there's
something else permission related that I missed... this will definitely
point it out.
confirm with most people in my office due to the fact some are off on
Fridays...
All of the potential solutions that I've come across for this "word
working without a work file" issue all point to checking your "temp"
files location, to ensure you have rights. I know we've tried giving
full access to the users temp folders to no avail.
Well, after using process monitor on my own machine to see where word
was storing temp files, I discovered that it not only stores them in
your current "temp" or "tmp" variable, but ALSO in wherever your
"Temporary Internet Files" variable is, inside a subfolder called
"Content.Word".
So, after checking random registries of the users impacted, I was
consistently finding their cache pointing to "%systemroot%\Temporary
Internet Files". This explains why elevated privileges would
alleviate the problem.
This has yet to be tested, but if you have a few clients you can
remove Power User, and just move their temporary internet files
location to "c:\documents and settings\username\Local Settings
\Temporary Internet Files". That should be done within the IE ->
Tools ->Internet Options dialog.
If this doesn't work, then I invite you to to run process monitor on a
client machine currently experiencing the issue, in case there's
something else permission related that I missed... this will definitely
point it out.