Local home directories vs network home directories?

We have an existing linux server which handles web, ftp, dhcp and email for our design group. I am planning the integration of a new mac os x server to handle shared work folders, client archives, shared resources (stock images etc) with eSATA raids as a fail over back up. I have been doing a lot of reading and research, but have not arrived at a best solution for local vs network homes. Our users never connect from another mac workstation, and so utilize a number of iLife content mgmt apps. They all have large personal photo libraries, music libraries etc on their workstations. In addition, many of our projects involve working on extremely large photoshop files, video files etc. I am leaning towards leaving these users as local homes as there is concern over performance on the network. Pros? Cons? am open to any input before establishing final plans for osx server services.
Network is cat 5e ethernet with 3 gigabit switches (one on each floor of a 3 storey building with an uplink between ea floor)
more macs than I can list Mac OS X (10.4.8)

Is the local home with synchronization of
selected folders a variant of mobile home? or mobile
user? (newbie osx server admin, still digesting the
apple manuals!!
Ok what I believe your asking is can you sync your portable home directory ~/shortname to the Server /HomeDir/shortname and ignore the lets say ~/shortname/Pictures or Music Directory? Since you only want Work related files on the Server and only have to backup 1 big user directory with only work related file on the server? Well the answers is a big YES .
What is required takes a bit to setup. Heres a quick list of things to do and that need to be in place for it to all work smooth.
1. OS X Server Software with OD/LDAP setup 10.4.3 or higher!
2. All Client 10.4.3 or higher and binded to the OD/LDAP Server.
3. Setup Workgroup Admin/Preferences Management. You can set rules for a Group or individual Users. Groups being the preferred way. In here you can set the Path to the Files & Folders to ignore during the Sync. You can do lots of other MCX Managed client settings here and if your OD/bind is good it works great.
4. You'd have to move stuff around on the Local units i.e. ~/oldfiles to New ~/shortname which will be created. There a few way to do this and hold Permissions and all that just read about Mobile homes more. Think of it as a Laptop connecting for the first time to a binded OD server. Lots of folks have different ways.
My clients also work with Large files (PS, ID, ai) and a network home was a bit of a pain. To be honest it's not the large files that get you it was the BS cache files that slow it all down. There are now work arounds for the performance hit but took time for the community to figure it all out. I had them in 10.3 working on files in the /Users/Shared/ directory and moving finished work back to the server after.
10.4 has been the saviour of my sanity with mobile homes. Servers Fast Clients Fast, I have full control of clients (<--admin god complex), and all lived happily ever after... for the most part.

Similar Messages

Sync my local folders to the network home folder?

HI, I use the Workgroup manager to create a new user and then under the "Home" tab to create a "HOme" for that new user. When I save a file onto that new user's local desktop; I want that new files to be copied to the user's home folder's desktop. How can I do that?
When I logon the Macbook with the new user's logon, I can see the home folders (Desktop, Documents, Downloads, Library, Movies, Musics, ...etc) there on the server with a "no access red sign" and just no automatically sync to those folders. What do I miss out here?
Can anyone help? I want the users to be able to sync all the files from their Macbook to their home folders on the Xserve once they shutdown.

So you are saying that on the server you see red circles on the folders on the server right?
That would be correct because the local admin on the server does not have access to them. That is how it is susposed to work. If you would like to have access to those folders you can add the local admin to the ACL of the users folder and then propigate it down to the rest of the folders. You can do that in server admin.
You will then be able to see if the data is getting to the folders on the server.

Trouble with network home directors and keychain

Hello all,
I have recently started to dabble into Managed Accounts using 10.4.11 server, however I am running into sporadic issues. First of all, Keychain access to users is extremely flaky. All of my users' files are being imported from existing local accounts, so I'm betting that my import procedure has something to do with my problems. Fortunately all of my local accounts have long ago had their uid's changed to mirror the users workgroup UID, so I haven't had to bother with changing permissions on any files. My import process goes like this.
First, I create the users home folder in the Workgroup Manager. Then, I log into the users computer via ARD, take control, connect to the users Home Folder, and copy all of the contents of the users local folder into the Network Home. Once this is done, I apply the correct permissions to the users home folder to ensure that no files may have been overlooked during the import process, and then I log out of the users account, log into the administrator account, and completely delete the users local account. I then add the computer to the Servers managed computer list, add the user as the sole authorized user (other then Administrators of course), restart the computer, and then log in as the workgroup user.
Once this is done, I usually have several issues with the Keychain in authorizing the workgroup user to use the existing keychains. Even after logging back in to the local Administrator account and completely deleting all existing users' keychains, the user has the same issues. To my untrained eyes, some programs have a hard time accessing the proper keychain, or remembering that the keychain has been altered.
The second problem that has only recently cropped up is that some users are loosing the ability to use their keyboard in certain applications. This happened to me maybe once or twice in the last couple of days, but starting today, and in the last 2 hours, has had this happen no less then 10 times. The only program that I have seen this happen to is Microsoft Excel 2004, and it is also the only program that I have had it happen to me on.
This is only happening on users who are using Leopard 10.5.4.
Any help is appreciated. Also, is the macos-x mailing list dead? I haven't seen any posts to it in almost a week...
Thanks,
James

Hi
I’m sorry that the guide is unreliable for you, although it does seem strange that it is. Perhaps there is something fundamentally wrong with the configuration of the AD Server?
Apple have made binding clients to Active Directory relatively simple and easy since 10.4. You had to work a little harder in 10.3. All I can add is successful integration depends almost entirely on how well the AD Server is set up. It might be worth your while to look more closely at that for a solution?
Speaking for myself I have never really had a problem and as far as I can tell all of the installations I have been involved with that required AD-OD integration are still working as desired. Some of them going back 2 years, that’s pretty reliable don’t you think?
Tony

Network home folders, collaboration sharepoint and Microsoft Word 2008

I'm hoping someone who knows how Microsoft Word 2008 works on network volumes can shed some light on our situation.
We run a small managed network with about 15 leopard clients and a leopard server. We've got two sharepoints, a "homes" share for network home folders, and an "Office" share with our shared office document folders.
Several times a week, users will encounter a situation where Microsoft Word 2008 will claim that a file is open by another user, or that the file can be opened in "read only" mode, even though the file is not in use. Naturally, the problem cannot be replicated when I am present.
### My Hypothesis ###
My users are in the habit of quickly borrowing machines from other users to pull up documents in the "office" share by using the "connect as" button. So, for example, userA is logged in to her machine (and is thus connected to the network home folder on the server). userB comes along and borrows her machine -- without logging out, will connect to the shared office folder, pull up and edit/print a document, etc. We're not currently auto mounting the office share.
I know that Microsoft Word creates lock folders located in the .TemporaryItems folder at the root level of the "office" share. The folders are named "folder.xxxx", where xxxx is the userid of the account that created the lock folder. Everyone uses a network account, so everyone has a unique userID. If I list the .TemporaryItems folder using the CLI, i can see lock folders that are several days or a week old. So Word doesn't seem to be cleaning up after itself immediately, at least not always.
So my question: when userB connects to the office share on a borrowed machine (logged in to the client machine using the network home folder of userA), is it possible that word will now create lock folders for userB, and will be unable to clean up lock folders created by userA?
Anyone have other ideas for investigating the "file in use" problem?

Switched user back to the network home folder and adjusted the MS Word preferences so that the autorecovery files would be stored on the local client machine. There doesn't seem to be a comparable setting in the Excel preferences.
My initial testing suggests that this has reduced how often this problem occurs, but has not eliminated it. I tested by repeatedly opening and closing a couple of different word files in rapid succession -- i was able to replicate the "file opens as read only" problem occasionally.
I've talked to Apple server support about this issue. While they were helpful, they didn't have an explanation or solution for this problem. There are a number of postings in the microsoft mactopia discussion boards site where people report similar problems.

Converting a local account to a network account

What's the best way to move a local home directory to a network account? I'd like to convert the local account information to the network account. I have a OD server setup in Leopard 10.5.5 and the client is 10.5.5 also.
The user is setup on the server and I just need to get all of the user's local data into the network account, I will delete the local account when all the files are transferred.
Thanks.

i usually do the following on the client side:
login as a local admin of other user with admin privileges
rename (mv) the user's local home
delete the user's local account via the accounts pane or dscl
ensure the machine is bound to od
login and create a phd for the user in question
ensure that works fine and sync settings look ok
logout as the user, login as the admin (this can be done remotely)
mv the old home back to match the user's shortname on the server
change perms to set ownership on the new/old home
delete the remains of the original portable home (should be basically a default homedir) if you haven't yet
login again as the od user, and it should work
now, you'll have to be careful to maintain proper permissions and check sync settings afterward, but this approach generally works. alternately, you could rsync the local home to the network home with the user still logged in, and then skip a few steps above.

Local access to Network Home directories

Under Leopard, I want to allow a user to log in to the machine that hosts his network home directory, and access it locally from that machine.
User joe is set up in Open Directory to use a network home directory that is served from machine joe-ws. In other words, his Home record points to afp://;AUTH=Client%20Krb%20v2@joe-ws/Users/joe. There is also a mount record in OD that causes joe-ws:/Users to auto mount as /Network/Servers/joe-ws/Users
This is working perfectly -- Joe can log in anywhere on the network and see his files. He can also create portable home directories, sync them, and the like.
Except that he can't log in on joe-ws: if he does so, joe-ws tries to mount its own sharepoint via afp in order to find joe's home directory and that isn't a happy situation.
Is there any obvious way to do what I want?

I have found the source of my problem and resolved it -- it relates to case-sensitivity of host names.
What is supposed to happen is that automount and autofs are smart enough not to try to mount shares that are hosted locally. If, for example, if there is mount record in the directory asking for afp://joe-ws/Users to be mounted in /Network/Servers/joe-ws/Users, then on every machine but joe-ws, it'll happen. On joe-ws, on the other hand, automount just creates /Network/Servers/joe-ws as a link to /
In my case, there was a typo in the local DNS zone records, causing joe-ws to think it's name was joe-ws.DOMAIN.com, whereas the mount records referred to joe-ws.domain.com (difference being case).
Therefore, automount, running on joe-ws.DOMAIN.com tried to mount a sharepoint hosted on joe-ws.domain.com. DNS sees these as the same host; automount doesn't, so fails to apply the special magic that normally applies when you ask it to mount a sharepoint that is hosted locally.

Migrating local user accounts/home directories to network user accounts

Hi,
I am planning on moving the user accounts from several Mac OS X client machines to a new Mac OS X Server machine (Quad core Xeon MacPro). I am very familiar with OS X client in a support environment, but do not have extensive experience with Server.
I read over the instructions in this article
http://docs.info.apple.com/article.html?path=ServerAdmin/10.4/en/c6um3.html
and it appears to be fairly straight forward, although I do have some questions regarding the existing data (home folders) and how to set the clients to log in to the network account.
Previously, in the event that I have needed to move a person's home directory to a new computer or recover from a corrupt OS (and Archive&install was not an option), in OS X client I would:
1) Back up the home directory.
2) Erase/reinstall OS X client.
3) Log in as Root.
4) Go into "Accounts" pref pane and create user with same short name as original/backed-up home directory.
5) Replace the newly created home directory with the backed-up home directory.
6) Go into Terminal and chown/chgrp the home directory to username/staff, respectively.
This would result in a perfectly migrated user account. All settings and files working just as they did on the previous system/install of OS X.
First Question: Could I employee a similar method to retain the content and settings from the local user accounts on the server as I migrate them to network users? Moving the user accounts to the server as described, then running terminal to set proper ownership...
Second Question: What do I do on each client system to tell it to recognize the networked home directory for each user? Do I just change the user's home folder path in Netinfo Manager to the automount location?
Thanks in advance for any help you can offer,
-David
MacPro 2.66 Quad Core (MA356LL/A) Mac OS X Server 10.4.8

