AD/OD Integration for Tiger

Authored by: Anonymous on Tuesday, October 25 2005 @ 08:24 am MDT

Has anyone had any success setting disc quotas in this scenario? I've
tried:
sudo edquota -u username
to set a prototype user
sudo edquota -p username
to copy that users settings to everyone else
followed by:
sudo serveradmin settings afp:updateHomeDirQuota = no
to stop afp resetting the quotas.

repquota gave me long list of quotas all with the same username: that of
the prototype user.

I've tried creating the .quota.user and .quota.group files myself, setting
the priveliges to 640, ower = root, group = admin

and running edquota again / using webmin

webmin produced the same outcome as mentioned above.

Now i'm really struggling with a perl script someone has sent me (i know
nothing about perl).

For me, edquota has always produced very flakey results
consistantly over the past year i've been trying to do this. webmin seemed
to be promising but produced the same results

I've never got disc quotas to work.

Am i alone?

Any suggestions??

or magic (easy to use) scripts / lovely Aqua GUI tools knocking around out
there??????

[ Reply to This | # ]

Authored by: tdassel on Monday, November 07 2005 @ 10:15 am MST

Hello,

we are just pulling our hair out, when trying to get network home folders to work with users that log into their Macs using their Active Directory account.
They have the path to their home in their AD profile.
Now comes the part, were AFP seems to have a bug.
If a user belongs to more then 12 groups in AD ( Member of ... ) he gets the annoying message that the home folder is located on a afp or smb volume that he can't be logged in at this time.
Remove any group and it works like a charm if you are below 12 group memberships.
As 12 is not exactly a natural border ( like 8, 16, 32, 64... ) we simply don't know what is wrong with AFP.
If you do the same with the settings in Directory Services changed to SMB, everythings works, no mater how many groups you are a member of.
If you have a Profile Path set ( in AD: Profile -> User Profile ) you will not get far either, as this will result in the same message.
The problem to nail down the problem, because the logs are not really helping ( or am I locking in the wrong places ? )

Anybody who has the same problem ?

Is there a complete list of causes for the homeshare on afp / smb share " bug ?

Thomas

[ Reply to This | # ]

Authored by: krknopp on Wednesday, February 08 2006 @ 06:21 pm MST

I've looked all over and can't find if the newly created Open Directory needs to
be the same as the Active Directory name or if it needs a different DNS name.
i.e. AD DNS name: test.lan. Does the OD name need to be test.lan or
test.ldap?

[ Reply to This | # ]