[AgentOrange]

Hi everyone.

I have finally given the Leopard A.D. plug-in the punt! This will sound like a sales pitch.

I have moved on to Centrify which provides me with a much cleaner interaction between A.D. and my OS X clients.

Authentication is FAST, GPO’s(really GPO’s) are read by my OS X clients, and there are command line utilities that work for troubleshooting.

I could not have asked for a better solution.

The cost is very managable at $60/client.

I am in my final stages of testing and will be going live in my local environment next week.

If you have not tried it, do so. http://www.centrify.com

[AgentOrange]

lmadden,

Since you have the pre-release of 10.5.3 update; do you know if they fixed the issue that prevented non-admin users from being able to add printers?

Currently, upto 10.5.2, only admins can add printers.

[AgentOrange]

I don’t think you should have to shut down your Xserve. As long as the client is not bound to OD it should have “no” effect.

I am looking into a product called Centrify for OS X client management. Screw Steve and Apple…

I would still maintain the Xerve only for image deployments.

[AgentOrange]

Here is reply I have from a tech at Apple. If ANYONE is a member of Apple’s developer connection, maybe you could pass on a link for 10.5.3. Apparently it is to be released soon..with supposed “fixes”. This tech slipped and probably was not supposed to tell me this…

Greetings,

Apple does not provide any information about expected release dates.
Please set software update to check every day for updates.

Thank you, [I took his name out]
ACSA, ACXA
Apple, Inc.

On May 1, 2008, at 3:35 PM, I wrote:

> Thanks. Is there an expected release date for 10.5.3?
>
> Me
> E: [email protected]
> T:
> C:
>
>
>
> —– Original Message —–
> From: [I took his name out] [@apple.com]
> Sent: 05/01/2008 08:30 AM EST
> To: ME
> Subject: Case #….. – issue with active directory login and
> 10.5.2 clients
>
>
>
>
> Greetings,
>
> I have found a number of escalations related to AD integration. None
> of these report the exact same issue that you described over the phone
> yesterday, but they are similar. In one of the escalations, the admin
> seemed to have success by specifying a local directory of the user
> home for the first login and then changing the home to a network
> location after verifying that subsequent logins function. I still can
> not say that I know that engineering will be able to provide a
> resolution. It might be worth waiting for the 10.5.3 update, or if
> you are a member of the apple developer connection you can get the
> update now.
>
> Thank you, [I took his name out]
> ACSA, ACXA
> Apple, Inc.

[AgentOrange]

Unfortunately, I concur. This is now happening to me again. It was fine for about 4 days.

What is really frustrating is that Apple wants to charge $1000 to “try” and fix this problem and so far no Mac pro seems to have an answer on how to resolve this Leopard and AD problem.

[AgentOrange]

I have seen this and believe I have fixed it. Do this:

– Unbind your computer from AD

– /System/Library/PrivateFrameworks/FamilyControls.framework/Versions/A/Resources and backup and delete parentalcontrolsd

– reboot your computer

– Rebind to AD

– Try logging on/off a few times

Somehow, I think this parental controls is messing with the system and AD. Leopard so far to me seems to be no better than Windows Vista and UAC. At least in Vista, I can disable UAC.

One thing I found tho is that since doing this the test system I have is a wee bit slow. Not sure if this is related as it is an Intel Mac book with 2GB of ram(not exactly old hardware)

[Author]

Posts