A network account is really existing only on the server but if you use "portable homefolders" (Tiger client and server) you could "migrate" the local account to a "server" one by:
Login locally as another user with administrative rights.
Change the name of the old account folder in /Users.
Remove the "old" account locally (woun't remove the "old" folder as you changed the name) only Netinfo data.
Login using the serveraccount login/password thus creating a homefolder on the server.
Logout and back in, enable portable homefolder.
Logout and then in as a local admin and remove the new user folder.
Change the name on the old userfolder to what the new one had.
I'm not a 100% sure Netinfo has the server account UID now (added by logging in and creating the portable account?) but if it does:
(http://forums.macosxhints.com/archive/index.php/t-12077.html)
"Finding and changing UIDs across the filesystem is a one-liner command:
sudo find / -user UID -exec chown userName {} \;
(replace UID with the old UID number and userName with the new user name to associate file ownership.)"
(A portable account must have got some "kind" of UID?)
Let the machine "sync" with the server account.
If you want an "on network only" account I don't know what you need to remove locally afterwards.
HTH

Folder Redirection not working on SMB Network Home Directories

I've setup network home directories on a 10.7.3 server. NHDs are available via SMB currently. I'm trying to setup folder redirection via MCXRedirector for both the ~/Library/Cache folder and ~/Downloads and redirect them to the local client. Client is 10.7.3 joined to OD. I'm using Login Redirection and the option to delete the existing folder and create a symlink. I used these instructions to create the redirectors: http://www.afp548.com/article.php?story=MCXRedirector
When NHDs are available via SMB, the folders are created on the local client, but the symlinks aren't created in the NHD. I can switch the NHDs to be available via AFP, and then it works fine. I can switch back to SMB and the symlink stays in place and appears to work with no issue.
Am I missing something here? I can't find any documentation that says I can't use MCXRedirector with SMB shares, and I see a number of posts where it appears that people are using it successfully... so I'm not sure what is wrong? Any help or suggestions is appreciated.

Hi James,
For folder redirection issues, we can go to Windows Logs\Application in Event Viewer to check if some related error events were logged. Besides, we can also run cmd command
gpresult/v or gpresult/z to collect group policy result to check if something goes wrong.
Regarding how to configure folder redirection, in my opinion, the following article provides a good guide.
Configuring Folder Redirection
http://technet.microsoft.com/library/cc786749.aspx
Best regards,
Frank Shen

Final Cut Pro with Network Home Directories

Hi,
I have been tasked with setting up a Mac network primarily for use with FCP. The main requirement is that the user profiles are roaming as users will move from desk to desk, it is a college.
I have an Xserve with OS X server and Open Directory configured. I have configured the network home directories and have successfully logged in with different users.
My questions is regarding Final Cut. What is the best way to configure Final Cut to reduce the amount of network traffic?
I have redirected the users cache folder to the local Mac and configured the scratch disc to a local hard drive. Are there any of tips that someone with a similar setup can recommend?
Thanks

Most schools end up using ext HDs. Each student has their own firewire HD with All the fcp capture, scratch etc docs on it.
Thats the only way to meet the demands of video production and retain portability

Users on network home directories hang after sleep

Hi,
I have the following problem: I have a 10.5 server with network home directories. I can login from Snow Leopard (10.6.1) however whenever the machine goes to sleep and comes back from sleep, the user hangs then if you wait a bit then it will come with the message that the share has been disconnected and it asks you to manually unmount. It will stay there forever. When you click disconnect, the system will unmount and remount the home directory but in the mean time, Mail will have reported disk i/o errors in the logs and throw errors (ranging from type in your password to 'rebuild index').
Going through the log files (and verbosity high) it seems that when going to sleep, the system doesn't unmount the network home directory. After it wakes up from sleep it attempts to unmount the home directory share which off course fails because it's in use and then it locks up, after you click disconnect, it says "spins reported" in the logs and goes on with remounting the shares.
The issue doesn't happen if the user is local. If anybody has an idea as to how this works or if they have it working, please let me know. I have tried just about anything. AFP shares, NFS shares, I have tried with or without the intr, nolocks, locallocks mount options - they all have the same issue. I have even tried another Mac Mini with a fresh install of Snow Leopard.

I found a possible cause and solution.
This has been on 10.6.1 with Mac Mini's. Then we got a new Mac Pro with 10.6 out of the (Apple) factory which I updated to 10.6.1, same issue. What I didn't think about is that by default I install a heap of software (including XCode, Adobe CS4 and Office 2008) with customized packages and workgroup manager preferences.
So I was mucking around with Cocktail (the tool to clean up caches etc.) and I noticed Snow Leopard hung every time after cleaning & recreating some caches. Now that I had a reliable way to hang Snow Leopard I investigated what could cause it.
I noticed during a PackageMaker session that Adobe CS4 installs a Version Cue startup script in /etc/machinit_peruser.d. I deleted it, rebooted, used Cocktail again and it went all the way through without hanging. Rebooted again, according to the logs it pre-linked & cached the kernel and several kernel extensions and that was it, no more hangs, no more issues logging in after sleep or screensaver.
So possible causes:
- VersionCue installs itself as a kernel module or something (the location says "mach" which is the kernel after all) which is not compatible with Snow Leopard.
- The caches and kernel extensions were 'dirty' out of the box but VersionCue (or something else that interacts with it) blocked my or Snow Leopard's automated attempts to clean them.
- VersionCue reinitializes (it sits on the network after all) after a sleep or screen saver timeout in a way that gives issues with Snow Leopard

Need Help setting up "Network Home Directories" or Something Similar

Alright so, I am sure the answer to my question exists but I have no idea what i am looking for as far as syntax is concerned. I have taken over as tech at a full mac School and have not touched a mac before in my life. I will try my best to give a detailed description without an entire life story.
My school has 10.4 on laptops which we run a script on to bind to a directory allowing them to access accounts created on our server. That part works fine. The problem we are having is syncing or saving any files/changes to these networked accounts. The accounts seem to have home directories created, i went through workgroup manager and set up login/out and background syncs, and nothing seems to work(Copy/save). This year it would have been nice to have the syncing feature since all student/teacher laptops would go back and forth from home and work. However next year will change a bit since we will keep all student laptops here and the teachers will still take them home. We also have desktops of course which do not move and will be accessed by the students.
I need to find a way for students to log into the server to access their account and have it automatically pop up displaying their own files/folder on any machine they access since they wont always be at the same machine. considering there will be upwards of 100 students accessing each machine, local syncing for this would not be a good idea. My best guess would be setting up network home directories so they can log into and work directly from the server and have nothing but the original OS installed on their local machine.
As far as the teachers go, Since they have one laptop the entire year and take them home the syncing method would be the best. That way they can come here, turn on their laptop, automatically sync as they log in, and save everything when they log out (or every so many minutes since some of them close it and just run home). I tried doing this with a student account but could not get it to work. My other problem with this is that the teacher laptops are 10.5 and I have no clue how to bind them to the directory since I was not the one who created the original script which is something i would like to reverse engineer to my standards since it has some nice little things in it I just wish to tweak.
A short recap of what i need:
1) Network based accounts with network home directories, nothing locally saved
2) Network Based accounts with Portable Home Directories, Syncing between local and server files
3) Bind 10.5 machines to server
4) Program to read and edit a script.
I somewhat know the terminology for PHDs and MHDs and have read a bit about those but still cannot get them to work, but I am extremely frustrated with my lack of terminology for NHDs (If that is what they would even be called) and have had a hard time finding any information on how to set them up. The only thing i found was stating that if the server goes down, so do the accounts. Which isnt a problem since we have multiple servers as well as last ditch local accounts for students to just access the computers.
As far as i know, our servers are running LDAPv3 w/ OD, maybe even not with OD, I really don't know. If anyone can give me any help with this it would be much appreciated. If you need any additional information let me know and I will try my best to get it to you. I may even be willing to wipe everything and start fresh if it is required since these havent been used much in over 2 years, only for drive mounting storage.

