Discussion Locked

Strange local drive mapping in Word97

0 helpful
1 reply
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I our Terminal Server/Metaframe 1.8 enviroment we dont use "Connect client drives at logon", instead we use "change client b: a:" to map the users local a:. When a user open a document in word from local a: it all works, but when the user makes the choice "save as" you se the path \\client\a$ instead of "A$ on 'Client'(B:)" and a new mapping of the local a: at the first aviable letter. The original letter B: are still aviable. This only happens in Word97 and not in anyone of the other Office applications.
Anyone ?

1 reply

by rchilton

It sounds similar to a problem we were having at one of our sites. When we switched servers, Word97 began to try and save to UNC paths. To correct it, we set up a REG file with the following:

[HKEY_CURRENT_USER\Software\Microsoft\Office\8.0\Word\Options]
"DontUseUNC"=dword:00000001

We had it load on each machine using the login script.

I hope that solves your problem, or at least gives you a new direction to look.

This discussion is closed to new replies.