[AaronAdams]

Thanks for the info. I found a thread on the Apple support discussion board about this. Archiving OD, changing the server to a standalone, changing it back to an OD master, and restoring from the archive also solves the problem.

I think Apple really needs a more descriptive error message here.

[AaronAdams]

[QUOTE BY= AledDavies]OK. All this was discovered via trial and error and the Apple documentation. Your mileage may vary…[/quote]
Thanks for taking the time to write that out, I’m sure many of us will appreciate it as time goes on.

[QUOTE BY= AledDavies]You can set up a mobile directory using /Users however it will end up synching against itself which is really confusing as you won’t be warned of this.[/quote]
It seems kind dumb that you should be able to do this. Is there any real reason why you’d want to sync a home directory back onto itself? If not , shouldn’t there be a warning presented, if not an outright denial?

[QUOTE BY= Anonymous]When I login to the OSXS host, I am prompted to create a mobile home.

I told it “never” and it still asks every time I login. Any ideas?[/quote]
I have that same issue on all of my clients and the server. Also, they never remember my workgroup management settings. I’ve had that problem since Panther. Is this something I’m doing wrong?

[AaronAdams]

[QUOTE BY= AledDavies]Anyway I finally managed to get the Portable Home Directories to work. Turns out I hadn’t setup the User correctly in OpenDirectory.[/QUOTE]
Care to share the correct configuration details for those of us who aren’t quite as experienced?

[AaronAdams]

I’ve installed this update (after cloning of course!) on my server with no noticeable problems.

[AaronAdams]

I’m not sure if this is an acceptable solution for you, but I’ll offer it up.

Instead of rotating the logs, I use awstats to purge log records it has already processed. In the /etc/awstats/awstats.sitename.conf file, there are two sections to control this:

# AWStats can purge log file, after analyzing it. Note that AWStats is able
# to detect new lines in a log file, to process only them, so you can launch
# AWStats as often as you want, even with this parameter to 0.
# With 0, no purge is made, so you must use a scheduled task or a web server
# that make this purge frequently.
# With 1, the purge of the log file is made each time AWStats update is ran.
# This parameter doesn't work with IIS (This web server doesn't let its log
# file to be purged).
# Change : Effective for new updates only
# Possible values: 0 or 1
# Default: 0
# 
PurgeLogFile=1

# When PurgeLogFile is setup to 1, AWStats will clean your log file after
# processing it. You can however keep an archive file (saved in "DirData") of
# all processed log records by setting this to 1 (For example if you want to
# use another log analyzer).
# This parameter is not used if PurgeLogFile=0
# Change : Effective for new updates only
# Possible values: 0 or 1
# Default: 0
#
ArchiveLogRecords=1

This keeps my access_log small and provides an archive that I can compress and save for later if I need it.

[AaronAdams]

[QUOTE BY= macshome] The workgroup selection box comes up because you are logging in as an admin and the Mac thinks there are some mcx settings to apply.[/quote]
I understand why that happens now, thank you. But… (and there’s always a but) since I installed 10.3.6 on this machine, it has started remembering my choices. I cleared the “Enable workgroup management” checkbox and checked the “Remember my choices” box, and that window has not come back since. I don’t know if that’s a fix incorporated into 10.3.6, or if something changed on my system because of the install and now it it able to remember my preference.

[QUOTE BY= macshome]I’m curious as to your FUS scheme that you are using. We are integrating active directory and we just use the cached user account feature to make a mobile account. The users then just use that cached account when on the road or at home.[/quote]
I have two accounts on my machine, one that is a local account that I use for my personal things, and a second that is an AD-authenticated account that I use for work. It is also cached for use as a mobile account as you described. There really isn’t any technical reason I divide things into two accounts, it’s more for my own organization and logical consistency. I prefer not to mix business and personal files, and the items I need in my dock or on my desktop are different at work than they are at home, for instance.

[QUOTE BY= macshome]The mount is probably hanging around as automatically mounted home shares are pretty persistent. They are done that way so that when you log back in you jump right into the folder. In any case if you are logged out of that account then you can just dismiss the warning. It’s doing what it is supposed to by letting you know a network mount dropped.[/quote]
Understood.

[QUOTE BY= macshome]You might be loosing the AD authentication because the AD plugin seems to be pretty sensitive to network changes/irregularities and it tends to re-write /L/P/edu.mit.Kerberos at the drop of a hat. You can try removing the auto-config lines from said file after you have logged in a via AD successfully.[/quote]
This is another one of those things that was somehow fixed after I installed 10.3.6. Now I can change network locations and login and logout of accounts all day long and things work without having to kill the DirectoryServices component. I don’t know what Apple did, or even if they did anything at all, but I’m grateful.

Thanks for your help macshome.

[AaronAdams]

Here are the solutions I was given:

The “Enable Workgroup Management” window is a bug. It has something to do with the fact that my AD-based user is an admin in the domain and on the local machine, so the authentication window displays that dialog. I never completely understood this whole topic, but since it’s more of a minor annoyance than a work stopping problem, I just click through it and go on.

Secondly, every account on the machine seems to require a unique long name. For instance, my local account has a short name of aaron, my AD account has a short name of adamsa, but both have the long name Aaron Adams. Changing the long name of my local account fixed some of the authentication weirdness I was experiencing. I have no idea why the long name makes any difference. The short names and UIDs for each account are unique, why does it care what the long name is?

Lastly, I found out that when I switch locations and want to login to AD, I have to manually kill the DirectoryServices component so it will restart and straighten out whatever it needs to straighten out. I created an alias in my .bash_profile to execute this command:

sudo kill $(ps -ax | awk '/\/usr\/sbin\/DirectoryService/ {print $1}')

It seems to me that the OS should perform an operation like this on its own when I change locations. In my mind, there’s no reason why I should have to do this manually at the command line.

Admittedly, I don’t know as much about this whole topic as I should, as you can tell from the semi-informed and semi-technical reply I’ve provided here. If anyone can provide some insight into these matters, it would be greatly appreciated.

[Author]

Posts