I received some information on another forum, however I am still stuck.
So i rebound a laptop to the server via Directory Access, created a new account using Workgroup Manager, set the Home Point in WGM for the Account to a specified folder on the server's raid and no luck.
The account authenticates with the server, but it saves everything locally and ignores the NHD. Anyone with any ideas?

Mac OS X Server, Network Home Directories & Time Machine

hi,
I am using mac os x server to manage a small workgroup using open directory and network home directories, the server is backed up using time machine. From what I understand, time machine does work on network home directories.
However, as I am backing up my server using Time Machine, it is already backing up the user directories. Is there any way of getting a client to access the server time machine backup to access the backups of the user directories?
Of course, it would be easy to restore files by logging onto the server as the user and restoring from there. I am just wondering if there is a more elegant solution available to do this from a client machine.
any thoughts?
thx!

Hi,
I am trying to do the same exact thing and find that it is best to do this locally (for now). Not only is the network way slower, but it seems to make things worse. For example, things backed up via the client machine are routed from the FTP server/volume mount and different permission wise. When you try to restore them locally, it should work, but the folder had different permissions because they were initially created in root (for me). So, I hope they would come out with something better than what is available now. Thanks!

10.5.6 Login Items Error with Network Home Directories

I'm splitting this post off from a previous discussion which can be found here:
http://discussions.apple.com/thread.jspa?threadID=1835976&tstart=0
With 10.5.6 our Login Items are not working on client machines that use Network Home Directories. Everything works fine under 10.5.5.
When the 10.5.6 client logs in, login items with a path directed to the Home/Documents folder cannot be found, and the following error appears in Console:
"Unable to resolve startup item: status = -35, theURL == NULL = 1"
I have no problem manually navigating to the Home/Documents folder and opening the login items. Removing and re-adding the login items does not fix the problem. Revert to 10.5.5 and the login items are fine.
Below is a suspicious error that I see repeated multiple times in Console (viewing "All Messages") on the 10.5.6 clients but not on the 10.5.5 clients:
Sender:
loginwindow 34
Message:
FolderManager: Failed looking up user domain root; url='file://localhost/Network/Servers/myserver_name.com/Users/my_username/' path =/Network/Servers/myserver_name.com/Users/my_username/ err=-35 uid=0 euid=10790
I'm sure I could find a work-around by moving the location of my login items or maybe even changing to launchd. However, this error seems to indicate something going on with the 10.5.6 install that might be more serious. I've done some typical troubleshooting: DFA, Repairing Permissions, Clearing Caches, trashing loginwindow and MCX preferences, deleting the /Library/Managed Preferences folder, rechecking DNS on the server (forward and reverse lookup OK).
Any help is appreciated!
Thanks!

