[rmniemela]

Good suggestion, except that when I alter the activedirectory.plist file, the system overwrites the file on a reboot. Even worse, it deletes the whole line that I’ve adjusted.

For example, I’ve tried to adjust the following lines in the users section:

2.5.4.17
dsAttrTypeStandard:SMBHomeDirectory

where 2.5.4.17 is the AD field for postal_code.

This field is unused in our environment.

When I reboot the client, both lines have disappeared, even if I change the protection so that system has read only access.

[rmniemela]

If your accounts are in Active Directory, there is only one attribute (“field”) in the schema that is used to tell AD where the AD home folder is (actually it’s called a profile folder in AD).
Because the Mac AD plug-in uses that same attribute, that means that a user gets the same home folder location for both their AD and Mac home folders.

Our problem is we have users who log into both environments. We have to somehow find a way to direct their Windows profile folder to our Windows cluster server (an “smb” share) when they are logging into a PC; and if the same user logs into a Mac, we have to direct their Mac home folder to our Mac file server (an “afp” share). Otherwise, we’ll have to create separate accounts for each environment.

BTW, I’m the IT person responsible for AD in our environment. Because we are moving to AD 2003 (which allows us to reverse schema changes), I’m more than willing to experiment with adding the Apple-specific schema changes that are suggested on Gordon Shukwit’s site. I’ve actually added those schema changes to our test AD environment, but the AD plugin (at least in 10.3.8) doesn’t automatically use the additional attributes (apparently, it’s supposed to detect them and use them instead of the AD native attributes). That would solve all of our problems, but it doesn’t seem to be working for me.

[Author]

Posts