- This topic has 4 replies, 1 voice, and was last updated 21 years, 5 months ago by
.
-
Posts
-
We have a 2003 AD server and a bunch of emacs running 10.3.5 using the AD plug-in to authenticate to the AD server. We have an xserve that is using WGM to manage prefs on the emacs. We have DISABLE managed prefs to simply troubleshooting.
Problem 1: Some users get errors when loading up MS office. The errors follow the user from emac to emac, though the actual text of the error sometimes changes. Other users have no problems, regardless of the emac they’re using. The symptom persists regardless of whether the emacs are being managed using WGM on our xserve.
Problem 2: When the user logs in their AD home folder does NOT mount on the desktop. Instead the entire VOLUME that contains their home folder mounts on the desktop. Is this normal? If not is there a way to fix it so that ONLY the users home folder mounts on the desktop, NOT the volume that contains it (short of creating a share point of each home folder on the AD server).
I’ll take a shot at this because I’m fishing for answers to the problem mentioned in the first part of this post.
I, too, am storing home folders on a W2k server, but in the fashion of OSX (Documents, Library, Public, etc.). My problem comes in when setting up Classic prefs. It fails due to the 31 character filename limitation of W2K AFP. I’ll guess this won’t be the only file that will have a problem. This may explain your Office application errors. I’m looking for a work-around if anybody knows of one.
Regarding the latter part of your message, the only way I’ve found to have individual user folders mounted is to break the share on the common container and share the folders individually. Make sure to change the home folder path in the account properties accordingly. Take care, though. I’ve found an odd limitation of W2K SFM. Depending on the length of share name there is a limit to how many shares you can create. For example, I created 212 4-character share names. When I created #213, AFP file sharing failed on the W2K server (completely crashed OS9 machines accessing it).
An option to creating individual shares would be to hide mounted drives locally. Since your preferences are local you could force a locked Finder prefs with a login hook so users could only see their folder. Properly permitted, however, users should be able to access only their own files in any case.MacTroll wrote:
have you tried mounting the homes over SMB?
SFM is such a pain in the rear, that you should at least play with a straight SMB home connection.
Ok. I’ll bite. 🙂 What would you suggest as a work-around?
Ok, let me also clarify something… when I say we’re storing homefolders on the Windows server, we’re doing DATA-ONLY home folders. We’re NOT storing the user’s library in those window’s home folders, NOR are we booting the eMacs from the homefolders. They’re just for storing the users’ documents.
- You must be logged in to reply to this topic.