just to tell you, same thing here - it's nothing special about your setup. it's not a big issue for us as the kernel panic at logout on 10.5.6 is the real killer (no it's NOT JUST FONTS) so our workround is that we're not rolling it out! (staying 10.5.5).
but on my own test 10.5.6 mac i get exactly the same issue with login items that are in the network home. local apps (font management app, ichat etc in /Applications) OK, but stuff on the mounted home server - nope and a line in the syslog for each item:
Jan 28 09:25:54 hc04800-bssaht loginwindow[32028]: Unable to resolve startup item: status = -36, theURL == NULL = 1

AD Nested Group & Network Home Directories

Hi,
I have nested an AD group into my newly created OD master. Authentication is successful with home directories set to local startup disk.
I'd like to be able to run all user (~ 200 students) home directories from OS X server and WGM.
I know of 2 ways to direct user profiles to the correct network home
1. use the homedirectory attribute in AD
2. amend the AD schema to recognise OS X attributes
The AD admin is understandably anxious about adjusting the schema at this point. If I provide a case that highlights what's involved, he may consider it.
Has anyone tried this? Does anyone know a good source for info on the subject? I have a feeling number 2 is the best option.
Is there an alternate method of configuring home directories other than above?
Any advice greatly appreciated!

Well, I answered my own question. I found that in order to have my network home directory automount at login I had to use my AD account login as my initial login. I had been trying to log in using Fast User Switching from my old local account and even though I could log in, the directory would not mount.
This has probably been discussed somewhere before. I just hadn't found it yet!

ARD 3.2, network home directories and two admin workstations = problems

Hello:
I've got a situation where I've got two ARD admin workstations in two separate classrooms where the instructors have network home directories. If an instructor switches from one machine to another after setting up ARD on the first (i.e. entering a password, making computer lists, etc.), they are asked to enter their ARD password and they are not allowed in no matter what password they enter. It seems that there is some machine specific information in the ~/Library/Preferences/com.apple.RemoteDesktop.plist file because the only way around the problem that I've found is to delete this file and re-enter a password. This creates a new plist file, but the problem comes back as soon as the user uses ARD on the other admin workstation. Each machine has a separate (licensed) copy of ARD on it.
What's the right way to use ARD with admins that have network home directories?

Hi,
You mentioned the machines are all from a single image. I realize you are an experienced ARD user. However, there are quirks in this app at any stage of development. I'm sure you already applied a unique name to the shared network name and have no DHCP conflicts as well as checked that all the accounts, not just the admin account that permissions are checked. Although you may have all the correct ports addressed and configured, there is no accurate accounting for the gremlins. These play havoc across the network. Sometimes the only thing you can do is go to the machine and walk through the settings as if it was the first time. I can't tell you how many times a problem has resolved itself after just logging into the admin and redoing the settings. I mean the exact settings that are already selected. Sometimes the settings were actually wrong, even ones that came from an identical image. Like forgetting to select the observe and control selections in the sharing options for all the users. Other times it was simply deselecting and reselecting the options and restarting that snapped the machine out of the funk.
Aside from the occasional discovery of admin setup issues, I live by the motto "the simplest solutions are usually the best, and should be tried first". Glitches do happen though. Sometimes running the scanner and reselecting and dragging the same machine into your user lists can refresh a connection that is not acting properly. I have detected countless quirks that cause strange side effects. Do a get info on the specific machine and delete the IP, then make sure you have the "name".local in the DNS name field. Re-enter the admin or try a user account name in this experiment and test this. This has given me clues to setup issues before having to go to the machine. I know this stuff sounds simplistic but it has solved most of my issues.
Good Luck

Local home directories vs network home directories?

Similar Messages

Maybe you are looking for