I
i.am.mikael.lofgren
Hi!
I have now seen this problem at different clients:
http://word.mvps.org/Mac/CantSaveToServer.html
All with Mac OS X server 10.4.8 and Office 2004 (11.3),
and its easy to recall.
1. Have a AFP share that everyone mounts on the desktop (not network
home)
2. Check the user ID (open Terminal type "id")
3. Almost every user have 501, make a new document from lets say "A"
save it, no problem, close the document. Now open this document from
"B" with same ID as "A",
do some changes in the document and save it, and have it open,
go to "A" and logout or restart the computer (and DONT disconnent the
share)
its now the problems begin for "B".
4. There might be a workaround to check every users ID and make them
different,
but is very hard to check that, or tell everyuser to unmount the share
before a restart/logout,
but the problem show up if someone forgets, runaway with a laptop etc.
5. My suggestion to Microsoft to fix this is:
Either not make temporary files to shares.
Not make temporary files that depends on user id, take
something else, user shortname, time, randomnumber.
This fix must be quite easy to manage!
And we need it now!!
I have now seen this problem at different clients:
http://word.mvps.org/Mac/CantSaveToServer.html
All with Mac OS X server 10.4.8 and Office 2004 (11.3),
and its easy to recall.
1. Have a AFP share that everyone mounts on the desktop (not network
home)
2. Check the user ID (open Terminal type "id")
3. Almost every user have 501, make a new document from lets say "A"
save it, no problem, close the document. Now open this document from
"B" with same ID as "A",
do some changes in the document and save it, and have it open,
go to "A" and logout or restart the computer (and DONT disconnent the
share)
its now the problems begin for "B".
4. There might be a workaround to check every users ID and make them
different,
but is very hard to check that, or tell everyuser to unmount the share
before a restart/logout,
but the problem show up if someone forgets, runaway with a laptop etc.
5. My suggestion to Microsoft to fix this is:
Either not make temporary files to shares.
Not make temporary files that depends on user id, take
something else, user shortname, time, randomnumber.
This fix must be quite easy to manage!
And we need it now!!