[THIN] Re: Word 2003 autorecovery on Citrix
- From: "Angus Macdonald" <Angus.Macdonald@xxxxxxxxxxxxxxxxxxx>
- To: <thin@xxxxxxxxxxxxx>
- Date: Mon, 27 Nov 2006 09:12:46 -0000
I suspect something goes into the profile. We use slightly modified flex
profiles and include the entire Office registry tree so a normal logoff on one
server and logon to another should include everything in the tree and provoke
the autorecovery.. Perhaps it's stored elsewhere in HKCU. I'll have a sniff
around with RegMon.
at least the autorecovery files can be loaded manually nowadays.
Angus
-----Original Message-----
From: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx]On Behalf Of
Rob Beekmans
Sent: 24 November 2006 18:15
To: thin@xxxxxxxxxxxxx
Subject: [THIN] Re: Word 2003 autorecovery on Citrix
Hi Angus,
I haven't looked at it before, but I could imagine that with the crash it saves
something in the users profile that triggers to look at the autorecovery file
after restart. but if what you writes is true, it is server based.....what kind
of profiles you use?
Have you taken a closer look with Regmon or similair tools to see what it does,
when it restarts??
I don't think you should asume that just the presence of the autorecovery file
on the W: disk would trigger it....If they weren't deleted correctly they would
pop-up every time you start word...there must be another trigger.
I'll check later on.....I have to do some work tonight anyway.
If I find something intresting i let you know
greetz
Rob
_____
Van: thin-bounce@xxxxxxxxxxxxx [mailto:thin-bounce@xxxxxxxxxxxxx] Namens Angus
Macdonald
Verzonden: vrijdag 24 november 2006 11:48
Aan: thin@xxxxxxxxxxxxx
Onderwerp: [THIN] Word 2003 autorecovery on Citrix
We have uncovered a little snag with Word 2003 on PS3. We have autorecovery
setup in Word, saving to a network drive (W:). Autosave files are saved in W:
perfectly. If I terminate winword.exe on a server and restart it, autorecovery
works just fine. However, if I run Word on another server, Word doesn't notice
the autorecovery files, even though they are in the same folder (W:).
Similarly, if I start a new session on the original server, the autorecovery
files are again ignored. The .asd recovery files may be opened manually but
asking my users to deviate from years of practice opens up a world of pain.
So presumably there is more to autorecovery than just the presence of
autorecovery files in the expected location. Does anyone know what that might
be?
Angus
Other related posts:
