Netware 6.5 shares and Windows 7 Document libraries

[Anonymous_User]

We're using Netware 6.5 for file and print services and currently working on a strategy for Windows 7 deployment on our network.

Currently we run XP, and users home directories are mapped to H:. "My Documents" is then pointed to H:, and the net result is that programs -- by default -- prompt users to save documents to the server.

With windows 7 this is more complex. We can't add the home directory to the user's document library because the Netware 6.5 shares aren't indexed.

I guess the ultimate problem is that in Windows 7, it's not always clear exactly where (i.e., on what physical device) a file is being saved, and we'd like to make it reasonably simple for users to make sure files are going to the server, not the local drive.

Any suggestions?

[Anonymous_User]

Alanm-williamson,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

[Johnsji]

Alanm,

Same problem here...a real sticking point. You are not alone (if that makes you feel any better). I am not sure who is going to fix the issue Microsoft or Novell or a combination of both. We can't be the only ones with the issue. If I find anything out I will let you know.

[Michael_Fleming]

Check out SLUtil.exe command line use with libraries to get around it. Still not an ideal fix but it is something.

[pcoen]

SLUtil is probably the way to go. I haven't tried it, but with OES2 SP3 it should be possible to get this working somewhat. If you have opportunistic locking enabled, you can use offline files support with OES 2 SP3 and CIFS. I think once you do that, the local Windows box can index the files and that makes them show up as a "proper" Library.

I looked into this last year - Windows Search 4.0 wasn't much of a change, and it's not clear that a 3rd party could get away with implementing the server side of it. Without the server side, you have to cache the files locally to index them. There also seemed to be some scalability issues. Even with a Windows server, it looked like there would be performance problems if you had it indexing millions of files.